similar to: Bug#824341: wheezy-pu: update xen-utils-4.1 with patch to boot jessie/grub2 VMs

On 14/05/16 19:35, Adam D. Barratt wrote: > Control: tags -1 + moreinfo > > On Sat, 2016-05-14 at 19:10 +0200, Daniel Pocock wrote: >> If somebody is still running wheezy for their dom0 (host) environment >> and they are using jessie or other systems with grub2 in their VMs, they >> can't boot their VM. >> >> A rather trivial 1-line fix in the dom0

Control: tags -1 + moreinfo On Sat, 2016-05-14 at 19:10 +0200, Daniel Pocock wrote: > If somebody is still running wheezy for their dom0 (host) environment > and they are using jessie or other systems with grub2 in their VMs, they > can't boot their VM. > > A rather trivial 1-line fix in the dom0 (host) system fixes the problem. > > Please advise if the release team

Package: xen-utils-4.1 Version: 4.1.4-3+deb7u4 Severity: serious Tags: patch dom0 running wheezy domU upgraded from wheezy to jessie. The domU doesn't boot any more, errors: Error code: Using <class 'grub.GrubConf.Grub2ConfigFile'> to parse /grub/grub.cfg Error parameters: Traceback (most recent call last):, File "/usr/lib/xcp/lib/pygrub.xcp", line 853, in

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 26/04/15 10:45, Bastian Blank wrote: > Hi Daniel > > On Sun, Apr 26, 2015 at 10:35:01AM +0200, Daniel Pocock wrote: >> This should probably be released in an update to wheezy. > > Well, if you can pursuade the release team. We have grub2 for Xen > in Jessie now and it can be used on Wheezy as well. > Can you be

I recently updated the kernel on an Ubuntu 11.04 PVM domU. The dom0 is an up to date Debian Squeeze host (Xen 4.0.1). Attempting to start the domU after this with xm create gives "Error: Boot loader didn''t return any data!". I ran pygrub against the domU manually, I got the following: Traceback (most recent call last): File "/usr/lib/xen-default/bin/pygrub", line

Package: xen-utils-4.0 Version: 4.0.1-1 Severity: normal Tags: patch pygrub could not boot a newly-updated Debian/testing domU with a non-chained grub2. The traceback was: Using <class 'grub.GrubConf.Grub2ConfigFile'> to parse /grub/grub.cfg WARNING:root:Unknown directive load_video WARNING:root:Unknown directive terminal_output Traceback (most recent call last): File

On Sun, Apr 26, 2015 at 10:50:16AM +0200, Daniel Pocock wrote: > On 26/04/15 10:45, Bastian Blank wrote: > > Well, if you can pursuade the release team. We have grub2 for Xen > > in Jessie now and it can be used on Wheezy as well. > Can you be more specific? If somebody is running a wheezy dom0 and > they install grub2 in their domU before rebooting it the first time, >

On Sat, 2013-09-28 at 20:59 -0700, Tril wrote: > Backtrace from manual run of the buggy GrubConf.py: > # python /usr/lib/xen-4.1/lib/python/grub/GrubConf.py grub2 grub.cfg > WARNING:root:Unknown directive load_video > WARNING:root:Unknown directive terminal_output > WARNING:root:Unknown image directive load_video > Traceback (most recent call last): > File

Sorry didn't work. Aso it will only handle this special case, not the general case of /dev/something. # python GrubConf.py grub2 /home/tehadmin/snail-grub.cfg WARNING:root:Unknown directive load_video WARNING:root:Unknown directive terminal_output WARNING:root:Unknown image directive load_video Traceback (most recent call last): File "GrubConf.py", line 467, in <module>

Confirmed this issue. To reproduce: Install a fresh Wheezy AMD64 guest under Xen 4.1 (hypervirtualized, boot from the debian-7.1.0-amd64-CD-1.iso). Use "entire disk" automatic layout for partitioning, this creates /dev/xvda1 for / and /dev/xvda5 for swap. It will create /boot/grub/grub.cfg with many references to (/dev/xvda,msdos1) which works fine when the machine is booted

Hi Daniel On Sun, Apr 26, 2015 at 10:35:01AM +0200, Daniel Pocock wrote: > This should probably be released in an update to wheezy. Well, if you can pursuade the release team. We have grub2 for Xen in Jessie now and it can be used on Wheezy as well. Bastian -- Beam me up, Scotty, there's no intelligent life down here! -------------- next part -------------- A non-text attachment was

Package: xen-utils-4.0 Version: 4.0.1-5.2 Severity: important Tags: upstream patch pygrub in Debian Squueze does not support Grub2 submenus. At least Ubuntu Precise uses a submenu for older kernel versions, so a Precise domU with more than one kernel installed will be unbootable (without manual fixes) on a Squeeze dom0. Attached is a patch that adds submenu support to pygrub. -- System

Package: xen-hypervisor-4.4-amd64 Version: 4.4.1-9+deb8u4 Severity: important Dear Maintainer, I installed a fresh Debian Jessie amd64 on our new server with Intel Xeon E3-1270 v5 Skylake CPU and EFI. Linux without Xen boots flawlessly and shows 8 CPU cores. I then tried all combinations of Xen 4.4 (with xsave=off for Skylake support), Xen 4.6 (crashes after a few seconds during boot) and

Package: xen-hypervisor-4.1-amd64 Version: 4.1.4-3+deb7u1 Package: xen-linux-system-amd64 Version: 3.2+46 Package: xen-utils-4.1 Version: 4.1.4-3+deb7u1 Package: xenwatch Version: 0.5.4-3 Package: xenstore-utils Version: 4.1.4-3+deb7u1 Package: xen-tools Version: 4.3.1-1 I installed Debian 7 (amd64) in a HX5 blade server (IBM Bladecenter H) 32 GB RAM, 2 Intel Xeon SixCore 2.Ghz, Internal

Hi all, After applying some updates onto a Debian web server, I rebooted it. However it will no longer start, and generates this error in XenCenter: 22/12/2011 09:57:45 Error: Starting VM ''Web Server'' - Using <class ''grub.GrubConf.Grub2ConfigFile''>; to parse /boot/grub/grub.cfg - WARNING:root:Unknown directive load_video - WARNING:root:Unknown directive

Booting a fedora 19 domU failed because a it could not properly parse the grub.cfg file. This was cased by set default="${next_entry}" This statement actually is within an ''if'' statement, so maybe it would be better to skip code within if/fi blocks... But this patch seems to work fine. --- tools/pygrub/src/GrubConf.py | 2 ++ 1 files changed, 2 insertions(+), 0

Package: xcp-xe Version: 1.3.2-14 Severity: important My dom0 is 64 bit wheezy with the xen-xapi environment I try the following: xe vm-install \ template=Debian\ Wheezy\ 7.0\ \(64-bit\) new-name-label=wheezytest1 xe vm-param-set uuid=$MY_UUID \ other-config:install-repository=http://ftp.ch.debian.org/debian/ xe vif-create network-uuid=$MY_NET_UUID \ vm-uuid=$MY_UUID device=0 xe

Package: xen-hypervisor-4.1-amd64 Version: 4.1.4-2 Hi, Hvm domU does not starts up afer dom0 reboot. Bridge br0 is set up manually. Dom0: Debian Wheezy 3.2.0-4-amd64 #1 SMP Debian 3.2.35-2 x86_64 GNU/Linux DomU: Debian Squeeze 2.6.32-5-amd64 #1 SMP Sun Sep 23 10:07:46 UTC 2012 x86_64 GNU/Linux config: ===<======== kernel = '/usr/lib/xen-4.1/boot/hvmloader' builder = 'hvm'

There's a couple of patches in 4.1 which might plausibly be the fix for this. changeset: 23246:8f927378135a user: Jan Beulich <jbeulich at suse.com> date: Wed Mar 07 08:35:58 2012 +0000 files: xen/arch/ia64/xen/domain.c xen/arch/x86/domain.c xen/arch/x86/domctl.c description: passthrough: release assigned PCI devices

Package: xen-hypervisor-4.3-amd64 Version: 4.3.0-3+b1 Severity: critical File: xen-hypervisor-4.3-amd Justification: breaks the whole system Dear Maintainer, Installation is a minimal system designed only to get dom0 working. The following are the uncommented GRUB commands GRUB_DEFAULT=0 GRUB_TIMEOUT=5 GRUB_DISTRIBUTOR=`lsb_release -i -s 2> /dev/null || echo Debian`