[libvirt-users] ANNOUNCE: oz0.6.0 release
by Chris Lalancette
All,
I'm pleased to announce release 0.6.0 of Oz. Oz is a program for doing
automated installation of guest operating systems with limited input from
the user.
Release 0.6.0 is a bugfix and feature release for Oz. Some of the
highlights between Oz 0.5.0 and 0.6.0 are:
- The ability to specify the destination for the ICICLE output from oz-install
and oz-generate-icicle
- pydoc class documentation for all internal Oz classes
- Automatic detection of KVM or QEMU at runtime (this allows oz to be used
within virtual machines, although with a large performance hit)
- Less scary warning messages in the debug output
- Printing of the screenshot path when a build fails
- Ability to run multiple Oz installs of the same OS at the same time
- Support for OEL and ScientificLinux
- Support for RHEL-5.7
- Support for CentOS 6
- Support for OpenSUSE arbitrary file injection and command execution
- Ability to make the TDL (template) parsing enforce a root password
- Rejection of localhost URLs for repositories (since they must be reachable
from the guest operating system, localhost URLs make no sense)
Fedora-14, Fedora-15, and RHEL-6 packages are available for this release. Note
that to install the RHEL-6 packages, you must be running RHEL-6.1 or later.
Instructions on how to get and use Oz are available at
http://aeolusproject.org/oz.html
If you have any questions or comments about Oz, please feel free to contact
aeolus-devel(a)lists.fedorahosted.org or me (clalance(a)redhat.com) directly.
Thanks to everyone who contributed to this release through bug reports,
patches, and suggestions for improvement.
--
Chris Lalancette
14 years
[libvirt-users] issue with virErrorInitialize
by Sharad Mishra
One of my team mate investigated the issue where libvirt-cim was
segfaulting when unloading providers. More info on this issue is at
https://www.redhat.com/archives/libvirt-users/2011-August/msg00069.html
Here is the gist of his investigation -
I've looked into the libvirt source code and the reason for issues with the
unload of libvirt-cim providers is there (and cimprovider -r forces an
unload,
just as cimserver shutdown does).
virConnectOpen() does call virInitialize() which then will initialize the
gcrypt library after initializes the thread setup ->virThreadInitialize(),
creates the error reporting structure ->virErrorInitialize() and initialize
a
random number generator ->virRandomInitialize().
The issue is hidden in virErrorInitialize(). It calls virErrorInitialize()
which uses the wrapper function virThreadLocalInit(&virLastErr,
virLastErrFreeData);.
virThreadLocalInit() calls pthread_create() with a destructor function
(virLastErrFreeData()) which will be called on thread exits.
Trouble here is that pthread_key_delete() is never called in libvirt, but
next
time the system runs through the key list and libvirt has been unloaded the
system will jump to an already unloaded function (the pointer were
virLastErrFreeData() was loaded formerly) and consequently crash the
process.
Fixing this will not be easy, but a start would be a libvirt function on
its
externalize interface that allows cleanup short before library unload, or
alternatively libvirt does the thread key delete on library unload.
Thanks
Sharad Mishra
Open Virtualization
Linux Technology Center
IBM
14 years
[libvirt-users] How to Connect a new CD via virt-manager
by Marc Haber
Hi,
I have virt-manager 0.9 connecting to a libvirtd 0.9.3 on Debian
unstable. Hypervisor being used is KVM.
In a VM, I can select the "IDE CDROM 1" and click on "disonnect" which
makes the virtual disk disappear from the virtual drive and the former
disconnect button now reads "connect". Hence, when I click there,
nothing happens.
Currently, the only way I am aware to get a new CD in the virtual
drive is to delete it and to add a new virtual CD drive.
Is this a bug, or am I doing things wrong?
Greetings
Marc
--
-----------------------------------------------------------------------------
Marc Haber | "I don't trust Computers. They | Mailadresse im Header
Mannheim, Germany | lose things." Winona Ryder | Fon: *49 621 72739834
Nordisch by Nature | How to make an American Quilt | Fax: *49 3221 2323190
14 years
[libvirt-users] Detaching LVM volume from Windows guest
by mkey
Hello,
I have some difficulties regarding to above title. Windows as guest OS
is running on KVM(Ubuntu natty).
After attaching LVM volume to guest OS and did "safely remove device" in
guest windows, detaching volume was failed.
> root@localhost:/opt/win# virsh detach-disk testwin vdc
> error: Failed to detach disk
> errpr: operation failed: detaching virtio-disk2 device failed: Device
'virtio-disk2' not found
But kvm(qemu?) seems like detaching device successfully.
> root@localhost:/opt/win# virsh qemu-monitor-command testwin 'info block'
> drive-virtio-disk0: type=hd removable=0
file=/opt/win/win2008server.virtio.img ro=0 drv=qcow2 encrypted=0
So, problem is, libvirt doesn't know detaching, but kvm(qemu) knows.
Again, please let me know if anybody has workaround.
P.S. at some website, I found "hotunplugging is not supported in current
libvirt", is that related on this matter?
Regards,
mkey
14 years
[libvirt-users] Detaching LVM volume from Windows guest
by mkey
Hello,
I have some difficulties regarding to above title. Windows as guest OS
is running on KVM(Ubuntu natty).
After attaching LVM volume to guest OS and did "safely remove device" in
guest windows, detaching volume was failed.
> root@localhost:/opt/win# virsh detach-disk testwin vdc
> error: Failed to detach disk
> errpr: operation failed: detaching virtio-disk2 device failed: Device
'virtio-disk2' not found
But kvm(qemu?) seems like detaching device successfully.
> root@localhost:/opt/win# virsh qemu-monitor-command testwin 'info block'
> drive-virtio-disk0: type=hd removable=0
file=/opt/win/win2008server.virtio.img ro=0 drv=qcow2 encrypted=0
So, problem is, libvirt doesn't know detaching, but kvm(qemu) knows.
Again, please let me know if anybody has workaround.
P.S. at some website, I found "hotunplugging is not supported in current
libvirt", is that related on this matter?
Regards,
mkey
14 years
[libvirt-users] build libvirt from source yourself and make sure to get the XenAPI driver enabled.
by Lovocas Mou
Hi,
I want install libvirt on my ubuntu11.04, and I want to test using
libvirt to manage a xenserver,
after download the tar and extract them
when in this step : ./configure --with-esx --with-xenapi
--prefix=/opt/libvirt
....
checking for xen_vm_start in -lxenserver... no
configure: error: You must install the XenServer Library to compile XenAPI
driver with -lxenserver
.....
I get this error, but i get very few information about it from google.
>>libvirt can use XenAPI via libxenserver [1]. That should allow you to
>> use libvirt with a Citrix XenServer. You can use virsh like this
>> assuming you have a libxenserver enabled libvirt:
>>
>> virsh -c xenapi://my-xen-server
>>
>> But it's true, there is no documentation about this on the libvirt website
>> yet.
>>
>> [1] http://community.citrix.com/display/xs/Download+SDKs
I download the libxenserver source and binary file from the above url, but I
don't know how to install it and how to use -lxenserver,
can anyone help me?
thanks!
14 years
[libvirt-users] which vols added to storage pool during refresh?
by Gareth S Bestor
(opps, actually meant to post this to libvirt-users instead of
libvirt-cim...)
We're looking at a problem when we have a libvirt pool defined, below
[root@xnl2192 ~]# virsh pool-dumpxml ScsiPool-host2
<pool type='scsi'>
<name>ScsiPool-host2</name>
<uuid>f2ea1882-881f-9f49-838d-39e070f68002</uuid>
<capacity>136583315456</capacity>
<allocation>136583315456</allocation>
<available>0</available>
<source>
<adapter name='host2'/>
</source>
<target>
<path>/dev/disk/by-id</path>
<permissions>
<mode>0700</mode>
<owner>-1</owner>
<group>-1</group>
</permissions>
</target>
</pool>
As you can see, this pool maps to /dev/disk/by-id. There may be a large
number of actual volume entries in /dev/disk/by-id, however it appears
only a distinct subset of them are actually added into the libvirt pool
when you do a pool-refresh. What does libvirt check when determining
which, and whether or not, to add one of these volume into the vol-list?
In particular, we have a case when one specific volume in /dev/disk/by-id
is *not* added into the pool, and no amount of pool-refresh makes a
difference. We did notice that if you remove all the sym links in
/dev/disk/by-id and do a pool-refresh, that libvirt re-scans the bus,
recreates the links in /dev/disk/by-id, and adds (some of) the volumes
back into the vol-list. But not this one problematic vol, so clearly there
is something about this vol that libvirt doesnt like and why it is
(deliberately?) not added to the pool.
What checks, etc does libvirt make against vols when determining whether
to add them to a pool?
- G
Dr. Gareth S. Bestor
IBM Senior Software Engineer
Systems & Technology Group - Systems Management Standards
971-285-6375 (mobile)
bestor(a)us.ibm.com_______________________________________________
Libvirt-cim mailing list
Libvirt-cim(a)redhat.com
https://www.redhat.com/mailman/listinfo/libvirt-cim
14 years
Re: [libvirt-users] Migration hangs on Gentoo with KVM
by Eric Blake
[re-adding the list]
On 08/01/2011 04:22 PM, Jonathan Stoppani wrote:
>
> On Aug 1, 2011, at 16:20 , Eric Blake wrote:
>
>> On 08/01/2011 04:11 PM, Jonathan Stoppani wrote:
>>> Hi there,
>>>
>>> I'm trying to migrate a domain between two Gentoo hosts using KVM as hypervisor, but the migration hangs.
>>> I tried both live or offline migration modes without success.
>>
>> Does your 'nc' command have a -q option? If so, then this is probably
>>
>> https://bugzilla.redhat.com/show_bug.cgi?id=726174
>>
>
> Thanks for the prompt answer Eric! Yes, nc has a q option:
>
> -q, --hold-timeout=SEC1[:SEC2] Set hold timeout(s) for local [and remote]
Glad to hear that we found root cause to your problems, then.
>
> The bug specifically refers to ssh, does that mean that it should work over tcp?
The problem is that libvirt is trying to start a remote nc session over
ssh; but looking at http://libvirt.org/remote.html, it looks like ssh is
the only protocol using nc in that manner (so yes, you can probably
avoid the issue by using tcp or tls). Meanwhile, I think you can work
around it without patching libvirt, by using this as your remote URI:
qemu+ssh://user@remotehost/system?netcat=/path/to/nc-wrapper
where nc-wrapper is an executable script installed on remotehost,
looking like:
#!/bin/sh
exec /path/to/real/nc -q0 "$@"
--
Eric Blake eblake(a)redhat.com +1-801-349-2682
Libvirt virtualization library http://libvirt.org
14 years
