WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-users

[Xen-users] Failing to provision a VM when vif MTU > 1500 with patches a

To: "xen-users@xxxxxxxxxxxxxxxxxxx" <xen-users@xxxxxxxxxxxxxxxxxxx>
Subject: [Xen-users] Failing to provision a VM when vif MTU > 1500 with patches applied
From: Digimer <linux@xxxxxxxxxxx>
Date: Thu, 28 Apr 2011 18:13:59 -0400
Delivery-date: Thu, 28 Apr 2011 15:15:31 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.15) Gecko/20110307 Fedora/3.1.9-0.39.b3pre.fc14 Thunderbird/3.1.9
Hi all,

  I'm testing the patches from rhbz 697021 and 697310. I've run into an
odd problem, which I expect is just the matter of an exit code with
either xen-network-common.sh (patched) or vif-bridge.

Bug links:
- https://bugzilla.redhat.com/show_bug.cgi?id=697021
- https://bugzilla.redhat.com/show_bug.cgi?id=697310

  When I try to provision a new VM, the VM starts paused. If I wait long
enough, it fails (see below). If I drop the call to the background with
<ctrl>+<z> and then unpause the VM, it will be 50/50 chance whether it
stays up and running or is destroyed when the caller script gives up on
vif.

  Regardless, I see that the vifX.Y interface was, in fact, created and
is up. When I unpause the VM, data passes over the vif, so I know it's
working, too.

  Here is what I get from the terminal where I provision the VM:

====
virt-install --connect xen \
> --name vm0002_pppoe \
> --ram 2048 \
> --arch x86_64 \
> --vcpus 1 \
> --cpuset 1-7 \
> --location http://10.255.0.1/f9/x86_64/img \
> --os-type linux \
> --os-variant rhel5.4 \
> --disk path=/dev/drbd_x4_vg0/vm0002_1 \
> --network bridge=xenbr0 \
> --network bridge=xenbr2 \
> --vnc \
> --paravirt


Starting install...
Retrieving file .treeinfo...                             |  390 B
00:00
Retrieving file vmlinuz...                               | 1.8 MB
00:00
Retrieving file initrd.img...                            |  16 MB
00:01
ERROR    POST operation failed: xend_post: error from xen daemon:
(xend.err 'Device 1 (vif) could not be connected. Hotplug scripts not
working.')
Domain installation may not have been
 successful.  If it was, you can restart your domain
 by running 'virsh start vm0002_pppoe'; otherwise, please
 restart your installation.
ERROR    POST operation failed: xend_post: error from xen daemon:
(xend.err 'Device 1 (vif) could not be connected. Hotplug scripts not
working.')
Traceback (most recent call last):
  File "/usr/sbin/virt-install", line 892, in ?
    main()
  File "/usr/sbin/virt-install", line 754, in main
    start_time, guest.start_install)
  File "/usr/sbin/virt-install", line 816, in do_install
    dom = install_func(conscb, progresscb, wait=(not wait))
  File "/usr/lib/python2.4/site-packages/virtinst/Guest.py", line 541,
in start_install
    return self._do_install(consolecb, meter, removeOld, wait)
  File "/usr/lib/python2.4/site-packages/virtinst/Guest.py", line 633,
in _do_install
    self.domain = self.conn.createLinux(install_xml, 0)
  File "/usr/lib64/python2.4/site-packages/libvirt.py", line 1277, in
createLinux
    if ret is None:raise libvirtError('virDomainCreateLinux() failed',
conn=self)
libvirtError: POST operation failed: xend_post: error from xen daemon:
(xend.err 'Device 1 (vif) could not be connected. Hotplug scripts not
working.')
====

  And here is what I see in /var/log/messages.

====
Apr 28 18:06:00 xenmaster004 kernel: device vif2.0 entered promiscuous mode
Apr 28 18:06:00 xenmaster004 kernel: ADDRCONF(NETDEV_UP): vif2.0: link
is not ready
Apr 28 18:07:40 xenmaster004 kernel: xenbr0: port 3(vif2.0) entering
disabled state
Apr 28 18:07:40 xenmaster004 kernel: device vif2.0 left promiscuous mode
Apr 28 18:07:40 xenmaster004 kernel: xenbr0: port 3(vif2.0) entering
disabled state
====

  Any clues?

-- 
Digimer
E-Mail: digimer@xxxxxxxxxxx
AN!Whitepapers: http://alteeve.com
Node Assassin:  http://nodeassassin.org

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users

<Prev in Thread] Current Thread [Next in Thread>
  • [Xen-users] Failing to provision a VM when vif MTU > 1500 with patches applied, Digimer <=