Re: kern/52199 (vioscsi kernel panic on a KVM hypervisor)

[MB <code%boerschig.net@localhost>]

The following reply was made to PR kern/52199; it has been noted by GNATS.

From: MB <code%boerschig.net@localhost>
To: gnats-bugs%NetBSD.org@localhost
Cc: 
Subject: Re: kern/52199 (vioscsi kernel panic on a KVM hypervisor)
Date: Sun, 14 May 2017 21:21:42 +0200

 Am 13.05.2017 um 22:38 schrieb jdolecek%NetBSD.org@localhost:
 > Synopsis: vioscsi kernel panic on a KVM hypervisor
 > 
 > State-Changed-From-To: open->feedback
 > State-Changed-By: jdolecek%NetBSD.org@localhost
 > State-Changed-When: Sat, 13 May 2017 20:38:08 +0000
 > State-Changed-Why:
 > A fix was committed in src/sys/dev/pci/vioscsi.c revision 1.17. Can you
 > please check with updated -current kernel?
 > 
 > 
 > 
 Thanks for your work.
 The installation works now, allthough the "resource shortage" messages appear.
 The 'resource shortage' messages also seem to affect the write performance.
 However, I see some strange behavior and I'm not sure if it is related to the vioscsi driver:
 
 After installation, I put some load on the virtual disk, and the whole system seems to freeze. 
 Once it continued after a couple of minutes, currently it is wedged for 10min+..
 FWIW, I could produce this on a 10gb test image, default installation, with the following, but only on 3 out of 8 attempts:
 
 dd if=/dev/urandom of=/home/test1.bin bs=1m count=128
 ls -lahR / 
 for i in $(seq 0 8);do dd if=/home/test1.bin of=/home/foo$i ;done
 #when the system freezes, here are no "adapter resource shortage" messages, they only appear when the system works without freeze
 ls -lahR / 
 for i in $(seq 0 8);do dd if=/home/test1.bin of=/home/foo$i ;done
 #this freezes, no keyboard input, not even '(qemu) sendkey ctrl-alt-f2'