similar to: [PATCH, PV-GRUB DOC] Add details to PV-GRUB documentation

Hello, The attached patch adds bzip2 and lzma/xz libs to stubdom for pvgrub. This is the first step of getting the additional compression methods supported in pvgrub. There''s still some Makefile voodoo to sort out before pvgrub actually properly gets linked against these new libs. This patch only adds the libs and makes them build. -- Pasi

I have this working on Fedora. It turned out to be very easy to add this as I simply took the grub-ext4-support.patch from the Fedora grub package and put it in xen-4.0.1/stubdom/grub.patches/ . Using pvgrub (without a vif on the virtual machine as I was having problems if I did give it a network interface) I could read and boot from ext4 partition with this patch but not without it. Is this

Does this install -d -m0755 -p "/mnt/gen2/TmpDir/portage/app-emulation/xen-pvgrub-4.3.0/image//usr/lib/xen/boot" install -m0644 -p mini-os-x86_32-grub/mini-os.gz "/mnt/gen2/TmpDir/portage/app-emulation/xen-pvgrub-4.3.0/image//usr/lib/xen/boot/pv-grub-x86_32.gz" make: Leaving directory `/mnt/gen2/TmpDir/portage/app-emulation/xen-pvgrub-4.3.0/work/xen-4.3.0/stubdom'

Hi, The following patches add support for ext4 and btrfs to PV-GRUB. These patches are taken nearly verbatim from those provided by Fedora and Gentoo. We''ve been using these patches for the PV-GRUB images available in EC2 for some time now with no problems. Changes from v1: - Makefile has been changed to check the exit code from patch - The btrfs patch has been rebased to apply

PV-GRUB: xfs support i386 doesn''t have PAE anyway. Index: fsys_xfs.c =================================================================== RCS file: /sources/grub/grub/stage2/fsys_xfs.c,v retrieving revision 1.5 diff -u -p -r1.5 fsys_xfs.c --- fsys_xfs.c 8 May 2005 02:18:14 -0000 1.5 +++ fsys_xfs.c 10 Jul 2008 13:09:50 -0000 @@ -101,7 +101,7 @@ static inline __const__ xfs_uint16_t le16

so it appears that PVGRUB requires that I specifiy (in my domain config file) either the -x86_64 or the -x86_32 version. Does anyone have a clever way I can let my users switch between x86_64 and i386 without giving them access to the domain config file? Preferably, something more secure than PyGRUB? I was considering hacking up PyGRUB so that it only allows the user a choice of

Hello, I am still confused: does pyGrub run in dom0 as root? as it says in here: "PyGRUB used to act as a “PV bootloader”: it runs in dom0 as root, opens the PV disk image, reads its GRUB menu.lst, presents a GRUB-like menu to let the user choose a kernel which it copies to the dom0 filesystem, it then closes the disk image and eventually tells the domain builder to use that copy. Such a

After hours of googling and not really finding a definitive solution to my problem, I''m a little stuck and would really appreciate some help from others. I have a CentOS 5.4 x86-64 server running Xen 3.3 from the gitco repos as dom0. On this I have created two logical volumes comprising 8GB for the system disk (xvda) and 1.5GB for swap (xvdb). I ran mkfs.ext3 and mkswap on these to

Hi, Having a problem getting a domu to boot correctly. When I enter xl create guest it boots straight into grubdom. If I enter the config location in grubdom t boots as expected. The location of the grub.cfg is the same in my domu config as what in entering but just will not work. Any ideas? Ian .

On Sat, Feb 20, 2016 at 9:24 PM, Sarah Newman <srn at prgmr.com> wrote: > On 02/17/2016 04:30 AM, George Dunlap wrote: >> I have the following packages going through the CBS: >> * A CentOS 7 xen-4.6.1-2, with XSAs 170 and 154 >> * A CentOS 6 xen-4.6.1-2, with XSAs 170 and 154 >> * A CentOS 6 xen-4.4.3-11, with XSAs 170 >> >> All these should show up in

In dispatch_rw_block_io after a call to HYPERVISOR_grant_table_op, there is the following code which calls fast_flush_area and breaks out of the loop early if one of the handles returned from HYPERVISOR_grant_table_op is negative: for (i = 0; i < nseg; i++) { if (unlikely(map[i].handle < 0)) { DPRINTK("invalid buffer -- could not remap it\n"); fast_flush_area(pending_idx,

Hello, I just wrote a step-by-step tutorial how to install the latest Xen 4.0.1 hypervisor on Fedora 13 (x86_64) host from src.rpm packages, and the pvops dom0 kernel from git repository. Check it out: http://wiki.xensource.com/xenwiki/Fedora13Xen4Tutorial It also shows how to install various Xen PV guests using the native distro installers: - CentOS 5.5 - Fedora 13 - Ubuntu 10.04 LTS

Hello, I just wrote a step-by-step tutorial how to install the latest Xen 4.0.1 hypervisor on Fedora 13 (x86_64) host from src.rpm packages, and the pvops dom0 kernel from git repository. Check it out: http://wiki.xensource.com/xenwiki/Fedora13Xen4Tutorial It also shows how to install various Xen PV guests using the native distro installers: - CentOS 5.5 - Fedora 13 - Ubuntu 10.04 LTS

On Fri, Sep 25, 2015 at 12:55 PM, Johnny Hughes <johnny at centos.org> wrote: > On 09/25/2015 03:01 AM, Christoph wrote: >> Am 2015-09-25 09:53, schrieb Pasi K?rkk?inen: >>> >>> Yeah the testing rpms for centos7/xen are in virt7-xen-44-testing >>> repository (and virt7-xen-46-testing aswell). >>> >> >> oh cool... how stable is it? I

Thank Zhigang Wang for your response. I have test pvgrub with this config file: #pv-config kernel = "/usr/lib/xen/boot/pv-grub-x86_32.gz" extra = "(hd0,5)/boot/grub/menu.lst" memory = 512 name = "ExampleDomain" disk = [ ''file:/var/lib/xen/images/opensuse11-1/disk0,xvda,w'' ] vif = [ "bridge=eth0" ] root = "/dev/sda5 ro" start

I have the following packages going through the CBS: * A CentOS 7 xen-4.6.1-2, with XSAs 170 and 154 * A CentOS 6 xen-4.6.1-2, with XSAs 170 and 154 * A CentOS 6 xen-4.4.3-11, with XSAs 170 All these should show up in mirrors hopefully sometime later today. As usual, please report any problems here. Xen 4.4 only has XSA 170 because at the time the embargo was lifted, I didn't have a suitable

Hi there, I''m trying to find out if theres anything wrong with using extra = "clocksource=jiffies" in domU configuration. It seems to fix some problems we''ve had with live migration. Thanks. -- Please remember that an email is just like a postcard; it is not confidential nor private nor secure and can be read by many other people than the intended recipient.

On Sun, Sep 27, 2015 at 6:33 PM, Christoph <mangel at gmx.de> wrote: > Am 2015-09-25 17:25, schrieb George Dunlap: >> >> The code is from the XenProject, which is developed by a number of >> different companies, not just Citrix. >> >> The XenProject has greatly expanded our automated testing over the >> last few years; additionally, a number of

Hey all, I have need to boot 32bit domu''s on a amd64 system. I was able to deploy a 32bit image but the kernel is still 64bit. I have a feeling in my .cfg file for the domU I need to specify a 32bit kernel. Is this correct? _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users

Hi Everyone, To convert an HVM install to PV, is it just as simple as creating a new config file, and use the "kernel" and "initrd" parameters to boot from a XEN kernel stored in the Dom0, and use the (ex) HVM''s disk image in the "disk" parameter? Or is there something else I am missing? Thanks _______________________________________________ Xen-users