similar to: DomU pygrub issue - OSS Xen to XCP

Hello there, I have some issues regarding xend domU migration to XCP VM. I try to migrate my old xend domU''s to my xen Could using the xva.py script. All seems to work quite ok, the migration process doesn''t throw any errors, i get a .xva file with a proper Size. When importing that file, immidiately the VG and LV is created, and VM properties are assigned correctly. But when

Hullo Everybody ; I am failing to start my new VM and it tells me unkown bootloader . Below are my parameters and output . Could somebody be having an idea of putting right this problem? [root@virtualintranet /]# xe vm-param-list uuid=70645ba3-bcbc-683b-099e-ed197301fcc2 uuid ( RO) : 70645ba3-bcbc-683b-099e-ed197301fcc2 name-label ( RW): PVG1

Hi all, i still have problem.. Some time I am able to install and other not. I tried this on different machine either in a pool and either in a single installation of XCP. These are the steps I use to create a VM: # set disk size xe template-param-set uuid=9d8c3be5-f16b-7446-b978-e23551d8a77e other-config:disks="<provision><disk device=\"0\"

Hi Folks: I am having trouble creating a Fedora 14 domU on a XCP 1.0 dom0 hypervisor and am hoping that someone can help me figure out what I am doing wrong. Here is what I did (per the user''s guide and reference manual): ## Step 1. Create the VM: # uuid=$(xe vm-install template=''Other install media'' new-name-label=''test'') ## Note: I also tried

Hey, Is it possible to covert a .img to a xva? I have a virtual machine on a xen machine that i would like to run in a xen cloud. I used the xva.py and it gave me a xva + kernel i followed the copy instructions but i get this: [root@box ~]# xe vm-start vm=converted Error code: WARNING: /dev/xvda is not a disk image Error parameters: Traceback (most recent call last):, File

Hey, Is it possible to covert a .img to a xva? I have a virtual machine on a xen machine that i would like to run in a xen cloud. I used the xva.py and it gave me a xva + kernel i followed the copy instructions but i get this: [root@box ~]# xe vm-start vm=converted Error code: WARNING: /dev/xvda is not a disk image Error parameters: Traceback (most recent call last):, File

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

(Moving from offlist discussion.) I''m interested in opinions... Assume there are four single vcpu domains A, B, C, D, running on a 2-CPU physical machine. We wish to test for time skew on domain A. Assuming B, C, and D are all running some workload that attempts to fully saturate the (single) cpu. 1) Should the affect on domain A be essentially the same regardless of what load

Hi, I''ve installed XCP 0.5 and I''m following these steps: http://xenbits.xen.org/xapi/install.html to install ddk VM. But I can''t get network working. I tried to create a vif under xenbr0 then assigned mannually a IP address and to create a vif under xapi0. But in both cases I can ping only dom0 IP. What am I doing wrong? Thanks in advance. -- Sergio Roberto

Hello, I have installed XCP in Debian following the steps depicted in http://wiki.xen.org/wiki/XCP_toolstack_on_a_Debian-based_distribution . Out of the box, dom0 takes hold of all the available memory, so I cannot start any domU (I''m using XenCenter). If I try to limit the dom0 memory using kernel parameter dom0_mem, it is apparently ignored. Info: # cat /proc/cmdline placeholder

Hello, i have 3 XCP 1.0.0 hosts in a pool, one of them is not enabled: xe host-param-list uuid=402f07f4-99c0-4501-9787-8dee8984e313 uuid ( RO) : 402f07f4-99c0-4501-9787-8dee8984e313 name-label ( RW): xcp1.domain.com name-description ( RW): Default install of XenServer allowed-operations (SRO):

Fix for pygrub path on Solaris. Signed-off-by: John Levon <john.levon@sun.com> diff --git a/tools/python/xen/xend/XendDomainInfo.py b/tools/python/xen/xend/XendDomainInfo.py --- a/tools/python/xen/xend/XendDomainInfo.py +++ b/tools/python/xen/xend/XendDomainInfo.py @@ -37,7 +37,7 @@ from xen.util.blkif import blkdev_uname_ from xen.util.blkif import blkdev_uname_to_file from xen.util

Hello everyone. I have the following problem that could help would appreciate. 1) Environment: HOST 1: xen-hypervisor-3.2-1-amd64 with all VM in LVM disk. HOST 2: XCP 0.5 2) The VM that I wish migrate is a domU in XEN and is debian lenny over LVM: ................................................................................................... # Configuration file for the Xen instance

# HG changeset patch # User Zhigang Wang <zhigang.x.wang@oracle.com> # Date 1342720736 14400 # Node ID ec9655b30a5fa5b5abb3e05505f681f9be559613 # Parent 43e21ce7f22151524b800a6cf0ac4ba1233b34a7 pygrub: add syslog support to pygrub Currently, when pygrub failed, we don''t know the reason because xend/xl will not capture the stderr message. This patch will log the error message to

Hello, I must be missing something very very basic. Because I am having trouble launching some vm''s that I recently built whereas I don''t have any problem at all launching some older images I made in very much the same way! First there is vm01 which works just fine: [root@lcent5-1:/etc/xen]$:xm create vm01 Using config file "./vm01". Started domain vm01

Hello, I must be missing something very very basic. Because I am having trouble launching some vm''s that I recently built whereas I don''t have any problem at all launching some older images I made in very much the same way! First there is vm01 which works just fine: [root@lcent5-1:/etc/xen]$:xm create vm01 Using config file "./vm01". Started domain vm01

So i successfully upgraded my Debian vm''s to Debian 6 on XCP 1.0, but when i try to install a new clean one it always fails. Why is this? The VM won''t even start, while i used the Debian 6 squeeze template. Is this even possible? Thanks, Peter _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com

I recently updated the kernel on an Ubuntu 11.04 PVM domU. The dom0 is an up to date Debian Squeeze host (Xen 4.0.1). Attempting to start the domU after this with xm create gives "Error: Boot loader didn''t return any data!". I ran pygrub against the domU manually, I got the following: Traceback (most recent call last): File "/usr/lib/xen-default/bin/pygrub", line

Running a heavily modified xen-unstable changset 19590:f80cf52a4fb6 with debugger_attached set, I was seeing the debug traps getting lost from the EXCEPTION_BITMAP in vmx_update_guest_cr() when transitioning from real to protected mode. In my codebase, I could fix this trivially by clearing the debug_state_latch and letting vmx_do_resume() reapply the setting. However, while it looks like a valid

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