[Pkg-xen-devel] Unable to run domU guests

[laamalif at pm.me]

Hi Maintainers,

Since recent update dom0 is unable to run any PV or HVM guests.

DEBIAN VERSION:
Distributor ID:	Debian

Description: Debian GNU/Linux 10 (buster)
Release: 10
Codename: buster

KERNEL VERSION: Linux mve 4.19.0-9-amd64 #1 SMP Debian 4.19.118-2+deb10u1 (2020-06-07) x86_64 GNU/Linux

PROGRAM:

xen-utils-4.11
Version: 4.11.4+24-gddaaccbbab-1~deb10u1

ERROR MESSAGES:
Waiting for domain Windows (domid 1) to die [pid 4631]

/var/log/syslog
===========
Jul 21 18:52:52 mve systemd-udevd[27997]: Could not generate persistent MAC address for vif1.0-emu: No such file or directory
Jul 21 18:52:52 mve kernel: [110127.093692] tun: Universal TUN/TAP device driver, 1.6
Jul 21 18:52:52 mve systemd-udevd[27997]: link_config: autonegotiation is unset or enabled, the speed and duplex are not writable.
Jul 21 18:52:52 mve xara: /etc/xen/scripts/vif-bridge: online type_if=vif XENBUS_PATH=backend/vif/1/0
Jul 21 18:52:52 mve kernel: [110127.285604] xenbr0: port 2(vif1.0) entered blocking state
Jul 21 18:52:52 mve kernel: [110127.285605] xenbr0: port 2(vif1.0) entered disabled state
Jul 21 18:52:52 mve kernel: [110127.285643] device vif1.0 entered promiscuous mode
Jul 21 18:52:52 mve kernel: [110127.288401] IPv6: ADDRCONF(NETDEV_UP): vif1.0: link is not ready
Jul 21 18:52:52 mve xara: /etc/xen/scripts/vif-bridge: Successful vif-bridge online for vif1.0, bridge xenbr0.
Jul 21 18:52:52 mve xara: /etc/xen/scripts/vif-bridge: Writing backend/vif/1/0/hotplug-status connected to xenstore.
Jul 21 18:52:52 mve xara: /etc/xen/scripts/vif-bridge: add type_if=tap XENBUS_PATH=backend/vif/1/0
Jul 21 18:52:52 mve kernel: [110127.362197] xenbr0: port 3(vif1.0-emu) entered blocking state
Jul 21 18:52:52 mve kernel: [110127.362198] xenbr0: port 3(vif1.0-emu) entered disabled state
Jul 21 18:52:52 mve kernel: [110127.362241] device vif1.0-emu entered promiscuous mode
Jul 21 18:52:52 mve xara: /etc/xen/scripts/vif-bridge: Successful vif-bridge add for vif1.0-emu, bridge xenbr0.
Jul 21 18:52:52 mve kernel: [110127.365133] xenbr0: port 3(vif1.0-emu) entered blocking state
Jul 21 18:52:52 mve kernel: [110127.365135] xenbr0: port 3(vif1.0-emu) entered forwarding state
Jul 21 18:52:52 mve kernel: [110127.413131] xenbr0: port 3(vif1.0-emu) entered disabled state
Jul 21 18:52:52 mve kernel: [110127.414991] device vif1.0-emu left promiscuous mode
Jul 21 18:52:52 mve kernel: [110127.414993] xenbr0: port 3(vif1.0-emu) entered disabled state
Jul 21 18:52:52 mve xara: /etc/xen/scripts/block: remove XENBUS_PATH=backend/vbd/1/51712
Jul 21 18:52:52 mve xara: /etc/xen/scripts/vif-bridge: offline type_if=vif XENBUS_PATH=backend/vif/1/0
Jul 21 18:52:52 mve kernel: [110127.441499] xenbr0: port 2(vif1.0) entered disabled state
Jul 21 18:52:52 mve kernel: [110127.443669] device vif1.0 left promiscuous mode
Jul 21 18:52:52 mve kernel: [110127.443670] xenbr0: port 2(vif1.0) entered disabled state
Jul 21 18:52:52 mve xara: /etc/xen/scripts/vif-bridge: brctl delif xenbr0 vif1.0 failed
Jul 21 18:52:52 mve xara: /etc/xen/scripts/vif-bridge: ifconfig vif1.0 down failed
Jul 21 18:52:52 mve xara: /etc/xen/scripts/vif-bridge: Successful vif-bridge offline for vif1.0, bridge xenbr0.
Jul 21 18:52:53 mve xara: /etc/xen/scripts/vif-bridge: remove type_if=tap XENBUS_PATH=backend/vif/1/0
Jul 21 18:52:53 mve xara: /etc/xen/scripts/vif-bridge: Successful vif-bridge remove for vif1.0-emu, bridge xenbr0.
Jul 21 18:52:59 mve xara: /etc/xen/scripts/block: add XENBUS_PATH=backend/vbd/2/51712

/var/log/xen/xl-Windows.log
=====================
Domain 1 has shut down, reason code 3 0x3
Action for shutdown reason code 3 is destroy
Domain 1 needs to be cleaned up: destroying the domain
Done. Exiting now
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://alioth-lists.debian.net/pipermail/pkg-xen-devel/attachments/20200721/f19030de/attachment.html>