From mboxrd@z Thu Jan 1 00:00:00 1970 From: Erik Brakkee Subject: UDP problem with virtio... Date: Fri, 25 May 2012 22:55:37 +0200 Message-ID: <4FBFF1C9.2030606@brakkee.org> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="------------070008020108060502090502" To: KVM list Return-path: Received: from smtp-vbr6.xs4all.nl ([194.109.24.26]:4400 "EHLO smtp-vbr6.xs4all.nl" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932697Ab2EYUzj (ORCPT ); Fri, 25 May 2012 16:55:39 -0400 Received: from brakkee.org (a83-163-128-75.adsl.xs4all.nl [83.163.128.75]) by smtp-vbr6.xs4all.nl (8.13.8/8.13.8) with SMTP id q4PKtad3055645 for ; Fri, 25 May 2012 22:55:37 +0200 (CEST) (envelope-from erik@brakkee.org) Received: from pelican.lan (pelican.fritz.box [192.168.178.30]) by brakkee.org (Postfix) with ESMTP id B464A6F89F for ; Fri, 25 May 2012 22:55:34 +0200 (CEST) Sender: kvm-owner@vger.kernel.org List-ID: This is a multi-part message in MIME format. --------------070008020108060502090502 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Hi, I am running a guest that exposes a NFS share to be used by a TViX box. The TViX box is not that advanced and uses NFS over UDP instead of TCP. What I am seeing is that when I use the virtio network driver, the TViX box cannot mount the filesystem. However, when I use rtl8139 instead, it can. The problem is easily reproduced: 1. Create a guest that uses a virtio network interface (bridging setup) 2. Expose an NFS share on the guest 3. mount the NFS share using 'mount -o udp host:/share /localdir' 4. verify that the NFS share cannot be mounted. 5. Modify the guest to use rtl8139 device emulation and stop the guest and start it 6. mount the NFS share using 'mount -o udp host:/share /localdir' 7. Verify tha the NFS share can be mounted Now the bug reporting guidelines say that I should always use the latest KVM version but compiling KVM from source and using that is not really an option. The server is important enough not to mess around with. Therefore, my question is whether this problem has been seen before or not. My configuration is as follows: *Host* centos 6.2 uname -a gives "Linux falcon.fritz.box 2.6.32-220.17.1.el6.x86_64 #1 SMP Wed May 16 00:01:37 BST 2012 x86_64 x86_64 x86_64 GNU/Linux" KVM software: qemu-kvm-0.12.1.2-2.209.el6_2.5.x86_64 *Guest* OpenSuSE 11.3 uname -a gives "Linux shikra 2.6.34.7-0.7-default #1 SMP 2010-12-13 11:13:53 +0100 x86_64 x86_64 x86_64 GNU/Linux" I also see in the instructions I should try running qemu with some alternative switches, but I am not running qemu directly. I am using virt-manager and a domain.xml to configure how qemu runs. How should I modify the domain.xml to help in troubleshooting this issue? Cheers Erik PS. the domain.xml is attached. --------------070008020108060502090502 Content-Type: text/xml; name="shikra.xml" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="shikra.xml" shikra 3a524d9f-a9df-4280-d0d7-e7562a860147 6291456 6291456 8 hvm destroy restart restart /usr/libexec/qemu-kvm