fail to boot with VT-x/AMD-V in 1.6

bl · Post by bl » 3. May 2008, 16:44

Hardy amd64 VM fail to boot, just a black screeb (can not see the man holding the notebook) with VT-x/AMD-V enabled. It worked on the previous version.

monstbox · Post by **monstbox** » 3. May 2008, 16:55

Yep same problem here. I came here to find a solution and went to post this topic and this one beat me to it. I am on AMD64x2 Turion. This worked really well in the 1.5.6 version for the first time for me then in 1.6 it is broke again

billstei · Post by **billstei** » 3. May 2008, 17:14

Same on Ubuntu Gutsy / VB 1.6. Turned off Vt-x/AMD-V and now it boots.

Post by **Sasquatch** » 3. May 2008, 17:15

Intel T2300, VT-x support, no problems booting it. If you guys run the 64 bit version, perhaps running the x86 will let it work? My CPU does not work with x64, so I have to use the x86, works just fine.

Guest · Post by **Guest** » 3. May 2008, 17:26

exactly the same problem here

cpu: amd X2 4200
ubuntu 8.04 64 bit version
virtualbox 1.6 64 bit version

PS: I also removed everything about KVM to make sure that they don't collide while using AMD-V but that didn't work

Guest · Post by **Guest** » 3. May 2008, 17:27

Sasquatch wrote:Intel T2300, VT-x support, no problems booting it. If you guys run the 64 bit version, perhaps running the x86 will let it work? My CPU does not work with x64, so I have to use the x86, works just fine.

it may be an AMD specific bug I don't think architecture is relevant

Post by **Sasquatch** » 3. May 2008, 18:07

It's possible, but the first two posts were about the 64 bit edition. Still possible to be AMD specific. Only one way to know for sure.

billstei · Post by **billstei** » 3. May 2008, 18:18

I am running 32 bit x86 Ubuntu Gutsy and AMD X2 cpu and it fails.

Post by **Sasquatch** » 3. May 2008, 19:14

Very well, then I suggest you create a ticket for a bugreport. This is not intended. A fix could be released soon.

monstbox · Post by **monstbox** » 3. May 2008, 19:39

ticket 1458 seems to cover what we are talking about here.
I am curious. All the ones with this issue (including me) are on Ubuntu Hardy also saw a Gutsy. There was a new Hardy kernel update today which did not help or make things worse for virtualbox.
Are there any non Ubuntu users that are having this issue? And then I guess the next question should be are there any non Ubuntu users where selecting the VT does work?

monstbox · Post by **monstbox** » 3. May 2008, 19:42

ticket 1454 also covers this same issue

billstei · Post by **billstei** » 3. May 2008, 20:21

There was a question regarding whether anyone is running the kvm kernel module. I show no kvm from doing ls /dev or from dmesg | grep kvm Does that cover it or is there something else I need to check?

Bill

Isaac702 · Post by **Isaac702** » 3. May 2008, 21:56

Ok I'm using Opensuse 10.3 64bit and I'm having this problem so it isn't just limited to Ubuntu users.

Processor: AMD Turion 64 X2 2GHz
OS: Opensuse 10.3 64bit
Version: 1.6 64bit

Has anyone tried using a Vanilla Kernel to see if its a problem with a option on Opensuse's and Ubuntu's custom kernel?

billstei · Post by **billstei** » 3. May 2008, 22:28

I'm using a realtime kernel (in Ubuntu the 2.6.22-14-rt version). Correlation anyone?

Bill

melix · Post by **melix** » 6. May 2008, 16:08

Same here with Ubuntu Hardy Heron.

AMD Athlon(tm) 64 X2 Dual Core Processor 5000+
Kernel 2.6.24-16-generic
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt rdtscp lm 3dnowext 3dnow pni cx16 lahf_lm cmp_legacy svm extapic cr8_legacy ts fid vid ttp tm stc