search for: xentester

Hi. I have following errors in my log file: Mar 22 05:33:11 xentest libvirtd: 05:33:11.518: error : failed Xen syscall topology cpuset syntax error Mar 22 05:33:21 xentest libvirtd: 05:33:21.418: error : failed Xen syscall topology cpuset syntax error Mar 22 05:33:41 xentest libvirtd: 05:33:41.274: error : failed Xen syscall topology cpuset syntax error Mar 22 05:33:41 xentest libvirtd:

...gt; Thanks for pinpointing the issue, here is the command line use for domU > installation: > virt-install -l http://mirror.centos.org/centos/5/os/i386/ -p -n cent5 -r 768 --vcpus=1 --disk=/srv/xen/mailserver.img --graphics vnc,listen=0.0.0.0,port=5901 Here is my kernel info: uname -a Linux XenTester 3.1.0-rc9+ #1 SMP Mon Mar 12 18:18:34 CDT 2012 x86_64 x86_64 x86_64 GNU/Linux Other xen related info: [root at XenTester su]# /etc/init.d/xend start [root at XenTester su]# xm list Name ID Mem VCPUs State Time(s) Domain-0...

Hello Community, I encountered an error while running "xm console domU". Here is the running script: # xm console domU xenconsole: Could not read tty from store: No such file or directory I googled and found out that this issue is mostly result from forgetting starting xenconsole service. However, after I started xenconsole, the issue is still there. Please see: #

I try to bring up xend but get this error in the xend-debug.log /etc/xen/scripts/network-bridge: line 62: ip: command not found Link veth0 is missing. This may be because you have reached the limit of the number of interfaces that the loopback driver supports. If the loopback driver is a module, you may raise this limit by passing it as a parameter (nloopbacks=<N>); if the driver is

Hi, the problem is as follows:(And then, others can't login mostly because of the os' busing and you can't do anything else.) [**@xentest ::三 12月 21::~]$ sudo xm list Name ID Mem VCPUs State Time(s) Domain-0 0 1748 2 r----- 29396.3 xp-101 1 256

I dont know gentoo, but the package might be called iproute2. You might also need the bridge-utils. Regards Dominik Friedrich Nietzsche schrieb: > Thanks found the issue atleast, here is what I get: > > xentest scripts # which ip > which: no ip in >

Hello Community, I am installing a domU image via virt-install. However, it seems that a driver needs to be installed for the connection as I saw an error while running the command. Can anyone give any hints about this error? Here is the running script: # virt-install --connect=xen:/// -p -d Thu, 15 Mar 2012 10:17:55 DEBUG Launched with command line: /usr/bin/virt-install --connect=xen:///

Hello Community, I am installing a domU image via virt-install. However, it seems that a driver needs to be installed for the connection as I saw an error while running the command. Can anyone give any hints about this error? Here is the running script: # virt-install --connect=xen:/// -p -d Thu, 15 Mar 2012 10:17:55 DEBUG Launched with command line: /usr/bin/virt-install --connect=xen:///

I run a centos6.2 guest VM in xen4.1.2, the id of centos-domU is 22. The info of dom0 is: 2.6.32-131.21.1.el6.xendom0.x86_64 #1 SMP Tue Dec 13 18:09:29 EST 2011 x86_64 x86_64 x86_64 GNU/Linux Centos-domU: 2.6.32-220.7.1.el6.x86_64 #1 SMP Wed Mar 7 00:52:02 GMT 2012 x86_64 x86_64 x86_64 GNU/Linux At dom0, I went like this: [malei@xentest-4-1 Tue Apr 30 ~]$ sudo gdbsx -a 22 64 9999 Listening on

Hello Community, I successfully installed and run xen (xm list and xm info can output appropriately). However, while I was installing domU image by using virt-install -p at domU OS. I encountered an error information" Host does not support virtualization type ''xen'' ". I built xen from source. Some of my friends have the same issue, but if they use pre-build xen, the

I installed Debian sarge amd64 on a Intel em64t processor machines and have been using the Xen 3.0 packages in backports.org. I can boot a 32 bit guest OS fine if I use the vmlinuz-2.6.16-1-xen-em64t-p4kernel, but when trying to use the stock vmlinuz-2.6.16-xen from their binary tarball, or building it from the source package I get the following error: xentest:/var/log# xm create debian0.cfg -c

Hi, I seem to remember that there used to be ISO downloads of Xen available, for people wanting to give it an easy way for a test drive, and to submit (automated) feedback on which machines and configurations Xen ran (in)correctly. However, I do not seem to be able to find these ISO images for download at Xen.org anymore. Has the project stopped making these useful test images - and if so, why ?

Hi, I seem to remember that there used to be ISO downloads of Xen available, for people wanting to give it an easy way for a test drive, and to submit (automated) feedback on which machines and configurations Xen ran (in)correctly. However, I do not seem to be able to find these ISO images for download at Xen.org anymore. Has the project stopped making these useful test images - and if so, why ?

docs/man/xl.pod.1 | 6 +++++- tools/libxl/xl_cmdimpl.c | 39 ++++++++++++++++++++++++++++++++++++--- tools/libxl/xl_cmdtable.c | 3 ++- 3 files changed, 43 insertions(+), 5 deletions(-) xl: Introduce shutdown xm compatibility option -a to shutdown all domains Signed-off-by: Sander Eikelenboom <linux@eikelenboom.it> diff -r 9dc729b75595 -r 67f9ef649937 docs/man/xl.pod.1 ---

I am starting an instance passing xml configuration like this. Contents inside my kickstart file is this *apt-get install vim --assume-yes* . But I think kickstart is not considered while booting instance though I am able to start instance. Please help. Thanks in advance "<domain type='xen'>" + " <name>testVM-server</name>"

If I tell it to use an NFS source (eg nfs://server/mnt/cdrom) then itin Centos5 tries to do a CIFS mount instead (I can see it running mount.cifs and in the xterm I ran virt-manager from it then asks for a password). Wow. If I tell it to use an lvm2 volume (/dev/VolGroup00/xentest - already created at 1Gb) then it goes through, calculates the amount of space required etc etc and then barfs with

Hi, we have some problems with acpidump running on Xen Dom0. On 64 bit Dom0 it will trigger the OOM killer, on 32 bit Dom0s it will cause a kernel crash. The hypervisor does not matter, I tried 4.1.3-rc2 as well as various unstable versions including 25467, also 32-bit versions of 4.1. The Dom0 kernels were always PVOPS versions, the problems starts with 3.2-rc1~194 and is still in 3.5.0-rc3.