Grub multiboot is unable to load Xen under EFI
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Release Notes for Ubuntu |
Fix Released
|
Undecided
|
Unassigned | ||
xen (Ubuntu) |
Confirmed
|
Medium
|
Unassigned |
Bug Description
As a new Xen user, when I install the `xen-hypervisor
But upon rebooting, even if Xen succeed to boot, the system is basically unusable, and there are plenty of Irq errors in dmesg.
It turns out that EFI is not very well supported under Xen:
http://
The alternatives are:
- boot directly from the Efi (instead of relying on grub's multiboot)
- enable legacy boot in the EFI, and reinstall grub in bios-mode (and hope that everything goes well)
Since I don't think that the latter can be automated, the first one would be a better approach for ubuntu's packaging, I think.
But even if that's not possible, or there are no resources for it, at least (until EFI on Grub won't be properly supported), either at install time or at boot time, the fact that the system is running on EFI should be detected, and explicitly warn the user (halt the boot process?) to avoid leaving him in a puzzlingly half-working system.
ProblemType: Bug
DistroRelease: Ubuntu 15.10
Package: xen-hypervisor-
ProcVersionSign
Uname: Linux 4.2.0-18-generic x86_64
ApportVersion: 2.19.1-0ubuntu5
Architecture: amd64
CurrentDesktop: Unity
Date: Sun Nov 29 19:19:05 2015
InstallationDate: Installed on 2015-11-22 (7 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
SourcePackage: xen
UpgradeStatus: No upgrade log present (probably fresh install)
mtime.conffile.
Changed in xen (Ubuntu): | |
importance: | Undecided → Critical |
Changed in ubuntu-release-notes: | |
assignee: | nobody → Stefan Bader (smb) |
status: | New → Confirmed |
Changed in ubuntu-release-notes: | |
status: | Confirmed → Fix Released |
assignee: | Stefan Bader (smb) → nobody |
Changed in ubuntu-release-notes: | |
assignee: | nobody → mstr (9sj) |
Changed in ubuntu-release-notes: | |
assignee: | mstr (9sj) → nobody |
Status changed to 'Confirmed' because the bug affects multiple users.