PVS 7.6 & VMWare 5.5

[Orsay sysadmin]

Hello,

 

I have got a trouble with provisionning server and my VMs.

I can't boot my VM devices from the PS Console (the message is "failed") whereas i can my physicals devices and i can boot my VMs devices from the VSphere Console.

I can shutdown the devices without any issues.

 

I had a POC XenDesktop 5.0 and PVS 6.0 and i didn't have any issues...

 

How can i debug that?

Does someone have an idea?

 

Thanks for help

 

PVS: 7.6

ESXi: 5.5

VM Version: 10

VM guest OS: Windows server 2012

[CarlStalhood]

PvS doesn't use true hypervisor power management like Studio does.

 

I don't think VMware supports Wake-on-LAN for VMs and thus you can't send that signal to the VMs. 

[Orsay sysadmin]

Hello Carl,

 

Thank you for your answer.

Like i understand, VMware supports Wake-on-LAN for VM, please have a look to https://pubs.vmware.com/vsphere-55/index.jsp#com.vmware.vsphere.vm_admin.doc/GUID-879FA851-2B24-49E6-B58F-F25D0E923D17.html

[CarlStalhood]

From your link: "Wake on LAN can resume virtual machines that are in an S1 sleep state only. It cannot resume suspended, hibernated, or powered off virtual machines."

 

So PvS can't use Wake on LAN to power on ESXi VMs that are powered off.

 

It would be nice if PvS used the same power management as Studio (XenApp/XenDesktop).

[Orsay sysadmin]

Hello,

 

Thank you Carl for your help.

 

So, a VM can be wake on lan if it's shutdown. 

It can be wake up if it's in "S1 Sleep", that mean in hibernate for Windows, is it? 

[CarlStalhood]

I don't think so. I think it is sleep or standby.

[Stephen Madaras]

Carl, thanks for your great work.

 

Just wondering, we have PVS 7.6 and VMware 5.1 and we can definitely 'boot' from PVS console as the first questioner asks. But we also just upgrade some servers to PVS 7.8 and it is on VMware 6 and it doesn't allow us to boot. Did this functionality change or are we doing something wrong?

[SCOTT BURKHARDT]

I have the same problem. PVS 7.8 and VMWARE 5.5 can 'boot' from PVS console. Upgraded one VCenter to 6 from 5.5 and installed from scratch another VCenter using version 6. No PVS 7.8 CANNOT 'boot' from console using VMWARE 6. HELP!!!

 

Thank you. 

[Carl Fallis]

PVS can only start VMs from a hypervisor it created using the XenDesktop Setup Wizard or the Streamed VM Wizard.  It does this by keeping the hypervisor information for the target.  It calls directly to the host to start up the VM.  It does not use WAL. I would suggest turning on CDF tracing on PVS and reviewing the log it could be a permission issue or if you are using XenDesktop make sure it's power management is not set so it will turn off the VM, which can happen once the VM is registered. 

[Kreston Yates]

I am running Vsphere 6 and created my provisioned (7.9) VM's with the XenDesktop Setup Wizard and am still unable to Boot the devices via the PVS console...

[dpalchu521]

Had the same issue on PVS 7.6 - 7.12. This happens when the device does not have an associated VirtualHostingPoolId. To check using Powershell run get-pvsdeviceinfo -devicename. 

 

The ID comes from the established host connection and can be found via get-pvsvirtualhostingpool.

 

The problem is it cannot be modified via Powershell. Set-pvsdevice does not let you do that. So the only way to assign virtual hosting ID to the machine is via SQL. 

 

I am guessing blank ID is caused is either by recreating the hosting within PVS console or by creating device via GUI which does not prompt for hosting settings.

[Frédéric LOUKA]

Hello,

With latest versions (in my case, PVS 1912 LTSR), it now possible to create a device including the VirtualHostingPoolId setting with this command line:

 

New-PvsDevice -Name mytargetdevicename -CollectionName Win2019 -SiteName Datacenter1 -VirtualHostingPoolId xxxxxx-xxxx-xxx-xxxxx-xxxxxx -DeviceMac 005056XXXXXX.

I've just tried and I managed to boot my target device from the PVS Console. 

 

Hope it'll help,

 

Fred