similar to: Getting xen domus memory stats working on CentOS

Hello, I need your help please! Excuse my bad English. Since we installed Xen have experiencing random network disconnections in our guests with any reason, the ping don’t response. I solve this issue, I connect to VNC Server in the host, open the virt-manager, all VMs is running, next I open the disconnected guest and then click in the black window, after that the guest response ping,

I am running xen 3.2-1 (Debian 3.2.1-2) on Debian Lenny (2.6.26-2-xen-amd64 #1 SMP Wed Mar 10) on two identical production systems. This morning on one of the systems, xentop stopped displaying. Running xentop results in: unable to open xenstore : Connection refused Failed to initialize xenstat library xm list: Error: (9, ''Bad file descriptor'') xm dmseg: Error: Subcommand

Hello! I recently upgraded a number of Debian testing packages (three days ago) and just now rebooted the system, with the effect that the Xen domUs don't know their `eth0' devices anymore: #v+ # ifconfig eth0 eth0: error fetching interface information: Device not found #v- I'm using xen-hypervisor-3.0.3-1-i386-pae 3.0.3-0-2 and upgraded linux-image-2.6.18-4-xen-686 from

Hi list! Now when Fedora 10 is out, I thought of writing here what's needed to run Fedora 10 Xen domUs on CentOS 5 dom0. Fedora 10 does not have separate kernel-xen, but instead Xen domU support is included in the normal kernel-PAE.i686 and kernel.x86_64 (based on the pv_ops Xen support included in the mainline/vanilla Linux kernels). RHEL 5.3 beta (and final obviously too) includes

Hi, I have some network problems with my DomUs (etch) on a debian etch running xen 3.0.3. The domain0 is a DL360 G5 with tg3 network card If i download something from outside my dom0 box to a domU, i get this network rate: ~865kbits ... and it must be ~ 10Mbits, i think. Doing some tests with iperf i get this: [ 4] local outside_server port 5001 connected with _domU_ port 54889 [ 4]

Hello, We''ve recently started seeing several domUs on multiple machines losing all network connectivity. At least one of these machines (since they are customer machines I can''t verify it for all of them) give the error: $ sudo ifup eth0 eth0: full queue wasn''t stopped! About the only Google hit for this message is:

Package: xen-utils-common Version: 3.0.3-0-2 Severity: wishlist Tags: patch Currently when hostnames are wider than 10 chars, the xentop output is messed up. Please add the following patch to support up to 20 chars, or better yet, allow the columns to auto size :) #! /bin/sh /usr/share/dpatch/dpatch-run ## xentop-name-width.dpatch by <apeeters@lashout.net> ## ## All lines beginning with

Hey All, I’m attempting to gather stats on usage of the “metal”, by which I mean the physical host’s hardware. I would like to know the CPU, IO, and network stats for the hardware. Normally I would get these from /proc/stat, /proc/diskstat, and ifconfig respectively. However, because of the segregation of VMs and Dom0’s special relationship as a paravirtualized I don’t know if I can trust this

Sorry for the top post, blackberry. Well I like to be able to install my machines in the xenstore with 'xm new' and then manage them from there, but virt-install and virsh are useful too, so I just use CentOS base then replace their xen with the one from xen.org keeping libvirt and now I have the best of both worlds. The commercial one isn't without gripes too. Like I wish they had

Hi everyone, I have looked through the list archives and seen a few posts about jumbo frame support, but there is no definitive answer on whether or not it has been tested or is working for anyone. I tried using an MTU of 9000 in a domU and encountered some very interesting and not-so-great results. My machines used in this test are: * NFS (physical) * dom0 (physical) * domU (virtual)

Hi, I''m new to Xen and I''ve set up a few domUs using Debian (I suspect there may be a problem there, see at end). To begin with everything worked OK, I rebooted domUs without any problems, but twice now when I try when I try to restart or shutdown a domain, the xm command locks up. # xm list Error: Device 0 not connected Usage: xm list [options] [Domain, ...] List information

Package: xen-utils-4.3 Version: 4.3.0-3+b1 Using the xl toolstack there's no information about the networks of the domUs in xentop. I have a PV and a HVM domU and both are shown as having 0 network interfaces, while in fact they have functioning interfaces. Here's one of the interfaces that should be shown, from xenstore: 29 = "" 0 = "" frontend =

Hi everybody! I know this is an ultraknown issue, but in my case i think it is going beyond. As you may guess my domUs clocks go faster or slower They come with the same OS (Centos 5 2.6.18-92.1.18.el5 ) but each of them have a different clock speed. Why? Dom0 does not syncronize domUs : So i watched out looking for any solution.... First attempt: /proc/sys/xen/independent_wallclock = 0

Hello, I have a live migration problem on my setup. Migrated DomUs hang, but continue as normal when migrated back. Both nodes are i386 Debian Squeeze dom0 (xen 4.0.1 + pvops0 2.6.32-5-xen-686) Node A is a 32bits 2.4 Ghz Pentium4, node B is a 32bits 2.0 Ghz Celeron. DomUs are Debian Squeeze (2.6.32-5-xen-686 >= 2.6.32-22 or 2.6.32-5-686-bigmem >= 2.6.32-22) and Ubuntu Maverick

Hello, I''m using my dom0 on a RHLE 4.4 with xen 3.0.4-1. My domUs work on the same O/S, and any virtual disk is composed by 5 files : disk = [

Hi folks, I am using Xen 2.0.7 with debian based dom0 and domUs on several machines. Every few days I find the clocks of dom0 and domUs on the same machine to differ between seconds and hours. I know this is mentionened every now and then on the list. What I want to know: Is this bug still officially not fixed? Is something done to fix it or is it left as is? I just have to know the state

Hello, On a xenserver with several (39) domUs, we experience problems with the system clock of the domUs. The clock seems to drift away several seconds up to two minutes from the dom0 clock. We do have set independent_wallclock=0. According to the docs (i.e. http://wiki.xensource.com/xenwiki/InstallationNotes) that way domUs should use the dom0 clock, but apparently that''s not the case.

Hello! I've noticed this problem two times now.. last time I fixed it by rebooting the (centos 5.1 x86 32b) xen host/dom0. Symptoms: - Already running domUs (debian 2.6.18-6-xen-686 32b PAE) continue running and working OK - Cannot start new domUs (debian 2.6.18-6-xen-686).. kernel bootup just hangs before running initrd. Same domU with the exact same xen domU cfgfile worked earlier.

On Thu, Apr 7, 2016 at 5:46 PM, exvito here <ex.vitorino at gmail.com> wrote: > Hello all, > > I'm addressing the mailing list following the suggestion of gwd on > #centos-virt @freenode IRC. > > The subject says most of it. Here are the details : > > - Was running 4.4.x and configured such that /etc/xen/auto domUs would be > saved/restored on dom0

Hi, Im just setting up a new server which I have nearly complete. I have the DomUs automatically starting by placing the sym links in /etc/xen/auto and by executing /etc/init.d/xendomains on startup however I cannot get them to shutdown gracefully. I have set in /etc/default/xendomains to shutdown and not save but it seems this setting is ignored and the DomUs just get killed. Is