Jaromír Dole?ek <jaromir.dole...@gmail.com> wrote:
> Thanks. Could you please try a -current kernel for DOMU and see if it
> crashes the same? If possible a DOMU kernel from daily builds, to rule
> out local compiler issue.
It crashes the same way with a kernel from 201808050730. here is uname
-a output:
NetBSD bacasable 8.99.23 NetBSD 8.99.23 (XEN3PAE_DOMU) #0: Sun Aug 5
06:48:50 UTC 2018
mkre...@mkrepro.netbsd.org:/usr/src/sys/arch/xen/compile/XEN3PAE_DOMU
i386
> xbd is not mpsafe, so it shouldn't be even race due to parallell
> processing on different CPUs. Maybe it would be useful to check if the
> problem still happens when you assign just single CPU to the DOMU.
I get the crash with vcpu = 1 for the domU. I also tried to pin a single
cpu for the test domU, I still get it to crash:
xl vcpu-pin bacasable 0 0
xl vcpu-pin $other_domU all 1-3
An interesting point: Adding the -X flag to dump seems to let it work
without a panic. It may be luck, but that did not crash so far.
--
Emmanuel Dreyfus
http://hcpnet.free.fr/pubz
m...@netbsd.org
