similar to: Network problem

HI again, This is the solution to my problem, hope it helps someone in the future. First of all, thanks to Ramachandran Radhakrishnan for helping me with this. The problem was my NIC: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller (rev 01) What happens, is that the NIC''s driver sets the HWADRRESS = FE:FF:FF:FF:FF:FF, and that''s the same

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

Hi, I was hoping someone on this forums could help me out with a problem I was facing with Xen. When I compiled the kernel for Xen-3.1.3 using "make world"(I know this is an old version but I need to use it for some compatibility issues), the kernel was missing the Xen netloop module. There was no /kernel/drivers/xen/netback/netloop.ko in the newly compiled kernel. I think we would

We have a 10Gbps connection to our server so I need to be able to create VMs using the faster e1000 nics instead of the default Realtek 100Mbps ones but I''m not sure how to go about it. Is there a walkthrough or "howto" or can someone point me at some simple instructions? I''m using xen-3.0.3-105.el5_5.5 and Centos 5.5 kernel 2.6.18-194.32.1.el5.centos.plusxen VMs are

I have a new x3655 IBM and whenever the /etc/xen/scripts/network-bridge script starts, the ethernet would no longer work. This post isn''t about the cause, but the fix. I did a lot of tcpdumps and Googling, but I''ll spare you that. All they do is prove that yes, there is an issue. :) I tried Debian 4.0 i386/amd64 and Ubuntu 7.04 Server i386/amd64 and they all exhibit the

Hi Everyone, In my HVM guest''s config file, I have given my guest 3 interface. I have called them fw1, fw2 and fw3. I have joined each interface to a bridge on the Dom0. This does appear when I do a "brctl show". However, there are 3 other interfaces also added called tapx.0,tapx.1 and tapx.2 (Where x is the domain ID for the guest). Furthermore, I am only able to run

On a selection of boxes, ntpd running in Xen Dom0 reproducibly exhibits extermely high noise/jitter. Switching back to -default, non-xen kernel ntpd runs with very low jitter/noise. Question -- how can I ''tame'' ntpd noise & jitter when running in Dom0? Is the problem a config issue, or a bug? Already reported this downstream; everybody''s "stumped".

On a selection of boxes, ntpd running in Xen Dom0 reproducibly exhibits extermely high noise/jitter. Switching back to -default, non-xen kernel ntpd runs with very low jitter/noise. Question -- how can I ''tame'' ntpd noise & jitter when running in Dom0? Is the problem a config issue, or a bug? Already reported this downstream; everybody''s "stumped".

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 ! 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 try to get networking running with xen 3.2, but it seems I fail miserably. I am on sles10sp1, with xen 3.2.0, and kernel rpm''s installed from SP2. I configured in /etc/sysconfig/network the NETWORK_LIST: NETWORK_LIST="bridge,0,default,00:DE:AD:BE:EF,192.168.8.13/24,dhcp-off" but an ifconfig xenbr0 still shows the mac address of peth0 fe:ff:ff:ff:ff:ff. Initially, I

Hello , I use Centos 5.4 , with the redhat version of xen . I need for some guest to change the hardware for the network . So in my xen config i add the model option in the vif line . When the guest boot , i had the right emulation , but after a reboot , the guest loose the configuration . Someone can confirm the bug in centos 5.5 ? Have someone a patch ? Extract of my config : builder

Hi, One of my servers in a IDC in another country mysteriously went down this morning, and when I contacted the IDC, I was told that XEN doesn''t boot up, as follows: [QUOTE] This is error message on the screen " Error 19: Linux Kernel must be loaded before initrd" Server is currently up with 2nd kernel. Please check the grub.conf. [/QUOTE] Looking at grub.conf, I see the

All, I've spent quite a few hours trying to figure this out to no avail... I have two machines and the result is the same on both. Additionally, each machine does not support full hardware virtualization... I am able to create 8 VMs. When attempting to create ninth VM, I get the following error: Error: Device 51712 (vbd) could not be connected. /etc/xen/scripts/block failed; error

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

Package: xen-utils-common Version: 3.0+hg11292-2 Severity: normal After a recent etch upgrade (2.6.17, xen-3.0.2) I was unable to "xm create" until I "modprobe netloop nloopbacks=10" Error was network-bridge couln't create vif interface (backend not found). brctl addbr ... fails because of no free netloop device. passing more nloopbacks device to the module fixed the

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

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

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?

Attempting to install a fully virtualized instance of Windows 2003 fails on CentOS 5.2 x86_64 with xen-3.0.3-64.el5. After issuing the command... # virt-install --hvm -s 70 -f /vm/ts05/ts05.dsk -n ts05 --cdrom /download/Win2003x64/disk1.iso --vnc -r 1024 The script just hangs at... Creating domain... In another terminal window, I can see that vnc-viewer has been started and is