similar to: Driver domains communication protocol proposal

Hi, I''ve been touring XCP and making my way around it for the last few days, and am having problems with some reasonably straightforward actions. I''ve poured a several hours into different ways of resolving the issue, but am coming up short. Here''s the main issue. The following command (plugging in a VBD to the dom0 VM), when, run, hangs for several minutes, and then

Package: xcp-xapi Version: 1.3.2-6 Severity: normal Tags: upstream Normally (in 'iso-based' XCP) is possible to attach VDI to dom0. That operation usually looks like: xe vbd-create vdi-uuid=... vm-uuid=(dom0 uuid) device=N xe vbd-plug I done those steps in xcp-xapi and got success (no error), but no xvd* device found. Here operations log: # xe vbd-create

Package: xcp-xapi Version: 1.3.2-6 Severity: normal Tags: upstream /usr/lib/xcp/bin/xe-edit-bootloader failing with following message: /usr/lib/xcp/bin/xe-edit-bootloader -u 19f66083-e776-70d1-1808-3712688ad138 Creating dom0 VBD: 0fdb952e-92ff-4b53-dd49-8d54b2268787 Plugging VBD: Waiting for /dev/sm/backend/4c15ea03-5d70-938e-8265-d5424c0fda5e/963afb9a-9ceb-410f-8554-8be9fb70e7e0: . done

Package: xcp-xapi Version: 1.3.2-6 Severity: normal Tags: upstream vbd plug to PV domain cause following error: The server failed to handle your request, due to an internal error. The given message may give details useful for debugging the problem. message: the device disappeared from xenstore (frontend (domid=4 | kind=vbd | devid=51760); backend (domid=0 | kind=vbd | devid=51760)) (same error

How do I resolve this issue? Please help me. ################################################ [root@xenhost2 ~]# xe vm-list uuid=0a0efde9-a92f-3619-478c-64edd8b0adf8 uuid ( RO) : 0a0efde9-a92f-3619-478c-64edd8b0adf8 name-label ( RW): rhel52 power-state ( RO): halted ################################################ [root@xenhost2 ~]# xe vm-start

I am running Xen 3.3.0 and am trying to run a XenEnterprise image. The image has a hda directory with files called chunk-000000000.gz - chunk-000000042.gz and a filed called ova.xml with the following: <appliance version="0.1"> <vm name="VM"> <label> Manager </label> <shortdesc> </shortdesc> <config

I've had another attempt at installing Wheezy 64 bit from a template as PV. I attach my full script below. I've made much more progress this time, but there are still outstanding issues: - neither "xe console" or VNC seems to allow ALT-F[2-6] keystrokes, so I can't get other virtual terminals and therefore can't obtain any useful log/status messages. This issue alone

Title: HOWTO-FreeBSD-on-XCP Author: John D. "Trix" Farrar Date: 2012-02-09 * The Challenge - ParaVirtualized FreeBSD 9.0-RELEASE under XCP 1.1.0 The idea here is to create a PV FreeBSD VM under Xen Cloud Platform (XCP) without starting with an HVM first. The documentation I''''ve been able to find on-line is at least a year old and is mostly written for Xen (under

Package: xen-utils-common Version: 4.4.0-5 Severity: important Tags: patch Hello, xen-init-list fails to parse output of xen list -l when using XM toolstack. Therefore, /etc/init.d/xendomains stop fails to shutdown any guests still running on shutdown. xen-init-list fails with the following message: /usr/lib/xen-common/bin/xen-init-list Traceback (most recent call last): File

----- Forwarded message from Keir Fraser <keir at xen.org> ----- From: Keir Fraser <keir at xen.org> To: xen-devel at lists.xen.org Date: Mon, 17 Sep 2012 12:34:00 +0100 Subject: [Xen-devel] [ANNOUNCE] Xen 4.2 released! The Xen team is pleased to announce the release of Xen 4.2. The result of *18 months* of development, new features include: * Paging/sharing improvements for

I am now testing XEN live migration on two physical hosts with XEN 4.0.1 pvops Ubuntu 10.10 (2.6.35-22). Host A also acts as a NFS server, and Host B acts as a NFS client. When I migrate a guest domain from B to A. The ssh connection experiences a downtime of about 1 minute (the terminal does not react to the keyboard input till about 1 minute later). However, the "sudo xm console" does

Hello I am trying to boot/install VM on XenClient. I would like to learn the way to install VM. Please teach the example of the operation and config file. (Especially, configuration file of method of displaying screen.) thanks. ========================================= [My Executed History] (1) I made a config file for VM(Windows XP:below). (2) I executed the following commands. # xenvm

This fixes the xapi test case 02 with those parts that currently do not work disabled with ''if 0:'' Signed-off-by: Stefan Berger <stefanb@us.ibm.com> Index: root/xen-unstable.hg/tools/xm-test/tests/xapi/02_xapi-vbd_basic.py =================================================================== --- root.orig/xen-unstable.hg/tools/xm-test/tests/xapi/02_xapi-vbd_basic.py +++

This logfile was recorded while the vm-start was running. -------------- next part -------------- [20120727T14:43:34.919Z| info|vh10|1021 UNIX /var/lib/xcp/xapi|session.logout D:dd291648d150|xapi] Session.destroy trackid=e3179eeb95ba96c64ab771d0cb1557b6 [20120727T14:44:02.180Z|debug|vh10|25|Starting periodic scheduler D:641021a392d0|backgroundscheduler] Adding function Logrotate to queue,

Jason, I found that I had to manually edit the VM config file to add the cdrom in the Disk section. For example I added: Disk = [ "file:/location/disk.img,had,w" , "file:/location/en_ws_2003_ent_sp2_vl.is,hdb:cdrom,r"] Where /location is the directory you have the ISO image stored. It then is able to boot and mount the CD-ROM on the 2nd boot. Good luck, -Peter Subject:

Hullo Everybody I have taken the steps below and I failed to get a device similar to /dev/xvda in DOM 0 where am I getting it wrong Create VDI, *[root@virtualintranet /]# xe vdi-create sm-config:type=raw sr-uuid=b303be09-6a32-8d94-d248-7551860fbc3f name-label="Centos-Vdi" virtual-size=20GiB type=user* eefa9066-a991-44c3-b537-d20d65f3d10c create VBD *[root@virtualintranet /]# xe

...because vbd_size() dereferences bd_disk if bd_part is NULL. Signed-off-by: Laszlo Ersek<lersek@redhat.com> --- drivers/xen/blkback/vbd.c | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff -r 415a9b435fef drivers/xen/blkback/vbd.c --- a/drivers/xen/blkback/vbd.c Mon May 23 18:36:33 2011 +0100 +++ b/drivers/xen/blkback/vbd.c Wed May 25 12:15:26 2011 +0200 @@ -73,7 +73,6 @@

What are the outstanding things to do before we think we can start on the 4.2 -rc''s? Does anyone have a timetable in mind? hypervisor: * ??? - Keir, Tim, Jan? tools: * libxl stable API -- we would like 4.2 to define a stable API which downstream''s can start to rely on not changing. Aspects of this are: * event handling (IanJ working

Hello, I noticed a bug in Xen-4.1-3, which is also still present in xen+git. I know that the Python xend is deprecated, but I''m stuck with xen-4.1 until xen is usable with libvirt, so my patch might still be helpful for others. This is a follow-up to <http://lists.xen.org/archives/html/xen-users/2012-11/msg00069.html>, which still keeps me busy. /xen/xend/server/SrvDomain.py

Hi, i have just install debian wheezy and xen-hypervisor-4.1-amd64 helped with http://wiki.debian.org/Xen http://wiki.xenproject.org/wiki/Xen_Beginners_Guide#Installing_Debian_Squeeze created test.cfg http://pastebin.com/D5Wsx6eB xl create test.conf Parsing config file test.conf xc: info: VIRTUAL MEMORY ARRANGEMENT: Loader: 0000000000100000->0000000000174170 TOTAL: