similar to: [RESEND][BUGFIX][ACM] fix return code in acm-related xm scripts

This patch fixes an indentation error in main.py. The effect of this bug is that block-attach does not check labels if the ACM is active. This bug slipped in with change set 11572_:_ ad22c711ccb7 <http://xenbits.xensource.com/xen-unstable.hg?cs=ad22c711ccb7>. This patch is essential and should get into 3.0.3. I tested the patch with security off and on. Thanks Reiner P.S. We are

Updates xensec_ezpolicy ACM policy generation tool so that it works with wxPython under Python 2.5 as well. Thanks Reiner Signed-off by: Reiner Sailer <sailer@us.ibm.com> _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

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

Same functionality as the previous patches in this series. I have updated the error handling to correct the problems discovered by Ewan. This patch successfully completes the xm-test suite on my dev machine. In addition, we have tested out the affected commands by hand to ensure that error handling is being done properly. Hopefully this one will not create any more problems.

This patch adds a policy name to the policy definition. This policy name must be unique and must change if the content of the file changes. The policy name is used to ensure that the XM tools and the hypervisor work on the same policy, i.e., interpret the security information on domains consistently. This patch also simplifies the policy management by moving policy and labels into a single

This patch adds an ACM hook into the network scripts (/etc/xen/scripts). It adds iptables rules that enforce mandatory access control on network packets exchanged between virtual interfaces. If ACM is active, this patch sets the default FORWARD policy in Dom0 to DROP and adds iptables ACCEPT rules between vifs that belong to domains that are permitted to share (determined by using the

This patch: * adds a C-based security policy translation tool to Xen (secpol_xml2bin) and removes the current Java security policy translator (Java dependencies). The C-based tool integrates into the Xen source tree build and install (using gnome libxml2 for XML parsing). See install.txt. * introduces security labels and related tools. Users can now use semantic-rich label names to put

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 all, Could you teach me about the behavior of xm commands when ''ACMError'' occurred? I am testing the behavior of xm commands with wrong arguments. When I tested xm commands related to security (xm *label/*policy), I found that some of them. - return 0, - show ACMError''s Traceback messages. Are these results specifications or bugs? Example: # xm cfgbootpolicy

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, 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, 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, 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, This patch fixes a error message of xm suspend command for Domain-0. Signed-off-by: Masaki Kanno <kanno.masaki@jp.fujitsu.com> Best regards, Kan diff -r 2a8eaba24bf0 tools/python/xen/xend/XendDomain.py --- a/tools/python/xen/xend/XendDomain.py Tue Feb 26 15:11:51 2008 +0000 +++ b/tools/python/xen/xend/XendDomain.py Thu Feb 28 14:23:39 2008 +0900 @@ -865,7 +865,7 @@

Hi, When I tested the xm pause/unpause command, I found poor error messages. The following is the error messages. # xm list Name ID Mem(MiB) VCPUs State Time(s) Domain-0 0 492 1 r----- 394.6 vm1 1 512 1 r----- 3.0 # xm pause 0 Error: (22, ''Invalid argument'') # xm pause

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