similar to: internal ip

Hello Everyone, I have set up a xen server with 10 physical network devices using the bridge mode of XEN. This is because I want to split and separate the network traffic for security reasons. Maybe the best way is to use pci back hide. But I want to understand what is going on here. For all testings I have only activated eth[0-3]. My first tests were successful. I have created a VM using

Hi folks, I''m updating my xen server from a dom0 on debian sarge, using a self compiled xen 3.0.4 and a kernel 2.6.16, to a standard debian etch using the deb packages xen 3.0.3 and kernel 2.6.18. On the old server, all my hvm machines use vnc console and a password is set into xend-config.sxp and it works nice. On the new etch server, with the same hvms and configuration files,

I have a Xen DomU configuration that was made in the days before libvirt and virt-install. In this configuration I have: vif = [ ''mac=00:16:3e:05:06:01, bridge=xenbr0'', ''mac=00:16:3e:05:06:0a, bridge=xenbr1'' ] and then in xend-config.sxp I define (network-script my-network-bridge) where my-network-bridge is in the scripts directory and looks like this:

Somehow I managed to disable the creation of xenbr0 on boot-up of the host system. CentOS 5 with standard CentOS Xen. I changed all Xen VMs to use xenbr0 instead of virbr0 and disabled virtlibd. Works fine. But when I later restarted the machine I found that all networking for guests had gone. On inspection there's no xenbr0 created anymore. I can get it up by stopping network (or eth0)

Hi *.*, This is a continuation on the 2 NICs thread after some more testing. Just to remember my goal. --------------------------- I want to create a domU with 2 virtual NICS. One of them will contact the outside world, the other one will contact a VPN. No reason in concrete for choosing the bridging protocol, only because its the default one. I installed the dom0 with the 2 NICs active, with

Hello, I use xen for a few months now and I upgraded to opensuse 10.3 with xen 3.1 (64bit versions) recently. Everything works fine, but there is a problem when I change xend-config.sxp to use my own network script (it''s slightly modified version of network-virtual scripts from http://en.opensuse.org/Xen3_yet_another_Virtual_Network_Concept ) instead of default network-bridge script.

Package: xen-utils-common Version: 4.3.0-3 Severity: normal Dear Maintainer, I've just set up a fresh Jessie system using the installer dated 2014-03-05, then installed and enabled Xen 4.3. I've done this quite a few times before using Wheezy and 4.1. I set up xenbr0, then created a test domU using xen-create-image, which completed without issue. However I was unable to start the new

I'm seeing an issue with xend not running a custom network script automatically, but works when I run it manually. In /etc/xen/xend-config.sxp I've changed: (network-script network-bridge) TO: (network-script network-custom) Here is /etc/xen/scripts/network-custom: # !/bin/bash # network-custom script=/etc/xen/scripts/network-bridge case $1 in start) $script start vifnum=0

Hello, Where can I find a link (or docs) to *working* network config for xen 4.1.2? My tests (s. below) were not successful. Thank you in advance for any hints. Regards, Mark # --- root@xen411dom0:~# cat /etc/network/interfaces # Used by ifup(8) and ifdown(8). See the interfaces(5) manpage or # /usr/share/doc/ifupdown/examples for more information. auto lo iface lo inet loopback auto bond0

I just cant get a Centos 5.1 domU to install under Centos 5.1 dom0. It is maddening! I'm trying to replace a single server that currently uses simple ethernet aliases (eth0:0, eth0:1, etc) with a new server that uses Xen virtualization. Maybe I dont understand bridging properly or something. My dom0 has the following: eth0 Link encap:Ethernet HWaddr 00:00:44:11:22:33 inet

Already reported.... http://bugs.centos.org/view.php?id=2516 >Subject: RE: [CentOS-virt] xenbr0 isn't created anymore >To: <centos-virt at centos.org> >Message-ID: > <E2BB8074E5500C42984D980D4BD78EF9022A704E at MFG-NYC-EXCH2.mfg.prv> >Content-Type: text/plain; charset="us-ascii" > >Kai Schaetzl wrote: >> >> Somehow I managed

I am writing this email in the hopes of getting some advice from Xen users. My main concern is performance and stability. Before I get any further, let me explain the environment: 1. I am using redhat enterprise linux 5 with the xen kernel (2.6.18-8.1.1.el5xen). This is on a Sun X4200 with two dual core AMD processors, 16Gb of RAM, a Sun StoredgeTek 3320 attached to the X4200,

Hello, I just setup a Xen server and wanted to use bond0 for my network connection. I ended up downloading and addeding the attatched file and making the following change in /etc/xen/xend-config.sxp. I added this line: (network-script 'network-bond netdev=bond0') Would this line be a good one to add to the commented lines and include the network-bond file in the scripts? Just thought

Hello, I am installing xen-3.0.31 on debian-etch-r7 version (apt-get install xen-linux-system-2.6.18-6-xen-686 screen ssh debootstrap python python-twisted iproute bridge-utils libcurl3-dev libssl0.9.7). My eth0 is configured to get IP via dhcp (interfaces file attached). I am able to boot into dom0, but starting xenbr0 causes loss of IP connectivity. Here is what I do. Initially, my

This is all on SuSE enterprise 10 Our server was moved to a new location last night. After powerup there was no sign of networking so our ISP reconfigured the box. Outbound connectivity had previously been through eth1 but is now through eth0 Since restarting Xen I now have no network connectivity through the hosts. I have tried to provide all the relevant details below. If anyone has a moment

Hello, Fast question: from DomU I cannot ping Dom0, I only get 19:17:33.573370 arp who-has 192.168.10.1 tell 192.168.10.150 19:17:34.573421 arp who-has 192.168.10.1 tell 192.168.10.150 using tcpdump in Dom0. Why? --------------- Detailed question: I''m setting up a Xen virtual server. The environment is: -HVM -AMD64 -Debian Etch and using Xen from Debian repository (so Xen 3.0.3,

Hi, I''m using eth2 on my dom0 for bridging. The change required is in the file: /etc/xen/xend-config.sxp You need to tell it which device to bridge when it calls the network-bridge script, by using a line similar to: (network-script ''network-bridge netdev=eth1 bridge=xenbr0'') Note: the "bridge=xenbr0" part is needed in Fedora due to a current bug in the

Hi Gerhard; I'm pretty new to this list too but I think this may be a bonding issue. What bonding mode are you using in /etc/modprobe.conf? You should have a couple of lines in there: alias bond0 bonding options bond0 miimon=x mode=x What kind of switch are you connecting to and have you done any specific configuration to the switch to support your bonding mode? (depends on the mode).

hi, i cleared all the stuffs(everything) related to xen and libvirt. i installed freshly xen-4.2.1 from the source. *Installation steps are as follows:* apt-get build-dep xen apt-get install libc6-dev libglib2.0-dev libyajl-dev yajl-tools libbz2-dev bison flex zlib1g-dev git-core texinfo debhelper debconf-utils debootstrap fakeroot *OR* apt-get install bcc bin86 gawk bridge-utils iproute

Hi, I have taken the long and winding road and indeed it lead me to your door. I need your help, please. My Xen includes 2 guests. Xen itself (10.2.0.52) gets free access to the outside world and to its guests. Both guests however (10.2.0.54/10.2.0.55) see each other but stay under house arrest! Not a single ping manages to go past the bridge (xenbr0) and get an answer from the default gateway