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. The suspicion is that the created scsibus0 has only one target and 256 LUNs (scsibus1 on the same VM, attached to an MPT SCSI adapter, has 8 and 16)L .... dmesg | egrep scsibus [ 1.021614] scsibus0 at vioscsi0: 1 target, 256 luns per target [ 1.021614] scsibus1 at mpt0: 16 targets, 8 luns per target [ 2.429331] scsibus1: waiting 2 seconds for devices to settle... [ 2.459338] scsibus1: holding up boot [ 4.431688] sd0 at scsibus1 target 0 lun 0: <VBOX, HARDDISK, 1.0> disk fixed [ 4.469382] sd1 at scsibus1 target 1 lun 0: <VBOX, HARDDISK, 1.0> disk fixed [ 4.479495] sd2 at scsibus1 target 2 lun 0: <VBOX, HARDDISK, 1.0> disk fixed .... Full dmesg.boot is attached. Chavdar On Thu, 21 Jan 2021 at 18:52, Chavdar Ivanov <ci4ic4%gmail.com@localhost> wrote: > > On Thu, 21 Jan 2021 at 16:15, Reinoud Zandijk <reinoud%netbsd.org@localhost> wrote: > > > > On Thu, Jan 21, 2021 at 11:45:25AM +0000, Chavdar Ivanov wrote: > > > On Sat, 21 Nov 2020 at 16:37, Chavdar Ivanov <ci4ic4%gmail.com@localhost> wrote: > > > I see there were a few recent commits around sys/dev/pci/virtio*. Just > > > to mention that the presence of a virtio scsi device in a -current > > > (from yesterday) vm under VirtualBox 6.1.16 now results in a Guru > > > Meditation Error: > > > ...... > > > 00:00:16.505215 [ 1.0443388] virtio1: SCSI device (rev. 0x01) > > > 00:00:16.505234 [ 1.0443388] vioscsi0 at virtio1: features: 0x100000000 > > > > It doesn't report that the feature negotiation goes wrong before printing its > > features, so the host is accepting v1 but nothing else and that should be OK. > > > > > 00:00:16.505323 virtio-scsi#0: virtio-scsci > > > numTargets=1!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! > > > 00:00:16.505391 emR3Debug: rc=VERR_INVALID_PARAMETER > > > > Clumsy error reporting of VirtualBox! What parameter, what call etc. > > > > Could you please test the code with vioscsi revision 0? i.e. with `legacy' > > setting? Or/and the setting 'Virtio SCSI Single' if applicable? > > What are the knobs for these settings? The only 'legacy' VBox setting > I know of is in the System->Acceleration->Paravirtualization Interface > settings. > > > Also please boot the kernel with `netbsd -vx'? > > I can attach the dmesg.boot file without virtio-scsi; with it I still > get the error. > > > > > Is there a way to get better error message? > > I've attached the full VBox.log file, it may be useful, as there are > other places referring to virtio-scsi. > > I have been using virtio-net for a long time without problems; this VM > runs whenever I run my laptop under Windows 10 and I had added a > virtio-scsi driver with a disk just to check if at some stage this > driver would be available. The VM still uses vboxvideo (insead of the > recommended now VMware video) and I always build and install the > additions on it (although obviously in this case it doesn't get to > module load). > > > > > With regards, > > Reinoud > > > > Thanks, > > Chavdar > > > -- > ---- -- ----
Attachment:
dmesg.boot
Description: Binary data