- Users - libvirt List Archives

[libvirt-users] network problem
by Evaggelos Balaskas 07 Oct '12

07 Oct '12

Hi, i have a lvm partition that i need to share from the host server to the virtual machines. em1: 10.0.0.251 em2: 10.0.0.252 macvtap:em1 10.0.0.249 macvtap:em2 10.0.0.250 With identical configs (so i believe that they are) from VM win2003 i can ping to all the above IPs and open the samba share as a map drive. >From VM: win2008 i can ping to VMwin2003 but not at hosts IPs .251 & 252. I have attached some info on my setup. Plz advice. -- Evaggelos Balaskas - Unix System Engineer http://gr.linkedin.com/in/evaggelosbalaskas

1 0

[libvirt-users] alias as volume names for multipath storrage pools
by Michael Menge 05 Oct '12

05 Oct '12

Hi, I use virt-manager 0.9.4 and libvirt 0.9.13-0 and have configured a multipath storage pool. In the storage management window of virtmanager, only the short device name "dm-1" is shown as volumename. Is there a way to display the alias name or the path in thes storage window, as example_vm_root oder /dev/mapper/example_vm_root is more informative as dm-1 Regards Michael Menge -------------------------------------------------------------------------------- M.Menge Tel.: (49) 7071/29-70316 Universität Tübingen Fax.: (49) 7071/29-5912 Zentrum für Datenverarbeitung mail: michael.menge(a)zdv.uni-tuebingen.de Wächterstraße 76 72074 Tübingen

2 2

[libvirt-users] error: authentication failed: Authorization requires authentication but no agent is available
by Yih Chuang 05 Oct '12

05 Oct '12

I ran into this error. Any way to fix it? [vmcuser@rhel60h207kvm .ssh]$ virsh -c qemu+ssh:// vmcuser(a)9.10.110.241/system list --all error: authentication failed: Authorization requires authentication but no agent is available. error: failed to connect to the hypervisor Here is my settings different from default: [root@rhel60e201c libvirt]# diff libvirtd.conf libvirtd.conf.old 81c81 < unix_sock_group = "vmcuser" --- > #unix_sock_group = "libvirt" 88c88 < unix_sock_ro_perms = "0777" --- > #unix_sock_ro_perms = "0777" 98c98 < unix_sock_rw_perms = "0770" --- > #unix_sock_rw_perms = "0770" 129c129 < auth_unix_ro = "none" --- > #auth_unix_ro = "none" [root@rhel60e201c libvirt]# diff qemu.conf qemu.conf.old 151c151 < user = "vmcuser" --- > #user = "root" 154c154 < group = "vmcuser" --- > #group = "root" Thanks. --Yih

1 0

[libvirt-users] no callback on VIR_DOMAIN_EVENT_ID_BALLOON_CHANGE in 0.10.2
by Ben Clay 04 Oct '12

04 Oct '12

I'm trying to track balloon growth after issuing a setmem command to a KVM guest with libvirt 0.10.2 and qemu-kvm 0.12.1.2 on CentOS 6.3. libvirt 0.10.2 was built from tar today and appears to be working fine. The guest is running CentOS 6.3 as well. Using the provided test programs under examples/domain-events/ in C and Python, I'm not seeing VIR_DOMAIN_EVENT_ID_BALLOON_CHANGE ever tick, although I do see other events like VIR_DOMAIN_EVENT_ID_LIFECYCLE, VIR_DOMAIN_EVENT_ID_REBOOT, and VIR_DOMAIN_EVENT_ID_RTC_CHANGE. The balloon is definitely changing, and is reflected by both virsh -c qemu:///system dommemstat <dom> and free inside the guest. Here's the balloon in my config for reference: <memballoon model='virtio'> <alias name='balloon0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x05' function='0x0'/> </memballoon> Is my understanding incorrect of what VIR_DOMAIN_EVENT_ID_BALLOON_CHANGE is? Is there something else this event is tracking, other than a virsh -c qemu:///system setmem <dom> <mem in KB> command and/or subsequent balloon movement inside the guest? Or, is my old version of qemu-kvm not passing this event back to libvirt? The latter doesn't seem correct because I'm getting seemingly-valid values from dommemstat - ie, if I setmem 200MB when the guest OS and applications are consuming 300MB, it reports near 300MB (and the guest no longer responds) instead of just parroting the 200MB value I fed it. Thanks! Ben Clay rbclay(a)ncsu.edu

2 3

[libvirt-users] Problems connecting with a remote VirtualBox server
by john Sanabria 04 Oct '12

04 Oct '12

Hi, I want to connect to my VirtualBox hypervisor using a string connection similar to this virsh -c vbox+ssh://localhost/session but it does not work however I can run virsh -c vbox:///session successfully. josanabr@leader:~$ virsh -c vbox+ssh://localhost/session error: End of file while reading data: : Input/output error error: failed to connect to the hypervisor josanabr@leader:~$ virsh -c vbox:///session Welcome to virsh, the virtualization interactive terminal. Type: 'help' for help with commands 'quit' to quit virsh # I have not modified any libvirt configuration file. I appreciate your feedback. -- John Sanabria - Profesor de la EISC Universidad del Valle

1 0

[libvirt-users] IPv4 routed virtual networks
by Gene Czarcinski 04 Oct '12

04 Oct '12

OK, either I have taken a stupid pill and am missing something basic or routed network do not work. I assume that, if they did work, it would be in more or less that same manner as a nat network as far as ping'ing, ssh'ing, etc. to another real host on the same real LAN as the virtualization host. At least that is what I believe I should expect. I have googled for info and everything says that it should work. On of the referenced documents was this: http://berrange.com/posts/2009/12/13/routed-subnets-without-nat-for-libvirt… I checked through everything and it all matches what is in the document. I can go from the guest to the host (ping, ssh, etc) but not from that guest to another real host on the same real LAN. I am patching the relevant info below: ---------------------------------- net.ipv4.conf.all.forwarding = 1 net.ipv4.conf.p32p1.forwarding = 1 net.ipv4.conf.virbr8.forwarding = 1 -------------------------------- <network> <name>routed</name> <uuid>1b2a0197-e708-165c-f266-6822e73cfbdd</uuid> <forward dev='p32p1' mode='route'> <interface dev='p32p1'/> </forward> <bridge name='virbr8' stp='on' delay='0' /> <mac address='52:54:00:B9:59:49'/> <domain name='routed'/> <ip address='192.168.123.1' netmask='255.255.255.0'> <dhcp> <range start='192.168.123.128' end='192.168.123.254' /> </dhcp> </ip> </network> ------------------------------- Chain INPUT (policy ACCEPT 0 packets, 0 bytes) pkts bytes target prot opt in out source destination 0 0 ACCEPT udp -- virbr8 * 0.0.0.0/0 0.0.0.0/0 udp dpt:53 0 0 ACCEPT tcp -- virbr8 * 0.0.0.0/0 0.0.0.0/0 tcp dpt:53 0 0 ACCEPT udp -- virbr8 * 0.0.0.0/0 0.0.0.0/0 udp dpt:67 0 0 ACCEPT tcp -- virbr8 * 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 -- p32p1 virbr8 0.0.0.0/0 192.168.123.0/24 0 0 ACCEPT all -- virbr8 p32p1 192.168.123.0/24 0.0.0.0/0 0 0 ACCEPT all -- virbr8 virbr8 0.0.0.0/0 0.0.0.0/0 0 0 REJECT all -- * virbr8 0.0.0.0/0 0.0.0.0/0 reject-with icmp-port-unreachable 0 0 REJECT all -- virbr8 * 0.0.0.0/0 0.0.0.0/0 reject-with icmp-port-unreachable ------------------------------ This is Fedora 17 with an updated libvirt 0.10.1-4.fc17 [another system with the same "problem" is running libvirt 0.10.2-1.fc17]. Anyone know what is going on? BTW, I searched bugzilla for the comment containing the string routed filed against packages libvirt, qemu, qemu-kvm, or kvm ...Result .. no hits! If this is really a bug rather than something I did or did not do, then nobody is using routed virtual networks. BTW, I have a real F17 systems sitting between to networks on two different NICs and it routes things nicely, thank you very much. It does work but not for the virtual networks. I would really like it to be something I am missing. Gene

2 1

[libvirt-users] libvirt Java to connect at the XEN
by Felipe Oliveira Gutierrez 03 Oct '12

03 Oct '12

Hi people, I am new using libvirt for Java I created a class to test my conecction with XEN, but it is throwing a exception that I can't figure out how I solve this. Does anyone knoe how to configure it correctly? I cat use this class from the command line: $ javac -classpath /usr/java/jdk1.6.0_34/bin/libvirt-0.4.9.jar test.java $ java -classpath .:/usr/java/jdk1.6.0_34/bin/jna.jar:/usr/java/jdk1.6.0_34/bin/libvirt-0.4.9.jar test and it connect to the XEN. But when I put the code on my eclipse it doesn't work any more. ... conn = new Connect("xen:///", true); .... libvir: XML-RPC error : authentication failed: Error checking for authorization org.libvirt.unix.manage: Remote Exception invoking org.freedesktop.PolicyKit1.Authority.CheckAuthorization() on /org/freedesktop/PolicyKit1/Authority at name org.freedesktop.PolicyKit1: org.freedesktop.PolicyKit1.Error.Failed: Action org.libvirt.unix.manage is not registered exception caught:org.libvirt.LibvirtException: authentication failed: Error checking for authorization org.libvirt.unix.manage: Remote Exception invoking org.freedesktop.PolicyKit1.Authority.CheckAuthorization() on /org/freedesktop/PolicyKit1/Authority at name org.freedesktop.PolicyKit1: org.freedesktop.PolicyKit1.Error.Failed: Action org.libvirt.unix.manage is not registered level:VIR_ERR_ERROR code:VIR_ERR_AUTH_FAILED domain:VIR_FROM_RPC hasConn:false hasDom:false hasNet:false message:authentication failed: Error checking for authorization org.libvirt.unix.manage: Remote Exception invoking org.freedesktop.PolicyKit1.Authority.CheckAuthorization() on /org/freedesktop/PolicyKit1/Authority at name org.freedesktop.PolicyKit1: org.freedesktop.PolicyKit1.Error.Failed: Action org.libvirt.unix.manage is not registered str1:authentication failed: %s str2:Error checking for authorization org.libvirt.unix.manage: Remote Exception invoking org.freedesktop.PolicyKit1.Authority.CheckAuthorization() on /org/freedesktop/PolicyKit1/Authority at name org.freedesktop.PolicyKit1: org.freedesktop.PolicyKit1.Error.Failed: Action org.libvirt.unix.manage is not registered str3:null int1:-1 int2:-1 Exception in thread "main" java.lang.NullPointerException at TestLibVirt.main(TestLibVirt.java:88) -- *-- Felipe Oliveira Gutierrez* *-- **lipe.82(a)gmail.com* <lipe.82(a)gmail.com> *-- https://sites.google.com/site/lipe82/Home/diaadia*

1 0

[libvirt-users] Request to participate to the list
by Felipe Oliveira Gutierrez 02 Oct '12

02 Oct '12

Hi, I need to use libvirt on my eucalyptus server. Can I go into to the list? Do I have to install libvirt-0.10.2.tar.gz alone, or I need to install libvirt-java-0.4.9.tar.gz after to developing codes using java? Bets Regards, Felipe -- *-- Felipe Oliveira Gutierrez* *-- **lipe.82(a)gmail.com* <lipe.82(a)gmail.com> *-- https://sites.google.com/site/lipe82/Home/diaadia*

2 1

[libvirt-users] High availability for guests
by Renich Bon Ciric 30 Sep '12

30 Sep '12

Hello, What is the recommended way to offer high availability to Guests? For example, let host1, host2 and host3 be libvirt and KVM/Qemu enabled. If I start a guest in host1, how can I guarantee that it will stay online if host1 goes down? GlusterFS, for example, would take care of storage; but what about CPU and RAM? How can this be accomplished? Thank you for any feedback or comment in adavance. -- It's hard to be free... but I love to struggle. Love isn't asked for; it's just given. Respect isn't asked for; it's earned! Renich Bon Ciric http://www.woralelandia.com/ http://www.introbella.com/

2 3

[libvirt-users] Inconsistent iptables forwarding rules for virtual networks?
by Marwan Tanager 27 Sep '12

27 Sep '12

Hi everyone. Those are the iptables forwarding rules associated with the two virtual networks on my machine: ----------------------------------------------------------------------------------------- -A FORWARD -d 192.168.100.0/24 -o virbr1 -m state --state RELATED,ESTABLISHED -j ACCEPT -A FORWARD -s 192.168.100.0/24 -i virbr1 -j ACCEPT -A FORWARD -i virbr1 -o virbr1 -j ACCEPT -A FORWARD -o virbr1 -j REJECT --reject-with icmp-port-unreachable -A FORWARD -i virbr1 -j REJECT --reject-with icmp-port-unreachable -A FORWARD -d 192.168.122.0/24 -o virbr0 -m state --state RELATED,ESTABLISHED -j ACCEPT -A FORWARD -s 192.168.122.0/24 -i virbr0 -j ACCEPT -A FORWARD -i virbr0 -o virbr0 -j ACCEPT -A FORWARD -o virbr0 -j REJECT --reject-with icmp-port-unreachable -A FORWARD -i virbr0 -j REJECT --reject-with icmp-port-unreachable ----------------------------------------------------------------------------------------- Using this setup I can ping from a guest on 192.168.100.0/24 to a guest on 192.168.122.0/24, however the reverse is not possible (I get 'port unreachable' icmp messages). This is caused by the fourth rule, which rejects packets forwarded to virbr1. Moving the fourth rule to the end, obviously eliminates this problem. So, is this default setup intentional for some reason, or should the rules just be rearranged by libvirt, so that any rule on the FORWARD chain which has a REJECT target (which reject forwarding "to" some virtual interface) would go to the end of the chain, and thus, allowing the virtual networks to reach each other by default? Thanks. Marwan

2 2