public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Sasha Levin <levinsasha928@gmail.com>
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 21:20:52 +0200	[thread overview]
Message-ID: <20110517192052.GD29574@elte.hu> (raw)
In-Reply-To: <1305659307.12150.37.camel@sasha>


* Sasha Levin <levinsasha928@gmail.com> wrote:

> On Tue, 2011-05-17 at 20:40 +0200, Ingo Molnar wrote:
> > * Sasha Levin <levinsasha928@gmail.com> wrote:
> > 
> > > 3. Within the guest, mount the fs:
> > > mount -t 9p -otrans=virtio kvm_9p <local_dir> -oversion=9p2000
> > > This will mount the 9p server to local_dir.
> > 
> > Really cool!
> 
> Thanks!
> 
> > is root-9p possible? I.e. ideally i'd like to have no image at all - just a 
> > guest kernel and a directory hierarchy for the guest filesystem.
> 
> >From what I can tell, not currently.
> 
> '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.

This needs guest kernel support, in form of a small amount of 9p specific 
mounting glue code that the guest kernel will run if either a .config option is 
set or a boot commandline is specified.

Such a thing already exists for another networked filesystem: NFS, so i would 
suggest looking at the CONFIG_ROOT_NFS=y glue in Linux, i think 9p mounting 
support would be welcome!

Thanks,

	Ingo

  reply	other threads:[~2011-05-17 19:20 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 [this message]
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
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=20110517192052.GD29574@elte.hu \
    --to=mingo@elte.hu \
    --cc=asias.hejun@gmail.com \
    --cc=gorcunov@gmail.com \
    --cc=kvm@vger.kernel.org \
    --cc=levinsasha928@gmail.com \
    --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