similar to: Question about ACMError

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

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 new command without uuid parameter repeatedly, I saw many same managed domain as follows. # xm list Name ID Mem VCPUs State Time(s) Domain-0 0 941 2 r----- 51.9 # xm new /xen/vm1.conf Using config file "/xen/vm1.conf". # xm new /xen/vm1.conf Using config file

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

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:

On Feb 24, 2011, at 11:52 AM, Devang Patel wrote: > > On Feb 24, 2011, at 11:36 AM, Devang Patel wrote: > >> >> On Feb 12, 2011, at 2:07 AM, Nathan Jeffords wrote: >> >>> Hello All, >>> >>> I have created a set of patches that get dwarf debugging support working for the COFF object file. I also believe I have fixed what appears to be a

destroy() is being called on exception in both start() and create(). It needs to be called only in create(). Signed-off-by: Aravindh Puthiyaparambil <aravindh.puthiyaparambil@unisys.com> _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

Hi, An APIC error continues happening. __ __ _ _ _ _ _ _ \ \/ /___ _ __ | || | / | _ _ _ __ ___| |_ __ _| |__ | | ___ \ // _ \ ''_ \ | || |_ | |__| | | | ''_ \/ __| __/ _` | ''_ \| |/ _ \ / \ __/ | | | |__ _|| |__| |_| | | | \__ \ || (_| | |_) | | __/ /_/\_\___|_| |_| |_|(_)_| \__,_|_|

Xend will do a hypercall to destory domain when creating VTI guest fail. If "is_vti" not be set at this point, HV will call relinquish_vcpu_resource() which belong to domU. It may try to free a NULL pointer, so dom0 crash. This patch fix it. Signed-off-by, Zhang Xin < xing.z.zhang@intel.com > Good good study,day day up ! ^_^ -Wing(zhang xin) OTC,Intel Corporation

This patch fixes return codes for the acm-related Xen management scripts (error conditions) and addresses minor issues that ''pycheck'' complains about. It is tested with xm-test and by manually running the xm commands. It also handles the return case (reported by Masaki Kanno) that was missed in the originally patch. Signed-off by: Reiner Sailer <sailer@us.ibm.com>

On Feb 24, 2011, at 11:36 AM, Devang Patel wrote: > > On Feb 12, 2011, at 2:07 AM, Nathan Jeffords wrote: > >> Hello All, >> >> I have created a set of patches that get dwarf debugging support working for the COFF object file. I also believe I have fixed what appears to be a bug in how line info sections are referred to from the DW_TAG_compile_unit DIE. I have run

I am using a CentOS 5.2 x86_64 machine and compiled Xen 3.3.0. Everything seemed to build and install okay. After rebooting to the new of Xen, when I try to create a new domU, I get an error message saying "ACMError: Policy file ''/etc/xen/acm-security/policies/-security_policy.xml'' not found." I tried to find some documentation on what this is but I coming up with

I have a UIP200 on the way for eval. Does anyone have tips or tricks to get it working right away with * ? I hate having to go through the pain someone else braver than I went through already. :) Tim --

Folks, It seems like the * v 0.9 and iaxcomm won't speak to each other. Is there another IAX2 client that is usable under Linux (Debian preferred)? Thanks, Tim --

It would be a real kick to get one of these to run Asterisk. :) http://www.gumstix.com/ Tim -- >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>><<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<< >>

What is the best inexpensive voip phone out there? I want to try a few with *, but don't want to go broke while I'm just playing around... Tim --

I have a system that has a TDM400 with 3 FXO modules. Recently, the system started not seeing the ports. No answer, no lines available for oubound dial, and only a reboot of the machine will bring it back. Any ideas to try? Thanks, Tim --

Hi, I am extending LLVM for HPC applications. As one of them, I am trying to make MachinePipeliner available on AArch64 + Scalable Vector Extension environment. MachinePipeliner is currently used only by Hexagon CPU. Since it is a very portable implementation, I think that it will actually work just by adding a little code for many CPUs(See Code [2]). The current MachinePipeliner is written on