similar to: virt-install w/ routed networking

Hi! I want to forward the port 3389 from the domU to the virtual server with ip address 192.168.122.77 with not success... I tried a lot of iptables rules with no luck so far. Is this possible? I take a look at other post and I don''t found an answer. By example: /sbin/iptables -t nat -A PREROUTING -p tcp -i xenbr0 --dport 3389 -j DNAT --to 192.168.122.77:3389 the virtual nic for the

I''m using xen-3.0.3-64.el5_2.1 on centos 5.2. When I installed centos 5.2 at first time, I could see shared physical device (xenbr0). but after updating virtualization package by yum, it disappeared... connection.py is patched at centos 5.2 release time. so I can''t find out what''s wrong.... bridge configuration is below and it''s normal state.

Hi, I''m trying to install xen with this configuration: dom0 -> Centos 5.3 dom1 -> Fedora 10 dom2 -> Fedora 10 Centos kernel = (2.6.18-128.1.10.el5.centos.plusxen) XEN Version = 3.0.3 I''m having some problems trying to install xen on my mychine, but i''ve been able to solve all of them but one: i can''t reach my gateway from

Hi ! I have install the xen4+centos5 on my server following the post of the kernel version is 2.6.32.27 which is download from git://git.kernel.org/pub/scm/linux/kernel/git/jeremy/xen.git But after I reboot the server ,and run the "ifconfig", whose output likes the following [root@localhost scripts]# ifconfig eth0 Link encap:Ethernet HWaddr 00:15:C5:EB:96:C3

Hi, I tried this post on the Xen list first with no answer. I have 4 machines and 3 of which (all different) have no network access when booted into Xen. I tried using Fedora Core 8 and it produced the same results. Is it normal for the virbr0 interface to take an arbitrary IP? How does it decide what to use? An ifconfig when booted into Xen shows the following: eth0 Link encap:Ethernet

Just created the first completely new Xen VM with the Virtual Machine Manager after 5.0 became 5.1 and I notice these two differences: - there's now virbr0 instead of xenbr0. Which means I have now xenbr0 and vitbr0 interfaces running. As virbr0 just the new name for xenbr0? If so, can I just change that name in the older configuration files, so that all use the same interface name? -

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

Hi, I have Xen 3.0.3 installed on CentOS 5.5 with 2 paravirtualized domU''s configured to use the default bridge networking and am having networking issues. If I boot the computer fresh I am able to ping dom0 and can SSH into it and start the domU''s. The following ping snippet demonstrates the problem. The first group of "Destination Host Unreachable" is while the

Hi Every one, I'm hoping some one can point me in the right direction. We are piloting KVM + Libvirt for migrating off Xen and I'm stuck with the network bridge configuration via libvirt. What we have currently with xen is: 1 server with Wan/lan interfaces and a pool of public ip addresses. Using xen bridge scripts I'd start a xenbr0 and attach eth0 (wan) and go ahead and assign

Hi, I ''ve got a CentOS 5.2 server running xen 3.0 with 2 DomUs also running CentOS 5.2. All my boxes are up-to date. I''m experiencing trouble with networking. Dom0 can reach the outside world when no DomU are started. It can also reach the outside world when only one DomU is running. The troubles begin when I start the second DomU. At first, this new DomU, called DomU2,

Hello, Are there any good alternatives to the network-nat script on Debian Squeeze? I have tried using (network-script network-nat) and (vif-script vif-nat), but I end up with an error message like Error: Device 1 (vif) could not be connected. ip addr add 10.0.1.259 dev vif4.1 failed with configuration file directive vif =[ ''script=vif-nat,ip=10.0.1.132'' ] I need Internet

I've got a Centos guest and a Windows 2003 server guest running in Xen under Centos (5.2 in both cases), and they can get out to the network, and I can ping them from dom0. This is my first Xen install, and I haven't used Linux as a router before (I'm very familiar with it as a webserver and development platform) so I'm a bit weak on the bridging code and NAT / IP masquerading.

I am fairly new to xen and am trying to build a new guest using virt-manager. When I get to the screen where you can choose virtual or shared physical device there are no physical devices to choose from. Is there some step that I have missed while setting up my Dom0? -Joel Coopersmith Sr. Systems and Networking Analyst joel.coopersmith@accenture.com

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)

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

I tried netperf / netserver with Dom0 / DomU, but I could''nt get a correct NW traffic with xentop. Is there anybody could help me? At Host1''s Dom0, run netperf -H VMIP At Host2''s DomU (with VMIP named TTVM), run netserver At Host1, run xentop this way ->"xentop -n -b -d 1" At Host2, run xentop this way->"xentop -n -b -d 1" In Host2''s

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?

Hello, I''m using Debian Squeeze with Xen 4.0 HVM. Both running 64bits. I''ve got 4 domU''s requiring the bridged setup to work, I''ve got an IP address for each. Now I need to setup routed networking for the rest of domU''s. I just changed the configuration in xend-config.sxp and restarted Xen. Routing started to work, while there are still

Hello! I''ve got CentOS 5.3 x64 as dom0 and the same OS for domU. I''ve installed it using the following manual: http://www.howtoforge.com/centos_5.0_xen Guest image was taken from stacklet.com Unfortunately, I can''t make domU working with public static IP. When I use bridged networking, the guest don''t have network connection at all. When I use routed

Hi All, I am facing an issue regarding communicating a value from outside to a Guest OS (linux, solaris and windows) launched on Xen Server. I did went through this thread, but It was not completely clear. http://lists.xensource.com/archives/html/xen-users/2006-07/msg00473.html My question is - Is there a way in Xen, through which I can communicate a value from outside to a Guest OS (linux,