thr3ads.net - Xen users - [Fedora-xen] Personalizing names of "vifX.X" [Jan 2006]

If this information is useful, please help other people find it:
Share via:

Leonardo Pinto

2006-Jan-05 10:25 UTC

[Fedora-xen] Personalizing names of "vifX.X"

Somebody could answer me if is possible to modify the standard of the name
of the virtual interfaces vifX.X? And where I can make these alterations for
my proper personalizations?

Thankful,

--
Leonardo Pinto
listas#openlogic dot com br


________________________________________________
Mensagem enviada usando OpenLogic WebMail 2.7.2

PAINCHAUD Christophe

2006-Jan-05 13:59 UTC

head link

[Fedora-xen] RE: [Xen-users] Personalizing names of "vifX.X"

A dev just pointed me this link :
http://xenbits.xensource.com/xen-unstable.hg?cmd=changeset;node=95f84e37c90d
573dd01cc29db5b81ffb5f86f84a


Regards...

Christophe PAINCHAUD


-----Message d''origine-----
De : xen-users-bounces@lists.xensource.com
[mailto:xen-users-bounces@lists.xensource.com] De la part de Leonardo Pinto
Envoyé : Thursday, January 05, 2006 11:26 AM
À : Xen Users
Cc : Fedora Xen
Objet : [Xen-users] Personalizing names of "vifX.X"

Somebody could answer me if is possible to modify the standard of the name
of the virtual interfaces vifX.X? And where I can make these alterations for
my proper personalizations?

Thankful,

--
Leonardo Pinto
listas#openlogic dot com br

Leonardo Pinto

2006-Jan-05 13:59 UTC

head link

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

Here everything functioned well. I applied the patches in the hand in
following the files of the FC4:

"/etc/xen/scripts/vif-common.sh" and
"/usr/lib/python/xen/xend/server/netif.py"

Remaining only obviously the last adjustment in the configuration file of
the virtual machine:

"vif = [ '' mac=aa:00:00:00:00:11, bridge=isp0, vifname=isp0.0
'' ]"

Special thanks for "PAINCHAUD Christophe".

--
Leonardo Pinto
listas#openlogic dot com br
> I tried to apply it to the 2 files vif-common.sh and netif.py however thevifnames specified inside the config don''t work. Any ideas ?On 1/5/06,
PAINCHAUD Christophe>
>
>  &lt;cpainchaud@ecritel.net&gt; wrote:
> A dev just pointed me this link :
>
http://xenbits.xensource.com/xen-unstable.hg?cmd=changeset;node=95f84e37c90d573dd01cc29db5b81ffb5f86f84a>
> Regards...
>
> Christophe PAINCHAUD
>
>
> Somebody could answer me if is possible to modify the standard of the name
> of the virtual interfaces vifX.X? And where I can make these alterations
for> my proper personalizations?
>
> Thankful,
> --
> Leonardo Pinto

________________________________________________
Mensagem enviada usando OpenLogic WebMail 2.7.2

Anand

2006-Jan-05 14:33 UTC

head link

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

I tried to apply it to the 2 files vif-common.sh and netif.py however the
vifnames specified inside the config don''t work. Any ideas ?

On 1/5/06, PAINCHAUD Christophe <cpainchaud@ecritel.net>
wrote:>
>
> A dev just pointed me this link :
>
>
http://xenbits.xensource.com/xen-unstable.hg?cmd=changeset;node=95f84e37c90d573dd01cc29db5b81ffb5f86f84a
>
> Regards...
>
> Christophe PAINCHAUD
>
> -----Message d''origine-----
> De : xen-users-bounces@lists.xensource.com [
>
mailto:xen-users-bounces@lists.xensource.com<xen-users-bounces@lists.xensource.com>]
> De la part de Leonardo Pinto
> Envoyé : Thursday, January 05, 2006 11:26 AM
> À : Xen Users
> Cc : Fedora Xen
> Objet : [Xen-users] Personalizing names of "vifX.X"
>
> Somebody could answer me if is possible to modify the standard of the name
> of the virtual interfaces vifX.X? And where I can make these alterations
> for
> my proper personalizations?
>
> Thankful,
>
> --
> Leonardo Pinto
> listas#openlogic dot com br
>
> _______________________________________________
> Xen-users mailing list
> Xen-users@lists.xensource.com
> http://lists.xensource.com/xen-users
>
>

--

regards,

Anand

Anand

2006-Jan-05 19:18 UTC

head link

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

My mistake i was still trying to use vifname= setting as a seperate
directive instead of using it with the vif= setting.

Works like a charm. Thanks everyone.

On 1/5/06, Leonardo Pinto <listas@openlogic.com.br>
wrote:>
> Here everything functioned well. I applied the patches in the hand in
> following the files of the FC4:
>
> "/etc/xen/scripts/vif-common.sh" and
> "/usr/lib/python/xen/xend/server/netif.py"
>
> Remaining only obviously the last adjustment in the configuration file of
> the virtual machine:
>
> "vif = [ '' mac=aa:00:00:00:00:11, bridge=isp0, vifname=isp0.0
'' ]"
>
> Special thanks for "PAINCHAUD Christophe".
>
> --
> Leonardo Pinto
> listas#openlogic dot com br
>
> > I tried to apply it to the 2 files vif-common.sh and netif.py however
> the
> vifnames specified inside the config don''t work. Any ideas ?On
1/5/06,
> PAINCHAUD Christophe
> >
> >
> >  &lt;cpainchaud@ecritel.net&gt; wrote:
> > A dev just pointed me this link :
> >
>
>
http://xenbits.xensource.com/xen-unstable.hg?cmd=changeset;node=95f84e37c90d573dd01cc29db5b81ffb5f86f84a
> >
> > Regards...
> >
> > Christophe PAINCHAUD
> >
> >
> > Somebody could answer me if is possible to modify the standard of the
> name
> > of the virtual interfaces vifX.X? And where I can make these
alterations
> for
> > my proper personalizations?
> >
> > Thankful,
> > --
> > Leonardo Pinto
>
>
> ________________________________________________
> Mensagem enviada usando OpenLogic WebMail 2.7.2
>
>

--

regards,

Anand

Leonardo Pinto

2006-Jan-06 11:07 UTC

head link

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

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


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

Anand

2006-Jan-06 13:28 UTC

head link

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

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.

On 1/5/06, Leonardo Pinto <listas@openlogic.com.br>
wrote:>
> Here everything functioned well. I applied the patches in the hand in
> following the files of the FC4:
>
> "/etc/xen/scripts/vif-common.sh" and
> "/usr/lib/python/xen/xend/server/netif.py"
>
> Remaining only obviously the last adjustment in the configuration file of
> the virtual machine:
>
> "vif = [ '' mac=aa:00:00:00:00:11, bridge=isp0, vifname=isp0.0
'' ]"
>
> Special thanks for "PAINCHAUD Christophe".
>
> --
> Leonardo Pinto
> listas#openlogic dot com br
>
> > I tried to apply it to the 2 files vif-common.sh and netif.py however
> the
> vifnames specified inside the config don''t work. Any ideas ?On
1/5/06,
> PAINCHAUD Christophe
> >
> >
> >  &lt;cpainchaud@ecritel.net&gt; wrote:
> > A dev just pointed me this link :
> >
>
>
http://xenbits.xensource.com/xen-unstable.hg?cmd=changeset;node=95f84e37c90d573dd01cc29db5b81ffb5f86f84a
> >
> > Regards...
> >
> > Christophe PAINCHAUD
> >
> >
> > Somebody could answer me if is possible to modify the standard of the
> name
> > of the virtual interfaces vifX.X? And where I can make these
alterations
> for
> > my proper personalizations?
> >
> > Thankful,
> > --
> > Leonardo Pinto
>
>
> ________________________________________________
> Mensagem enviada usando OpenLogic WebMail 2.7.2
>
>

--

regards,

Anand

Anand

2006-Jan-06 14:39 UTC

head link

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

Can you scan your /var/log/messages for the error i wrote ?

On 1/6/06, Leonardo Pinto <listas@openlogic.com.br>
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@lists.xensource.com
http://lists.xensource.com/xen-users

Leonardo Pinto

2006-Jan-06 14:53 UTC

head link

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

It forgives me my friend... I also tried to use NAT and I did not obtain to
make function. And was following the topic that I passed you that I got
success.

Good luck,

--
Leonardo Pinto
listas#openlogic dot com br

> 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&nbsp; 6 22:57:36 xen hal.hotplug[11209]: timout(10000 ms) waiting
for
/class/net/vif4.0> Jan&nbsp; 6 22:58:31 xen net.agent[11281]: remove event not handled
> Jan&nbsp; 6 22:58:31 xen net.agent[11291]: remove event not handled
> Jan&nbsp; 6 22:58:32 xen logger: /etc/xen/scripts/vif-nat:
xenstore-read
backend/vif/4/0/domain failed.> Jan&nbsp; 6 22:58:53 xen hald[4869]: Timed out waiting for hotplug
event
1168. Rebasing to 1172>
> Any clues ??On 1/6/06,
________________________________________________
Mensagem enviada usando OpenLogic WebMail 2.7.2


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

Anand

2006-Jan-06 17:32 UTC

head link

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

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@openlogic.com.br>
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@lists.xensource.com
http://lists.xensource.com/xen-users

Xen users - Jan 2006 - Personalizing names of "vifX.X"

[Fedora-xen] Personalizing names of "vifX.X"

[Fedora-xen] RE: [Xen-users] Personalizing names of "vifX.X"

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

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

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

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

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

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

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

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