Thanks,
I ran into another issue; vms were NOT being destroyed before new ones were
reloaded, causing vms to pileup on the host.
If found problems on our setup in libvirt.pm;
Issue #1;
The statement "next if ($domain_name !~ /^$computer_name:/);" in sub
delete_existing_domains didn't work for me. I had to replace it with "if
($domain_name =~ $computer_name) {" ..."}" (this might have risks involved, if
the image has $domain_name in it name).
Issue #2
Then I had to ADD a bunch of "$domain_name =~ s/^\s+|\s+$//g;" where virsh was
being called. This was required because $domain_name had leading spaces which
would make virsh fail.
Again, I think most of those issues are caused by us using older version of
libvirt and qemu/KVM.
Existing vms are now destroyed before loading new ones in their slot.
Cheers
Yanik
________________________________________
To: [email protected]; [email protected]
Subject: RE: libvirt qemu-img
Thanks,
I ran into another issue; vms were NOT being destroyed before new ones were
reloaded, causing vms to pileup on the host.
If found roblems on my setup in libvirt.pm;
Issue #1;
The statement
-----Original Message-----
From: Aaron Peeler [mailto:[email protected]]
Sent: Monday, November 12, 2012 7:21 AM
To: [email protected]
Subject: Re: libvirt qemu-img
We are using Fedora 16.
Aaron
On Fri, Nov 9, 2012 at 3:39 PM, Waldron, Michael H <[email protected]>
wrote:
> I have run into the same issues in experimenting with libvirt on our
> VCL 2.3 test system. I would also be interested to hear how others are
> doing it. I'm also using CentOS 6.
>
>
> Mike Waldron
> Systems Specialist
> ITS - Research Computing Center
> University of North Carolina at Chapel Hill
>
> ________________________________
> From: Yannick Charbonneau [[email protected]]
> Sent: Friday, November 09, 2012 2:51 PM
> To: '[email protected]'
> Subject: RE: libvirt qemu-img
>
> I think I figured it out…
>
>
>
> It appears the qemu-img distributed with CentOS 6 is old and doesn’t
> support multi file .vmdks convert.
>
>
>
> I recompiled the latest version and it copied/converted the .vmdks properly.
>
>
>
> I am now facing a problem with libguestfs, NOT recognizing the OS
> inside the .qcow2. Again, I think this is due to older release of libguestfs.
>
>
>
> What distro are you guys using for libvirt hosts?
>
>
>
> From: Yannick Charbonneau [mailto:[email protected]]
> Sent: Thursday, November 08, 2012 9:47 PM
> To: <[email protected]>
> Subject: libvirt qemu-img
>
>
>
> Hi All,
>
>
>
> We have a vorking vcl 2.3 + esxi setup working.
>
>
>
> We are now trying out a libvirt host. We have the host up but we are
> having issues deploying our vmare images on it.
>
>
>
> It appears be related with multiple files .vmdks disks and qemu-img convert.
> The resulting qcow2 file is way too small, and the vm fails to boot
> saying disk is NOT bootable.
>
>
>
> If I take a -flat.vmdk image and convert it, I can boot the vm
> manually in virt-manager.
>
>
>
> Anybody has seen this?
>
>
>
> Thanks
>
>
>
> Yanik
--
Aaron Peeler
Program Manager
Virtual Computing Lab
NC State University
All electronic mail messages in connection with State business which are sent
to or received by this account are subject to the NC Public Records Law and may
be disclosed to third parties.
