similar to: xm migrate help

# HG changeset patch # User john.levon@sun.com # Date 1181229858 25200 # Node ID e46be7b5f9bf2b17f66c82950b4fc3962e1266d0 # Parent 2a188f88483d726cb5b880f948a1baeeb2bd42a1 Remove unimplemented xm migrate --resource option. Signed-off-by: Gary Pennington <gary.pennington@sun.com> diff --git a/tools/python/xen/xend/XendDomain.py b/tools/python/xen/xend/XendDomain.py ---

This patch -Displays[1] current parameters for running domains ala xm list -Allow users to set[2] one or more parameters[3] without having to provide values for parameters they do not wish to change -Adds additional testing of sched-sedf via new xm-test testcases. With this patch applied, test 02_sedf_period_lower_neg.py exposes a bug[4]. I''ll follow up this email with a patch for

I am running xen (first 2.0.5 now 2.0.6) with NetBSD 3.0_BETA as domain and guest OS. If i execute the command "halt -p" in the unprivileged domain and wait till the last message (... done), nothing happens until i press the enter button. Then i get this output: on the screen ************************ REMOTE CONSOLE EXITED ************************ (54, ''Connection reset by

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

''xm block-attach'' doesn''t let me assign the same backend device anymore, even if I use ''r!'' or ''w!''. I think this has changed since 3.1.1 (or maybe since 3.1.0). Is this the way it is supposed to work? Thanks James _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com

Hi, I have a problem with xend on Debian Sarge. I am using the 2.6.12-xen0 kernel with xen-unstable. I also installed the TwistedWeb package TwistedWeb-0.5.0. # xend start /usr/lib/python2.3/site-packages/xen/xend/server/SrvDir.py:4: DeprecationWarning: twisted.protocols.http has moved to twisted.web.http. See http://twistedmatrix.com/projects/web. from twisted.protocols import http I think

>From tools/libxc/xc_atropos.c: int xc_atropos_domain_set(int xc_handle, u32 domid, u64 period, u64 slice, u64 latency, int xtratime) which takes 6 arguments >From tools/python/xen/xm/main.py: class ProgAtropos(Prog): <snip> def main(self, args): if len(args) != 5: self.err("%s: Invalid argument(s)" % args[0])

This patch unifys error messag of migrate and sysrq. Signed-off-by: Yoshinori Katase <y_katase@soft.fujitsu.com> Best Regards, Yoshinori Katase diff -r bfcdf4099d23 tools/python/xen/xm/migrate.py --- a/tools/python/xen/xm/migrate.py Thu Jan 12 13:27:55 2006 +++ b/tools/python/xen/xm/migrate.py Fri Jan 13 15:26:14 2006 @@ -56,8 +56,8 @@ if opts.vals.help: opts.usage()

Hi, I''ve tried to do "xm save" on my Windows XP guest, which runs by ioemu. When I did this, #xm save 6 /xenimages/snapshot1 Error: /usr/lib/xen/bin/xc_save 10 19 6 0 0 0 failed xend.log: [2006-10-06 16:34:22 xend] DEBUG (XendCheckpoint:80) [xc_save]: /usr/lib/xen/bin/xc_save 10 19 6 0 0 0 [2006-10-06 16:34:23 xend] ERROR (XendCheckpoint:227) Couldn''t map

Hello, I have 2 Dell 1955 blade servers, running RHEL5-Xen. I''m testing the migrate functionality from one blade to another. I can start the domain, move it to one blade (minor delay/packet loss) and everything is fine. When I try to move it back to the original blade the migration fails and the DomU crashes c1b1 = Blade 1 (192.168.131.201) c1b2 = Blade 2

Hi I have a setup where I have an eth2 10GB interface setup a loop back between two dell 1950 servers. I have enabled VT in the bios. The eth0 interface is on a 1GB network. I am using an iscsi shared drive for the HVM image. I have followed the instruction provided in http://www.osrg.net/kemari/usage.html Now once everything is setup: After launching the HVM, I execute the following

These xm info, top, dmesg and log requre no parameter. But log''s error message differs from other 3 command''s error messages, when parameter is given. # xm log 1 Error: ''xm log'' requires 0 argument. log Print the xend log Other 3 commands ignore parameter. I think it might be better symmetricalize. Signed-off-by: Yoshinori

I''m finding I cannot use the vif parameter with ''bridge'' only For example: vif=bridge=xen-br2 This errors out: [2005-09-30 14:23:55 xend] DEBUG (XendDomainInfo:1107) Creating vif dom=16 vif=0 mac=None [2005-09-30 14:23:55 xend] DEBUG (XendDomainInfo:665) Destroying vifs for domain 16 [2005-09-30 14:23:55 xend] DEBUG (XendDomainInfo:674) Destroying vbds for domain

hello, I ma using Xen 3.2.1 xm migrate --live make the guest crash as soon as it is mgrated xm migrate (without --live option) makes everything work flawlessy anyone has any hint for this problem ? thanks Rick _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users

I''m trying to do VM migration on XEN 3.0 and am getting the below mentioned error. Both the nodes have same OS installed. Both have AMD CPU''s. XM live migrate or XM migrate with VM powered off both ways I''m getting the error. /usr/lib64/xen/bin/xc_save 20 None 0 0 0 failed Any advice/suggestion on how to resolve this? Thanks Mihir

xen_changeset : Sun Apr 16 15:45:57 2006 +0100 9629:07408313ce33 /var/log/xend.log: [2006-04-19 20:42:09 xend] DEBUG (balloon:126) Balloon: free 1348; need 521; done. [2006-04-19 20:42:09 xend] DEBUG (XendCheckpoint:148) [xc_restore]: /usr/lib/xen/bin/xc_restore 11 20 42 133120 1 2 [2006-04-19 20:42:10 xend] ERROR (XendCheckpoint:227) xc_linux_restore start: max_pfn = 20800

Hello, i have two xen hosts servers configured to support migration of domus, but when i try to migrate, the command never ends, i can see on the remote server the machine with xm list but the machine is not accesible, and on the own server i see migrating-{machine_name} and i have access to it. Every server have one nic, with public ip (that is using with xenbr0), and i have a virbr0 configured

xend cannot start with error: ...ption starting xend: ''module'' object has no attribute ''VIRQ_DOM_EXC'' Traceback (most recent call last): File "/usr/lib/python2.3/xen/xend/server/SrvDaemon.py", line 304, in run self.createFactories() File "/usr/lib/python2.3/xen/xend/server/SrvDaemon.py", line 319, in createFactories

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

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