Ubuntu domU can not start after domU was upgraded from 19.04 to 19.10
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
xen (Ubuntu) |
Confirmed
|
Undecided
|
Stefan Bader |
Bug Description
Hello,
I upgraded a Xen PV domU with Ubuntu 19.04 installed to 19.10. The domU is running on a Ubuntu 18.04 server with xen 4.9.2. The upgrade went fine, and I restarted the system as expected. But the domU want start. I use pygrub for the domU to start.
Here the config of the domU
-------
# Basics
name = "lisa"
memory = 2048
bootloader = "pygrub"
# Disks
disk = [
'phy:
'phy:
]
# Network Interface
vif = [
'bridge=xenbr0, mac=00:
'bridge=xenbr1, mac=00:
]
# Advanced
vcpus=2
-------
Here the output when I start the machine with xl:
-------
xl create /etc/xen/lisa.cfg
Parsing config from /etc/xen/lisa.cfg
xc: error: panic: xc_dom_
: Invalid kernel
xc: error: panic: xc_dom_core.c:702: xc_dom_find_loader: no loader found: Invalid kernel
libxl: error: libxl_dom.
libxl: error: libxl_create.
libxl: error: libxl_domain.
libxl: error: libxl_domain.
libxl: error: libxl_domain.
-------
Thanks for your help
Imker
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xen-hypervisor-
ProcVersionSign
Uname: Linux 4.15.0-70-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.9
Architecture: amd64
Date: Sat Nov 30 15:30:19 2019
InstallationDate: Installed on 2013-05-16 (2388 days ago)
InstallationMedia: Ubuntu-Server 12.04.2 LTS "Precise Pangolin" - Release amd64 (20130214)
SourcePackage: xen
UpgradeStatus: Upgraded to bionic on 2018-09-20 (435 days ago)
Changed in xen (Ubuntu): | |
assignee: | nobody → Stefan Bader (smb) |
Changed in xen (Ubuntu): | |
importance: | Undecided → Wishlist |
importance: | Wishlist → Undecided |
I've had the same problem for a while now, similar setup as described on the forums:
https:/ /ubuntuforums. org/showthread. php?t=2431459& p=13913095# post13913095
I can boot the older 5.0.0 kernel if I'm fast enough with the console immediately upon creation of the DomU (i.e., xl create -c ...), but this makes unattended DomU start unachievable.