© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
bbfa235
(Get the code!)
# lsb_release -rd
Description: Ubuntu 16.04.3 LTS
Release: 16.04
This problem is related to the latest kernel for meltdown spectre patches for xen pv guest and pygrub.
This is the kernel that was attempting to be upgraded.
linux-image-
I tried to report this issue with the following command but it failed:
````
ubuntu-bug linux
*** Collecting problem information
The collected information can be sent to the developers to improve the
application. This might take a few minutes.
...............
*** Problem in linux-image-
The problem cannot be reported:
This is not an official Ubuntu package. Please remove any third party package and try again.
Press any key to continue...
No pending crash reports. Try --help for more information.
````
I have an Ubuntu 14.04 running Xen and a VM running Ubuntu 16.04 LTS that I'm having issues with it booting after upgrading the kernel for meltdown and spectre vulnerability.
````
sudo apt-get update
sudo apt-get upgrade
sudo apt-get dist-upgrade
````
Ubuntu 14.04 xen host reboot failure log:
````
$ tailf /var/log/
Domain 24 needs to be cleaned up: destroying the domain
Done. Rebooting now
libxl: error: libxl_bootloade
libxl: error: libxl_exec.
libxl: error: libxl_create.
````
````
cat /var/log/
Using <class 'grub.GrubConf.
┌─────
│ Ubuntu │
│ Ubuntu, with Linux 4.4.0-109-generic │
│ Ubuntu, with Linux 4.4.0-109-generic (recovery mode) │
│ Ubuntu, with Linux 4.4.0-108-generic │
│ Ubuntu, with Linux 4.4.0-108-generic (recovery mode) │
│ Ubuntu, with Linux 4.4.0-104-generic │
│ Ubuntu, with Linux 4.4.0-104-generic (recovery mode) │
│ Ubuntu, with Linux 4.4.0-15-generic │
└─────
Use the ^ and ┴ keys to select which entry is highlighted.
Press enter to boot the selected OS, 'e' to edit the
commands before booting, 'a' to modify the kernel arguments
before booting, or 'c' for a command line.
Traceback (most recent call last):
File "/usr/lib/
os.write(fd, ostring)
OSError: [Errno 28] No space left on device
````
I was able to get the vm to boot only by rapidly attempt to access the menu options and boot the old kernel (4.4.0-15-generic). Disk space and inodes seems fine on the host Ubuntu 14.04LTS and Ubuntu 16.04LTS Guest.
Ubuntu 14.04 Host:
````
root@host:
udev 197M 12K 197M 1% /dev
tmpfs 42M 1.1M 41M 3% /run
/dev/dm-0 104G 49G 50G 50% /
none 4.0K 0 4.0K 0% /sys/fs/cgroup
none 5.0M 0 5.0M 0% /run/lock
none 208M 0 208M 0% /run/shm
none 100M 0 100M 0% /run/user
/dev/sda1 236M 40M 184M 18% /boot
root@host:
Filesystem Inodes IUsed IFree IUse% Mounted on
udev 50K 721 49K 2% /dev
tmpfs 52K 849 52K 2% /run
/dev/dm-0 6.6M 86K 6.5M 2% /
none 52K 2 52K 1% /sys/fs/cgroup
none 52K 5 52K 1% /run/lock
none 52K 1 52K 1% /run/shm
none 52K 2 52K 1% /run/user
/dev/sda1 61K 298 61K 1% /boot
root@host:
````
Ubuntu 16.04 PV Guest:
````
root@guest:~# df -hFilesystem Size Used Avail Use% Mounted on
udev 950M 0 950M 0% /dev
tmpfs 200M 3.1M 197M 2% /run
/dev/mapper/
tmpfs 997M 0 997M 0% /dev/shm
tmpfs 5.0M 0 5.0M 0% /run/lock
tmpfs 997M 0 997M 0% /sys/fs/cgroup
/dev/xvda1 472M 192M 256M 43% /boot
tmpfs 200M 0 200M 0% /run/user/1000
root@www2:~# df -hi
Filesystem Inodes IUsed IFree IUse% Mounted on
udev 238K 406 237K 1% /dev
tmpfs 250K 491 249K 1% /run
/dev/mapper/
tmpfs 250K 1 250K 1% /dev/shm
tmpfs 250K 7 250K 1% /run/lock
tmpfs 250K 16 250K 1% /sys/fs/cgroup
/dev/xvda1 122K 315 122K 1% /boot
tmpfs 250K 4 250K 1% /run/user/1000
root@guest:~#
````
Here is the guest Ubuntu 16.04 OS kernels:
````
root@guest:~# dpkg -l | grep linux-image-
ii linux-image-
ii linux-image-
ii linux-image-
ii linux-image-
ii linux-image-
ii linux-image-
ii linux-image-
ii linux-image-
ii linux-image-generic 4.4.0.109.114 amd64 Generic Linux kernel image
root@guest:~#
````
I'm currently able to boot to 4.4.0-15.31
Here is my xen config file that I use to start the vm:
````
# cat /etc/xen/guest.cfg
# /var/lib/
name = "guest"
#kernel = "/var/lib/
#ramdisk = "/var/lib/
bootloader = "/usr/lib/
memory = 2048
vcpus = 1
disk = [ '/dev/host-
#
# Networking
#
vif = [ 'ip=xxx.xxx.xxx.xxx ,mac=AA:
#
# Behaviour
#
on_poweroff = 'destroy'
on_reboot = 'restart'
on_crash = 'restart'
````
I also tried launching the vm with strace output of
````
strace xl create -c file.cfg
````
is here: https:/
I'm a bit lost as to the cause of this... I was hoping to just upgrade the kernel for meltdown and spectre, but this issue I've never faced before. I think it might be related to pygrub and the new kernel? I don't know for sure though anything I can check to figure this out better? Thanks.