- Users - libvirt List Archives

[libvirt-users] livemigration over specific bridge/nic?
by Christoph Raible 25 Mar '11

25 Mar '11

Hi @all, I have a question about the livemigration with libvirt / kvm. I have two bridges configured in my setup of each host. Now I want to set br1 (private network) as default NIC for live migration. Is there any solution to get this work for me? I tried to bind libvirt to those IP-Range but after that the livemigration doesn't works. If you need more details please tell me :) Regards, Christoph -- Vorstand/Board of Management: Dr. Bernd Finkbeiner, Dr. Roland Niemeier, Dr. Arno Steitz, Dr. Ingrid Zech Vorsitzender des Aufsichtsrats/ Chairman of the Supervisory Board: Michel Lepert Sitz/Registered Office: Tuebingen Registergericht/Registration Court: Stuttgart Registernummer/Commercial Register No.: HRB 382196

2 2

Re: [libvirt-users] libvirt unavailable while a VM is in migration?]
by Igor Serebryany 24 Mar '11

24 Mar '11

On Mon, Dec 20, 2010 at 02:14:42PM +0100, Jiri Denemark wrote: > Ouch, I wonder if that could be the reason... Just to make sure that my strange compiling/packages aren't causing the problem, I've set up two servers running fedora 14 with the official libvirt packages. i experience the same problem -- while a vm is in migration, nothing else works. my traces reveal libvirt getting stuck at the same exact spot as on my debian machines. at this point, i'm pretty sure that this is a bug in libvirt. Has libvirt ever had the ability to perform other operations while a qemu migration is in progress? If so than this is a regression, and a pretty serious one. For me, this makes live-migrations totally unusable, and since I cannot run my project without live-migrations and I cannot use any outside tools to do live-migrations when I'm using libvirt this makes libvirt totally unusable. i am desperate to get this bug fixed, and i don't think i have the resources to try to patch it myself. is there anything i can do to help you guys? more debugging info? foot massage? --Igor

2 3

[libvirt-users] storage pool vs storage volume
by Zvi Dubitzky 23 Mar '11

23 Mar '11

Can anybody give a good reference to understand the difference between storage pool and storage volume >From what I have seem storage volume describes the physical storage media and the pool a collection of such But from the XML at libvirt I do not exactly understand that . thanks Zvi Dubitzky Email:dubi@il.ibm.com

2 2

[libvirt-users] using more than 1 core by a virtual machine
by Zvi Dubitzky 22 Mar '11

22 Mar '11

My virtual machine xml file has <vcpu>2</vcpu> clause while the host has 2 physical cpus (cores). Is this enough to cause a VM running 2 endless loop threads to use the 2 cores ? In my case the VM running reports (cat /roc/cpuinfo) that it has 2 vcpus but it uses only 1 core (at a time) because the 'top' at the host shows 100%cpu (out of total 200%) used by the endless loop application Also virsh vcpuinfo <vm> shows only 1 CPU and 1 vcpu any idea ? thanks Zvi Dubitzky Email:dubi@il.ibm.com

2 3

[libvirt-users] About monitoring
by kadir yüceer 22 Mar '11

22 Mar '11

Hello all, As I've been exporing libvirt api, I've seen event registerers, and types of events are defined, undefined, and you know the rest. Is it all for event types? Any ideas about how to look for a device access event, for example? Kind regards

2 1

[libvirt-users] start/stop hooks
by Mateusz Kijowski 22 Mar '11

22 Mar '11

Hi list, I have a quick question. Is there a way to run a script on the libvirt host after a domain is started/stopped ? -- Mateusz

2 1

[libvirt-users] error : remoteDispatchAuthPolkit:3799 : Policy kit denied action org.libvirt.unix.manage from pid 2381
by Christoph Raible 21 Mar '11

21 Mar '11

Hi @all, first my system: OS: Scientific Linux 6.0 Hypervisor: KVM + libvirt I got the following error /*error : remoteDispatchAuthPolkit:3799 : Policy kit denied action org.libvirt.unix.manage from pid 2381*/ when I want to connect with: /*virsh -c qemu:///system*/ to the hypervisor with a new added user. The user is in in kvm and qmeu group and the connection with virsh -c qemu://$hostname/system works fine. Also root login with the "login" works fine. I configured libvirt to use TLS-authetification... Did anyone of you have a solution to solve this problem. Best Regards Christoph Raible -- Vorstand/Board of Management: Dr. Bernd Finkbeiner, Dr. Roland Niemeier, Dr. Arno Steitz, Dr. Ingrid Zech Vorsitzender des Aufsichtsrats/ Chairman of the Supervisory Board: Michel Lepert Sitz/Registered Office: Tuebingen Registergericht/Registration Court: Stuttgart Registernummer/Commercial Register No.: HRB 382196

1 0

[libvirt-users] libvirtd -- iptables
by Kurian Thayil 18 Mar '11

18 Mar '11

Hi All, I created a couple of virtual networks (forward mode=nat) in my rhel6-kvm box. I've come across 2 weird issues. 1. My Iptables rule chainset contains repeated rules. The same rule gets repeated block by block 2. For connecting to guest using SSH, I created a custom IPTables chain. I want this chain to be on top of the FORWARD chain, but everytime the libvirtd is restarted the rule comes to the bottom of the chain (Appended). Can anyone suggest me what the solution could be? My IPtable rules are given below: Let me know if any further info is needed. [root@santiago Packages]# iptables -L -n -v Chain INPUT (policy ACCEPT 41 packets, 5818 bytes) pkts bytes target prot opt in out source destination 0 0 ACCEPT udp -- vbr0 * 0.0.0.0/0 0.0.0.0/0 udp dpt:53 0 0 ACCEPT tcp -- vbr0 * 0.0.0.0/0 0.0.0.0/0 tcp dpt:53 0 0 ACCEPT udp -- vbr0 * 0.0.0.0/0 0.0.0.0/0 udp dpt:67 0 0 ACCEPT tcp -- vbr0 * 0.0.0.0/0 0.0.0.0/0 tcp dpt:67 0 0 ACCEPT udp -- vbr1 * 0.0.0.0/0 0.0.0.0/0 udp dpt:53 0 0 ACCEPT tcp -- vbr1 * 0.0.0.0/0 0.0.0.0/0 tcp dpt:53 0 0 ACCEPT udp -- vbr1 * 0.0.0.0/0 0.0.0.0/0 udp dpt:67 0 0 ACCEPT tcp -- vbr1 * 0.0.0.0/0 0.0.0.0/0 tcp dpt:67 0 0 ACCEPT udp -- vbr0 * 0.0.0.0/0 0.0.0.0/0 udp dpt:53 0 0 ACCEPT tcp -- vbr0 * 0.0.0.0/0 0.0.0.0/0 tcp dpt:53 0 0 ACCEPT udp -- vbr0 * 0.0.0.0/0 0.0.0.0/0 udp dpt:67 0 0 ACCEPT tcp -- vbr0 * 0.0.0.0/0 0.0.0.0/0 tcp dpt:67 0 0 ACCEPT udp -- vbr1 * 0.0.0.0/0 0.0.0.0/0 udp dpt:53 0 0 ACCEPT tcp -- vbr1 * 0.0.0.0/0 0.0.0.0/0 tcp dpt:53 0 0 ACCEPT udp -- vbr1 * 0.0.0.0/0 0.0.0.0/0 udp dpt:67 0 0 ACCEPT tcp -- vbr1 * 0.0.0.0/0 0.0.0.0/0 tcp dpt:67 0 0 ACCEPT udp -- vbr0 * 0.0.0.0/0 0.0.0.0/0 udp dpt:53 0 0 ACCEPT tcp -- vbr0 * 0.0.0.0/0 0.0.0.0/0 tcp dpt:53 0 0 ACCEPT udp -- vbr0 * 0.0.0.0/0 0.0.0.0/0 udp dpt:67 0 0 ACCEPT tcp -- vbr0 * 0.0.0.0/0 0.0.0.0/0 tcp dpt:67 0 0 ACCEPT udp -- vbr1 * 0.0.0.0/0 0.0.0.0/0 udp dpt:53 0 0 ACCEPT tcp -- vbr1 * 0.0.0.0/0 0.0.0.0/0 tcp dpt:53 0 0 ACCEPT udp -- vbr1 * 0.0.0.0/0 0.0.0.0/0 udp dpt:67 0 0 ACCEPT tcp -- vbr1 * 0.0.0.0/0 0.0.0.0/0 tcp dpt:67 0 0 ACCEPT udp -- vbr0 * 0.0.0.0/0 0.0.0.0/0 udp dpt:53 0 0 ACCEPT tcp -- vbr0 * 0.0.0.0/0 0.0.0.0/0 tcp dpt:53 0 0 ACCEPT udp -- vbr0 * 0.0.0.0/0 0.0.0.0/0 udp dpt:67 0 0 ACCEPT tcp -- vbr0 * 0.0.0.0/0 0.0.0.0/0 tcp dpt:67 0 0 ACCEPT udp -- vbr1 * 0.0.0.0/0 0.0.0.0/0 udp dpt:53 0 0 ACCEPT tcp -- vbr1 * 0.0.0.0/0 0.0.0.0/0 tcp dpt:53 0 0 ACCEPT udp -- vbr1 * 0.0.0.0/0 0.0.0.0/0 udp dpt:67 0 0 ACCEPT tcp -- vbr1 * 0.0.0.0/0 0.0.0.0/0 tcp dpt:67 0 0 ACCEPT udp -- vbr0 * 0.0.0.0/0 0.0.0.0/0 udp dpt:53 0 0 ACCEPT tcp -- vbr0 * 0.0.0.0/0 0.0.0.0/0 tcp dpt:53 0 0 ACCEPT udp -- vbr0 * 0.0.0.0/0 0.0.0.0/0 udp dpt:67 0 0 ACCEPT tcp -- vbr0 * 0.0.0.0/0 0.0.0.0/0 tcp dpt:67 0 0 ACCEPT udp -- vbr1 * 0.0.0.0/0 0.0.0.0/0 udp dpt:53 0 0 ACCEPT tcp -- vbr1 * 0.0.0.0/0 0.0.0.0/0 tcp dpt:53 0 0 ACCEPT udp -- vbr1 * 0.0.0.0/0 0.0.0.0/0 udp dpt:67 0 0 ACCEPT tcp -- vbr1 * 0.0.0.0/0 0.0.0.0/0 tcp dpt:67 Chain FORWARD (policy ACCEPT 0 packets, 0 bytes) pkts bytes target prot opt in out source destination 0 0 ACCEPT all -- * vbr0 0.0.0.0/0 10.10.0.0/24 state RELATED,ESTABLISHED 0 0 ACCEPT all -- vbr0 * 10.10.0.0/24 0.0.0.0/0 0 0 ACCEPT all -- vbr0 vbr0 0.0.0.0/0 0.0.0.0/0 0 0 REJECT all -- * vbr0 0.0.0.0/0 0.0.0.0/0 reject-with icmp-port-unreachable 0 0 REJECT all -- vbr0 * 0.0.0.0/0 0.0.0.0/0 reject-with icmp-port-unreachable 0 0 ACCEPT all -- * vbr1 0.0.0.0/0 10.10.1.0/24 state RELATED,ESTABLISHED 0 0 ACCEPT all -- vbr1 * 10.10.1.0/24 0.0.0.0/0 0 0 ACCEPT all -- vbr1 vbr1 0.0.0.0/0 0.0.0.0/0 0 0 REJECT all -- * vbr1 0.0.0.0/0 0.0.0.0/0 reject-with icmp-port-unreachable 0 0 REJECT all -- vbr1 * 0.0.0.0/0 0.0.0.0/0 reject-with icmp-port-unreachable 5688 588K rhel-virt-forward-1 all -- * * 0.0.0.0/0 0.0.0.0/0 0 0 ACCEPT all -- * vbr0 0.0.0.0/0 10.10.0.0/24 state RELATED,ESTABLISHED 0 0 ACCEPT all -- vbr0 * 10.10.0.0/24 0.0.0.0/0 0 0 ACCEPT all -- vbr0 vbr0 0.0.0.0/0 0.0.0.0/0 0 0 REJECT all -- * vbr0 0.0.0.0/0 0.0.0.0/0 reject-with icmp-port-unreachable 0 0 REJECT all -- vbr0 * 0.0.0.0/0 0.0.0.0/0 reject-with icmp-port-unreachable 0 0 ACCEPT all -- * vbr1 0.0.0.0/0 10.10.1.0/24 state RELATED,ESTABLISHED 0 0 ACCEPT all -- vbr1 * 10.10.1.0/24 0.0.0.0/0 0 0 ACCEPT all -- vbr1 vbr1 0.0.0.0/0 0.0.0.0/0 0 0 REJECT all -- * vbr1 0.0.0.0/0 0.0.0.0/0 reject-with icmp-port-unreachable 0 0 REJECT all -- vbr1 * 0.0.0.0/0 0.0.0.0/0 reject-with icmp-port-unreachable 0 0 ACCEPT all -- * vbr0 0.0.0.0/0 10.10.0.0/24 state RELATED,ESTABLISHED 0 0 ACCEPT all -- vbr0 * 10.10.0.0/24 0.0.0.0/0 0 0 ACCEPT all -- vbr0 vbr0 0.0.0.0/0 0.0.0.0/0 0 0 REJECT all -- * vbr0 0.0.0.0/0 0.0.0.0/0 reject-with icmp-port-unreachable 0 0 REJECT all -- vbr0 * 0.0.0.0/0 0.0.0.0/0 reject-with icmp-port-unreachable 0 0 ACCEPT all -- * vbr1 0.0.0.0/0 10.10.1.0/24 state RELATED,ESTABLISHED 0 0 ACCEPT all -- vbr1 * 10.10.1.0/24 0.0.0.0/0 0 0 ACCEPT all -- vbr1 vbr1 0.0.0.0/0 0.0.0.0/0 0 0 REJECT all -- * vbr1 0.0.0.0/0 0.0.0.0/0 reject-with icmp-port-unreachable 0 0 REJECT all -- vbr1 * 0.0.0.0/0 0.0.0.0/0 reject-with icmp-port-unreachable 0 0 ACCEPT all -- * vbr0 0.0.0.0/0 10.10.0.0/24 state RELATED,ESTABLISHED 0 0 ACCEPT all -- vbr0 * 10.10.0.0/24 0.0.0.0/0 0 0 ACCEPT all -- vbr0 vbr0 0.0.0.0/0 0.0.0.0/0 0 0 REJECT all -- * vbr0 0.0.0.0/0 0.0.0.0/0 reject-with icmp-port-unreachable 0 0 REJECT all -- vbr0 * 0.0.0.0/0 0.0.0.0/0 reject-with icmp-port-unreachable 0 0 ACCEPT all -- * vbr1 0.0.0.0/0 10.10.1.0/24 state RELATED,ESTABLISHED 0 0 ACCEPT all -- vbr1 * 10.10.1.0/24 0.0.0.0/0 0 0 ACCEPT all -- vbr1 vbr1 0.0.0.0/0 0.0.0.0/0 0 0 REJECT all -- * vbr1 0.0.0.0/0 0.0.0.0/0 reject-with icmp-port-unreachable 0 0 REJECT all -- vbr1 * 0.0.0.0/0 0.0.0.0/0 reject-with icmp-port-unreachable 0 0 ACCEPT all -- * vbr0 0.0.0.0/0 10.10.0.0/24 state RELATED,ESTABLISHED 0 0 ACCEPT all -- vbr0 * 10.10.0.0/24 0.0.0.0/0 0 0 ACCEPT all -- vbr0 vbr0 0.0.0.0/0 0.0.0.0/0 0 0 REJECT all -- * vbr0 0.0.0.0/0 0.0.0.0/0 reject-with icmp-port-unreachable 0 0 REJECT all -- vbr0 * 0.0.0.0/0 0.0.0.0/0 reject-with icmp-port-unreachable 0 0 ACCEPT all -- * vbr1 0.0.0.0/0 10.10.1.0/24 state RELATED,ESTABLISHED 0 0 ACCEPT all -- vbr1 * 10.10.1.0/24 0.0.0.0/0 0 0 ACCEPT all -- vbr1 vbr1 0.0.0.0/0 0.0.0.0/0 0 0 REJECT all -- * vbr1 0.0.0.0/0 0.0.0.0/0 reject-with icmp-port-unreachable 0 0 REJECT all -- vbr1 * 0.0.0.0/0 0.0.0.0/0 reject-with icmp-port-unreachable 0 0 ACCEPT all -- * * 0.0.0.0/0 0.0.0.0/0 PHYSDEV match --physdev-is-bridged Chain OUTPUT (policy ACCEPT 38 packets, 4234 bytes) pkts bytes target prot opt in out source destination Chain rhel-virt-forward-1 (1 references) pkts bytes target prot opt in out source destination 25 2100 ACCEPT icmp -- eth0 vbr1 0.0.0.0/0 0.0.0.0/0 3515 262K ACCEPT tcp -- eth0 vbr1 0.0.0.0/0 0.0.0.0/0 tcp dpt:22 0 0 ACCEPT icmp -- eth0 vbr0 0.0.0.0/0 0.0.0.0/0 0 0 ACCEPT tcp -- eth0 vbr0 0.0.0.0/0 0.0.0.0/0 tcp dpt:22 **************Details about my virtual network interfaces are given below: [root@santiago Packages]# virsh net-list --all Name State Autostart ----------------------------------------- vir0 active yes vir1 active yes Thank you in advance. Regards, --Kurian.

1 0

[libvirt-users] RH6 qemu expects driver name
by Robert Šmol 18 Mar '11

18 Mar '11

Hi, I am trying to start machine on RH6. virsh # start ulp-001 error: Failed to start domain ulp-001 error: internal error process exited while connecting to monitor: char device redirected to /dev/pts/1 qemu-kvm: -device lsi,id=scsi0,bus=pci.0,addr=0x5: Parameter 'driver' expects a driver name Try with argument '?' for a list. virsh # version Compiled against library: libvir 0.8.1 Using library: libvir 0.8.1 Using API: QEMU 0.8.1 Running hypervisor: QEMU 0.12.1 This is part of the config <disk type='file' device='disk'> <driver name='qemu' type='raw'/> <source file='/rhev-data/defaultStore/ulp-001a.img'/> <target dev='sda' bus='scsi'/> <address type='drive' controller='0' bus='0' unit='0'/> </disk> <controller type='ide' index='0'> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x1'/> </controller> <controller type='scsi' index='0'> <address type='pci' domain='0x0000' bus='0x00' slot='0x05' function='0x0'/> </controller> Any tips? -- stereoIT - Open Source Technology Partners http://www.stereoit.com mobile: +420 776 762378

2 3

[libvirt-users] SSH recovery console
by Nikita A Menkovich 17 Mar '11

17 Mar '11

Hello, Is there available to create ssh recovery console except vnc console, that is default by libvirt. For example connect to kvm@host:2220 and go to first console For example like here <serial type="tcp"> <source mode="bind" host="127.0.0.1" service="2445"/> <protocol type="telnet"/> <target port="1"/> </serial> But not plain format -- Nikita A Menkovich http://libc6.org/ JID: menkovich(a)gmail.com

2 1