| |
|
 |
|
 |
|
|
|
| |
|
|
xen-users
Re: [Xen-users] Device 0(vif) could not be connected (3 eth interfaces)
On Tue, 2007-06-26 at 21:05 -0400, paul van allsburg wrote:
> I have a server with 3 NICs, 0 & 1 are internal nets, and 2(correction) is
> internet
> and nfs access to install location. I have done a clean install of F7 &
> xen: 2.6.20-2925.11.fc7xen.
>
> xm list shows:
> Name ID Mem VCPUs State
> Time(s)
> Domain-0 0 941 1 r-----
> 1313.4
>
> But everytime I run virt install it fails with: "(vif) could not be
> connected". I have replicated this exact error on two different
> machines that have three network cards.
>
> This is what happens:
> # virt-install
> What is the name of your virtual machine? vm01
> How much RAM should be allocated (in megabytes)? 256
> What would you like to use as the disk (path)? /opt/vm01.img
> How large would you like the disk (/opt/vm01.img) to be (in gigabytes)?
> 6
> Would you like to enable graphics support? (yes or no) no
> What is the install location? nfs:19.10.101.27:/media/f7
>
>
> Starting install...
> libvir: Xen Daemon error : GET operation failed:
> libvir: Xen Daemon error : GET operation failed:
> Creating storage file... 100% |=========================| 6.0 GB
> 00:00
> libvir: Xen Daemon error : POST operation failed: (xend.err 'Device 0
> (vif) could not be connected. Hotplug scripts not working.')
>
>
> This is what is configured by the system before running virt-install.
> The documentation says Xen creates, by default, seven pair of "connected
> virtual ethernet interfaces" for use by dom0. Should they have been
> created by now, and if so why not & can I manually force them to be
> made? Any help would be greatly appreciated - at this point I'm
> completely stuck.
>
>
> eth0 Link encap:Ethernet HWaddr 00:30:48:70:EE:E2
> inet addr:192.168.0.1 Bcast:192.168.0.255 Mask:255.255.255.0
> inet6 addr: fe80::230:48ff:fe70:eee2/64 Scope:Link
> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> RX packets:410 errors:0 dropped:0 overruns:0 frame:0
> TX packets:67 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:1000
> RX bytes:32403 (31.6 KiB) TX bytes:10607 (10.3 KiB)
> Base address:0xa800 Memory:f2000000-f2020000
>
> eth1 Link encap:Ethernet HWaddr 00:30:48:70:EE:E3
> inet addr:192.168.1.1 Bcast:192.168.1.255 Mask:255.255.255.0
> inet6 addr: fe80::230:48ff:fe70:eee3/64 Scope:Link
> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> RX packets:50 errors:0 dropped:0 overruns:0 frame:0
> TX packets:422 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:1000
> RX bytes:9291 (9.0 KiB) TX bytes:33399 (32.6 KiB)
> Base address:0xac00 Memory:f2020000-f2040000
>
> eth2 Link encap:Ethernet HWaddr 00:0A:5E:1A:47:23
> inet addr:19.10.101.22 Bcast:19.10.111.255 Mask:255.255.240.0
> inet6 addr: 2002:c66e:6914:a:20a:5eff:fe1a:4723/64
> Scope:Global
> inet6 addr: fe80::20a:5eff:fe1a:4723/64 Scope:Link
> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> RX packets:7043375 errors:0 dropped:0 overruns:0 frame:0
> TX packets:5161 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:0
> RX bytes:608195310 (580.0 MiB) TX bytes:446312 (435.8 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:10937 errors:0 dropped:0 overruns:0 frame:0
> TX packets:10937 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:0
> RX bytes:96970751 (92.4 MiB) TX bytes:96970751 (92.4 MiB)
>
> peth2 Link encap:Ethernet HWaddr 00:0A:5E:1A:47:23
> inet6 addr: fe80::20a:5eff:fe1a:4723/64 Scope:Link
> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> RX packets:7302669 errors:0 dropped:0 overruns:0 frame:0
> TX packets:5177 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:1000
> RX bytes:767149610 (731.6 MiB) TX bytes:512881 (500.8 KiB)
> Interrupt:21
>
> virbr0 Link encap:Ethernet HWaddr 00:00:00:00:00:00
> inet addr:192.168.122.1 Bcast:192.168.122.255
> Mask:255.255.255.0
> inet6 addr: fe80::200:ff:fe00:0/64 Scope:Link
> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> RX packets:0 errors:0 dropped:0 overruns:0 frame:0
> TX packets:49 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:0
> RX bytes:0 (0.0 b) TX bytes:9492 (9.2 KiB)
>
> Thanks! -paul
>
I'm going on the assumption that the default config for xen in fedora7
is the network-bridge/vif-bridge method. Then following the notes in
http://lists.xensource.com/archives/html/xen-users/2006-02/msg00030.html
when xend starts up, it runs the network-bridge script, which:
- creates a new bridge named "xenbr0"
- "real" ethernet interface eth0 is brought down
- the IP and MAC addresses of eth0 are copied to
virtual network interface veth0
- real interface eth0 is renamed "peth0"
- virtual interface veth0 is renamed "eth0"
- peth0 and vif0.0 are attached to bridge xenbr0
- the bridge, peth0, eth0 and vif0.0 are brought up
That being the case then the bridge on my machine is virbr0, not xenbr0. Why
did f7 change it?
I am missing the vif0.2 interface - how can I create it/why is it missing?
Thanks,
Paul
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
|
|
|
| |
|
Home