Page 1 of 1
VirtualBox Error with VT-x/AMD-V after suspend
Posted: 26. Apr 2009, 11:45
by graysky
I using VB 2.2.0 on Arch Linux and have been doing so for a while now. Today I attempted to run my 64-bit guest VM and got this error from VB:
Code: Select all
VT-x/AMD-V hardware acceleration has been enabled, but is not operational. Your 64-bit guest will fail to detect a 64-bit CPU and will not be able to boot.
Please ensure that you have enabled VT-x/AMD-V properly in the BIOS of your host computer.
I rebooted and entered my BIOS. All my virtualization options are set to enable. Can anyone think of a reason why this would be happening?
Re: VirtualBox Error with VT-x/AMD-V
Posted: 26. Apr 2009, 14:36
by vbox4me2
Look for vt.iso to verify vt-x is actually working.
Re: VirtualBox Error with VT-x/AMD-V
Posted: 26. Apr 2009, 16:09
by graysky
vbox4me2 wrote:Look for vt.iso to verify vt-x is actually working.
I did a 'locate vt.iso' but found nothing.
UPDATE: I think I have pin pointed the cause of this problem. If I reset my BIOS to default settings, then reload my customized settings and boot into Linux, everything is fine. This problem starts when the machine gets suspended and then awakened. Upon waking up, the symptoms I described above occur and they survive a reboot! The only cure seems to be reseting the BIOS to default settings, then reloading my custom settings which is a drag.
Can anyone suggest why this might be happening? Are they any logs I can look into to help trouble-shoot?
Re: VirtualBox Error with VT-x/AMD-V
Posted: 26. Apr 2009, 16:17
by vbox4me2
Check for updates on your BIOS, sounds like a bios bug.
Re: VirtualBox Error with VT-x/AMD-V
Posted: 26. Apr 2009, 16:26
by graysky
vbox4me2 wrote:Check for updates on your BIOS, sounds like a bios bug.
I just checked, and I'm running the current BIOS revision.
A small update. entering the BIOS and resetting it is NOT necessary. If I
totally power down my system, then boot into Arch, the problem is gone and the 64-bit VM works just fine. If I just reboot, the problem is
not solved and the 64-bit VM does not work giving that error. This problem starts when the machine gets suspended and then awakened. Upon waking up, the symptoms I described above occur and they survive a reboot! Again, the only cure seems to be a power down then startup again (cold boot).
Are they any logs I can look into to help trouble-shoot?
Here are two logs relating to pm:
pm-powersave.log
Code: Select all
/usr/lib/pm-utils/power.d/sched-powersave false: **sched policy powersave OFF
success.
pm-suspend.log
Code: Select all
Initial commandline parameters:
Sun Apr 26 08:13:55 EDT 2009: Running hooks for suspend.
/usr/lib/pm-utils/sleep.d/00auto-quirk suspend suspend: Adding quirks from HAL: --quirk-dpms-on --quirk-dpms-suspend --quirk-vbe-post --quirk-vbemode-restore --quirk-vbestate-restore --quirk-vga-mode-3
success.
/usr/lib/pm-utils/sleep.d/00logging suspend suspend: Linux novelty 2.6.29-ARCH #1 SMP PREEMPT Fri Apr 17 14:14:28 CEST 2009 x86_64 Intel(R) Xeon(R) CPU X3360 @ 2.83GHz GenuineIntel GNU/Linux
Module Size Used by
ipv6 309664 16
cpufreq_userspace 3732 4
fuse 61136 4
joydev 12160 0
hid_microsoft 4116 0
usbhid 40288 0
hid 49280 2 hid_microsoft,usbhid
snd_hda_codec_realtek 255828 1
snd_seq_oss 33696 0
snd_seq_midi_event 7248 1 snd_seq_oss
snd_seq 56672 4 snd_seq_oss,snd_seq_midi_event
snd_seq_device 7236 2 snd_seq_oss,snd_seq
snd_hda_intel 29352 1
snd_hda_codec 67696 2 snd_hda_codec_realtek,snd_hda_intel
psmouse 54764 0
snd_pcm_oss 43424 0
snd_mixer_oss 16880 1 snd_pcm_oss
snd_hwdep 8568 1 snd_hda_codec
nvidia 8116408 30
i2c_i801 10512 0
uhci_hcd 25360 0
ohci1394 32516 0
sg 29664 0
iTCO_wdt 13072 0
iTCO_vendor_support 3540 1 iTCO_wdt
pcspkr 2800 0
snd_pcm 81176 3 snd_hda_intel,snd_hda_codec,snd_pcm_oss
snd_timer 22688 2 snd_seq,snd_pcm
snd 66504 13 snd_hda_codec_realtek,snd_seq_oss,snd_seq,snd_seq_device,snd_hda_intel,snd_hda_codec,snd_pcm_oss,snd_mixer_oss,snd_hwdep,snd_pcm,snd_timer
soundcore 7584 1 snd
snd_page_alloc 9728 2 snd_hda_intel,snd_pcm
ehci_hcd 39612 0
sky2 53364 0
ieee1394 88640 1 ohci1394
serio_raw 6132 0
i2c_core 24032 2 nvidia,i2c_i801
usbcore 161488 4 usbhid,uhci_hcd,ehci_hcd
intel_agp 30960 0
evdev 11616 8
thermal 18896 0
fan 5240 0
button 7312 0
battery 12504 0
ac 4984 0
acpi_cpufreq 8736 0
freq_table 4144 1 acpi_cpufreq
processor 44712 2 thermal,acpi_cpufreq
it87 27016 0
hwmon_vid 3696 1 it87
coretemp 7056 0
rtc_cmos 12056 0
rtc_core 20100 1 rtc_cmos
rtc_lib 2864 1 rtc_core
ext4 233096 2
mbcache 8148 1 ext4
jbd2 62912 1 ext4
crc16 1968 1 ext4
sd_mod 27528 6
sr_mod 16804 0
cdrom 37832 1 sr_mod
pata_acpi 5168 0
ata_generic 5908 0
pata_jmicron 3984 0
ahci 36128 4
libata 175468 4 pata_acpi,ata_generic,pata_jmicron,ahci
scsi_mod 117784 4 sg,sd_mod,sr_mod,libata
total used free shared buffers cached
Mem: 4045348 3801276 244072 0 1636308 1839996
-/+ buffers/cache: 324972 3720376
Swap: 2048248 0 2048248
success.
/usr/lib/pm-utils/sleep.d/00powersave suspend suspend: success.
/usr/lib/pm-utils/sleep.d/01grub suspend suspend: not applicable.
/usr/lib/pm-utils/sleep.d/11netcfg suspend suspend: success.
/usr/lib/pm-utils/sleep.d/49bluetooth suspend suspend: not applicable.
/usr/lib/pm-utils/sleep.d/55NetworkManager suspend suspend: success.
/usr/lib/pm-utils/sleep.d/75modules suspend suspend: not applicable.
/usr/lib/pm-utils/sleep.d/90clock suspend suspend: not applicable.
/usr/lib/pm-utils/sleep.d/94cpufreq suspend suspend: success.
/usr/lib/pm-utils/sleep.d/95led suspend suspend: not applicable.
/usr/lib/pm-utils/sleep.d/98smart-kernel-video suspend suspend: success.
/usr/lib/pm-utils/sleep.d/99video suspend suspend: kernel.acpi_video_flags = 0
success.
Sun Apr 26 08:13:56 EDT 2009: performing suspend
Sun Apr 26 10:05:28 EDT 2009: Awake.
Sun Apr 26 10:05:28 EDT 2009: Running hooks for resume
/usr/lib/pm-utils/sleep.d/99video resume suspend: success.
/usr/lib/pm-utils/sleep.d/98smart-kernel-video resume suspend: success.
/usr/lib/pm-utils/sleep.d/95led resume suspend: not applicable.
/usr/lib/pm-utils/sleep.d/94cpufreq resume suspend: success.
/usr/lib/pm-utils/sleep.d/90clock resume suspend: not applicable.
/usr/lib/pm-utils/sleep.d/75modules resume suspend: success.
/usr/lib/pm-utils/sleep.d/55NetworkManager resume suspend: success.
/usr/lib/pm-utils/sleep.d/49bluetooth resume suspend: not applicable.
/usr/lib/pm-utils/sleep.d/11netcfg resume suspend: success.
/usr/lib/pm-utils/sleep.d/01grub resume suspend: not applicable.
/usr/lib/pm-utils/sleep.d/00powersave resume suspend: success.
/usr/lib/pm-utils/sleep.d/00logging resume suspend: success.
/usr/lib/pm-utils/sleep.d/00auto-quirk resume suspend: success.
Sun Apr 26 10:05:29 EDT 2009: Finished.
Re: VirtualBox Error with VT-x/AMD-V
Posted: 26. Apr 2009, 16:49
by vbox4me2
Take this to bugtracker so the devellopers can see if this is a VBox problem or not.
Re: VirtualBox Error with VT-x/AMD-V
Posted: 26. Apr 2009, 18:25
by graysky
vbox4me2 wrote:Take this to bugtracker so the devellopers can see if this is a VBox problem or not.
Can do... what's the URL to access the bugtracker?
UPDATE: I just booted into Windows XP x64 edition and repeated this bug so it's probably not a Linux issue, it's either a problem with VBox, or with my system/Motherboard.
Can anyone else out there who has a 64-bit VM (Windows, or Linux host) please give this a try and report back?
1) Verify that the 64-bit VM works
2) Suspend your host machine then wake it back up
3) Try to run your 64-bit VM again and see if you get the same result I do
Re: VirtualBox Error with VT-x/AMD-V after suspend
Posted: 27. Oct 2009, 00:12
by danstiner
I have this issue also in Windows 7 64bit with any VT-x vm's after resuming from a suspend state.
Using a eVGA 680i LT mobo with a E6750 Intel Core 2 Duo
Might attempt a bios update sometime to see if that fixes it, but I'm none to hopeful.