similar to: xm list --long and SXP

Hi, i had the problem, if i migrate a domU to another Dom0, i have to copy the sxp file tool (and the same problem in a few other scenarios too). For an easier solution, i created a tool to generate a domU-sxp-file from/for a running DomU. If anyone need it too, it is available here (compiled for amd64): http://www.xncore.com/download/stuff/xntool-running2sxp.gz Usage: xntool-running2sxp

Package: xen-utils-common Severity: minor Version: 3.0.3-0-2 During a domU state transition (at least on domU shutdown), "xm list" seems to occasionally fail. This is only intermittent, but it could cause problems if there are automated tools (or unaware humans) inspecting the output or return codes of "xm list". here's a recent transcript (the numbers preceding the bash

Years ago when i first started using xen i specified a dom0_mem=xxx in grub. I no longer do this, what i do now is set the dom0_min-mem setting in xend-config.sxp to 1024. I also have a few scripts that run at boot and one of them does a `xm mem-set 0 1024`. after that a xm list 0 shows dom0 allocated 1024 Ram. The problem comes on teh system when i run free or free -m, free shows dom0

Package: xen-utils-common Version: 3.0.3-0-2 Severity: normal After running "halt" in a couple of domains I ran "xm list" repeatedly to see when the halt command was complete. Below is some of the output. The "Device 0 not connected" should not occur. yoyoxen:~# xm list Name ID Mem(MiB) VCPUs State Time(s) Domain-0

Hi folks, is there a tool to convert a vm''s classic config file to sxp? I tried "xm create OLDCONF -n" and pasted the output in a config file at /var/lib/xend/domains/SOMEFOLDER/config.sxp, but that did not make virsh recognize the vm at all (although I restrarted xend, which helps for example after virt-clone). I am trying this on Xen4 using Debian6. Dirk

QUESTION: What, if anything, can I do so that I can use xl (in place of xm) with libvirt 1.0.2 and Xen 4.2.1 in Ubuntu 13.04? BACKGROUND: I am testing a fully updated (as of March 27) installation of Ubuntu 13.04 that includes the following packages: libvirt - version 1.0.2-0ubuntu9 xen-hypervisor-4.2-amd64 - version 4.2.1-0ubuntu1 Upon setting TOOLSTACK=xm in /etc/default/xen (as well as

Right now xm will return 1 if you run `xm list non_existant_domain` Wouldnt it be a better idea to have a specific error code for this error so that scripts wrapping around xm can better determine if the domain does not exist or if xm just failed for whatever reason? ~Shaun _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com

Package: xen-utils-common Version: 3.0.3-0-2 Error message: # xm create test.cfg -c Error: Device 0 (vif) could not be connected. Backend device not found. /etc/xen/xend-config.sxp contains an error in its default configuration. Line 87 should read: (network-script network-bridge) Not: (network-script network-dummy)

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

Hi, I want to use xm on xen-api-server. So first, I uncomment the following lines in /etc/xen/xend-config.sxp: (xen-api-server ((9363 pam ''^localhost$ example\\.com$'') (unix none))) and then restart xend, it seems all right: # netstat -anp | grep 9363 tcp 0 0 0.0.0.0:9363 0.0.0.0:* LISTEN

Package: xen-utils-common Version: 4.4.0-5 Severity: important Tags: patch Hello, xen-init-list fails to parse output of xen list -l when using XM toolstack. Therefore, /etc/init.d/xendomains stop fails to shutdown any guests still running on shutdown. xen-init-list fails with the following message: /usr/lib/xen-common/bin/xen-init-list Traceback (most recent call last): File

Package: xen-utils-common Version: 4.1.2-1 Severity: grave Justification: renders package unusable (Grave because dash is the default /bin/sh) With dash 0.5.5.1-7.4 as /bin/sh, /usr/sbin/xm enters an infinite loop of reexcuting itself. When run with bash, it works correctly. I traced that to /usr/lib/xen-common/bin/xen-toolstack; here's the diff between "/bin/sh -x /usr/sbin/xm"

Package: xen-utils-common Version: 4.3.0-3 Severity: normal Dear Maintainer, I've just set up a fresh Jessie system using the installer dated 2014-03-05, then installed and enabled Xen 4.3. I've done this quite a few times before using Wheezy and 4.1. I set up xenbr0, then created a test domU using xen-create-image, which completed without issue. However I was unable to start the new

During investigation of other issues, it came to light that in at least 4.2.2, "xl list -l" displays domain ids as -1 when using SXP, irrespective of actual value. Ian C identified that this issue was likely fixed in the upcoming 4.3 release but the commit responsible for the fix (a73a7a0c647a9a5e30d8bc473c0a1e8648817183) was not likely a candidate for backporting in its entirety.

Hi! New installation (debian jessie) -> missing of /etc/xen/xend-config.sxp file. Package: xen-utils-common (4.4.1-3) -- (O__ ------------------------------------------------------ //\ / Varosi Csokonai Konyvtar // ) | Tel.: 59/503-152 V__/_ szistvan at tux.hu \ szistvan at mail.vcsk.hu

Package: xen-utils-3.0.3-1 Version: 3.0.3-0-1 Severity: normal Tags: patch Manpages that are provided with the source are not included with the utilities. Use perl-doc package at build-time to generate appropriate manpages and dh_manpages to install them in the appropriate locations. diff -urN xen-3.0-3.0.3-0/debian/control xen-3.0-3.0.3-0.new/debian/control --- xen-3.0-3.0.3-0/debian/control

Hi. I found this issue with IA64 box while looking at the c/s of 18204:21dd1fdb73d8, but I believe the things is same with x86 box. I''m not sure whether this patch coexist with the old ioemu which is to be removed soon. So it might be desirable to apply this patch after deleting the internal ioemu tree. thanks, xm: Don''t spawn vncviewer twice. Without this patch, vncviewer

On one of my xen hosts a virtual machine does not start at boot. I can see that xendomains gives an error: service xendomains start Starting auto Xen domains: fszeleNo handlers could be found for logger "xend" Error: Disk isn't accessible No handlers could be found for logger "xend" Error: Disk isn't accessible An error occured while creating domain fszele: Usage: xm

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

Hi, Xm list and xm vcpu-list show wrong DomID(name). Under this situation, # xm list Name ID Mem(MiB) VCPUs State Time(s) Domain-0 0 512 1 r----- 1064.6 test1 13 64 1 r----- 83879.7 # xm list 1 13 Error: Domain ''1'' not found when running ''xm list'' # xm list