similar to: how to use xm on xen-api-server

Hi, I have successfully upgraded from Xen 4.1.3-rc1-pre to Xen 4.2-unstable. Please refer to the following document for the installation instructions. Installation Instructions for Xen 4.1.x or 4.2-unstable and Linux Kernel 3.x.x on Ubuntu and Debian Linux - Version 1.1.pdf =========================================================================== Download link:

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

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: 4.3.0-3 Severity: normal Dear Maintainer, * What led up to the situation? I upgraded my server from squeeze to wheezy and then to jessie. Server is Intel S3200SHV m/b with Intel(R) Core(TM)2 Quad CPU. I'm pretty sure that before that it was running whatever came before squeeze, I forget the name. I was trying to get xen_pciback to work, so I

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

I have an installation of 32bit SLES 10.1 on 2 servers in my lab that I just rebuilt. I applied the files from xen-3.1.0-install-x86_32.tgz and broke all the virtman functions. The errors I got indicate some missing python classes, specifically xen.install. I''m not sure why. This is what I get when I try to run virtman from the command line. If I try to run it from yast i get nothing.

Fix config file parsing for VMX domains. If we define "vif" in the config file, image.py will raise error "vmx: missing vbd configuration". The reason is "vif" is dealt with as a "vbd" device. This patch fixes this issue by dealing with "vbd" and "vif " separately, removing "macaddr" arg and parsing mac address from

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

Hi, i''m using xen 4.2.1 when i do xm list it is getting permission denied, xend.log logs as 2013-10-04 11:54:05 10244] INFO (XendDomainInfo:169) Recreating domain 0, UUID 00000000-0000-0000-0000-000000000000. at /local/domain/0 [2013-10-04 11:54:05 10244] DEBUG (XendDomain:476) Adding Domain: 0 [2013-10-04 11:54:05 10244] DEBUG (XendDomainInfo:1882) XendDomainInfo.handleShutdownWatch

''vncdisplay=N'' in hvm config file is ignored when building qemu-dm arguments. xm create or xm new -> xm start with hvm config file containing vnc=1 vncdisplay=5 results in ''-vncunused'' being passed to qemu-dm. There are several approaches for a fix - this patch defaults vncdisplay to None in xm options. It currently defaults to 1 and is always included in

I can't get xen live migration to work - CentOS 5.6. I have set up xend-config.sxp as per RHEL5 virtualization guide, but when I try it, I get [root at xenhost1 ]# xm migrate testwww xenhost2 -l Error: (104, 'Connection reset by peer') Usage: xm migrate <Domain> <Host> Migrate a domain to another machine. Options: -h, --help Print this help. -l, --live

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello, since pinning the cpu cores to Dom0 and the DomUs the shutdown of the VMs doesn''t work anymore. When shutting down or rebooting a DomU the DomU just freezes after the shutdown process but won''t reboot or stop the DomU. The shutdown itself seems to be complete though. We can reproduce this problem on 4 different servers.

xm list --long says it outputs the server details in SXP, what is SXP, i want to parse this output using perl. ~Shaun _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

> From: Nico Kadel-Garcia <nkadel@gmail.com> > Date: December 28, 2006 6:32:42 AM EST (CA) > To: Ian Pratt <m+Ian.Pratt@cl.cam.ac.uk> > Cc: "Bhatia, Nikhil" <bhatia@ornl.gov>, xen- > devel@lists.xensource.com, xen-users@lists.xensource.com, > ian.pratt@cl.cam.ac.uk > Subject: Re: [Xen-users] RE: [Xen-devel] Xen-3.0.3 migration problems > >

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