> Hello,
>
> I just got a new PC with the following specs:
> - Intel Core i7 920 processor (4 physical cores @ 2.79GHz, with
> hyperthreading)
> - Gigabyte EX58-DS4 motherboard, which has an Intel X58 Express chipset
>
> As best I can tell, all of these components support hardware-assisted
> virtualization and should be sufficient for Hyper-V.
>
> I've installed Windows Server 2008 x64 edition and have installed the
> Hyper-V role. I've also been into the BIOS and have ensured that the
> following are set to ENABLED:
> - Virtualization Technology
> - No-Execute Memory Protect
> (I should note that hyperthreading is also turned on.)
>
> In my understanding, this should be sufficient to get Hyper-V running.
>
> However, whenever I go into the Hyper-V manager, I see two errors in the
> log:
> - Error 32: Hyper-V launch failed; at least one of the processors in the
> system does not appear to provide a virtualization platform supported by
> Hyper-V.
> - Error 42: Hyper-V launch failed; Either VMX not present or not enabled
> in
> BIOS
>
>
> I've been tearing my hair out trying to work out whether:
> - My hardware just doesn't support it (which seems unlikely from
> everything
> I've read)
> - My BIOS or drivers need updating (I've got them all at the latest
> versions)
> - I'm missing a setting in the BIOS setup screen (but I have no idea what)
>
> I saw a couple of posts from various people saying that the locale has to
> be
> set to English (United States) for Hyper-V to work. When I originally
> installed the OS, I had English (New Zealand). I've since changed my
> locale
> (and made the same change to the system locale, AND applied that to all
> the
> reserved accounts). I then uninstalled and reinstalled Hyper-V (twice, for
> good measure). The problem remains.
>
> If anyone would be able to help me out with this I'd really appreciate it.
> I
> had specifically bought this machine to run Hyper-V, and I don't want to
> use
> it for anything else in the meantime in case I need to reinstall the OS.
>
> Thanks in advance!
>
> John

> Well, you've got newer hardware than I do. But I'd strongly suspect that you
> should be turning OFF hyper-threading. I'd certainly give that a try, at
> least.
>
> --
> Charlie.
> http://msmvps.com/blogs/xperts64
> http://mvp.support.microsoft.com/profile/charlie.russel
>
> "JohnD" <(email address - cut out)> wrote in message
> news:(email address - cut out)...
> > Hello,
> >
> > I just got a new PC with the following specs:
> > - Intel Core i7 920 processor (4 physical cores @ 2.79GHz, with
> > hyperthreading)
> > - Gigabyte EX58-DS4 motherboard, which has an Intel X58 Express chipset
> >
> > As best I can tell, all of these components support hardware-assisted
> > virtualization and should be sufficient for Hyper-V.
> >
> > I've installed Windows Server 2008 x64 edition and have installed the
> > Hyper-V role. I've also been into the BIOS and have ensured that the
> > following are set to ENABLED:
> > - Virtualization Technology
> > - No-Execute Memory Protect
> > (I should note that hyperthreading is also turned on.)
> >
> > In my understanding, this should be sufficient to get Hyper-V running.
> >
> > However, whenever I go into the Hyper-V manager, I see two errors in the
> > log:
> > - Error 32: Hyper-V launch failed; at least one of the processors in the
> > system does not appear to provide a virtualization platform supported by
> > Hyper-V.
> > - Error 42: Hyper-V launch failed; Either VMX not present or not enabled
> > in
> > BIOS
> >
> >
> > I've been tearing my hair out trying to work out whether:
> > - My hardware just doesn't support it (which seems unlikely from
> > everything
> > I've read)
> > - My BIOS or drivers need updating (I've got them all at the latest
> > versions)
> > - I'm missing a setting in the BIOS setup screen (but I have no idea what)
> >
> > I saw a couple of posts from various people saying that the locale has to
> > be
> > set to English (United States) for Hyper-V to work. When I originally
> > installed the OS, I had English (New Zealand). I've since changed my
> > locale
> > (and made the same change to the system locale, AND applied that to all
> > the
> > reserved accounts). I then uninstalled and reinstalled Hyper-V (twice, for
> > good measure). The problem remains.
> >
> > If anyone would be able to help me out with this I'd really appreciate it.
> > I
> > had specifically bought this machine to run Hyper-V, and I don't want to
> > use
> > it for anything else in the meantime in case I need to reinstall the OS.
> >
> > Thanks in advance!
> >
> > John
>
>

> Hi Charlie
>
> Thanks for your reply. Actually that's one thing I neglected to mention -
> I
> did try turning off hyper-threading, and it made no difference.
>
> Thanks
>
> John
>
> "Charlie Russel - MVP" wrote:
>
>> Well, you've got newer hardware than I do. But I'd strongly suspect that
>> you
>> should be turning OFF hyper-threading. I'd certainly give that a try, at
>> least.
>>
>> --
>> Charlie.
>> http://msmvps.com/blogs/xperts64
>> http://mvp.support.microsoft.com/profile/charlie.russel
>>
>> "JohnD" <(email address - cut out)> wrote in message
>> news:(email address - cut out)...
>> > Hello,
>> >
>> > I just got a new PC with the following specs:
>> > - Intel Core i7 920 processor (4 physical cores @ 2.79GHz, with
>> > hyperthreading)
>> > - Gigabyte EX58-DS4 motherboard, which has an Intel X58 Express chipset
>> >
>> > As best I can tell, all of these components support hardware-assisted
>> > virtualization and should be sufficient for Hyper-V.
>> >
>> > I've installed Windows Server 2008 x64 edition and have installed the
>> > Hyper-V role. I've also been into the BIOS and have ensured that the
>> > following are set to ENABLED:
>> > - Virtualization Technology
>> > - No-Execute Memory Protect
>> > (I should note that hyperthreading is also turned on.)
>> >
>> > In my understanding, this should be sufficient to get Hyper-V running.
>> >
>> > However, whenever I go into the Hyper-V manager, I see two errors in
>> > the
>> > log:
>> > - Error 32: Hyper-V launch failed; at least one of the processors in
>> > the
>> > system does not appear to provide a virtualization platform supported
>> > by
>> > Hyper-V.
>> > - Error 42: Hyper-V launch failed; Either VMX not present or not
>> > enabled
>> > in
>> > BIOS
>> >
>> >
>> > I've been tearing my hair out trying to work out whether:
>> > - My hardware just doesn't support it (which seems unlikely from
>> > everything
>> > I've read)
>> > - My BIOS or drivers need updating (I've got them all at the latest
>> > versions)
>> > - I'm missing a setting in the BIOS setup screen (but I have no idea
>> > what)
>> >
>> > I saw a couple of posts from various people saying that the locale has
>> > to
>> > be
>> > set to English (United States) for Hyper-V to work. When I originally
>> > installed the OS, I had English (New Zealand). I've since changed my
>> > locale
>> > (and made the same change to the system locale, AND applied that to all
>> > the
>> > reserved accounts). I then uninstalled and reinstalled Hyper-V (twice,
>> > for
>> > good measure). The problem remains.
>> >
>> > If anyone would be able to help me out with this I'd really appreciate
>> > it.
>> > I
>> > had specifically bought this machine to run Hyper-V, and I don't want
>> > to
>> > use
>> > it for anything else in the meantime in case I need to reinstall the
>> > OS.
>> >
>> > Thanks in advance!
>> >
>> > John
>>
>>

> Then I'd check with the mobo mfg and see if there's a BIOS update. I can't
> see a reason why it shouldn't enable. (You _have_ done a full power off
> reboot since making the BIOS changes, correct?)
>
> --
> Charlie.
> http://msmvps.com/blogs/xperts64
> http://mvp.support.microsoft.com/profile/charlie.russel
>
> "JohnD" <(email address - cut out)> wrote in message
> news:(email address - cut out)...
> > Hi Charlie
> >
> > Thanks for your reply. Actually that's one thing I neglected to mention -
> > I
> > did try turning off hyper-threading, and it made no difference.
> >
> > Thanks
> >
> > John
> >
> > "Charlie Russel - MVP" wrote:
> >
> >> Well, you've got newer hardware than I do. But I'd strongly suspect that
> >> you
> >> should be turning OFF hyper-threading. I'd certainly give that a try, at
> >> least.
> >>
> >> --
> >> Charlie.
> >> http://msmvps.com/blogs/xperts64
> >> http://mvp.support.microsoft.com/profile/charlie.russel
> >>
> >> "JohnD" <(email address - cut out)> wrote in message
> >> news:(email address - cut out)...
> >> > Hello,
> >> >
> >> > I just got a new PC with the following specs:
> >> > - Intel Core i7 920 processor (4 physical cores @ 2.79GHz, with
> >> > hyperthreading)
> >> > - Gigabyte EX58-DS4 motherboard, which has an Intel X58 Express chipset
> >> >
> >> > As best I can tell, all of these components support hardware-assisted
> >> > virtualization and should be sufficient for Hyper-V.
> >> >
> >> > I've installed Windows Server 2008 x64 edition and have installed the
> >> > Hyper-V role. I've also been into the BIOS and have ensured that the
> >> > following are set to ENABLED:
> >> > - Virtualization Technology
> >> > - No-Execute Memory Protect
> >> > (I should note that hyperthreading is also turned on.)
> >> >
> >> > In my understanding, this should be sufficient to get Hyper-V running.
> >> >
> >> > However, whenever I go into the Hyper-V manager, I see two errors in
> >> > the
> >> > log:
> >> > - Error 32: Hyper-V launch failed; at least one of the processors in
> >> > the
> >> > system does not appear to provide a virtualization platform supported
> >> > by
> >> > Hyper-V.
> >> > - Error 42: Hyper-V launch failed; Either VMX not present or not
> >> > enabled
> >> > in
> >> > BIOS
> >> >
> >> >
> >> > I've been tearing my hair out trying to work out whether:
> >> > - My hardware just doesn't support it (which seems unlikely from
> >> > everything
> >> > I've read)
> >> > - My BIOS or drivers need updating (I've got them all at the latest
> >> > versions)
> >> > - I'm missing a setting in the BIOS setup screen (but I have no idea
> >> > what)
> >> >
> >> > I saw a couple of posts from various people saying that the locale has
> >> > to
> >> > be
> >> > set to English (United States) for Hyper-V to work. When I originally
> >> > installed the OS, I had English (New Zealand). I've since changed my
> >> > locale
> >> > (and made the same change to the system locale, AND applied that to all
> >> > the
> >> > reserved accounts). I then uninstalled and reinstalled Hyper-V (twice,
> >> > for
> >> > good measure). The problem remains.
> >> >
> >> > If anyone would be able to help me out with this I'd really appreciate
> >> > it.
> >> > I
> >> > had specifically bought this machine to run Hyper-V, and I don't want
> >> > to
> >> > use
> >> > it for anything else in the meantime in case I need to reinstall the
> >> > OS.
> >> >
> >> > Thanks in advance!
> >> >
> >> > John
> >>
> >>
>
>

> Hi Charlie
>
> I've checked and it has the latest BIOS (actually the only one, since it's
> a
> fairly new motherboard). And yes, I did completely power off after
> changing
> the BIOS settings - and just to be sure, I pulled the power cord out for
> about 10 seconds.
>
> I've got a question in with the manufacturer, Gigabyte, so I'm hoping
> they'll be able to help - just wanted to make sure I hadn't missed
> anything
> obvious that someone on here would know about :)
>
> Thanks for your advice.
>
> John
>
> "Charlie Russel - MVP" wrote:
>
>> Then I'd check with the mobo mfg and see if there's a BIOS update. I
>> can't
>> see a reason why it shouldn't enable. (You _have_ done a full power off
>> reboot since making the BIOS changes, correct?)
>>
>> --
>> Charlie.
>> http://msmvps.com/blogs/xperts64
>> http://mvp.support.microsoft.com/profile/charlie.russel
>>
>> "JohnD" <(email address - cut out)> wrote in message
>> news:(email address - cut out)...
>> > Hi Charlie
>> >
>> > Thanks for your reply. Actually that's one thing I neglected to
>> > mention -
>> > I
>> > did try turning off hyper-threading, and it made no difference.
>> >
>> > Thanks
>> >
>> > John
>> >
>> > "Charlie Russel - MVP" wrote:
>> >
>> >> Well, you've got newer hardware than I do. But I'd strongly suspect
>> >> that
>> >> you
>> >> should be turning OFF hyper-threading. I'd certainly give that a try,
>> >> at
>> >> least.
>> >>
>> >> --
>> >> Charlie.
>> >> http://msmvps.com/blogs/xperts64
>> >> http://mvp.support.microsoft.com/profile/charlie.russel
>> >>
>> >> "JohnD" <(email address - cut out)> wrote in message
>> >> news:(email address - cut out)...
>> >> > Hello,
>> >> >
>> >> > I just got a new PC with the following specs:
>> >> > - Intel Core i7 920 processor (4 physical cores @ 2.79GHz, with
>> >> > hyperthreading)
>> >> > - Gigabyte EX58-DS4 motherboard, which has an Intel X58 Express
>> >> > chipset
>> >> >
>> >> > As best I can tell, all of these components support
>> >> > hardware-assisted
>> >> > virtualization and should be sufficient for Hyper-V.
>> >> >
>> >> > I've installed Windows Server 2008 x64 edition and have installed
>> >> > the
>> >> > Hyper-V role. I've also been into the BIOS and have ensured that the
>> >> > following are set to ENABLED:
>> >> > - Virtualization Technology
>> >> > - No-Execute Memory Protect
>> >> > (I should note that hyperthreading is also turned on.)
>> >> >
>> >> > In my understanding, this should be sufficient to get Hyper-V
>> >> > running.
>> >> >
>> >> > However, whenever I go into the Hyper-V manager, I see two errors in
>> >> > the
>> >> > log:
>> >> > - Error 32: Hyper-V launch failed; at least one of the processors in
>> >> > the
>> >> > system does not appear to provide a virtualization platform
>> >> > supported
>> >> > by
>> >> > Hyper-V.
>> >> > - Error 42: Hyper-V launch failed; Either VMX not present or not
>> >> > enabled
>> >> > in
>> >> > BIOS
>> >> >
>> >> >
>> >> > I've been tearing my hair out trying to work out whether:
>> >> > - My hardware just doesn't support it (which seems unlikely from
>> >> > everything
>> >> > I've read)
>> >> > - My BIOS or drivers need updating (I've got them all at the latest
>> >> > versions)
>> >> > - I'm missing a setting in the BIOS setup screen (but I have no idea
>> >> > what)
>> >> >
>> >> > I saw a couple of posts from various people saying that the locale
>> >> > has
>> >> > to
>> >> > be
>> >> > set to English (United States) for Hyper-V to work. When I
>> >> > originally
>> >> > installed the OS, I had English (New Zealand). I've since changed my
>> >> > locale
>> >> > (and made the same change to the system locale, AND applied that to
>> >> > all
>> >> > the
>> >> > reserved accounts). I then uninstalled and reinstalled Hyper-V
>> >> > (twice,
>> >> > for
>> >> > good measure). The problem remains.
>> >> >
>> >> > If anyone would be able to help me out with this I'd really
>> >> > appreciate
>> >> > it.
>> >> > I
>> >> > had specifically bought this machine to run Hyper-V, and I don't
>> >> > want
>> >> > to
>> >> > use
>> >> > it for anything else in the meantime in case I need to reinstall the
>> >> > OS.
>> >> >
>> >> > Thanks in advance!
>> >> >
>> >> > John
>> >>
>> >>
>>
>>

> A lot of folks are having some teething issues with the BIOS for these new
> mobos, so I wouldn't be surprised to find that there's an issue.
>
> One other thing did occur to me. There are two versions of each edition of
> Windows Server 2008. One with, and one without, Hyper-V. If you
> inadvertently installed the one without hyper-v, you need to re-install from
> scratch.
>
> --
> Charlie.
> http://msmvps.com/blogs/xperts64
> http://mvp.support.microsoft.com/profile/charlie.russel
>
> "JohnD" <(email address - cut out)> wrote in message
> news:(email address - cut out)...
> > Hi Charlie
> >
> > I've checked and it has the latest BIOS (actually the only one, since it's
> > a
> > fairly new motherboard). And yes, I did completely power off after
> > changing
> > the BIOS settings - and just to be sure, I pulled the power cord out for
> > about 10 seconds.
> >
> > I've got a question in with the manufacturer, Gigabyte, so I'm hoping
> > they'll be able to help - just wanted to make sure I hadn't missed
> > anything
> > obvious that someone on here would know about :)
> >
> > Thanks for your advice.
> >
> > John
> >
> > "Charlie Russel - MVP" wrote:
> >
> >> Then I'd check with the mobo mfg and see if there's a BIOS update. I
> >> can't
> >> see a reason why it shouldn't enable. (You _have_ done a full power off
> >> reboot since making the BIOS changes, correct?)
> >>
> >> --
> >> Charlie.
> >> http://msmvps.com/blogs/xperts64
> >> http://mvp.support.microsoft.com/profile/charlie.russel
> >>
> >> "JohnD" <(email address - cut out)> wrote in message
> >> news:(email address - cut out)...
> >> > Hi Charlie
> >> >
> >> > Thanks for your reply. Actually that's one thing I neglected to
> >> > mention -
> >> > I
> >> > did try turning off hyper-threading, and it made no difference.
> >> >
> >> > Thanks
> >> >
> >> > John
> >> >
> >> > "Charlie Russel - MVP" wrote:
> >> >
> >> >> Well, you've got newer hardware than I do. But I'd strongly suspect
> >> >> that
> >> >> you
> >> >> should be turning OFF hyper-threading. I'd certainly give that a try,
> >> >> at
> >> >> least.
> >> >>
> >> >> --
> >> >> Charlie.
> >> >> http://msmvps.com/blogs/xperts64
> >> >> http://mvp.support.microsoft.com/profile/charlie.russel
> >> >>
> >> >> "JohnD" <(email address - cut out)> wrote in message
> >> >> news:(email address - cut out)...
> >> >> > Hello,
> >> >> >
> >> >> > I just got a new PC with the following specs:
> >> >> > - Intel Core i7 920 processor (4 physical cores @ 2.79GHz, with
> >> >> > hyperthreading)
> >> >> > - Gigabyte EX58-DS4 motherboard, which has an Intel X58 Express
> >> >> > chipset
> >> >> >
> >> >> > As best I can tell, all of these components support
> >> >> > hardware-assisted
> >> >> > virtualization and should be sufficient for Hyper-V.
> >> >> >
> >> >> > I've installed Windows Server 2008 x64 edition and have installed
> >> >> > the
> >> >> > Hyper-V role. I've also been into the BIOS and have ensured that the
> >> >> > following are set to ENABLED:
> >> >> > - Virtualization Technology
> >> >> > - No-Execute Memory Protect
> >> >> > (I should note that hyperthreading is also turned on.)
> >> >> >
> >> >> > In my understanding, this should be sufficient to get Hyper-V
> >> >> > running.
> >> >> >
> >> >> > However, whenever I go into the Hyper-V manager, I see two errors in
> >> >> > the
> >> >> > log:
> >> >> > - Error 32: Hyper-V launch failed; at least one of the processors in
> >> >> > the
> >> >> > system does not appear to provide a virtualization platform
> >> >> > supported
> >> >> > by
> >> >> > Hyper-V.
> >> >> > - Error 42: Hyper-V launch failed; Either VMX not present or not
> >> >> > enabled
> >> >> > in
> >> >> > BIOS
> >> >> >
> >> >> >
> >> >> > I've been tearing my hair out trying to work out whether:
> >> >> > - My hardware just doesn't support it (which seems unlikely from
> >> >> > everything
> >> >> > I've read)
> >> >> > - My BIOS or drivers need updating (I've got them all at the latest
> >> >> > versions)
> >> >> > - I'm missing a setting in the BIOS setup screen (but I have no idea
> >> >> > what)
> >> >> >
> >> >> > I saw a couple of posts from various people saying that the locale
> >> >> > has
> >> >> > to
> >> >> > be
> >> >> > set to English (United States) for Hyper-V to work. When I
> >> >> > originally
> >> >> > installed the OS, I had English (New Zealand). I've since changed my
> >> >> > locale
> >> >> > (and made the same change to the system locale, AND applied that to
> >> >> > all
> >> >> > the
> >> >> > reserved accounts). I then uninstalled and reinstalled Hyper-V
> >> >> > (twice,
> >> >> > for
> >> >> > good measure). The problem remains.
> >> >> >
> >> >> > If anyone would be able to help me out with this I'd really
> >> >> > appreciate
> >> >> > it.
> >> >> > I
> >> >> > had specifically bought this machine to run Hyper-V, and I don't
> >> >> > want
> >> >> > to
> >> >> > use
> >> >> > it for anything else in the meantime in case I need to reinstall the
> >> >> > OS.
> >> >> >
> >> >> > Thanks in advance!
> >> >> >
> >> >> > John
> >> >>
> >> >>
> >>
> >>
>
>

> Hi Charlie - I had wondered about that as well actually. The media I have
> doesn't say whether it has Hyper-V or not. But Hyper-V was listed as an
> available server role after I'd installed the OS, so I assume it's the one
> with Hyper-V?
>
> John
>
> "Charlie Russel - MVP" wrote:
>
>> A lot of folks are having some teething issues with the BIOS for these
>> new
>> mobos, so I wouldn't be surprised to find that there's an issue.
>>
>> One other thing did occur to me. There are two versions of each edition
>> of
>> Windows Server 2008. One with, and one without, Hyper-V. If you
>> inadvertently installed the one without hyper-v, you need to re-install
>> from
>> scratch.
>>
>> --
>> Charlie.
>> http://msmvps.com/blogs/xperts64
>> http://mvp.support.microsoft.com/profile/charlie.russel
>>
>> "JohnD" <(email address - cut out)> wrote in message
>> news:(email address - cut out)...
>> > Hi Charlie
>> >
>> > I've checked and it has the latest BIOS (actually the only one, since
>> > it's
>> > a
>> > fairly new motherboard). And yes, I did completely power off after
>> > changing
>> > the BIOS settings - and just to be sure, I pulled the power cord out
>> > for
>> > about 10 seconds.
>> >
>> > I've got a question in with the manufacturer, Gigabyte, so I'm hoping
>> > they'll be able to help - just wanted to make sure I hadn't missed
>> > anything
>> > obvious that someone on here would know about :)
>> >
>> > Thanks for your advice.
>> >
>> > John
>> >
>> > "Charlie Russel - MVP" wrote:
>> >
>> >> Then I'd check with the mobo mfg and see if there's a BIOS update. I
>> >> can't
>> >> see a reason why it shouldn't enable. (You _have_ done a full power
>> >> off
>> >> reboot since making the BIOS changes, correct?)
>> >>
>> >> --
>> >> Charlie.
>> >> http://msmvps.com/blogs/xperts64
>> >> http://mvp.support.microsoft.com/profile/charlie.russel
>> >>
>> >> "JohnD" <(email address - cut out)> wrote in message
>> >> news:(email address - cut out)...
>> >> > Hi Charlie
>> >> >
>> >> > Thanks for your reply. Actually that's one thing I neglected to
>> >> > mention -
>> >> > I
>> >> > did try turning off hyper-threading, and it made no difference.
>> >> >
>> >> > Thanks
>> >> >
>> >> > John
>> >> >
>> >> > "Charlie Russel - MVP" wrote:
>> >> >
>> >> >> Well, you've got newer hardware than I do. But I'd strongly suspect
>> >> >> that
>> >> >> you
>> >> >> should be turning OFF hyper-threading. I'd certainly give that a
>> >> >> try,
>> >> >> at
>> >> >> least.
>> >> >>
>> >> >> --
>> >> >> Charlie.
>> >> >> http://msmvps.com/blogs/xperts64
>> >> >> http://mvp.support.microsoft.com/profile/charlie.russel
>> >> >>
>> >> >> "JohnD" <(email address - cut out)> wrote in message
>> >> >> news:(email address - cut out)...
>> >> >> > Hello,
>> >> >> >
>> >> >> > I just got a new PC with the following specs:
>> >> >> > - Intel Core i7 920 processor (4 physical cores @ 2.79GHz, with
>> >> >> > hyperthreading)
>> >> >> > - Gigabyte EX58-DS4 motherboard, which has an Intel X58 Express
>> >> >> > chipset
>> >> >> >
>> >> >> > As best I can tell, all of these components support
>> >> >> > hardware-assisted
>> >> >> > virtualization and should be sufficient for Hyper-V.
>> >> >> >
>> >> >> > I've installed Windows Server 2008 x64 edition and have installed
>> >> >> > the
>> >> >> > Hyper-V role. I've also been into the BIOS and have ensured that
>> >> >> > the
>> >> >> > following are set to ENABLED:
>> >> >> > - Virtualization Technology
>> >> >> > - No-Execute Memory Protect
>> >> >> > (I should note that hyperthreading is also turned on.)
>> >> >> >
>> >> >> > In my understanding, this should be sufficient to get Hyper-V
>> >> >> > running.
>> >> >> >
>> >> >> > However, whenever I go into the Hyper-V manager, I see two errors
>> >> >> > in
>> >> >> > the
>> >> >> > log:
>> >> >> > - Error 32: Hyper-V launch failed; at least one of the processors
>> >> >> > in
>> >> >> > the
>> >> >> > system does not appear to provide a virtualization platform
>> >> >> > supported
>> >> >> > by
>> >> >> > Hyper-V.
>> >> >> > - Error 42: Hyper-V launch failed; Either VMX not present or not
>> >> >> > enabled
>> >> >> > in
>> >> >> > BIOS
>> >> >> >
>> >> >> >
>> >> >> > I've been tearing my hair out trying to work out whether:
>> >> >> > - My hardware just doesn't support it (which seems unlikely from
>> >> >> > everything
>> >> >> > I've read)
>> >> >> > - My BIOS or drivers need updating (I've got them all at the
>> >> >> > latest
>> >> >> > versions)
>> >> >> > - I'm missing a setting in the BIOS setup screen (but I have no
>> >> >> > idea
>> >> >> > what)
>> >> >> >
>> >> >> > I saw a couple of posts from various people saying that the
>> >> >> > locale
>> >> >> > has
>> >> >> > to
>> >> >> > be
>> >> >> > set to English (United States) for Hyper-V to work. When I
>> >> >> > originally
>> >> >> > installed the OS, I had English (New Zealand). I've since changed
>> >> >> > my
>> >> >> > locale
>> >> >> > (and made the same change to the system locale, AND applied that
>> >> >> > to
>> >> >> > all
>> >> >> > the
>> >> >> > reserved accounts). I then uninstalled and reinstalled Hyper-V
>> >> >> > (twice,
>> >> >> > for
>> >> >> > good measure). The problem remains.
>> >> >> >
>> >> >> > If anyone would be able to help me out with this I'd really
>> >> >> > appreciate
>> >> >> > it.
>> >> >> > I
>> >> >> > had specifically bought this machine to run Hyper-V, and I don't
>> >> >> > want
>> >> >> > to
>> >> >> > use
>> >> >> > it for anything else in the meantime in case I need to reinstall
>> >> >> > the
>> >> >> > OS.
>> >> >> >
>> >> >> > Thanks in advance!
>> >> >> >
>> >> >> > John
>> >> >>
>> >> >>
>> >>
>> >>
>>
>>

> Hello,
>
> I just got a new PC with the following specs:
> - Intel Core i7 920 processor (4 physical cores @ 2.79GHz, with
> hyperthreading)
> - Gigabyte EX58-DS4 motherboard, which has an Intel X58 Express chipset
>
> As best I can tell, all of these components support hardware-assisted
> virtualization and should be sufficient for Hyper-V.
>
> I've installed Windows Server 2008 x64 edition and have installed the
> Hyper-V role. I've also been into the BIOS and have ensured that the
> following are set to ENABLED:
> - Virtualization Technology
> - No-Execute Memory Protect
> (I should note that hyperthreading is also turned on.)
>
> In my understanding, this should be sufficient to get Hyper-V running.
>
> However, whenever I go into the Hyper-V manager, I see two errors in the log:
> - Error 32: Hyper-V launch failed; at least one of the processors in the
> system does not appear to provide a virtualization platform supported by
> Hyper-V.
> - Error 42: Hyper-V launch failed; Either VMX not present or not enabled in
> BIOS
>
>
> I've been tearing my hair out trying to work out whether:
> - My hardware just doesn't support it (which seems unlikely from everything
> I've read)
> - My BIOS or drivers need updating (I've got them all at the latest versions)
> - I'm missing a setting in the BIOS setup screen (but I have no idea what)
>
> I saw a couple of posts from various people saying that the locale has to be
> set to English (United States) for Hyper-V to work. When I originally
> installed the OS, I had English (New Zealand). I've since changed my locale
> (and made the same change to the system locale, AND applied that to all the
> reserved accounts). I then uninstalled and reinstalled Hyper-V (twice, for
> good measure). The problem remains.
>
> If anyone would be able to help me out with this I'd really appreciate it. I
> had specifically bought this machine to run Hyper-V, and I don't want to use
> it for anything else in the meantime in case I need to reinstall the OS.
>
> Thanks in advance!
>
> John

> Hi all,
>
> Just FYI, I got a reply from Gigabyte, the manufacturer of the
> motherboard,
> who essentially said that I shouldn't be trying to run a server OS on a
> desktop board and to please switch to Vista.
>
> I'm not particularly happy with this response so I've gone back to them,
> but
> if anyone has this model of board (EX58-DS4) and HAS managed to get
> Hyper-V
> running, I'd be really keen to find out whether there were any special
> things
> you had to do to make it work.
>
> And if anyone else has any ideas, I'd also be very keen to hear them!
>
> Thanks,
>
> John
>
> "JohnD" wrote:
>
>> Hello,
>>
>> I just got a new PC with the following specs:
>> - Intel Core i7 920 processor (4 physical cores @ 2.79GHz, with
>> hyperthreading)
>> - Gigabyte EX58-DS4 motherboard, which has an Intel X58 Express chipset
>>
>> As best I can tell, all of these components support hardware-assisted
>> virtualization and should be sufficient for Hyper-V.
>>
>> I've installed Windows Server 2008 x64 edition and have installed the
>> Hyper-V role. I've also been into the BIOS and have ensured that the
>> following are set to ENABLED:
>> - Virtualization Technology
>> - No-Execute Memory Protect
>> (I should note that hyperthreading is also turned on.)
>>
>> In my understanding, this should be sufficient to get Hyper-V running.
>>
>> However, whenever I go into the Hyper-V manager, I see two errors in the
>> log:
>> - Error 32: Hyper-V launch failed; at least one of the processors in the
>> system does not appear to provide a virtualization platform supported by
>> Hyper-V.
>> - Error 42: Hyper-V launch failed; Either VMX not present or not enabled
>> in
>> BIOS
>>
>>
>> I've been tearing my hair out trying to work out whether:
>> - My hardware just doesn't support it (which seems unlikely from
>> everything
>> I've read)
>> - My BIOS or drivers need updating (I've got them all at the latest
>> versions)
>> - I'm missing a setting in the BIOS setup screen (but I have no idea
>> what)
>>
>> I saw a couple of posts from various people saying that the locale has to
>> be
>> set to English (United States) for Hyper-V to work. When I originally
>> installed the OS, I had English (New Zealand). I've since changed my
>> locale
>> (and made the same change to the system locale, AND applied that to all
>> the
>> reserved accounts). I then uninstalled and reinstalled Hyper-V (twice,
>> for
>> good measure). The problem remains.
>>
>> If anyone would be able to help me out with this I'd really appreciate
>> it. I
>> had specifically bought this machine to run Hyper-V, and I don't want to
>> use
>> it for anything else in the meantime in case I need to reinstall the OS.
>>
>> Thanks in advance!
>>
>> John

> Hello,
>
> I just got a new PC with the following specs:
> - Intel Core i7 920 processor (4 physical cores @ 2.79GHz, with
> hyperthreading)
> - Gigabyte EX58-DS4 motherboard, which has an Intel X58 Express chipset
>
> As best I can tell, all of these components support hardware-assisted
> virtualization and should be sufficient for Hyper-V.
>
> I've installed Windows Server 2008 x64 edition and have installed the
> Hyper-V role. I've also been into the BIOS and have ensured that the
> following are set to ENABLED:
> - Virtualization Technology
> - No-Execute Memory Protect
> (I should note that hyperthreading is also turned on.)
>
> In my understanding, this should be sufficient to get Hyper-V running.
>
> However, whenever I go into the Hyper-V manager, I see two errors in the log:
> - Error 32: Hyper-V launch failed; at least one of the processors in the
> system does not appear to provide a virtualization platform supported by
> Hyper-V.
> - Error 42: Hyper-V launch failed; Either VMX not present or not enabled in
> BIOS
>
>
> I've been tearing my hair out trying to work out whether:
> - My hardware just doesn't support it (which seems unlikely from everything
> I've read)
> - My BIOS or drivers need updating (I've got them all at the latest versions)
> - I'm missing a setting in the BIOS setup screen (but I have no idea what)
>
> I saw a couple of posts from various people saying that the locale has to be
> set to English (United States) for Hyper-V to work. When I originally
> installed the OS, I had English (New Zealand). I've since changed my locale
> (and made the same change to the system locale, AND applied that to all the
> reserved accounts). I then uninstalled and reinstalled Hyper-V (twice, for
> good measure). The problem remains.
>
> If anyone would be able to help me out with this I'd really appreciate it. I
> had specifically bought this machine to run Hyper-V, and I don't want to use
> it for anything else in the meantime in case I need to reinstall the OS.
>
> Thanks in advance!
>
> John

> Hello,
>
> I just got a new PC with the following specs:
> - Intel Core i7 920 processor (4 physical cores @ 2.79GHz, with
> hyperthreading)
> - Gigabyte EX58-DS4 motherboard, which has an Intel X58 Express chipset
>
> As best I can tell, all of these components support hardware-assisted
> virtualization and should be sufficient for Hyper-V.
>
> I've installed Windows Server 2008 x64 edition and have installed the
> Hyper-V role. I've also been into the BIOS and have ensured that the
> following are set to ENABLED:
> - Virtualization Technology
> - No-Execute Memory Protect
> (I should note that hyperthreading is also turned on.)
>
> In my understanding, this should be sufficient to get Hyper-V running.
>
> However, whenever I go into the Hyper-V manager, I see two errors in the log:
> - Error 32: Hyper-V launch failed; at least one of the processors in the
> system does not appear to provide a virtualization platform supported by
> Hyper-V.
> - Error 42: Hyper-V launch failed; Either VMX not present or not enabled in
> BIOS
>
>
> I've been tearing my hair out trying to work out whether:
> - My hardware just doesn't support it (which seems unlikely from everything
> I've read)
> - My BIOS or drivers need updating (I've got them all at the latest versions)
> - I'm missing a setting in the BIOS setup screen (but I have no idea what)
>
> I saw a couple of posts from various people saying that the locale has to be
> set to English (United States) for Hyper-V to work. When I originally
> installed the OS, I had English (New Zealand). I've since changed my locale
> (and made the same change to the system locale, AND applied that to all the
> reserved accounts). I then uninstalled and reinstalled Hyper-V (twice, for
> good measure). The problem remains.
>
> If anyone would be able to help me out with this I'd really appreciate it. I
> had specifically bought this machine to run Hyper-V, and I don't want to use
> it for anything else in the meantime in case I need to reinstall the OS.
>
> Thanks in advance!
>
> John

>
>> Hello,
>>
>> I just got a new PC with the following specs:
>> - Intel Core i7 920 processor (4 physical cores @ 2.79GHz, with
>> hyperthreading)
>> - Gigabyte EX58-DS4 motherboard, which has an Intel X58 Express chipset
>>
>> As best I can tell, all of these components support hardware-assisted
>> virtualization and should be sufficient for Hyper-V.
>>
>> I've installed Windows Server 2008 x64 edition and have installed the
>> Hyper-V role. I've also been into the BIOS and have ensured that the
>> following are set to ENABLED:
>> - Virtualization Technology
>> - No-Execute Memory Protect
>> (I should note that hyperthreading is also turned on.)
>>
>> In my understanding, this should be sufficient to get Hyper-V running.
>>
>> However, whenever I go into the Hyper-V manager, I see two errors in the
>> log:
>> - Error 32: Hyper-V launch failed; at least one of the processors in the
>> system does not appear to provide a virtualization platform supported by
>> Hyper-V.
>> - Error 42: Hyper-V launch failed; Either VMX not present or not enabled
>> in
>> BIOS
>>
>>
>> I've been tearing my hair out trying to work out whether:
>> - My hardware just doesn't support it (which seems unlikely from
>> everything
>> I've read)
>> - My BIOS or drivers need updating (I've got them all at the latest
>> versions)
>> - I'm missing a setting in the BIOS setup screen (but I have no idea
>> what)
>>
>> I saw a couple of posts from various people saying that the locale has to
>> be
>> set to English (United States) for Hyper-V to work. When I originally
>> installed the OS, I had English (New Zealand). I've since changed my
>> locale
>> (and made the same change to the system locale, AND applied that to all
>> the
>> reserved accounts). I then uninstalled and reinstalled Hyper-V (twice,
>> for
>> good measure). The problem remains.
>>
>> If anyone would be able to help me out with this I'd really appreciate
>> it. I
>> had specifically bought this machine to run Hyper-V, and I don't want to
>> use
>> it for anything else in the meantime in case I need to reinstall the OS.
>>
>> Thanks in advance!
>>
>> John
>
> The new F4 BIOS from Gigabyte solves the problem. However I had to set
> "C3/C6/C7 State Support" in BIOS to Disabled, otherwise Windows will hang
> during boot when Hyper-V is installed.
>
>
> Posted via http://www.VirtualServerFaq.com - Brought to you by Business
> Information Technology Shop - http://www.bitshop.com