Hi, On Wed, 7 Sep 2016, Igor Boehm wrote: > virtio0 at pci0 dev 3 function 0 "Qumranet Virtio Network" rev 0x00 > vio0 at virtio0: address 52:54:a2:01:85:cd > virtio0: msix shared > virtio1 at pci0 dev 4 function 0 "Qumranet Virtio SCSI" rev 0x00 > vioscsi0 at virtio1: qsize 128 > scsibus2 at vioscsi0: 255 targets > sd0 at scsibus2 targ 0 lun 0: <QEMU, QEMU HARDDISK, 2.5+> SCSI3 0/direct fixed > sd0: 390625MB, 512 bytes/sector, 800000000 sectors, thin > virtio1: msix shared > virtio2 at pci0 dev 5 function 0 "Qumranet Virtio Memory" rev 0x00 > viomb0 at virtio2 > virtio2: apic 0 int 10
I know there have been reports about problems with virtio-scsi (openbsd driver vioscsi(4)) in the past. I could not reproduce these problems and thought they were maybe caused by very old qemu versions. But maybe there are also bugs in openbsd's vioscsi driver. How much control do you have over the VM? Can you change the disk type to virtio-block (openbsd driver vioblk(4))? That driver in openbsd is much better tested and works reliably (in my experience). I will try to reproduce the issue doing the same as you did. If I can't, I may get back to you for access to the VM. Cheers, Stefan
