[Bug 1751028] Re: impossible to start a xen domain on precise with the spectre/meltdown kernel
** Changed in: linux (Ubuntu) Importance: Undecided => High ** Also affects: linux (Ubuntu Precise) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Precise) Status: New => Confirmed ** Changed in: linux (Ubuntu Precise) Importance: Undecided => High ** Tags added: pti -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1751028 Title: impossible to start a xen domain on precise with the spectre/meltdown kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1751028/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1751028] Re: impossible to start a xen domain on precise with the spectre/meltdown kernel
apport information ** Tags added: apport-collected ** Description changed: 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=0x18000, 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
[Bug 1751028] Re: impossible to start a xen domain on precise with the spectre/meltdown kernel
$ cat /proc/version_signature Ubuntu 3.13.0-141.190~precise1-generic 3.13.11-ckt39 $ sudo lspci -vnvn 00:03.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] ES1000 [1002:515e] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device [103c:31fb] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping+ SERR+ FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- Reset- FastB2B- PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn- Capabilities: [90] PCI-X bridge device Secondary Status: 64bit+ 133MHz+ SCD- USC- SCO- SRD- Freq=133MHz Status: Dev=00:05.0 64bit- 133MHz- SCD- USC- SCO- SRD- Upstream: Capacity=0 CommitmentLimit=0 Downstream: Capacity=0 CommitmentLimit=0 Capabilities: [a0] HyperTransport: MSI Mapping Enable+ Fixed- Mapping Address Base: fee0 Capabilities: [b0] HyperTransport: Slave or Primary Interface Command: BaseUnitID=5 UnitCnt=3 MastHost- DefDir- Link Control 0: CFlE+ CST- CFE- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- Reset- FastB2B- PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn- Capabilities: [a0] HyperTransport: MSI Mapping Enable+ Fixed- Mapping Address Base: fee0 Capabilities: [b0] Express (v1) Root Port (Slot-), MSI 00 DevCap: MaxPayload 512 bytes, PhantFunc 0, Latency L0s <64ns, L1 <1us ExtTag- RBE+ FLReset- DevCtl: Report errors: Correctable- Non-Fatal+ Fatal+ Unsupported- RlxdOrd+ ExtTag- PhantFunc- AuxPwr- NoSnoop+ MaxPayload 512 bytes, MaxReadReq 128 bytes DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr- TransPend- LnkCap: Port #1, Speed 2.5GT/s, Width x16, ASPM L0s L1, Latency L0 <4us, L1 <16us ClockPM- Surprise+ LLActRep+ BwNot- LnkCtl: ASPM Disabled; RCB 128 bytes Disabled- Retrain- CommClk- ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt- LnkSta: Speed 2.5GT/s, Width x16, TrErr- Train- SlotClk- DLActive- BWMgmt- ABWMgmt- RootCtl: ErrCorrectable- ErrNon-Fatal+ ErrFatal+ PMEIntEna- CRSVisible- RootCap: CRSVisible- RootSta: PME ReqID , PMEStatus- PMEPending- Capabilities: [98] Power Management version 3 Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0+,D1-,D2-,D3hot+,D3cold+) Status: D0 NoSoftRst+ PME-Enable- DSel=0 DScale=0 PME- Capabilities: [80] MSI: Enable- Count=1/2 Maskable- 64bit+ Address: Data: Capabilities: [78] Subsystem: Hewlett-Packard Company Device [103c:3113] Capabilities: [50] HyperTransport: Slave or Primary Interface Command: BaseUnitID=15 UnitCnt=5 MastHost- DefDir- DUL- Link Control 0: CFlE+ CST- CFE- Kernel driver in use: pcieport Kernel modules: shpchp 00:10.0 PCI bridge [0604]: Broadcom HT2100 PCI-Express Bridge [1166:0142] (rev a2) (prog-if 00 [Normal decode]) Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr+ Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B- PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn- Capabilities: [a0] HyperTransport: MSI Mapping Enable+ Fixed- Mapping Address Base: fee0 Capabilities: [b0] Express (v1) Root Port (Slot-), MSI 00 DevCap: MaxPayload 512 bytes, PhantFunc 0, Latency L0s <64ns, L1 <1us ExtTag- RBE+ FLReset- DevCtl: Report errors: Correctable- Non-Fatal+ Fatal+ Unsupported- RlxdOrd+ ExtTag- PhantFunc- AuxPwr- NoSnoop+ MaxPayload 512 bytes, MaxReadReq 128 bytes DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr- TransPend- LnkCap: Port #2, Speed 2.5GT/s, Width x8, ASPM L0s L1, Latency L0 <4us, L1 <16us ClockPM- Surprise+ LLActRep+ BwNot- LnkCtl: ASPM Disabled; RCB 128 bytes Disabled- Retrain- CommClk- ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt- LnkSta: Speed 2.5GT/s, Width x8, TrErr- Train- SlotClk- DLActive- BWMgmt- ABWMgmt- RootCtl: ErrCorrectable- ErrNon-Fatal+ ErrFatal+ PMEIntEna- CRSVisible- RootCap: CRSVisible- RootSta: PME ReqID , PMEStatus-
