similar to: Xen API or XM

I tried to start a domain that I knew would fail, as the vbd it would use was already in use. However, Xend entered a state that made xm unusable and I had to restart it: # xm create -c hal2.xm Using config file "./hal2.xm". /usr/lib/xen/bin/xenconsole: invalid option -- 1 Invalid number of arguments Try `/usr/lib/xen/bin/xenconsole --help'' for more information. # xm list

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

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

Currently console class''s "other_config" parameters (such as "vnclisten" and "vncpasswd") are not passed to xend when creating a domain by xm command through xen-api. The attached patch fixes this problem. Regards, ----------------------- Yosuke Iwamatsu NEC Corporation _______________________________________________ Xen-devel mailing list

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

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

On 2/12/19 1:35 AM, Gabriel F. T. Gomes wrote: > On Sun, Feb 10 2019, Hans van Kranenburg wrote: >> >> Please remove the 'xm' file from the bash-completion package. This >> command does not exist in Xen any more (last time it was relevant was in >> Jessie, where it was already deprecated). > > That should be easy to do for Debian. On the other hand, I

I've just done a fresh lenny amd64 install, and taken the xm-debian.cfg example: http://people.debian.org/~joeyh/d-i/images/daily/netboot/xen/xm-debian.cfg and built a 32 bit lenny inside a 64 bit lenny dom0 # xm create -c xm-th2.cfg install=true install-installer=http://people.debian.org/~joeyh/d-i/images/daily/ When I try to boot the domU: # xm create -c xm-debian.cfg it

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

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.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:~#

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

Hi all, I'm running Centos 5.5 with Xen 4.0.1 Would like to use a USB key (not a block device) in my domU. Dom0 lsusb yields; Bus 002 Device 004: ID 064f:0bd8 ABC-Systems AB CDE/FG xm usb-add shows; Usage: xm usb-add <domain> <[host:bus.addr] [host:vendor_id:product_id]> Not sure what combo will work in this case. However, I've read some notes regarding xm usb-attach.

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

Package: xen-utils-common Version: 3.0.3-0-2 Severity: normal gzip -3 compresses the Xen save files in a reasonably small amount of time and makes them take less than half the space that they might otherwise require. On systems with an encrypted root filesystem and on systems that have really fast CPUs if xm supported such compression then that would increase the speed of xm save and xm restore

Virsh (the xm-like tool that comes with libvirt) uses .xml files to define and describe DomUs. xm uses simple configuration files to define and describe DomUs. Is there any interoperability between these two? Like can virsh take an xm DomU config file, or vice versa? Or is there a tool to translate between them? On a somewhat related note, can anyone tell me at a high level what is different

Hi, I don''t understand something about the vcpu-set function. My configuration: *memory = 2048 cpu = ''1-2'' maxvcpu = 4 vcpus = 1* When the DomU is running, and when i try to set 2 or 3 vpcu i get the error : xm vcpu-set domain_name 2 *Error: Cannot set vcpus greater than max vcpus on running domain Usage: xm vcpu-set <Domain> <vCPUs> Set the number of

Dear All, I am trying the test suite named xm-test for Xen testing. I have finished the installation of the test suite by following its README document. But I got import error that can not find a module named "xs", when I tried to run all test scripts provided by xm-test. The error message is presented as follows: Traceback (most recent call last): ...

Processing commands for control at bugs.debian.org: > retitle 655301 xend shouldn't start if TOOLSTACK is not xm Bug #655301 [xcp-xapi] xcp-xapi fails to start Changed Bug title to 'xend shouldn't start if TOOLSTACK is not xm' from 'xcp-xapi fails to start' > reassign 655301 xen-utils-common Bug #655301 [xcp-xapi] xend shouldn't start if TOOLSTACK is not xm Bug