[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-users] Personalizing names of "vifX.X"


  • To: Leonardo Pinto <listas@xxxxxxxxxxxxxxxx>
  • From: Anand <xen.mails@xxxxxxxxx>
  • Date: Fri, 6 Jan 2006 23:02:00 +0530
  • Cc: Xen Users <xen-users@xxxxxxxxxxxxxxxxxxx>
  • Delivery-date: Fri, 06 Jan 2006 17:37:46 +0000
  • Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:references; b=hMqsSdiTj4aW6ej4spQJQbtZmqVc85p0Lzq+FpA1yhIkcS7YLXZ067iSOIuMiqfgibRVe0jn4CvICViepLgQSitWiftO3m6E/bFwcKrI6GxezXytU+rzV2uH7SOdALoL85ffc/bqtBFnDNjSggcK43GaBwwclSppdYTpt+Lkl6s=
  • List-id: Xen user discussion <xen-users.lists.xensource.com>

When i try to use nat in xend-config.sxp, my domU hangs at trying to get eth0 ip from dhcp server. In /var/log/xend.log in dom0, i see this

Jan  6 22:57:36 xen hal.hotplug[11209]: timout(10000 ms) waiting for /class/net/vif4.0
Jan  6 22:58:31 xen net.agent[11281]: remove event not handled
Jan  6 22:58:31 xen net.agent[11291]: remove event not handled
Jan  6 22:58:32 xen logger: /etc/xen/scripts/vif-nat: xenstore-read backend/vif/4/0/domain failed.
Jan  6 22:58:53 xen hald[4869]: Timed out waiting for hotplug event 1168. Rebasing to 1172

Any clues ??

On 1/6/06, Leonardo Pinto <listas@xxxxxxxxxxxxxxxx> wrote:
As I said previously. After the patch made with hand in the related files,
I am following this topic:
http://lists.xensource.com/archives/html/xen-devel/2005-06/msg00691.html

Good luck,

--
Leonardo Pinto
listas#openlogic dot com br


> I am using the custom vif names now inside domU config. However while
> booting up and shutting down domU, i see this inside /var/log/messages in
> dom0
>
> Jan  6 18:54:20 xen net.agent[8922]: remove event not handled
>
> Jan  6 18:54:36 xen hald[4869]: Timed out waiting for hotplug event 1148.
> Rebasing to 1149
> Jan  6 18:54:37 xen hal.hotplug[9720]: timout(10000 ms) waiting for
> /class/net/vif3.0
>
> This is the third time a domU has been booted on this machine so i can
> understand the vif3.0, however i have put a custom name for the vifname as
> vm01.
>
> ifconfig from dom0
>
> eth0      Link encap:Ethernet  HWaddr 00:08:A1:50:FA:19
>           inet addr:192.168.1.250  Bcast: 192.168.1.255  Mask:
> 255.255.255.0
>           inet6 addr: fe80::208:a1ff:fe50:fa19/64 Scope:Link
>           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>           RX packets:7828 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:6329 errors:0 dropped:0 overruns:0 carrier:0
>           collisions:0 txqueuelen:0
>           RX bytes:3537327 ( 3.3 MiB)  TX bytes:835757 (816.1 KiB)
>
> lo        Link encap:Local Loopback
>           inet addr:127.0.0.1  Mask:255.0.0.0
>           inet6 addr: ::1/128 Scope:Host
>           UP LOOPBACK RUNNING  MTU:16436  Metric:1
>           RX packets:1 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:1 errors:0 dropped:0 overruns:0 carrier:0
>           collisions:0 txqueuelen:0
>           RX bytes:76 (76.0 b)  TX bytes:76 (76.0 b)
>
> peth0     Link encap:Ethernet  HWaddr FE:FF:FF:FF:FF:FF
>           inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link
>           UP BROADCAST RUNNING NOARP MULTICAST  MTU:1500  Metric:1
>           RX packets:7811 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:6449 errors:0 dropped:0 overruns:0 carrier:0
>           collisions:0 txqueuelen:1000
>           RX bytes:3548430 ( 3.3 MiB)  TX bytes:859382 (839.2 KiB)
>           Interrupt:16 Base address:0xa000
>
> vif0.0    Link encap:Ethernet  HWaddr FE:FF:FF:FF:FF:FF
>           inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link
>           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>           RX packets:6332 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:7830 errors:0 dropped:0 overruns:0 carrier:0
>           collisions:0 txqueuelen:0
>           RX bytes:837371 (817.7 KiB)  TX bytes:3537471 (3.3 MiB)
>
> vm01      Link encap:Ethernet  HWaddr FE:FF:FF:FF:FF:FF
>           inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link
>           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>           RX packets:7 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:55 errors:0 dropped:14 overruns:0 carrier:0
>           collisions:0 txqueuelen:0
>           RX bytes:762 (762.0 b)  TX bytes:11140 (10.8 KiB)
>
> xenbr0    Link encap:Ethernet  HWaddr FE:FF:FF:FF:FF:FF
>           inet6 addr: fe80::200:ff:fe00:0/64 Scope:Link
>           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>           RX packets:341 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:5 errors:0 dropped:0 overruns:0 carrier:0
>           collisions:0 txqueuelen:0
>           RX bytes:31190 ( 30.4 KiB)  TX bytes:378 ( 378.0 b)
>
> ifconfig from inside domU
>
> eth0      Link encap:Ethernet  HWaddr AA:00:00:18:98:FB
>           inet addr:192.168.1.105   Bcast:192.168.1.255
> Mask:255.255.255.0
>           inet6 addr: fe80::a800:ff:fe18:98fb/64 Scope:Link
>           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>           RX packets:56 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:7 errors:0 dropped:0 overruns:0 carrier:0
>           collisions:0 txqueuelen:1000
>           RX bytes:11226 ( 10.9 KiB)  TX bytes:762 (762.0 b)
>
> lo        Link encap:Local Loopback
>           inet addr: 127.0.0.1  Mask:255.0.0.0
>           inet6 addr: ::1/128 Scope:Host
>           UP LOOPBACK RUNNING  MTU:16436  Metric:1
>           RX packets:0 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
>           collisions:0 txqueuelen:0
>           RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)
>
> Any help would be appreciated.


________________________________________________
Mensagem enviada usando OpenLogic WebMail 2.7.2




--

regards,

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

 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.