xen 4.1.2 not booting on Linux Mint 13 Maya with grub2 1.99 UEFI boot
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Linux Mint |
New
|
Undecided
|
Unassigned |
Bug Description
1) Linux Mint 13 Maya with 3.2.0-26-generic kernel and latest updates (except those that were withheld from updating)
Xen 4.1.2 package installed via synaptic
Hardware: Asus Sabertooth X79 motherboard, i7 3930K CPU with VT-d support (C2 stepping), 32GB memory, 120GB SSD and several WD20EARX HDDs, PNY (Nvidia) Quadro 600 GPU.
Linux Mint 13 is installed on the GPT partitioned SSD using the following partitions:
/dev/sda1 EFI system partition (fat32)
/dev/sda2 /boot partition (ext2)
/dev/sda3 formatted to LVM:
/dev/mapper/
/dev/mapper/
UEFI boot.
Linux Mint 13 boots just fine and mounts the LVs (/ and /home).
2) Installed xen-amd64 (Xen 4.1.2) and auxiliary packages via synaptic and ran update-grub. Rebooted and the system stopped at this screen:
(XEN) Xen version 4.1.2 (Ubuntu 4.1.2-Zubuntu2.1) (<email address hidden>) (gcc version 4.6.3 (Ubuntu/Linaro 4.6.3-1ubuntu5) ) Mon Jun 18 14:13:52 UTC 2012
(XEN) Bootloader: GRUB 1.99-21ubuntu3.1
(XEN) Command line: placeholder
(XEN) Video information:
(XEN) VGA is text mode 80x25, font 8x16
(XEN) VBE/DDC methods: V2; EDID transfer time: 1 seconds
(XEN) Disc information:
(XEN) Found 0 MBR signatures
(XEN) Found 0 EDD information structures
(XEN) Xen-e801 RAM map:
(XEN) 0000000000000000 - 000000000009d400 (usable)
(XEN) 0000000000100000 - 00000000deb00000 (usable)
(XEN) System RAM: 3562MB (3648116kB)
3) The system doesn't respond to keyboard input and needs a hard reset (power off) to shutdown/reboot.
Here is the relevant part of the grub.cfg file:
### BEGIN /etc/grub.
submenu "Xen 4.1-amd64" {
menuentry 'LinuxMint GNU/Linux, with Xen 4.1-amd64 and Linux 3.2.0-26-generic' --class linuxmint --class gnu-linux --class gnu --class os --class xen {
insmod part_gpt
insmod ext2
set root='(hd0,gpt2)'
search --no-floppy --fs-uuid --set=root d461c2c7-
echo 'Loading Xen 4.1-amd64 ...'
multiboot /xen-4.1-amd64.gz placeholder
echo 'Loading Linux 3.2.0-26-generic ...'
module /vmlinuz-
echo 'Loading initial ramdisk ...'
module /initrd.
}
Adding
recordfail
gfxmode $linux_gfx_mode
insmod gzio
above the insmod part_gpt produces this screen output BEFORE the above screen appears:
"Booting a command list
Loading Xen 4.1-amd64 ...
WARNING: no console will be available to OSLoading Linux 3.2.0-26-generic ...
Loading initial ramdisk ..."
4) About 2 months ago I installed Linux Mint LMDE and then the Xen kernel and it booted just fine, using the same synaptic installation procedure with no modifications.
I was hoping that the Xen hypervisor (dom0) using a LM13 Maya installation would work the same way and boot.
5) I completely removed all xen packages and re-installed Xen. No difference - it doesn't boot!
I also tried some grub commands for the xen kernel (limiting or increasing the default memory size to 4GB, for example), but that made no difference.
I suspect that either the xen-am64 kernel doesn't work, or perhaps a problem with the initrd.
I understand that initrd.
I'm still searching the log files but there seems to be no entry of the xen boot, compared to tons of logs for a regular boot.
tags: | removed: 3.2.0-26-generic kernel |
tags: | removed: 13 linux maya mint |
description: | updated |
I added the set pager=0 and set debug=all commands at grub and got to the following point where the system froze:
lib/relocator. c:1222: min_addr = 0x0, max_addr = 0xffffffffffffffff, target = 0x100000 c:433: trying to allocate in 0x100000- 0xfffffffffffff ffff aligned 0x1 size 0x1bd000 c:529: Blocking at 0xa75b1000- 0xde295000
lib/relocator.
lib/relocator.
I had this same situation before when trying to install LM13 to boot via UEFI, also using LVM for / and /home !!! Later I somehow managed to install LM13 with the said setup, but it looks like that installing the xen hypervisor package breaks something. So my guess is that it's either something with the grub script (update-grub) that doesn't work, or a missing step (grub-install?), or something missing in the UEFI boot setup?
I will try to reinstall grub-efi and see if that makes a difference.
P.S.: In the meantime I installed all upgradable packages, but that didn't make any difference.