2nd PVS VMWare Maschine not booting

[Marc Graeber]

Hi,

 

i create a second VMMware Maschine to boot the new vDisk Image. After booting tftp from PVS Server the 2nd VM i get this error message:

 

Error: Attemping to set IP address on boot NIC

 

The fristVM Boot perfect wihout any errors. So have someone had this error before?

[CarlStalhood]

How did you create the second machine? If you clone the first machine, does it work?

[Marc Graeber]

Hi Carl,

 

i create zu machine manuell. I will try tomorrow clone the frist one and let you know if it works. thx

[Marc Graeber]

with a clone its works fine. is something wrong in the vdisk image maybe?

[CarlStalhood]

Virtual Hardware (e.g., NIC settings) is different. Compare the two .vmx files.

[Carl Fallis]

Citrix Provisioning only supports targets that are created with the CVAD setup Wizard or stream VM wizard 

[Carl Fallis]

The other thing does the new VM have more than one NIC?  If so you may want to remove the other NIC. 

[Ryan Swanepoel1709159576]

We are also facing this issue. Here is what we have discovered so far:

vDisk = Server 2019 + CVAD/TD 2311
 

PVS Server = 2019 + PVS 2311

Running on VMWare ESXi host 8.0, when we create the target devices from a template that has VM compatibility 7.0 everything works without issue. If we then upgrade that VM compatibility to version 8.0 PXE boot breaks. We currently have a ticket open with VMWare to investigate this, some investigation has revealed the ethernet0.pciSlotNumber is being changed from value "192" (Compat 7) to "33" (Once upgraded to Compat 8).

Even if manually changed back the same issue persists with "Attempting to set IP address ..."

Edited May 1 by Ryan Swanepoel1709159576

[Carl]

On 5/1/2024 at 6:31 AM, Ryan Swanepoel1709159576 said:

Running on VMWare ESXi host 8.0, when we create the target devices from a template that has VM compatibility 7.0 everything works without issue. If we then upgrade that VM compatibility to version 8.0 PXE boot breaks. We currently have a ticket open with VMWare to investigate this, some investigation has revealed the ethernet0.pciSlotNumber is being changed from value "192" (Compat 7) to "33" (Once upgraded to Compat 8).

By upgrading the VM you are changing the network, PVS can not survive a network change to the streaming NIC,   The image is created such that the NIC is avalaible at boot time, if that changes the target will not boot since PnP service is not started when the new NIC has to be loaded to stream the OS.  The above is a change to the hardware