libvirt/KVM
Hi Has anyone tried Libvirt in 2.3 RC3? I've updated VCL 2.2.1 to VCL 2.3 and cannot get Libvirt working. I've made some adjustments and able to successfully capture an image, but cannot make reservation based on the image. I'm using CentOS 6.2 with KVM as VM host (yum groupinstall Virtualization 'Virtualization Client' 'Virtualization Platform' 'Virtualization Tools'). If Libvirt is working for you, could you please share your configuration (ie. VM host version and packages, VCL computer configuration, etc) ? -- Thank you, Dmitri Chebotarov Virtual Computing Lab Systems Engineer, TSD - Ent Servers & Messaging 223 Aquia Building, Ffx, MSN: 1B5 Phone: (703) 993-6175 Fax: (703) 993-3404
VCL image capture dies, "failed to prepare vmx file"
Hi, all. Trying to resurrect a thread I started on Friday, subject 'Image capture succeeds, then "fails"'. Mike Haudenschild helped me narrow down the problem but so far I haven't been able to find a cause or a fix. I'm trying to capture my first Linux VM. Things go along okay through the capture stage, but (thanks Mike) we fail when VCL tries to reserve and deploy the new image. The critical message from the log appears to be: |17491|19:19|reload| WARNING |17491|19:19|reload| 2012-06-19 14:10:22|17491|19:19|reload|VMware.pm:load(395)|failed to prepare vmx file for vcl-linux-template-2-bak on VM host: vcl0001 |17491|19:19|reload| ( 0) VMware.pm, load (line: 395) |17491|19:19|reload| (-1) new.pm, reload_image (line: 618) |17491|19:19|reload| (-2) new.pm, process (line: 248) |17491|19:19|reload| (-3) vcld, make_new_child (line: 568) |17491|19:19|reload| (-4) vcld, main (line: 346) Further down, I'll paste in a complete copy of the log mail I got from this attempt. Our VM storage settings for this VM host are: Repository Path: /vmfs/volumes/nfs-vcl-templates Data Store Path: /vmfs/volumes/T2_6045_dev_VCL_ds01 VM Path: /vmfs/volumes/T2_6045_dev_VCL_ds01 (Note Data Store and VM are explicitly the same; we've also had VM Path set to "(empty)" with no apparent difference in behavior.) Both of those paths are writable on the hypervisor. During capture, a VM directory appears in both locations. In the directory under the Repository path, we have many vmdk files, sizes ranging from 842M to 1.5k, with names like: vmwarelinux-linuxtemplate2v1226-v0-s001.vmdk vmwarelinux-linuxtemplate2v1226-v0-s002.vmdk vmwarelinux-linuxtemplate2v1226-v0-s003.vmdk [...] vmwarelinux-linuxtemplate2v1226-v0-s016.vmdk vmwarelinux-linuxtemplate2v1226-v0.vmdk My first guess is that we have one vmdk file for each attempted capture, and this is a series of xdiffs on the original? In the Data Store/VM directory, we have: # pwd /vmfs/volumes/T2_6045_dev_VCL_ds01/vmwarelinux-linuxtemplate2v1226-v0 # ls -lh -rw---1 root root 30.0G Jun 19 20:12 vmwarelinux-linuxtemplate2v1226-v0-flat.vmdk -rw---1 root root 527 Jun 19 20:12 vmwarelinux-linuxtemplate2v1226-v0.vmdk So, it seems that those locations are accessible and writable, and being written. What else might cause the vmx file prep to fail? I went to VMware.pm line 395, but that's a call to a subroutine, prepare_vmx(), which is a fairly lengthy chunk of code and doesn't appear to be dropping any breadcrumbs as it runs, only the failure message when it exits. So stepping through that without guidance is going to be a challenge. Meanwhile we've also started trying to capture a Windows image. That's dying too, but with a different set of error messages. I'll post that under separate cover. Thanks for any insight. Complete log message follows. -m reservation failed on vcl-linux-template-2-bak: process failed after trying to load or make available time: 2012-06-19 14:10:22 caller: State.pm:reservation_failed(213) ( 0) State.pm, reservation_failed (line: 213) (-1) new.pm, process (line: 298) (-2) vcld, make_new_child (line: 568) (-3) vcld, main (line: 346) management node: pilot-lab.uchicago.edu reservation PID: 17491 parent vcld PID: 2491 request ID: 19 reservation ID: 19 request state/laststate: reload/image request start time: 2012-06-19 14:10:12 request end time: 2012-06-19 14:40:12 for imaging: no log ID: none computer: vcl-linux-template-2-bak computer id: 7 computer type: virtualmachine computer eth0 MAC address: computer eth1 MAC address: computer private IP address: 10.50.84.15 computer public IP address: 10.50.84.15 computer in block allocation: no provisioning module: VCL::Module::Provisioning::VMware::VMware vm host: vcl0001 vm host ID: 1 vm host computer ID: 1 vm profile: VMware ESXi - IT Services vm profile VM path: /vmfs/volumes/T2_6045_dev_VCL_ds01 vm profile repository path: /vmfs/volumes/nfs-vcl-templates vm profile datastore path: /vmfs/volumes/T2_6045_dev_VCL_ds01 vm profile disk type: localdisk image: vmwarelinux-linuxtemplate2v1226-v0 image display name: linux-template-2v12 image ID: 26 image revision ID: 22 image size: 30720 MB use Sysprep: yes root access: yes image owner ID: 1 image owner affiliation: Local image revision date created: 2012-06-19 14:08:20 image revision production: yes OS module: VCL::Module::OS::Linux user: vclreload user name: vcl reload user ID: 2 user affiliation: Local RECENT LOG ENTRIES FOR THIS PROCESS: 2012-06-19 14:10:20|17491|19:19|reload|VMware.pm:get_image_size_bytes(3841)|retrieved the size of the image from the datastore on the VM host: 32,212,255,247 2012-06-19 14:10:20|17491|19:19|reload|VMware.pm:get_image_size_bytes
Windows capture fails
Hi List. As threatened, here's the tale of our attempt to capture our
first Windows image. As with our Linux capture, it appears that the VM
disk image is being copied into our Data and Repository paths, but
something goes wrong later in the process, but the warnings we find in
the log are different for our Windows image than for the Linux one.
As before, I'll paste the full log from the "PROBLEM" mail below, but it
looks like this is significant:
|19609|20:20|image| WARNING
|19609|20:20|image| 2012-06-19
14:36:58|19609|20:20|image|VIM_SSH.pm:initialize(112)|required VM host OS
subroutine is not implemented: execute
|19609|20:20|image| ( 0) VIM_SSH.pm, initialize (line: 112)
|19609|20:20|image| (-1) Module.pm, new (line: 207)
|19609|20:20|image| (-2) VMware.pm, (eval) (line: 1303)
|19609|20:20|image| (-3) VMware.pm, get_vmhost_api_object (line: 1303)
|19609|20:20|image| (-4) VMware.pm, initialize (line: 278)
|19609|20:20|image| (-5) Module.pm, new (line: 207)
2012-06-19
14:36:58|19609|20:20|image|VMware.pm:get_vmhost_api_object(1313)|API object
could not be created: VCL::Module::Provisioning::VMware::VIM_SSH
This looks to me like there must be something missing, maybe within the
Windows VM itself? Did we leave out a package somewhere?
Thanks,
-m
--
Michael Jinks :: mji...@uchicago.edu
University of Chicago IT Services
Complete log message follows:
VCL::image object could not be created and initialized
time: 2012-06-19 14:36:58
caller: vcld:make_new_child(571)
( 0) vcld, make_new_child (line: 571)
(-1) vcld, main (line: 346)
management node: pilot-lab.uchicago.edu
reservation PID: 19609
parent vcld PID: 2491
request ID: 20
reservation ID: 20
request state/laststate: image/image
request start time: 2012-06-19 14:36:50
request end time: 2012-06-19 15:36:50
for imaging: no
log ID: none
computer: vcl-win7-test
computer id: 8
computer type: virtualmachine
computer eth0 MAC address:
computer eth1 MAC address:
computer private IP address: 10.50.84.16
computer public IP address: 10.50.84.16
computer in block allocation: no
provisioning module: VCL::Module::Provisioning::VMware::VMware
vm host:
vm host ID:
vm host computer ID:
vm profile:
vm profile VM path:
vm profile repository path:
vm profile datastore path:
vm profile disk type:
image: vmwarewin7-win7vmimage27-v0
image display name: win7-vm-image
image ID: 27
image revision ID: 23
image size: 1450 MB
use Sysprep: no
root access: yes
image owner ID: 1
image owner affiliation: Local
image revision date created: 2012-06-19 14:36:50
image revision production: yes
OS module: VCL::Module::OS::Windows::Version_6::7
user: admin
user name: vcl admin
user ID: 1
user affiliation: Local
RECENT LOG ENTRIES FOR THIS PROCESS:
|19609|20:20|image| (-1) Autoload.pm, __ANON__ (line: 80)
|19609|20:20|image| (-2) VMware.pm, get_vmhost_datastructure (line: 1161)
|19609|20:20|image| (-3) VMware.pm, get_vmhost_api_object (line: 1282)
|19609|20:20|image| (-4) VMware.pm, initialize (line: 278)
|19609|20:20|image| (-5) Module.pm, new (line: 207)
|19609|20:20|image| WARNING
|19609|20:20|image| 2012-06-19
14:36:58|19609|20:20|image|DataStructure.pm:_automethod(812)|corresponding data
has not been initialized for get_vmhost_profile_image_id:
$self->request_data->{reservation}{20}{computer}{vmhost}{vmprofile}{imageid}
|19609|20:20|image| ( 0) DataStructure.pm, _automethod (line: 812)
|19609|20:20|image| (-1) Autoload.pm, __ANON__ (line: 80)
|19609|20:20|image| (-2) VMware.pm, get_vmhost_datastructure (line: 1162)
|19609|20:20|image| (-3) VMware.pm, get_vmhost_api_object (line: 1282)
|19609|20:20|image| (-4) VMware.pm, initialize (line: 278)
|19609|20:20|image| (-5) Module.pm, new (line: 207)
2012-06-19
14:36:58|19609|20:20|image|VMware.pm:get_vmhost_datastructure(1190)|created
DataStructure object for VM host: vcl-win7-test
2012-06-19
14:36:58|19609|20:20|image|VMware.pm:get_vmhost_api_object(1293)|attempting to
load VMware control module: VCL::Module::Provisioning::VMware::VIM_SSH
2012-06-19
14:36:58|19609|20:20|image|VMware.pm:get_vmhost_api_object(1299)|loaded VMware
control module: VCL::Module::Provisioning::VMware::VIM_SSH
2012-06-19 14:36:58|19609|20:20|image|Module.pm:new(172)|set 'vmhost_data' key
for VCL::Module::Provisioning::VMware::VIM_SSH object from arguments
2012-06-19 14:36:58|19609|20:20|image|Module.pm:new(172)|set 'vmhost_os' key
for VCL::Module::Provisioning::VMware::VIM_SSH object from arguments
2012-06-19
14:36:58|19609|20:20|image|Module.pm:create_mn_os_object(335)|management node
OS object has already been created, address: 37c3000, returning 1
2012-06-19
14:36:58|19609|20:20|image|Module.pm:new(200)|VCL::Module::Provisioning::VMware::VIM_SSH
object created for computer vcl-win7-te
