VMware Horizon Community
elgwhoppo
Hot Shot
Hot Shot
Jump to solution

In-Guest VHD Capture Error

Hey All, I'm testing an AppVolumes 2.9 In-Guest VHD setup and getting a weird error during capture. When attempting to provision an appstack on a packaging VM I get the following error: Unable to mount provisioning volume "TestAppStack1"

In the event logs on the manager servers it looks like this (bolded underlined is interesting):

[2015-06-24 16:45:18 UTC] P3228R76  INFO (NTLM) Authenticating workstation APPVCAP1$ on domain PYRO

[2015-06-24 16:45:18 UTC] P3228R76  INFO Processing by Agent::ComputersController#startup as HTML

[2015-06-24 16:45:18 UTC] P3228R76  INFO   Parameters: {"name"=>"svservice", "uuid"=>"42220fa2-5e2d-3b7c-2c1b-9e7d56f1d26c", "status"=>"0", "osver"=>"6.1.7601", "sp"=>"1.0", "suite"=>"256", "product"=>"1", "arch"=>"0", "proc"=>"1", "agentver"=>"2.9.0.726U", "domain"=>"PYRO", "workstation"=>"APPVCAP1", "pre-startup"=>"1", "machinesid"=>"S-1-5-21-840342296-2375657599-223093104"}

[2015-06-24 16:45:18 UTC] P3228R76  INFO        Cvo: Manager version: "2.9.0.23" - Running as "APPVOLUMES2$@PYRO"

[2015-06-24 16:45:18 UTC] P3228R76  INFO    Manager: Computer Startup: upn="PYRO\APPVCAP1$" account="APPVCAP1$" - RequestMachine: IP="10.0.102.2" UUID="42220fa2-5e2d-3b7c-2c1b-9e7d56f1d26c"

[2015-06-24 16:45:18 UTC] P3228R76  INFO        Cvo: Loaded existing record for "Computer <PYRO\APPVCAP1$>"

[2015-06-24 16:45:18 UTC] P3228R76  INFO        Cvo: Re-using "#<Cvo::Hypervisor::InGuestAdapter:0x84c8340>" - 166 secs old - Ping took 0ms

[2015-06-24 16:45:18 UTC] P3228R76  INFO        Cvo: Onlining "Computer <PYRO\APPVCAP1$>" with 4 previous login(s) - last login: 2015-06-24 16:32:25 UTC

[2015-06-24 16:45:18 UTC] P3228R76  INFO        Cvo: Removing "0" (non-early) attachments on "Computer <PYRO\APPVCAP1$>"

[2015-06-24 16:45:18 UTC] P3228R76  INFO        Cvo: Detaching volumes for "Computer <PYRO\APPVCAP1$>"

[2015-06-24 16:45:18 UTC] P3228R76  INFO        Cvo: Unable to unmount volumes for "Computer <PYRO\APPVCAP1$>" because a target VM was not provided

[2015-06-24 16:45:18 UTC] P3228R76  INFO        Cvo: Starting capture for "TestAppStack1" in "Computer <PYRO\APPVCAP1$>" on ""

[2015-06-24 16:45:18 UTC] P3228R76  INFO        Cvo: Unable to mount "TestAppStack1" because a target machine was not provided

[2015-06-24 16:45:18 UTC] P3228R76  INFO        Cvo: Unable to attach volume "TestAppStack1" to ""

[2015-06-24 16:45:18 UTC] P3228R76 ERROR        Cvo: Unable to mount provisioning volume "TestAppStack1"

[2015-06-24 16:45:18 UTC] P3228R76  INFO   Rendered text template (0.0ms)

[2015-06-24 16:45:18 UTC] P3228R76  INFO Completed 200 OK in 405.7ms (Views: 31.3ms | ActiveRecord: 78.1ms)

[2015-06-24 16:45:18 UTC] P3228R76  INFO

I've done the following:

  • The capture VM is powered off before starting.
  • The logged on user can authenticate and write to the SMB share
  • Completely rebuilt the capture machine
  • Restarted all components

It looks like because of the empty quotes that something isn't right and it's still trying to capture applications with the VMware settings rather than with In-Guest VHD.

Not sure why it's failing to get some of the necessary information.

Interesting....I just noteced that the agent log that the agent seems to think it's a vCenter, rather than an In-Guest VHD. Not sure why that is.

[2015-06-24 16:44:51.858 UTC] [svservice:P880:T916] UninitializeWmi: called

[2015-06-24 16:44:51.858 UTC] [svservice:P880:T916] *** Finished

[2015-06-24 16:45:33.028 UTC] [svservice:P868:T872] *** Started

[2015-06-24 16:45:33.043 UTC] [svservice:P868:T872] Running from: C:\Program Files\CloudVolumes\Agent\svservice.exe (release build)

[2015-06-24 16:45:33.043 UTC] [svservice:P868:T912] Checking agent version from "C:\Program Files\CloudVolumes\Agent\VERSION32.txt"

[2015-06-24 16:45:33.043 UTC] [svservice:P868:T912] Build: "Release-Agent-Build-32" (letter U)

[2015-06-24 16:45:33.043 UTC] [svservice:P868:T912] Build version: "2.9.0.726U"

[2015-06-24 16:45:33.043 UTC] [svservice:P868:T912] CheckOfflineVHDMode: dwResetWritableDays was set to (0) days, turn off offline mode!

[2015-06-24 16:45:33.043 UTC] [svservice:P868:T912] VHD offline mode was off!

[2015-06-24 16:45:33.043 UTC] [svservice:P868:T912] ServiceInit starting

[2015-06-24 16:45:34.182 UTC] [svservice:P868:T912] Running on Windows 6.1 build 7601 (service pack 1.0)

[2015-06-24 16:45:34.182 UTC] [svservice:P868:T912] OS is a workstation

[2015-06-24 16:45:34.182 UTC] [svservice:P868:T912] Architecture: x86 (1 processors)

[2015-06-24 16:45:34.182 UTC] [svservice:P868:T912] Running as: PYRO\APPVCAP1$ (NameSamCompatible)

[2015-06-24 16:45:34.182 UTC] [svservice:P868:T912] Setting status to SERVICE_START_PENDING

[2015-06-24 16:45:34.182 UTC] [svservice:P868:T912] MachineSID is "S-1-5-21-840342296-2375657599-223093104"

[2015-06-24 16:45:34.182 UTC] [svservice:P868:T912] Hypervisor configured as: vcenter

[2015-06-24 16:45:34.182 UTC] [svservice:P868:T912] CleanUpSystemDrive: Flag CleanSystemWritable was configured, auto cleanup the system writable directories...

[2015-06-24 16:45:34.182 UTC] [svservice:P868:T912] Moving C:\SnapVolumesTemp to C:\SnapVolumesTemp.old

[2015-06-24 16:45:34.182 UTC] [svservice:P868:T912] CleanUpSystemDrive: deleted "C:\SnapVolumesTemp"

[2015-06-24 16:45:34.182 UTC] [svservice:P868:T912] InitMountedVolumesObjects: called (initialized 0)

[2015-06-24 16:45:34.182 UTC] [svservice:P868:T912] Using 60 worker threads to communicate with driver

[2015-06-24 16:45:34.182 UTC] [svservice:P868:T912] InitializeWmi: called

[2015-06-24 16:45:34.198 UTC] [svservice:P868:T912] UpdateInteractiveSessionCount: SessionId 0 of 2 -> CurrentSessionId 0 Name(Services) State(4)

[2015-06-24 16:45:34.198 UTC] [svservice:P868:T912] UpdateInteractiveSessionCount: SessionId 1 of 2 -> CurrentSessionId 1 Name(Console) State(2)

[2015-06-24 16:45:34.198 UTC] [svservice:P868:T912] UpdateInteractiveSessionCount: Found 0 active / 2 total user session(s)

[2015-06-24 16:45:34.198 UTC] [svservice:P868:T912] HttpComputerStartup: called 0 logged in (computer startup)

Also when I look at the service registry at HKLM\SYSTEM\CurrentControlSet\services\svservice\Parameters

The Hypervisor REG_SZ value is set to vcenter....but this is supposed to be an In-Guest VHD deployment. So...that's weird. Anybody else doing in-guest VHD?

VCDX-Desktop
0 Kudos
1 Solution

Accepted Solutions
elgwhoppo
Hot Shot
Hot Shot
Jump to solution

Turns out that I needed to start with a fresh database (rather than just check the overwrite box) and a fresh capture machine. Once I did that it worked fine, even though the endpoint type was vcenter.

VCDX-Desktop

View solution in original post

0 Kudos
2 Replies
elgwhoppo
Hot Shot
Hot Shot
Jump to solution

Apparently In-Guest VHD is not for a VMware based VDI at all. I want to use In-Guest attach for VMware based VMs, and the install keeps tagging the capture VM as a vcenter endpoint.

So what is the appropriate registry to force In-Guest VHD? When I set it to localhost or VHD the logs say unknown, but if I say xenserver at least it recognizes that. Still, no joy on the capture even with those settings in place.

For those curious about why the heck this is coming up, I want the appstacks and writable volumes on SMB shares so they can be easily replicated.

VCDX-Desktop
0 Kudos
elgwhoppo
Hot Shot
Hot Shot
Jump to solution

Turns out that I needed to start with a fresh database (rather than just check the overwrite box) and a fresh capture machine. Once I did that it worked fine, even though the endpoint type was vcenter.

VCDX-Desktop
0 Kudos