This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
apport-collect 1751028
and then change the status of the bug to 'Confirmed'.
If, due to the nature of the issue you have encountered, you are unable
to run this command, please add a comment stating that fact and change
the bug status to 'Confirmed'.
This change has been made by an automated script, maintained by the
Ubuntu Kernel Team.
** Changed in: linux (Ubuntu)
Status: New => Incomplete
** Tags added: precise
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1751028
Title:
impossible to start a xen domain on precise with the spectre/meltdown
kernel
Status in linux package in Ubuntu:
Incomplete
Bug description:
Hi,
Applying the Spectre/Meltdown patched kernel (3.2.0-133-generic -
precise ESM), it's not possible to boot my xen domUs anymore (dom0 is
fine). It works fine with 3.2.0-131-generic and 3.13.0-141-generic
(lts-trusty with Spectre/Meltdown mitigations).
This is with xen 4.1.6.1-0ubuntu0.12.04.13
xend.log below :
[2018-02-22 10:56:03 1566] DEBUG (XendDomainInfo:103)
XendDomainInfo.create(['vm', ['name', 'REDACTED'], ['memory', '6144'],
['on_reboot', 'restart'], ['on_crash', 'destroy'], ['on_xend_start', 'ignore'],
['on_xend_stop', 'ignore'], ['vcpus', '1'], ['oos', 1], ['image', ['linux',
['kernel', '/vmlinuz'], ['ramdisk', '/initrd.img'], ['root', '/dev/xvda1 ro'],
['videoram', 4], ['args', 'nogbpages console=hvc0 earlyprintk=xen nosplash'],
['tsc_mode', 0], ['nomigrate', 0]]], ['s3_integrity', 1], ['device', ['vbd',
['uname', 'phy:/dev/Ubuntu/REDACTED-disk'], ['dev', 'xvda1'], ['mode', 'w']]],
['device', ['vbd', ['uname', 'phy:Ubuntu/REDACTED-swap'], ['dev', 'xvda2'],
['mode', 'w']]], ['device', ['vif', ['ip', 'REDACTED'], ['mac',
'02:00:5B:BD:5E:E2']]]])
[2018-02-22 10:56:03 1566] DEBUG (XendDomainInfo:2498)
XendDomainInfo.constructDomain
[2018-02-22 10:56:03 1566] DEBUG (balloon:187) Balloon: 6291628 KiB free;
need 16384; done.
[2018-02-22 10:56:03 1566] DEBUG (XendDomain:476) Adding Domain: 2
[2018-02-22 10:56:03 1566] DEBUG (XendDomainInfo:2836)
XendDomainInfo.initDomain: 2 256
[2018-02-22 10:56:03 1566] DEBUG (XendDomainInfo:2863)
_initDomain:shadow_memory=0x0, memory_static_max=0x180000000,
memory_static_min=0x0.
[2018-02-22 10:56:03 1566] INFO (image:182) buildDomain os=linux dom=2
vcpus=1
[2018-02-22 10:56:03 1566] DEBUG (image:721) domid = 2
[2018-02-22 10:56:03 1566] DEBUG (image:722) memsize = 6144
[2018-02-22 10:56:03 1566] DEBUG (image:723) image = /vmlinuz
[2018-02-22 10:56:03 1566] DEBUG (image:724) store_evtchn = 1
[2018-02-22 10:56:03 1566] DEBUG (image:725) console_evtchn = 2
[2018-02-22 10:56:03 1566] DEBUG (image:726) cmdline = root=/dev/xvda1
ro nogbpages console=hvc0 earlyprintk=xen nosplash
[2018-02-22 10:56:03 1566] DEBUG (image:727) ramdisk = /initrd.img
[2018-02-22 10:56:03 1566] DEBUG (image:728) vcpus = 1
[2018-02-22 10:56:03 1566] DEBUG (image:729) features =
[2018-02-22 10:56:03 1566] DEBUG (image:730) flags = 0
[2018-02-22 10:56:03 1566] DEBUG (image:731) superpages = 0
[2018-02-22 10:56:04 1566] ERROR (XendDomainInfo:2927)
XendDomainInfo.initDomain: exception occurred
Traceback (most recent call last):
File "/usr/lib/xen-4.1/bin/../lib/python/xen/xend/XendDomainInfo.py", line
2898, in _initDomain
channel_details = self.image.createImage()
File "/usr/lib/xen-4.1/bin/../lib/python/xen/xend/image.py", line 165, in
createImage
return self.createDomain()
File "/usr/lib/xen-4.1/bin/../lib/python/xen/xend/image.py", line 184, in
createDomain
result = self.buildDomain()
File "/usr/lib/xen-4.1/bin/../lib/python/xen/xend/image.py", line 1069, in
buildDomain
rc = LinuxImageHandler.buildDomain(self)
File "/usr/lib/xen-4.1/bin/../lib/python/xen/xend/image.py", line 745, in
buildDomain
superpages = self.superpages)
Error: (1, 'Internal error', 'panic: xc_dom_boot.c:79: launch_vm:
SETVCPUCONTEXT failed (rc=-1)')
[2018-02-22 10:56:04 1566] ERROR (XendDomainInfo:488) VM start failed
Traceback (most recent call last):
File "/usr/lib/xen-4.1/bin/../lib/python/xen/xend/XendDomainInfo.py", line
474, in start
XendTask.log_progress(31, 60, self._initDomain)
File "/usr/lib/xen-4.1/bin/../lib/python/xen/xend/XendTask.py", line 209,
in log_progress
retval = func(*args, **kwds)
File "/usr/lib/xen-4.1/bin/../lib/python/xen/xend/XendDomainInfo.py", line
2930, in _initDomain
raise VmError(str(exn))
VmError: (1, 'Internal error', 'panic: xc_dom_boot.c:79: launch_vm:
SETVCPUCONTEXT failed (rc=-1)')
[2018-02-22 10:56:04 1566] DEBUG (XendDomainInfo:3071)
XendDomainInfo.destroy: domid=2
[2018-02-22 10:56:05 1566] DEBUG (XendDomainInfo:2401) Destroying device
model
[2018-02-22 10:56:05 1566] DEBUG (XendDomainInfo:2408) Releasing devices
[2018-02-22 10:56:05 1566] ERROR (XendDomainInfo:108) Domain construction
failed
Traceback (most recent call last):
File "/usr/lib/xen-4.1/bin/../lib/python/xen/xend/XendDomainInfo.py", line
106, in create
vm.start()
File "/usr/lib/xen-4.1/bin/../lib/python/xen/xend/XendDomainInfo.py", line
474, in start
XendTask.log_progress(31, 60, self._initDomain)
File "/usr/lib/xen-4.1/bin/../lib/python/xen/xend/XendTask.py", line 209,
in log_progress
retval = func(*args, **kwds)
File "/usr/lib/xen-4.1/bin/../lib/python/xen/xend/XendDomainInfo.py", line
2930, in _initDomain
raise VmError(str(exn))
VmError: (1, 'Internal error', 'panic: xc_dom_boot.c:79: launch_vm:
SETVCPUCONTEXT failed (rc=-1)')
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1751028/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : [email protected]
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
