similar to: Bug#648670: xm was unable determine an actual domU state under some conditions

Hi, I tried to test a wrong operation on purpose again. When I tried xm sysrq command to a inactive managed domain, I saw the following error message. The error message did not have a message text behind "Error:". And I found an AssertionError message in xend.log. # xm list PVdomain.1 Name ID Mem VCPUs State Time(s) PVdomain.1

Package: xen-utils-4.1 Version: 4.1.4-3+deb7u1 Severity: important When starting (or migrating in) a domain, sometimes I get the following exception: [2014-04-01 10:58:08 4821] ERROR (XendDomainInfo:2927) XendDomainInfo.initDomain: exception occurred Traceback (most recent call last): File "/usr/lib/xen-4.1/bin/../lib/python/xen/xend/XendDomainInfo.py", line 2914, in _initDomain

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

Dom0 = centos 5 (32bit), 4GB Ram DomU = centos 5 (PV) (32bit) xen 3.1.2 rc1, compiled using XEN_TARGET_X86_PAE=Y kernel 2.6.18, modified to load areca card drivers initrd image created using the following command mkinitrd -v -f --with=aacraid --with=arcmsr --with=sd_mod --with=scsi_mod initrd-2.6.18-xen.img 2.6.18-xen When i issue xm create for a domU which was working earlier i get the

Hi Moonwalker, You might have some luck poking around under /var/lib/xend/*, or perhaps by removing and recreating the guest. Unfortunately the xend toolstack is not really maintained upstream (to be honest it is unmaintainable and no one has stepped up). Since you are using the "managed domains" functionality you might be interested in the xcp-xapi package which is in Wheezy today.

*After running intensively (i.e. running >10 guests and migrating them all into other machines etc.) , I wasn''t able to * *run xen tools as the following messages show. * ** ># xm list Error: (9, ''Bad file descriptor'') Usage: xm list [options] [Domain, ...] List information about all/some domains. -l, --long Output all VM details in SXP

Package: xen-utils-common Version: 4.2.1-2 Severity: important After run xm create -c win2008.hvm Using config file "./win2008.hvm". Error: 'NoneType' object has no attribute 'rfind' /var/log/xen/xend.log: [2013-06-10 21:48:59 31935] ERROR (xmlrpclib2:181) Internal error handling xend.domain.create Traceback (most recent call last): File

Package: xen-utils-common Version: 3.0.3-0-2 Severity: important I have installed all the packages I can think of to get Xen going and it still fails with the following : /var/log/xen/xend-debug.log: Exception starting xend: (111, 'Connection refused') er.py", line 463, in process_request_thread self.finish_request(request, client_address) File "SocketServer.py",

Hi all, I''m a total xen-newbie ... I''ve installed xen-3.0-testing from source. (http://www.cl.cam.ac.uk/Research/SRG/netos/xen/downloads/xen-3.0-testing-src.tgz). I''ve followed the intruction for the installation, dom0 work fine and domU start up without problem !!! Now, I''ve tryed to migrate the domU to another dom0 machine but I receive this error on the

Package: xen-utils-3.2-1 Severity: important Hello! When using xenapi.PBD.create() the following error occurs: xen.xm.XenAPI.Failure: Internal error: global name 'genuuid' is not defined. (Attached you can find the logging of the remote host.) This (and other syntax errors) are already fixed in the xen-unstable.hg (see http://xenbits.xensource.com/xen-unstable.hg?rev/7fd49c55c0b0).

Package: xen-utils-4.0 Version: 4.0.1~rc6-1 Severity: important Issue confirmed with xen-utils-4.0 (4.0.1~rc6-1) in Debian Squeeze AMD64. Trace of error while using xm-debian.cfg (attached): [2010-09-02 00:53:21 1407] ERROR (xmlrpclib2:178) Internal error handling xend.domain.create Traceback (most recent call last): File "/usr/lib/xen-4.0/lib/python/xen/util/xmlrpclib2.py",

Hello I use xen and I am trying to use the parallel port of Centos 5.2 host from a Windows XP (HVM) guest. I have tried to transfer control of the port by blacklisting lp, parport and parport_pc + adding: ioports = [ "0378-037a" ] to the xen configuration file. However, in the presence of this line, xm create replies with: Error: function takes exactly 4 arguments (3

Hi all, I am trying the pci-passthrough on xen 3.3.0. I binded the pci slot to pciback using late binding. But xend fails to allocate this slot to domU. linux-242:/home/xen-3.3.0 # xm create -c pci=08:01.0 /etc/xen/xen3.3_guest1 Using config file "/etc/xen/xen3.3_guest1". Error: [Errno 2] No such file or directory: ''/sys/bus/pci/devices/0000:06:00.0/config''

Hi, I have a problem that I can't solve it: the hvm-guest don't start (same image works under Xen 4.01 on another machines). Further I'm confust, because I had to use xm instad of xl. A PV-guest works fine. I start it with 'xm create jessie'. Some data you can see down. What further information do you need? vg. ------------------------------------------------- call with

Is serial port "passthrough" possible for the version of xen that ships with centos 5.2? I've disabled the xen hypervisor serial console, and can see the serial port in dom0. I've masked out the 8250, 8250_pnp and serial_core modules on dom0 and rebooted. xm create domain fails with the error that exactly 4 arguments are required and only 3 were given. Steps I followed: 1) I

Xen Version: 4.2.0 Linux Kernel Version: 3.2.30 OS: Debian 6.0 Sometimes when trying to reboot a VM, the reboot fails with the following message in xend.log: Has anyone experienced this issue before, know the cause and/or fix? This is an HVM VM. Device model is set in the configuration file device_model = ''/usr/lib/xen/bin/qemu-dm'' We use the same configuration file with

Hi I''m a sysadmin and I''ve installed on my server Red Hat Enterprise Linux 5 to use its xen embedded with six virtual machines just created and running. Now I have a problem: when I attempt to create my seventh virtual machine, xen gives me this error: Error: destroyDevice() takes exactly 3 arguments (2 given) In /var/log/xen/xend.log find this errors: [2007-11-13 11:34:00

Hi I have configured few VMs with RHEL5,32 bit, but some VMs after successful stop/restart few times, suddenly they start giving following error from "xm create vm1.cfg" startup. ---- Error: (''c618d493-a696-7637-333d-bd891fa41ac2'', ''VM_metrics'') ---- If i replace system.img, they starts working again. This is what i see in xend.log file. This happens

Thanks a lot....recompiling xen-tools wih ioemu flagsolved my problem. Daniel Bojczuk On Sun, Jun 27, 2010 at 10:55 AM, Mohamed Yacoubi <myacoubi@euro-web.fr> wrote: > Hi, > Can you recompile xen-tools with USE = "ioemu" ? > That should solve the problem. > Best regards, > Le 22 juin 2010 à 22:01, Daniel Bojczuk a écrit : > > I stiil did not solve te

I have built a dom 0 using a Gentoo Linux kernel. All is up and running with no errors. I downloaded a Centos 4.4 image from the web and when I rum xm I get an error 22. Does anyone know what I am doing wrong and/or where I can find more documentation on running unmodified VMX guest domains. The Xen 3.0 Users Manual is out of date. Here is the control file: sun temp # cat