pci-arbiter + rumpdisk boots!
Hi all, I got the arbiter to play nice with rumpdisk! But as soon as you log in it crashes the disk and qemu, I think probably because there is a mismatched libpciaccess.so in userspace versus the statically linked ones in the pci/disk servers? I'm not sure yet. -- PCI device_open (mem) PCI not pci, fallback to kernel Starting enhanced syslogd: rsyslogdrsyslogd: could not load module 'imklog', err ors: trying to load module /usr/lib/i386-gnu/rsyslog/imklog.so: /usr/lib/i386-gn u/rsyslog/imklog.so: undefined symbol: klogWillRunPrePrivDrop [v8.39.0 try http: //www.rsyslog.com/e/2066 ] . Starting deferred execution scheduler: atd. Starting periodic command scheduler: cron. Starting system message bus: dbus. Debian GNU/Hurd bullseye/sid zamhurd console login: root Password: The programs included with the Debian GNU/Hurd system are free software; the exact distribution terms for each program are described in the individual files in /usr/share/doc/*/copyright. Debian GNU/Hurd comes with ABSOLUTELY NO WARRANTY, to the extent permitted by applicable law. ahcisata0 channel 0: setting WDCTL_RST failed for drive 0 ./noide: line 4: 535871 Segmentation fault (core dumped) /extra/qemu/bin/qemu-system-i386
Re: pci-arbiter + rumpdisk boots!
Damien Zammit, le mar. 02 mars 2021 00:14:29 +1100, a ecrit: > I got the arbiter to play nice with rumpdisk! Yay!! > But as soon as you log in it crashes the disk and qemu, I think probably > because there is a mismatched > libpciaccess.so in userspace versus the statically linked ones in the > pci/disk servers? Well, I'd rather first make sure about concurrent pci-arbiter processes Then > ahcisata0 channel 0: setting WDCTL_RST failed for drive 0 > ./noide: line 4: 535871 Segmentation fault (core dumped) > /extra/qemu/bin/qemu-system-i386 This is really not supposed to happen: a guest is not supposed to be able to crash qemu :) So it could be a bug in qemu's ahci support actually. Samuel
Re: pci-arbiter + rumpdisk boots!
> This is really not supposed to happen: a guest is not supposed to be > able to crash qemu :) > So it could be a bug in qemu's ahci support actually. Could be interesting try it in real hardware ;) El lun, 1 mar 2021 a las 14:29, Samuel Thibault () escribió: > Damien Zammit, le mar. 02 mars 2021 00:14:29 +1100, a ecrit: > > I got the arbiter to play nice with rumpdisk! > > Yay!! > > > But as soon as you log in it crashes the disk and qemu, I think probably > because there is a mismatched > > libpciaccess.so in userspace versus the statically linked ones in the > pci/disk servers? > > Well, I'd rather first make sure about concurrent pci-arbiter processes > > Then > > > ahcisata0 channel 0: setting WDCTL_RST failed for drive 0 > > ./noide: line 4: 535871 Segmentation fault (core dumped) > /extra/qemu/bin/qemu-system-i386 > > This is really not supposed to happen: a guest is not supposed to be > able to crash qemu :) > So it could be a bug in qemu's ahci support actually. > > Samuel > >
