similar to: [PATCH] Fix error message of xm suspend for Domain-0

This patch fixes IO deadlocks in the vtpm hotplug scripts. Signed off by: Matthew Fioravante matthew.fioravante@jhuapl.edu --- Changed since previous: * rebased off of latest xen stable * replaced instances of gawk with awk diff --git a/tools/hotplug/Linux/vtpm b/tools/hotplug/Linux/vtpm --- a/tools/hotplug/Linux/vtpm +++ b/tools/hotplug/Linux/vtpm @@ -1,22 +1,18 @@ #!/bin/bash +export

Implements tool interfaces for scheduling domains. libxenctrl, xm, and xend. signed-off-by: Mike D. Day <ncmike@us.ibm.com> -- libxc/xc_domain.c | 85 +++++++++++++++++++++++++++++++++--- libxc/xenctrl.h | 43 ++++++++++++++++-- python/xen/xend/XendDomain.py | 78 +++++++++++++++++++++++++++++++++ python/xen/xend/server/SrvDomain.py |

Hi, I found two setResume()s in XendDomainInfo.py. One or the other is not necessary, is it? # grep -n -A 2 setResume ./tools/python/xen/xend/XendDomainInfo.py 1394: def setResume(self, isresume): 1395- self._resume = isresume 1396- -- 1409: def setResume(self, state): 1410- self._resume = state 1411- Signed-off-by: Masaki Kanno <kanno.masaki@jp.fujitsu.com> Best

Recent xen uses xenbus to suspend PV-on-HVM guest domain. The related code in the xen-unstable tree will fall into infinite loop when guest domain failed on suspending one or more devices. The patch attached changes the logic, and raises an XendError after 1 minute waiting. The patch also makes use of "control/shutdown" entry in xenstore, allows guest kernel report the failure of the

Hi all, when i try to create a new virtual machine in a new instalation of xen3.4 ( compiled from source) i get this error: xm create windows2.hvm Using config file "./windows2.hvm". Error: Domain ''y'' does not exist. And this is the log: [2009-06-25 17:59:42 13862] TRACE (XendDomainInfo:291) domain_getinfo(2) failed, ignoring: (3, ''No such process'')

Hi Keir, The CS# 17131 which I write for bind guest to NUMA node via cpu affinity missed one condition existing in some machines, where there aren''t any cpus but only memories. Under this condition it will fail to set cpu_affinity because of none parameter. I cope with this condition in the new patch and make a little change of the methods to find suitable node to bind guest. When

Hi, on ia64, the do_* functions for hypercalls are called in C. However, they are not declared in any .h file. I think it is cleaner to declare them in an header file rather than locally. The question is in which header file. Thank you for any suggestion. The do_* functions are at least: extern long do_ni_hypercall(void); extern long do_dom0_op(dom0_op_t *u_dom0_op); extern long

Hi, This patch fixes the Bug:835 issue. # xm create /home/kanno/smp-domU.conf cpu_weight=512 cpu_cap=150 Using config file "/home/kanno/smp-domU.conf". Started domain vm1-smp # xm sched-credit -d vm1-smp {''cap'': 150, ''weight'': 512} Signed-off-by: Masaki Kanno <kanno.masaki@jp.fujitsu.com> Best regards, Kan

Hi, I tested unlikely operations about the xm reboot/shutdown command. As a result, I found the following problems. Problem 1: Can reboot/shutdown Domain-0 by mistake. # xm list Name ID Mem(MiB) VCPUs State Time(s) Domain-0 0 1024 2 r----- 31.0 # xm reboot 0 Error: Can''t specify Domain-0 # xm reboot 00 #

Hi, When I tested xm vcpu-pin command, I encountered the following strange problem. I encountered it on x86, but I didn''t encounter it on ia64. On x86: # xm vcpu-list Name ID VCPU CPU State Time(s) CPU Affinity Domain-0 0 0 0 -b- 31.3 any cpu Domain-0 0 1 1 r--

Hi, When I tested xm create command, I saw the following error message. I expected an error message "Error: (12, ''Cannot allocate memory'')" because I intentionally caused a memory shortage on the test. But the error message was different from my expectation. # xm create /xen/HVMdomain.1 Using config file "/xen/HVMdomain.1". Error: an integer is required

Hi, This patch adds more user registers to show them to xenctx for ia64. Tested domU/domVTi on ia64. Sample is the below. # ./xenctx 1 0 iip: e000000000000810 ipsr: 00001012087a6010 b0: a000000100068a70 b6: a00000010014ff60 b7: e000000000000800 cr_ifs: 800000000000050a ar_unat:

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

Hi, When I tried xm trigger command to a inactive managed domain, I saw the following error message. # xm list vm1 Name ID Mem VCPUs State Time(s) vm1 256 2 0.0 # xm trigger vm1 init Error: an integer is required Usage: xm trigger <Domain> <nmi|reset|init> [<VCPU>]

Hi, I found minor bugs in xm restore command. 1) When I gave a wrong check point file, a return code of command was 0. # touch /tmp/dummy # xm restore /tmp/dummy Error: not a valid guest state file: signature read # echo $? 0 2) When Xend had been stopping, I saw the following traceback message. # xend stop # xm restore /xen/save.vm1 Unexpected error: exceptions.AttributeError Please

Hi, As for xm create and xm new, an error may not occur even if wrong vscsi configuration is given. e.g. vscsi = [ ''0:0:0:0,0:0:0:0'', ''0:0:0:0,1:0:0:0'' ] # xm create vm1 Using config file "/etc/xen/vm1". Started domain vm1 (id=8) # xm scsi-list vm1 Idx BE state host phy-hctl phy vir-hctl devstate 0 0 1 0 0:0:0:0

Hi, We can give multiple domains to the following commands. But, the help messages of the commands are explained to be able to give a single domain. # xm vcpu-list vm1 vm2 Name ID VCPU CPU State Time(s) CPU Affinity vm1 1 0 0 r-- 1409.3 any cpu vm2 2 0 0 r-- 1255.8

Hi, When I tested the xentop with a wrong option, the xentop returned the return code 0. # xentop --abc xentop: unrecognized option `--abc'' Usage: xentop [OPTION] Displays ongoing information about xen vm resources <snip> # echo $? 0 If the wrong option was specified, I think that the xentop had better return the return code 1 (or not 0). This patch fixes the return code of

Hi, I believe that a value of "result[''status'']" is an integer, isn''t a character string. diff -r 8d41996e6897 tools/python/xen/xend/server/DevController.py --- a/tools/python/xen/xend/server/DevController.py Mon Oct 27 18:51:52 2008 +0000 +++ b/tools/python/xen/xend/server/DevController.py Tue Oct 28 09:14:53 2008 +0900 @@ -542,7 +542,7 @@ class

Hi, The xm vcpu-set command is able to set zero to the number of VCPU of a domain. Therefore I think that it is a natural result that the xm start command fails. But I think that a xm vcpu-set command must fail usually. # xm list Name ID Mem VCPUs State Time(s) Domain-0 0 942 2 r----- 75.2 vm1