- Users - libvirt List Archives

[libvirt-users] bridge could not be initialized
by abhishek jain 19 Jun '14

19 Jun '14

Hi I'm trying to run VM using libvirt.xml file and getting following error... virsh start instance-00000003 error: Failed to start domain instance-00000003 error: internal error Process exited while reading console log output: failed to launch bridge helper kvm: -netdev bridge,br=qbr1f2191ce-38,id=hostnet0: Device 'bridge' could not be initialized Below is the libvirt.xml file.. domain type="kvm"> <uuid>d9f007b9-584f-41c8-a706-e096f354575b</uuid> <name>instance-00000003</name> <memory>524288</memory> <vcpu>1</vcpu> <os> <type>hvm</type> <kernel>/opt/stack/data/nova/instances/d9f007b9-584f-41c8-a706-e096f354575b/kernel</kernel> <initrd>/opt/stack/data/nova/instances/d9f007b9-584f-41c8-a706-e096f354575b/ramdisk</initrd> <cmdline>root=/dev/vda console=tty0 console=ttyS0</cmdline> </os> <features> <acpi/> <apic/> </features> <clock offset="utc"> <timer name="pit" tickpolicy="delay"/> <timer name="rtc" tickpolicy="catchup"/> </clock> <devices> <disk type="file" device="disk"> <driver name="qemu" type="qcow2" cache="none"/> <source file="/opt/stack/data/nova/instances/d9f007b9-584f-41c8-a706-e096f354575b/disk"/> <target bus="virtio" dev="vda"/> </disk> <interface type="bridge"> <mac address="fa:16:3e:26:55:ff"/> <model type="virtio"/> <source bridge="qbr1f2191ce-38"/> <target dev="tap1f2191ce-38"/> <filterref filter="nova-instance-instance-00000003-fa163e2655ff"/> </interface> <serial type="file"> <source path="/opt/stack/data/nova/instances/d9f007b9-584f-41c8-a706-e096f354575b/console.log"/> </serial> <serial type="pty"/> </devices> </domain> Please help regarding this. Thanks Abhishek Jain

3 2

[libvirt-users] dumpxml removes <source> portion from network descritiption
by Thomas Stein 19 Jun '14

19 Jun '14

Hello. I have a strange error with one of my VMs. If i use dumpxml to save a VM description the source part of the network part is missing. This prevents redifining the machine from the dumped xml file: This is how it looks before dumpxml: <interface type='bridge'> <mac address='52:54:00:34:a1:56'/> <source bridge='br406'/> <model type='virtio'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/> </interface> And afterwards: <interface type='bridge'> <mac address='52:54:00:34:a1:56'/> <target dev='vnet6'/> <model type='virtio'/> <alias name='net0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/> </interface> Someone has an idea whats causing this? Is there a special option maybe? thanks and best regards t.

2 2

[libvirt-users] Use keepalive to monitor health of qemu-kvm process
by Abhijeet Rastogi 19 Jun '14

19 Jun '14

Hi everyone, I've had instances where qemu-kvm process dies and become a zombie. At that state, libvirtd reports the instance to be running and I can't restart the VM because libvirtd fails to kill the qemu-kvm process. Finding the root cause of that is a topic for another day. I also see this line in logs: Jun 15 13:36:57 d12566 libvirtd: 10424: warning : virKeepAliveTimerInternal:156 : No response from client 0x1600420 after 5 keepalive messages in 31 seconds Is it possible to monitor the keepAlive thing via command-line ? (as a nagios check). I know that I can poll for that line in the logs but is there a better way? I couldn't find any option in virsh to do a KeepAlive check. Thanks -- Cheers, Abhijeet Rastogi (shadyabhi)

1 0

[libvirt-users] Live migrate failure
by Tuân Tạ Bá 18 Jun '14

18 Jun '14

Hi everyone, I use KVM on Openstack Cloud. And KVM migrated successfull, but not ping. *Source Host SIDE: *"/var/log/libvirt/libvirtd.log" 2014-06-16 05:15:50.599+0000: 2096: warning : qemuMigrationCancelDriveMirror:1383 : Unable to stop block job on drive-virtio-disk0 2014-06-16 05:15:50.601+0000: 2096: *warning : qemuMigrationCancelDriveMirror:1383 : Unable to stop block job on drive-virtio-disk1* *2014-06-16 05:15:50.651+0000: 2096: error : virCommandWait:2348 : internal error: Child process (ovs-vsctl --timeout=5 get Interface tap6977e4a1-cd external_ids:PortData) unexpected exit status 1: ovs-vsctl: no key "PortData" in Interface record "tap6977e4a1-cd" column external_ids* 2014-06-16 05:15:50.651+0000: 2096: error : virNetDevOpenvswitchGetMigrateData:219 : Unable to run command to get OVS port data for interface tap6977e4a1-cd: Operation not permitted 2014-06-16 05:15:50.651+0000: 2096: error : qemuMigrationCookieNetworkAlloc:367 : Unable to run command to get OVS port data for interface tap6977e4a1-cd: Operation not permitted 2014-06-16 05:15:50.651+0000: 2096: warning : qemuMigrationRun:3262 : Unable to encode migration cookie 2014-06-16 05:15:53.321+0000: 2096: warning : virAuditSend:135 : Failed to send audit message virt=kvm op=stop reason=migrated vm="instance-0001b37c" uuid=631ac4c7-8e84-4cf6-ad98-93877cdbe1bd vm-pid=-1: Operation not permitted *Destination Host SIDE:* "/var/log/libvirt/libvirtd.log" ...... 2014-06-16 05:15:41.419+0000: 2229: warning : virAuditSend:135 : Failed to send audit message virt=kvm resrc=cgroup reason=allow vm="instance-000 1b37c" uuid=631ac4c7-8e84-4cf6-ad98-93877cdbe1bd cgroup="/sys/fs/cgroup/devices/machine/instance-0001b37c.libvirt-qemu/" class=major category=pty maj=88 acl=rw: Operation not permitted 2014-06-16 05:15:41.620+0000: 2229: warning : qemuDomainObjEnterMonitorInternal:1175 : This thread seems to be the async job owner; entering moni tor without asking for a nested job is dangerous 2014-06-16 05:15:43.552+0000: 2229: warning : virAuditSend:135 : Failed to send audit message virt=kvm resrc=vcpu reason=start vm="instance-0001b 37c" uuid=631ac4c7-8e84-4cf6-ad98-93877cdbe1bd old-vcpu=0 new-vcpu=2: Operation not permitted 2014-06-16 05:15:43.552+0000: 2229: warning : virAuditSend:135 :* Failed to send audit message *virt=kvm op=start reason=migrated vm="instance-0001 b37c" uuid=631ac4c7-8e84-4cf6-ad98-93877cdbe1bd vm-pid=21063:* Operation not permitted* 1) I'm using libvirt version 1.1.1, libvirt-bin 1.1.1-0ubuntu8.5~cloud0 libvirt0 1.1.1-0ubuntu8.5~cloud0 python-libvirt 1.1.1-0ubuntu8.5~cloud0 2) #cat /etc/libvirt/qemu.conf ... user = "root" group = "root" I searched GOOGLE, René speaks "downgrading to libvirt 1.1.0 and reinstalling everything. They will ok". But I don't think that. How to resolve this error?. Thanks all! -- TuanTaBa

2 2

[libvirt-users] Libvirt 1.2.5/Qemu woes
by andy zerger 16 Jun '14

16 Jun '14

Hi all - I'm dealing with a libvirt 1.2.5 and Qemu-1.7.1 also Qemu-2.0 (all source compile,) which somehow isn't seeing any hypervisors when connected to via virt-manager. I'm sure I must be doing something wrong but cannot figure out what. My basic config and current state here in pastebin: http://pastebin.com/m5M8PfFC Thanks for any input, this has been baffling. Best Regards, Andy

2 2

[libvirt-users] Fedora 19/20 new install :Unable to create vcpu cgroup
by Patrick Chemla 16 Jun '14

16 Jun '14

Hi, After full new install of Fedora 19 or 20, I am getting this when I want to create a new VMs. Impossible de terminer l'installation : « Unable to create vcpu cgroup for fedora20(vcpu: 0): Aucun fichier ou dossier de ce type » Traceback (most recent call last): File "/usr/share/virt-manager/virtManager/asyncjob.py", line 91, in cb_wrapper callback(asyncjob, *args, **kwargs) File "/usr/share/virt-manager/virtManager/create.py", line 1787, in do_install guest.start_install(meter=meter) File "/usr/share/virt-manager/virtinst/guest.py", line 403, in start_install noboot) File "/usr/share/virt-manager/virtinst/guest.py", line 467, in _create_guest dom = self.conn.createLinux(start_xml or final_xml, 0) File "/usr/lib64/python2.7/site-packages/libvirt.py", line 2897, in createLinux if ret is None:raise libvirtError('virDomainCreateLinux() failed', conn=self) libvirtError: Unable to create vcpu cgroup for fedora20(vcpu: 0): Aucun fichier ou dossier de ce type I saw that there is no cpu mounted, only cpuacct. I saw on other server that cpu is a link to cpu,cpuacct But I can't find how to add this in a config file Thanks for help Patrick

2 12

[libvirt-users] libvirt issue while deploying a VM
by Zvi Dubitzky 16 Jun '14

16 Jun '14

Using libvirt under openstack I encounter a problem when launching a VM with multiple partitions (2 G image) , While a single partition can be launched successfully . The launch is done with Openstack. We are using in libvirtd.conf log_level=1 and log_outputs="1:file:/var/log/libvirt/libvirtd.log" we can see that in /var/log/libvirt/libvirtd.log appear the following error message and the VM is finally shutdown : 2014-06-11 14:47:26.166+0000: 12971: error : qemuMonitorIO:614 : internal error End of file from monitor ( file attached below) ( VM shutdown seen here) The host has enough resources( we see no complains) and the XML of the VM is : The libvirt version is: 0.10.2 The qemu-kvm version: 0.12.1.2 >From the internet we could not figure out a solution to the problem Any idea what is causing this error and how to overcome ? Thx Zvi Dubitzky Email:dubi@il.ibm.com

2 3

[libvirt-users] libvirt, openSUSE, SuSeFirewall2 and port forwarding
by Johannes Kastl 14 Jun '14

14 Jun '14

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello list, I thought I had already asked this question, but apparently I just started writing a draft mail and never sent it (at least I can't find it in the archives). Has anyone setup qemu VMs using libvirt on openSUSE, and has gotten port forwarding to work? I used on of the many scripts out there, that go into /etc/libvirt/hooks/qemu, and it is being called. Somehow it seems once in a while SuSefirewall2 just forgets about iptable rules set with this script. And sometimes they don't appear, even if the script is executed. Anyone else having the same issues? Any openSUSE users willing to try this? Thanks in advance! Regards, Johannes - -- What do Bud Light and sex in a canoe have in common? Both is fuckin' close to water. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) Comment: Using GnuPG with SeaMonkey - http://www.enigmail.net/ iEYEARECAAYFAlOcmAAACgkQzi3gQ/xETbJRwwCfZe3YKXfQG7O0aHFDvD6EwXus a/8An36n1L/pAWSTuue3w0GG2ovAsw07 =aLj5 -----END PGP SIGNATURE-----

1 0

[libvirt-users] Status of Host machine.
by Sijo Jose 13 Jun '14

13 Jun '14

Hi, Using libvirt how can we check the status of a remote/local host machine.. isAlive() method is giving true even if the internet connection is broken OR libvirt demon in the remote machine is being stopped. so isAlive() does not seems to be handy, Is there some other way to get the status of remote host..? Thanks -Sijo

2 3

[libvirt-users] about sharing the hugepage memory segment between the host and the container
by WANG Cheng D 12 Jun '14

12 Jun '14

Dear all, What I want to do is to share a hugepage memory segment between the host and a container (I am trying to use intel DPDK package in container). For a normal memory (4k page), the memory sharing can be achieved by memory-mapped I/O (mmap())method with the same disk file on the host exposed to the container (that is, the host and the container share the same disk file). my questions are: 1) Do I need to mount the hugetlbfs in host and container respectively? 2) According to my understanding, the exposed file that will be shared by the host and container must locate at the hugetlbfs mount point. Is this right? 3) According to my understanding, the mount point in the host doesn't necessarily to be the same as that of the container, as long as the mount point is exposed to the container, Is this right? 4) If I want to share the hugepage memory segment betwen two containers, what's the answers for 1) ? 5) According to my internet research, if use open() to open a file under the hugepage mount point, the mmap() will automatically return a pointer to the hugepage memory segment. Is this right? Apart from this, I cannot see other difference from memory-mapped I/O with the 4k page memory. Any answer will be highly appreciated. Cheng Wang

1 0