similar to: [RFC] Bootloader configuration

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

I''ve got a CentOS 5.3 dom0 with Xen 3.4.1-rc5 (or so). I''ve tried the same stuff below with 3.4.0, no difference. I''m trying to install 2009.06 PV domU based on instructions from [1] and [2]. I can run the install fine, I can also get the kernel and boot archive (from [2]) after the install. But for the life of me I can''t get the installed domU to boot. If I

This enables the usage of a bootloader, i.e., pygrub, when starting a domain using xm in Xen-API mode. Signed-off-by: Stefan Berger <stefanb@us.ibm.com> _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

Note: I could simply direct boot the appropriate kernel/initrd to get the alpha1 installation going as always done in the past, but I think this should work. The Debian alpha 1 installer page says it should. Details $ sudo xm create -c wheezytest.cfg Using config file "./wheezytest.cfg". Error: Boot loader didn''t return any data! direct pygrub test run: # pygrub

Hullo everybody I want to install a guest slackeware guest OS on a VM for xenserver 5.6 . I have created logical volumes , mounted the slackware 13 image and copied the /lib/modules and below are my configurations. [root@virtualintranet /]# uname -r 2.6.27.42-0.1.1.xs5.6.0.44.111158xen *Grub Configs:* [root@virtualintranet grub]# cat grub.conf default=0 timeout=10 title

Hullo everybody I want to install a guest slackeware guest OS on a VM for xenserver 5.6 . I have created logical volumes , mounted the slackware 13 image and copied the /lib/modules and below are my configurations. [root@virtualintranet /]# uname -r 2.6.27.42-0.1.1.xs5.6.0.44.111158xen *Grub Configs:* [root@virtualintranet grub]# cat grub.conf default=0 timeout=10 title

# HG changeset patch # User Olaf Hering <olaf@aepfle.de> # Date 1346945306 -7200 # Node ID 8a2eef481d3ab3ca5692dd0083c95cf314fe1da3 # Parent 19d367bf07b7687b831c212a57a70e73ea14d3b7 pygrub: always append --args If a bootloader entry in menu.lst has no additional kernel command line options listed and the domU.cfg has ''bootargs="--args=something"'' the additional

Greetings! Trying to to run a xen3 domU on a xen4 dem0 I run into problems. The xen server ''XEN1''(dom0) is openSUSE-11.3 (kernel 2.6.34) and xen-4.0.1. With qemu I created an image ''M08.raw'' from the SUSE-9.3 (kernel 2.6.11) and XEN-3.0 installation CD''s. The XEN modules were included in the installation. In M08.raw/boot I configured grub/menu.lst:

Hi I am having some problems installing a paravirt RHEL guest on a deb amd64 xen machine uname -a = Linux debxen 2.6.20-1-xen-amd64 #1 SMP Tue Apr 24 22:23:22 UTC 2007 x86_64 GNU/Linux ============== xm info ============== host : debxen release : 2.6.20-1-xen-amd64 version : #1 SMP Tue Apr 24 22:23:22 UTC 2007 machine : x86_64

Hi, All I''m just new to this list, I''m started to dealing with OSS Xen to XCP migration earlier this week, seem the domUs installed via virt-install are function well, but domUs copied via dom0 are failed during bootup process, finally I realize if I could fix this on my OSS Xen will resolve all. Can I have any suggestion from you please ? *Details* *Source XenHost* OS:

I mounted an iso file like so: ------------------------------------------- # mount -o loop=/dev/loop0 /path/to/iso /tmp/mnt #ls /tmp/mnt cdromupgrade  dists  doc  install  isolinux  md5sum.txt  pics  pool  preseed  README.diskdefines  ubuntu ------------------------------------------- I used the following file to try to have pygrub boot the mounted iso: -------------------------------------------

domUloader potentially makes my life a lot easier, but from experiments and looking at the code, it doesn''t seem like there is any way to pass kernel command line arguments with it. Am I just missing something? Thanks, John Byrne _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

When I am trying to create a PV guest on DQ35, i am getting following error: >xm create CENTOS_PV.cfg -c Traceback (most recent call last): File "/usr/bin/pygrub", line 680, in ? zfsinfo = fsimage.getbootstring(fs) AttributeError: ''module'' object has no attribute ''getbootstring'' Error: Boot loader didn''t return any data! PV

Populate-on-demand: Check pages being returned by the balloon driver This patch series is the second result of my work last summer on decreasing fragmentation of superpages in a guests'' p2m when using populate-on-demand. This patch series is against 4.1; I''m posting it to get feedback on the viability of getting a ported version of this patch into 4.2. As with the previous

I am running a Debian Squeeze Xen 4.0.1 Hypervisor and 2.6.32-5-xen-amd64 dom0. My xen-tools.conf: lvm = vg00 size = 100Gb # Disk image size. memory = 2048Mb # Memory size swap = 2G # Swap size # noswap = 1 # Don''t use swap at all for the new system. fs = ext4 # use the EXT3 filesystem for the disk image. dist = `xt-guess-suite-and-mirror --suite` # Default

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

************************ Installation profile ************************ [root@ServerRHL51 vm]# cat snv85.install name = "Solaris85pvm" vcpus = 1 memory = "1024" kernel = "/usr/lib/xen-solaris/unix-85" ramdisk = "/usr/lib/xen-solaris/x86.miniroot-85" extra = "/platform/i86xpv/kernel/amd64/unix - nowin -B install_media=cdrom" disk =

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

I have fedora13 as domain0 kernel on xen-3.4.3 or xen-4.0.1. I installed ubuntu10.04 as guest-os following this : 1) download installer from : - http://fi.archive.ubuntu.com/ubuntu/dists/lucid/main/installer-amd64/current/images/netboot/xen/vmlinuz - http://fi.archive.ubuntu.com/ubuntu/dists/lucid/main/installer-amd64/current/images/netboot/xen/initrd.gz to /boot directory 2) edit xen guest

# HG changeset patch # User Ian Campbell <ian.campbell@citrix.com> # Date 1337273492 -3600 # Node ID cdb947baea102aa6a1d53472f8a3e5f2d6cc485e # Parent ac45608496cd85b0bf1aed6e5b869b4a86ca672f libxl: do not overwrite user supplied config when running bootloader. Currently when running the bootloader libxl will update b_info->u.pv.kernel, .ramdisk, .cmdline and .bootloader. This can