similar to: virtman breaks after installing XEN 3.1 on SELS 10.1

Hello i'm setting up a debian system, with no root acount, i manage it with the sudo command, and installed the new xen 3.3.0 on it than i installed fluxbox and vnc4server on this machine, to get remote access to the debian/xen system i use ssh and xvnc4viewer, ssh for the console and xvnc4viewer for the windowmanager, until than everything works fine. than i installed virt-manager from the

Waay back at the end of 3.0.3 dev cycle I brought up the issue of XenD running far too many xenstore transactions per-request http://lists.xensource.com/archives/html/xen-devel/2006-10/msg00487.html Short summary: # nc -U /var/lib/xend/xend-socket GET /xend/domain/test Resulted in approx 16 xenstore transactions for a domain with one disk and one NIC - this increases as # of devices

Hi, I am trying to install Xen 3.1.3 from the source code. The machine on which I would like to install it doesn''t have access to the Internet. So I did a "make world" on a different machine, copied the files to where I actually wanted to install Xen and then re-built and installed it. However, when I boot into the new kernel and try to execute "xm" or

I can't get xen live migration to work - CentOS 5.6. I have set up xend-config.sxp as per RHEL5 virtualization guide, but when I try it, I get [root at xenhost1 ]# xm migrate testwww xenhost2 -l Error: (104, 'Connection reset by peer') Usage: xm migrate <Domain> <Host> Migrate a domain to another machine. Options: -h, --help Print this help. -l, --live

Package: xen-utils-3.2-1 Severity: important Hello! When using xenapi.PBD.create() the following error occurs: xen.xm.XenAPI.Failure: Internal error: global name 'genuuid' is not defined. (Attached you can find the logging of the remote host.) This (and other syntax errors) are already fixed in the xen-unstable.hg (see http://xenbits.xensource.com/xen-unstable.hg?rev/7fd49c55c0b0).

Package: xen-hypervisor-3.4-i386 Version: 3.4.3~rc3-2 Severity: important Tags: sid After booting into the xen kernel, xm cannot run because xend is not running (the sysfs hypervisor is not populated) # dpkg -l | grep xen ii libc6-xen 2.10.2-6 GNU C Library: Shared libraries [Xen version] ii libxenstore3.0

QUESTION: What, if anything, can I do so that I can use xl (in place of xm) with libvirt 1.0.2 and Xen 4.2.1 in Ubuntu 13.04? BACKGROUND: I am testing a fully updated (as of March 27) installation of Ubuntu 13.04 that includes the following packages: libvirt - version 1.0.2-0ubuntu9 xen-hypervisor-4.2-amd64 - version 4.2.1-0ubuntu1 Upon setting TOOLSTACK=xm in /etc/default/xen (as well as

Hello all: My Environment: Ubuntu6.06 + Xen3.0.4 My XenLinux was booted successfully. But when i starting the "xend" service, errors displayed. I searched in google, but could not get an available solution. Please help me! Thank you very much! Error log: ----------------------------------------------------------------------------------------------- root@zwang-desktop:~#

Currently with the credit scheduler, cpu_weight cannot be assigned to guest domains at boot time.(it can be set with xm sched-weight after booting) This patch allows CPU weight, and CAP to be set by the Xen configuration files. Specification: The following can be added to the Xen configuration files. 1.CPU WEIGHT [OPTIONAL] cpu_weight = cpu weight value -sets the cpu time ratio to be

Hello, I posted this yesterday to the Xen-devel list, posting it additionally to the fedoraproject list too. My problem is Virt-manager is unable to connect to the hypervisor (explained below). However, xm list, xm info work fine. So I followed the guide http://wiki.xen.org/wiki/Xen_4.2_Build_From_Source_On_RHEL_CentOS_Fedora and built/installed Xen from source, using grub2-mkconfig to rebuild

Hello: I just gave 3 tries at compiling a xen kernel. I managed to get the networking in the host to work ok on the third try, unfortuately xend gives me the following errors in my xend.log and will not start. Any ideas? It fails to start with the following error ---------------------------------------------------- /usr/sbin/xend [root@localhost ~]# /usr/sbin/xend start Traceback (most recent

Hi, I downloaded XEN 3.1 source code on a fedora 6 machine. I did # make world # make install It did not give me an error then when I restarted the machine the Grub did not have 2 options. It had only one option that was the kernel. On loading the OS, when i gave # xend it gives the following errors: [root@localhost sbin]# xend ERROR Internal error: Could not obtain handle on privileged command

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

Package: xen-utils-3.0.3-1 Version: 3.0.3-0-4 Severity: important # /etc/init.d/xend start Restarting XEN control daemon: xendTraceback (most recent call last): File "/usr/lib/xen-3.0.3-1/bin/xend", line 40, in <module> from xen.xend.server import SrvDaemon File "/usr/lib/xen-3.0.3-1/lib/python/xen/xend/server/SrvDaemon.py", line 17, in <module> import

Hi. I have xen xen-3.0.4_1 If tls in not disabled I am getting the following: ***************************************************************   ***************************************************************   ** WARNING: Currently emulating unsupported memory accesses  **   **          in /lib/tls glibc libraries. The emulation is    **   **          slow. To ensure full performance you

When a domain is in the process of shutting down there is a small window when the domain is known to XenD, but it will be unable to form an SXPR for it due it being in the middle of device hot-unplug. This causes the ''xm list'' command to totally fail with an error like # xm list Error: Device 0 not connected Usage: xm list [options] [Domain, ...] List information about all/some

Hi there I get the same error, only /usr/lib/python/xen/lowlevel/xu.so does -not- exist I see a dir named /usr/lib/python/site-packages/xen/lowlevel with just one file in it: __init__.pyc even if I do a find -name xu.* from / I get nothing I run Suse 9.3 and kernel 2.6.8-24.14, which seems to be the only way to get Dom0 up under Suse 9.3 for the time being Hints most welcome! Chris

When I start xen in the dom 0 , it''s display me these errors: [root@datacenter root]# xend start /usr/lib/python/xen/xend/server/SrvDaemon.py:28: RuntimeWarning: Python C API version mismatch for module xen.lowlevel.xu: This Python has API version 1011, module xen.lowlevel.xu has version 1012. from xen.lowlevel import xu Traceback (most recent call last): File

This patch adds new control messages for vcpu hotplug events. Via the xm vcpu_hotplug sub-program, VCPUS in domains can be enabled/disabled when CONFIG_HOTPLUG_CPU is enabled in the target domain''s kernel. Currently there is nothing that tracks whether a VCPU is up or down. My previous [1]patch added a new per-VCPU flag (VCPUF_down) which could be used to keep track of which VCPUS are

Hi, I am using XEN-4.1.2 and linux-2.6.32 as dom0. After I upgraded stackless python from 2.5 to 2.7 (and rebuilt xen). XenAPI became unusable, I spent some time to investigate XenAPI,py, it looks fine. So, I guess xend has problem with python 2.7, because it always returned method unknown. Do I have to tweak xend to let it support python 2.7? Thanks, Eric /root # python Python 2.7.5 Stackless