From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: AHCI? Date: Sun, 05 Apr 2009 18:39:55 +0300 Message-ID: <49D8D0CB.70908@redhat.com> References: <84fb38e30904042030s5fa1b80exff8f45c165188b77@mail.gmail.com> <49D89B02.2090303@redhat.com> <84fb38e30904050753n361bd112i54b58202ab84be15@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: kvm@vger.kernel.org To: tsuraan Return-path: Received: from mx2.redhat.com ([66.187.237.31]:49231 "EHLO mx2.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751047AbZDEPkA (ORCPT ); Sun, 5 Apr 2009 11:40:00 -0400 In-Reply-To: <84fb38e30904050753n361bd112i54b58202ab84be15@mail.gmail.com> Sender: kvm-owner@vger.kernel.org List-ID: tsuraan wrote: >> No plan that I know of. Is the LSI scsi device not supported by Solaris? >> > > Yeah, there was a short thread about it last July > (http://www.mail-archive.com/kvm@vger.kernel.org/msg01633.html). The > jist of it is that 64-bit OpenSolaris no longer supports the 53c895a > SCSI controller. According to that thread, the 53c1010 is what VMWare > uses, and OpenSolaris still uses that. > > I see. That sucks. > I don't really understand how a VM exposes a virtual device to a > hosted OS, but I assume that it involves looking at a driver for a > piece of hardware and then writing some code that emulates the > behaviour expected by that driver? The best way is to look at the device spec and write the emulation to conform to that. > I would think AHCI would be a > great way to go, if that's the case, since it would be an actual > implementation of a standard instead of an arbitrary card. Does kvm > use the qemu source for its drivers, or is there a separate source > tree for it now? We use the qemu source (we have our own branch, but it's very close to qemu upstream). -- error compiling committee.c: too many arguments to function