Bug#886591: 4.9.0-5 (after kaiser patch) breaks xen pvh

[Michael Stone]

A debconf function to prevent creating an unbootable system would still 
be nice...

Bug#886591: 4.9.0-5 (after kaiser patch) breaks xen pvh

[Gianluigi Tiesi]

On 01/08/2018 10:47 AM, Hans van Kranenburg wrote:

tags 886491 + wontfix
tags 886591 + wontfix
thanks

On 01/07/2018 11:28 PM, Hans van Kranenburg wrote:


Thanks for your report. This does not render the complete package
unusable for any user.


The answer from upstream Xen to this is:

https://lists.xenproject.org/archives/html/xen-devel/2018-01/msg00540.html

So, breakage is expected and it's not going to be fixed.

Hans van Kranenburg



perhaps it does not work even with pti=off

--
Gianluigi Tiesi 
EDP Project Leader
Netfarm S.r.l. - http://www.netfarm.it/
Free Software: http://oss.netfarm.it/

Q: Because it reverses the logical flow of conversation.
A: Why is putting a reply at the top of the message frowned upon?

Bug#886491: Bug#886591: 4.9.0-5 (after kaiser patch) breaks xen pvh

[Hans van Kranenburg]

tags 886491 + wontfix
tags 886591 + wontfix
thanks

On 01/07/2018 11:28 PM, Hans van Kranenburg wrote:
> 
> Thanks for your report. This does not render the complete package
> unusable for any user.

The answer from upstream Xen to this is:

https://lists.xenproject.org/archives/html/xen-devel/2018-01/msg00540.html

So, breakage is expected and it's not going to be fixed.

Hans van Kranenburg

Bug#886591: 4.9.0-5 (after kaiser patch) breaks xen pvh

[Hans van Kranenburg]

# ok, let's try again...
severity 886591 important
reassign 886591 src:linux 4.9.65-3+deb9u2
merge 886591 886491
thanks

Thanks for your report. This does not render the complete package
unusable for any user.

Hans

Bug#886591: 4.9.0-5 (after kaiser patch) breaks xen pvh

[Gianluigi Tiesi]

Package: linux-image-4.9.0-5-amd64
Version: 4.9.65-3+deb9u2
Severity: grave

I've updated kernel to new version in stretch linux-image-4.9.0-5-amd64 
(4.9.65-3+deb9u2)
and pvh-enabled xen domain are refusing to start.

Nothing useful in the log, it just says the domain crashes

Waiting for domain xen3 (domid 2) to die [pid 5488]
Domain 2 has shut down, reason code 3 0x3
Action for shutdown reason code 3 is destroy
Domain 2 needs to be cleaned up: destroying the domain
Done. Exiting now

without pvh = 1 or with previous linux-image-4.9.0-4-amd64 (4.9.65-3) it works 
fine

relevant xen domain config:

device_model_version = 'none'
kernel  = '/boot/vmlinuz-4.9.0-4-amd64'
extra   = 'elevator=noop'
ramdisk = '/boot/initrd.img-4.9.0-4-amd64'
vcpus   = '8'
memory  = '4096'
pvh = 1

(or /boot/vmlinuz-4.9.0-5-amd64 when trying new kernel)


Regards



-- System Information:
Debian Release: buster/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 4.9.0-5-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)