Date: Sun, 12 Jan 2014 22:47:17 -0500 From: Nathan Whitehorn <nwhitehorn@freebsd.org> To: Bryan Venteicher <bryanv@freebsd.org> Cc: svn-src-head@freebsd.org, svn-src-all@freebsd.org, src-committers@freebsd.org Subject: Re: svn commit: r260566 - head/sys/dev/virtio/scsi Message-ID: <52D361C5.2030507@freebsd.org> In-Reply-To: <CAGaYwLfsu=2giMffqJN7Fnt_exYGMSQRDJxXv68yQWd=VTGdoQ@mail.gmail.com> References: <201401121740.s0CHelGk032373@svn.freebsd.org> <52D313F1.9010005@freebsd.org> <CAGaYwLfsu=2giMffqJN7Fnt_exYGMSQRDJxXv68yQWd=VTGdoQ@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 01/12/14 20:02, Bryan Venteicher wrote: > > > On Sun, Jan 12, 2014 at 4:15 PM, Nathan Whitehorn > <nwhitehorn@freebsd.org <mailto:nwhitehorn@freebsd.org>> wrote: > > This looks like it is uses a two-level set of hierarchical LUNs. Does > REPORT_LUNS not work? The new extended LUN support in CAM should > be able > to handle this kind of thing now without virtio knowing anything > about it. > > > > Details from the PR seem to suggest the Google Compute Engine > hypervisor (I'd guess it is some QEMU fork) doesn't support REPORT_LUNS. > Indeed. It's unfortunate their implementation is broken, but I guess we have to work around it. -Nathan
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?52D361C5.2030507>