From: Sasha Levin <levinsasha928@gmail.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: 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: Tue, 17 May 2011 23:27:31 +0300 [thread overview]
Message-ID: <1305664052.12150.43.camel@sasha> (raw)
In-Reply-To: <1305659307.12150.37.camel@sasha>
On Tue, 2011-05-17 at 22:08 +0300, Sasha Levin wrote:
> 'kvm_9p' isn't created as a device under /dev, it's just a name used
> internally by 9pnet_virtio (and located under sysfs).
>
> I couldn't figure out which params the kernel would expect to boot using
> 9p over virtio (theres no device name to begin with).
>
> I've also couldn't find anything that suggested it's possible to boot
> using virtio-9p as rootfs.
Ignore that.
Naming the virtio transport "/dev/root" and passing proper params to the
kernel makes it work:
[ 1.844983] VFS: Mounted root (9p filesystem) on device 0:11.
I'll make some changes to the virtio-9p patch to make it easier for the
user to do that.
--
Sasha.
next prev parent reply other threads:[~2011-05-17 20:27 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 [this message]
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
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=1305664052.12150.43.camel@sasha \
--to=levinsasha928@gmail.com \
--cc=asias.hejun@gmail.com \
--cc=gorcunov@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.