similar to: RE: [Xen-ia64-devel] New error trying to create a domain(usinglatestxend-unstable

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

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

Hi, We cannot get correct records of VDI by VDI.get_record. The correct records of VDI are gotten by this patch. Signed-off-by: Masaki Kanno <kanno.masaki@jp.fujitsu.com> Best regards, Kan _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

Hi, I tried to test a wrong operation on purpose again. When I tried xm sysrq command to a inactive managed domain, I saw the following error message. The error message did not have a message text behind "Error:". And I found an AssertionError message in xend.log. # xm list PVdomain.1 Name ID Mem VCPUs State Time(s) PVdomain.1

Hi, I found the following problems. xm pci-attach command and xm pci-detach command fail on inactive managed domains. An attaching patch solves the problems. # xm list Name ID Mem VCPUs State Time(s) Domain-0 0 1024 2 r----- 51.5 vm1 512 2

Hi, These patches enhance XenAPI for pvSCSI. Basically, I implemented XenAPI for pvSCSI according to the patch of XenAPI document which I sent before. However, I renamed the class name of virtual SCSI devices to "DSCSI". As for the patch of XenAPI document, I''m going to send it next week. Signed-off-by: Masaki Kanno <kanno.masaki@jp.fujitsu.com> Best regards,

Hi, I tested xm block-attach command with a wrong parameter(file:). Naturally a command error occurred. Then I retested xm block-attach command with a correct parameter(phy:). But a command error occurred again. The second command error occurred because Xend did not remove device information from self.info when the first command error occurred. # xm block-attach vm1 file:/dev/hda4 hdb1 w

Hi, I fixed the Xen bugzilla 936. http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=936 Currently, "cpus" output to config.sxp is the following form. Therefore _parse_sxp() cannot convert ''[1'' to integer. e.g. (cpus ''[1, 2]'') --- string This patch changes output form of "cpus". The form is as follows. e.g. (cpus (1 2))

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