Hardware Virtualization

[sawo]

Probably the problem is caused by the drivers.The driver refuse to start, because some other device or driver uses this virtual address.Check in device manager for any drivers that have Exclamation mark on them.

[notausgang]

hi sawo,

thx for ur reply. I checked ur hint, and no, everything is working fine. Ur hint brought me to the idea that maybe Eset SmartSecurity is the problem as it installs a virtual networkadapter and the firewalldriver in a lower socketlayer. Deinstalled it, reinstalled Hyper-V (once with and once without networkadapter), same problem. The problem really seems to be the chipset. I contact the vendor if he cud help.
As i allready wrote above it isn’t possible to activate DEP and Virtualization feature of the processor at the same time (only on server2008 🙁 )
So if i turn DEP on, system can’t find the hypervisor. If i turn virtualization on, Hyper-V complains that DEP isn’t activated and refuse to start.

EDIT: Started a last try, deinstalled Hyper-V, ticked the option “Max CPU Value ID” in Bios, rebooted PC. Same thing, DEP on No Virtualization feature. Unticked the option, rebootet… and unbelivable, DEP and Virtualization r both running! Wohoo, installed Hyper-V again, rebootet and.. gosh, Virtualization feature off again!

[sawo]

Well, VIA aren’t the best when it comes to chipsets so maybe their drivers have something to do with it.. I still think its some kind of driver issue, or in the worst case scenario the motherboard itself..

[notausgang]

yeah u might be right. After using and testing 64bit version for a few days many other issues occured. so it really seems to be the bad driverprogramming and support by via.
Doesn’t got an response for my supportrequest yet. will keep u informed.

[Author]

Posts