Go Premium for a chance to win a PS4. Enter to Win

x
?
Solved

Connection issues during VMimage PXE boot to another VM.

Posted on 2010-09-08
6
Medium Priority
?
1,164 Views
Last Modified: 2012-05-10
Hi I have been trying for a minute to PXE boot a vmware windows xp image to another vmware 2003 server running provisioning server.

If you are familiar with Citrix provisioning you will know that I need to load the vdisk during pxe boot to make it active.  I have configured boot options 66 and 67 and I can see the xp vm acquiring a IP address as well as connecting to the vdisk but something happens during the connection that causes it not to complete correctly.  I get no errors during the boot and there are no errors collected on the provisioning server.  Both vm images are using the E1000 drivers.
0
Comment
Question by:adrianjfx
  • 3
  • 2
6 Comments
 
LVL 28

Expert Comment

by:bgoering
ID: 33632729
if the vdisk is pre-configured with VMware Tools it probably won't work. You need to have the native E1000 driver for PXE boot to be successful in a VM. Tools install replaces that driver.

See http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1009104

Good Luck
0
 
LVL 17

Expert Comment

by:vivigatt
ID: 33635517
I am not an expert with PVS, but with HP Image Manager (which is more or less the same), there arze no issues using VMWare tools in the "client" configuration.

I guess it depends what kind of virtual NIC there is in your client VM.

Using "flexible" is certainly the best choice, but you may have to use it from the beginning (switching to flexible after the VM has been created and its OS has been installed might give unpredictable results).

Also, in some cases (that I am currently investigating), the PXE part of the boot process takes forever (more than 3 minutes), but when Windows (and Windows NIC drivers) take control of the VM, then everything runs at the speed of light!

If you can describe your problem more precisely, I may help a little more.
For instance, what happens when "the boot process does not complete correctly"? What does the VM display then?

And also, what VMWare product are you using? ESX4? Something else?


0
 

Author Comment

by:adrianjfx
ID: 33637165
Hi Vivgatt, I figured that the VMware tools didnt have much impact, but I still tried removing them with no success.  I agree that the problem has to be the network card.  I am currently using the E1000 driver per VMWare KB 1009104.

I will try to switch the adapter to flexible and see what results I get.  For clarity, when the boot process does not complet correctly the system just continues to boot normally, but on the PVS server a green checkmark does not appear next to the device which indicates that the vdisk was mounted.  (The VM displays no error).

I'm sure its something to do with the vm to vm communication as I am able to successfully boot using physical machines.
0
Industry Leaders: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

 
LVL 17

Expert Comment

by:vivigatt
ID: 33641383
Do you mean that your VM can actually boot off Provisioning Server ?
If so, there is no issue with the PXE portion of the boot process.

Or is the vDisk a non system disk (not a boot disk), and then, does it appear in the disks available to your VM?

If the VM has a boot vDisk AND a "VM HDD" (a .vmdk file", what can happen is that you begin to boot off the vDisk (the PXE portion), and when Windows switches to protected mode and uses its drivers, it then continues to boot off the vmdk disk. The VM then never registers that it mounted a vDisk (since I think this is done by a Windows component). This is easy to check: Configure your VM so that it does not have any .vmdk disk and see if it then can boot completely off PVS. And if so, check if then it registers OK...
0
 

Accepted Solution

by:
adrianjfx earned 0 total points
ID: 33827452
Hi guys, i figured this one out.  All you have to do is ensure the network card is the first on the list in the bios boot order.  Thanks for your help!
0
 

Author Comment

by:adrianjfx
ID: 33827453
.
0

Featured Post

Free Tool: Port Scanner

Check which ports are open to the outside world. Helps make sure that your firewall rules are working as intended.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

This article is a collection of issues that people face from time to time and possible solutions to those issues. I hope you enjoy reading it.
This article will show you step-by-step instructions to build your own NTP CentOS server.  The network diagram shows the best practice to setup the NTP server farm for redundancy.  This article also serves as your NTP server documentation.
If you're a developer or IT admin, you’re probably tasked with managing multiple websites, servers, applications, and levels of security on a daily basis. While this can be extremely time consuming, it can also be frustrating when systems aren't wor…
Monitoring a network: why having a policy is the best policy? Michael Kulchisky, MCSE, MCSA, MCP, VTSP, VSP, CCSP outlines the enormous benefits of having a policy-based approach when monitoring medium and large networks. Software utilized in this v…

876 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question