similar to: Bug#1092495: linux-image-amd64: xz compression incompatible with Xen/pygrub

Hi, I ran into this bug on bookworm and was able to fix an existing machine by booting the old kernel and then converting it to pvgrub. But... I am unable to create new pvgrub compatible DomU's now because xen-create-image does not support pvgrub. I attempted to work around this by adding a xen-create-image role script that installs grub-xen, but it will not install properly inside the

Hi Damien, On Donnerstag, 16. Januar 2025 00:08:24 CET Damien Norris wrote: [...] > > All this left me with an incomplete grub config after xen-create-image > was finished, so pvgrub will not boot it. > > Currently xen-create-image installs 6.1.0-29 kernel (because it's not > looking at bookworm-updates by default) so this problem is recoverable; > boot in pygrub and

Processing control commands: > fixed -1 4.19.1-1 Bug #1092495 [src:xen] linux-image-amd64: xz compression incompatible with Xen/pygrub Marked as fixed in versions xen/4.19.1-1. > affects -1 linux-image-amd64 Bug #1092495 [src:xen] linux-image-amd64: xz compression incompatible with Xen/pygrub Added indication that 1092495 affects linux-image-amd64 -- 1092495:

Package: release.debian.org Severity: normal Tags: bookworm User: release.debian.org at packages.debian.org Usertags: pu X-Debbugs-Cc: xen at packages.debian.org, hans at knorrie.org, maxi at daemonizer.de Control: affects -1 + src:xen [ Reason ] Linux 6.12 changed the way it xz compresses the kernel [1]. This broke direct kernel boot in bookworm xen for kernels 6.12 or newer. It only affects

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

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

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

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

Your message dated Fri, 10 Jan 2025 20:36:04 +0100 with message-id <39184179.XM6RcZxFsP at localhost> and subject line Re: libxen: Libxen Includes Code Similar to LZO Decompressor with a Known CVE has caused the Debian Bug report #1085137, regarding libxen: Libxen Includes Code Similar to LZO Decompressor with a Known CVE to be marked as done. This means that you claim that the problem has

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

Package: xen-utils-3.2-1 Version: 3.2.1-2 Severity: normal Tags: patch Hi, There is a bug xen-3-3.2.1/tools/libfsimage/reiserfs/fsys_reiserfs.c, it is using "unsigned long" which is 64 bits on amd64 arch and 32 bits on i386 arch. This makes pygrub can't work on reiserfs on amd64 arch. You can easily reproduce it. A patch is included for fixing this problem. diff

When will we see progress on this? pvgrub is the newer and better thing, and it's the only way to do many things. For one thing, It should make it easier to boot an OS on a partitioned block device, pygrub can't do that unless you probe the paritions first and make then visible on Dom0 - a hassle. Otherwise, it would just simply do what real GRUB can really do. I would really like to

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

Attached fixes running pygrub with many kernels to do proper scrolling Signed-off-by: Jeremy Katz <katzj@redhat.com> _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

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'

https://bugzilla.redhat.com/show_bug.cgi?id=466681 just to be sure that some one in xvm-team notices that before any bits from xvm-gate are putback ;) Florian

Thank you for your contribution to Debian. Mapping bookworm to stable. Mapping stable to proposed-updates. Accepted: -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 Format: 1.8 Date: Sun, 26 Jan 2025 22:42:25 +0100 Source: xen Architecture: source Version: 4.17.5+23-ga4e5191dc0-2 Distribution: bookworm Urgency: medium Maintainer: Debian Xen Team <pkg-xen-devel at lists.alioth.debian.org>

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Xen Security Advisory CVE-2012-4544 / XSA-25 Xen domain builder Out-of-memory due to malicious kernel/ramdisk ISSUE DESCRIPTION ================= The Xen PV domain builder contained no validation of the size of the supplied kernel or ramdisk either before or after decompression. This could cause the toolstack to consume all available RAM

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Xen Security Advisory CVE-2012-4544,CVE-2012-2625 / XSA-25 version 2 Xen domain builder Out-of-memory due to malicious kernel/ramdisk UPDATES IN VERSION 2 ==================== Clarify that XSA-25 is reporting, via the Xen.org security process, both CVE-2012-4544 and CVE-2012-2625. Also we would like to

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