XenDesktop 5.6 – Citrix Personal vDisk failed to start

I updated last week my lab at home :

  • XenServer 6.0 to XenServer 6.0.2
  • Provisioning Services 6.0 to Provisioning Services 6.1
  • and XenDesktop 5.5 to XenDesktop 5.6

Everything went well for XenDesktop, update was smooth and VDA update was successful and simple as well. I did the setup of Personal vDisk successfully and it worked without doing anything specific. Then I wanted to built a new Windows 7 golden image to take a fresh start and install the less application possible, this is when I began to have an issue with Personal vDisk :

Startup failed

Personal vDisk failed to start because the snapshot inventory has not been updated. Update the inventory then try again.

Status code: 15

Error code: 0x0

Alright, I had a freshWindows 7 VM updated to the last Microsoft patches with Acrobat Reader installed, PVS Target Device, Citrix Profile Management, EdgeSight and XenTools… Every time I was creating a new vDisk using Imaging Wizard, the operation was successful but all the VMs I tried to launch after had this issue… I got the log files to try to understand what was wrong by clicking on the collect logs button : I got a zip file containing PvDSvc.log.txt, PvDWMI.log.txt and SysVol-lvmSupervisor.log, I will just past an excerpt here :

[...]
[ERROR][03-18-2012 17:34:11]WSFileSystem.cpp        [2773] GetNamedSecurityInfo failed for \\?\C:\Windows\MEMORY.DMP,Error2
[INFO ][03-18-2012 17:34:16]ImageUpdateVDeskNativeOP.cpp[3011] File \Windows\inf\setupapi.app.log of size 174.339 KB got relocated to the guest volume
[INFO ][03-18-2012 17:34:18]ImageUpdateVDeskNativeOP.cpp[3011] File \Windows\inf\setupapi.dev.log of size 2.997 MB got relocated to the guest volume
[INFO ][03-18-2012 17:34:21]ImageUpdateVDeskNativeOP.cpp[3011] File \Windows\Microsoft.NET\Framework\v2.0.50727\CONFIG\DefaultWsdlHelpGenerator.aspx of size 68.801 KB got relocated to the guest volume
[INFO ][03-18-2012 17:34:21]ImageUpdateVDeskNativeOP.cpp[3011] File \Windows\Microsoft.NET\Framework\v2.0.50727\CONFIG\machine.config of size 25.435 KB got relocated to the guest volume
[INFO ][03-18-2012 17:34:21]ImageUpdateVDeskNativeOP.cpp[3011] File \Windows\Microsoft.NET\Framework\v2.0.50727\CONFIG\machine.config.comments of size 41.868 KB got relocated to the guest volume
[INFO ][03-18-2012 17:34:21]ImageUpdateVDeskNativeOP.cpp[3011] File \Windows\Microsoft.NET\Framework\v2.0.50727\CONFIG\machine.config.default of size 19.601 KB got relocated to the guest volume
[INFO ][03-18-2012 17:34:21]ImageUpdateVDeskNativeOP.cpp[3011] File \Windows\Microsoft.NET\Framework\v2.0.50727\CONFIG\web.config of size 29.356 KB got relocated to the guest volume
[INFO ][03-18-2012 17:34:21]ImageUpdateVDeskNativeOP.cpp[3011] File \Windows\Microsoft.NET\Framework\v2.0.50727\CONFIG\web.config.comments of size 56.394 KB got relocated to the guest volume
[INFO ][03-18-2012 17:34:21]ImageUpdateVDeskNativeOP.cpp[3011] File \Windows\Microsoft.NET\Framework\v2.0.50727\CONFIG\web.config.default of size 29.327 KB got relocated to the guest volume
[INFO ][03-18-2012 17:34:21]ImageUpdateVDeskNativeOP.cpp[3011] File \Windows\Microsoft.NET\Framework\v2.0.50727\CONFIG\web_hightrust.config of size 8.500 KB got relocated to the guest volume
[INFO ][03-18-2012 17:34:21]ImageUpdateVDeskNativeOP.cpp[3011] File \Windows\Microsoft.NET\Framework\v2.0.50727\CONFIG\web_hightrust.config.default of size 12.249 KB got relocated to the guest volume
[INFO ][03-18-2012 17:34:21]ImageUpdateVDeskNativeOP.cpp[3011] File \Windows\Microsoft.NET\Framework\v2.0.50727\CONFIG\web_lowtrust.config of size 7.1008 KB got relocated to the guest volume
[INFO ][03-18-2012 17:34:21]ImageUpdateVDeskNativeOP.cpp[3011] File \Windows\Microsoft.NET\Framework\v2.0.50727\CONFIG\web_lowtrust.config.default of size 7.1008 KB got relocated to the guest volume
[INFO ][03-18-2012 17:34:21]ImageUpdateVDeskNativeOP.cpp[3011] File \Windows\Microsoft.NET\Framework\v2.0.50727\CONFIG\web_mediumtrust.config of size 8.68 KB got relocated to the guest volume
[INFO ][03-18-2012 17:34:21]ImageUpdateVDeskNativeOP.cpp[3011] File \Windows\Microsoft.NET\Framework\v2.0.50727\CONFIG\web_mediumtrust.config.default of size 11.54 KB got relocated to the guest volume
[INFO ][03-18-2012 17:34:21]ImageUpdateVDeskNativeOP.cpp[3011] File \Windows\Microsoft.NET\Framework\v2.0.50727\CONFIG\web_minimaltrust.config of size 6.978 KB got relocated to the guest volume
[INFO ][03-18-2012 17:34:21]ImageUpdateVDeskNativeOP.cpp[3011] File \Windows\Microsoft.NET\Framework\v2.0.50727\CONFIG\web_minimaltrust.config.default of size 6.978 KB got relocated to the guest volume
[INFO ][03-18-2012 17:34:22]ImageUpdateVDeskNativeOP.cpp[3011] File \Windows\Microsoft.NET\Framework\v4.0.30319\Config\machine.config of size 35.115 KB got relocated to the guest volume
[INFO ][03-18-2012 17:34:22]ImageUpdateVDeskNativeOP.cpp[3011] File \Windows\Microsoft.NET\Framework\v4.0.30319\Config\machine.config.comments of size 87.446 KB got relocated to the guest volume
[INFO ][03-18-2012 17:34:22]ImageUpdateVDeskNativeOP.cpp[3011] File \Windows\Microsoft.NET\Framework\v4.0.30319\Config\machine.config.default of size 35.115 KB got relocated to the guest volume
[INFO ][03-18-2012 17:34:22]ImageUpdateVDeskNativeOP.cpp[3011] File \Windows\Registration\R000000000001.clb of size 21.40 KB got relocated to the guest volume
[INFO ][03-18-2012 17:34:41]WSFileSystem.cpp        [2126] Compression Enabled on V:\Windows\System32\DRVSTORE
[INFO ][03-18-2012 17:34:43]ImageUpdateVDeskNativeOP.cpp[3011] File \Windows\System32\Microsoft\Protect\S-1-5-18\1fc7d60d-e494-4187-907a-dd8400a01342 of size 468 Bytes got relocated to the guest volume
[INFO ][03-18-2012 17:34:43]ImageUpdateVDeskNativeOP.cpp[3011] File \Windows\System32\Microsoft\Protect\S-1-5-18\fb0c4ef9-9ed2-478f-b1b0-b5ec3eb54a38 of size 468 Bytes got relocated to the guest volume
[INFO ][03-18-2012 17:34:43]ImageUpdateVDeskNativeOP.cpp[3011] File \Windows\System32\Microsoft\Protect\S-1-5-18\Preferred of size 24 Bytes got relocated to the guest volume
[INFO ][03-18-2012 17:34:43]ImageUpdateVDeskNativeOP.cpp[3011] File \Windows\System32\Microsoft\Protect\S-1-5-18\User\04ece708-132d-4bf0-a647-e3329269a012 of size 468 Bytes got relocated to the guest volume
[INFO ][03-18-2012 17:34:43]ImageUpdateVDeskNativeOP.cpp[3011] File \Windows\System32\Microsoft\Protect\S-1-5-18\User\a0023eb6-1b09-4216-bfea-a0dace62be44 of size 468 Bytes got relocated to the guest volume
[INFO ][03-18-2012 17:34:43]ImageUpdateVDeskNativeOP.cpp[3011] File \Windows\System32\Microsoft\Protect\S-1-5-18\User\a4989c32-bd96-4df1-b609-db2d3cb6b6d8 of size 468 Bytes got relocated to the guest volume
[INFO ][03-18-2012 17:34:43]ImageUpdateVDeskNativeOP.cpp[3011] File \Windows\System32\Microsoft\Protect\S-1-5-18\User\Preferred of size 24 Bytes got relocated to the guest volume
[INFO ][03-18-2012 17:34:45]ImageUpdateVDeskNativeOP.cpp[3011] File \Windows\System32\wbem\Repository\INDEX.BTR of size 3.936 MB got relocated to the guest volume
[INFO ][03-18-2012 17:34:45]ImageUpdateVDeskNativeOP.cpp[3011] File \Windows\System32\wbem\Repository\MAPPING1.MAP of size 48.740 KB got relocated to the guest volume
[INFO ][03-18-2012 17:34:45]ImageUpdateVDeskNativeOP.cpp[3011] File \Windows\System32\wbem\Repository\MAPPING2.MAP of size 48.736 KB got relocated to the guest volume
[INFO ][03-18-2012 17:34:45]ImageUpdateVDeskNativeOP.cpp[3011] File \Windows\System32\wbem\Repository\MAPPING3.MAP of size 48.736 KB got relocated to the guest volume
[INFO ][03-18-2012 17:34:46]ImageUpdateVDeskNativeOP.cpp[3011] File \Windows\System32\wbem\Repository\OBJECTS.DATA of size 14.96 MB got relocated to the guest volume
[INFO ][03-18-2012 17:35:29]ImageUpdateVDeskNativeOP.cpp[3033] Number of files relocated 35, Total size of all files relocated 21.872 MB
[INFO ][03-18-2012 17:35:29]ImageUpdateVDeskNativeOP.cpp[3055] END CREATE-VDESKNATIVE-FILESYSTEM, STATUS 0
[INFO ][03-18-2012 17:35:29]ImageUpdateOP.cpp       [0081] RingCube::ImageUpdate::IUVDESKNATIVE_OP::BuildVDeskFileSystem took 86 secs
[INFO ][03-18-2012 17:35:30]ImageUpdateOP.cpp       [0081] RingCube::ImageUpdate::IUVDESKNATIVE_OP::CreateVDeskFileSystemAndCatalogStageFinal took 86 secs
[INFO ][03-18-2012 17:35:30]ImageUpdateOP.cpp       [0081] RingCube::ImageUpdate::IUVDESKNATIVE_OP::CreateVDeskFileSystemAndCatalog took 93 secs
[INFO ][03-18-2012 17:35:31]VDeskNativeActivation.cpp[0650] Template VHD C:\ProgramData\Citrix\personal vDisk\UserData.VDESK.TEMPLATE successfully created
[INFO ][03-18-2012 17:35:31]VDeskNativeSvcUtil.cpp  [1812] Service start type IvmVhd ==> 0
[INFO ][03-18-2012 17:35:31]VDeskNativeSvcUtil.cpp  [1812] Service start type Ivm ==> 0
[INFO ][03-18-2012 17:35:31]VDeskNativeSvcUtil.cpp  [1812] Service start type IvmBoot ==> 1
[INFO ][03-18-2012 17:35:31]VDeskNativeSvcUtil.cpp  [1812] Service start type WorkstationAgent ==> 3
[WARN ][03-18-2012 17:37:30]VDeskNativeVDIConfig.cpp[0205] RegQueryValueEx failed size retrieval for Userinit, Error:2
[INFO ][03-18-2012 17:37:30]VDeskNativeSvc.cpp      [1224] Exiting from vDesk Native service!!!
[INFO ][03-18-2012 17:40:23]VDeskNativeSvcUtil.cpp  [1812] Service start type IvmVhd ==> 3
[INFO ][03-18-2012 17:40:24]VDeskNativeSvcUtil.cpp  [1812] Service start type Ivm ==> 3
[INFO ][03-18-2012 17:40:24]VDeskNativeSvcUtil.cpp  [1812] Service start type IvmBoot ==> 3
[INFO ][03-18-2012 17:40:24]VDeskNativeSvcUtil.cpp  [1812] Service start type WorkstationAgent ==> 2
[WARN ][03-18-2012 17:42:46]VDeskNativeVDIConfig.cpp[0205] RegQueryValueEx failed size retrieval for Userinit, Error:2
[INFO ][03-18-2012 17:42:46]VDeskNativeSvc.cpp      [1224] Exiting from vDesk Native service!!!
[INFO ][03-18-2012 17:44:10]VDeskNativeSvcUtil.cpp  [1812] Service start type IvmVhd ==> 3
[INFO ][03-18-2012 17:44:10]VDeskNativeSvcUtil.cpp  [1812] Service start type Ivm ==> 3
[INFO ][03-18-2012 17:44:10]VDeskNativeSvcUtil.cpp  [1812] Service start type IvmBoot ==> 3
[INFO ][03-18-2012 17:44:10]VDeskNativeSvcUtil.cpp  [1812] Service start type WorkstationAgent ==> 2
[INFO ][03-18-2012 20:11:50]VDeskNativeUtil.cpp     [1361] IVM Service start type 3
[WARN ][03-18-2012 20:11:50]VDeskNativeSvc.cpp      [0882] PvD is not enabled
[INFO ][03-18-2012 20:12:00]PvDWmiClient.cpp        [0130] Admin assigned drive letter : P
[INFO ][03-18-2012 17:45:18]VDeskNativeUtil.cpp     [1361] IVM Service start type 3
[INFO ][03-18-2012 17:45:18]VDeskNativeUtil.cpp     [1361] IVM Service start type 3
[WARN ][03-18-2012 17:45:49]WmiClass.cpp            [0047] Unknown interface.
[WARN ][03-18-2012 20:12:12]WmiClass.cpp            [0047] Unknown interface.
[WARN ][03-18-2012 20:12:12]WmiClass.cpp            [0047] Unknown interface.
[WARN ][03-18-2012 20:12:12]WmiClass.cpp            [0047] Unknown interface.
[WARN ][03-18-2012 20:12:12]WmiClass.cpp            [0047] Unknown interface.
[WARN ][03-18-2012 20:12:12]WmiClass.cpp            [0047] Unknown interface.
[WARN ][03-18-2012 20:12:12]WmiClass.cpp            [0047] Unknown interface.
[WARN ][03-18-2012 20:12:12]WmiClass.cpp            [0047] Unknown interface.
[WARN ][03-18-2012 20:12:12]WmiClass.cpp            [0047] Unknown interface.
[WARN ][03-18-2012 20:12:12]WmiClass.cpp            [0047] Unknown interface.
[INFO ][03-18-2012 20:12:13]VDeskNativeUtil.cpp     [1361] IVM Service start type 3
[INFO ][03-18-2012 20:12:13]VDeskNativeUtil.cpp     [1361] IVM Service start type 3
[WARN ][03-18-2012 20:13:22]WmiClass.cpp            [0047] Unknown interface.
20120318 09:35:03.524 00000001 1 07 0 0 00 0004 0008: IvmLog initialization complete
20120318 09:35:03.524 00000002 1 07 0 0 00 0004 0008: Ivm REL built at Fri Nov  4 00:36:44 2011. (Note that is different from last modified time)
20120318 09:35:03.524 00000003 1 07 0 0 00 0004 00E0: Timer manager started with 32 timers
20120318 09:35:03.524 00000004 1 05 0 0 00 0004 0008: Registry filtering initialized
20120318 09:35:03.524 00000005 1 02 0 0 00 0004 0008: Hooking SSDT start.
20120318 09:35:03.524 00000006 1 02 0 0 00 0004 00E8: volume processing WI function started, waiting for boot driver to start...
20120318 09:35:03.524 00000007 1 02 0 0 00 0004 0008: Hooking SSDT done, 0 intercepts installed.
20120318 09:35:03.524 00000008 1 23 0 0 00 0004 0008: IVM operation mode: NativeMode
20120318 09:35:03.524 00000009 1 23 0 0 00 0004 0008: IvmNativeStart: started the thread to wait for the VHD and start the session
20120318 09:35:03.540 0000000A 2 02 0 0 00 0004 0008: IvmStateChange: current driver state StateRunning, status 0x0
20120318 09:35:03.540 0000000B 2 02 0 0 00 0004 0008: DriverEntry: driver load successful, status 0x0
20120318 09:35:03.680 0000000C 1 02 1 0 00 0004 0034: PNP notification for volume [\??\STORAGE#Volume#{837b9062-7085-11e1-9215-806e6f6e6963}#0000000000100000#{53f5630d-b6bf-11d0-94f2-00a0c91efb8b}]
20120318 09:35:03.727 0000000D 1 02 1 0 00 0004 0034: PNP notification for volume [\??\STORAGE#Volume#{837b9062-7085-11e1-9215-806e6f6e6963}#0000000006500000#{53f5630d-b6bf-11d0-94f2-00a0c91efb8b}]
20120318 09:35:04.601 0000000E 1 03 1 0 00 0004 0008: attached to volume [\Ntfs][\Device\HarddiskVolume2] on C:
20120318 09:35:07.112 0000000F 1 02 0 0 00 0004 00E8: volume processing WI function now processing notifications...
20120318 09:35:07.112 00000010 1 23 0 0 00 0004 00EC: IvmpNativeSessionCreationFunction: IvmBoot got loaded and signaled, waiting for the volume to show up
20120318 09:35:07.112 00000011 1 02 0 0 00 0004 00E8: volume processing WI function dequeued volume [\??\STORAGE#Volume#{837b9062-7085-11e1-9215-806e6f6e6963}#0000000006500000#{53f5630d-b6bf-11d0-94f2-00a0c91efb8b}]
20120318 09:35:07.112 00000012 1 07 0 0 00 0004 00E8: IvmLogSwitchToFile: relocating log to file \??\STORAGE#Volume#{837b9062-7085-11e1-9215-806e6f6e6963}#0000000006500000#{53f5630d-b6bf-11d0-94f2-00a0c91efb8b}\IvmSupervisor.log, see you there!
20120318 09:35:07.112 00000013 1 07 0 0 00 0004 00E8: IvmLogSwitchToFile: after switching the log file...
20120318 09:35:07.112 00000014 1 02 0 0 00 0004 00E8: moved log file to BOOT volume...
20120318 09:35:07.112 00000015 1 02 0 0 00 0004 00E8: volume processing WI function checking volume [\??\STORAGE#Volume#{837b9062-7085-11e1-9215-806e6f6e6963}#0000000006500000#{53f5630d-b6bf-11d0-94f2-00a0c91efb8b}]
20120318 09:35:07.112 00000016 1 02 0 0 00 0004 00E8: IvmBootpCheckAndStartIvm:allocated all the strings
20120318 09:35:09.187 00000017 1 02 0 0 00 0004 00E8: IvmBootpCheckAndStartIvm:failed to open the volume guard file (C0000034), volume won't grow but we should try to start the session anyway.
20120318 09:35:09.187 00000018 1 02 0 0 00 0004 00E8: IvmBootpCheckAndStartIvm:couldn't open the recomposition guard file
20120318 09:35:09.187 00000019 1 02 0 0 00 0004 00E8: IvmBootpCheckAndStartIvm failed with C0000034
20120318 09:35:09.187 0000001A 1 02 0 0 00 0004 00E8: volume processing WI function dequeued volume [\??\STORAGE#Volume#{837b9062-7085-11e1-9215-806e6f6e6963}#0000000000100000#{53f5630d-b6bf-11d0-94f2-00a0c91efb8b}]
20120318 09:35:09.203 0000001B 1 02 0 0 00 0004 00E8: volume processing WI function checking volume [\??\STORAGE#Volume#{837b9062-7085-11e1-9215-806e6f6e6963}#0000000000100000#{53f5630d-b6bf-11d0-94f2-00a0c91efb8b}]
20120318 09:35:09.203 0000001C 1 02 0 0 00 0004 00E8: IvmBootpCheckAndStartIvm:allocated all the strings
20120318 09:35:09.499 0000001D 1 03 1 0 00 0004 00E8: attached to volume [\Ntfs][\Device\HarddiskVolume1] on \\?\Volume{a56ceda3-6a8a-11e1-965c-806e6f6e6963}
20120318 09:35:09.499 0000001E 1 02 0 0 00 0004 00E8: IvmBootpCheckAndStartIvm:failed to open the volume guard file (C0000034), volume won't grow but we should try to start the session anyway.
20120318 09:35:09.499 0000001F 1 02 0 0 00 0004 00E8: IvmBootpCheckAndStartIvm:couldn't open the recomposition guard file
20120318 09:35:09.499 00000020 1 02 0 0 00 0004 00E8: IvmBootpCheckAndStartIvm failed with C0000034
20120318 09:35:37.127 00000021 1 23 0 0 00 0004 00EC: IvmpNativeSessionCreationFunction: timed out waiting for the volume, check if we found a VHD at all
20120318 09:35:37.127 00000022 1 23 0 1 01 0004 00EC: IvmpNativeSessionCreationFunction: no vhd, signal that session creation was aborted
20120318 09:35:37.127 00000023 0 23 0 0 00 0004 00EC: IvmpNativeSessionCreationFunction: failed to find IVM volume in time (status:00000102)... abort session creation
20120318 09:35:37.127 00000024 0 02 0 0 00 0004 00E8: IvmBootpVolumeProcessingWIFunction: IVM session was created or aborted... stop processing volumes
20120318 09:35:37.127 00000025 1 02 0 0 00 0004 00E8: IvmBootpVolumeProcessingWIFunction: unregistering volume notification...
20120318 09:55:55.147 00000026 1 03 1 0 00 0004 0034: attached to volume [\Ntfs][\Device\IvmVhdDisk00000001] on V:
20120318 09:57:33.084 00000027 1 03 0 0 00 0004 002C: IvmFileSystemVolumeInstanceTeardownCallback: instance teardown for volume [\Device\IvmVhdDisk00000001], reason 8
20120318 09:57:33.084 00000028 1 03 0 0 00 0004 002C: detached from volume [\Device\IvmVhdDisk00000001]
20120318 10:00:58.478 00000001 1 07 0 0 00 0004 0008: IvmLog initialization complete
20120318 10:00:58.478 00000002 1 07 0 0 00 0004 0008: Ivm REL built at Fri Nov  4 00:36:44 2011. (Note that is different from last modified time)
20120318 10:00:58.478 00000003 1 07 0 0 00 0004 00E0: Timer manager started with 32 timers
20120318 10:00:58.478 00000004 1 05 0 0 00 0004 0008: Registry filtering initialized
20120318 10:00:58.478 00000005 1 02 0 0 00 0004 0008: Hooking SSDT start.
20120318 10:00:58.478 00000006 1 02 0 0 00 0004 00E8: volume processing WI function started, waiting for boot driver to start...
20120318 10:00:58.478 00000007 1 02 0 0 00 0004 0008: Hooking SSDT done, 0 intercepts installed.
20120318 10:00:58.478 00000008 1 23 0 0 00 0004 0008: IVM operation mode: NativeMode
20120318 10:00:58.478 00000009 1 23 0 0 00 0004 0008: IvmNativeStart: started the thread to wait for the VHD and start the session
20120318 10:00:58.478 0000000A 2 02 0 0 00 0004 0008: IvmStateChange: current driver state StateRunning, status 0x0
20120318 10:00:58.478 0000000B 2 02 0 0 00 0004 0008: DriverEntry: driver load successful, status 0x0
20120318 10:00:58.649 0000000C 1 02 1 0 00 0004 0034: PNP notification for volume [\??\STORAGE#Volume#{837b9062-7085-11e1-9215-806e6f6e6963}#0000000000100000#{53f5630d-b6bf-11d0-94f2-00a0c91efb8b}]
20120318 10:00:58.680 0000000D 1 02 1 0 00 0004 0034: PNP notification for volume [\??\STORAGE#Volume#{837b9062-7085-11e1-9215-806e6f6e6963}#0000000006500000#{53f5630d-b6bf-11d0-94f2-00a0c91efb8b}]
20120318 10:00:59.772 0000000E 1 03 1 0 00 0004 0008: attached to volume [\Ntfs][\Device\HarddiskVolume2] on C:
20120318 10:01:02.378 0000000F 1 02 0 0 00 0004 00E8: volume processing WI function now processing notifications...
20120318 10:01:02.378 00000010 1 23 0 0 00 0004 00EC: IvmpNativeSessionCreationFunction: IvmBoot got loaded and signaled, waiting for the volume to show up
20120318 10:01:02.378 00000011 1 02 0 0 00 0004 00E8: volume processing WI function dequeued volume [\??\STORAGE#Volume#{837b9062-7085-11e1-9215-806e6f6e6963}#0000000006500000#{53f5630d-b6bf-11d0-94f2-00a0c91efb8b}]
20120318 10:01:02.378 00000012 1 07 0 0 00 0004 00E8: IvmLogSwitchToFile: relocating log to file \??\STORAGE#Volume#{837b9062-7085-11e1-9215-806e6f6e6963}#0000000006500000#{53f5630d-b6bf-11d0-94f2-00a0c91efb8b}\IvmSupervisor.log, see you there!
20120318 10:01:02.378 00000013 1 07 0 0 00 0004 00E8: IvmLogSwitchToFile: after switching the log file...
20120318 10:01:02.378 00000014 1 02 0 0 00 0004 00E8: moved log file to BOOT volume...
20120318 10:01:02.378 00000015 1 02 0 0 00 0004 00E8: volume processing WI function checking volume [\??\STORAGE#Volume#{837b9062-7085-11e1-9215-806e6f6e6963}#0000000006500000#{53f5630d-b6bf-11d0-94f2-00a0c91efb8b}]
20120318 10:01:02.378 00000016 1 02 0 0 00 0004 00E8: IvmBootpCheckAndStartIvm:allocated all the strings
20120318 10:01:02.378 00000017 1 02 0 0 00 0004 00E8: IvmBootpCheckAndStartIvm:failed to open the volume guard file (C0000034), volume won't grow but we should try to start the session anyway.
20120318 10:01:02.378 00000018 1 02 0 0 00 0004 00E8: IvmBootpCheckAndStartIvm:couldn't open the recomposition guard file
20120318 10:01:02.378 00000019 1 02 0 0 00 0004 00E8: IvmBootpCheckAndStartIvm failed with C0000034
20120318 10:01:02.378 0000001A 1 02 0 0 00 0004 00E8: volume processing WI function dequeued volume [\??\STORAGE#Volume#{837b9062-7085-11e1-9215-806e6f6e6963}#0000000000100000#{53f5630d-b6bf-11d0-94f2-00a0c91efb8b}]
20120318 10:01:02.378 0000001B 1 02 0 0 00 0004 00E8: volume processing WI function checking volume [\??\STORAGE#Volume#{837b9062-7085-11e1-9215-806e6f6e6963}#0000000000100000#{53f5630d-b6bf-11d0-94f2-00a0c91efb8b}]
20120318 10:01:02.378 0000001C 1 02 0 0 00 0004 00E8: IvmBootpCheckAndStartIvm:allocated all the strings
20120318 10:01:03.033 0000001D 1 03 1 0 00 0004 00E8: attached to volume [\Ntfs][\Device\HarddiskVolume1] on \\?\Volume{a56ceda3-6a8a-11e1-965c-806e6f6e6963}
20120318 10:01:03.033 0000001E 1 02 0 0 00 0004 00E8: IvmBootpCheckAndStartIvm:failed to open the volume guard file (C0000034), volume won't grow but we should try to start the session anyway.
20120318 10:01:03.033 0000001F 1 02 0 0 00 0004 00E8: IvmBootpCheckAndStartIvm:couldn't open the recomposition guard file
20120318 10:01:03.033 00000020 1 02 0 0 00 0004 00E8: IvmBootpCheckAndStartIvm failed with C0000034
20120318 10:01:32.392 00000021 1 23 0 0 00 0004 00EC: IvmpNativeSessionCreationFunction: timed out waiting for the volume, check if we found a VHD at all
20120318 10:01:32.392 00000022 1 23 0 1 01 0004 00EC: IvmpNativeSessionCreationFunction: no vhd, signal that session creation was aborted
20120318 10:01:32.392 00000023 0 23 0 0 00 0004 00EC: IvmpNativeSessionCreationFunction: failed to find IVM volume in time (status:00000102)... abort session creation
20120318 10:01:32.392 00000024 0 02 0 0 00 0004 00E8: IvmBootpVolumeProcessingWIFunction: IVM session was created or aborted... stop processing volumes
20120318 10:01:32.392 00000025 1 02 0 0 00 0004 00E8: IvmBootpVolumeProcessingWIFunction: unregistering volume notification...
20120318 10:14:44.195 00000026 1 03 1 0 00 0004 0038: attached to volume [\Ntfs][\Device\IvmVhdDisk00000001] on V:
20120318 10:16:19.183 00000027 1 03 0 0 00 0004 0030: IvmFileSystemVolumeInstanceTeardownCallback: instance teardown for volume [\Device\IvmVhdDisk00000001], reason 8
20120318 10:16:19.183 00000028 1 03 0 0 00 0004 0030: detached from volume [\Device\IvmVhdDisk00000001]
20120318 10:28:44.540 00000001 1 07 0 0 00 0004 0008: IvmLog initialization complete
20120318 10:28:44.540 00000002 1 07 0 0 00 0004 0008: Ivm REL built at Fri Nov  4 00:36:44 2011. (Note that is different from last modified time)
20120318 10:28:44.540 00000003 1 07 0 0 00 0004 00E0: Timer manager started with 32 timers
20120318 10:28:44.540 00000004 1 05 0 0 00 0004 0008: Registry filtering initialized
20120318 10:28:44.540 00000005 1 02 0 0 00 0004 0008: Hooking SSDT start.
20120318 10:28:44.540 00000006 1 02 0 0 00 0004 00E8: volume processing WI function started, waiting for boot driver to start...
20120318 10:28:44.540 00000007 1 02 0 0 00 0004 0008: Hooking SSDT done, 0 intercepts installed.
20120318 10:28:44.540 00000008 1 23 0 0 00 0004 0008: IVM operation mode: NativeMode
20120318 10:28:44.540 00000009 1 23 0 0 00 0004 0008: IvmNativeStart: started the thread to wait for the VHD and start the session
20120318 10:28:44.540 0000000A 2 02 0 0 00 0004 0008: IvmStateChange: current driver state StateRunning, status 0x0
20120318 10:28:44.540 0000000B 2 02 0 0 00 0004 0008: DriverEntry: driver load successful, status 0x0
20120318 10:28:44.712 0000000C 1 02 1 0 00 0004 0034: PNP notification for volume [\??\STORAGE#Volume#{837b9062-7085-11e1-9215-806e6f6e6963}#0000000000100000#{53f5630d-b6bf-11d0-94f2-00a0c91efb8b}]
20120318 10:28:44.758 0000000D 1 02 1 0 00 0004 0034: PNP notification for volume [\??\STORAGE#Volume#{837b9062-7085-11e1-9215-806e6f6e6963}#0000000006500000#{53f5630d-b6bf-11d0-94f2-00a0c91efb8b}]
20120318 10:28:47.676 0000000E 1 03 1 0 00 0004 0008: attached to volume [\Ntfs][\Device\HarddiskVolume2] on C:
20120318 10:28:48.112 0000000F 1 02 0 0 00 0004 00E8: volume processing WI function now processing notifications...
20120318 10:28:48.112 00000010 1 23 0 0 00 0004 00EC: IvmpNativeSessionCreationFunction: IvmBoot got loaded and signaled, waiting for the volume to show up
20120318 10:28:48.112 00000011 1 02 0 0 00 0004 00E8: volume processing WI function dequeued volume [\??\STORAGE#Volume#{837b9062-7085-11e1-9215-806e6f6e6963}#0000000006500000#{53f5630d-b6bf-11d0-94f2-00a0c91efb8b}]
20120318 10:28:48.112 00000012 1 07 0 0 00 0004 00E8: IvmLogSwitchToFile: relocating log to file \??\STORAGE#Volume#{837b9062-7085-11e1-9215-806e6f6e6963}#0000000006500000#{53f5630d-b6bf-11d0-94f2-00a0c91efb8b}\IvmSupervisor.log, see you there!
20120318 10:28:48.112 00000013 1 07 0 0 00 0004 00E8: IvmLogSwitchToFile: after switching the log file...
20120318 10:28:48.112 00000014 1 02 0 0 00 0004 00E8: moved log file to BOOT volume...
20120318 10:28:48.112 00000015 1 02 0 0 00 0004 00E8: volume processing WI function checking volume [\??\STORAGE#Volume#{837b9062-7085-11e1-9215-806e6f6e6963}#0000000006500000#{53f5630d-b6bf-11d0-94f2-00a0c91efb8b}]
20120318 10:28:48.112 00000016 1 02 0 0 00 0004 00E8: IvmBootpCheckAndStartIvm:allocated all the strings
20120318 10:28:48.112 00000017 1 02 0 0 00 0004 00E8: IvmBootpCheckAndStartIvm:failed to open the volume guard file (C0000034), volume won't grow but we should try to start the session anyway.
20120318 10:28:48.112 00000018 1 02 0 0 00 0004 00E8: IvmBootpCheckAndStartIvm:couldn't open the recomposition guard file
20120318 10:28:48.112 00000019 1 02 0 0 00 0004 00E8: IvmBootpCheckAndStartIvm failed with C0000034
20120318 10:28:48.112 0000001A 1 02 0 0 00 0004 00E8: volume processing WI function dequeued volume [\??\STORAGE#Volume#{837b9062-7085-11e1-9215-806e6f6e6963}#0000000000100000#{53f5630d-b6bf-11d0-94f2-00a0c91efb8b}]
20120318 10:28:48.112 0000001B 1 02 0 0 00 0004 00E8: volume processing WI function checking volume [\??\STORAGE#Volume#{837b9062-7085-11e1-9215-806e6f6e6963}#0000000000100000#{53f5630d-b6bf-11d0-94f2-00a0c91efb8b}]
20120318 10:28:48.112 0000001C 1 02 0 0 00 0004 00E8: IvmBootpCheckAndStartIvm:allocated all the strings
20120318 10:28:48.362 0000001D 1 03 1 0 00 0004 00E8: attached to volume [\Ntfs][\Device\HarddiskVolume1] on \\?\Volume{a56ceda3-6a8a-11e1-965c-806e6f6e6963}
20120318 10:28:48.362 0000001E 1 02 0 0 00 0004 00E8: IvmBootpCheckAndStartIvm:failed to open the volume guard file (C0000034), volume won't grow but we should try to start the session anyway.
20120318 10:28:48.362 0000001F 1 02 0 0 00 0004 00E8: IvmBootpCheckAndStartIvm:couldn't open the recomposition guard file
20120318 10:28:48.362 00000020 1 02 0 0 00 0004 00E8: IvmBootpCheckAndStartIvm failed with C0000034
20120318 10:29:18.127 00000021 1 23 0 0 00 0004 00EC: IvmpNativeSessionCreationFunction: timed out waiting for the volume, check if we found a VHD at all
20120318 10:29:18.127 00000022 1 23 0 1 01 0004 00EC: IvmpNativeSessionCreationFunction: no vhd, signal that session creation was aborted
20120318 10:29:18.127 00000023 0 23 0 0 00 0004 00EC: IvmpNativeSessionCreationFunction: failed to find IVM volume in time (status:00000102)... abort session creation
20120318 10:29:18.127 00000024 0 02 0 0 00 0004 00E8: IvmBootpVolumeProcessingWIFunction: IVM session was created or aborted... stop processing volumes
20120318 10:29:18.127 00000025 1 02 0 0 00 0004 00E8: IvmBootpVolumeProcessingWIFunction: unregistering volume notification...
20120318 10:33:51.448 00000026 1 03 1 0 00 0004 003C: attached to volume [\Ntfs][\Device\IvmVhdDisk00000001] on V:
20120318 10:35:32.599 00000027 1 03 0 0 00 0004 0040: IvmFileSystemVolumeInstanceTeardownCallback: instance teardown for volume [\Device\IvmVhdDisk00000001], reason 8
20120318 10:35:32.599 00000028 1 03 0 0 00 0004 0040: detached from volume [\Device\IvmVhdDisk00000001]
20120318 10:40:43.400 00000001 1 07 0 0 00 0004 0008: IvmLog initialization complete
20120318 10:40:43.400 00000002 1 07 0 0 00 0004 0008: Ivm REL built at Fri Nov  4 00:36:44 2011. (Note that is different from last modified time)
20120318 10:40:43.400 00000003 1 07 0 0 00 0004 00E0: Timer manager started with 32 timers
20120318 10:40:43.400 00000004 1 05 0 0 00 0004 0008: Registry filtering initialized
20120318 10:40:43.400 00000005 1 02 0 0 00 0004 0008: Hooking SSDT start.
20120318 10:40:43.400 00000006 1 02 0 0 00 0004 00E8: volume processing WI function started, waiting for boot driver to start...
20120318 10:40:43.400 00000007 1 02 0 0 00 0004 0008: Hooking SSDT done, 0 intercepts installed.
20120318 10:40:43.400 00000008 1 23 0 0 00 0004 0008: IVM operation mode: NativeMode
20120318 10:40:43.400 00000009 1 23 0 0 00 0004 0008: IvmNativeStart: started the thread to wait for the VHD and start the session
20120318 10:40:43.400 0000000A 2 02 0 0 00 0004 0008: IvmStateChange: current driver state StateRunning, status 0x0
20120318 10:40:43.400 0000000B 2 02 0 0 00 0004 0008: DriverEntry: driver load successful, status 0x0
20120318 10:41:16.300 0000000C 1 02 1 0 00 0004 0040: PNP notification for volume [\??\STORAGE#Volume#{837b9062-7085-11e1-9215-806e6f6e6963}#0000000000100000#{53f5630d-b6bf-11d0-94f2-00a0c91efb8b}]
20120318 10:41:16.331 0000000D 1 02 1 0 00 0004 0040: PNP notification for volume [\??\STORAGE#Volume#{837b9062-7085-11e1-9215-806e6f6e6963}#0000000006500000#{53f5630d-b6bf-11d0-94f2-00a0c91efb8b}]
20120318 10:41:16.690 0000000E 1 03 1 0 00 0004 0008: attached to volume [\Ntfs][\Device\HarddiskVolume2] on C:
20120318 10:41:17.345 0000000F 1 02 0 0 00 0004 00E8: volume processing WI function now processing notifications...
20120318 10:41:17.345 00000010 1 23 0 0 00 0004 00EC: IvmpNativeSessionCreationFunction: IvmBoot got loaded and signaled, waiting for the volume to show up
20120318 10:41:17.345 00000011 1 02 0 0 00 0004 00E8: volume processing WI function dequeued volume [\??\STORAGE#Volume#{837b9062-7085-11e1-9215-806e6f6e6963}#0000000006500000#{53f5630d-b6bf-11d0-94f2-00a0c91efb8b}]
20120318 10:41:17.345 00000012 1 07 0 0 00 0004 00E8: IvmLogSwitchToFile: relocating log to file \??\STORAGE#Volume#{837b9062-7085-11e1-9215-806e6f6e6963}#0000000006500000#{53f5630d-b6bf-11d0-94f2-00a0c91efb8b}\IvmSupervisor.log, see you there!
20120318 10:41:17.345 00000013 1 07 0 0 00 0004 00E8: IvmLogSwitchToFile: after switching the log file...
20120318 10:41:17.345 00000014 1 02 0 0 00 0004 00E8: moved log file to BOOT volume...
20120318 10:41:17.345 00000015 1 02 0 0 00 0004 00E8: volume processing WI function checking volume [\??\STORAGE#Volume#{837b9062-7085-11e1-9215-806e6f6e6963}#0000000006500000#{53f5630d-b6bf-11d0-94f2-00a0c91efb8b}]
20120318 10:41:17.345 00000016 1 02 0 0 00 0004 00E8: IvmBootpCheckAndStartIvm:allocated all the strings
20120318 10:41:17.345 00000017 1 02 0 0 00 0004 00E8: IvmBootpCheckAndStartIvm:failed to open the volume guard file (C0000034), volume won't grow but we should try to start the session anyway.
20120318 10:41:17.345 00000018 1 02 0 0 00 0004 00E8: IvmBootpCheckAndStartIvm:couldn't open the recomposition guard file
20120318 10:41:17.345 00000019 1 02 0 0 00 0004 00E8: IvmBootpCheckAndStartIvm failed with C0000034
20120318 10:41:17.345 0000001A 1 02 0 0 00 0004 00E8: volume processing WI function dequeued volume [\??\STORAGE#Volume#{837b9062-7085-11e1-9215-806e6f6e6963}#0000000000100000#{53f5630d-b6bf-11d0-94f2-00a0c91efb8b}]
20120318 10:41:17.345 0000001B 1 02 0 0 00 0004 00E8: volume processing WI function checking volume [\??\STORAGE#Volume#{837b9062-7085-11e1-9215-806e6f6e6963}#0000000000100000#{53f5630d-b6bf-11d0-94f2-00a0c91efb8b}]
20120318 10:41:17.361 0000001C 1 02 0 0 00 0004 00E8: IvmBootpCheckAndStartIvm:allocated all the strings
20120318 10:41:17.564 0000001D 1 03 1 0 00 0004 00E8: attached to volume [\Ntfs][\Device\HarddiskVolume1] on \\?\Volume{a56ceda3-6a8a-11e1-965c-806e6f6e6963}
20120318 10:41:17.564 0000001E 1 02 0 0 00 0004 00E8: IvmBootpCheckAndStartIvm:failed to open the volume guard file (C0000034), volume won't grow but we should try to start the session anyway.
20120318 10:41:17.564 0000001F 1 02 0 0 00 0004 00E8: IvmBootpCheckAndStartIvm:couldn't open the recomposition guard file
20120318 10:41:17.564 00000020 1 02 0 0 00 0004 00E8: IvmBootpCheckAndStartIvm failed with C0000034
20120318 10:41:47.360 00000021 1 23 0 0 00 0004 00EC: IvmpNativeSessionCreationFunction: timed out waiting for the volume, check if we found a VHD at all
20120318 10:41:47.360 00000022 1 23 0 1 01 0004 00EC: IvmpNativeSessionCreationFunction: no vhd, signal that session creation was aborted
20120318 10:41:47.360 00000023 0 23 0 0 00 0004 00EC: IvmpNativeSessionCreationFunction: failed to find IVM volume in time (status:00000102)... abort session creation
20120318 10:41:47.360 00000024 0 02 0 0 00 0004 00E8: IvmBootpVolumeProcessingWIFunction: IVM session was created or aborted... stop processing volumes
20120318 10:41:47.360 00000025 1 02 0 0 00 0004 00E8: IvmBootpVolumeProcessingWIFunction: unregistering volume notification...
20120318 17:39:27.556 00000001 1 07 0 0 00 0004 0008: IvmLog initialization complete
20120318 17:39:27.556 00000002 1 07 0 0 00 0004 0008: Ivm REL built at Fri Nov  4 00:36:44 2011. (Note that is different from last modified time)
20120318 17:39:27.556 00000003 1 07 0 0 00 0004 00E0: Timer manager started with 32 timers
20120318 17:39:27.556 00000004 1 05 0 0 00 0004 0008: Registry filtering initialized
20120318 17:39:27.556 00000005 1 02 0 0 00 0004 0008: Hooking SSDT start.
20120318 17:39:27.556 00000006 1 02 0 0 00 0004 00E8: volume processing WI function started, waiting for boot driver to start...
20120318 17:39:27.556 00000007 1 02 0 0 00 0004 0008: Hooking SSDT done, 0 intercepts installed.
20120318 17:39:27.571 00000008 1 23 0 0 00 0004 0008: IVM operation mode: NativeMode
20120318 17:39:27.571 00000009 1 23 0 0 00 0004 0008: IvmNativeStart: started the thread to wait for the VHD and start the session
20120318 17:39:27.571 0000000A 2 02 0 0 00 0004 0008: IvmStateChange: current driver state StateRunning, status 0x0
20120318 17:39:27.571 0000000B 2 02 0 0 00 0004 0008: DriverEntry: driver load successful, status 0x0
20120318 17:39:27.743 0000000C 1 02 1 0 00 0004 0040: PNP notification for volume [\??\STORAGE#Volume#{837b9062-7085-11e1-9215-806e6f6e6963}#0000000000100000#{53f5630d-b6bf-11d0-94f2-00a0c91efb8b}]
20120318 17:39:27.774 0000000D 1 02 1 0 00 0004 0040: PNP notification for volume [\??\STORAGE#Volume#{837b9062-7085-11e1-9215-806e6f6e6963}#0000000006500000#{53f5630d-b6bf-11d0-94f2-00a0c91efb8b}]
20120318 17:39:28.133 0000000E 1 03 1 0 00 0004 0008: attached to volume [\Ntfs][\Device\HarddiskVolume2] on C:
20120318 17:39:28.866 0000000F 1 02 0 0 00 0004 00E8: volume processing WI function now processing notifications...
20120318 17:39:28.866 00000010 1 23 0 0 00 0004 00EC: IvmpNativeSessionCreationFunction: IvmBoot got loaded and signaled, waiting for the volume to show up
20120318 17:39:28.866 00000011 1 02 0 0 00 0004 00E8: volume processing WI function dequeued volume [\??\STORAGE#Volume#{837b9062-7085-11e1-9215-806e6f6e6963}#0000000006500000#{53f5630d-b6bf-11d0-94f2-00a0c91efb8b}]
20120318 17:39:28.866 00000012 1 07 0 0 00 0004 00E8: IvmLogSwitchToFile: relocating log to file \??\STORAGE#Volume#{837b9062-7085-11e1-9215-806e6f6e6963}#0000000006500000#{53f5630d-b6bf-11d0-94f2-00a0c91efb8b}\IvmSupervisor.log, see you there!
20120318 17:39:28.866 00000013 1 07 0 0 00 0004 00E8: IvmLogSwitchToFile: after switching the log file...
20120318 17:39:28.866 00000014 1 02 0 0 00 0004 00E8: moved log file to BOOT volume...
20120318 17:39:28.866 00000015 1 02 0 0 00 0004 00E8: volume processing WI function checking volume [\??\STORAGE#Volume#{837b9062-7085-11e1-9215-806e6f6e6963}#0000000006500000#{53f5630d-b6bf-11d0-94f2-00a0c91efb8b}]
20120318 17:39:28.866 00000016 1 02 0 0 00 0004 00E8: IvmBootpCheckAndStartIvm:allocated all the strings
20120318 17:39:28.866 00000017 1 02 0 0 00 0004 00E8: IvmBootpCheckAndStartIvm:failed to open the volume guard file (C0000034), volume won't grow but we should try to start the session anyway.
20120318 17:39:28.866 00000018 1 02 0 0 00 0004 00E8: IvmBootpCheckAndStartIvm:couldn't open the recomposition guard file
20120318 17:39:28.866 00000019 1 02 0 0 00 0004 00E8: IvmBootpCheckAndStartIvm failed with C0000034
20120318 17:39:28.866 0000001A 1 02 0 0 00 0004 00E8: volume processing WI function dequeued volume [\??\STORAGE#Volume#{837b9062-7085-11e1-9215-806e6f6e6963}#0000000000100000#{53f5630d-b6bf-11d0-94f2-00a0c91efb8b}]
20120318 17:39:28.866 0000001B 1 02 0 0 00 0004 00E8: volume processing WI function checking volume [\??\STORAGE#Volume#{837b9062-7085-11e1-9215-806e6f6e6963}#0000000000100000#{53f5630d-b6bf-11d0-94f2-00a0c91efb8b}]
20120318 17:39:28.866 0000001C 1 02 0 0 00 0004 00E8: IvmBootpCheckAndStartIvm:allocated all the strings
20120318 17:39:29.084 0000001D 1 03 1 0 00 0004 00E8: attached to volume [\Ntfs][\Device\HarddiskVolume1] on \\?\Volume{a56ceda3-6a8a-11e1-965c-806e6f6e6963}
20120318 17:39:29.084 0000001E 1 02 0 0 00 0004 00E8: IvmBootpCheckAndStartIvm:failed to open the volume guard file (C0000034), volume won't grow but we should try to start the session anyway.
20120318 17:39:29.084 0000001F 1 02 0 0 00 0004 00E8: IvmBootpCheckAndStartIvm:couldn't open the recomposition guard file
20120318 17:39:29.084 00000020 1 02 0 0 00 0004 00E8: IvmBootpCheckAndStartIvm failed with C0000034
20120318 17:39:58.880 00000021 1 23 0 0 00 0004 00EC: IvmpNativeSessionCreationFunction: timed out waiting for the volume, check if we found a VHD at all
20120318 17:39:58.880 00000022 1 23 0 1 01 0004 00EC: IvmpNativeSessionCreationFunction: no vhd, signal that session creation was aborted
20120318 17:39:58.880 00000023 0 23 0 0 00 0004 00EC: IvmpNativeSessionCreationFunction: failed to find IVM volume in time (status:00000102)... abort session creation
20120318 17:39:58.880 00000024 0 02 0 0 00 0004 00E8: IvmBootpVolumeProcessingWIFunction: IVM session was created or aborted... stop processing volumes
20120318 17:39:58.880 00000025 1 02 0 0 00 0004 00E8: IvmBootpVolumeProcessingWIFunction: unregistering volume notification...

Clearly with the SysVol-lvmSupervisor.log file, something was wrong… It took me some time to figure out what could be wrong. I just noticed every time I wanted to use Imaging Wizard, when the VM needed to reboot to load the vDisk and boot, before restarting the Personal vDisk inventory manager was launch and requested to be updated… So I did the update but at every reboot the same pop-up came again and again…

I went to read the “manual” :

To update master images that use personal vDisks

You enable the personal vDisk feature for use with a master image when you install the Virtual Desktop Agent. During the installation procedure and after any update to the image after installation, it is important that the disk’s inventory is refreshed and a new snapshot is created. This procedure describes the required steps.

Because administrators, not users, manage master images, if you install an application that places binary files in the administrator’s user profile, the application is not available to users of shared virtual desktops (including those based on pooled catalogs and pooled with personal vDisk catalogs). Users must install such applications themselves.

It is best practice to take a snapshot of the image after each step in this procedure.

  1. Update the master image by installing any applications or operating system updates, and performing any system configuration on the machine.For master images based on Windows XP that you plan to deploy with personal vDisks, check that no dialog boxes are open (for example, messages confirming software installations or prompts to use unsigned drivers). Open dialog boxes on master images in this environment prevent the Virtual Desktop Agent from registering with the controller. You can prevent prompts for unsigned drivers using the Control Panel. For example, on Windows XP click System > Hardware > Driver Signing, and select the option to ignore warnings.
  2. Shut down the machine. For Windows 7 machines, click Cancel when Citrix personal vDisk blocks the shutdown.
  3. In the Citrix personal vDisk dialog box, click Update Inventory. This step may take several minutes to complete.
    Important: If you interrupt the following shutdown (even to make a minor update to the image), the personal vDisk’s inventory no longer matches the master image. This causes the personal vDisk feature to stop working. If you interrupt the shutdown, you must restart the machine, shut it down, and when prompted click Update Inventory again.
  4. When the inventory operation shuts down the machine, take a snapshot of the master image.

In fact what I didn’t read on the Citrix eDoc are the step to create the golden image and how to use Personal vDisk Inventory Update tool :

  1. Build you Microsoft Windows golden image.
  2. Install apps and everything you need.
  3. Use Imaging Wizard to export your VMs on a vDisk to a PVS store.
  4. (This is what I didn’t read in the manual) Switch the boot of the VM you used (in PVS) to boot from vDisk instead of Hard Drive (Keep the vDisk in private mode)
  5. Boot the VM and then run the Personal vDisk Inventory Update (just Shutdown the VM and click Cancel when Citrix personal vDisk blocks the shutdown.
  6. Shutdown the VM.
  7. Change the vDisk mode to standard and create new VMs through the XenDesktop Wizard as follow :

And boot up you new VMs, everything should work like a charm with Personal vDisk enable

To sum up this blog, you need to boot your vDisk at least one time in private mode to run the Personal vDisk Inventory Update before changing the vDisk mode to standard and boot all your VMs.

Resources :
About Personal vDisk, Citrix eDocs : [link]
XenDesktop 5.6 Citrix eDocs : [link]

Post author