All of lore.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
To: sol10x86-j9pdmedNgrk@public.gmane.org
Cc: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org,
	qemu-devel-qX2TKyscuCcdnm+yROfE0A@public.gmane.org
Subject: Re: [Qemu-devel] Making qemu images executable (and store command line arguments in them =P)
Date: Fri, 17 Aug 2007 15:40:58 +0300	[thread overview]
Message-ID: <46C5975A.6070906@qumranet.com> (raw)
In-Reply-To: <21867471.1187283941478.JavaMail.root-Fl5e2thpha4zbC/FaE+QG4/aXZnnTYK5@public.gmane.org>

Ben Taylor wrote:
> ---- "Jorge Lucángeli Obes" <t4m5yn@gmail.com> wrote: 
>   
>> I've been giving some thought to Anthony's idea:
>>
>> http://kvm.qumranet.com/kvmwiki/Specs/StoringCommandLineInImage
>>
>> However, maybe I'm just too much on vacations, but I don't seem to
>> come up with a nice way of doing this. Everything keeps coming back to
>> creating a new 'container' image format and then implementing block
>> layer functions that only add the number of sectors occupied by the
>> command-line to the read and write calls made by QEMU, and then just
>> relay those calls to the image-specific functions. That doesn't sound
>> very efficient.
>>     
>
> No, and it fundamentally breaks using a real disk with QEMU.
>
>   

Why?  It's optional.

>> The '#!' trick works nice with scripts, but I don't see it playing
>> very well with images. ¿Comments? ¿Pointers?
>>     
>
> Personally, I'm not sure why we wouldn't just write out the command line
> data to a file tied to the primary image file, with some kind of time stamp
> to correlate the data from the command line and the last updated time
> of the primary image file.  It's intuitive, and doesn't require a bucket of
> programming to make work.  The down side is if qemu crashes, the
> time stamp between the parameter file and the image file may indicate
> the potential for "difference", but this can just be a notice (just as snapshots
> used to do with the image files in 0.7.x)
>   

It's not easy to use: if you move the image, you need to move the file. 
I'd like to have exactly one entity to worry about when using a virtual
machine.

-- 
Do not meddle in the internals of kernels, for they are subtle and quick to panic.


-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/
_______________________________________________
kvm-devel mailing list
kvm-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/kvm-devel

WARNING: multiple messages have this Message-ID (diff)
From: Avi Kivity <avi@qumranet.com>
To: sol10x86@cox.net
Cc: kvm-devel@lists.sourceforge.net, qemu-devel@nongnu.org
Subject: Re: [kvm-devel] [Qemu-devel] Making qemu images executable (and store command line arguments in them =P)
Date: Fri, 17 Aug 2007 15:40:58 +0300	[thread overview]
Message-ID: <46C5975A.6070906@qumranet.com> (raw)
In-Reply-To: <21867471.1187283941478.JavaMail.root@eastrmwml26.mgt.cox.net>

Ben Taylor wrote:
> ---- "Jorge Lucángeli Obes" <t4m5yn@gmail.com> wrote: 
>   
>> I've been giving some thought to Anthony's idea:
>>
>> http://kvm.qumranet.com/kvmwiki/Specs/StoringCommandLineInImage
>>
>> However, maybe I'm just too much on vacations, but I don't seem to
>> come up with a nice way of doing this. Everything keeps coming back to
>> creating a new 'container' image format and then implementing block
>> layer functions that only add the number of sectors occupied by the
>> command-line to the read and write calls made by QEMU, and then just
>> relay those calls to the image-specific functions. That doesn't sound
>> very efficient.
>>     
>
> No, and it fundamentally breaks using a real disk with QEMU.
>
>   

Why?  It's optional.

>> The '#!' trick works nice with scripts, but I don't see it playing
>> very well with images. ¿Comments? ¿Pointers?
>>     
>
> Personally, I'm not sure why we wouldn't just write out the command line
> data to a file tied to the primary image file, with some kind of time stamp
> to correlate the data from the command line and the last updated time
> of the primary image file.  It's intuitive, and doesn't require a bucket of
> programming to make work.  The down side is if qemu crashes, the
> time stamp between the parameter file and the image file may indicate
> the potential for "difference", but this can just be a notice (just as snapshots
> used to do with the image files in 0.7.x)
>   

It's not easy to use: if you move the image, you need to move the file. 
I'd like to have exactly one entity to worry about when using a virtual
machine.

-- 
Do not meddle in the internals of kernels, for they are subtle and quick to panic.

  parent reply	other threads:[~2007-08-17 12:40 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-16 17:05 [Qemu-devel] Making qemu images executable (and store command line arguments in them =P) Ben Taylor
2007-08-16 17:05 ` Ben Taylor
     [not found] ` <21867471.1187283941478.JavaMail.root-Fl5e2thpha4zbC/FaE+QG4/aXZnnTYK5@public.gmane.org>
2007-08-16 20:36   ` Dan Shearer
2007-08-16 20:36     ` Dan Shearer
2007-08-17 12:40   ` Avi Kivity [this message]
2007-08-17 12:40     ` [kvm-devel] " Avi Kivity
2007-08-17 13:09     ` [kvm-devel] " Christian Brunschen
2007-08-17 13:09       ` [kvm-devel] [Qemu-devel] " Christian Brunschen
     [not found]       ` <5F34873A-05BE-4D91-8590-93898C7755CA-HEm3bjczhZmzQB+pC5nmwQ@public.gmane.org>
2007-08-19 10:35         ` Avi Kivity
2007-08-19 10:35           ` [kvm-devel] " Avi Kivity
2007-08-19 11:04           ` Markus Hitter
2007-08-19 11:08             ` Avi Kivity
2007-08-19 13:14               ` [kvm-devel] " Christian Brunschen
2007-08-19 13:14                 ` [kvm-devel] [Qemu-devel] " Christian Brunschen
  -- strict thread matches above, loose matches on Subject: below --
2007-08-15 22:52 Jorge Lucángeli Obes
     [not found] ` <59abf66e0708151552r6192f7e1he7ebe5bffd49525f-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2007-08-15 23:52   ` Mark Williamson
2007-08-15 23:52     ` Mark Williamson
     [not found]     ` <200708160052.51858.mark.williamson-kDbDZe0LBGWFxr2TtlUqVg@public.gmane.org>
2007-08-16 16:11       ` Andreas Färber
2007-08-16 16:11         ` Andreas Färber

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=46C5975A.6070906@qumranet.com \
    --to=avi-atkuwr5tajbwk0htik3j/w@public.gmane.org \
    --cc=kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
    --cc=qemu-devel-qX2TKyscuCcdnm+yROfE0A@public.gmane.org \
    --cc=sol10x86-j9pdmedNgrk@public.gmane.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 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.