similar to: Bug#644100: pygrub error if the root disk value is not the first in the list.

Package: xen-utils-4.0 Version: 4.0.1-2 If you reboot with the DomU disk DRBD domain destroy. pygrub error when trying to run a image on DRBD device My config DomU ------------------------------------------------------ bootloader = '/usr/lib/xen-default/bin/pygrub' vcpus = '1' memory = '256' cpus="8-15" root = '/dev/xvda2 ro' #disk

Hi all, after upgrading from xen 3.0 to xen 3.2 I cannot start my domUs: I get: VmError: Boot loader didn''t return any data! Suggestions? This is the log [2008-06-25 11:24:53 2755] DEBUG (XendDomainInfo:84) XendDomainInfo.create([''vm'', [''name'', ''engtest3.infolan''], [''memory'', ''2048''],

Hi I have configured few VMs with RHEL5,32 bit, but some VMs after successful stop/restart few times, suddenly they start giving following error from "xm create vm1.cfg" startup. ---- Error: (''c618d493-a696-7637-333d-bd891fa41ac2'', ''VM_metrics'') ---- If i replace system.img, they starts working again. This is what i see in xend.log file. This happens

Hardware: 2x Intel Xeon Quad-Core 2.33GHz 24GB FBDIMM RAM 2x 2TB HDD in RAID-1 Intel Server Board S5400SF Setup: Arch Linux x86_64 Xen 4.1.2 Grub2 Multiboot Synopsis: I set up a new VM for Debian Squeeze following instructions here: http://www.howtoforge.com/installing-debian-squeeze-6.0-domu-on-centos-5.5-x86_64-dom0. Partitioning & installation completed correctly. When I tried to run the

Hello, I would like to use the kernel in the domU, so that a user can install it's own kernel. While starting the domU with pygrub I get the following error: "Error: Boot loader didn't return any data!" This is the configfile of the domU: -------------- # # Configuration file for the Xen instance lenny.vandervlis.nl, created # by xen-tools 3.9 on Sun Oct 19 15:46:03 2008. # #

Package: xen-hypervisor-4.1-amd64 Version: 4.1.1-3 Severity: important Whenever I try to start a domU, xm create failed for 'Boot loader didn't return any data!'. % sudo xm create -c squeeze.cfg Using config file "/etc/xen/squeeze.cfg". Error: Boot loader didn't return any data! It seems related to the following error in dmesg [1440.163935] pygrub[3654] trap invalid

I''m newbie Xen-4.1.1 I''m trying to boot DomU with the following configuration. Sometime DomU boot, but sometime boot failed I''m not sure what is the problem. I can attach that image with tap-ctl on Dom0. Does anybody advice me about this problem?? Sincerely * Environment OS : Scientific Linux 6.1 x86_64 Kernel : 2.6.32.43

Hello I''m trying to convert a HVM to PV dom0. The domU is a 10SP2 SLED ( Kernel 2.6.16.60-0.21 i386) and is a SLES11SP2 dom0 (Kernel 3.0.13-0.27-xen 64bit). The truth is that every tutorial I see it differently and I do not know where this error. When I start the domU, pvgrub shows the options but when I select the kenel-xen, returns the error "Boot loader did not return any

Hi, I''m trying to install a FC 16 PV guest. After installation the guest doesn''t load with: Error: Boot loader didn''t return any data! xend.log: [2011-11-14 18:57:32 32321] ERROR (XendBootloader:214) Boot loader didn''t return any data! [2011-11-14 18:57:32 32321] ERROR (XendDomainInfo:483) VM start failed Traceback (most recent call last): File

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

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

Hello List, i am trying to get xen 3.3.1+ linux kernel 2.6.18 +drbd 8.3.0 working. Here is my config: ---------------------------------------------- kernel = ''/boot/vmlinuz-2.6.18.8-xenU'' memory = ''128'' root = ''/dev/sda2 ro'' disk = [ ''drbd:pgone-disk,sda2,w'' ] name

Hello, I''m using Xen (installed from source - "hg clone http://xenbits.xen.org/xen-4.0-testing.hg") on Debian Lenny. Dom0 kernel is 2.6.32-bpo.5-xen-686. Until now I have successfully ran the Lucid Ubuntu as domU guest, defining disks as (and also as file:): disk = [''tap2:aio:/home/xen/domains/lucid/disk.img,xvda1,w'',

Hi -- I''m getting this error even though I have correct DVD ISO image for snv_92. bash-3.2# uname -a SunOS stoakly2 5.11 snv_92 i86pc i386 i86xpv bash-3.2# xm create snv.py Using config file "./snv.py". Error: (2, ''Invalid kernel'', ''elf_xen_note_check: ERROR: Will only load images built for the generic loader or Linux images'') bash-3.2#

Hi All: I have run Xen 4.0.1 on my PC ( Intel(R) Core(TM) i7 CPU ) , when I run HVM domain, I found an error: sudo xm create winxp.cfg [2010-11-23 17:00:24 4993] DEBUG (XendDomainInfo:3053) XendDomainInfo.destroy: domid=1 [2010-11-23 17:00:24 4993] DEBUG (XendDomainInfo:2416) No device model [2010-11-23 17:00:24 4993] DEBUG (XendDomainInfo:2418) Releasing devices [2010-11-23 17:00:24 4993]

On Wed, Jun 22, 2016 at 05:45:05PM +0000, Shaun Reitan wrote: > Any of you guys ever seen an issue with Xen 4.4 were xm cannot create a > guest because of what looks like an issue allocating memory even though xm > info shows like 5x the amount of free memory needed? We are still > unfortunately still using xm... it's on my list, i know.. > We've had this

I am trying to get a vm running on a different host. It fails to start with the error below. Both hosts are running the same software CentOS 5.4 and Xen 3.3.1 any clues as to why it fails would be appreciated. [2009-05-04 15:31:59 3933] DEBUG (XendDomainInfo:89) XendDomainInfo.create([''vm'', [''name'', ''agree-37''],

On Wed, Jun 22, 2016 at 6:45 PM, Shaun Reitan <shaun.reitan at ndchost.com> wrote: > Any of you guys ever seen an issue with Xen 4.4 were xm cannot create a > guest because of what looks like an issue allocating memory even though xm > info shows like 5x the amount of free memory needed? We are still > unfortunately still using xm... it's on my list, i know.. > >

Hi everyone, I generated my own DomU guest using opensuse''s yast dirinstall and stored it on a seperate iscsi target. I created it as a DomU on my Domain0 (2.6.25.16-0.1-xen kernel) successfully, using the following configuration: name = "vm01-opensuse11-base-LAMP" memory = 256 kernel = "/boot/vmlinuz-xen" ramdisk = "/boot/initrd-xen" root =

Hello everyone... I get the following error when i try to creat a virtual machine Error: (4, ''Out of memory'', "xc_dom_boot_mem_init: can''t allocate low memory for domain\n") I''m using Xen under Gentoo, kernel 2.6.32-r1 in a i686 Dual Core AMD Opteron(tm) Processor 290 AuthenticAMD with 16Gb of memory and 4Tb of hard disk. It was a pain to install