Re: [libvirt-users] Renaming a LVM LV (where is vol-edit??)

2012-05-22 Thread Dax Kelson
On Tue, May 22, 2012 at 4:09 PM, Eric Blake wrote: > > Your short-term workaround may unfortunately be limited to doing things > manually with lvm commands. To help others, this is the procedure I used: 1. Stop guest 2. lvrename 3. virsh pool-refresh 4. virsh edit guestname (LVoldname -> LV

Re: [libvirt-users] Renaming a LVM LV (where is vol-edit??)

2012-05-22 Thread Eric Blake
On 05/22/2012 04:04 PM, Dax Kelson wrote: > Hello, > > I'm using a LVM storage pool. I renamed a guest and I would like to > change the LV name to match to avoid future confusion. > > How do i do this? There is no vol-edit command (fully updated RHEL6). I agree that 'vol-edit' (or even a subset

[libvirt-users] Renaming a LVM LV (where is vol-edit??)

2012-05-22 Thread Dax Kelson
Hello, I'm using a LVM storage pool. I renamed a guest and I would like to change the LV name to match to avoid future confusion. How do i do this? There is no vol-edit command (fully updated RHEL6). Thanks, Dax Kelson ___ libvirt-users mailing list l

[libvirt-users] Failed to mount devpts

2012-05-22 Thread Marco Yuen
Hi all, I've been trying to start a LXC container using libvirt, but I keep getting `Failed to mount devpts on /vservers/quantum/fs/dev/pts: Invalid argument'. I found a similar thread on the mailing list a couple months ago (https://www.redhat.com/archives/libvirt-users/2012-January/msg00052

Re: [libvirt-users] Python Libvirt Bindings

2012-05-22 Thread Martin Kletzander
On 05/22/2012 10:04 AM, Martin Kletzander wrote: [...] > I'll have a look at it and fix it if it's like this. Going through the docs, I realized I made a mistake and I've set up the keys incorrectly (I should read more slowly and twice) and the documentation is right. '*key*.pem' goes to '/etc/pki

Re: [libvirt-users] Python Libvirt Bindings

2012-05-22 Thread Martin Kletzander
On 05/21/2012 08:03 PM, Hubert Zhang wrote: > https://www.redhat.com/archives/libvirt-users/2012-May/msg5.html > > > When I run the sample code with the case of Python code for using qemu+tcp > with SASL, I always got this SASL error: > > Traceback (most recent call last): > File "esxLi