- Users - libvirt List Archives

[libvirt-users] Put virbr0 in promiscusous
by Sagar Shedge 24 Nov '14

24 Nov '14

Hi , I have two virtual machines VM1 and VM2. Then I have added eth0 of my VM to 'default' network. Use case :- I want to monitor all traffic on virbr0('default' network). Steps followed :- 1. Add VM1 eth0 to virbr0 2. Add VM2 eth1 to virbr0 3. brctl setageing ovsbr0 0 ..(To put bridge in promiscuous) Now I am running tcpdump on eth1 of VM2 and trying to ping google.com(outside world) In VM2 (tcpdump -i eth1), I can see only ingress(incoming) traffic of VM1. I am not able see outgoing traffic of VM1. If I create another bridge and trying same scenario with 2 VM then VM2 can see both ingress and outgress traffic. So want to know what is the issue? Is libvirt doing something different with this virtbr0 bridge? -- Sagar Dilip Shedge, Pune. With Regards.

2 5

[libvirt-users] Error starting domain: internal error: missing IFLA_VF_INFO in netlink response
by Hong-Hua.Yin＠freescale.com 24 Nov '14

24 Nov '14

Hi, We try PCI Passthrough of host network devices on PPC platform. http://wiki.libvirt.org/page/Networking#Assignment_with_.3Cinterface_type.3… But we got a similar issue as below that reported on RedHat before: https://bugzilla.redhat.com/show_bug.cgi?id=1040626 With <hostdev>, it could start VM successfully. <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x01' slot='0x00' function='0x4'/> </source> </hostdev> Logged into VM and checked for VF using lspci root@model : qemu ppce500:~# lspci 00:00.0 PCI bridge: Freescale Semiconductor Inc MPC8533E 00:02.0 Power PC: Freescale Semiconductor Inc Device 0000 (rev 20) 00:03.0 Unclassified device [00ff]: Red Hat, Inc Virtio memory balloon But it will fail if using <interface type="hostdev">: <interface type="hostdev" managed="yes"> <mac address="00:e0:0c:00:20:01"/> <source> <address type="pci" domain="0x0000" bus="0x01" slot="0x00" function="0x4"/> </source> </interface> # virsh create vf.xml 2014-11-24 11:08:31.390+0000: 3556: info : libvirt version: 1.2.2 2014-11-24 11:08:31.390+0000: 3556: debug : virLogParseOutputs:1378 : outputs=1:file:virsh.log error: Failed to create domain from vf.xml error: internal error: missing IFLA_VF_INFO in netlink response Exactly We're using max_vfs=2 and libnl-3.2.22 # ls -l /usr/lib64/libnl-3.so.200.17.0 -rwxr-xr-x 1 root root 154440 Sep 17 07:15 /usr/lib64/libnl-3.so.200.17.0 Why this issue happened on PPC? Is there anything architecture-specific support needed to add? Thanks, Olivia

1 0

Re: [libvirt-users] some problem with snapshot by libvirt
by Payes Anand 22 Nov '14

22 Nov '14

Eric Blake <eblake@...> writes: > > On 05/27/2012 06:39 PM, xingxing gao wrote: > > Hi,all,i am using libvirt to manage my vm,in these days i am testing > > the libvirt snapshot ,but meet some problem: > > > > the snapshot was created from this command: > > snapshot-create-as win7 --disk-only --diskspec > > vda,snapshot=external --diskspec hda,snapshot=no > > > > but when i tried to revert from the snapshot which created from the > > above command ,i got error below: > > > > virsh # snapshot-revert win7 1338041515 --force > > error: unsupported configuration: revert to external disk snapshot not > > supported yet > > Yep. You've run into a case where I haven't yet been able to code > things. The problem is that reverting to a disk image has a question - > you are starting with two files (the snapshot backing file and the new > qcow2 wrapper), but the moment you reload the backing file for > modification, you invalidate the qcow2 wrapper. There are two sane > options - create yet another qcow2 wrapper around the same backing file, > or delete the qcow2 wrapper as part of reverting to the snapshot, but we > would probably need two new flags to the virDomainRevertToSnapshot API > to select one of these two behaviors. In the meantime, the only way to > revert to a disk-only snapshot is to manually edit the domain XML to > match what you want to do, possibly with manual qemu-img operations as well. > > Help in writing the patches to improve the functionality would be welcome. > Has the issue ( revert to external disk snapshot ) been solved in later versions of libvirt? I am using: Compiled against library: libvirt 1.2.2 Using library: libvirt 1.2.2 Using API: QEMU 1.2.2 Running hypervisor: QEMU 2.1.92 On trying to revert to an external snapshot, Getting the error: revert to external disk snapshot not supported yet If not is there any alternate.

2 1

[libvirt-users] some problem with snapshot by libvirt
by xingxing gao 22 Nov '14

22 Nov '14

Hi,all,i am using libvirt to manage my vm,in these days i am testing the libvirt snapshot ,but meet some problem: the snapshot was created from this command: snapshot-create-as win7 --disk-only --diskspec vda,snapshot=external --diskspec hda,snapshot=no but when i tried to revert from the snapshot which created from the above command ,i got error below: virsh # snapshot-revert win7 1338041515 --force error: unsupported configuration: revert to external disk snapshot not supported yet version: virsh # version Compiled against library: libvir 0.9.4 Using library: libvir 0.9.4 Using API: QEMU 0.9.4 Running hypervisor: QEMU 1.0.93

4 8

[libvirt-users] How to enable apparmor security driver for libvirt
by Jackie 21 Nov '14

21 Nov '14

Hi guys, I want to enable apparmor security driver for my libvirt env with ubuntu os. What I do is as following: First, I got the source code and compile it. ubuntu@ubuntu:~/github$git clone git://libvirt.org/libvirt.git ubuntu@ubuntu:~/github/libvirt$ dpkg -l|grep apparmor ii apparmor 2.8.95~2430-0ubuntu5 amd64 User-space parser utility for AppArmor ii libapparmor-dev:amd64 2.8.95~2430-0ubuntu5.1 amd64 AppArmor development libraries and header files ii libapparmor-perl 2.8.95~2430-0ubuntu5 amd64 AppArmor library Perl bindings ii libapparmor1:amd64 2.8.95~2430-0ubuntu5.1 amd64 changehat AppArmor library ubuntu@ubuntu:~/github/libvirt$./autogen.sh --system --with-apparmor ubuntu@ubuntu:~/github/libvirt$make -j8 ubuntu@ubuntu:~/github/libvirt$sudo make install Then I configure the apparmor (security_driver = "apparmor") in /etc/libvirt/qemu.conf, and restart libvirtd. I thought this may be ok. But it turned out that apparmor security driver is not loaded for my libvirt: The output of "virsh capabilities | grep apparmor" is None. What's the problem? Best Regards~ Jackie

1 0

[libvirt-users] Cannot find suitable CPU model for given data
by mb 21 Nov '14

21 Nov '14

Hello all, I have a new Sun fire X4140 server with two amd opteron 2435 CPUs running debian jessie, libvirt 1.2.9-3, virtinst 1.0.1-3, qemu/kvm 2.1. When attempting to create virtual machines (with --debug), I receive this: [Thu, 20 Nov 2014 13:56:36 virt-install 1842] DEBUG (cli:234) File "/usr/share/virt-manager/virt-install", line 876, in <module> sys.exit(main()) File "/usr/share/virt-manager/virt-install", line 870, in main start_install(guest, continue_inst, options) File "/usr/share/virt-manager/virt-install", line 588, in start_install fail(e, do_exit=False) File "/usr/share/virt-manager/virtinst/cli.py", line 234, in fail logging.debug("".join(traceback.format_stack())) [Thu, 20 Nov 2014 13:56:36 virt-install 1842] ERROR (cli:235) internal error: Cannot find suitable CPU model for given data [Thu, 20 Nov 2014 13:56:36 virt-install 1842] DEBUG (cli:237) Traceback (most recent call last): File "/usr/share/virt-manager/virt-install", line 560, in start_install dom = guest.start_install(meter=meter, noboot=options.noreboot) 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/lib/python2.7/dist-packages/libvirt.py", line 3440, in createLinux if ret is None:raise libvirtError('virDomainCreateLinux() failed', conn=self) libvirtError: internal error: Cannot find suitable CPU model for given data [Thu, 20 Nov 2014 13:56:36 virt-install 1842] DEBUG (cli:248) Domain installation does not appear to have been successful. svm and svm_lock are present in /proc/cpuinfo, in the initial output of virt-install with --debug, it says it will use the proper cpu: <cpu mode="custom" match="exact"> <model>Opteron_G3</model> </cpu> I've tried using --cpu host, --cpu best, --cpu Opteron_G3, all fail with the same error. Anyone know what I can do here? I'd like to stick with KVM, but maybe Xen would work? I'm not sure if this error is coming from libvirt, or KVM itself. Thanks! mb

1 0

[libvirt-users] maxvcpus
by Laszlo Hornyak 20 Nov '14

20 Nov '14

Hi list, According to the libvirt documentation [1] "Show maximum number of virtual CPUs for guest domains on this connection" This may not be a complete definition. My first guess from the above was that this returns the number of virtual CPUs that can exist at the same time on the host, either one or several VMs. In fact it returned 16 in my fedora 20 desktop running with KVM, while this is not the real limit of vCPUs. I can define a VM with more than 16 vCPUs (which does not really make sense when I have only two cores, but it looks cool) and also I can have well over 16 virtual machines running on the host. I looked into the implementation and now I understand that each driver returns different values, but I do not understand the constants. Can you guys give me some hints how should I understand the output of the command? Best regards, Laszlo [1] : http://libvirt.org/sources/virshcmdref/html/sect-maxvcpus.html -- EOF

2 2

Re: [libvirt-users] virsh net-start default fails
by Michal Privoznik 20 Nov '14

20 Nov '14

On 22.10.2014 00:03, David Roundy wrote: > Hi Michal, > > I am attaching debug logs. > > David Well, I can see the error message there, but not the reason. Does the /etc/libvirt/qemu/networks/default.xml file exist? Michal

3 3

[libvirt-users] Whether Virsh migrate VM works with xen hypervisor??
by Ajitha Robert 20 Nov '14

20 Nov '14

Hi all By referring https://libvirt.org/migration.html.. I tried VM migration between two libvirt machines I tried instance migration with ssh, tls and tcp. In all three I got the same error as " this function is not supported by the connection driver" *Eg* migrate --live domuname xen+tls://desthostname/system error: this function is not supported by the connection driver: virDomainMigrate3 My question is Whether live migration is supported with Xen hypervisor. -- *Regards,Ajitha R*

1 0

[libvirt-users] Connecting libvirt remotely using tls: TLS handshake failed : packet with unexpected length +gnutls_handhsake Error
by Ajitha Robert 19 Nov '14

19 Nov '14

Hi all, I am facing an error while connecting libvirt remotely using tls.. I have created CA, client and server certificates with RSA 1024 bit using Openssl. I am using debian linux flavor in both client and server. *Original Error:* (When trying to connect remote libvirt) virsh -c xen+tls://destinationipaddr/system error: failed to connect to the hypervisor error: authentication failed: TLS handshake failed A TLS packet with unexpected length was received. In source code i found the error line. the return value is 21 ./src/rpc/virnettlscontext.c: ret = gnutls_handshake(sess->session); *Below are log details* *client(Initiator of ssl connection ) :* virNetTLSSessionHandshake:1351 : Ret=-21 error: authentication failed: TLS handshake failed A TLS packet with unexpected length was received. *In the server side, * virNetTLSSessionHandshake:1369 : authentication failed: TLS handshake failed Could not negotiate a supported cipher suite. Please guide me for solving this error -- *Regards,Ajitha R*

2 2