VirtualBox

Opened 14 years ago

Last modified 6 years ago

#7009 reopened defect

Starting VM with Intel-VT enabled freezes system

Reported by: Linuxhippy Owned by:
Component: VMM/HWACCM Version: VirtualBox 3.2.10
Keywords: Cc:
Guest type: other Host type: Linux

Description (last modified by Frank Mehnert)

When starting a VM on my laptop with Intel-VT enabled, the host freezes immediatly. As workarround I can disable VT in BIOS.

I experience the problem with: VirtualBox-3.2.4 and 3.1 Fedora-12 and Fedora-13 + rawhide-2.6.34

Because the system freezes immediatly after starting the VM, log files are empty. I'll attach a log file generated when VT was disabled.

Attachments (2)

VBox.log (71.9 KB ) - added by Linuxhippy 14 years ago.
vmware.log (71.7 KB ) - added by Linuxhippy 13 years ago.

Download all attachments as: .zip

Change History (26)

by Linuxhippy, 14 years ago

Attachment: VBox.log added

comment:1 by Frank Mehnert, 14 years ago

I assume that you can re-enable VT-x in your BIOS but disable the VT-x/AMD-V checkbox in the VM settings. Could you test this as well? Did you ever install an older version of VirtualBox on this machine?

comment:2 by Frank Mehnert, 14 years ago

Resolution: worksforme
Status: newclosed

No response, closing.

comment:3 by Linuxhippy, 14 years ago

Resolution: worksforme
Status: closedreopened

Sorry for the late response, was quite busy lately. I updated to VirtualBox-3.2.8 + Linux-2.6.34.3 and the problem still persists.

As soon as the VirtualBox logo disappears in the VM-Window the whole system freezes, disabling VT in Bios or using VirtualBox's checkbox helps. Disabling "Nested Pages" while leaving "IVT" turned on did not help.

comment:4 by Linuxhippy, 14 years ago

And yes, I remember I tried VirtualBox-3.1.? some time ago and experienced the same problem.

comment:5 by Frank Mehnert, 14 years ago

Were you ever able to execute any other VMM on your host working in VT-x mode? We have some reports about freezes in VT-x mode, some of them were solved by a BIOS update.

comment:6 by Linuxhippy, 14 years ago

Yes, VMWare-Player works with VT-x enabled.

The machine is a Tecra-A8 Laptop with one of the first Core2Duos (stepping 6 / B2), but has a recent BIOS.

Thanks, Clemens

comment:7 by Linuxhippy, 14 years ago

So is there anything I can do to get this problem fixed, like providing information or running test-cases?

comment:8 by Frank Mehnert, 13 years ago

Component: otherVMM/HWACCM

comment:9 by Sander van Leeuwen, 13 years ago

How sure are you that VMWare Player used VT-x on your system?

comment:10 by Linuxhippy, 13 years ago

Pretty sure

comment:11 by Sander van Leeuwen, 13 years ago

Either you're 100% sure or you're not. :) Select hardware virtualization in the setting dialog and upload the VM session log please.

comment:12 by Linuxhippy, 13 years ago

Either you're 100% sure or you're not

You asked how sure I am, not wether or not. I know I had VT-x enabled, but I didn't read the logs to validate wether it was really used.

Select hardware virtualization in the setting dialog and upload the VM session log please.

Doesn't work, VirtualBox crashes the system instantly, there are no logs after the crash.

comment:13 by Linuxhippy, 13 years ago

By the way, still happens with 3.2.10 + 2.6.34.7. So what can I do to bring this foreward?

comment:14 by Frank Mehnert, 13 years ago

Version: VirtualBox 3.2.4VirtualBox 3.2.10

comment:15 by Sander van Leeuwen, 13 years ago

I've asked you for the VMWare log of the session which you say uses VT-x. Please attach that.

comment:16 by Linuxhippy, 13 years ago

Still happens with VirtualBox-4.0.2, on a fresh Fedora-14 installation (2.6.35.11-83.fc14.i686).

vmware log attached.

by Linuxhippy, 13 years ago

Attachment: vmware.log added

comment:17 by enteon, 13 years ago

Can confirm this bug on Debian Squeeze 32 Bit (2.6.32) ; VirtualBox OSE 3.2.10 and 4.0.2 ; Thinkpad T60 T7200 CPU, latest BIOS.

Using 32 Bit Windows kernel (installed and Installation DVD) 7 and XP.

Even more weird: NO freeze IF there is no battery present. In which case the BIOS won't allow any faster CPU multiplicator than the slowest (1GHz, fastest would be 2GHz). Even though VT-x is enabled!

But as soon as the CPU may switch its frequency I have to disable VT-x in order to run any of the Windows kernels.

There is nothing in /var/log/messages except for "'VirtualBox' uses 32-bit capabilities (legacy support in use)", which was pretty obvious to me.

in reply to:  17 comment:18 by enteon, 13 years ago

Nevermind, happened in KVM too so i figured out that my CPU got too few volts. My bad.

comment:19 by Linuxhippy, 13 years ago

This is one of those typical bug-reports. One of those which make me regret I spend my time again and again.

I file it, then I am asked about tons of information (in this case I set up VMWare, just to get the log file) - and when there is finally nothing left which would stop investigation the report just rots and nobody cares.

comment:20 by Mihai Hanor, 13 years ago

You have not provided any information that can be analyzed, the cause of your hangs is not contained in the files you provided. If the devs can't reproduce the issue, they can't tell what's going wrong.

Try to monitor the live vbox.log file, the linux system logs (e.g. /var/log/kern.log, daemon.log, messages and dmesg), while starting the VM, from a local console window (tail -f to follow), or over a ssh session, or (even better) over a serial (COM) console. Run VB headless, so you can run from the full-blown textmode linux console, and not from X.

Also, you can try to learn how to debug a fozen linux kernel. Search on google for "debugging linux hangs", "linux hard lockup", "linux magic SysRq key" and other similar key words/combinations. Here's a some useful links, things should be similar for Fedora:
http://en.wikibooks.org/wiki/Linux_Guide/Freezes#Alt.2BSysRq
http://www.av8n.com/computer/htm/kernel-lockup.htm

comment:21 by Frank Mehnert, 10 years ago

Description: modified (diff)
Resolution: fixed
Status: reopenedclosed

Please reopen if still relevant with VBox 4.3.2.

comment:22 by Mahdi, 6 years ago

Resolution: fixed
Status: closedreopened

I have same problem. I am ready to give you remote assistance permission.

Virtualbox 5 (latest version in software center) Ubentu 16.04 Thinkpad e560 (Purchased in asia)

Version 1, edited 6 years ago by Mahdi (previous) (next) (diff)

comment:23 by Linuxhippy2, 6 years ago

frank: I could give it a try on the affected machine - but that would mean some work installing a recent linux version etc. And to be honest I wonder why I should do the work - in the 7 years since I've reported this issue, not a single VirtualBox engineer found it worth to investigate. So if there are no ressources to investigate this issue, I see no sense in keeping it alive (or better - closing it) to the sake of statistics.

Mahdi: What processor type does the Thinkpad e560 have?

comment:24 by Mahdi, 6 years ago

x64 I think (Intel® Core™ i5-6200U CPU @ 2.30GHz × 4 )

Note: See TracTickets for help on using tickets.

© 2023 Oracle
ContactPrivacy policyTerms of Use