Hello, Sorry, I forgot to mention this but I also noticed you may have encountered this bug: https://issues.apache.org/jira/browse/VCL-928
Try changing the SCSI controller to "LSI Logic SAS" and see if the VM can boot. If this works, a workaround would be to create this file: /vmfs/volumes/datastore1/win7base/win7base.vmx.reference Add this line to the file and save it: scsi0.virtualdev = "lsisas1068" This should cause VCL to use the "LSI Logic SAS" adapter for this image and this image only. For future images you create, change the "Virtual Disk Mode" setting for the VM host from "shared" to "dedicated". This setting only affects how VCL handles things if the location where the VM working directories reside is low on space and images need to be deleted. This isn't an issue for you since you have the repository path set and have plenty of space for now. If this does not work, please send the vcld.log output from the current failure and I'll dig deeper. Hope this helps, Andy On Fri, Jul 22, 2016 at 10:25 AM, Luckmore Chirongo <[email protected] > wrote: > Hi Andy, > > Thanks for your response. I have commented out the code in VMware.pm and > the vm is now able to continue booting. > > Unfortunately it gets a BSOD before completing boot and resets. In the > vmware.log file, I saw: > > 2016-07-22T13:09:38.523Z| vcpu-0| I120: CDROM: Mode Sense for Unsupported > Page 0x1B > 2016-07-22T13:09:38.523Z| vcpu-0| I120: CDROM ide0:0: CMD 0x5a (MODE > SENSE(10)) FAILED (key 0x5 asc 0x24 ascq 0) > > I then went on to remove the cdrom device just to test and got another > BSOD, but the vmware.log file was no longer showing the cdrom device error. > > Attached is the vmware.log file and the BSOD screen with the error code. > > Thanks again for your assistance > > Kind regards, > Luckmore Chirongo > > > ------------------------------ > *From:* Andy Kurth <[email protected]> > *To:* [email protected]; Luckmore Chirongo <[email protected]> > *Sent:* Thursday, July 21, 2016 7:43 PM > > *Subject:* Re: Image capture failing > > Hello, > The problem relates to: > > 2016-07-16T13:54:52.556Z| vmx| I120: Msg_Question: > 2016-07-16T13:54:52.556Z| vmx| I120: [msg.cpuid.noVHVQuestion] Virtualized > Intel VT-x/EPT is not supported on this platform. > 2016-07-16T13:54:52.556Z| vmx| I120+ Continue without virtualized Intel > VT-x/EPT? > 2016-07-16T13:54:52.556Z| vmx| I120: > ---------------------------------------- > 2016-07-16T13:54:52.556Z| vmx| I120: MsgIsAnswered: Using builtin default > '_No' as the answer for 'msg.cpuid.noVHVQuestion' > 2016-07-16T13:54:52.556Z| vmx| I120: MsgQuestion: msg.cpuid.noVHVQuestion > reply=1 > 2016-07-16T13:54:52.556Z| vmx| I120: Module CPUID power on failed. > > > I think the reason it is happening is because the VCL code is adding the > following settings to the .vmx file: > > monitor.virtual_exec = "hardware" > monitor.virtual_mmu = "hardware" > vhv.enable = "TRUE" > > These settings allow you to run a nested ESXi or KVM VM on an ESXi host. > You can prevent these from being added on your host by commenting out the > lines in: > File: /usr/local/vcl/lib/VCL/Module/Provisioning/VMware/VMware.pm > > Add a # to the beginning of these lines and save VMware.pm: > "monitor.virtual_mmu" => "hardware", > "monitor.virtual_exec" => "hardware", > "vhv.enable" => "TRUE", > > I'll try to improve the code to detect whether the host is capable of > using these settings. > > Regards, > Andy > > > > On Wed, Jul 20, 2016 at 5:31 AM, Luckmore Chirongo < > [email protected]> wrote: > > Hello Andy, > > Please receive the attached file. > > Thanks, > Luckmore Chirongo > > > ------------------------------ > *From:* Andy Kurth <[email protected]> > *To:* [email protected]; Luckmore Chirongo <[email protected]> > *Sent:* Tuesday, July 19, 2016 4:32 PM > *Subject:* Re: Image capture failing > > Hello, > There should be a file in the VM's directory: > /vmfs/volumes/datastore1/vcl-running/win7base_4-v0/vmware.log > > This file should have more information. Please send it. > > Thanks, > Andy > > On Sat, Jul 16, 2016 at 10:12 AM, Luckmore Chirongo < > [email protected]> wrote: > > Hello, > > I have a VCL installation on one VMware host with local storage and one > management node. > > When capturing an image, the process fails and the vcld log shows > something to the effect that VCL is unable to power up the captured image. > > Specs: Dell Poweredge 2960 with 16GB RAM, local datastore is 500GB > > The VMware log shows: > > 2016-07-16T13:54:53.033Z [2E540B70 verbose 'Default' > opID=FD806D12-00000AB5 user=root] AdapterServer: > target='vim.DiagnosticManager:ha-diagnosticmgr', method='browse' > 2016-07-16T13:54:53.051Z [2E880B70 verbose 'Default' > opID=FD806D12-00000AB6 user=root] AdapterServer: > target='vmodl.query.PropertyCollector:ha-property-collector', > method='waitForUpdates' > 2016-07-16T13:54:53.099Z [2E540B70 verbose 'Default' > opID=FD806D12-00000AB7 user=root] AdapterServer: > target='vim.DiagnosticManager:ha-diagnosticmgr', method='browse' > 2016-07-16T13:54:53.148Z [2E880B70 verbose 'Default' > opID=FD806D12-00000AB8 user=root] AdapterServer: > target='vim.DiagnosticManager:ha-diagnosticmgr', method='browse' > 2016-07-16T13:54:53.187Z [2D880B70 info 'Libs'] VmdbPipeStreamsOvlError > Couldn't read: OVL_STATUS_EOF, (11) Resource temporarily unavailable. > 2016-07-16T13:54:53.188Z [2D880B70 info 'Libs'] VigorClientCnxDemux: > VmdbCnx failed: Lost a connection to the running VMX instance. > 2016-07-16T13:54:53.188Z [2D880B70 info 'Libs'] VigorClientDisconnect: > disconnect /vm/#fc0e47d014a3b93c/ via /db/connection/#35/ > 2016-07-16T13:54:53.188Z [2D880B70 info 'Libs'] VmdbCnxDisconnect: > Disconnect: closed pipe for sub cnx '/db/connection/#35/' (-32) > 2016-07-16T13:54:53.188Z [2D880B70 info > 'vm:/vmfs/volumes/5786139d-4f1678da-1498-001ec9d2ac15/vcl-running/win7base_4-v0/win7base_4-v0.vmx'] > Unmounting VM begun. > 2016-07-16T13:54:53.188Z [2D880B70 verbose > 'Vmsvc.vm:/vmfs/volumes/5786139d-4f1678da-1498-001ec9d2ac15/vcl-running/win7base_4-v0/win7base_4-v0.vmx'] > Vigor client state callback 4 error Lost a connection to the running VMX > instance. > 2016-07-16T13:54:53.189Z [2D880B70 info 'Libs'] VMDB unmount initiated for > /vm/#fc0e47d014a3b93c/. > 2016-07-16T13:54:53.190Z [2D880B70 info 'Libs'] VigorClientUnmountCb: > Mount state values have changed for /vm/#fc0e47d014a3b93c/. > 2016-07-16T13:54:53.190Z [2D880B70 info 'Libs'] VmdbDbRemoveCnx: Removing > Cnx from Db for '/db/connection/#35/' > 2016-07-16T13:54:53.191Z [2D880B70 info 'Libs'] VigorClientUnmountCb unset > Vigor path on vm unmount. > 2016-07-16T13:54:53.191Z [2D880B70 info 'Libs'] VigorClientUnmountCb: > Unmount complete for /vm/#fc0e47d014a3b93c/. > 2016-07-16T13:54:53.191Z [2D880B70 info > 'vm:/vmfs/volumes/5786139d-4f1678da-1498-001ec9d2ac15/vcl-running/win7base_4-v0/win7base_4-v0.vmx'] > Reloading config state. > 2016-07-16T13:54:53.191Z [2D880B70 info > 'vm:/vmfs/volumes/5786139d-4f1678da-1498-001ec9d2ac15/vcl-running/win7base_4-v0/win7base_4-v0.vmx'] > Unmounting VM complete. > 2016-07-16T13:54:53.238Z [2E880B70 verbose 'Default' > opID=FD806D12-00000AB9 user=root] AdapterServer: > target='vim.DiagnosticManager:ha-diagnosticmgr', method='browse' > 2016-07-16T13:54:53.290Z [2D140B70 verbose 'Default' > opID=FD806D12-00000ABA user=root] AdapterServer: > target='vim.DiagnosticManager:ha-diagnosticmgr', method='browse' > 2016-07-16T13:54:53.315Z [2D880B70 info 'Libs'] VMHS: Transitioned > vmx/execState/val to poweredOff > 2016-07-16T13:54:53.336Z [2E540B70 info > 'Vmsvc.vm:/vmfs/volumes/5786139d-4f1678da-1498-001ec9d2ac15/vcl-running/win7base_4-v0/win7base_4-v0.vmx'] > Upgrade is required for virtual machine, version: 8 > 2016-07-16T13:54:53.355Z [2D880B70 info 'vm:Vix: [34368 > foundryVM.c:11404]: FoundryVMMountStateChangeCallback: remount complete, > set flag, VM = > /vmfs/volumes/5786139d-4f1678da-1498-001ec9d2ac15/vcl-running/win7base_4-v0/win7base_4-v0.vmx'] > 2016-07-16T13:54:53.355Z [2D880B70 info > 'Vmsvc.vm:/vmfs/volumes/5786139d-4f1678da-1498-001ec9d2ac15/vcl-running/win7base_4-v0/win7base_4-v0.vmx'] > Power On failed: vim.fault.GenericVmConfigFault > 2016-07-16T13:54:53.355Z [2D880B70 verbose > 'Vmsvc.vm:/vmfs/volumes/5786139d-4f1678da-1498-001ec9d2ac15/vcl-running/win7base_4-v0/win7base_4-v0.vmx'] > Power On message: Failed to start the virtual machine. > 2016-07-16T13:54:53.355Z [2D880B70 verbose > 'Vmsvc.vm:/vmfs/volumes/5786139d-4f1678da-1498-001ec9d2ac15/vcl-running/win7base_4-v0/win7base_4-v0.vmx'] > Power On translated error to vim.fault.GenericVmConfigFault > 2016-07-16T13:54:53.355Z [2D880B70 verbose > 'Vmsvc.vm:/vmfs/volumes/5786139d-4f1678da-1498-001ec9d2ac15/vcl-running/win7base_4-v0/win7base_4-v0.vmx'] > Vigor client state callback 0 error Lost a connection to the running VMX > instance. > 2016-07-16T13:54:53.355Z [2E540B70 info 'Hostsvc'] Decremented SIOC > Injector Flag2 > 2016-07-16T13:54:53.355Z [2E540B70 warning > 'Vmsvc.vm:/vmfs/volumes/5786139d-4f1678da-1498-001ec9d2ac15/vcl-running/win7base_4-v0/win7base_4-v0.vmx'] > Failed operation > 2016-07-16T13:54:53.378Z [2D880B70 info 'vm:Vix: [34368 > foundryVMPowerOps.c:980]: FoundryVMPowerStateChangeCallback: > /vmfs/volumes/5786139d-4f1678da-1498-001ec9d2ac15/vcl-running/win7base_4-v0/win7base_4-v0.vmx'] > vmx/execState/val = poweredOff. > 2016-07-16T13:54:53.378Z [2E241B70 verbose > 'Vmsvc.vm:/vmfs/volumes/5786139d-4f1678da-1498-001ec9d2ac15/vcl-running/win7base_4-v0/win7base_4-v0.vmx'] > VM is not online; not registering notification for Bootsrap > 2016-07-16T13:54:53.378Z [2E540B70 info 'Vimsvc.ha-eventmgr'] Event 183 : > Cannot power on win7base:vmwarewin7-win7base4-v0 (shared) on host1 in > ha-datacenter. A general system error occurred: > 2016-07-16T13:54:53.378Z [2E540B70 info > 'Vmsvc.vm:/vmfs/volumes/5786139d-4f1678da-1498-001ec9d2ac15/vcl-running/win7base_4-v0/win7base_4-v0.vmx'] > State Transition (VM_STATE_POWERING_ON -> VM_STATE_OFF) > 2016-07-16T13:54:53.378Z [2E540B70 verbose 'Hostsvc.HaHost'] ModeMgr::End: > op = normal, current = normal, count = 1 > 2016-07-16T13:54:53.387Z [2E241B70 verbose 'Hbrsvc'] Replicator: > ReconfigListener triggered for config VM 4 > 2016-07-16T13:54:53.387Z [2E540B70 info 'Hostsvc'] Lookupvm: World ID not > set for VM 4 > 2016-07-16T13:54:53.387Z [2E540B70 verbose > 'Vmsvc.vm:/vmfs/volumes/5786139d-4f1678da-1498-001ec9d2ac15/vcl-running/win7base_4-v0/win7base_4-v0.vmx'] > Time to gather config: 8 (msecs) > 2016-07-16T13:54:53.388Z [2E540B70 info 'Vimsvc.TaskManager'] Task > Completed : haTask-4-vim.VirtualMachine.powerOn-447828994 Status error > 2016-07-16T13:54:53.389Z [2E241B70 verbose 'Hbrsvc'] Replicator: > VmReconfig ignoring VM 4 not configured for replication > > Attached also is my vcld log, host profile etc. > > I will appreciate any help you can give, and thanks in advance. > > > > > > > >
