On 05/18/2011 02:05 AM, Sasha Levin wrote:
On Tue, 2011-05-17 at 20:18 -0500, Eric Van Hensbergen wrote:
On Tue, May 17, 2011 at 3:27 PM, Sasha Levinlevinsasha...@gmail.com wrote:
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
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
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
On Thu, 2011-05-26 at 08:22 -0700, Venkateswararao Jujjuri wrote:
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
On 05/18/2011 02:05 AM, Sasha Levin wrote:
On Tue, 2011-05-17 at 20:18 -0500, Eric Van Hensbergen wrote:
On Tue, May 17, 2011 at 3:27 PM, Sasha Levinlevinsasha...@gmail.com wrote:
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
On Tue, May 17, 2011 at 9:35 PM, Sasha Levin levinsasha...@gmail.com wrote:
Overview:
9p allows for simple RPC based resource sharing over
different transports (in our case, virtio).
This is the implementation of (most of) the original
9p2000 protocol, without the .u or the .l extensions.
* Eric Van Hensbergen eri...@gmail.com wrote:
- Update atime/mtime in p9_wstat, not really needed.
The underlying storage may handle this for you, I think 9p avoids
updating atime by default, at least in caching scenarios -- too much
unnecessary protocol traffic.
Yeah, atime is
On Wed, 2011-05-18 at 09:38 +0300, Pekka Enberg wrote:
On Tue, May 17, 2011 at 9:35 PM, Sasha Levin levinsasha...@gmail.com wrote:
Overview:
9p allows for simple RPC based resource sharing over
different transports (in our case, virtio).
This is the implementation of (most of) the
On Wed, May 18, 2011 at 1:35 PM, Sasha Levin levinsasha...@gmail.com wrote:
I'm not sure how to do the guest part automatically, it's just a simple
mount command - but I don't see how we can do it in a simple manner.
IIRC, Ingo suggested a kernel config option - a kernel parameter might
also
On Wed, 2011-05-18 at 13:38 +0300, Pekka Enberg wrote:
On Wed, May 18, 2011 at 1:35 PM, Sasha Levin levinsasha...@gmail.com wrote:
I'm not sure how to do the guest part automatically, it's just a simple
mount command - but I don't see how we can do it in a simple manner.
IIRC, Ingo
* Sasha Levin levinsasha...@gmail.com wrote:
On Wed, 2011-05-18 at 13:38 +0300, Pekka Enberg wrote:
On Wed, May 18, 2011 at 1:35 PM, Sasha Levin levinsasha...@gmail.com
wrote:
I'm not sure how to do the guest part automatically, it's just a simple
mount command - but I don't see how
On Tue, 2011-05-17 at 23:27 +0300, Sasha Levin wrote:
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
* Sasha Levin levinsasha...@gmail.com wrote:
When trying to boot a distribution rootfs we get a lot of symbolic link and
file locking errors, since neither of those is supported by legacy 9p2000 -
thats understandable. It just prevents from almost anything more complicated
than simple
Overview:
9p allows for simple RPC based resource sharing over
different transports (in our case, virtio).
This is the implementation of (most of) the original
9p2000 protocol, without the .u or the .l extensions.
How to use:
1. Make sure kernel is compiled with:
CONFIG_NET_9P=y
* Sasha Levin levinsasha...@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!
Still todo (but can live without):
- Multiple virtio-9p devices.
- Ugly hack in
On Tue, 2011-05-17 at 20:40 +0200, Ingo Molnar wrote:
* Sasha Levin levinsasha...@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?
* Sasha Levin levinsasha...@gmail.com wrote:
On Tue, 2011-05-17 at 20:40 +0200, Ingo Molnar wrote:
* Sasha Levin levinsasha...@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
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
On Tue, May 17, 2011 at 3:27 PM, Sasha Levin levinsasha...@gmail.com wrote:
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
19 matches
Mail list logo
