similar to: [PATCH] [XM] Pass --skipdtd parameter to ''xm new'' application

Pyxml/xmlproc is being used in tools/xen/xm/xenapi_create.py but is unmaintained for several years now. xmlproc is used only for validating XML documents against a DTD file. This patch replaces the pyxml/xmlproc based XML validation with code based on lxml, which is actively maintained. Signed-off-by: Stephan Peijnik <spe@anexia.at> diff -r 6e0ffcd2d9e0 -r 7082ce86e492

Hello, i have Centos5.1 64bit, with xen3.2, using centos xen kernel, xen3.2 builded from source rpm for centos. Virtual machines work fine trough xm create configname ,but when i am trying to add them to xen source : xm new configname, this is what i get : [root at xen-prod xen]# xm new test01.hvm Unexpected error: exceptions.ImportError Please report to xen-devel at lists.xensource.com

Hi, i am running Centos5.1 i386, with xen3.2.0 compiled from source rpms provided on xen.org. As dom0 kernel i am using centos-xen kernels. When i am trying to add new machine to xen source using xm new, this is what i get : [root@xxx /]# xm new centos01 Unexpected error: exceptions.ImportError Please report to xen-devel@lists.xensource.com Traceback (most recent call last): File

Package: xen-utils-common Version: 3.4.2-2 Severity: important On a fresh Debian Sid system, I get this: # xm new Unexpected error: <type 'exceptions.ImportError'> Please report to xen-devel at lists.xensource.com Traceback (most recent call last): File "/usr/lib/xen-3.4/bin/xm", line 8, in <module> main.main(sys.argv) File

Le vendredi 20 juin 2008 08:48, vous avez ?crit?: > tags 487165 moreinfo > thanks > > On Thu, Jun 19, 2008 at 11:57:49PM +0200, Laurent L?onard wrote: > > xm create requires the python-xml package to work, perhaps it should be a > > dependency of xen-utils-common ? > > For what does xm create need python-xml? For me it works fine without. > > Bastian Sorry I

Package: xen-utils-common Version: 3.2.0-2 Severity: normal --- Please enter the report below this line. --- This bug is a duplicate of the bug #487165, but I tagged it as wishlist and I have no answer about it. But I think it should be interesting to correct it, sorry for this. xm new requires the python-xml package to work, perhaps it should be a dependency of xen-utils-common ? debian:~#

I''m using a source-compiled Xen-4.0.2-rc1-pre (changeset: Fri Sep 17 17:06:57 2010 +0100 21350:6e0ffcd2d9e0) on a brand new Debian Testing (Squeeze/sid) install. The first problem that I ran accross was just getting xend to start. I was getting a python error saying that it couldn''t import SrvDaemon. I got around that by moving /usr/lib/python2.6/site-packages/xen to

This fixes the xapi test case 02 with those parts that currently do not work disabled with ''if 0:'' Signed-off-by: Stefan Berger <stefanb@us.ibm.com> Index: root/xen-unstable.hg/tools/xm-test/tests/xapi/02_xapi-vbd_basic.py =================================================================== --- root.orig/xen-unstable.hg/tools/xm-test/tests/xapi/02_xapi-vbd_basic.py +++

The following test case does local migration 3 times in a loop. I currently see the following error output on x86-64 (only!) inside the guest (change debugMe in line 68 of xm-test/lib/XmTestLib/Console.py to True): @%@%> XENBUS error -12 while reading message XENBUS error -12 while reading message XENBUS unexpected type [1325400064], expected [4] XENBUS error -12 while reading message XENBUS

This enables the usage of a bootloader, i.e., pygrub, when starting a domain using xm in Xen-API mode. Signed-off-by: Stefan Berger <stefanb@us.ibm.com> _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

Hello! I have new xen-3.3.0 installed and working on latest Ubuntu Hardy, with Linux 2.6.18-xen from xen.org. When I run "xm new" I got this error: root@hyper02:~# xm li Name ID Mem VCPUs State Time(s) Domain-0 0 512 1 r----- 1869.9 vsrv65 4 1024 1

hello, Env: Ubuntu Karmic Server 9.10 Xen 4.0 rc8 kernel 2.6.32.10 pv_ops Trying to import a working xen cfg file into domain management causes this crash. This ability is not so vital, but maybe someone can shed light on the missing packages/thing. tlviewer@ubsvr91:~$ sudo xm new /etc/xen/vm/karmic.py Unexpected error: <type ''exceptions.ImportError''> Please report to

Hi, I can confirm, missing dependency on pyton-xml for 'xm new...' command. lin:/etc/xen# xm new lenny1 Unexpected error: <type 'exceptions.ImportError'> Please report to xen-devel at lists.xensource.com Traceback (most recent call last): File "/usr/lib/xen-3.2-1/bin/xm", line 7, in <module> main.main(sys.argv) File

Package: xen Severity: important Hello, New install of XEN 4.0, can't create a vm : xm new k2000-shinken Unexpected error: <type 'exceptions.ImportError'> Please report to xen-devel at lists.xensource.com Traceback (most recent call last): File "/usr/lib/xen-4.0/bin/xm", line 8, in <module> main.main(sys.argv) File

Package: xen-utils-3.2-1 Version: 3.2.1-2 Severity: important The xm command has an option to define a domain in Xen: xm new vm_config_file.cfg Using default dependences it isn't working: :~# xm new oromigration-oromail.cfg Unexpected error: <type 'exceptions.ImportError'> Please report to xen-devel at lists.xensource.com Traceback (most recent call last): File

When redirecting the output of the echo command using ''>'' on bash, the output seems to be broken up into multiple write()s (depending on the version of busybox?). Unfortunately /dev/tpm0 needs to have the complete command written to in one chunk. The work-around ''echo <string> > file ; cat file > /dev/tpm0'' seems to get around this problem. The

Package: xen-utils-common Version: 4.0.0-1 Severity: important The xm utility requires python-xml but the package does not depend on it. # xm new --help_vars Unexpected error: <type 'exceptions.ImportError'> Please report to xen-devel at lists.xensource.com Traceback (most recent call last): File "/usr/lib/xen-4.0/bin/xm", line 8, in <module>

Package: xen-utils-4.0 Version: 4.0.1-2 Severity: normal VM created successfully when I edit this file: /usr/lib/xen-4.0/lib/python/xen/xm/xenapi_create.py comment line 22 : #from xml.parsers.xmlproc import xmlproc, xmlval, xmldtd -- System Information: Debian Release: 6.0 APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-5-xen-amd64

This patch rewrites the rtc/timeoffset entry so the VM''s record can be retrieved with the Java xmlrpc library. If the entry is ''None'' it upsets the xmlrpc parser. This fixes it, though maybe there''s a better place in xend to place similar code. Signed-off-by: Stefan Berger <stefanb@us.ibm.com> _______________________________________________ Xen-devel

This patch adds a TPM device model to the qemu dm for fully virtualized VMs. It is enabled in the VM only if the user requests a TPM device in the vm configuration file using the ''vtpm=[...]'' line. It enables the qemu device model command line with a ''vtpm_instance <instance number>'' parameter. Signed-off-by: David Safford <safford@watson.ibm.com>