- Users - libvirt List Archives

[libvirt-users] Fwd: unable to ping from guests in virbr0 to guests in virbr1 network
by Marwan Tanager 19 Nov '12

19 Nov '12

---------- Forwarded message ---------- From: mallapadi niranjan <niranjan.ashok(a)gmail.com> Date: Mon, Nov 19, 2012 at 7:30 PM Subject: Re: [libvirt-users] unable to ping from guests in virbr0 to guests in virbr1 network To: Marwan Tanager <marwan.tngr(a)gmail.com> On Mon, Nov 19, 2012 at 7:51 PM, Marwan Tanager <marwan.tngr(a)gmail.com>wrote: > On Mon, Nov 19, 2012 at 12:09:53PM +0530, mallapadi niranjan wrote: > > Hi all, > > > > I have 3 guests (2-RHEL4 and 1 RHEL6) and have some issues regarding > > networking between them. The 2 RHEL4 system's use default bridge virbr0 > and > > get ip's of range 192.168.122.0/24 (192.168.122.207, 192.168.122.167) > > > > I created another bridge (virbr1) with NAT forwarding (no dhcp). The > > network i choose was 192.168.100.0/24. And the third system (RHEL6) was > > assigned static ip-addres 192.168.100.101, > > > > >>From the RHEL6 system which uses virbr1 is able to ping systems in > > 192.168.122.0/24 series , but guest systems in 192.168.122.0/24 are not > > able to ping RHEL6 system (in virbr1) network. > > > > >>From the RHEL4 guests i am able to ping the gateway ip's > (192.168.122.1, > > 192.168.100.1) , but not the RHEL6 system > > > > > > Versions: > > Fedora release 16 (Verne) > > libvirt-0.9.6.3-1.fc16.x86_64 > > qemu-kvm-0.15.1-8.fc16.x86_64 > > > > Any hints on what could be the problem > > The problem is caused by the relative order of the iptables rules for > those two > networks. > > When libvirt created virbr1 for the network 192.168.100.0/24 it inserted a > couple of iptables rules on the FORWARDING chain for this interface, but it > added them before the rules of virbr0 on the same chain. Those rules > basically > are ordered as follows (at least on my system which I suspect is different > from > yours since I also had the same problem): > > 1. Forward packets destined for the interface that are part of an > established > connection. > 2. Forward packets coming from the interface. > 3. Forward packets coming from and destined to the same interface > (loopback). > 4. Reject forwarding anything else to the interface. > 5. Reject forwarding anything else from the interface. > okay that seems to be the behaviour: hain FORWARD (policy ACCEPT) target prot opt source destination ACCEPT all -- 0.0.0.0/0 192.168.100.0/24 state RELATED,ESTABLISHED ACCEPT all -- 192.168.100.0/24 0.0.0.0/0 ACCEPT all -- 0.0.0.0/0 0.0.0.0/0 REJECT all -- 0.0.0.0/0 0.0.0.0/0 reject-with icmp-port-unreachable REJECT all -- 0.0.0.0/0 0.0.0.0/0 reject-with icmp-port-unreachable ACCEPT all -- 0.0.0.0/0 192.168.200.0/24 state RELATED,ESTABLISHED ACCEPT all -- 192.168.200.0/24 0.0.0.0/0 ACCEPT all -- 0.0.0.0/0 0.0.0.0/0 REJECT all -- 0.0.0.0/0 0.0.0.0/0 reject-with icmp-port-unreachable REJECT all -- 0.0.0.0/0 0.0.0.0/0 reject-with icmp-port-unreachable ACCEPT all -- 0.0.0.0/0 192.168.122.0/24 state RELATED,ESTABLISHED ACCEPT all -- 192.168.122.0/24 0.0.0.0/0 ACCEPT all -- 0.0.0.0/0 0.0.0.0/0 REJECT all -- 0.0.0.0/0 0.0.0.0/0 reject-with icmp-port-unreachable REJECT all -- 0.0.0.0/0 0.0.0.0/0 reject-with icmp-port-unreachable REJECT all -- 0.0.0.0/0 0.0.0.0/0 reject-with icmp-host-prohibited I can ping from 192.168.100.0/24 -> 192.168.122.0/24 (but not the viceversa) > > Since those rules are inserted for every interface libvirt adds in this > order, > you can only ping from one interface to another if the set of rules for the > interface you are pinging from comes before that of the one you're pinging > to. > Otherwise, rule number 4 of the destination interface will get in the way > since > iptables matches the packets against the rules in a chain according to > their > order on it. > > A possible workaround: > > iptables-save >/path/to/iptables/dump/file > > then, edit the file to move all relevant rules that REJECT things on the > FORWARDING chain to the end of the chain. > > then put this command in your rc.local script: > > cat /path/to/iptables/dump/file | iptables-restore > > This solution is not reliable though because you will need to update the > file > containing the rules every time you add a new virtual network or update the > iptables rules for some other reason. > Right , > > Also, I hinted before at this problem on the list and someone pointed me > that > it's a bug, but nobody confirmed. Read my message on this topic with the > subject: Inconsistent iptables forwarding rules for virtual networks, to > get a > clearer picture. > > Okay, will look in to that mail > > Marwan >

1 0

[libvirt-users] unable to ping from guests in virbr0 to guests in virbr1 network
by mallapadi niranjan 19 Nov '12

19 Nov '12

Hi all, I have 3 guests (2-RHEL4 and 1 RHEL6) and have some issues regarding networking between them. The 2 RHEL4 system's use default bridge virbr0 and get ip's of range 192.168.122.0/24 (192.168.122.207, 192.168.122.167) I created another bridge (virbr1) with NAT forwarding (no dhcp). The network i choose was 192.168.100.0/24. And the third system (RHEL6) was assigned static ip-addres 192.168.100.101, >From the RHEL6 system which uses virbr1 is able to ping systems in 192.168.122.0/24 series , but guest systems in 192.168.122.0/24 are not able to ping RHEL6 system (in virbr1) network. >From the RHEL4 guests i am able to ping the gateway ip's (192.168.122.1, 192.168.100.1) , but not the RHEL6 system Versions: Fedora release 16 (Verne) libvirt-0.9.6.3-1.fc16.x86_64 qemu-kvm-0.15.1-8.fc16.x86_64 Any hints on what could be the problem Regards Niranjan

3 4

[libvirt-users] how to make the volume's format to qcow2 when creating volume
by zhijun liu 19 Nov '12

19 Nov '12

hi,all the following are files of pool and volume. storage pool is based on logical(LVM) and iscsi,now I create volume specified the format to "qcow2" *pool.xml* <pool type='logical'> <name>pool_190</name> <source> <device path='/dev/disk/by-path/ip-192.168.0.190:3260-iscsi-iqn.2012-11.com.cloudking:server.target1-lun-1'/> </source> <target> <path>/dev/pool_190</path> </target> </pool> *volume.xml* <?xml version="1.0" encoding="UTF-8" ?> <volume> <name>volume1</name> <capacity unit="GB">1</capacity> <target> <format type="qcow2" /> </target> </volume> *the problmes is :when the volume created successfully,However, the volume's format is 'raw'* like this image: /dev/pool_190/volume1 *file format: raw* virtual size: 1.0G (1073741824 bytes) disk size: 0 how to resolve this troublesome. libvirt :0.9.8 os:ubuntu12.04 many thanks for any reply....

2 1

Re: [libvirt-users] Failed to build libvirt-1.0.0-1.fc17.src.rpm on a CentOS 6.3 system
by Abbas 16 Nov '12

16 Nov '12

On 11/17/2012 02:47 AM, Frank Shi wrote: > Thanks much Abbas for your prompt response. Right, I have fixed all the > dependency issues. It compiled but failed during running test cases. I > prefer building from src-rpm is because I need to install the package onto > other machines. Building from src-rpm can generate rpm so it makes > future deploy easier. Then the start off point will be CentOS' srpms. You might still need to do some patchwork and testing before you get a working rpm (a reason why there's no third party repo for latest kvm and libvirt). Installing on multiple machines sounds like you tend towards stability and Fedora's packages won't do that job anyway! > Anyway, follow your recommendation, I downloaded the source tar and tried > to compile it from source. This time I am seeing following problems. What > could be the problem? > > Thanks, Frank > > =============== > $ tar xvf libvirt-1.0.0-rc1.tar.gz > $ libvirt-1.0.0 > $ ./configure Try using the supplied autogen script first. > libxl/libxl_conf.c:471: error: 'libxl_domain_build_info' It's a missing dep error. Quick time-savers for latest KVM and Libvirt (on latest CentOS 6.3): # qemu-kvm deps yum install gcc pkgconfig SDL-devel zlib-devel alsa-lib-devel pciutils-devel gnutls-devel glib glib2-devel ./configure --prefix=/usr --sysconfdir=/etc make && make install # libvirt deps yum install git python-devel libtool patch libxml2 libxml2-devel yajl-devel device-mapper-devel libnl-devel ./autogen-sh --system make && make install # packages to remove qemu-img qemu-kvm libvirt libvirt-client virt-top The kvm_intel manually loaded of course! ------ bassu

1 0

[libvirt-users] Failed to build libvirt-1.0.0-1.fc17.src.rpm on a CentOS 6.3 system
by Frank Shi 16 Nov '12

16 Nov '12

Hi, List, I am seeing following problems when building libvirt-1.0.0-1.fc17.src.rpm. The first failed test case is xml2sexprtest as you can see below. $ sudo rpmbuild -ba SPECS/libvirt.spec + make check TEST: virshtest ........................................ 40 ........... 51 OK TEST: sockettest ...................................... 38 OK TEST: virbuftest .... 4 OK TEST: commandtest ..................... 21 OK TEST: virhashtest .............. 14 OK TEST: virnetmessagetest ..... 5 OK TEST: virnetsockettest ............... 15 OK TEST: viratomictest .. 2 OK TEST: utiltest ... 3 OK TEST: virnettlscontexttest ........................................ 40 ........ 48 OK TEST: shunloadtest . 1 OK TEST: virtimetest ............... 15 OK TEST: viruritest .................. 18 OK TEST: virkeyfiletest . 1 OK TEST: virauthconfigtest ...... 6 OK TEST: virbitmaptest ...... 6 OK TEST: virlockspacetest ....... 7 OK TEST: securityselinuxtest TEST: virdrivermoduletest ....... 7 OK TEST: xml2sexprtest .!.!!.....................!..!!!!.!!!!!! 40 !!!!!!!!!!... 53 FAIL TEST: sexpr2xmltest ........................................ 40 ........... 51 OK TEST: xmconfigtest ..............!.!.!.!.!.!.!.!.!.!.!.!.!. 40 !.!.!.!.!.!.!.!.!...!.!.!. 66 FAIL TEST: xencapstest .......... 10 OK TEST: statstest TEST: reconnect TEST: qemuxml2argvtest ........................................ 40 ........................................ 80 ........................................ 120 ........................................ 160 ........................................ 200 ........................................ 240 ...... 246 OK TEST: qemuxml2xmltest ........................................ 40 ........................................ 80 ................................... 115 OK TEST: qemuxmlnstest ....... 7 OK TEST: qemuargv2xmltest ........................................ 40 ................................... 75 OK TEST: qemuhelptest ................ 16 OK TEST: domainsnapshotxml2xmltest ....... 7 OK TEST: qemumonitortest .. 2 OK TEST: qemumonitorjsontest !!!!! 5 FAIL TEST: esxutilstest .... 4 OK TEST: vmx2xmltest ........................................ 40 .......... 50 OK TEST: xml2vmxtest ........................................ 40 ..... 45 OK TEST: networkxml2xmltest ................ 16 OK TEST: networkxml2argvtest ......... 9 OK TEST: nwfilterxml2xmltest ........................................ 40 . 41 OK TEST: storagevolxml2xmltest ....... 7 OK TEST: storagepoolxml2xmltest ............. 13 OK TEST: nodedevxml2xmltest ............. 13 OK TEST: interfacexml2xmltest ................... 19 OK TEST: cputest ........................................ 40 .......................... 66 OK TEST: eventtest ............... 15 OK TEST: libvirtdconftest ....................................... 39 OK make[1]: *** [check-TESTS] Error 1 make: *** [check-am] Error 2 error: Bad exit status from /var/tmp/rpm-tmp.E2o2Vs (%check) Bad exit status from /var/tmp/rpm-tmp.E2o2Vs (%check) Not sure whether the failures are related to xml. Anyway, following is a list of xml packages installed, python-lxml-2.2.3-1.1.el6.x86_64 xmldb-api-sdk-0.1-0.4.20011111cvs.1.5.el6.noarch xmlto-0.0.23-3.el6.x86_64 xmlrpc-c-1.16.24-1209.1840.el6.x86_64 xml-commons-resolver-1.1-4.18.el6.x86_64 xmlrpc-c-client-1.16.24-1209.1840.el6.x86_64 xmldb-api-0.1-0.4.20011111cvs.1.5.el6.noarch xmlrpc3-client-3.0-4.15.el6.noarch xmlgraphics-commons-1.3.1-1.1.el6.noarch libxml2-devel-2.7.6-4.el6_2.4.x86_64 libxml2-2.7.6-4.el6_2.4.x86_64 xml-common-0.6.3-32.el6.noarch perl-libxml-perl-0.08-10.el6.noarch libxml2-python-2.7.6-4.el6_2.4.x86_64 xml-commons-apis-1.3.04-3.6.el6.x86_64 # cat /proc/version Linux version 2.6.32-279.el6.x86_64 (mockbuild(a)c6b9.bsys.dev.centos.org) (gcc version 4.4.6 20120305 (Red Hat 4.4.6-4) (GCC) ) #1 SMP Fri Jun 22 12:19:21 UTC 2012 Thanks, Frank

2 1

[libvirt-users] authentication failed, but why?
by huancong deng 16 Nov '12

16 Nov '12

I set the me into the group libvirt and write the config for libvirtd: ================================================== listen_tls = 0 listen_tcp = 0 auth_tcp = "none" mdns_adv = 0 unix_sock_group = "libvirt" unix_sock_ro_perms = "0770" unix_sock_rw_perms = "0770" unix_sock_dir = "/var/run/libvirt" log_filters = "1:libvirt 1:util 1:qemu" log_output = "1:file:/var/log/libvirt/libvirtd.log" max_clients = 500 min_workers = 10 max_workers = 50 max_requests = 50 max_client_requests = 8 =========================================== but I can't login the libvirt: [xxxxxx@u70 ~]$ virsh error : authentication failed: Authorization requires authentication but no agent is available. who can tell me why? thanks a lot. :)

1 0

[libvirt-users] Handling connection closes in (older) Sys::Virt
by Henrik Ahlgren 14 Nov '12

14 Nov '12

I hope this is the correct mailing list for discussing the Sys::Virt Perl module. It appears that the most recent version has a new method called register_close_callback that, I believe, can be used to catch errors when the connection to libvirt is closed, e.g. due to libvirt restart or a network related issue. (I've been testing this simply by killing the the SSH process in the libvirt server.) However, Debian still ships libvirt 0.9.12 in stable backports and testing, as probably do many other mainstream distributions. The latest Perl bindings that can be installed from CPAN is thus 0.9.12 and it does not have support for close callbacks. Not only that, when a Perl program loses the (ssh) connection to libvirt, Perl just crashes: Program received signal SIGPIPE, Broken pipe. 0x00007ffff73de0d0 in __write_nocancel () from /lib/libpthread.so.0 Setting a $SIG{PIPE} handler does not seem to help. Is there any possibility of a Perl program surviving and gracefully handling a closed libvirt connection with libvirt version 0.9.12 or older? Henrik

2 4

[libvirt-users] Virt-io Kernels for older RHEL/CentOS versions
by Chandana De Silva 14 Nov '12

14 Nov '12

All, I need to run a number of guests which user older distributions of RHEL and CentOS on an RHEL 6.3 host. The versions are; 4.8 - i386 5.1 - i386 5.2 - x86_64 5.3 - i386 Currently I am running these with the E1000 network driver and the IDE driver. Where can I find kernels (or modules) for virtio for these OS's ? Thanks in advance Chandana

2 2

[libvirt-users] virt-install kickstart local file
by Joe Linoff 13 Nov '12

13 Nov '12

Hi Everybody: I am trying to get virt-install to work with a kickstart file that is on the local file system. I tried using the --initrd-inject="/tmp" --extra-args="ks=file:/myks.cfg" but I got this error message: ERROR --extra-args only work if specified with --location. Here is the basic command: virt-install \ --accelerate \ --cdrom /tools/iso/CentOS-6.3-x86_64-bin-DVD1.iso \ --disk device=disk,path="/var/lib/libvirt/images/myguest.img" \ --graphics vnc \ --name myguest \ --os-type linux \ --os-variant rhel6 \ --ram 2048 \ --vpcus 1,maxvcpus=4 \ --initrd-inject "/tmp" \ --extra-args "ks=file:/myks.cfg" Why do I need the location? I thought that was only used when installatiing from a distribution tree. I am using a DVD ISO image. If I have to use it, how would I specify it? If this approach won't work, I could move the ks.cfg file to an NFS mounted file system but I am not sure what the syntax is for that. I am running this on a CentOS 6.3 system. libvirt: 0.9.10 qemu: 0.12.1 Thank you, Joe

2 1

[libvirt-users] virt-viewer X forwarding through ssh broken since FC17 upgrade?
by Ken Coar 13 Nov '12

13 Nov '12

Ever since I upgraded my laptop from FC15 to FC17, I've been getting this message when I ssh to some RHEL6 hosts inside Red Hat. In particular, I'm trying to do this: virt-viewer --connect \ qemu+ssh://kvm11.devlab.phx1.redhat.com/system \ bork-s01.candlepin.dev.devlab.phx1.redhat.com This is the message I get: X11 forwarding request failed on channel 0 A viewer window pops up for a fraction of a second and then goes away. Using -vvvv on the local ssh command gives a few possibly related messages: debug2: x11_get_proto: /usr/bin/xauth list :0.0 2>/dev/null debug1: Requesting X11 forwarding with authentication spoofing. debug2: channel 0: request x11-req confirm 1 debug1: Requesting authentication agent forwarding. debug2: channel 0: request auth-agent-req(a)openssh.com confirm 0 : debug1: Remote: No xauth program; cannot forward with spoofing. This is new, and, not being an X maven, largely opaque to me. xauth is provided by package xorg-x11-xauth, which is typically *not* installed. Installing it on the system to which I'm trying to ssh gets rid of the message, but doesn't change the up-down behaviour of the viewer window. Temporarily moving my local /usr/bin/xauth leads to this message in addition: Warning: No xauth data; using fake authentication data for X11 forwarding. X11 forwarding request failed on channel 0 Since there's a window popping up at all, I doubt this is directly related to the problem getting the viewer to run. However, on systems *with* xauth installed 'echo $DISPLAY' shows a value, but on those *without* xauth, $DISPLAY is null. (So why am I getting any sort of X popup at all in that case?) Has anyone else seen this, and hopefully have a solution? The problem is actually two-fold: 1. Why 'X11 forwarding failed' and how to get rid of it/revert to behaviour in previous versions; and 2. Why is virt-viewer dying and how to keep it alive. (Again, how to revert to 'it *used* to work' conditions. ;-) ) Thanks! -- #ken B-)} Ken Coar, RHCE, RHCSA, Sanagendamgagwedweinini IT Engineering Tower, Red Hat/RDU "Millennium hand and shrimp!"

2 2