I have three xen installations, two servers and one laptop. The laptop install was done about half a year ago but the server installs are new. The laptop install is working flawlessly but the two servers have the same domU network problems. I have been pulling my hair for a while now but got stuck, so I'm turning to you for help.
All installations has been done with help from the FedoraXenQuickstartFC5 howto. Both servers are fresh minimum installs of Fedora Core 5, updated via yum and they use the latest xen0 kernel - 2.6.17-1.2157_FC5xen0 . When trying to install a domU client with xenguest-install.py or try to startup an existing domU image I get no network connection.
xm create -c fedora2.cfg
Using config file "/etc/xen/fedora2.cfg".
Going to boot Fedora Core (2.6.17-1.2157_FC5xenU)
kernel: /vmlinuz-2.6.17-1.2157_FC5xenU
initrd: /initrd-2.6.17-1.2157_FC5xenU.img
Error: Device 0 (vif) could not be connected. Backend device not found.
When running xenguest-install.py I get to the point where I configure the network and get stuck there.
On my laptop ifconfig shows me the interfaces, eth0, lo, peth0, vif0.0 and xenbr0. On the servers the peth0, vif0.0 and xenbr0 interfaces doesn't exist.
The domain0 logs tells me:
cat messages |grep xen
Aug 10 11:58:34 XD0-01 logger: /etc/xen/scripts/vif-bridge: Could not find bridge, and none was specified
Aug 10 12:09:27 XD0-01 kernel: Linux version 2.6.17-1.2157_FC5xen0 (brewbuilder@xxxxxxxxxxxxxxxxxxxxxxxxxxxx) (gcc version 4.1.1 20060525 (Red Hat 4.1.1-1)) #1 SMP Wed Jul 12 00:28:36 EDT 2006
Aug 10 12:09:27 XD0-01 kernel: xen_mem: Initialising balloon driver.
Aug 10 12:09:27 XD0-01 kernel: IA-32 Microcode Update Driver: v1.14-xen <tigran@xxxxxxxxxxx>
Aug 10 12:09:33 XD0-01 xenstored: Checking store ...
Aug 10 12:09:33 XD0-01 xenstored: Checking store complete.
Aug 10 12:09:33 XD0-01 xenstored: Checking store ...
Aug 10 12:09:33 XD0-01 xenstored: Checking store complete.
Aug 10 12:23:05 XD0-01 logger: /etc/xen/scripts/vif-bridge: Could not find bridge, and none was specified
cat xend-debug.log
Link veth0
1 is missing.
This may be because you have reached the limit of the number of interfaces
that the loopback driver supports. If the loopback driver is a module, you
may raise this limit by passing it as a parameter (nloopbacks=<N>); if the
driver is compiled statically into the kernel, then you may set the parameter
using loopback.nloopbacks=<N> on the domain 0 kernel command line.
cat xend.log
<snip>
[2006-08-10 12:23:05 xend.XendDomainInfo ] DEBUG (XendDomainInfo:919) XendDomainInfo.handleShutdownWatch
[2006-08-10 12:23:05 xend] DEBUG (DevController:143) Waiting for devices vif.
[2006-08-10 12:23:05 xend] DEBUG (DevController:149) Waiting for 0.
[2006-08-10 12:23:05 xend] DEBUG (DevController:449) hotplugStatusCallback /local/domain/0/backend/vif/1/0/hotplug-status.
[2006-08-10 12:23:05 xend] DEBUG (DevController:449) hotplugStatusCallback /local/domain/0/backend/vif/1/0/hotplug-status.
[2006-08-10 12:23:05 xend] DEBUG (DevController:463) hotplugStatusCallback 2.
[2006-08-10 12:23:05 xend.XendDomainInfo] DEBUG (XendDomainInfo:1397) XendDomainInfo.destroy: domid=1
[2006-08-10 12:23:05 xend.XendDomainInfo] DEBUG (XendDomainInfo:1405) XendDomainInfo.destroyDomain(1)
Does anyone of you have any ideas on how to get the network working?
All help is appreciated,
Thanks in advance,
/KJS
-- Fedora-xen@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-xen
