From mboxrd@z Thu Jan 1 00:00:00 1970 From: Venkateswararao Jujjuri Subject: Re: [PATCH 2/2] kvm tools: Add virtio-9p Date: Thu, 26 May 2011 08:22:54 -0700 Message-ID: <4DDE704E.2010404@linux.vnet.ibm.com> References: <1305657337-2584-1-git-send-email-levinsasha928@gmail.com> <1305657337-2584-2-git-send-email-levinsasha928@gmail.com> <20110517184023.GC16689@elte.hu> <1305659307.12150.37.camel@sasha> <1305664052.12150.43.camel@sasha> <1305709505.12150.71.camel@sasha> <4DDE6398.107@linux.vnet.ibm.com> <1306420607.3065.20.camel@lappy> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Eric Van Hensbergen , Ingo Molnar , penberg@kernel.org, asias.hejun@gmail.com, prasadjoshi124@gmail.com, gorcunov@gmail.com, kvm@vger.kernel.org To: Sasha Levin Return-path: Received: from e36.co.us.ibm.com ([32.97.110.154]:55255 "EHLO e36.co.us.ibm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751930Ab1EZPXm (ORCPT ); Thu, 26 May 2011 11:23:42 -0400 Received: from d03relay01.boulder.ibm.com (d03relay01.boulder.ibm.com [9.17.195.226]) by e36.co.us.ibm.com (8.14.4/8.13.1) with ESMTP id p4QFHowt014114 for ; Thu, 26 May 2011 09:17:50 -0600 Received: from d03av02.boulder.ibm.com (d03av02.boulder.ibm.com [9.17.195.168]) by d03relay01.boulder.ibm.com (8.13.8/8.13.8/NCO v10.0) with ESMTP id p4QFNKxJ047586 for ; Thu, 26 May 2011 09:23:22 -0600 Received: from d03av02.boulder.ibm.com (loopback [127.0.0.1]) by d03av02.boulder.ibm.com (8.14.4/8.13.1/NCO v10.0 AVout) with ESMTP id p4Q9MRS4023055 for ; Thu, 26 May 2011 03:22:28 -0600 In-Reply-To: <1306420607.3065.20.camel@lappy> Sender: kvm-owner@vger.kernel.org List-ID: On 05/26/2011 07:36 AM, Sasha Levin wrote: > On Thu, 2011-05-26 at 07:28 -0700, Venkateswararao Jujjuri wrote: >> Any progress on this? May I get more detailed instructions on how >> you did this trick? Basically booting on 9P/VirtIO. >> >> Thanks, >> JV >> > Ofcourse. This change didn't go into tools/kvm/ since we only support > the legacy 9p2000 protocol at the moment, which means that even though > we can boot - it's quite unusable to work with. > > The trick is pretty simple: You need to name your virtio transport > "/dev/root" (I think it's currently named "local" in qemu). Once it's > named this way, boot with the following kernel cmdline added: > "root=/dev/root rootflags=rw,trans=virtio,version=9p2000 rootfstype=9p > rw" (You should be able to change version to one of the 9p2000 > extensions). Ah I guess you are making use of rootfstype. So in this setup basically the virtio transport you create is /dev/root instead of "kvm_9p" correct? Also your dir will be / ? i.e Start KVM with '--virtio-9p /'. ? > I've noticed that the transport *has* to be named "/dev/root", naming it > something else (and adjusting the "root=" parameter) doesn't seem to > work. > > Also, if it's named "/dev/root" I couldn't mount it as a simple > filesystem from within a guest - not as root. >