Ubuntu guest won't boot after update

[brycesteiner]

Hello,
I installed 4.2.12 yesterday and it seemed to go well. I included the extension pack and it booted. I then installed the guest additions in Ubuntu. I think I'm runn 4.12 (but not certain). I went to boot the guest up and it no goes anywhere but halts on a black screen. Anything i can do? I use it strictly for KmyMoney.
The windows XP virtual machines seem to work fine.

This is a Mac OSX 10.8.3 host

thanks,
Bryce

[Perryg]

Post the guests log file (as an attachment)
See Online Users Manual for the location of the file.

[achilles0101]

Yeah, same issue here. I get the low graphics message in UBuntu and cannot access the login screen. After uninstalling the guest tools I get access to Unity again. I have replicated the problem several times by uninstalling the tools and reinstalling them several times. The problem is clearly in the guest tools. I have tested the guest tools in a WIndows guest (XP) and no issues there. My host is UBuntu 13.0464bit and my UBuntu guest was 12.0464bit.

[Perryg]

Still don't see a guest log. At this point all we know is it does not work, but that is little to go on.

[brycesteiner]

I reinstalled the Guest additions from the command line and no change. The file is attached.

thanks,
Bryce

[rolfi]

The same here: Linux does not boot after update the guest additions. Host is OS X 10.8.3, guest is Xubuntu Precise Pangolin (32 Bit). Any suggestions who to uninstall the guest additions? I can ping the vm and I can access the vm via samba. How can I get a shell on the vm to try to uninstall the guest additions? SSH doesn't work. Thanks.

[brycesteiner]

Going back to 4.2.10 allowed me to get my work done and the Guest additions work fine.

[noteirak]

This seems to be a common issue : please discuss it on the release specific topic.

[mpack]

Updating a VM while it is suspended often causes problems. Try discarding the saved state.

[brycesteiner]

I always shutdown the virtual machines and don't have any saved states. Reverting back to 4.2.10 fixed it for me.

[mpack]

I always shutdown the virtual machines and don't have any saved states.

The log you posted seems to say otherwise. It seems to me to show a VM resuming from a saved state. Naturally, reverting to the correct VBox version will fix the problem, as will discarding the saved state as I suggested.

03:05:02.477545 Changing the VM state from 'RUNNING' to 'SUSPENDING'.
03:05:02.504678 AIOMgr: Endpoint for file '/Users/brycesteiner/VirtualBox VMs/Linux 12.04/Linux 12.04.vdi' (flags 000c0781) created successfully
03:05:02.556275 PDMR3Suspend: 78 698 294 ns run time
03:05:02.556301 Changing the VM state from 'SUSPENDING' to 'SUSPENDED'.
03:05:14.228107 Changing the VM state from 'SUSPENDED' to 'RESUMING'.
03:05:14.228815 AIOMgr: Endpoint for file '/Users/brycesteiner/VirtualBox VMs/Linux 12.04/Linux 12.04.vdi' (flags 000c0723) created successfully
03:05:14.253702 Changing the VM state from 'RESUMING' to 'RUNNING'.

[Perryg]

I see those as well but looking at the short time interval it appears to be something that VirtualBox is doing to try to fix an issue
Time elapsed is only like 12 seconds from suspend to resumed.

There is defiantly an issue with this build on certain hosts and guests. It really needs to be posted at viewtopic.php?f=1&t=55091 so the DEVs can see and fix this.

[mpack]

Time elapsed is only like 12 seconds from suspend to resumed.

Doesn't the clock stop? Isn't time suspended along with everything else?


ps. I added a link to this topic in the 4.2.12 discussion thread.

[Perryg]

It sort of depends. Take a snapshot or use pause and the time would be close to what you are seeing here. When I save state this is what the log shows:

Code: Select all

00:22:45.390053 Changing the VM state from 'RUNNING' to 'SUSPENDING'.
00:22:45.407750 AIOMgr: Endpoint for file '/drive/tara1/VirtualBox-VMs/openSUSE-KDE/openSUSE-KDE.vdi' (flags 000c0781) created successfully
00:22:45.460607 PDMR3Suspend: 70 511 255 ns run time
00:22:45.460624 Changing the VM state from 'SUSPENDING' to 'SUSPENDED'.
00:22:47.382888 Changing the VM state from 'SUSPENDED' to 'SAVING'.
00:22:47.383112 VUSB: detached 'HidMouse' from port 1
00:22:53.193513 SSM: Footer at 0x225caacf (576498383), 36 directory entries.
00:22:53.193537 VUSB: attached 'HidMouse' to port 1
00:22:53.193748 SSM: Successfully saved the VM state to '/drive/tara1/VirtualBox-VMs/openSUSE-KDE/Snapshots/2013-04-11T02-27-36-627375000Z.sav'
00:22:53.193755 Changing the VM state from 'SAVING' to 'SUSPENDED'.
00:22:53.193772 Console::powerDown(): A request to power off the VM has been issued (mMachineState=Saving, InUninit=0)
00:22:53.193803 Changing the VM state from 'SUSPENDED' to 'POWERING_OFF'.

Now when I start the guest is actually creates a new log file.

Thank you for posting a link to the proper place. These seem to be getting scattered all over the place.

[mpack]

Ok, so when you intentionally suspend a VM you get those additional messages about successfully writing the .SAV file and stopping the VM.

This begins to look more like VirtualBox might be implementing power saving in a new way... except I'd expect that to kick in 20mins or so after booting, not prevent the VM from booting at all.