|

Citrix: Citrix PVS and BSOD when booting target VM from vDisk

ByKees Baggerman

1 min read

Kees Baggerman

Kees Baggerman·Senior Technical Director at Nutanix – Former Citrix CTP – NVIDIA Enterprise Platform Advisor – 15+ years in EUC

All posts →

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.

citrix pvs

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

 

The following two tabs change content below.

Kees Baggerman

Kees Baggerman is Senior Technical Director — Performance & Solutions Engineering R&D at Nutanix, where he leads a global team responsible for defining how enterprise applications are delivered on the Nutanix platform. A former Citrix Technology Professional and NVIDIA Enterprise Platform Advisor, he has spent 15+ years driving EUC strategy and technical direction across architecture, product, and customer success. He has been writing here since 2011 — sharing what he learns at the intersection of platform engineering and enterprise IT.
Kees Baggerman

Kees Baggerman

Senior Technical Director at Nutanix - Former Citrix CTP - NVIDIA Enterprise Platform Advisor - 15+ years in EUC

Kees Baggerman is Senior Technical Director — Performance & Solutions Engineering R&D at Nutanix, where he leads a global team responsible for defining how enterprise applications are delivered on the Nutanix platform. A former Citrix Technology Professional and NVIDIA Enterprise Platform Advisor, he has spent 15+ years driving EUC strategy and technical direction across architecture, product, and customer success. He has been writing here since 2011 — sharing what he learns at the intersection of platform engineering and enterprise IT.

Similar Posts

4 Comments

  1. Hi

    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

    Thank you

    Best regards

    Marin

    Reply

    1. Marin,

      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?

      Regards,

      Kees Baggerman

      Reply

    1. 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.

      Reply

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.