similar to: errors when xend starts

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

Hi all! After upgrading to Squeeze, I am watching a Xen VMHost that after a while it hangs. This did not happen when I was using Xen with Debian Lenny (in this case as with Squeeze, the Xen components are from Debian repositories). In each case I connected a keyboard and monitor to the computer and the screen remained black without answering any key. This problem seems to also affect domUs,

I am not even sure this is a shorewall issue as kernel, iptables, and shorewall have all recently been updated. Shorewall Version: 4.2.9 Iptables Version: v1.4.3.2 Kernel Version: 2.6.30-rc8 OS: Centos 4.7 X86_64 I see the following on std-output and /var/log/messages Jun 4 22:17:27 firewall shorewall: Compiling... Jun 4 22:17:29 firewall kernel: Netfilter messages via NETLINK v0.30. Jun

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

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

Hi all, I''m struggling to install Xen Hypervisor on my PC, but after one week''s attempt again and again, it still doesn''t work. Anyone can give some suggestion or helpful link? 1. download the xen 4.0.0 stable tarball from here, http://www.xen.org/products/xen_source.html 2. unzip the tar and run install.sh and ''make world'' 3. make install 4. then I

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

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

xenconsole fix. reference of tty->count in xencons_close() is racy. It must be protected by tty_sem semaphore like con_close() in drivers/char/vt.c -- yamahata _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

Hi, can anyone help me with this (weirdest problem Ive ever seen) I have the latest Debian Squeeze vendor xen dom0 kernel and 1 domU succesfully installed on it using bridged networking. From dom0, I can ping/telnet etc. to anywhere on the web WHAT IS WORKING > * From my domU I can successfully ping google.com and telnet to 8.8.8.8:53 (googles dns server) * tcpdump vif1.0 and I see SYNs and

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, 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 list, i'm have samba installed at debian squeeze 2.6.32-5-686 :~# dpkg -l | grep samba ii samba 2:3.5.6~dfsg-3squeeze2 SMB/CIFS file, print, and login server for Unix ii samba-common 2:3.5.6~dfsg-3squeeze2 common files used by both the Samba server and client ii samba-common-bin 2:3.5.6~dfsg-3squeeze2

I''ve seen a lot of threads w/ similar problems, but none have posted a resolution. I am using Debian 4.0r1 (Etch). I was using the xen packages from stable, but have tried w/ testing as well and the problem persists. http://pastie.caboo.se/95144 Host is 10.0.0.20 on network 10.0.0.0/24. Dom0 is thus 10.0.0.20 DomU is 10.0.0.30 When the bridge is enabled, DomU can ping everything.

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 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 * in xend-config.xsp I have: ******************************** (network-script network-route) (vif-bridge xen-br0) (vif-script vif-bridge) ******************************** and in /etc/network/interfaces ********************************* iface eth0 inet static address 0.0.0.0 auto xen-br0 iface xen-br0 inet static pre-up ifconfig eth0 up pre-up brctl addbr xen-br0 pre-up brctl addif

Hello, my server has massive problems with my NIC. I got: "Detected Tx Unit Hang". At the moment I use 2.6.31 from Jeremy, does anyone know if it''s fixed in 2.6.32 or newer tree? Regards, Stefan Kuhne _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

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,

I''m trying to get DHCP working with DomU clients. I don''t want to use libvirtd. There''s a dhcpd on the machine and it works fine for all clients in the network, but not for DomUs. If I set a static IP on the DomU all networking for them is fine, so there''s no general networking problem. I use the xen 3.2 packages for CentOS on CentOS 5.1. There was a public