similar to: Strange Network behaviour

I inherited a xen server that is setup to have all the VM images hosted on an iSCSI mounted NAS array. We been experiencing a random (about every 2-3 days) issue where xen would crash all the VMs, leaving nothing but the Domain0 running. What appears to be happening is something causes the iSCI mount to hiccup. Running "vgchange -a y" and restarting all the VMs brings everything up.

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

Hello. First of all I ''m pretty new to Linux and this is my first install of Xen. So don''t mind me wrong if sometimes I don''t know which command is appropriate to fetch results. I''m running a new Debian Squeeze release 2.6.32-5-xen-amd64 with minimal components. I''ve been going through install of Xen as per the documentation for the 4.2.1 release and

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 All, Having an issue with xen-4.0-unstable where after completing a live migration, an arp is never sent out to update the switch with the new location of the mac address. Network is configured as per libvirt''s instructions with the xen network-script disabled and the bridge (xenbr0) always up.

We''ve been hitting the following issue on a variety of hosts and recent Xen/dom0 version combinations. Here''s an excerpt from our latest: Xen: 4.1.4 (xenbits @ 23432) Dom0: 3.7.1-x86_64 BUG: unable to handle kernel NULL pointer dereference at 000000000000001c IP: [<ffffffff8141a301>] evtchn_from_irq+0x11/0x40 PGD 0 Oops: 0000 [#1] SMP Modules linked in: ebt_comment

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

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

Hello again, folks! I''m getting one strange problem with FC5 running on XEN 3.0.3 x64... The MRTG point to my machine with XEN running one absurd volume of output data sent (normal is around 6 MB/s) and when XEN is working we get 80 MB/s until my DRAC is alive... after this, the machine crash, DRAC stop do reply, swith stop do work together... Anyone knows whats happening now? ;)

This issue was brought up about a year and a half ago. So I''ll bring it up again and see if anything happens. I''ve got an infiniband network and am attempting to pass the infiniband card through the host and give it to the guest. I''m working with standard CentOS 5.2 on both guest and host with their provided xen (3.0.3 ish). I''ve also attempted to install the

This issue was brought up about a year and a half ago. So I''ll bring it up again and see if anything happens. I''ve got an infiniband network and am attempting to pass the infiniband card through the host and give it to the guest. I''m working with standard CentOS 5.2 on both guest and host with their provided xen (3.0.3 ish). I''ve also attempted to install the

Hello, I''m facing a rather strange problem with the netback interface. My setup involves a netvm, which has some physical network interfaces assigned, and a client VM where a net front is running (exposed as eth0) and which is connected to that netvm (via vif42.0 interface, as seen in the netvm on the dumps below). Now, the netvm has two physical network interfaces assigned: 1) A

18. Juli 2017 16:45, "Michal Privoznik" <mprivozn@redhat.com> schrieb: > On 07/18/2017 04:31 PM, c.monty@web.de wrote: > >> Hello! >> >> I have upgraded all libvirt packages to version 3.5.0-655.1 and restarted host. > > That wasn't necessary. It's not Windows ;-) > >> This is the current default network config: >> ld4004:~

Hi, At my provider (xs4all) I've got an ipv6 tunnel working. Now I would like to distribute ipv6 via the tinc tunnel. My tinc.conf: ------------ Name=server AddressFamily=ipv4 Device=/dev/net/tun PrivateKeyFile=/etc/tinc/fvhglobalnet/rsa_key.priv GraphDumpFile=|/usr/bin/dot -Tpng -o /var/www/htdocs.keetweej.vanheusden.com/stats/tinc-fvh-network-graph.png Mode=switch KeyExpire=299

Hello, I have been playing with the XCP for a while now, and must say I''m very exited about the technology. I had no prior experience with Xen so it has taken me a while to understand the concepts, but now I feel most important issues are solved and I''ve purchased some hardware to build my (tiny) cloud on. The box is a Supermicro 1026TT-IBXF, so I have 2 x Ethernet and 1 x

Hi, you have to limit dom0 memory on two places, xen hypervisor option and xend config. In this example below I limit memory to 256MB: /boot/grub/menu.lst 87c87 < # xenhopt= --- > # xenhopt=dom0_mem=256M /etc/xen/xend-config.sxp 120c120 < (dom0-min-mem 196) --- > (dom0-min-mem 256) After changing /boot/grub/menu.lst you have to run update-grub and reboot the machine. After

Package: xen-hypervisor-3.0.3-1-amd64 Version: 3.0.3-0-2 Severity: grave Justification: renders package unusable This bug looks to be tracked in upstream: http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=762 Mailing list discussion here: http://lists.xensource.com/archives/html/xen-bugs/2006-11/msg00030.html -- System Information: Debian Release: 4.0 APT prefers testing APT policy:

Hi all, I''ve a serious problem with my dom0 xen installation, that''s why I''m blocked to daily work. I come to describe my virtualization scenary and the arised problem. Hardware is a Dell server with 3 physicall ethernet network cards and 16 GB RAM. Initially installed CentOS-5.2 with Xen-3.0.3 and 2.6.18-128.el5xen kernel. Dom0 with 7 domU paravirtuallized (they have

Hi all, I''ve a serious problem with my dom0 xen installation, that''s why I''m blocked to daily work. I come to describe my virtualization scenary and the arised problem. Hardware is a Dell server with 3 physicall ethernet network cards and 16 GB RAM. Initially installed CentOS-5.2 with Xen-3.0.3 and 2.6.18-128.el5xen kernel. Dom0 with 7 domU paravirtuallized (they have

VM traffic is already limited by a throughput limit, but there is no control over the maximum packet per second (PPS). In DDOS attack the major issue is rather PPS than throughput. With provider offering more bandwidth to VMs, it becames easy to coordinate a massive attack using VMs. Example: 100Mbits ~ 200kpps using 64B packets. This patch provides a new option to limit VMs maximum packets per