From: "Jorge Lucángeli Obes" <t4m5yn@gmail.com>
To: Laurent Vivier <Laurent.Vivier@bull.net>
Cc: kvm-devel@lists.sourceforge.net, qemu-devel@nongnu.org
Subject: Re: [kvm-devel] [Qemu-devel] Re: Storing command line options in images
Date: Tue, 14 Aug 2007 16:02:35 -0300 [thread overview]
Message-ID: <59abf66e0708141202t4eaf009cs4596cc76a164e3de@mail.gmail.com> (raw)
In-Reply-To: <46C1BCAC.9030203@bull.net>
On 8/14/07, Laurent Vivier <Laurent.Vivier@bull.net> wrote:
> Markus Hitter wrote:
> >
> > Am 13.08.2007 um 11:19 schrieb Laurent Vivier:
> >
> >> We can modify qemu to test if the argument is a directory, if yes, it
> >> reads args
> >> from file args in this directory and for security the disk image must
> >> be in the
> >> same directory.
> >>
> >> for instance, we have:
> >>
> >> ./pc1/
> >> ./pc1/args
> >> ./pc1/my_disk
> >>
> >> and in ./pc1/args, we have "-hda my_disk"
> >
> > ... and "-hdb ../pc2/my_other_disk"
>
> If we want to preserve security we should forbid this, but you can make a soft link:
>
> ln -s shared_disks/my_disk1 pc1/my_shared_disk
> ln -s shared_disks/my_disk1 pc2/my_shared_disk
>
> and have pc1/args and pc2/args = "-hda my_disk -hdb my_shared_disk"
> to have:
>
> qemu -hda pc1/my_disk -hdb pc1/my_shared_disk
>
> qemu -hda pc2/my_disk and -hdb pc2/my_shared_disk
>
> > The directory idea sounds good. Especially for me, as I'm obviously the
> > only one running one disk image in different virtual machines.
> >
> > Plus, it'd work for physical partitions / disks: Simply have a directory
> > with an "args" file only.
> >
> >
> > my $ 0.01
> > Markus
Quoting Thiemo, this '@' thing was "a feature which is now implemented
in the GNU toolchain". That's why I tried it. Now I would like to know
what he did to get it working. It would certainly be an useful
feature, even if it does not exactly suit our purposes.
I still think that the executable-image approach could work nicely.
However, the point in favour of a configuration directory when using
physical partitions or disks is good. Nonetheless, a physical
partition is much less "volatile" than an disk image, so the
disadvantage of keeping a shell script is small in that case.
Cheers,
Jorge
next prev parent reply other threads:[~2007-08-14 19:02 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-10 4:55 [Qemu-devel] Storing command line options in images Jorge Lucángeli Obes
2007-08-10 16:02 ` [Qemu-devel] Re: [kvm-devel] " Anthony Liguori
2007-08-10 17:14 ` Avi Kivity
2007-08-10 18:43 ` [kvm-devel] [Qemu-devel] " Anthony Liguori
2007-08-10 19:41 ` Avi Kivity
2007-08-10 20:11 ` Anthony Liguori
2007-08-11 1:41 ` Jorge Lucángeli Obes
2007-08-13 8:55 ` Avi Kivity
2007-08-13 9:19 ` Laurent Vivier
2007-08-13 9:27 ` Christian MICHON
2007-08-14 14:18 ` Markus Hitter
2007-08-14 14:31 ` Laurent Vivier
2007-08-14 19:02 ` Jorge Lucángeli Obes [this message]
2007-08-14 20:07 ` Thiemo Seufer
2007-08-14 20:46 ` Christian MICHON
2007-08-13 19:39 ` Thiemo Seufer
2007-08-13 20:26 ` Christian MICHON
2007-08-13 22:21 ` Philip Boulain
2007-08-13 22:27 ` [Qemu-devel] Re: [kvm-devel] " Jernej Simončič
2007-08-13 23:31 ` [kvm-devel] [Qemu-devel] " Thiemo Seufer
2007-08-14 14:26 ` Philip Boulain
2007-08-14 3:17 ` Anthony Liguori
2007-08-14 4:39 ` Jorge Lucángeli Obes
2007-08-14 7:44 ` Kevin Wolf
2007-08-14 7:46 ` Laurent Vivier
2007-08-15 21:26 ` Segher Boessenkool
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=59abf66e0708141202t4eaf009cs4596cc76a164e3de@mail.gmail.com \
--to=t4m5yn@gmail.com \
--cc=Laurent.Vivier@bull.net \
--cc=kvm-devel@lists.sourceforge.net \
--cc=qemu-devel@nongnu.org \
/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;
as well as URLs for NNTP newsgroup(s).