bug with 4.3.10 - forces VT-x, was working with VT-d (FIXED)

[FearTec]

Hello


UPDATE: FUIXED
All Fixed: Uninstalled Hyper-V as a Windows feature and the acceleration tab is enabled in Virtualbox and I can boot up VM's.
Thanks for the fix loukingjr

I has installed Virtual box on a new Dell Precision M 4800 with a i7-4700MQ CPU that supports VT-D but not VT-x.

I happily installed DOS 6.22, 3.11, 95, 98, NT4, 2003 64bit, Windows 7, 2008 R2, 2012 etc (all from valid MSDN subscription for testing).

I was happily using Server 2003 64bit until Virtualbox Update 4.3.10. Now The Main settings/system acceleration tab is greyed out.

Virtualbox reports the following when I try and start my previously working 64bit 2003 server VM.

> VT-x is not enabled (VERR_VMX_NO_VMX).
> Result Code:
> E_FAIL (0x80004005)
> Component:
> Console
> Interface:
> IConsole {8ab7c520-2442-4b66-8d74-4ff1e195d2b6}

I have virtualization enabled in the bios and can run windows server 2003 64bit from a HyperV session with n troubles.

Should I roll back to Virtual 4.2.x or wait for 4.3.2 or leave Virtualbox and go with HyperV?

My CPU does not support VT-x (but does not support VT-D).

[mpack]

VT-d is not relevant.

There is no bug in 4.3.10, all that has happened is that it no longer silently falls back to raw mode if VT-x is enabled on systems that don't support it. So, just turn VT-x off in the VM settings. You will also need to set the number of CPU cores to 1, since setting it >1 also requires VT-x.

You were NOT "happily using <anything> 64bit" in previous versions. There has never been a version of VBox that was capable of running 64bit guests (or >1 cores) on hosts which don't have VT-x. All that happened in the past was that your misconfigs were silently ignored.

[jorgensen]

Just to point out that VT-x and VT-d is two different things.
Not sure how VirtualBox support VT-d.

[mpack]

PCI Passthrough is only supported in Linux guests, and only when VT-d is available. VT-d == redirected I/O.

As I said, VT-d is not relevant to the OPs problem.

[FearTec]

>You were NOT "happily using <anything> 64bit" in previous versions.

I still think there is a bug because I has multiple 64bit OS's installed (DOS 6.22, Win3.11, 95, 98, NT4, 2K, Vista 64bit, 2008 R2 64bit, Windows 8 64 bit, Windows Server 2012 R2, Debinan 64bit, Gentoo etc) Some of the virtuals has multiple CPU's allocated.



As soon as I updated to 4.3.10 the main settings/system acceleration tab is greyed out on all VM's and the VM's wont boot anymore, Some were suspected and cannot resume. Virtualization is still enabled in the BIOS.

>So, just turn VT-x off in the VM settings.

I'd like to but the main settings/system acceleration tab is greyed out.

I'll roll back the version and boot as before and post screenshots.

[noteirak]

I'd like to but the main settings/system acceleration tab is greyed out.

You didn't power off the VM : it's either paused or in a saved state. You cannot reconfigure this unless it is Powered off.

[FearTec]

I'd like to but the main settings/system acceleration tab is greyed out.

You didn't power off the VM : it's either paused or in a saved state. You cannot reconfigure this unless it is Powered off.

A few of the OS's were powered off and I still could not access the acceleration tab.

[mpack]

I still think there is a bug because I has multiple 64bit OS's installed (DOS 6.22, Win3.11, 95, 98, NT4, 2K, Vista 64bit, 2008 R2 64bit, Windows 8 64 bit, Windows Server 2012 R2, Debinan 64bit, Gentoo etc) Some of the virtuals has multiple CPU's allocated.

Eh?? Since when was DOS 6.22 a 64bit OS? Or Win3.11 (which is actually 16bit!), Win9x etc?

What is your definition of a 64bit OS?

I notice that The Win98 "System Properties" dialog shows 64MB RAM having been allocated... I do hope that's just a coincidence and doesn't indicate your understanding of the "64bit OS" term. Otherwise I'm not sure what that montage of guest images is supposed to be telling me. None of them demonstate a 64bit or multicore guest. Please don't post any more screenshots unless they serve a useful purpose.

It might be better if you pick one VM, describe the problem with it explicitly, and give proper diagnostic data for it, i.e. a VM log file. See Minimum information needed for assistance.

[FearTec]

>Eh?? Since when was DOS 6.22 a 64bit OS? Or Win3.11 (which is actually 16bit!), Win9x etc?

That was an earlier screenshot (not directly documenting the bug) but posted to indicate that I am not a newbie. I have been using Windows Since DOS 6.22 and have over 3000 posts on overclockers.com.au

https://www.google.com.au/#q=FearTec+si ... ers.com.au

Note Vista and Debian have the 64bit logo in the app titlebar icon. The screen shot wwas taken in an older version of Virtualbox before it failed to load them to display the acceleration tab.


> What is your definition of a 64bit OS?

A 64bit OS is one (Windows 64bit or Linux) that uses x86-64 (AMD64) 64bit binaries (not primarily 32bit or 16bit binaries). A 64bit OS would be one that runs on a 64bit processor (e.g 64bit Pentium D's, Core 2, i3/i5/i4 or Opteron, Athlon64 etc but not IA64 Itanium 64bit).

I have 22 OS's installed in Virtual box from 16bit DOS all the way up to Windows Server 2012 (64bit). I only made that image to post on a forum for my Tech Talk call back radio show.


>It might be better if you pick one VM, describe the problem with it explicitly, and give proper diagnostic data

Will do, I thought the log and original post was enough.

When I get to my work PC with the VMs I will pick one 64bit OS and post an images.

[mpack]

The 64bit icon indicates that you selected a 64bit template, not that you succeeded in installing a 64bit OS.

I don't have many more ways to say this: no version of VirtualBox has ever been able to run 64bit guests without VT-x/AMD-v. Any perception you had to the contrary is mistaken.

[FearTec]

Here is the screenshot showing my install with VM's.

I had all OS's installed without a hitch (16bit, 32bit and 64bit) with no issues. I have 1 CPU set maximum and all VM's were working pre 4.3.10

I updated to 4.3.10 and now the Acceleration tab on all VM's is greyed out. This is why I logged this as a possible bug.

[FearTec]

This machine settings have not change (no bios updates or windows updates). Hyper V works

[loukingjr]

you can't run virtualbox guests with Hyper-V enabled.

[mpack]

Hyper-v wouldn't be working on a CPU which doesn't have VT-x. If Hyper-v works then the info given in the first post was incorrect, which would be unfortunate since it was the premise for the entire discussion so far.

In addition, this is not behaviour which changed in 4.3.x. Two red herrings in one post?

[FearTec]

Ok' its obvious VirtualBox don't care about bug reports.

1. I was using VirtualBox with multiple 64bit VM's just fine,
2. Virtual Box was updated.
3. VM's failed to work
4. Virtualbox UI locked down, cant ascess acceleration tab
5. I installed test VM's in Microsoft Hyper V Manager provided with Windows (%windir%\system32\mmc.exe "%windir%\system32\virtmgmt.msc") to test if VT-t/VT-x was at fault or Virtual Box.
6. Hyper V works fine
7. Virtual Box does not
8. I cared to report this to Virtual Box Forums but it's obviously my fault.