I am reverse imaging a PVS vdisk in Xenserver to u...
# citrix-provisioning
c
I am reverse imaging a PVS vdisk in Xenserver to upgrade the Xentools. I got a merged base and created a MM Vdisk version and booted a MM target device and detached the Write cache disk and added a larger HDD 250GB and brought it online (MBR) then run P2PVS using "Citrix PVS Vdisk to this machine" option which completed successfully. I then shut it down and changed boot order to HDD and it boots up but gets stuck on a black screen and doesnt move off this. I done 3 other PVS Vdisks exact same method and didnt have any issues so not sure what is going on. Any ideas ?
j
Xenserver it is much easier just to import the pvs vhdx into xenserver to boot from it. Sometimes the p2pvs process can cause this issue.
c
yeah i tried the direct VHDX boot method but not licensed for it
i do have the xenserver 8 premium 10k socket licenses for Xenserver 8 installed on license server in prep for upgrade (currently on Citrix hypervisor 8.2 cu1) i may switch to that license to do the direct vhdx boot method
as currently using the Citrix DAAS premium (Citrix Hypervisor for apps &desktops) licenses
j
You should swap before the upgrade anyhow.
c
yeah was planning on switching the license just before the upgrade
I noticed the PVS target device software was 2203 on this Vdisk vs 2402 on other vdisks i reverse imaged. As you can in place upgrade PVS target device software on a MM Vdisk version gonna give that a shot then try running the P2PVS process again
even with the xenserver premium licenses cant import a .vhdx to do direct .vhdx boot
😕 1
still black screen after updating PVS target device software via MM vdisk and re runing P2PVS. Is there any other way to reverse image this Vdisk on Xenserver ? Direct VHDX boot i dont seem to be licensed for even tho using xenserver premium licenses ? and the P2PVS method isnt working. I recall a NFS method from years ago (Create NFS datastore / copy Vdisk to NFS datastore / Create a VM on NFS Datastore / Rename PVS Vdisk to same name as VM disk but that was a long time ago)
l
This is the NFS method, I've used it quite a lot in the past, has been a while since normally always using P2PVS now. Have you tried booting in to safe mode?
c
I managed to get it sorted Citrix Hypervisor 8.2 CU1 doesnt support .vhdx import/boot (Xenserver 8.4 does) it only supports .vhd import/boot so i had to convert my merged base PVS vdisk .vhdx file to a .vhd with starwind V2V then i was able to do the .vhd import/boot to create a new VM and managed to uninstall xentools / PVS target device software / VDA and reinstall them. I then exported the VM to a OVA/OVF and with the subsequent updated .vhd from the OVA package i converted it from .vhd to .vhdx with starwind V2V and then copied it to Vdisk store and imported the Vdisk .vhdx file and was able to boot a maintenance target device to it in private mode :)