Discuss the 4.3.22 release
-
- Site Moderator
- Posts: 39134
- Joined: 4. Sep 2008, 17:09
- Primary OS: MS Windows 10
- VBox Version: PUEL
- Guest OSses: Mostly XP
Re: Discuss the 4.3.22 release
Augmenting search engines doesn't seem to have worked: the first post of this discussion could hardly be clearer, yet people still post to this thread as if they haven't read it!
-
- Posts: 76
- Joined: 7. Oct 2012, 18:24
Re: Discuss the 4.3.22 release
I downgraded back to 4.3.10 and the sound works again.Brutalizer wrote:I am running Solaris 11.2 as host. I have installed Win7 in a VM and it works fine. I have also cloned the VM but in the clone the sound does not work at all. Any clues?
UPDATE: the original VM has a working sound, whereas the clone has no sound.
Last edited by Brutalizer on 3. Mar 2015, 22:44, edited 1 time in total.
Re: Discuss the 4.3.22 release
Aargh, i was premature in saying the Failed to load unit 'pgm' (VERR_NO_MEMORY) happens now, contrary to 4.3.16-4.3.20, only the first time after the upgrade. While resuming seemed to work once after the discard of saved state and subsequent suspend, it now consistently fails again with following errorg2flyer wrote:As i wrote, this time discarding saved state makes it work also for the future (not true in earlier versions).mpack wrote:@g2flyer: please discard the saved state associated with the VERR_NO_MEMORY VM. In future, best make sure VMs are fully shut down before you swap software versions from underneath them.
Regarding your suggestion to do proactively shutdown all VMs before an upgrade is not a really good solution when you have lots of VM. And, more importantly, this was never necessary before the problem arrived in 4.3.18!!
Code: Select all
Failed to open a session for the virtual machine Win7 KVM.
Failed to load unit 'pgm' (VERR_NO_MEMORY).
Result Code: NS_ERROR_FAILURE (0x80004005)
Component: Console
Interface: IConsole {8ab7c520-2442-4b66-8d74-4ff1e195d2b6}