From: Mike Swanson <mikeonthecomputer@gmail.com>
To: jhoger@pobox.com, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] VMWare player
Date: Fri, 21 Oct 2005 13:22:50 -0700 [thread overview]
Message-ID: <79bf98480510211322pf2c5fe9n70b8822a4fb91054@mail.gmail.com> (raw)
In-Reply-To: <1129922985.6570.51.camel@aragorn>
Yeah, it barely on topic. But the .vmx files are extremely simple text
files, and qemu-img creates vmdk disk images. Yes, it's possible to
install operating systems solely withing VMware (this is the correct
spelling, btw) Player, but you cannot install VMware Tools, even with
the appropriate (windows|linux|freebsd|netware).iso file.
On 10/21/05, John R. Hogerhuis <jhoger@pobox.com> wrote:
> Barely on-topic, but since VmWare interop crops up from time to time:
>
> http://www.vmware.com/products/player/
>
> I doubt this is targeted at QEMU, but rather at competing with Microsoft
> and VirtualPC. That or they are leaving the low-end market for server
> consolidation.
>
> This may in fact be as much VmWare as most people would need. Countdown
> has started for the first person to create a system image solely from
> freeware "VmWare Player" ;-)
>
> -- John.
--
Mike
next prev parent reply other threads:[~2005-10-21 20:23 UTC|newest]
Thread overview: 58+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-21 19:29 [Qemu-devel] VMWare player John R. Hogerhuis
2005-10-21 20:22 ` Mike Swanson [this message]
2005-10-21 21:37 ` John R. Hogerhuis
2005-10-22 10:48 ` [Qemu-devel] " Stefano Marinelli
2005-10-22 21:46 ` John R. Hogerhuis
2005-10-22 21:58 ` Johannes Schindelin
2005-10-23 4:05 ` John R. Hogerhuis
2005-11-10 2:14 ` John Wells
2005-11-10 2:18 ` Mike Swanson
2005-11-10 7:34 ` Christian MICHON
2005-11-10 13:20 ` Nis Jorgensen
2005-10-28 22:10 ` Henning Sprang
2005-10-22 14:34 ` [Qemu-devel] " Jim C. Brown
-- strict thread matches above, loose matches on Subject: below --
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
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 14:18 ` 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 23:03 ` 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-16 14:18 ` 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
2006-06-17 6:15 Mattia Gentilini (QD)
2006-06-17 7:25 ` Tim Walker
2006-06-17 15:46 Mattia Gentilini (QD)
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=79bf98480510211322pf2c5fe9n70b8822a4fb91054@mail.gmail.com \
--to=mikeonthecomputer@gmail.com \
--cc=jhoger@pobox.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 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).