- Users - libvirt List Archives

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

21 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 21 Mar '11

21 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 17 Mar '11

17 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 16 Mar '11

16 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

[libvirt-users] With which VMM ,libvirt cooperates the most?
by kadir yüceer 16 Mar '11

16 Mar '11

Hi all, I'm trying to develop some applications that communicate with VMM about guest OSs. Libvirt has drivers for many VMMs like Qemu, Vbox, etc. I'm currently using Vbox and time to time I get the error that says "this function is not supported by the connection driver". So, for which VMM, libvirt has the most compatible driver, regarding your experiences? Kind regards Kadir

2 1

[libvirt-users] remote xen+ssh://host
by sd 15 Mar '11

15 Mar '11

Hello, Is there a way where I can connect remote via ssh on a host and specify the username / password ? So far I found out that only the username can be specified and that will ssh keys. I would like something like xen+ssh://user:password@host thanks sd

1 0

[libvirt-users] Beware! Newbie is in town
by kadir yüceer 15 Mar '11

15 Mar '11

Hello everyone, I'm working on Ubuntu 10.10, installed libvirt and created a project in Netbeans, I included jna.jar and libvirt-0.4.7.jar. And guess what, I get the exception below when I'm trying to run test.java which connects to test:///default. Exception in thread "main" java.lang.UnsatisfiedLinkError: Unable to load library 'virt': libvirt.so: cannot open shared object file: No such file or directory at com.sun.jna.NativeLibrary.loadLibrary(NativeLibrary.java:164) at com.sun.jna.NativeLibrary.getInstance(NativeLibrary.java:237) at com.sun.jna.Library$Handler.<init>(Library.java:140) at com.sun.jna.Native.loadLibrary(Native.java:374) at com.sun.jna.Native.loadLibrary(Native.java:359) at org.libvirt.jna.Libvirt.<clinit>(Unknown Source) at org.libvirt.Connect.<clinit>(Unknown Source) at novatest_v01.Main.main(Main.java:21) I'm sure this question has been asked dozens of times, sorry. But any answer/comment is appreciated. Thanks Kadir

3 6

[libvirt-users] cgroups limitations on Virtual machines
by Zvi Dubitzky 14 Mar '11

14 Mar '11

I have 2 VMs launched by : 'virsh create <xml file>' . Both VMs get 2 vcpus (out of total 2 cores of the host) I then try bias their cpu cycle quota by manipulating the cpu_shares ( virsh schedinfo --set cpu_shares=<value> vm1/2 ) so that VM1 will get 3 times the cpu cycles VM2 gets. (e.g : VM1 cpu_shares = 150 . VM2 cpu_shares = 50) . There are no other VMs defined or any other significant process running on the host . Each VM runs the same process (2 threads endless loop ). Still both VM1 and VM2 get equal share of the 2 cores - running top utility at the host shows each is consuming 100% CPU. At each VM console cat /proc/cpuinfo shows 2 cores assigned to the VM. At the host : virsh vcpuinfo <vm1/2> shows each has 2 vcpus (0 an 1 )but actually a single separate CPU is used for either vcpu0 or vcpu1 at each VM at any check point in time (this is reasonable as it does not say what portion of the core cycles is used by each VM) . Can anyone explain that and how to bias the core usage of the 2 VMs by manipulating the cpu_shares parameter (or other parameters) so that 'top' at the host will reflect the bias . I would expect 'top' at the host to show 150% CPU for VM1 ( qemu-system-x86) and 50% CPU for VM2 (the other qemu-system-x86) with above set cpu_share values . Doing the same test with 2 plain processes (instead VMs udner libvirt) with same cpu_shares bias gives the expected biased cpu usage between the 2 processes My system is fedora14 and kernel 2.6.35.6-45.fc14.x86_64 . thanks Zvi Dubitzky Email:dubi@il.ibm.com

1 0