Misunderstanding the Xen network setup?

Question

Xen

Good afternoon, I spent several hours trying to figure out this issue myself, but alas, something does not work out, I ask for help from the community. In general, there is a situation, you need a solution, or at least point me where you can look.
Situation: Server with OracleLinux installed, Xen installed on it, oralcelinux is dom0. Established another domain on which OS WindowsXP. Everything seems to be fine. But no matter how I tried to configure the bridge, it did not work out. The bridge itself has been created.
I ask to help those who faced with the setting of this.
Thank you in advance.

Answer 1

Let's assume that you are using Xen 4.0.1.
In /etc/xen/xend-config.sxp you should have the lines

(vif-script vif-bridge)
(network-script 'network-bridge netdev=eth0')

This is needed to run a script (named network-bridge, found in /etc/xen/scripts) that bridges the specified network interface (eth0). If you do not explicitly specify the name of the bridge through the bridge parameter, then it is created with the same name as the physical interface, and the interface is renamed with the “p” prefix (i.e. in the case of eth0, you will create an eth0 bridge, and the physical interface will become peth0).
In the guest config, respectively, specify the line:

vif = [ 'mac=00:11:22:33:44:55, ip=используемый_IP_адрес, bridge=имя_моста' ]

Then restart xend (/etc/init.d/xend restart). If the bridge was not created for one reason or another (check via brctl show or ifconfig), then try running the bridge script manually:
/etc/xen/scripts/network-bridge start [параметры]
As parameters, specify everything that follows in the network-script line after the script name, i. "netdev=eth0", etc.
There is also a strange bug in /etc/xen/scripts/network-bridge that prevents a bridge from being created if at least one already exists (nonsense if you need to have more than 1 bridge for certain goals). If you still come across this, then remove the construction from the script /etc/xen/scripts/network-bridge

    if [ `brctl show | wc -l` != 1 ]; then
        return
    fi

Under Windows, it is worth installing paravirtual drivers . This can be done at any time, even when the network is already set up.

Answer 2

I studied the /var/log/xen/xend.log file, here is an excerpt that may be of interest, please see if there are any obvious errors in it. If not, then tomorrow I'll try to remove everything that is, and create a new config, and a new installation of the guest system. Thank you all in advance.
[2011-08-11 20:11:48 xend 9410] DEBUG (DevController:114) DevController: writing {'backend-id': '0', 'virtual-device': '768', 'device-type': 'disk', 'state': '1', 'backend': '/local/domain/0/backend/vbd/31/768'} to /local/domain/31/device/vbd/768.
[2011-08-11 20:11:48 xend 9410] DEBUG (DevController:116) DevController: writing {'domain': 'Update-Server', 'frontend': '/local/domain/31/device/vbd/768', 'format': 'raw', 'dev': 'hda', 'state': '1', 'params': '/usr/XenDisk/myimage.img', 'mode': 'w', 'online': '1', 'frontend-id': '31', 'type': 'file'} to /local/domain/0/backend/vbd/31/768.
[2011-08-11 20:11:48 xend 9410] DEBUG (DevController:114) DevController: writing {'backend-id': '0', 'mac': '00:16:3E:51:92:8C', 'handle': '0', 'state': '1', 'backend': '/local/domain/0/backend/vif/31/0'} to /local/domain/31/device/vif/0.
[2011-08-11 20:11:48 xend 9410] DEBUG (DevController:116) DevController: writing {'domain': 'Update-Server', 'handle': '0', 'script': '/etc/xen/scripts/vif-bridge', 'ip': '192.168.5.6', 'state': '1', 'frontend': '/local/domain/31/device/vif/0', 'mac': '00:16:3E:51:92:8C', 'online': '1', 'frontend-id': '31'} to /local/domain/0/backend/vif/31/0.
[2011-08-11 20:11:48 xend 9410] INFO (image:434) spawning device models: /usr/lib64/xen/bin/qemu-dm ['/usr/lib64/xen/bin/qemu-dm', '-d', '31', '-m', '256', '-boot', 'c', '-serial', 'pty', '-vcpus', '1', '-domain-name', 'Update-Server', '-net', 'nic,vlan=1,macaddr=00:16:3E:51:92:8C,model=rtl8139', '-net', 'tap,vlan=1,bridge=xenbr0', '-vnc', '192.168.5.5:31', '-vncunused']
[2011-08-11 20:11:48 xend 9410] INFO (image:437) device model pid: 25468
[2011-08-11 20:11:48 xend.XendDomainInfo 9410] DEBUG (XendDomainInfo:990) Storing VM details: {'shadow_memory': '8', 'uuid': '985e35d7-9508-705c-5c59-cfb261f94e8e', 'on_reboot': 'restart', 'start_time': '1313075508.97', 'on_poweroff': 'destroy', 'name': 'Update-Server', 'xend/restart_count': '0', 'vcpus': '1', 'vcpu_avail': '1', 'memory': '256', 'on_crash': 'restart', 'image': "(hvm (kernel /usr/lib/xen/boot/hvmloader) (args 'VNC_VIEWER=127.0.0.1:5512 ') (device_model /usr/lib64/xen/bin/qemu-dm) (vcpus 1) (boot c) (timer_mode 1) (serial pty) (vnc 1) (vncunused 1) (vnclisten 192.168.5.5) (display localhost:11.0) (xauthority /root/.Xauthority) (vncpasswd ))", 'maxmem': '256'}
[2011-08-11 20:11:48 xend.XendDomainInfo 9410] DEBUG (XendDomainInfo:1025) Storing domain details: {'console/port': '3', 'name': 'Update-Server', 'console/limit': '1048576', 'vm': '/vm/985e35d7-9508-705c-5c59-cfb261f94e8e', 'domid': '31', 'cpu/0/availability': 'online', 'memory/target': '262144', 'store/ring-ref': '65534', 'store/port': '2'}
[2011-08-11 20:11:48 xend.XendDomainInfo 9410] DEBUG (XendDomainInfo:2045) UUID Created: False
[2011-08-11 20:11:48 xend.XendDomainInfo 9410] DEBUG (XendDomainInfo:2046) Devices to release: [], domid = 30
[2011-08-11 20:11:48 xend.XendDomainInfo 9410] DEBUG (XendDomainInfo:2050) Releasing PVFB front-end devices (uuid not created)...
[2011-08-11 20:11:48 xend.XendDomainInfo 9410] DEBUG (XendDomainInfo:2058) Releasing PVFB backend devices ...
[2011-08-11 20:11:48 xend.XendDomainInfo 9410] DEBUG (XendDomainInfo:1246) XendDomainInfo.handleShutdownWatch
[2011-08-11 20:11:49 xend 9410] DEBUG (DevController:158) Waiting for devices vif.
[2011-08-11 20:11:49 xend 9410] DEBUG (DevController:164) Waiting for 0.
[2011-08-11 20:11:49 xend 9410] DEBUG (DevController:509) hotplugStatusCallback /local/domain/0/backend/vif/31/0/hotplug-status.
[2011-08-11 20:11:49 xend 9410] DEBUG (DevController:509) hotplugStatusCallback /local/domain/0/backend/vif/31/0/hotplug-status.
[2011-08-11 20:11:49 xend 9410] DEBUG (DevController:523) hotplugStatusCallback 1.
[2011-08-11 20:11:49 xend 9410] DEBUG (DevController:158) Waiting for devices usb.
[2011-08-11 20:11:49 xend 9410] DEBUG (DevController:158) Waiting for devices vbd.
[2011-08-11 20:11:49 xend 9410] DEBUG (DevController:164) Waiting for 768.
[2011-08-11 20:11:49 xend 9410] DEBUG (DevController:509) hotplugStatusCallback /local/domain/0/backend/vbd/31/768/hotplug-status.
[2011-08-11 20:11:49 xend 9410] DEBUG (DevController:509) hotplugStatusCallback /local/domain/0/backend/vbd/31/768/hotplug-status.
[2011-08-11 20:11:49 xend 9410] DEBUG (DevController:523) hotplugStatusCallback 1.
[2011-08-11 20:11:49 xend 9410] DEBUG (DevController:158) Waiting for devices irq.
[2011-08-11 20:11:49 xend 9410] DEBUG (DevController:158) Waiting for devices vkbd.
[2011-08-11 20:11:49 xend 9410] DEBUG (DevController:158) Waiting for devices vfb.
[2011-08-11 20:11:49 xend 9410] DEBUG (DevController:158) Waiting for devices pci.
[2011-08-11 20:11:49 xend 9410] DEBUG (DevController:158) Waiting for devices ioports.
[2011-08-11 20:11:49 xend 9410] DEBUG (DevController:158) Waiting for devices tap.
[2011-08-11 20:11:49 xend 9410] DEBUG (DevController:158) Waiting for devices vtpm.
[2011-08-11 20:11:49 xend 9410] INFO (XendDomain:387) Domain Update-Server (31) unpaused.

Answer 3

In general, I finally found an error why this whole thing does not work, I hope I understood correctly, if not, please correct me. First: If I understand correctly, he created a bridge for me on the eth0 interface. I need to change it to eth2, and that's where the ambush comes in. I did not find the design that Lux_In_Tenebris pointed out to me in the script file. When I try to create a bridge by hand, I get the following message:
[[email protected] xen]# brctl show
bridge name bridge id STP enabled interfaces
virbr0 8000.000000000000 yes
xenbr0 8000.feffffffffff no peth0
vif0.0

[[email protected] ~]# /etc/xen/scripts/network-bridge bridge=eth2bridge netdev=eth2 start
Link veth0 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=); if the
driver is compiled statically into the kernel, then you may set the parameter
using loopback.nloopbacks= on the domain 0 kernel command line.