From mboxrd@z Thu Jan 1 00:00:00 1970 From: Charles Duffy Subject: Re: Serial ATA Support - will it come? Date: Mon, 29 Dec 2008 12:16:38 -0600 Message-ID: References: <003327ECB4CD48CDB6A3B26BC4FD3440@Mobi> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit To: kvm@vger.kernel.org Return-path: Received: from main.gmane.org ([80.91.229.2]:55014 "EHLO ciao.gmane.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751847AbYL2SQx (ORCPT ); Mon, 29 Dec 2008 13:16:53 -0500 Received: from list by ciao.gmane.org with local (Exim 4.43) id 1LHMfY-0004Y0-H3 for kvm@vger.kernel.org; Mon, 29 Dec 2008 18:16:48 +0000 Received: from rrcs-71-41-149-67.sw.biz.rr.com ([71.41.149.67]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Mon, 29 Dec 2008 18:16:48 +0000 Received: from Charles_Duffy by rrcs-71-41-149-67.sw.biz.rr.com with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Mon, 29 Dec 2008 18:16:48 +0000 In-Reply-To: <003327ECB4CD48CDB6A3B26BC4FD3440@Mobi> Sender: kvm-owner@vger.kernel.org List-ID: Let's back up here a bit -- When you say "no disk was found at all" when using SCSI emulation, do you mean the kernel booted and was unable to find the hard drives, or did it not even get that far? The SCSI emulation uses the sym53c8xx driver, which was first developed against 2.0.36; it's been in the kernel long enough that I'm certain whatever kernel you're using supports it (or it wouldn't run a modern userland either). I'm guessing you're running a monolithic kernel with only the drivers you need compiled in, instead of any vendor kernel (as any and every vendor kernel would have this driver available). Frankly, if you want to allow your users to boot their machines on other than your usual hardware, it's only sensible to have a kernel that supports the secondary hardware as well as what you normally provision them -- whether this secondary hardware is physical or virtual. That said, there's a mechanism by which you can cheat: Boot the guest with an externally-provided kernel using -kernel and -append options to kvm. This isn't ideal -- you're no longer going through the guest's bootloader and so lose any settings included there -- but should be good enough for a rescue environment.