Can't install XP and Win7 on Vbox 3.10

[hiryu]

Hi !

I'm using Vbox from time to time as sandbox and to install crapware like iTunes or MediaGO.
Lately I've been updated from v 3.08 to 3.10 but haven't running anything since I haven't got time.
Today I wanted to Run my basic Win XP SP3 Home PL VM and received critical error.
So I uninstalled Vbox, cleaned (read Deleted all keys corresponding to VirtualBox) registry (including LEGACY keys) and started again - since I haven't deleted Vbox settings (it's cool that uninstaller don't even do that, not mentioning it does not remove drivers neither) and error still occured.
So I deleted all VM and started from stratch - and still the same error !! Win XP installer stars normally and error occurs right in moment when win installer loads fat and ntfs drivers (before is RAM driver).

I'm attaching log which have been created by Vbox - sorry it's in rar but log was 148KB and max allowed size is 128KB o0
Hope it will help.

[Sasquatch]

You have a bugged version that was uploaded by accident. Please grab 3.0.10 from the site again and install that one.

[hiryu]

I think this info should be posted on main site.
btw now I can't even install Vbox - MSI error 1603.
Suppose it will be good to clean registry again ;/

[Sasquatch]

That version was online for only a brief moment and an official announcement of the new version was never made. Only people who were on top of the FTP server were hit. It's their own fault for not waiting until the official release. And it is noted in the release announcement here on the forums, see it in Using VirtualBox forum.

[hiryu]

That version was online for only a brief moment and an official announcement of the new version was never made. Only people who were on top of the FTP server were hit. It's their own fault for not waiting until the official release. And it is noted in the release announcement here on the forums, see it in Using VirtualBox forum.

I'm pretty sure I've downloaded it from virtualbox.org NOT from an FTP since I do that almost always.
Nevermind.
U haven't posted anything about the bug so I needed to handle it on my own.

Regards

[Sasquatch]

Still, you were on top of things, as the official word didn't show on the site, only the link to the new version. Did the new build fixed your issue?

[Roy Sharp]

Hi,
This does not appear to be fixed.
I have re-downloaded, removed and reinstalled VirtualBox 3.0.10.54097
I am running Win7 and it starts, runs the machines and is happy until I start a virtual PC (win7 not the old 2007 version).
If I start the VirtualPC first I get "VirtualBox cannot operate in VMX root mode. Please close all other virtualisation programs. (VERR_VMX_IN_VMX_ROOT_MODE)"
Details: displays ...
Result Code:
E_FAIL (0x80004005)
Component:
Console
Interface:
IConsole {0a51994b-cbc6-4686-94eb-d4e4023280e2}

Help
Roy

[Sasquatch]

You can't run two virtualizers at the same time. Also, the new VPC requires hardware virtualization, and that can be accessed by one process only, and you can't mix hardware and software virtualization.

[Roy Sharp]

Few questions, for me and future readers ...

Can you clarify that this is due to the new version of Windows and/ or new hardware as I am sure that I ran both together on my old XP machine.

Also when you say I can't mix hard and soft virtualisation do you mean that you don't think that VirtualBox should run with hardware virtualisation enabled in the BIOS or that VB & VPC cannot run concurrently because they use s'ware and h'ware virtualisation (respectively)?

Is this insurmountable or will Virtualbox, in the future, be able to co-exist?

Does VMWare have the same problem? (sorry to mention them

Thanks,

[vbox4me2]

you can't mix hardware and software virtualization.

Changelog:
12.9 Version 2.2.0 (2009-04-08)
VMM: allow mixing of VT-x/AMD-V and software virtualization

Note: You can mix software and hardware virtualization when running mul-
tiple VMs. In certain cases a small performance penalty will be unavoidable
when mixing VT-x and software virtualization VMs. We recommend not mix-
ing virtualization modes if maximum performance and low overhead are es-
sential. This does not apply to AMD-V

[Sasquatch]

Few questions, for me and future readers ...

Can you clarify that this is due to the new version of Windows and/ or new hardware as I am sure that I ran both together on my old XP machine.

Lucky I think. Are you sure you ran a VPC VM along side a VB VM? Running either system at the same time is not the best way to do things, because the two systems are constantly accessing Ring 1, and that can cause problems (see wikipedia for the Ring 1 thing).

Also when you say I can't mix hard and soft virtualisation do you mean that you don't think that VirtualBox should run with hardware virtualisation enabled in the BIOS or that VB & VPC cannot run concurrently because they use s'ware and h'ware virtualisation (respectively)?

See below.

Is this insurmountable or will Virtualbox, in the future, be able to co-exist?

Does VMWare have the same problem? (sorry to mention them

Thanks,

As said before, hardware mode is only accessible by one program at a time, because the CPU feature is locked like a file that you're editing.

Changelog:12.9 Version 2.2.0 (2009-04-08)VMM: allow mixing of VT-x/AMD-V and software virtualization

That may be true, but it doesn't mean you can still mix VPC/VMW in hardware mode with VB in software or hardware mode, which I were getting at.