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<br><br><span style="font-weight: bold;">Jan 6 18:54:20 xen net.agent[8922]: remove event not handled
</span><br><br><span style="font-weight: bold;">Jan 6 18:54:36 xen hald[4869]: Timed out waiting for hotplug event 1148. Rebasing to 1149</span><br style="font-weight: bold;"><span style="font-weight: bold;">Jan 6 18:54:37 xen
hal.hotplug[9720]: timout(10000 ms) waiting for /class/net/vif3.0</span><br style="font-weight: bold;"><br>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.
<br><br>ifconfig from dom0<br><br>eth0 Link encap:Ethernet HWaddr 00:08:A1:50:FA:19<br> inet addr:<a href="http://192.168.1.250">192.168.1.250</a> Bcast:<a href="http://192.168.1.255">192.168.1.255</a> Mask:
<a href="http://255.255.255.0">255.255.255.0</a><br> inet6 addr: fe80::208:a1ff:fe50:fa19/64 Scope:Link<br> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1<br> RX packets:7828 errors:0 dropped:0 overruns:0 frame:0
<br> TX packets:6329 errors:0 dropped:0 overruns:0 carrier:0<br> collisions:0 txqueuelen:0<br> RX bytes:3537327 (3.3 MiB) TX bytes:835757 (816.1 KiB)<br><br>lo Link encap:Local Loopback<br>
inet addr:<a href="http://127.0.0.1">127.0.0.1</a> Mask:<a href="http://255.0.0.0">255.0.0.0</a><br> inet6 addr: ::1/128 Scope:Host<br> UP LOOPBACK RUNNING MTU:16436 Metric:1<br> RX packets:1 errors:0 dropped:0 overruns:0 frame:0
<br> TX packets:1 errors:0 dropped:0 overruns:0 carrier:0<br> collisions:0 txqueuelen:0<br> RX bytes:76 (76.0 b) TX bytes:76 (76.0 b)<br><br>peth0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF
<br> inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link<br> UP BROADCAST RUNNING NOARP MULTICAST MTU:1500 Metric:1<br> RX packets:7811 errors:0 dropped:0 overruns:0 frame:0<br> TX packets:6449 errors:0 dropped:0 overruns:0 carrier:0
<br> collisions:0 txqueuelen:1000<br> RX bytes:3548430 (3.3 MiB) TX bytes:859382 (839.2 KiB)<br> Interrupt:16 Base address:0xa000<br><br>vif0.0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF<br>
inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link<br> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1<br> RX packets:6332 errors:0 dropped:0 overruns:0 frame:0<br> TX packets:7830 errors:0 dropped:0 overruns:0 carrier:0
<br> collisions:0 txqueuelen:0<br> RX bytes:837371 (817.7 KiB) TX bytes:3537471 (3.3 MiB)<br><br>vm01 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF<br> inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link
<br> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1<br> RX packets:7 errors:0 dropped:0 overruns:0 frame:0<br> TX packets:55 errors:0 dropped:14 overruns:0 carrier:0<br> collisions:0 txqueuelen:0
<br> RX bytes:762 (762.0 b) TX bytes:11140 (10.8 KiB)<br><br>xenbr0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF<br> inet6 addr: fe80::200:ff:fe00:0/64 Scope:Link<br> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
<br> RX packets:341 errors:0 dropped:0 overruns:0 frame:0<br> TX packets:5 errors:0 dropped:0 overruns:0 carrier:0<br> collisions:0 txqueuelen:0<br> RX bytes:31190 (30.4 KiB) TX bytes:378 (
378.0 b)<br><br>ifconfig from inside domU<br><br>eth0 Link encap:Ethernet HWaddr AA:00:00:18:98:FB<br> inet addr:<a href="http://192.168.1.105">192.168.1.105</a> Bcast:<a href="http://192.168.1.255">192.168.1.255
</a> Mask:<a href="http://255.255.255.0">255.255.255.0</a><br> inet6 addr: fe80::a800:ff:fe18:98fb/64 Scope:Link<br> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1<br> RX packets:56 errors:0 dropped:0 overruns:0 frame:0
<br> TX packets:7 errors:0 dropped:0 overruns:0 carrier:0<br> collisions:0 txqueuelen:1000<br> RX bytes:11226 (10.9 KiB) TX bytes:762 (762.0 b)<br><br>lo Link encap:Local Loopback<br> inet addr:
<a href="http://127.0.0.1">127.0.0.1</a> Mask:<a href="http://255.0.0.0">255.0.0.0</a><br> inet6 addr: ::1/128 Scope:Host<br> UP LOOPBACK RUNNING MTU:16436 Metric:1<br> RX packets:0 errors:0 dropped:0 overruns:0 frame:0
<br> TX packets:0 errors:0 dropped:0 overruns:0 carrier:0<br> collisions:0 txqueuelen:0<br> RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)<br><br>Any help would be appreciated.<br><br><div><span class="gmail_quote">
On 1/5/06, <b class="gmail_sendername">Leonardo Pinto</b> <<a href="mailto:listas@openlogic.com.br">listas@openlogic.com.br</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Here everything functioned well. I applied the patches in the hand in<br>following the files of the FC4:<br><br>"/etc/xen/scripts/vif-common.sh" and<br>"/usr/lib/python/xen/xend/server/netif.py"<br><br>
Remaining only obviously the last adjustment in the configuration file of<br>the virtual machine:<br><br>"vif = [ ' mac=aa:00:00:00:00:11, bridge=isp0, vifname=isp0.0 ' ]"<br><br>Special thanks for "PAINCHAUD Christophe".
<br><br>--<br>Leonardo Pinto<br>listas#openlogic dot com br<br><br>> I tried to apply it to the 2 files vif-common.sh and netif.py however the<br>vifnames specified inside the config don't work. Any ideas ?On 1/5/06,<br>
PAINCHAUD Christophe<br>><br>><br>> &lt;cpainchaud@ecritel.net&gt; wrote:<br>> A dev just pointed me this link :<br>><br><a href="http://xenbits.xensource.com/xen-unstable.hg?cmd=changeset;node=95f84e37c90d573dd01cc29db5b81ffb5f86f84a">
http://xenbits.xensource.com/xen-unstable.hg?cmd=changeset;node=95f84e37c90d573dd01cc29db5b81ffb5f86f84a</a><br>><br>> Regards...<br>><br>> Christophe PAINCHAUD<br>><br>><br>> Somebody could answer me if is possible to modify the standard of the name
<br>> of the virtual interfaces vifX.X? And where I can make these alterations<br>for<br>> my proper personalizations?<br>><br>> Thankful,<br>> --<br>> Leonardo Pinto<br><br><br>________________________________________________
<br>Mensagem enviada usando OpenLogic WebMail 2.7.2<br><br></blockquote></div><br><br clear="all"><br>-- <br><br>regards,<br><br>Anand