ASP Developer Network - Brought to you by Steve Radich and BitShop, Inc. - http://www.bitshop.com

ASPDeveloper

ASPDeveloper.Net / VirtualServerFAQ.COM

Make sure you go to our home page for:

* Virtual Server 2005 FAQ
* ASP.Net 2.0 Information
* ASP.Net 2.0 Streaming Tutorials
* ASP.Net 2.0 HTML based Tutorials

Made possible by Business Internet Technology Shop (BitShop)

Virtual Server 2005

Recent Virtual Server 2005 posts

* Event ID 1058 - non-fatal exception
* Adding host OS to domain when DC is a guest VM
* Ip 169
* HYPER-V R2 AND REAL DVD DEVICEs
* problems with SCVMM and domain trust
* R4 ds/dsi firmware-drivers de R4 Sdhc. R4 ultra, R4 new, R4 III upgrade, R4 v3
* Hyper-V clustering, Quick Migration and virtual domain controllers
* hyper-v - teaming recommded at physical host ?
* SCVMM and perimeter host
* Hyper-V -sharing modem for sbs server - How do you connect a com port to a named pipe
* The security settings for the Virtual Server event log were change
* DVD ISO size limited to 4GB?
* iSCSI and Public/Private network problem when clustering with Hyper-V
* Understanding and Optimizing Virtual Networks in Hyper-V
* Hyper-V and Physical RAID
* backup hyper-v guests using dpm
* point me in the right direction
* VMServer benchmarks
* Backing up Hyper-V cluster with Data Protection Manager 2007
* Hyper-v events

Add Solution

Hyper-V and PXE Requests

Source: microsoft.public.virtualserver
Sent: 03/09/2009
From: Edwin
Message:

I have a domain environment setup. Within the environment I have two
separate servers.
Server 1: DHCP Server
Server 2: Hyper-V Server with WDS

They DHCP Server is successfully able to connect to the Hyper-V server via
the SCVMM Admin Console. Virtual Machines running on the Hyper-V server are
also able to receive an IP Address from the DHCP Server and have access to
the network.

The problem that I am having is that the virtual machines are not able to
PXE boot. They are able to receive an IP Address from the DHCP Server but
that is about it. Eventually an message is returned saying: "Boot failure.
Reboot and Select proper Boot device or Insert Boot Media in selected Boot
device"

The virtual machine IS configured to use an Emulated NIC. This is verified
becuase when the virtual machine tries to start it attempts to get a PXE
response as would normally be the case if this were not a virtual environment.

Also, the DHCP server is configured to respond to both PXE and DHCP
responses. The DHCP server also has the below options set:
* Option 60 - PXEClient
* Option 66 - 192.168.0.5 (I have also used the FQDN)
* Option 67 - boot\x86\wdsnbt.com

Within WDS on the Hyper-V server I have the option checked to "Authorize
this Windows Deployment Services server in DHCP" under the DHCP Authorization
section of the Advanced tab.

I also have a simple WinPE image added to the "Boot Images" of the WDS
server. Why am I not able to PXE boot?

Any assistance is greatly appreciated.

Thank you.

Post Reply | This is Spam! | Mark as Spam

Related Messages

Re: Hyper-V and PXE Requests

Sent: 03/09/2009
From: "Ryan Sokolowski [MVP]" <(email address - cut out)>
Message:

Perhaps I misunderstood your terminology, but you need to have a Legacy
Network Adapter installed in your VM.

--
Ryan Sokolowski
MVP - Clustering
MCT, MCITP x3, MCTS x8, MCSE x2, CCNA, CCDA, BCFP

"Edwin" <(email address - cut out)> wrote in message
news:(email address - cut out)...

Show quoted text

>I have a domain environment setup. Within the environment I have two
> separate servers.
> Server 1: DHCP Server
> Server 2: Hyper-V Server with WDS
>
> They DHCP Server is successfully able to connect to the Hyper-V server via
> the SCVMM Admin Console. Virtual Machines running on the Hyper-V server
> are
> also able to receive an IP Address from the DHCP Server and have access to
> the network.
>
> The problem that I am having is that the virtual machines are not able to
> PXE boot. They are able to receive an IP Address from the DHCP Server but
> that is about it. Eventually an message is returned saying: "Boot
> failure.
> Reboot and Select proper Boot device or Insert Boot Media in selected Boot
> device"
>
> The virtual machine IS configured to use an Emulated NIC. This is
> verified
> becuase when the virtual machine tries to start it attempts to get a PXE
> response as would normally be the case if this were not a virtual
> environment.
>
> Also, the DHCP server is configured to respond to both PXE and DHCP
> responses. The DHCP server also has the below options set:
> * Option 60 - PXEClient
> * Option 66 - 192.168.0.5 (I have also used the FQDN)
> * Option 67 - boot\x86\wdsnbt.com
>
> Within WDS on the Hyper-V server I have the option checked to "Authorize
> this Windows Deployment Services server in DHCP" under the DHCP
> Authorization
> section of the Advanced tab.
>
> I also have a simple WinPE image added to the "Boot Images" of the WDS
> server. Why am I not able to PXE boot?
>
> Any assistance is greatly appreciated.
>
> Thank you.

Re: Hyper-V and PXE Requests

Sent: 03/09/2009
From: "Edwin" <(email address - cut out)>
Message:

Yes. You are correct. There was a difference in terminology.

In other words I am NOT using the Synthetic Network Adapter for the VM. I
am using the Legacy Network Adapter for the VM.

Thank you.

"Ryan Sokolowski [MVP]" <(email address - cut out)> wrote in message
news:(email address - cut out)...

Show quoted text

> Perhaps I misunderstood your terminology, but you need to have a Legacy
> Network Adapter installed in your VM.
>
> --
> Ryan Sokolowski
> MVP - Clustering
> MCT, MCITP x3, MCTS x8, MCSE x2, CCNA, CCDA, BCFP
>
>
> "Edwin" <(email address - cut out)> wrote in message
> news:(email address - cut out)...
>>I have a domain environment setup. Within the environment I have two
>> separate servers.
>> Server 1: DHCP Server
>> Server 2: Hyper-V Server with WDS
>>
>> They DHCP Server is successfully able to connect to the Hyper-V server
>> via
>> the SCVMM Admin Console. Virtual Machines running on the Hyper-V server
>> are
>> also able to receive an IP Address from the DHCP Server and have access
>> to
>> the network.
>>
>> The problem that I am having is that the virtual machines are not able to
>> PXE boot. They are able to receive an IP Address from the DHCP Server
>> but
>> that is about it. Eventually an message is returned saying: "Boot
>> failure.
>> Reboot and Select proper Boot device or Insert Boot Media in selected
>> Boot
>> device"
>>
>> The virtual machine IS configured to use an Emulated NIC. This is
>> verified
>> becuase when the virtual machine tries to start it attempts to get a PXE
>> response as would normally be the case if this were not a virtual
>> environment.
>>
>> Also, the DHCP server is configured to respond to both PXE and DHCP
>> responses. The DHCP server also has the below options set:
>> * Option 60 - PXEClient
>> * Option 66 - 192.168.0.5 (I have also used the FQDN)
>> * Option 67 - boot\x86\wdsnbt.com
>>
>> Within WDS on the Hyper-V server I have the option checked to "Authorize
>> this Windows Deployment Services server in DHCP" under the DHCP
>> Authorization
>> section of the Advanced tab.
>>
>> I also have a simple WinPE image added to the "Boot Images" of the WDS
>> server. Why am I not able to PXE boot?
>>
>> Any assistance is greatly appreciated.
>>
>> Thank you.
>

Re: Hyper-V and PXE Requests

Sent: 03/10/2009
From: "Edwin" <(email address - cut out)>
Message:

Has anyone been able to successfully PXE boot a Virtual Machine with a DHCP
server and a separate Hyper-V server running WDS?

Thank you.

"Edwin" <(email address - cut out)> wrote in message
news:(email address - cut out)...

Show quoted text

> Yes. You are correct. There was a difference in terminology.
>
> In other words I am NOT using the Synthetic Network Adapter for the VM. I
> am using the Legacy Network Adapter for the VM.
>
> Thank you.
>
> "Ryan Sokolowski [MVP]" <(email address - cut out)> wrote in message
> news:(email address - cut out)...
>> Perhaps I misunderstood your terminology, but you need to have a Legacy
>> Network Adapter installed in your VM.
>>
>> --
>> Ryan Sokolowski
>> MVP - Clustering
>> MCT, MCITP x3, MCTS x8, MCSE x2, CCNA, CCDA, BCFP
>>
>>
>> "Edwin" <(email address - cut out)> wrote in message
>> news:(email address - cut out)...
>>>I have a domain environment setup. Within the environment I have two
>>> separate servers.
>>> Server 1: DHCP Server
>>> Server 2: Hyper-V Server with WDS
>>>
>>> They DHCP Server is successfully able to connect to the Hyper-V server
>>> via
>>> the SCVMM Admin Console. Virtual Machines running on the Hyper-V server
>>> are
>>> also able to receive an IP Address from the DHCP Server and have access
>>> to
>>> the network.
>>>
>>> The problem that I am having is that the virtual machines are not able
>>> to
>>> PXE boot. They are able to receive an IP Address from the DHCP Server
>>> but
>>> that is about it. Eventually an message is returned saying: "Boot
>>> failure.
>>> Reboot and Select proper Boot device or Insert Boot Media in selected
>>> Boot
>>> device"
>>>
>>> The virtual machine IS configured to use an Emulated NIC. This is
>>> verified
>>> becuase when the virtual machine tries to start it attempts to get a PXE
>>> response as would normally be the case if this were not a virtual
>>> environment.
>>>
>>> Also, the DHCP server is configured to respond to both PXE and DHCP
>>> responses. The DHCP server also has the below options set:
>>> * Option 60 - PXEClient
>>> * Option 66 - 192.168.0.5 (I have also used the FQDN)
>>> * Option 67 - boot\x86\wdsnbt.com
>>>
>>> Within WDS on the Hyper-V server I have the option checked to "Authorize
>>> this Windows Deployment Services server in DHCP" under the DHCP
>>> Authorization
>>> section of the Advanced tab.
>>>
>>> I also have a simple WinPE image added to the "Boot Images" of the WDS
>>> server. Why am I not able to PXE boot?
>>>
>>> Any assistance is greatly appreciated.
>>>
>>> Thank you.
>>

Re: Hyper-V and PXE Requests

Sent: 03/10/2009
From: "Ryan Sokolowski [MVP]" <(email address - cut out)>
Message:

Yes, I 've set this up and it works. Make sure that on the DHCP Tab in WDS
that both the checkboxes are not selected, since your DHCP server is
elsewhere.

--
Ryan Sokolowski
MVP - Clustering
MCT, MCITP x3, MCTS x8, MCSE x2, CCNA, CCDA, BCFP

"Edwin" <(email address - cut out)> wrote in message
news:(email address - cut out)...

Show quoted text

> Has anyone been able to successfully PXE boot a Virtual Machine with a
> DHCP server and a separate Hyper-V server running WDS?
>
> Thank you.
>
> "Edwin" <(email address - cut out)> wrote in message
> news:(email address - cut out)...
>> Yes. You are correct. There was a difference in terminology.
>>
>> In other words I am NOT using the Synthetic Network Adapter for the VM.
>> I am using the Legacy Network Adapter for the VM.
>>
>> Thank you.
>>
>> "Ryan Sokolowski [MVP]" <(email address - cut out)> wrote in message
>> news:(email address - cut out)...
>>> Perhaps I misunderstood your terminology, but you need to have a Legacy
>>> Network Adapter installed in your VM.
>>>
>>> --
>>> Ryan Sokolowski
>>> MVP - Clustering
>>> MCT, MCITP x3, MCTS x8, MCSE x2, CCNA, CCDA, BCFP
>>>
>>>
>>> "Edwin" <(email address - cut out)> wrote in message
>>> news:(email address - cut out)...
>>>>I have a domain environment setup. Within the environment I have two
>>>> separate servers.
>>>> Server 1: DHCP Server
>>>> Server 2: Hyper-V Server with WDS
>>>>
>>>> They DHCP Server is successfully able to connect to the Hyper-V server
>>>> via
>>>> the SCVMM Admin Console. Virtual Machines running on the Hyper-V
>>>> server are
>>>> also able to receive an IP Address from the DHCP Server and have access
>>>> to
>>>> the network.
>>>>
>>>> The problem that I am having is that the virtual machines are not able
>>>> to
>>>> PXE boot. They are able to receive an IP Address from the DHCP Server
>>>> but
>>>> that is about it. Eventually an message is returned saying: "Boot
>>>> failure.
>>>> Reboot and Select proper Boot device or Insert Boot Media in selected
>>>> Boot
>>>> device"
>>>>
>>>> The virtual machine IS configured to use an Emulated NIC. This is
>>>> verified
>>>> becuase when the virtual machine tries to start it attempts to get a
>>>> PXE
>>>> response as would normally be the case if this were not a virtual
>>>> environment.
>>>>
>>>> Also, the DHCP server is configured to respond to both PXE and DHCP
>>>> responses. The DHCP server also has the below options set:
>>>> * Option 60 - PXEClient
>>>> * Option 66 - 192.168.0.5 (I have also used the FQDN)
>>>> * Option 67 - boot\x86\wdsnbt.com
>>>>
>>>> Within WDS on the Hyper-V server I have the option checked to
>>>> "Authorize
>>>> this Windows Deployment Services server in DHCP" under the DHCP
>>>> Authorization
>>>> section of the Advanced tab.
>>>>
>>>> I also have a simple WinPE image added to the "Boot Images" of the WDS
>>>> server. Why am I not able to PXE boot?
>>>>
>>>> Any assistance is greatly appreciated.
>>>>
>>>> Thank you.
>>>

Post Reply | This is Spam! | Mark as Spam

Other groups

Virtual PC (Mac)(3592)	Virtual PC(12844)	Virtual PC (French)(496)
Virtual Server 2005(6245)

Our Sponsors

Virtual Server 2005 Info Here!
http://www.aspdeveloper.net

Wiki

Blogs

Articles

Image galleries

File galleries

Forums

Maps

Directories

ASP Developer Network (since 1996) - Brought to you by Steve Radich and BitShop, Inc. - http://www.bitshop.com
Copyright © 1997-2005 by BitShop, Inc. All Rights Reserved.
No content may be reproduced in any form without written permission from BitShop, Inc.
We will be honored to assist with reproduction rights on our material if you contact us.
We also can provide print articles for your magazine, private training seminars at your site, and conference presentations.
Thank you for visiting. Please bookmark our site if you found it useful!
If you wish to make a donation it will help further the development of these free resources: