[libvirt-users] cannot acquire state change lock
by Julian Robbins
Hi
I keep getting libvirtError: Timed out during operation: cannot acquire
state change lock
errors - what does this mean exactly ?
Using Ubuntu 64 bit 10.04 host and guest
--
Kind regards
Julian Robbins
14 years, 6 months
[libvirt-users] libvirt API hangs
by Zhang Qian
Hi,
I have someVMs in my KVM hosts(RHEL 5.5), I found when run "virsh save
<domain> <file>" to save a VM, the command "virsh dominfo <domain>" will
hang until the save command finishes.
Is this libvirt's behavior? Or KVM/QEMU's? This may impact the performance.
Thanks,
Qian
14 years, 6 months
[libvirt-users] Bridge with macvtap problem
by Eduardo
Hi friends!
I'm using libvirt 0.8.1 with qemu-kvm 0.12.4 on Linux 2.6.34. At the
moment there are 2 virtual machines running inside that host without
problem. They are using the macvtap feature for networking share. But I
can't do ping from the host to the guest, but I need this. And whatever
communication between them. Ping with other host is normal. Below
follows the xml domain definition of one guest:
<domain type='kvm' id='2'>
<name>vox2</name>
<uuid>2e143f6e-5506-8073-c5fc-3ea92fc2b579</uuid>
<memory>524288</memory>
<currentMemory>524288</currentMemory>
<vcpu>2</vcpu>
<os>
<type arch='x86_64' machine='pc-0.12'>hvm</type>
<boot dev='hd'/>
</os>
<features>
<acpi/>
</features>
<clock offset='utc'/>
<on_poweroff>destroy</on_poweroff>
<on_reboot>restart</on_reboot>
<on_crash>destroy</on_crash>
<devices>
<emulator>/usr/bin/qemu-system-x86_64</emulator>
<disk type='file' device='disk'>
<source file='/virtual/vox2.qcow2'/>
<target dev='sda' bus='scsi'/>
<alias name='scsi0-0-0'/>
<address type='drive' controller='0' bus='0' unit='0'/>
</disk>
<controller type='scsi' index='0'>
<alias name='scsi0'/>
<address type='pci' domain='0x0000' bus='0x00' slot='0x04' function='0x0'/>
</controller>
<interface type='direct'>
<mac address='52:54:00:2f:fe:3d'/>
<source dev='eth0' mode='bridge'/>
<target dev='macvtap1'/>
<model type='virtio'/>
<alias name='net0'/>
<address type='pci' domain='0x0000' bus='0x00' slot='0x05' function='0x0'/>
</interface>
<input type='mouse' bus='ps2'/>
<graphics type='vnc' port='5901' autoport='no' keymap='pt-br'/>
<video>
<model type='vmvga' vram='9216' heads='1'/>
<alias name='video0'/>
<address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0'/>
</video>
</devices>
</domain>
P.S.: The default network of libvirt is disabled.
--
*Eduardo Ramos*
Asterisk Manager
Linux User
www.freedominterface.org
+55 12 81129581
exten=>eduardo,1,hangup()
14 years, 6 months
[libvirt-users] apparmor and kvm/libvirt
by Julian Robbins
Hi
After kindly answering my question on snapshots not working whilst vm is
on, i find that apparmor is still disturbing the process where snapshots
can get written
But although i should just be able to disable apparmor for my vm in
virt-manager, whilst vm is off; that when i start the vm the apparmor
settings go back to being enabled and set to dynamic
This is stopping me from taking snapshots again whilst vm is on. :-(
I have also tried disabling the apparmor profile for libvirt on the host
but this appears to have had no effect. I know very little about appamor
and it is not particularly important to be used in this case.
I am using Ubuntu 10.04 LTS on both host and guest 64 bit.
--
Kind regards
Julian Robbins
14 years, 6 months
[libvirt-users] SCM_RIGHTS file error when attaching device?
by steven765＠yahoo.com
So I just upgraded to 0.8.1-1 and virt-manager 8.4 when i try to attach my network card that's been perfectly fine in the past i now get...
virsh # attach-device gnome /etc/libvirt/qemu/nic.xml
error: Failed to attach device from /etc/libvirt/qemu/nic.xml
error: internal error unable to send TAP file handle: No file descriptor supplied via SCM_RIGHTS
Any thoughts?
14 years, 6 months
[libvirt-users] How to configure kvm development environment
by Avdhoot Joshi
Hi,
Installed RHEL 5.5 on AMD Opteron.
[root@wlng-ppcore-nd3 ~]# uname -a
Linux wlng-ppcore-nd3 2.6.18-194.el5 #1 SMP Tue Mar 16 21:52:39 EDT 2010
x86_64 x86_64 x86_64 GNU/Linux
[root@wlng-ppcore-nd3 ~]# virsh version
Compiled against library: libvir 0.6.3
Using library: libvir 0.6.3
Using API: QEMU 0.6.3
Running hypervisor: QEMU 0.9.1
This is the default version of virsh using libvirt 0.6.3.
Downloaded libvirt 0.8.1, configured it as follows:
$ configure
$ make
$ make install
What should be done so that virsh uses the latest 0.8.1 libvirtd binary, how
to completely stop 0.6.3?
I want to execute a program using virDomainMemoryStats which is available
only in latest libvirtd.
Thanks,
Avdhoot
14 years, 6 months
Re: [libvirt-users] Problems moving qemu machine to libvirt
by Gunnar Thielebein
Hi Erik,
thanks for the solution provided.
I tried that but unfortunately it spits out this error message:
> Traceback (most recent call last):
> File "/usr/share/virt-manager/virtManager/engine.py", line 588, in run_domain
> vm.startup()
> File "/usr/share/virt-manager/virtManager/domain.py", line 150, in startup
> self._backend.create()
> File "/usr/lib/python2.6/dist-packages/libvirt.py", line 300, in create
> if ret == -1: raise libvirtError ('virDomainCreate() failed', dom=self)
> libvirtError: internal error cannot parse QEMU version number in ''
Looks to me that libvirt does some version checks with the emulator-node and
don't get reliable output.
The wrapper script:
/etc/libvirt/kvmvde:
> #!/bin/bash
> exec /usr/bin/kvm "$@" \
> -net nic,vlan=0,model=virtio,macaddr=52:54:61:44:21:23 \
> -net vde,vlan=0,group=libvirtd,mode=0770,sock=/var/run/vde.ctl
The xml section:
...
> <devices>
> <emulator>/etc/libvirt/kvmvde</emulator>
> <disk type='file' device='disk'>
> <source file='/var/lib/libvirt/images/vlxp01-gt/tmp7Jiyzz.qcow2'/>
> <target dev='hda' bus='ide'/>
> </disk>
...
Btw. is the bridge entry really necessary in the xml file?
I wonder if this wouldn't also work, but I am not at this step, currently:
=> http://libvirt.org/formatdomain.html#elementsNICSSlirp
"Generic ethernet connection"
> ...
> <devices>
> <interface type='ethernet'/>
> ...
> <interface type='ethernet'>
> <target dev='vnet7'/>
> <script path='/etc/qemu-ifup-mynet'/>
> </interface>
> </devices>
> ...
Perhaps this is a place to also start the vde hub?
On 10.06.2010 13:34, Erik de Castro Lopo wrote:
> #!/bin/bash
> exec /usr/bin/kvm $@ \
> -net nic,vlan=0,model=rtl8139,macaddr=52:54:61:44:21:23 \
> -net vde,vlan=0,group=vde2-net,mode=0770,sock=/var/run/kvm-vde-ctl
Any reason no to use the virtio driver?
Best,
Gunnar
14 years, 6 months
[libvirt-users] Functionality of virsh net-edit
by Arseny Klimovsky
Hi,
I am using version libvirt on debian lenny from backports repository,
version 0.7.6-1~bpo50+1, amd64.
Th functionality of "virsh net-edit" command is not very clearly
documented, and I think it should change a configuration of a running
network. But I see it doesn't.
So, I want to add new host, for example:
#I have old configuration
root@xxx:/etc/libvirt/qemu/networks# virsh net-edit default
Network default XML configuration edited.
#Here I added new line: new host definition
root@xxx:/etc/libvirt/qemu/networks# cat default.xml
#Here I see that new line
root@xxx:/etc/libvirt/qemu/networks# virsh net-dumpxml default
root@xxx:/etc/libvirt/qemu/networks# virsh net-edit default
#Here I see exactly the old network definition
Is this behaviour expected?
If yes, how to just add new host on a running network?
--
Arseny Klimovsky
14 years, 6 months
[libvirt-users] Documentation Bug: struct virSchedParameter missing value field
by Guido Winkelmann
Hi,
The libvirt documentation under
http://libvirt.org/html/libvirt-libvirt.html#virSchedParameter
fails to list the "value" member, even though that is kind of essential for
using the struct.
This is what the documentation says:
struct virSchedParameter{
charfield[VIR_DOMAIN_SCHED_FIELD_LENGTH] field : parameter name
int type : parameter type
}
This is how it looks in the actual header file:
typedef struct _virSchedParameter virSchedParameter;
struct _virSchedParameter {
char field[VIR_DOMAIN_SCHED_FIELD_LENGTH]; /* parameter name */
int type; /* parameter type */
union {
int i; /* data for integer case */
unsigned int ui; /* data for unsigned integer case */
long long int l; /* data for long long integer case */
unsigned long long int ul; /* data for unsigned long long integer
case */
double d; /* data for double case */
char b; /* data for char case */
} value; /* parameter value */
};
This one had me scratching my head for a while, because the way it is
documented, it's absolutely not clear how the struct is supposed to be used.
Only after studying the virsh source code for a while did I notice that this
struct apparently has more members than the documentation lets on...
Guido
14 years, 6 months
