From: Steffen Einsle <einsle@phptrix.de>
To: xen-devel@lists.xenproject.org
Subject: DomU Windows Server Essentials crashes with xen 4.16 but works with xen 4.14
Date: Mon, 25 Apr 2022 19:19:08 +0200 [thread overview]
Message-ID: <18bd542a-a649-c78b-b575-c62b4d533e44@phptrix.de> (raw)
Hello Everyone,
I have some xen servers I recently tried to update from xen 4.14 to xen 4.16
Everything worked without problem, except for the Windows Server
Essentials DomUs.
With xen 4.16 those domains crashed (reproducable) during boot -
KMODE_EXCEPTION_NOT_HANDLED.
I tried to install a new DomU Windows Server 2019 Essentials - this VM
crashed at the first reboot
(still in the installation routine) with the same error. No PV-drivers
installed yet.
I switched back to xen 4.14 and all VMs booted ok without problem.
All other VMs (Linux-PV, Windows-HVM (2008r2, 2012r2, 2016, 2019, 2022)
show no problems, only
the Windows Server Essentials crashes with xen 4.16.
The system is a gentoo kernel 5.17.3, qemu-6.2.0-r4, xen-4.16.0-r5,
xen-tools-4.16.0-r1
My working configuration is gentoo kernel 5.17.3, qemu-5.2.0-r2,
xen-4.14.3-r2, xen-tools-4.14.3
My DomU config file looks like this
name = 'DC-Server'
type = 'hvm'
memory = '8192'
vcpus = '6'
vif = [ 'mac=00:16:3E:ab:cd:50,bridge=br0' ]
disk = [ '/dev/vg1/ServerSys,raw,hda,rw',
'/dev/vg1/ServerData,raw,hdb,rw' ]
viridian = 'all'
localtime = '1'
vnc = '1'
keymap = 'de'
vnclisten = '0.0.0.0:10,websocket'
usb = '1'
usbdevice = 'tablet'
on_crash = 'restart'
boot = 'c'
xen_platform_pci = '1'
max_grant_frames = 128
I tried disabling viridian but this made no change.
Is this a known problem?
--
Steffen
next reply other threads:[~2022-04-25 17:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-25 17:19 Steffen Einsle [this message]
2022-04-26 7:06 ` DomU Windows Server Essentials crashes with xen 4.16 but works with xen 4.14 Roger Pau Monné
2022-04-26 8:10 ` Steffen Einsle
2022-04-26 16:37 ` Roger Pau Monné
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=18bd542a-a649-c78b-b575-c62b4d533e44@phptrix.de \
--to=einsle@phptrix.de \
--cc=xen-devel@lists.xenproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.