XEN-DomU autostart fails on cold boot after update to Buster

Kernels & Hardware, configuring network, installing services

XEN-DomU autostart fails on cold boot after update to Buster

Postby GerdB » 2020-07-24 09:54

Hello to all,

after updating my Debian to Buster the xen DomU autostart fails, but only on cold boot! If i "reboot" the Dom0, DomU's autostart works fine!?!

It seems to be a timing problem related to the hard drives, because on reboot (warm boot) the DomU will be ready a little faster. But I can not find any hint, what I have to do, to solve this problem.
Even if I do not use autostart and try to start the DomU manuelly after a cold boot, this also fails.

I am using Debian and xen more than 10 years, but now I have no idea or found hint in the logs about the reason.
syslog and xenstored_access can be found below the following link. Each of them is splitted in a part of "cold boot" (Kaltstart) and "reboot" (Warmstart).
https://a250695.jupiter.1blu.de/data/public/608212.php

Any help will be welcome.

Thanks and greetings
Gerd
GerdB
 
Posts: 2
Joined: 2020-07-24 08:57

Re: XEN-DomU autostart fails on cold boot after update to Bu

Postby pylkko » 2020-08-07 05:07

But is the disk physically OK?

Code: Select all
Jul 24 06:12:23 mainserver root: /etc/xen/scripts/block: Writing backend/vbd/1/51748/hotplug-error xenstore-read backend/vbd/1/51748/params failed. backend/vbd/1/51748/hotplug-status error to xenstore.
Jul 24 06:12:23 mainserver xendomains[913]: Starting Xen domain fileserver (from /etc/xen/auto/fileserver.cfg)...failed.
Jul 24 06:12:23 mainserver xendomains[913]: libxl: error: libxl_aoutils.c:539:async_exec_timeout: killing execution of /etc/xen/scripts/block add because of timeout
Jul 24 06:12:23 mainserver xendomains[913]: libxl: error: libxl_aoutils.c:539:async_exec_timeout: killing execution of /etc/xen/scripts/block add because of timeout
Jul 24 06:12:23 mainserver xendomains[913]: libxl: error: libxl_aoutils.c:539:async_exec_timeout: killing execution of /etc/xen/scripts/block add because of timeout
Jul 24 06:12:23 mainserver xendomains[913]: libxl: error: libxl_aoutils.c:539:async_exec_timeout: killing execution of /etc/xen/scripts/block add because of timeout
Jul 24 06:12:23 mainserver xendomains[913]: libxl: error: libxl_aoutils.c:539:async_exec_timeout: killing execution of /etc/xen/scripts/block add because of timeout
Jul 24 06:12:23 mainserver xendomains[913]: libxl: error: libxl_aoutils.c:539:async_exec_timeout: killing execution of /etc/xen/scripts/block add because of timeout
Jul 24 06:12:23 mainserver xendomains[913]: libxl: error: libxl_create.c:1299:domcreate_launch_dm: Domain 1:unable to add disk devices


After this there are lines upon lines about failing to add sbd, despite being able to add another disk just previous to it
User avatar
pylkko
 
Posts: 1779
Joined: 2014-11-06 19:02

Re: XEN-DomU autostart fails on cold boot after update to Bu

Postby GerdB » 2020-08-07 07:10

Yes, the disks are ok.

This Problem ist realy crazy:
- After a cold boot of Dom0 (mainserver), it is not possible to start this DomU (fileserver). It is the same on autostart with Dom0 (mainserver) or an manuall start after Dom0 (mainserver).
- The only way I can use this DomU (fileserver) is a reboot of Dom0 (mainserver) after a cold boot. Then it works also with autostart.
GerdB
 
Posts: 2
Joined: 2020-07-24 08:57


Return to System configuration

Who is online

Users browsing this forum: No registered users and 9 guests

fashionable