similar to: How to change default interface from eth0 to eth3?

Hi, I''m tying to load a full HVM enviroment with windows XP to test my first xen VM. This is my config file http://dpaste.org/pbJd/ <http://dpaste.org/pbJd/>when i run the command : xm create winxp.cfg i got Error: Domain ''winXP'' does not exist. Somebody can help me with this? i did read docs about config files, everyting seems to be in place thanks --

Hi! I have a problem with my new Xen setup. I have installed Debian etch with netinstall and I''m using 2.6.18-6-xen-amd64 kernel in my dom0 and 3.0.3-0-4 version xen hypervisor. I''m using four network cards on my system and using three of them as xen bridges and dom0 is using the fourth one only for it''s own. So basicly both of my virtual servers use a network card

Hello, I''m new to Xen (and this mailing-list) and facing some problems with the network. I''m stuck and don''t know how to continue. And Google isn''t very helpful either... My setup: - Ubuntu 7.10 for dom0 and Debian 4.0 for all domU - 4 physical NIC (DHCP from my ISP, internal LAN, DMZ & WLAN) - 1 Dom as firewall/router - 1 domU with internal services

Hi, I've been using CentOS & Xen on a server that has 2 VM's configured. The default configuration includes one physical iface that is propagated (by a default bridge) to the VM's. Since I wanted to configure additional physical iface, define a new bridge and propagate it to the viface-s of the VM's, i configured the bridge/phys. iface and brought it up (here are

ok i will do it in text: 66.92.114.46 eth0 209.141.2.194 eth1 192.168.119.101 eth2 192.168.120.101 eth3 What i have is a linux box RH7.3 which will eventually run Shorewall Firewall. On this box there is eth0 66.92.114.46 conneted to isp1 and eth1 209.141.2.194 connected to isp2 It also has eth2 192.168.119.101 and eth3 192.168.120.101 which will connect to a failover appliance which has 2 wan

Hi There, I have a bit of an odd issue. I am testing Xen 3.0.2 on a machine before fully migrating to it from 2.0.7. The host OS is Ubuntu 6.06, and I am running the pre-compiled Xen code (kernel, tools) from the Xen site. I have two NICs, both if which I amhidung from Dom0 via the ''pciback.hide'' grub entry. I am have the bridges setup in the

Hi, We would like to use VLAN tagged packets to be sent/received by the guest VMs running on xen hypervisor. Does xen bridging support vlan tagged packets arriving on the physical nic from outside of the xen host to be passed through with the vlan tag to the vif of the guest with the guest VM receiving the tagged packet ? We have a xenbr configured with two interfaces - eth3 (physical

Hi, I''m using Xen 3.0.3 on two servers with Debian Etch (amd64). These servers have 10 nics (2 onboard and 8 in two 4-port cards) so that every vm can have its own interface. This worked so far with the Xen Version from Etch with a wrapper script wich started 10 bridges at boot time. But now I''ve updated Xen on one of these server to Xen 3.2.0 from backports.org and now the

Hi. I have another question, hopefully easier than my last: Do all physical interfaces in dom0 need to have an IP addresse in order to be used as a bridge by guest domains? I thought that the interface would have to merely be "up" but not necessarily have an IP address configured since bridging is done at layer 2. But alas, if I don''t configure an IP address on dom0 the bridge

Hi, I''ve set up identical (what I think) machines using SLES 10 x86_64, but a new one of those is saying frequently in /var/log/messages: kernel: bond0: received packet with own address as source address A short summary of ifconfig looks like this: bond0 Link encap:Ethernet HWaddr 00:14:4F:2A:12:9C inet addr:132.199.176.78 Bcast:132.199.255.255 Mask:255.255.0.0 eth0

I have nic bonding (mode=802.3ad) setup on 2 servers, both running Centos 5.5 In the "Active Aggregator Info", on one reports 4 ports - which is correct - but the other only reports 3 ports. It's always eth0 that shows a different aggregator ID. Changing the cables around so it hits a different port on the switch makes no difference. The switch is correctly configured for the port

Hi everyone. I am pretty new to xen, but am having an issue that I can''t seem to crack. I am running the 2-6-16 kernel on Debian Etch. If I boot into the Etch kernel, everything works as it should. When I boot into the Xen kernel, eth0 no longer exists. >From what I understand, the network-bridge script will down my eth0, create a new virtual eth0 and bridge it into xenbr0

It seems that with their specific Xen packages, Debian likes to go against the norm, and rather than calling the Xen bridging device something sensible like "xenbr0", they rename the main physical ethernet device "eth0" to "peth0" and create "eth0" as the Xen bridge (as far as I can tell, anyways). Anyone know where exactly they do this so I can reverse it?

If I try to ifup eth0, I get the following: Device eth0 does not seem to be present, delaying initialization. DomU: Linux fedora1 2.6.16-1.2133_FC5xenU #1 SMP Tue Jun 6 02:58:27 EDT 2006 i686 i686 i386 GNU/Linux config: kernel = "/boot/vmlinuz-2.6-xenU" #ramdisk="/boot/initrd-2.6.16-1.2133_FC5xenU.img" memory = 128 name = "fedora1" #dhcp = "dhcp" disk =

Hi all, Does anyone know what the correct steps are to add a XEN bridge, let''s say xenbr0 to Debian Squeeze? I have added the following to /etc/network/interfaces # XEN Bridge auto xenbr0 iface xenbr0 inet manual bridge ports eth0 bridge_stp off bridge_fd 0 And then rebooted the server but brctl show still shows eth0 as bridge: newusaxen:~# brctl

I added a virtual interface eth0:1 on one of my machines and suddenly networking breaks on startup of the system (eth0 is gone) when xend starts and runs the network-bridge script. This is supposed to be fixed according to: https://bugzilla.redhat.com/show_bug.cgi I checked and the network-bridge script contains this fix. It works fine on one of my PCs when eth0:1 is added, but not on this

I''ve got 3 different sets of public ips, each with it''s own static ips, and default gateways, and only one physical ethernet port. I''d like to be able to setup domUs that use the various ips, and route through the gateway for that particular IP. My problem is that when I setup these ip addresses as alias on eth:0, only one set of ips/netmask/gateway will work. any

Hello, all! I could''t to find a solution. See my problem: kernel: 00 03aa9000 03aa9010 00010001(00) 0000000 00000000 (And a lot of messages like up) kernel:TxLisPtr=03aa9060 netif_queue_stopped=1 kernel: cur_tx=30(1e) dirty_tx=1(01) kernel: cur_rx=56 dirty_rx=56 cur_task=30 NETDEV WATCHDOG: eth3: transmit time out kernel: eth3 Transmit time out, TxStatus 00 TxFrameId resetting... I

Hi, I tried already a long time to enable network in my domU but I always fail with: # ifconfig eth0 192.168.0.1 up SIOCSIFADDR: No such device SIOCGIFFLAGS: No such device Do I need to load a kernel module? I use OpenSuse 10.2 with kernel 2.6.18.8-0.5-xen (for both domU and dom0). My config: kernel = "/boot/vmlinuz-xen" ramdisk = "/home/jens/initrd.gz" memory = 1024 name

Hi, I''ve installed xen 3.0.3 from packages (xen-linux-system) on a debian etch, and i''ve configured it with network-bridge script in the default way (netdev=eth0, bridge=xenbr0, etc...) which is ok for me. the problem I have: I cannot ping any outer machine from dom0 (nor any outer machine can ping me). It gives me a "Destination Host Unreachable" message that