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

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

Control: fixed -1 4.19.1-1 Control: affects -1 linux-image-amd64 Good to hear you were able to solve the problem for you by moving to pvgrub. I'm marking this bug as fixed in the xen version in unstable (as it should be really fixed there), but will leave the bug open as it still affects bookworm. This way it's also easier for other people to find out what's the problem and how to

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

Processing commands for control at bugs.debian.org: > found 1092495 4.17.3+10-g091466ba55-1~deb12u1 Bug #1092495 [src:xen] linux-image-amd64: xz compression incompatible with Xen/pygrub Marked as found in versions xen/4.17.3+10-g091466ba55-1~deb12u1. > thanks Stopping processing here. Please contact me if you need assistance. -- 1092495:

Package: xen-system-amd64 Version: 4.17.1+2-gb773c48e36-1 Severity: important Dear Maintainer, after upgrading my bullseye server to bookworm I ran into the issue that all VMs of type hvm are not starting anymore. xl throws an error: libxl: error: libxl_qmp.c:1399:qmp_ev_fd_callback: Domain 8:error on QMP socket: Connection reset by peer libxl: error: libxl_qmp.c:1438:qmp_ev_fd_callback: Domain

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, xen-utils-4.1's pygrub is unable to boot VMs from a partitionless blockdev that has grub installed in first sector. I'm not sure it deserves a bug report, although it is kind of a regression from 4.0. Long story short: zeroing first sector of domU's boot blockdev fixes it. Maybe some of this report would be useful in the wiki, if someone else has the same (odd) setup. --- The

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>

On Fri, Mar 14, 2025 at 10:42:24PM +0100, Maximilian Engelhardt wrote: > A fix [1] for the IO_PAGE_FAULT went into xen 4.20 which is now available in > testing and unstable. > The 4.20.0-1 Debian source package can also be compiled for bookworm if you > have a bookworm system running and want to test there. Please not that qemu > also needs to be recompiled for this xen version

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

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

-----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