On 08/03/2010 08:00 PM, Richard W.M. Jones wrote:
On Tue, Aug 03, 2010 at 07:48:17PM +0300, Avi Kivity wrote:
On 08/03/2010 07:44 PM, Avi Kivity wrote:
It's not a good path to follow. Tomorrow we'll need to load 300MB
initrds and we'll have to rework this yet again. Meanwhile the
kernel and virtio support demand loading of any image size you'd
want to use.
Even better would be to use virtio-9p. You don't even need an image
in this case.
We don't want to expose the whole host filesystem, just selected
files, and we want to use our own configuration files (basically
that's what is in the skeleton part that we do ship).
True. The guest might landmine its disks with something that the
libguestfs kernel would step on an be exploited.
You might hardlink the needed files into a private directory tree.
Of course, if we can use virtio-9p, then excellent. Is there good
documentation about virtio-9p? What I can find is fragmentary or
based on reading qemu -help ...
Not to my knowledge.
--
error compiling committee.c: too many arguments to function
