On Fri, May 27, 2022 at 04:41:29PM +0200, J. Hannken-Illjes wrote: > > On 27. May 2022, at 16:24, Manuel Bouyer <[email protected]> wrote: > > > > On Fri, May 27, 2022 at 02:52:55PM +0200, J. Hannken-Illjes wrote: > >>> On 27. May 2022, at 14:41, Matthias Petermann <[email protected]> > >>> wrote: > >>> > >>> Hello Jürgen, > >>> > >>> Am 27.05.2022 um 14:14 schrieb J. Hannken-Illjes: > >>>> Stack trace of thread vnconfig (1239) and from ddb "call fstrans_dump" > >>>> should give even more details. > >>> > >>> here is the stacktrace from the vnconfig process (the PID has changed > >>> since I restarted): > >>> > >>> https://www.petermann-it.de/tmp/p7.jpg > >> > >> This is the thread currently suspending the root fs (vrevoke suspends it). > >> > >> Looks like it is waiting for I/O to drain on the vnd device ... > >> > >>> You can find the output of fstrans_dump here: > >>> > >>> https://www.petermann-it.de/tmp/p8.jpg > >> > >> The owner is irritating, it should be vnconfig from above. > > > > I can reproduce it: > > What is the recipe?
xl create -c <guest> shutdown -p now in the guest notice that the guest doesn't shut down and run xl destroy <guest> (I think xl destroy is what causes the deadlock, by running a second vnconfig -u) But my dom0 has 32 vcpus, and this seems to cause oter troubles (at the xenstore level, among others). Trying again with only 1 vcpu. -- Manuel Bouyer <[email protected]> NetBSD: 26 ans d'experience feront toujours la difference --
