virtualbox.org

hi guys,

i have a VM in a windows server2008 host,which a xp client is installed in. and while booting i see 4 options to boot:
the timer goes on and the VM hangs there,showing some vertical lines which wont be filled (sometimes). i have searched similar problem in this forum and i have tried following solutions which none of them worked:

1-disabling 3D acceleration
2-increasing RAM and Graphic Memory to 512 and 16 and even more
3-disabling audio or changing the type from ac to sb
4-running the VM in another host

please help me! the logs are attached!

It looks like in the older log you suspended the VM after it had been running for 50mins or so. According to the log there was a glitch at the time, I don't know if its significant...
In the log of the later session the VM attempts to read the saved state, but immediately suspends the VM again.

I suspect that you may have to discard the saved state (right click VM, choose appropriate menu item). I also have a prejudice against relying on features such as "save state" - hence I would recommend that you take that little extra time to shut VMs down fully in future.

mpack wrote:It looks like in the older log you suspended the VM after it had been running for 50mins or so. According to the log there was a glitch at the time, I don't know if its significant...

Code: Select all

00:00:54.933 Changing the VM state from 'SUSPENDING' to 'SUSPENDED'.
00:01:04.085 ERROR [COM]: aRC=VBOX_E_INVALID_VM_STATE (0x80bb0002) aIID={515e8e8d-f932-4d8e-9f32-79a52aead882} aComponent={Console} aText={Invalid machine state Paused when checking if the guest entered the ACPI mode)}, preserve=false
00:01:07.561 Changing the VM state from 'SUSPENDED' to 'SAVING'.

In the log of the later session the VM attempts to read the saved state, but immediately suspends the VM again.

I suspect that you may have to discard the saved state (right click VM, choose appropriate menu item). I also have a prejudice against relying on features such as "save state" - hence I would recommend that you take that little extra time to shut VMs down fully in future.

my dear friend,

the VM is not in saved state,hence the discard menu is disabled. do you have any other solution in mind? when i close my VM(after hanging), i have two available options,saving the state,and shut down, according to your analysis i also tried saving the state once and discarding afterward and turning the VM on again,but didn't solve the issue.

The more recent log definitely shows the VM being restored from a saved state - in fact I quoted that section of the log above. It's hard to see how the VM could attempt to restore from a saved state without being aware that a saved state exists.

mpack wrote:The more recent log definitely shows the VM being restored from a saved state - in fact I quoted that section of the log above. It's hard to see how the VM could attempt to restore from a saved state without being aware that a saved state exists.

in order to show logs for the VM,i clicked Machine Menu and then show log,there are four log tab windows,which of them are the log? may be i'm attaching two of them which belongs to past!

The leftmost log "VBox.log" is the newest.

mpack wrote:The leftmost log "VBox.log" is the newest.

This is the newest Log of my last try to start the VM,my friend.

thank you for your time.

Your log looks similar to mine until it attempts to boot from the VM disks. Mine goes on to several other things, whereas yours seems to fail at that point.

VBox.log wrote: 00:00:03.443 Guest Log: BIOS: Boot from Floppy 0 failed
00:00:03.444 Guest Log: BIOS: CDROM boot failure code : 0003
00:00:03.445 Guest Log: BIOS: Boot from CD-ROM failed
00:00:03.445 Guest Log: BIOS: Booting from Hard Disk...
00:00:03.844 Guest Log: BIOS: int13_harddisk: function 15, unmapped device for ELDL=81
00:00:16.722 Changing the VM state from 'RUNNING' to 'SUSPENDING'.
00:00:16.752 Changing the VM state from 'SUSPENDING' to 'SUSPENDED'.

Mine does not have the line about trying "ELDL=81". I believe ELDL is a BIOS id for your hard disk. Your normal boot hard disk is ELDL=80, so I interpret that line as meaning that a boot sector was not found on the main boot drive so it looked for a second drive, and that failed too. It then fell through the bootstrap and the VM terminated!

In other words I suspect corruption of the boot sector of the boot disk. You can try using fixmbr and/or fixboot (Google for them), or even better would be to restore the drive from that backup copy you made recently! Hopefully you have not complicated matters by using snapshots.

Just to clarify: was this ever a fully working VM? And if yes, what happened before it stopped working?

mpack wrote:Just to clarify: was this ever a fully working VM? And if yes, what happened before it stopped working?

yes it was! actually i installed a Hyper-V Roll in my host machine-which is server2008- and the VM got too slow,so i removed the roll and i remember during the installation i was forced to reboot the system manually at a time,because the host was not responding properly, and after removing Hyperv Roll, the VM never started again...

I meant, was it ever a working VirtualBox VM? If it has only ever worked as a Hyper-v VM then migration problems are to be expected.

mpack wrote:I meant, was it ever a working VirtualBox VM? If it has only ever worked as a Hyper-v VM then migration problems are to be expected.

yes it was a working virtualBox VM! i wanted to run another seperate Hyper-v VM machine which was not related to this VM, this one was only a simple Virtualbox VM!

I am having the same problem and can see the exact same error in my log. When powering off the VM it gets stuck in the "powering off" state and never resumes. I am using Virtual-Box 4.0.16 Guest OS: Red Hat 2.6.32 Host Machine Operating System: Linux. Are you same having the same issues or have you managed to resolve the problem?