similar to: virtual network hangs during a file download

Dear List-Colleagues: I have been working on installing Xen on Suse 10.3 for some time now. I am green as grass - both a total newbie to Xen and a relative newbie to Linux (as well as a total newbie to SuSE). Currently, I am at the point that when I click on the Xen entry in my grub loader I see Xen starting and running through much of its early setup. Eventually, however, it quits on

Hi Michael: Sorry to brother. But I''ve been suffered this issue quite a long time. My test environment is 2.6.32.36 + xen 4.0.1 + bnx2, 2.3. Also cpu idle is disabled in grub. Grub info: title Red Hat Enterprise Linux Server (2.6.32.36xen) kernel /xen-4.0.1.gz iommu=off x2apic=off console=com1,vga com1=115200,8n1 noreboot cpuidle=0 cpufreq=none

Last problem I had involved changing one character in my configuration scripts. Really easy once someone showed me what was wrong. Well I think this issue is just the same. The moment I used apt to install the Xen kernal and tools I lost internet connectivity. I have been managing because I can restore connectivity be deleting the bridge mpower@dodtsair:~$ sudo ifdown eth0

Hi, If one sets xend to use network-bridge and there are no bridges already present then it seems that xend will clone eth0 to peth0, create xenbr0 and add peth0 and vif0.0 as ports on that bridge. If on the other hand xenbr0 is created in /etc/network/interfaces then xend will not do any of that peth0 stuff, nor will it add vif0.0 to xenbr0, yet (barring some changes in iptables rules) things

Hi, Creating a new domain is a lot easier in opensuse 11. I follow the instruction on the website and build a virtual machine which uses opensuse 11 as well (I installed it from iso image). Everything works fine except the network. I cannot access the Internet from DomU. Here is some information. P.S. the DomU id is 1. "brctl show" in Dom 0: bridge name bridge id STP

I come across some problem when using xen-4.1.1-rc1-pre from xen-4.1-testing tree and 2.6.32.36xen linux kernel from git://git.kernel.org/pub/scm/linux/kernel/git/jeremy/xen.git. when I use ''xend restart'' , it hangs when kernel dmesg printing ''Bridge firewalling registered'' and the console show below messages: localhost# xend restart Nothing to flush. Cannot

When starting xend i see the following errors on the console. I''m running CentOS 5 as the operating system with kernel 2.6.32.18 from 4.0.1''s `make prep-kernels` Below is a log, the things i''m concerned with is the XENBUS errors and the deprecated iptables stuff. Any ideas whats going on here? ---------------------------------------------------- Bridge

Hello, i noticed that the ingress qdisc is not working properly anymore in 3.0.4-1 (back in 3.0.2 the ingress qdisc was working for me): Install the ingress qdisc to peth0: # tc add qdisc dev peth0 ingress ... generate some traffic ... # tc -s qdisc show dev peth0 qdisc pfifo_fast 0: bands 3 priomap 1 2 2 2 1 2 0 0 1 1 1 1 1 1 1 1 Sent 324884 bytes 1749 pkt (dropped 0, overlimits 0 requeues

*Hello,* I have installed Xen as Hypervisor with OpenSUSE running in Dom0. I want to use ovswitch (ovs) instead of the bridges that Xen created. In order to do so, I installed ovs in dom0 just like for the plain Linux. Xen has replaced eth0 with peth0, and has created a bridge named eth0. And eth0 is connected peth0 interface , vif2.0 interface (VM), and everything is working fine. Now I delete

Hi All, I have a weird issue I''m not sure how to solve.  I''ve got Xen 3.2.1 working under RHEL 5.2 x86_64 just fine.  I fired off a CentOS 5.2 PV install and everything went smoothly... except that when I fire up the PV, the tap0 for bridging isn''t being created.  This results in the CentOS 5.2 domU''s bridged eth0 only being able to ping the RHEL5

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

Command just times our for me virt-install --paravirt --vcpus=4 --name server1 --ram 4096 --file /opt/xen-images/hlcnwmmp01.img -x "ks=http://10.203.1.11/kickstart/ks-xen.cfg" --file-size 40 --location http://128.61.111.11/pub/centos/5.4/os/x86_64 -b peth0 Starting install... Retrieving file vmlinuz... | 1.9 MB 00:00 Retrieving file initrd.img...

Hello. I''ve just started with Xen and configuring Dom0. My hardware is Core2Duo based Xeon server and I installed Debian etch for amd64 architecture. The Xen related pachages installed are the following. linux-image-2.6.17-2-xen-amd64 linux-modules-2.6.17-2-xen-amd64 xen-hypervisor-3.0.3-1-amd64 xen-tools xen-utils-3.0.3-1 xen-utils-common My problem is that when xend is

Hi Everyone, In order to prevent DomU from entering promiscuous mode, is it just a matter of adding these 2 rules when the vif is created? # Accept packets leaving the bridge going to the domU only if # the destination IP for that packet matches an authorized IPv4 # address for that domU. iptables -A FORWARD -m physdev --physdev-out vif1.0 \ --destination 216.146.46.43 -j ACCEPT

Thanks a lot for your hints Pasi. Due to your suggestion I open a new thread here. I have tested with model=e1000 (HVMs). As HVM configs are identical (not iso images and LVM volumes) I guess it is a xen 4.1.2* issue .. or just involved domU OS-kernels (however as it is HVM it should not play any role) Tested and correctly working OSes (getting an IP address and pinging of

I''m needing to put a network card on a test server XCP 1.0. I''m seeing the citrix hcl (http://hcl.xensource.com) and I''m a doubt. I base that on which version to look for a compatible card? If the kernel is the same as in 5.6.0 FP1, but if the version of XCP uses the hypervisor 3.4.2 neither appears on the list. ps: I had a RTL-8169 but stopped working with update 0.5

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

hello, I want to configure 2 interface like this eth0 for LAN is 172.16.0.3 eth1 for SAN is 192.168.0.13 I want all VM can access to all network my configuration is : (network-script ''network-bridge netdev=eth0'') to have peth0 and I have a peth0 interface (network-script ''network-bridge netdev=eth1'') to have peth1but I don''t have a peth1 interface

I had the dom0 which unfortunately didn''t have a console on it hit a race condition and saw oom errors on it also. This happened after it was running for over 36 hours with a domU whose load average was avg was around 3 most of the time. changeset: 7396:9b51e7637676 Dom0 - UP i686, Centos 4.1, 768 megs domU-1 92 megs snmpd domU-2 92 megs snmpdd domU-3 410 megs postgres, tomcat 5.5,

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?