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: Thu, 27 Apr 2017 23:32:57 +0200

 Well, booting a 7.99.70 kernel fixes the immediate crash, however
 copying 160mb of tarballs takes forever , and a lot of the
 "sd0(vioscsi0:0:1:0) adapter resource shortage" messages appear.
 Nothing I could run in production...
 I asked the ISP for more information on the KVM version used.
 
 Am 27.04.2017 um 21:30 schrieb Jaromír DoleÄ?ek:
 > The following reply was made to PR kern/52199; it has been noted by GNATS.
 > 
 > From: =?UTF-8?B?SmFyb23DrXIgRG9sZcSNZWs=?= <jaromir.dolecek%gmail.com@localhost>
 > To: gnats-bugs%netbsd.org@localhost
 > Cc: code%boerschig.net@localhost
 > Subject: Re: kern/52199 (vioscsi kernel panic on a KVM hypervisor)
 > Date: Thu, 27 Apr 2017 21:25:57 +0200
 > 
 >  Forgot to say - there were some improvements done to the driver on
 >  HEAD which were not ported to 7.1 branch yet, so using -current kernel
 >  might resolve your problem.
 >  
 >  Jaromir
 >  
 >  2017-04-27 21:24 GMT+02:00  <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: Thu, 27 Apr 2017 19:24:04 +0000
 >  > State-Changed-Why:
 >  > Can you please try booting with kernel from -current sources? You can download
 >  > it from http://nyftp.netbsd.org/pub/NetBSD-daily/HEAD/, for example
 >  > http://nyftp.netbsd.org/pub/NetBSD-daily/HEAD/201704270800Z/amd64/binary/kernel/
 >  >
 >  >
 >  >
 >  
 >