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-devel

[Xen-devel] Re: stubdom (with vif) startup failure

To: "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: [Xen-devel] Re: stubdom (with vif) startup failure
From: Dulloor <dulloor@xxxxxxxxx>
Date: Fri, 20 Feb 2009 15:56:47 -0500
Delivery-date: Fri, 20 Feb 2009 12:58:41 -0800
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:content-type; bh=RUbqNEcxCHha9itJm/H6y0YkLVNDi/m5SyxEJ7VO1AI=; b=WNQtOwJcUt/YYtcfRSBJoXk9mHSvkx/HMJHrzvaOV//m0/1kwZXpx4c02T80S2/aaq c5dU2cypTvbPSZ1k/Qb30OOj6rj7mNi5lCZq61zMdXruha7lsslrLvH637m9QueM5wJm Eqs9CtlctA+WHJ059EnbTN0rLy8+3rT/ygvzQ=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=DArR/ifyg23cfVjorb5yglwSYGaDlmoSzL+iHgz8eaJV5RDsSmflIvNcgXLwY9VOcJ AzvTlAIxuwoEKblaOE7RytrefdIQOG0fIdGTpEQaa67IYj1nlLhkRfa0iqMDby8oqPzM 0Qnt9jpcv8mg/uPzsrmioK2XWVRndkuBqIxyw=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <940bcfd20902201224k6944bf49yc1b9de998966b26f@xxxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <940bcfd20902201224k6944bf49yc1b9de998966b26f@xxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Problem is irrespective of vif-bridge or vif-nat. With vif-bridge, I get the following in qemu-dm.log :

***
xm create -c /data/xen-devel/xen-guest-confs/linux.hvm-dm target=13 memory=32 videoram=4 extra=" -d 13"
Using config file "/data/xen-devel/xen-guest-confs/linux.hvm-dm".
Started domain linux.hvm-dm (id=14)
Unexpected error: <type 'exceptions.OSError'>

Please report to xen-devel@xxxxxxxxxxxxxxxxxxx
Traceback (most recent call last):
  File "/usr/sbin/xm", line 10, in <module>
    main.main(sys.argv)
  File "//usr/lib/python/xen/xm/main.py", line 2953, in main
    _, rc = _run_cmd(cmd, cmd_name, args)
  File "//usr/lib/python/xen/xm/main.py", line 2977, in _run_cmd
    return True, cmd(args)
  File "<string>", line 1, in <lambda>
  File "//usr/lib/python/xen/xm/main.py", line 1381, in xm_importcommand
    cmd.main([command] + args)
  File "//usr/lib/python/xen/xm/create.py", line 1329, in main
    do_console(sxp.child_value(config, 'name', -1))
  File "//usr/lib/python/xen/xm/create.py", line 1356, in do_console
    (p, rv) = os.waitpid(cpid, os.WNOHANG)
OSError: [Errno 10] No child processes

***

"brctl show" output is :
bridge name     bridge id               STP enabled     interfaces
eth0            8000.001d0907323d       no              peth0

***

thanks
dulloor

On Fri, Feb 20, 2009 at 3:24 PM, Dulloor <dulloor@xxxxxxxxx> wrote:
Hey,

I have a problem getting a linux HVM (stubdom) working, when I have a network(vif)  configuration. I am at xen-unstable tip and using kubuntu hardy.

***
I mean -
vif = [ 'ip=10.0.0.5', 'type=ioemu, ip=10.0.0.1' ] is a problem, and
vif = [ '', 'type=ioemu, ip=10.0.0.1' ] is not.
***

***
The qemu-log shows the following error (added an extra print info) -
xm create -c /data/xen-devel/xen-guest-confs/linux.hvm-dm target=8 memory=32 videoram=4 extra=" -d 8"
Using config file "/data/xen-devel/xen-guest-confs/linux.hvm-dm".
Error: Device 1 (vif) could not be connected. ip route add 10.0.0.1 dev vif9.1 src 10.0.0.128 failed
***

***
The vif interfaces get created properly (as shown by udevmonitor) :
UDEV  [1235161178.765079] add      /devices/xen-backend/vfb-8-0 (xen-backend)
UEVENT[1235161178.798868] add      /devices/xen-backend/vif-8-0 (xen-backend)
UDEV  [1235161178.800035] add      /devices/xen-backend/vif-8-0 (xen-backend)
UEVENT[1235161178.808032] add      /class/net/vif8.0 (net)
UEVENT[1235161178.808056] online   /devices/xen-backend/vif-8-0 (xen-backend)
UDEV  [1235161178.809192] add      /class/net/vif8.0 (net)
UDEV  [1235161178.809873] online   /devices/xen-backend/vif-8-0 (xen-backend)
UDEV  [1235161178.927119] add      /devices/xen-backend/console-8-0 (xen-backend)
UDEV  [1235161179.433184] add      /devices/xen-backend/vkbd-9-0 (xen-backend)
UDEV  [1235161179.469299] add      /devices/xen-backend/vfb-9-0 (xen-backend)
UDEV  [1235161179.505958] add      /devices/xen-backend/vbd-9-768 (xen-backend)
UEVENT[1235161179.545319] add      /devices/xen-backend/vbd-9-5632 (xen-backend)
UDEV  [1235161179.549514] add      /devices/xen-backend/vbd-9-5632 (xen-backend)
UEVENT[1235161179.588920] add      /devices/xen-backend/vif-9-0 (xen-backend)
UDEV  [1235161179.589735] add      /devices/xen-backend/vif-9-0 (xen-backend)
UEVENT[1235161179.592308] add      /class/net/vif9.0 (net)
UEVENT[1235161179.592325] online   /devices/xen-backend/vif-9-0 (xen-backend)
UDEV  [1235161179.592955] add      /class/net/vif9.0 (net)
UDEV  [1235161179.593645] online   /devices/xen-backend/vif-9-0 (xen-backend)
UEVENT[1235161179.645029] add      /devices/xen-backend/vif-9-1 (xen-backend)
UDEV  [1235161179.645522] add      /devices/xen-backend/vif-9-1 (xen-backend)
UEVENT[1235161179.647080] add      /class/net/vif9.1 (net)
UEVENT[1235161179.648318] online   /devices/xen-backend/vif-9-1 (xen-backend)
UDEV  [1235161179.648959] add      /class/net/vif9.1 (net)
UDEV  [1235161179.649637] online   /devices/xen-backend/vif-9-1 (xen-backend)
UEVENT[1235161179.769995] add      /devices/xen-backend/console-9-0 (xen-backend)
UDEV  [1235161179.771212] add      /devices/xen-backend/console-9-0 (xen-backend)
UEVENT[1235161180.147784] remove   /devices/xen-backend/vkbd-9-0 (xen-backend)
UDEV  [1235161180.148338] remove   /devices/xen-backend/vkbd-9-0 (xen-backend)
UEVENT[1235161180.174375] remove   /devices/xen-backend/vfb-9-0 (xen-backend)
UDEV  [1235161180.174753] remove   /devices/xen-backend/vfb-9-0 (xen-backend)
UEVENT[1235161180.199455] remove   /devices/xen-backend/console-9-0 (xen-backend)
UDEV  [1235161180.199927] remove   /devices/xen-backend/console-9-0 (xen-backend)
UEVENT[1235161180.217561] remove   /devices/xen-backend/vbd-9-768 (xen-backend)
UEVENT[1235161180.218699] remove   /devices/xen-backend/vbd-9-5632 (xen-backend)
UEVENT[1235161180.219699] offline  /devices/xen-backend/vif-9-0 (xen-backend)
UDEV  [1235161180.220173] remove   /devices/xen-backend/vbd-9-768 (xen-backend)
UDEV  [1235161180.220930] offline  /devices/xen-backend/vif-9-0 (xen-backend)
UDEV  [1235161180.221188] remove   /devices/xen-backend/vbd-9-5632 (xen-backend)
UEVENT[1235161180.416047] remove   /class/net/vif9.0 (net)
UEVENT[1235161180.416328] remove   /devices/xen-backend/vif-9-0 (xen-backend)
UEVENT[1235161180.416673] offline  /devices/xen-backend/vif-9-1 (xen-backend)
UDEV  [1235161180.419046] remove   /class/net/vif9.0 (net)
UDEV  [1235161180.419587] remove   /devices/xen-backend/vif-9-0 (xen-backend)
UDEV  [1235161180.420152] offline  /devices/xen-backend/vif-9-1 (xen-backend)
UEVENT[1235161180.596000] remove   /class/net/vif9.1 (net)
UEVENT[1235161180.596261] remove   /devices/xen-backend/vif-9-1 (xen-backend)
UDEV  [1235161180.598250] remove   /class/net/vif9.1 (net)
UDEV  [1235161180.608525] remove   /devices/xen-backend/vif-9-1 (xen-backend)
***

Any help is appreciated.

thanks
dulloor



_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
<Prev in Thread] Current Thread [Next in Thread>