similar to: Xend fails to start on newly compiled xen dom0 kernel

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

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

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

Package: xen-utils-4.1 Version: 4.1.1-3 I have an HVM domU which was created with xen-utils-4.0 (and Xen 4.0 hypervisor of course). Recently I've upgraded to Xen 4.1 and xen-utils-4.1, but after a reboot I was unable to do anything with it: "xm start" caused "Domain is already running" error, while "xm shutdown" simply hadn't printed any error messages, only

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 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

Hi all, after upgrading from xen 3.0 to xen 3.2 I cannot start my domUs: I get: VmError: Boot loader didn''t return any data! Suggestions? This is the log [2008-06-25 11:24:53 2755] DEBUG (XendDomainInfo:84) XendDomainInfo.create([''vm'', [''name'', ''engtest3.infolan''], [''memory'', ''2048''],

Hello all; I am trying to create SuSE10 guest under my FC5 host, this configuration has worked before but due to abnormal shutdown of my server i get the following error while trying to create the guest OS; ** the same configuration *used to* work just fine *#xm create -c /etc/xen/suse.cfg* ------------------------------------------------------------------------------------- Using config file

Hi,    I''ve been using xVM with no problems since 2009.06 release (centos4/5, rhel4/5, sol10 as guests). This was using the 111a version. Just installed a new server with the 111b version and .... virt-install --nographics -p -r 8192 -n CentOS_48_64_92 -f /dev/zvol/dsk/zm0/vm/CentOS_48_64_92 -l ftp://192.168.101.120/pub/CentOS-48 -w bridge=aggr0 --os-type=linux --os-variant=rhel4

Hello, yesterday a coworker had to reboot one VM, the Vm did shutdown but never came back up. We are USing CentOS 5.1 and XEN xen-3.0-x86_64. What can be the reason of this behavior? Here ist the part of the logfile: [2008-07-02 15:04:18 xend.XendDomainInfo 31150] INFO (XendDomainInfo:947) Domain has shutdown: name=auto-input-vm1 id=26 reason=reboot. [2008-07-02 15:04:18 xend.XendDomainInfo

Hi -- I''m getting this error even though I have correct DVD ISO image for snv_92. bash-3.2# uname -a SunOS stoakly2 5.11 snv_92 i86pc i386 i86xpv bash-3.2# xm create snv.py Using config file "./snv.py". Error: (2, ''Invalid kernel'', ''elf_xen_note_check: ERROR: Will only load images built for the generic loader or Linux images'') bash-3.2#

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

I am trying to get a vm running on a different host. It fails to start with the error below. Both hosts are running the same software CentOS 5.4 and Xen 3.3.1 any clues as to why it fails would be appreciated. [2009-05-04 15:31:59 3933] DEBUG (XendDomainInfo:89) XendDomainInfo.create([''vm'', [''name'', ''agree-37''],

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

Hi, I have 6 DomU's with 4-virtual interfaces and 1 DomU with only one. When starting the DomU's in order where the domain with only one interface is started last it refuses to start with following error. If I start it first there is no problem starting them all. ---Error--- [2011-10-02 18:37:33 xend.XendDomainInfo 6728] DEBUG (XendDomainInfo:1335) XendDomainInfo.handleShutdownWatch

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

I am working on FC5 [root@blrkec38274d ~]# xm list Error: Error connecting to xend: No such file or directory. Is xend running? THE LOG FILE xend.log is below.... [2006-06-28 18:22:59 xend] INFO (SrvDaemon:285) Xend Daemon started [2006-06-28 18:22:59 xend] INFO (SrvDaemon:289) Xend changeset: unavailable . [2006-06-28 18:23:00 xend.XendDomainInfo] DEBUG (XendDomainInfo:201)

Hello Xen refuses to create domU VM. I have posted some info about my system. Please suggest a solution. gate xen # xm info host : gate release : 2.6.25.5-1.1dom0 version : #24 SMP Sun Aug 31 16:55:27 EEST 2008 machine : x86_64 nr_cpus : 2 nr_nodes : 1 cores_per_socket : 2 threads_per_core : 1 cpu_mhz : 1999 hw_caps : 178bf3ff:e3d3fbff:00000000:00000010:00000001:00000000:00000003:00000000

# HG changeset patch # User Hollis Blanchard <hollisb@us.ibm.com> # Date 1158780052 18000 # Node ID f7d90f962967a5a94fce0c04f8fcac449f36344f # Parent 041be3f6b38e05f904d240630c18cadb1259317b [XEND] Remove hard tabs. Signed-off-by: Hollis Blanchard <hollisb@us.ibm.com> diff -r 041be3f6b38e -r f7d90f962967 tools/python/xen/xend/XendDomainInfo.py ---

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