On Sat, 23 Jan 2021 at 10:13, Chavdar Ivanov <ci4...@gmail.com> wrote: > > On Fri, 22 Jan 2021 at 20:00, Reinoud Zandijk <rein...@netbsd.org> wrote: > > > > On Fri, Jan 22, 2021 at 02:23:46PM +0000, Chavdar Ivanov wrote: > > > After the latest virtio commits I no longer get the panic; the > > > virtio-scsi device is recognized and the bus is created; however, a > > > disk attached to it is not seen at all. > > > > thats interesting, since nothing changed that ought to have had influence; > > the > > only change was for virtio PCI v1.0's i386 compat the bus_space_write_8() > > was > > split into two bus_space_write_4()'s as its allowed by the spec. Since amd64 > > can write on every alignment, its odd that the write_8 would fail unless > > its a > > VirtualBox emulation error that doesn't expect an 8 byter to be written in > > one > > go. Very strange, i'll see if i can manage that. > > > > But the discs are there in the dmesg! See > > > > sd0 at scsibus1 target 0 lun 0: <VBOX, HARDDISK, 1.0> disk fixed > > sd0: fabricating a geometry > > sd0: 16384 MB, 16384 cyl, 64 head, 32 sec, 512 bytes/sect x 33554432 sectors > > sd0: fabricating a geometry > > sd1 at scsibus1 target 1 lun 0: <VBOX, HARDDISK, 1.0> disk fixed > > sd1: fabricating a geometry > > sd1: 16384 MB, 16384 cyl, 64 head, 32 sec, 512 bytes/sect x 33554432 sectors > > sd1: fabricating a geometry > > sd2 at scsibus1 target 2 lun 0: <VBOX, HARDDISK, 1.0> disk fixed > > sd2: fabricating a geometry > > sd2: 32768 MB, 32768 cyl, 64 head, 32 sec, 512 bytes/sect x 67108864 sectors > > sd2: fabricating a geometry > > > > So you can just access them using `disklabel' and fsck'ing and mounting them > > etc. Since they don't spawn dk* i presume they are not GPT. > > > > Please let me know if anything is wrong? > > Unfortunately no, sd[012] are attached to scsibus1, which is attached > to the mpt controller. It is scsibus0 which is attached to vioscsi0 > adapter: > ..... > vioscsi0 at virtio1: features: 0x100000000 > vioscsi0: cmd_per_lun 128 qsize 1024 seg_max 126 max_target 1 max_lun 256 > scsibus0 at vioscsi0: 1 target, 256 luns per target > vioscsi0: WARNING: power management not supported > scsibus1 at mpt0: 16 targets, 8 luns per target > .... > > > > Reinoud > > > > I still think it is this '1 target' - in order to be a bus, there > should be at least two targets available, as the controller itself has > one. Whether this is a driver problem or an emulation problem in the > vbox code, I don't know; I don't think I have tried vioscsi on a > different OS, which I am going to do now.
I modified an old CentOS VM - adding a virtio-scsi adapter and switching the network adapter emulation from Intel to virtio-net - and it worked right away, so I guess the virtio-scsi adapter works in principle. > > Chavdar > > > > -- > ---- -- ----
