From: "Daniel P. Berrange" <berrange@redhat.com>
To: joelee724@gmail.com, qemu-devel@nongnu.org
Cc: Paul Brook <paul@codesourcery.com>
Subject: Re: [Qemu-devel] VMware Player
Date: Wed, 14 Jun 2006 17:21:15 +0100 [thread overview]
Message-ID: <20060614162115.GC20393@redhat.com> (raw)
In-Reply-To: <4490357B.5040505@gmail.com>
On Wed, Jun 14, 2006 at 12:12:43PM -0400, Joe Lee wrote:
> You are right, and the idea is that the person have full interaction
> with the application environment including the underlying LAMP/WAMP
> stack that has been packaged. Users that want to quickly run and
> test-drive the appliance may not really need a full VM type application.
> Just something that could quickly run the image (appliance).
An VMWare player "appliance" is really just a disk image & config file.
Running a disk image in QEMU is just a matter of executing
qemu -hda /path/to/image
Perhaps adding "-m XXX" to set increased RAM.
This is no harder to do than using VMWare player
vmplayer /path/to/appliance
Since QEMU already understands VMWare disk images, there's even a good
chance that QEMU can run a VMWare "appliance" image itself. So it looks
to me that QEMU is already on a par with VMWare player in terms of being
able to quickly & simply test 'appliance' images.
Dan.
>
> Joe
>
> Paul Brook wrote:
> >On Wednesday 14 June 2006 16:53, Joe Lee wrote:
> >
> >>>Why on earth would we want to make a crippled version of qemu?
> >>>
> >>>AFAIK "Creating" a VMware virtual machine is just making a config file.
> >>>qemu doesn't have config files, so your question makes no sense.
> >>>
> >>Well, I was not thinking or suggesting of a crippled qemu version. I
> >>asked the question because there are some software
> >>appliances which are pre-built and pre-configured apps that are built on
> >>a LAMP stack and packaged as a single image
> >>type file. This image file can be downloaded and run on a product
> >>similar to VMware Player. This is used for quick demo
> >>purposes of an application with out the need to have a full virtual
> >>machine.
> >>
> >
> >My impression was that these "appliances" are full virtual machines. It's
> >just an OS install that's been stripped down and configured to run a
> >single application on startup.
> >
> >Paul
> >
> >
>
>
> _______________________________________________
> Qemu-devel mailing list
> Qemu-devel@nongnu.org
> http://lists.nongnu.org/mailman/listinfo/qemu-devel
--
|=- Red Hat, Engineering, Emerging Technologies, Boston. +1 978 392 2496 -=|
|=- Perl modules: http://search.cpan.org/~danberr/ -=|
|=- Projects: http://freshmeat.net/~danielpb/ -=|
|=- GnuPG: 7D3B9505 F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 -=|
next prev parent reply other threads:[~2006-06-14 16:23 UTC|newest]
Thread overview: 63+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-14 14:55 [Qemu-devel] VMware Player Joe Lee
2006-06-14 15:01 ` Paul Brook
2006-06-14 15:53 ` Joe Lee
2006-06-14 16:02 ` Paul Brook
2006-06-14 16:12 ` Joe Lee
2006-06-14 16:21 ` Daniel P. Berrange [this message]
2006-06-14 16:39 ` Jan Marten Simons
2006-06-14 17:42 ` Joe Lee
2006-06-14 16:10 ` Oliver Gerlich
2006-06-15 7:47 ` kadil
2006-06-15 13:18 ` WaxDragon
2006-06-15 13:43 ` Julian Seward
2006-06-15 13:50 ` Johannes Schindelin
2006-06-15 16:55 ` [Qemu-devel] " Ben Pfaff
2006-06-15 19:21 ` Joe Lee
2006-06-15 19:33 ` WaxDragon
2006-06-15 19:44 ` Joe Lee
2006-06-16 10:51 ` Jan Marten Simons
2006-06-16 11:01 ` Jan Marten Simons
2006-06-15 14:18 ` [Qemu-devel] " Joe Lee
2006-06-15 14:43 ` Johannes Schindelin
2006-06-15 19:42 ` Joe Lee
2006-06-15 20:55 ` Johannes Schindelin
2006-06-15 21:04 ` Joe Lee
2006-06-15 20:34 ` Joe Lee
2006-06-15 20:56 ` Johannes Schindelin
2006-06-15 21:03 ` Joe Lee
2006-06-16 3:39 ` Rick Vernam
2006-06-16 4:31 ` Joe Lee
2006-06-16 5:20 ` Rick Vernam
2006-06-15 22:29 ` Oliver Gerlich
2006-06-15 22:52 ` [Qemu-devel] Doing a Tcl/Tk based frontend John Morris
2006-06-15 23:23 ` Daniel P. Berrange
2006-06-15 23:33 ` Oliver Gerlich
2006-06-15 23:41 ` Anthony Liguori
2006-06-15 23:56 ` Daniel P. Berrange
2006-06-16 0:01 ` Anthony Liguori
2006-06-15 23:38 ` Anthony Liguori
2006-06-15 23:03 ` [Qemu-devel] VMware Player Johannes Schindelin
2006-06-15 23:38 ` Oliver Gerlich
2006-06-16 9:34 ` kadil
2006-06-15 15:25 ` Oliver Gerlich
2006-06-15 21:17 ` John Morris
2006-06-16 6:51 ` Tim Walker
2006-06-16 7:21 ` Kevin F. Quinn
2006-06-16 12:45 ` Stuart Brady
2006-06-16 15:02 ` Kevin F. Quinn
2006-06-16 15:07 ` Christian MICHON
2006-06-16 15:35 ` Oliver Gerlich
2006-06-16 17:18 ` Kevin F. Quinn
2006-06-17 16:06 ` [Qemu-devel] GUI for QEmu (ex "VMware Player" topic) NyOS
2006-06-16 14:18 ` [Qemu-devel] VMware Player Joe Lee
2006-06-16 14:26 ` Johannes Schindelin
2006-06-14 16:22 ` Jan Marten Simons
2006-06-14 17:15 ` Mattia Gentilini
2006-06-14 16:27 ` Larry Brigman
-- strict thread matches above, loose matches on Subject: below --
2006-06-17 15:46 Mattia Gentilini (QD)
2006-06-17 6:15 Mattia Gentilini (QD)
2006-06-17 7:25 ` Tim Walker
2005-10-21 19:29 [Qemu-devel] VMWare player John R. Hogerhuis
2005-10-21 20:22 ` Mike Swanson
2005-10-21 21:37 ` John R. Hogerhuis
2005-10-22 14:34 ` Jim C. Brown
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=20060614162115.GC20393@redhat.com \
--to=berrange@redhat.com \
--cc=joelee724@gmail.com \
--cc=paul@codesourcery.com \
--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 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.