From mboxrd@z Thu Jan 1 00:00:00 1970 From: Thomas Mueller Subject: Re: virtio & minimal .config Date: Tue, 19 Feb 2008 08:39:37 +0100 Message-ID: <47BA87B9.4010402@muellerit.ch> References: <47B990CC.2010209@chaschperli.ch> <47B99261.7090701@codemonkey.ws> <47B9B79E.1060807@chaschperli.ch> <47B9C1DB.1040505@codemonkey.ws> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: kvm-devel@lists.sourceforge.net Return-path: In-Reply-To: <47B9C1DB.1040505@codemonkey.ws> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: kvm-devel-bounces@lists.sourceforge.net Errors-To: kvm-devel-bounces@lists.sourceforge.net List-Id: kvm.vger.kernel.org >>>> >>>> >>> Please post your command line for launching KVM. Make sure you have a >>> root parameter like "root=/dev/vda1". >>> >> the "vda1" thing i didn't know. thanks. will also give it a try - tomorrow. >> >> Is "virtio" block device replacing SATA/SCSI - are the SCSI/SATA >> drivers needed on guest? >> > > The virtio block driver should be the only block driver you need in the > guest unless you want to give the guest a cdrom (which requires IDE). > The virtio block protocol should support everything needed to expose a > CDROM to a guest but we haven't implemented backend support for it yet. thanks to Anthony, you led me to the right direction. it's working now. problem was mainly that there's a new (ok, don't know if it's realy new, but i never used it) -drive option. i just updated http://kvm.qumranet.com/kvmwiki/Virtio with my new knowledge. :) - Thomas ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/