31 января 2008 г. 13:21
I have problem with Remote Installation Service in Hyper-V. The VM don´t boot on lan.
The DHCP give right IP address to virtual machine.
I used Lagacy Network Adapter to boot.
In native machine pxe work correctly.
"PXE-T01: File not found"
"PXE-E3B: TFTP Error - File Not found"
31 января 2008 г. 17:41
What PXE server are you using (WDS/RIS/etc...) also what is your network typology like and how long of a PXE delay are you using?
4 февраля 2008 г. 8:02
PXE run on windows server 2003 Service Pak 2. Used Windows Deployment Services but the type of images is RiSetup.
PXE delay is 0.
4 февраля 2008 г. 17:25
I will add this to my list of things to try and repro.
5 февраля 2008 г. 11:05
Most likely you have a default Network Adapter configured in the VM. This is a synthetic adapter which is used once the driver is loaded in the Guest OS through the integration components.
To get PXE support, you must install a Legacy Network Adapter.
5 февраля 2008 г. 11:43
The original post states that he was using a 'Legacy Network Adaptor'
5 февраля 2008 г. 11:55
My bad. Disregard my comments.
I used PXE in a Hyper-V VM with RIS before. Don't know for now if it works with physical machine.
11 февраля 2008 г. 8:12
Have you got some news about PXE installation in Hyper-V?
29 февраля 2008 г. 11:16
It seems, that a PXE boot from Hyper-V wants to select the 64bit boot structure (and I don's see a point on the Hyper-V installation itself to adjust this).
Proof: If you copy the PXEBOOT.com into the x64 folder on your WDS servers Boot folder you get a step further and run into an TFTP Download Failed error.
A solution to this issue would be to select x86 as default image for x64 machines on your WDS server with the command
wdsutil /set-server /defaultx86x64imagetype:x86
But this doesn't work here, so I tried to alter the path to the Boot x64 architecture in the properties of the WDS server in the WDS console. This seems to function - at least I got the Hyper-V system to boot the boot.wim.
Well, now it tells me weird stuff about not being able to contact DHCP server although in the DHCP leases the machine seems to have gotten an address.
Best greetings from Germany
29 февраля 2008 г. 15:32Модератор
I am curious..
Does the NIC on your host support TCP Offloading?
We have seen a bunch of strange behavior on our network when TCP Offliading is enabled on NIC and any type of PXE boot is involved.
We are still trying to quantify what this means in a virtualized environment, but in the physical world it has a tendancy to affect PXE and make it behave in flakey manners.
4 мая 2008 г. 22:39
Hi, my name is Sergio from Argentina, and I´m having a similar problem but in the inverted way.
I have a Datacenter in my job. In the subnet 10.5.100 is running a DHCP server that lease IPs to clients on this scope, and others scopes in the network.
In the same subnet I have a RIS server that works fine in the other subnets (typing the DHCP options BOOTSERVER and BOOTFILE in every scope) but in the 10.5.100 doesn´t work or have a big delay.
I am trying ADS because I want to deploy servers, but I have problems.
I installed ADS 1.1 in a Windows Server 2003 Ent. SP1. I boot a server to get DA, in the same subnet (putting the server MAC Address in the ADS Console devices) and the PXE boot don´t work.
The RIS service neither work, I don´t know why. Is the same subnet, there is not firewall in the datacenter.
The server that boot in PXE has a extrange behavior. Sometimes boots and sometimes not. If I wait too much time some times boot DA or RIS (very strange behavior).
Now... prepare. I prepared a VM Machine with VM WARE. This machine is installed in the server that can´t boot PXE (this server has a W2003 installation). The VM Machine boots PXE (RIS or ADS) without problems, very quickly.
The phisyc NIC in the server is a BroadCom. The additional drivers was installed y PreSystem (yeah, I know the problem with the Netxtreme NICs, I have the special RIS driver).
When DA boots correctly in the real server, DA boots fine and I can control the server without problems. The problem is similar to this post, but viceversa. It´s about timeout, because when DA boots, DA works fine.
Conclution: The VM boots PXE fine, the real server wasn´t (or have a big delay to make it).
Note: I use a Intel NIC with the same problem.
If someone wants to help me, respond this post or mail me to firstname.lastname@example.org
Thank you very much!