From: Sasha Levin <levinsasha928@gmail.com>
To: Venkateswararao Jujjuri <jvrao@linux.vnet.ibm.com>
Cc: Eric Van Hensbergen <ericvh@gmail.com>,
Ingo Molnar <mingo@elte.hu>,
penberg@kernel.org, asias.hejun@gmail.com,
prasadjoshi124@gmail.com, gorcunov@gmail.com,
kvm@vger.kernel.org
Subject: Re: [PATCH 2/2] kvm tools: Add virtio-9p
Date: Thu, 26 May 2011 17:36:47 +0300 [thread overview]
Message-ID: <1306420607.3065.20.camel@lappy> (raw)
In-Reply-To: <4DDE6398.107@linux.vnet.ibm.com>
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).
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.
--
Sasha.
next prev parent reply other threads:[~2011-05-26 14:36 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-17 18:35 [PATCH 1/2] kvm tools: Copy net/9p/9p.h Sasha Levin
2011-05-17 18:35 ` [PATCH 2/2] kvm tools: Add virtio-9p Sasha Levin
2011-05-17 18:40 ` Ingo Molnar
2011-05-17 19:08 ` Sasha Levin
2011-05-17 19:20 ` Ingo Molnar
2011-05-17 20:27 ` Sasha Levin
2011-05-18 1:18 ` Eric Van Hensbergen
2011-05-18 8:08 ` Ingo Molnar
2011-05-18 9:05 ` Sasha Levin
2011-05-20 1:10 ` Venkateswararao Jujjuri
2011-05-26 14:28 ` Venkateswararao Jujjuri
2011-05-26 14:36 ` Sasha Levin [this message]
2011-05-26 15:22 ` Venkateswararao Jujjuri
2011-05-26 15:30 ` Sasha Levin
2011-05-18 12:01 ` Sasha Levin
2011-05-18 12:06 ` Ingo Molnar
2011-05-18 12:23 ` Sasha Levin
2011-05-18 6:38 ` Pekka Enberg
2011-05-18 10:35 ` Sasha Levin
2011-05-18 10:38 ` Pekka Enberg
2011-05-18 10:47 ` Sasha Levin
2011-05-18 11:09 ` Ingo Molnar
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1306420607.3065.20.camel@lappy \
--to=levinsasha928@gmail.com \
--cc=asias.hejun@gmail.com \
--cc=ericvh@gmail.com \
--cc=gorcunov@gmail.com \
--cc=jvrao@linux.vnet.ibm.com \
--cc=kvm@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=penberg@kernel.org \
--cc=prasadjoshi124@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox