Yesterday I spend the day setting up a PoC for Citrix Provisioning Services (5.6.1 SP1) with XenDesktop, XenApp 6 and XenApp 5. But we discovered that all of the target VM’s would give a BSOD (0x0000007b meaning: inaccessible boot device) when booting from the vDisk while the master didn’t have any problems.
image source: Lako-Home
After investigating this we cloned the master and removed the hard drive. After creating the device in the Citrix PVS console we where able to boot successfully from this vDisk. So the VM was created manually and somewhere along the road there was a misconfiguration. We took the clone and converted it to a template. After this we installed CTX128726 for PVS so we can use the wizard to create XenApp VM’s with this vDisk from the PVS console
Latest posts by Kees Baggerman (see all)
- Nutanix AHV and Citrix MCS: Adding a persistent disk via Powershell – v2 - November 19, 2019
- Recovering a Protection Domain snapshot to a VM - September 13, 2019
- Checking power settings on VMs using powershell - September 11, 2019
- Updated: VM Reporting Script for Nutanix with Powershell - July 3, 2019
- Updated (again!): VM Reporting Script for Nutanix AHV/vSphere with Powershell - June 17, 2019
Your problem seems to be very similar to our. Can you be more precise about your workaround ? When you write “we remove the disk.. ” which disk is it ? The system disk or the swao / cache disk ? I am not sure to undestand really what you have done
I’ve made a clone from the reference machine, the OS disk for this machine was removed (there still was a small disk attached so the storage controller wouldn’t be deleted). After that we converted the clone VM into a template and used that template to create target vm’s. Hope this clarifies things?
i have the same problem did you find a solution ?
As stated in the blogpost:
So the VM was created manually and somewhere along the road there was a misconfiguration. We took the clone and converted it to a template.