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

Re: [Xen-users] xen3.0 no console on DomU and the error "VmError: Device

To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: Re: [Xen-users] xen3.0 no console on DomU and the error "VmError: Device 0 (vif) could not be connected. Hotplug scripts not working"
From: Ralph Passgang <ralph@xxxxxxxxxxxxx>
Date: Mon, 23 Jan 2006 11:21:41 +0100
Delivery-date: Mon, 23 Jan 2006 10:30:20 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <43D3FE13.7000902@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/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
References: <98339340928B6645A1FCC90B24F3853E01EDEC08@xxxxxxxxxxxxxxxxxxxxxxxxx> <1503588288.20060122185340@xxxxxxxxx> <43D3FE13.7000902@xxxxxxxxxxxxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: KMail/1.9.1
the debian sarge version of udev is too old for xen... please use just hotplug 
instead (reinstall udev), or (as you already said) backport a newer udev 
version to sarge.

Take a look at /etc/hotplug/* and /etc/udev/* for xen scripts. If you 
installed xen from source (and not from packages.debianbase.de's xen3 
packages), then you will have only the udev OR hotplug scripts installed.

If you had for example just hotplug installed at compile time, then you only 
will have the hotplug scripts installed in /etc. if you upgrade later on to 
udev, then udev will not be used because of that... in such a case you need 
to reinstall xen3 then...

--Ralph

Am Sonntag, 22. Januar 2006 22:50 schrieb Tim Sharpe:
> What version of udev are you running? I had this problem til I upgraded
> udev to the latest version.
>
> --Tim
>
> ckras.com Frieder 'cfreak' Kundel wrote:
> > Hello List,
> >
> > I have exactly the same problem, but I'm using debian sarge.
> > Is there any solution?
> >
> >
> > Best regards
> >
> > Frieder 'cfreak' Kundel
> > ckras.com
> > mailto:cfreak@xxxxxxxxx
> >
> > ------------------------------------
> > Von    : Herbert.Meier@xxxxxxxxxxxxxx <Herbert.Meier@xxxxxxxxxxxxxx>
> > An     : <xen-users@xxxxxxxxxxxxxxxxxxx>
> > Datum  : Freitag, 25. November 2005, 14:47
> > Betreff: [Xen-users] xen3.0 no console on DomU and the error "VmError:
> > Device 0 (vif) could not be connected. Hotplug scripts not working"
> >
> > Hi,
> > i have the following problem:
> > I have installed debian "testing" and xen3.0
> > Following Errors when i start DomU "A Debian Stable"
> > *****************************************************************+
> > /domain/0/backend/vif/5/0/hotplug-status.
> > [2005-11-23 17:41:00 xend] ERROR (SrvBase:87) Request wait_for_devices
> > failed. Traceback (most recent call last):
> >   File
> > "/local/scratch/xenod/cron-build/xen-unstable-x86_32.WF4149.dir/xen-unsta
> > ble.hg/dist/install/usr/lib/python/xen/web/SrvBase.py", line 85, in
> > perform File
> > "/local/scratch/xenod/cron-build/xen-unstable-x86_32.WF4149.dir/xen-unsta
> > ble.hg/dist/install/usr/lib/python/xen/xend/server/SrvDomain.py", line
> > 68, in op _wait_for_devices
> >   File
> > "/local/scratch/xenod/cron-build/xen-unstable-x86_32.WF4149.dir/xen-unsta
> > ble.hg/dist/install/usr/lib/python/xen/xend/XendDomainInfo.py", line
> > 1264, in wa itForDevices
> >   File
> > "/local/scratch/xenod/cron-build/xen-unstable-x86_32.WF4149.dir/xen-unsta
> > ble.hg/dist/install/usr/lib/python/xen/xend/XendDomainInfo.py", line 912,
> > in wai tForDevices_
> >   File
> > "/local/scratch/xenod/cron-build/xen-unstable-x86_32.WF4149.dir/xen-unsta
> > ble.hg/dist/install/usr/lib/python/xen/xend/server/DevController.py",
> > line 90, i n waitForDevices
> >   File
> > "/local/scratch/xenod/cron-build/xen-unstable-x86_32.WF4149.dir/xen-unsta
> > ble.hg/dist/install/usr/lib/python/xen/xend/server/DevController.py",
> > line 100, in waitForDevice
> > VmError: Device 0 (vif) could not be connected. Hotplug scripts not
> > working mei51@lnxmei51:/var/log$
> > +++++++++++++++++++++++++++++++++++++++++++++
> > I am not able to get to the DomU Console
> >
> >
> > lnxmei51:/# xm create test
> > Using config file "/etc/xen/test".
> > Error: Device 0 (vif) could not be connected. Hotplug scripts not working
> > lnxmei51:/#
> >
> >
> > lnxmei51:/# xm console test
> > no output
> > console hang !!
> > -------------------------------------------------------------------------
> >------------- Some facts
> > Here my Config File
> > ame ="test"
> > kernel ="/boot/vmlinuz-2.6.12.6-xenU"
> > root ="/dev/sdb1"
> > memory =128
> > disk =
> > ['file:/home/xen/images/test.img,sdb1,w','file:/home/xen/images/test_swa$
> > # network
> > vif = [ 'mac=aa:00:00:00:00:11, bridge=xenbr0' ]
> > nics=1
> > dhcp ="off"
> > ip="145.228.166.251"
> > netmask="255.255.255.224"
> > gateway="145.228.166.225"
> > hostname="test.herbert.com"
> > extra="3"
> > ****************************
> > So the result:
> > DomU works, but I have no chance to get in (no console, no network)
> > lnxmei51:/etc/xen# xm list
> > Name                              ID Mem(MiB) VCPUs State  Time(s)
> > Domain-0                           0      500     1 r-----  5067.3
> > vm01                               2      128     1 --p---     0.0
> > test                               3      128     1 --p---     0.0
> > lnxmei51:/etc/xen#
> > out of xm dmesg
> > Xen version 3.0-devel (xenod@xxxxxxxxxxxx) (gcc version 3.3.3 20040412
> > (Red Hat Linux 3.3.3-7)) Thu Nov 24 04:02:07 GMT 2005
> >  Latest ChangeSet: Wed Nov 23 19:37:33 2005 +0000 8002:8451c6567123
> > -----------------------------------
> > lnxmei51:/# brctl show
> > bridge name     bridge id               STP enabled     interfaces
> > xenbr0          8000.feffffffffff       no              peth0
> >                                                         vif0.0
> > lnxmei51:/#
> >
> >
> > lnxmei51:/# ifconfig
> > eth0      Protokoll:Ethernet  Hardware Adresse 00:04:23:C0:81:FC
> >           inet Adresse:145.228.166.229  Bcast:145.228.166.255 
> > Maske:255.255.255 .224
> >           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
> >           RX packets:110250 errors:0 dropped:0 overruns:0 frame:0
> >           TX packets:1865 errors:0 dropped:0 overruns:0 carrier:0
> >           Kollisionen:0 Sendewarteschlangenlänge:0
> >           RX bytes:8315293 (7.9 MiB)  TX bytes:189061 (184.6 KiB)
> > lo        Protokoll:Lokale Schleife
> >           inet Adresse:127.0.0.1  Maske:255.0.0.0
> >           UP LOOPBACK RUNNING  MTU:16436  Metric:1
> >           RX packets:104 errors:0 dropped:0 overruns:0 frame:0
> >           TX packets:104 errors:0 dropped:0 overruns:0 carrier:0
> >           Kollisionen:0 Sendewarteschlangenlänge:0
> >           RX bytes:6640 (6.4 KiB)  TX bytes:6640 (6.4 KiB)
> > peth0     Protokoll:Ethernet  Hardware Adresse FE:FF:FF:FF:FF:FF
> >           UP BROADCAST RUNNING NOARP MULTICAST  MTU:1500  Metric:1
> >           RX packets:110258 errors:0 dropped:0 overruns:0 frame:0
> >           TX packets:1869 errors:0 dropped:0 overruns:0 carrier:0
> >           Kollisionen:0 Sendewarteschlangenlänge:1000
> >           RX bytes:8758264 (8.3 MiB)  TX bytes:199457 (194.7 KiB)
> >           Basisadresse:0x1100 Speicher:e0580000-e05a0000
> > vif0.0    Protokoll:Ethernet  Hardware Adresse FE:FF:FF:FF:FF:FF
> >           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
> >           RX packets:1865 errors:0 dropped:0 overruns:0 frame:0
> >           TX packets:110250 errors:0 dropped:0 overruns:0 carrier:0
> >           Kollisionen:0 Sendewarteschlangenlänge:0
> >           RX bytes:189061 (184.6 KiB)  TX bytes:8315293 (7.9 MiB)
> > xenbr0    Protokoll:Ethernet  Hardware Adresse FE:FF:FF:FF:FF:FF
> >           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
> >           RX packets:108138 errors:0 dropped:0 overruns:0 frame:0
> >           TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
> >           Kollisionen:0 Sendewarteschlangenlänge:0
> >           RX bytes:6319473 (6.0 MiB)  TX bytes:0 (0.0 b)
> > lnxmei51:/#
> >
> >
> > ************************************
> > *************************************
> > Hope someone can help me .
> >
> >
> > I have testing allready the debian "hotplug and the udevd" but both
> > packets have the same result ! Regards
> > herbert
> >
> >
> >
> >
> > Mit freundlichen Grüßen
> > Herbert Meier
> > System Manager Network/G24/NMI-NC
> > Dipl. Phys.
> > ---------------------------------------------
> > arvato systems GmbH
> > An der Autobahn
> > 33311 Gütersloh
> > http://www.arvato-systems.de
> > herbert.meier@xxxxxxxxxxxxxx
> > Tel.: +49 (0) 5241 80 3765
> > Fax: +49 (0) 5241 80 6 3765
> >
> >
> > ---------------------------------------
> >
> >
> > _______________________________________________
> > Xen-users mailing list
> > Xen-users@xxxxxxxxxxxxxxxxxxx
> > http://lists.xensource.com/xen-users
>
> _______________________________________________
> Xen-users mailing list
> Xen-users@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-users

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

<Prev in Thread] Current Thread [Next in Thread>