search for: setvcpucontext

Hi guys, I cannot get my domU''s to boot. My current setup is as follows: Xen: 4.0.1 Dom0: Debian with custom linux 2.6.32.27 Xen kernel DomU: Same kernel as Dom0 When I try to start the VM, I just get: Error: (1, ''Internal error'', ''launch_vm: SETVCPUCONTEXT failed (rc=-1)\n'') And /var/log/xend.log says: [2011-01-23 15:36:01 3201] DEBUG (XendDomainInfo:101) > XendDomainInfo.create([''vm'', [''name'', ''testVM''], [''memory'', ''128''], > [''on_powe...

Hi guys, I cannot get my domU''s to boot. My current setup is as follows: Xen: 4.0.1 Dom0: Debian with custom linux 2.6.32.27 Xen kernel DomU: Same kernel as Dom0 When I try to start the VM, I just get: Error: (1, ''Internal error'', ''launch_vm: SETVCPUCONTEXT failed (rc=-1)\n'') And /var/log/xend.log says: [2011-01-23 15:36:01 3201] DEBUG (XendDomainInfo:101) > XendDomainInfo.create([''vm'', [''name'', ''testVM''], [''memory'', ''128''], > [''on_powe...

Last year we had a discussion[1] about how the hypercall ABI unfortunately contains fields that change width between 32- and 64-bit builds. This is a huge problem as we come up on the python management stack for ppc64, since the distributions ship 32-bit python. A 32-bit python/libxc cannot currently manage a 64-bit hypervisor. I had a patch but was unable to test it, and some other things were

...e (a small hosting community) are running a steadily growing number of Xen domUs on a quad dualcore Xeon server with 64GB ram. We''ve got 100 running domUs at the moment. Trying to create a new one results in this error: Error: (1, ''Internal error'', ''launch_vm: SETVCPUCONTEXT failed (rc=-1)\n'') If I shut down another domain, I can create one again, but the limit seems to be 100 domUs. Each domU has one network interface and one or two disk devices (raid-1 md device consisting of two iscsi luns). Version of Xen is rather old: 3.2.1-amd64 (Debian). Can anyon...

...ID Mem VCPUs State Time(s) Domain-0 0 942 2 r----- 76.2 vm1 256 0 0.0 # xm start vm1 Error: (1, ''Internal error'', ''launch_vm: SETVCPUCONTEXT failed (rc=-1)\n'') Usage: xm start <DomainName> Start a Xend managed domain -p, --paused Do not unpause domain after starting it This patch checks the number of VCPU given by the xm vcpu-set command. # xm list Name ID...

...ity", + (Addr)domctl->u.vcpuaffinity.cpumap.bitmap.p, + domctl->u.vcpuaffinity.cpumap.nr_cpus / 8); + break; + + case XEN_DOMCTL_getvcpucontext: + __PRE_XEN_DOMCTL_READ(getvcpucontext, vcpucontext, vcpu); + break; + + case XEN_DOMCTL_setvcpucontext: + __PRE_XEN_DOMCTL_READ(setvcpucontext, vcpucontext, vcpu); + __PRE_XEN_DOMCTL_READ(setvcpucontext, vcpucontext, ctxt.p); + break; + + case XEN_DOMCTL_set_cpuid: + PRE_MEM_READ("XEN_DOMCTL_set_cpuid", + (Addr)&domctl->u.cpuid, sizeof(domctl-...

These patches update the example FLASK policy shipped with Xen and enable its build if the required tools are present. The third patch requires rerunning autoconf to update tools/configure. [PATCH 1/3] flask/policy: sort dom0 accesses [PATCH 2/3] flask/policy: rework policy build system [PATCH 3/3] tools/flask: add FLASK policy to build

This patch series is a reworking of a series developed by Mukesh Rathor at Oracle. The entirety of the design and development was done by him; I have only reworked, reorganized, and simplified things in a way that I think makes more sense. The vast majority of the credit for this effort therefore goes to him. This version is labelled v13 because it is based on his most recent series, v11.