VM crash

Discussions related to using VirtualBox on Windows hosts.
Locked
rudolfr
Posts: 10
Joined: 27. Dec 2010, 12:59
Primary OS: MS Windows 7
VBox Version: PUEL
Guest OSses: 4.0.0

VM crash

Post by rudolfr »

Hello,

my VM crahs always if i start it. Here there are my log from the starting in the normal mode and also in the safe mode

Code: Select all

00:00:12.419 PIIX3 ATA: LUN#0: aborting current command
00:00:27.038 PIIX3 ATA: Ctl#0: RESET, DevSel=0 AIOIf=1 CmdIf0=0xe1 (-1 usec ago) CmdIf1=0xa0 (-1 usec ago)
00:00:27.039 PIIX3 ATA: Ctl#0: finished processing RESET
00:00:27.039 PIIX3 ATA: LUN#1: performing device RESET
00:00:27.203 Guest Additions information report: Version 4.0.0 r69151 '4.0.0'
00:00:27.203 Guest Additions information report: Interface = 0x00010004 osType = 0x00033000
00:00:27.203 Guest Additions capability report: (0x0) seamless: no, hostWindowMapping: no, graphics: no
00:00:27.211 Guest reported fixed hypervisor window at 0x00000000b9c00000 (size = 0xc00000, rc = VINF_SUCCESS)
00:00:34.670 Audio: set_record_source ars=0 als=0 (not implemented)
00:00:34.674 Audio: set_record_source ars=0 als=0 (not implemented)
00:00:35.040 PCNet#0: Init: ss32=1 GCRDRA=0x081f3420[64] GCTDRA=0x081f3020[64]
00:00:35.068 Guest Log: VBoxVideo: using HGSMI
00:00:39.538 Display::handleDisplayResize(): uScreenId = 0, pvVRAM=0000000008300000 w=1280 h=760 bpp=32 cbLine=0x1400, flags=0x1
00:00:39.549 Guest Log: VBoxDisp[0]: VBVA enabled
00:00:39.549 Display::handleDisplayResize(): uScreenId = 0, pvVRAM=0000000008300000 w=1280 h=760 bpp=32 cbLine=0x1400, flags=0x1
If i start in the safe mode it works, here is the log:

Code: Select all

00:00:10.215 PIT: mode=2 count=0xffff (65535) - 18.20 Hz (ch=0)
00:00:11.694 PIIX3 ATA: LUN#0: IDLE IMMEDIATE, CmdIf=0xef (-1 usec ago)
00:00:11.694 PIIX3 ATA: LUN#0: aborting current command
00:00:25.765 PIIX3 ATA: Ctl#0: RESET, DevSel=0 AIOIf=1 CmdIf0=0xe1 (-1 usec ago) CmdIf1=0xa0 (-1 usec ago)
00:00:25.765 PIIX3 ATA: Ctl#0: finished processing RESET
00:00:25.765 PIIX3 ATA: LUN#1: performing device RESET
00:00:25.900 Guest Additions information report: Version 4.0.0 r69151 '4.0.0'
00:00:25.900 Guest Additions information report: Interface = 0x00010004 osType = 0x00033000
00:00:25.900 Guest Additions capability report: (0x0) seamless: no, hostWindowMapping: no, graphics: no
00:00:25.909 Guest reported fixed hypervisor window at 0x00000000b9c00000 (size = 0xc00000, rc = VINF_SUCCESS)
00:00:31.493 Display::handleDisplayResize(): uScreenId = 0, pvVRAM=00000000081e0000 w=1152 h=864 bpp=32 cbLine=0x1200, flags=0x1
00:00:48.714 PATM: Disable block at 8070b918 - write 8070b972-8070b976
00:01:05.368 Guest requests the VM to be turned off
00:01:05.368 Changing the VM state from 'RUNNING' to 'POWERING_OFF'.
Whats the reason for this?
Attachments
FH-2011-01-23-18-18-56.log
safe mode
(59.6 KiB) Downloaded 11 times
FH-2011-01-23-17-58-40.log
normal mode
(62.88 KiB) Downloaded 7 times
Perryg
Site Moderator
Posts: 34369
Joined: 6. Sep 2008, 22:55
Primary OS: Linux other
VBox Version: OSE self-compiled
Guest OSses: *NIX

Re: VM crash

Post by Perryg »

What is the guest? 32 or 64 bit?
rudolfr
Posts: 10
Joined: 27. Dec 2010, 12:59
Primary OS: MS Windows 7
VBox Version: PUEL
Guest OSses: 4.0.0

Re: VM crash

Post by rudolfr »

the guest system is a 32 bit Windows XP pro.
the host system is a 64 bit windows 7 system
Perryg
Site Moderator
Posts: 34369
Joined: 6. Sep 2008, 22:55
Primary OS: Linux other
VBox Version: OSE self-compiled
Guest OSses: *NIX

Re: VM crash

Post by Perryg »

Your log shows that your hardware virt is locked out so you must make sure you do not try to use it or fix what is causing the problem.
XP guest should not have IO APIC enabled (since SMP support requires hardware virt).
rudolfr
Posts: 10
Joined: 27. Dec 2010, 12:59
Primary OS: MS Windows 7
VBox Version: PUEL
Guest OSses: 4.0.0

Re: VM crash

Post by rudolfr »

When i disable the IO APIC the system will not start, so i must enable it.
I have a version where i know that it work its a image before i chance everything. After updating VM and the graphic driver in the host it crash now. the guest system is clean/ok i think.
Perryg
Site Moderator
Posts: 34369
Joined: 6. Sep 2008, 22:55
Primary OS: Linux other
VBox Version: OSE self-compiled
Guest OSses: *NIX

Re: VM crash

Post by Perryg »

Once you enable IO APIC, Windows will try to update the single-processor kernel to the multi-processor kernel.
You can try to start the guest in safe mode and use the Windows system restore to a time before you started messing with the settings, but if you must leave IO APIC enabled you will need to fix the issue where hardware virt is locked or disabled.
rudolfr
Posts: 10
Joined: 27. Dec 2010, 12:59
Primary OS: MS Windows 7
VBox Version: PUEL
Guest OSses: 4.0.0

Re: VM crash

Post by rudolfr »

My problem is is make an appliance import from a vm where i know that this was in function, i use this a long time after making. But now when i import this vm it have this problem. After i install the new Nvidia Driver (i was go back to the old version) and the new vm version now it make problem.
so my opinion is that here is the trouble. because i have start in the safe mode and see no problem

i become now a new window from windows. this one see attachment. On the windows site there is a problem with bios or the graphic card. so i think there is an problem in the VM
Attachments
Zwischenablage04.jpg
Zwischenablage04.jpg (17.57 KiB) Viewed 3674 times
Perryg
Site Moderator
Posts: 34369
Joined: 6. Sep 2008, 22:55
Primary OS: Linux other
VBox Version: OSE self-compiled
Guest OSses: *NIX

Re: VM crash

Post by Perryg »

You can not install special drivers for the video, as that will create this problem you are seeing.
The guest must use the vbox video drivers to function.
rudolfr
Posts: 10
Joined: 27. Dec 2010, 12:59
Primary OS: MS Windows 7
VBox Version: PUEL
Guest OSses: 4.0.0

Re: VM crash

Post by rudolfr »

I mean i install the grafic driver for nvidia in my host system not in the guest system. sorry for this mistake.

i use in the guest the driver from virtualbox here is the screenshot from the hardware on the guest system in the safe mode.
Attachments
Zwischenablage02.jpg
Zwischenablage02.jpg (41.61 KiB) Viewed 3665 times
Perryg
Site Moderator
Posts: 34369
Joined: 6. Sep 2008, 22:55
Primary OS: Linux other
VBox Version: OSE self-compiled
Guest OSses: *NIX

Re: VM crash

Post by Perryg »

Alright, what does it say under the Computer tab in the device manager?
rudolfr
Posts: 10
Joined: 27. Dec 2010, 12:59
Primary OS: MS Windows 7
VBox Version: PUEL
Guest OSses: 4.0.0

Re: VM crash

Post by rudolfr »

as attachment see the screenshot
Attachments
Zwischenablage02.jpg
Zwischenablage02.jpg (48.96 KiB) Viewed 3661 times
Perryg
Site Moderator
Posts: 34369
Joined: 6. Sep 2008, 22:55
Primary OS: Linux other
VBox Version: OSE self-compiled
Guest OSses: *NIX

Re: VM crash

Post by Perryg »

~~~~
00:00:00.599 IOAPIC <integer> = 0x0000000000000001 (1)
~~~~
[/Devices/ioapic/0/] (level 3)
00:00:00.599 Trusted <integer> = 0x0000000000000001 (1)
~~~~
00:00:00.913 HWACCM: No VT-x or AMD-V CPU extension found. Reason VERR_VMX_MSR_LOCKED_OR_DISABLED
This needs to be addressed.
You should also look and see if you have intelppm.sys on the guest and if so rename it to intelppm.sys.old while in safe mode.
rudolfr
Posts: 10
Joined: 27. Dec 2010, 12:59
Primary OS: MS Windows 7
VBox Version: PUEL
Guest OSses: 4.0.0

Re: VM crash

Post by rudolfr »

I started windows in the safe mode and rename the intelppm.sys in the directory C:\Windows\System32\drivers into intelppm.sys.old
but its the same problem like before.
Locked