Virtual XP not starting says virtualization not enabled, but.....

By Southern Patriot
in The Fast Ring (Insider Previews)

 Share

Recommended Posts

Grand Master

Southern Patriot

Posted
  • Author
Posted
you need to power off and on your PC after you have enabled the VT in the BIOS. Rebooting is not enough

I have had it enabled since I got the machine and it has been powered off many times. That's not the issue here, unfortunately. Any other ideas?

Neowinian

Ozrics Tentacle

Posted
Posted
I have had it enabled since I got the machine and it has been powered off many times. That's not the issue here, unfortunately. Any other ideas?

Same issue here. Ironically, if I hard boot, verify BIOS and SAVE BIOS changes (there were none!), after booting it WORKS!!!

Until I reboot.... without going through the BIOS.

Grand Master

Southern Patriot

Posted
  • Author
Posted
Same issue here. Ironically, if I hard boot, verify BIOS and SAVE BIOS changes (there were none!), after booting it WORKS!!!

Until I reboot.... without going through the BIOS.

Nope, that didn't work here. I'm starting to think the motherboard in this machine (or at least the BIOS) has some really screwy limitations. When I have 4GB installed, I have random problems with my PCI WiFi card and my PCI USB port card (sometimes they refuse to show up, sometimes I get bluescreens related to the WiFi driver). All indications point to the system not properly mapping the PCI cards outside of the 4GB memory range. This is most likely because this motherboard originally came with a 32-bit processor. The current version of the BIOS that is installed supports 64-bit processors and >4GB of RAM, but I'm thinking it is still buggy. I'm going to look at replacing the motherboard next with one that actually works right in a 64-bit environment.

Apprentice

P00rSpy

Posted
Posted

I wonder why they force people to have hardware virtualisation, they even prevent the virtual pc 7.0 to start stating there's compatibility issue, is it the way MS will subsidize their new os by forcing people to buy new box... (maybe intel give them money)

Anyway I installed virtual box and it work ok for me until I (yes I) decide to upgrade...

I was runing virtual pc in the previous build without issue...

Grand Master

ToneKnee

Posted
Posted
Nope, that didn't work here. I'm starting to think the motherboard in this machine (or at least the BIOS) has some really screwy limitations. When I have 4GB installed, I have random problems with my PCI WiFi card and my PCI USB port card (sometimes they refuse to show up, sometimes I get bluescreens related to the WiFi driver). All indications point to the system not properly mapping the PCI cards outside of the 4GB memory range. This is most likely because this motherboard originally came with a 32-bit processor. The current version of the BIOS that is installed supports 64-bit processors and >4GB of RAM, but I'm thinking it is still buggy. I'm going to look at replacing the motherboard next with one that actually works right in a 64-bit environment.

Sounds like a power issue tbh, if not, then your motherboard is crap.

I wonder why they force people to have hardware virtualisation, they even prevent the virtual pc 7.0 to start stating there's compatibility issue, is it the way MS will subsidize their new os by forcing people to buy new box... (maybe intel give them money)

Anyway I installed virtual box and it work ok for me until I (yes I) decide to upgrade...

I was runing virtual pc in the previous build without issue...

Don't be stupid, hardware virtualisation is for speeding things up. Also, Virtual PC 7 is still in testing, reboot back to Microsoft if you are having problems.

Experienced

Qumahlin

Posted
Posted
I wonder why they force people to have hardware virtualisation, they even prevent the virtual pc 7.0 to start stating there's compatibility issue, is it the way MS will subsidize their new os by forcing people to buy new box... (maybe intel give them money)

Without hardware virtualization there is an enormous speed hit depending on the OS your emulating. Anyone who really needs or wants virtualization will have no problems upgrading their hardware to something more supportive. This isn't something likely to be used by your average user.

Grand Master

Southern Patriot

Posted
  • Author
Posted
Sounds like a power issue tbh, if not, then your motherboard is crap.

Not a power issue, because when I drop the RAM to 2GB it works fine. As for the "crap motherboard", I'm starting to believe that is most likely the case. Shopping for a new one soon.

Don't be stupid, hardware virtualisation is for speeding things up. Also, Virtual PC 7 is still in testing, reboot back to Microsoft if you are having problems.

We all know that hardware virtualization speeds things up, but it is very short-sighted for them to REQUIRE it (to be fair, some other VMs require it now too). I'd be happy to have the functionality even if it meant lower speed without virtualization. Microsoft should be aware that there are people with systems like mine that SHOULD by all rights support it, but for whatever reason can't get it working.

Proficient

jbo

Posted
Posted
Microsoft should be aware that there are people with systems like mine that SHOULD by all rights support it, but for whatever reason can't get it working.

I doubt many businesses buy emachines, and since this feature is not really intended for the home user because, as it is right now, most applications that home users use are already compatible with Vista/Win 7.

This is intended for the businesses who want to renew their old hardware because it's starting to fail but could not before because of the incompatibilities with custom written applications, legacy software that were made for specific machinery or old applications that would require a complete rewrite but still gets the business going.

Grand Master

Southern Patriot

Posted
  • Author
Posted (edited)
Disable the Viertualisation option in the bios and then restart the PC and then renable it and then restart the PC.

Tried that too. Even with the absolute latest version of the BIOS for this motherboard (the Foxconn BIOS, not the crappy eMachines BIOS). It turns out that Securable doesn't actually check that the SYSTEM supports virtualization, only that the model of CPU does. AMD has a utility that actually checks the BIOS, and it reports that it isn't enabled.

Oh well, time for a new motherboard.

I doubt many businesses buy emachines, and since this feature is not really intended for the home user because, as it is right now, most applications that home users use are already compatible with Vista/Win 7.

I have a feeling that this little problem isn't limited to eMachines (yeah, it seems to be a pretty prevelant problem, if this Google search is any indication: http://www.google.com/search?q=amd+hyper-v...amp;startPage=1 ). Either way, they should have made this use virtualization if the system supported it (for best performance) but revert to not using it if the system didn't support it.

post-26908-1241549641_thumb.jpg

Edited by roadwarrior
  • 7 months later...
Rookie

bbalegere

Posted
Posted

VMLite (a virtualization technology based on VirtualBox ) can run XP Mode in Windows even if your processor is not capable of Hardware Virtualization.

You can download VMlite here http://www.vmlite.com/

Source: http://agnipulse.com/2009/12/xp-mode-in-wi...virtualization/

This topic is now closed to further replies.
 Share
Go to topic listing

  • Recently Browsing   0 members

    • No registered users viewing this page.