similar to: sorting virtual network interface names with xen

When I start xen dom0 I get that same dhcp address for eth0 and for xen-br0, dom0 can talk to the world. If I start each of my 3 domU''s mannually, each guest gets a xen-br0 vif with a dhcp address and all 3 can talk to the outside world and each other (my "flat network"). What I want is a tiered network with the first domU acting as a firewall with 3 nics vif = [

Hi, I have a PC with 3 ethernet interfaces. I am trying to a) assign 2 ethernet interfaces exclusively to one domU by using the late binding method and b) to use a bridge between the third interface and dom0 (that works fine). The goal is to not to have to use bridges for the exclusively assigned interfaces. Is it possible? (If not, no need to read the rest) The problem I have is that I

Hi, I''m using CentOS 5.5 x86_64 xen 3.43 from gitco.de and I have an Openvox A1200P voip card and am passing it thru to another centos 5.5 DomU, when I 1st start the domain driver loads and everything seems quite nice and the device works, but after a reboor of the DomU, this is shown on my Dom0 dmesg Here''s Dom0 info [root@xen ~]# dmesg Bootdata ok (command line is ro

Hi, I''m using CentOS 5.5 x86_64 xen 3.43 from gitco.de and I have an Openvox A1200P voip card and am passing it thru to another centos 5.5 DomU, when I 1st start the domain driver loads and everything seems quite nice and the device works, but after a reboor of the DomU, this is shown on my Dom0 dmesg Here''s Dom0 info [root@xen ~]# dmesg Bootdata ok (command line is ro

Hi! Maybe, I found a bug of xen. My system: - domain0 - gentoo - xen-devel-3.0, kernel 2.6.12.5-r1 - domain1 - debian - kernel 2.6.12.5-r1 (2 interface: vif1.1 = eth0 (0.0.0.0), vif1.2 = eth1 (10.0.1.1 + gw 10.0.1.2)) Bridge: xen-br0 (config as 10.0.1.2) include (vif1.2, vif0.0) xen-br1 (config as 0.0.0.0) include (vif1.1, peth0) On server domain1 I use a pppoe server. If a send a pppoe request

I have a OpenSuse 10.3 with xen 3.1.0 running and it''s been running fine for a few months. This past weekend it suddenly started to act up and after some troubleshooting I can now say that it seems like the guests(domU) loose the outgoing network pipe, from the console I can see that the TX counter is stuck at the same value but it''s no errors. It behaves as if whatever I try to

Problem still not solved, or any idea whats wrong. here are some msgs: device vif1.0 entered promiscuous mode alloc irq_desc for 1246 on node 0 alloc kstat_irqs on node 0 brI: port 2(vif1.0) entering learning state device vif1.1 entered promiscuous mode brE: port 2(vif1.1) entering learning state physdev match: using --physdev-out in the OUTPUT, FORWARD and POSTROUTING chains for

We have a SLES11 system with XEN 3.3 and configured an internal bridge "intbr1" with interfaces "vif2.1" and "vif9.1" to two Linux-guests: # ifconfig (reduced output) intbr1 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:169 errors:0 dropped:0 overruns:0 frame:0 TX packets:85 errors:0 dropped:0 overruns:0

Pardon me for a long detailed post but this looks pretty serious. The bottom line is that, when I attempt to shut down or reboot my simple xen-2.0.7 server running FC3 with two domUs, shutting down xendomains appears to send python into an infinite loop. This may be due to a serious misconfiguration on my part but it is certainly a big problem. If we shutdown the domUs manually first, the

I think the diagram here: http://wiki.xensource.com/xenwiki/XenNetworking#line-474 should be more like this: http://pastebin.com/cjxbXrJW I''ve asked Stephen for edit rights on the wiki but wanted to ask for confirmation before editing it. Notes: The connections at the top are switch ports bond1 has eth2 and eth3 eth0 maps to bond0.100 and eth1 maps to bond1.200

Hi, I am using Xen 4.1.1 with Linux 3.0.1 kernel. Previously (Xen 3.4.4 and linux kernel 2.6.18) Xen by default created veth0 <--> vif0.0 pair in dom0. With Xen 4.1.1 these pairs are missing in dom0. Using command ''ip link add type veth'' I can create veth0 and veth1 but vif0.0 is still missing in dom0. (When new domU created I can see vif1.x created) Could you please help

Hi, I am using Xen 4.1.1 with Linux 3.0.1 kernel. Previously (Xen 3.4.4 and linux kernel 2.6.18) Xen by default created veth0 <--> vif0.0 pair in dom0. With Xen 4.1.1 these pairs are missing in dom0. Using command ''ip link add type veth'' I can create veth0 and veth1 but vif0.0 is still missing in dom0. (When new domU created I can see vif1.x created) Could you please help

Package: xen Version: 4.0.1-5.5 Severity: critical --- Please enter the report below this line. --- Hi! Since the update last weekind in stable/squeeze I'm experiencing problems with running Xen on amd64 and multiple domUs losing their network connection/VIFs. From http://blog.windfluechter.net/content/blog/2013/02/26/1597-xen-problems-vms-2632-5-xen-amd64 Unfortunately this update

Hello ! I which to use Xen in order to virtualize a complete local servers farm, using dom0 in front and multiple domU behind. I''m using an external interface, eth0, on Dom0, and a dummy interface, on which the DomUs are bridged through xenbr0. DomU DomU ---Dom0-- | | | | ---------------- | [vif1 vif2 dummy] | xenbr0 eth0---- local

errors from /var/log/xcp-xapi.log: 652Z|debug||1227 UNIX /var/lib/xcp/xapi|VM.start R:0b98978366e4|xapi] creating device emulator 652Z|debug||1227 UNIX /var/lib/xcp/xapi|VM.start R:0b98978366e4|xenops] Device.Dm.start domid=10 661Z|debug||1227 UNIX /var/lib/xcp/xapi|VM.start R:0b98978366e4|xenops] qemu-dm: should be running in the background (stdout redirected to syslog) 661Z|debug||1227 UNIX

Hello, I have been playing with the XCP for a while now, and must say I''m very exited about the technology. I had no prior experience with Xen so it has taken me a while to understand the concepts, but now I feel most important issues are solved and I''ve purchased some hardware to build my (tiny) cloud on. The box is a Supermicro 1026TT-IBXF, so I have 2 x Ethernet and 1 x

Greetings! I finally got the install done for a couple of gust OSs (Win 2003 server & Suse Enterprise 10) Bothe gusts are up and running, but - no networking. My setup: Hardware - AMD Athlon 4200+, ABIT Motherboard, 4 GB of DDR2 RAM, 2 onboard GB NICs Host OS- Suse Linux Enterprise server 10 Xen - 3.0.2_09749-0.4 Config file for Win 2003 server guest: # -*- mode: python; -*-

Hi, what is the proposed way to create domU guests on centos 6.5? At first I tried to follow the documentation on the xen project website which recommends using xl. I created a config file and ended up with getting a message that the kernel is not bootable when trying to create a guest. I also had to stop some daemon (xend?) because it said that xl isn`t compatible with it and the daemon must

Before starting xend (xen 3.0) these are my correct network interfaces: eth0 Link encap:Ethernet HWaddr 00:14:5E:0A:53:04 inet addr:192.168.1.51 Bcast:192.168.1.255 Mask:255.255.255.0 eth1 Link encap:Ethernet HWaddr 00:14:5E:0A:53:05 inet addr:192.168.1.52 Bcast:192.168.1.255 Mask:255.255.255.0 lo Link encap:Local Loopback inet

Hello, Was wondering if there is a solution to the error posted by "Dominique H Schramm" on the 5 Jan 2008 I''ve just changed from network-bridge to network-route and just noticed this problem Thanks, """ Hi guys, i got the following error: /etc/xen/scripts/network-route: line 27: /proc/sys/net/ipv4/conf/eth/proxy_arp: no such file or directory I use the