on an Acer veriton windows 10 latest (21H1)
a- virtualbox latest 6.1.22 + Extension_Pack cant install windows xp 64
b- virtualbox latest 5.2.44 + Extension_Pack i can install windows xp 64
and yes its the same host and the same os (just downgraded virtualbox)..... so
windows xp 64 on windows 10 host
-
- Site Moderator
- Posts: 39134
- Joined: 4. Sep 2008, 17:09
- Primary OS: MS Windows 10
- VBox Version: PUEL
- Guest OSses: Mostly XP
Re: windows xp 64 on windows 10 host
This is not news. VirtualBox 6.1 dropped support for raw mode VMs, i.e. VT-x or AMD-v is required, no matter the guest OS.
And incidentally, XP is usually 32bits, and that must be the case here as well, otherwise dropping VirtualBox versions would have made zero difference (64bit VMs have always required VT-x/AMD-v).
Your basic problem will be that Hyper-v is enabled on your host, which grabs VT-x and doesn't share. Read FAQ: I have a 64bit host, but can't install 64bit guests.
And incidentally, XP is usually 32bits, and that must be the case here as well, otherwise dropping VirtualBox versions would have made zero difference (64bit VMs have always required VT-x/AMD-v).
Your basic problem will be that Hyper-v is enabled on your host, which grabs VT-x and doesn't share. Read FAQ: I have a 64bit host, but can't install 64bit guests.
-
- Posts: 4
- Joined: 8. Jun 2021, 19:06
Re: windows xp 64 on windows 10 host
gpedit.msc (set Local Computer Policy > Computer Configuration > Administrative Templates > System > Device Guard > Turn on Virtualization Based Security to Disabled. in my case its "not configured" on Windows features both Hyper-V and Windows Hyper-V Platform are emptympack wrote:This is not news. VirtualBox 6.1 dropped support for raw mode VMs, i.e. VT-x or AMD-v is required, no matter the guest OS.
And incidentally, XP is usually 32bits, and that must be the case here as well, otherwise dropping VirtualBox versions would have made zero difference (64bit VMs have always required VT-x/AMD-v).
Your basic problem will be that Hyper-v is enabled on your host, which grabs VT-x and doesn't share. Read ......
-
- Site Moderator
- Posts: 39134
- Joined: 4. Sep 2008, 17:09
- Primary OS: MS Windows 10
- VBox Version: PUEL
- Guest OSses: Mostly XP
Re: windows xp 64 on windows 10 host
Those dialogs can't be relied on. The FAQ tells you what to do.
But the question is easily settled: provide a VM log file. Make sure the VM is fully shut down, then right click it in the manager UI. Select "Show Log" and save "VBox.log" (no other file) to a zip file. Attach the zip here.
But the question is easily settled: provide a VM log file. Make sure the VM is fully shut down, then right click it in the manager UI. Select "Show Log" and save "VBox.log" (no other file) to a zip file. Attach the zip here.
-
- Posts: 4
- Joined: 8. Jun 2021, 19:06
Re: windows xp 64 on windows 10 host
"VBox.log" for xp 64 ... working on vbox5.2.44 but not in 6.1.22mpack wrote:Those dialogs can't be relied on. The FAQ tells you what to do.
But the question is easily settled: provide a VM log file. Make sure the VM is fully shut down, then right click it in the manager UI. Select "Show Log" and save "VBox.log" (no other file) to a zip file. Attach the zip here.
-
- Site Moderator
- Posts: 20945
- Joined: 30. Dec 2009, 20:14
- Primary OS: MS Windows 10
- VBox Version: PUEL
- Guest OSses: Windows, Linux
Re: windows xp 64 on windows 10 host
Full VT-x is in the VM, so no Hyper-V or BIOS problems.
A couple more things that may help the diagnosis, please:
First, please clarify something in the initial post:
What exactly does happen when XP "can't install"?
Second, the posted log contains some 7 or so restarts or suspends. Was this a series of reboots, perhaps during the install process?
Third, can you please post a log from 6.1.22 with the install attempt and show what the error is?
A couple more things that may help the diagnosis, please:
First, please clarify something in the initial post:
Does "install" literally mean install, as in you can or cannot get the installer to run? Or does it mean, "The OS won't boot up correctly and throws some error."chamseddine wrote:i can/can't install windows xp 64
What exactly does happen when XP "can't install"?
Second, the posted log contains some 7 or so restarts or suspends. Was this a series of reboots, perhaps during the install process?
Third, can you please post a log from 6.1.22 with the install attempt and show what the error is?
-
- Site Moderator
- Posts: 39134
- Joined: 4. Sep 2008, 17:09
- Primary OS: MS Windows 10
- VBox Version: PUEL
- Guest OSses: Mostly XP
Re: windows xp 64 on windows 10 host
If you want us to diagnose a fault, you need to give us the log of the VM that displays the fault, not the VM that works.
-
- Posts: 4
- Joined: 8. Jun 2021, 19:06
Re: windows xp 64 on windows 10 host
solved by :chamseddine wrote:on an Acer veriton windows 10 latest (21H1)
a- virtualbox latest 6.1.22 + Extension_Pack cant install windows xp 64
b- virtualbox latest 5.2.44 + Extension_Pack i can install windows xp 64
and yes its the same host and the same os (just downgraded virtualbox)..... so
1. cmd (Administrator).
Code: Select all
Dism /Online /Cleanup-Image /RestoreHealth
Dism.exe /online /Cleanup-Image /StartComponentCleanup
sfc /scannow
Code: Select all
Disable-WindowsOptionalFeature -Online -FeatureName Microsoft-Hyper-V-All.
-------------------------------------
thanks to all ...
hope this helps some one else
-
- Site Moderator
- Posts: 39134
- Joined: 4. Sep 2008, 17:09
- Primary OS: MS Windows 10
- VBox Version: PUEL
- Guest OSses: Mostly XP
Re: windows xp 64 on windows 10 host
This isn't really getting any clearer.
The disk cleanup stuff is just placebo. That might affect Windows, it won't affect VirtualBox.
You say you ran "sfc /scannow" but you don't say that it found a fault. And again, this is a fix for Windows OS problems - providing anything was fixed.
The log you previously provided proved that Hyper-v was already disabled, as Scott mentioned.
Rebooting is probably the most powerful step in that list.
But, despite all that, if you say that the VM now runs then... great!
The disk cleanup stuff is just placebo. That might affect Windows, it won't affect VirtualBox.
You say you ran "sfc /scannow" but you don't say that it found a fault. And again, this is a fix for Windows OS problems - providing anything was fixed.
The log you previously provided proved that Hyper-v was already disabled, as Scott mentioned.
Rebooting is probably the most powerful step in that list.
But, despite all that, if you say that the VM now runs then... great!