public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Eric Blake <eblake@redhat.com>
To: cygwin@cygwin.com
Subject: Re: Last Version of Cygwin for XP
Date: Mon, 15 Feb 2016 14:53:00 -0000	[thread overview]
Message-ID: <56C1E676.20808@redhat.com> (raw)
In-Reply-To: <CACoZoo2Pr1+_0mnrQdjf6jADRwo8RYCysv8nLnZBiK-wxMCqEg@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 820 bytes --]

On 02/13/2016 05:41 PM, Erik Soderquist wrote:
> 
> Yes, I have, two of them fail entirely to start, and the third starts,
> but crashes quickly.  As each also has its own hardware drivers, I
> suspect it would be harder getting it to work in Wine than writing
> fresh.  They are currenty in VMware Player because they do not work
> correctly in VirtualBox either.  (I wanted the VM to be open source as
> well, but no such luck).  If anyone has suggestions on other open
> source virtual environments, I'm willing to try so I can eliminate
> VMware.  (Long term goal is 100% open source).

qemu-kvm works just fine at running Windows guests.  It's what I use for
maintaining my Cygwin packages.

-- 
Eric Blake   eblake redhat com    +1-919-301-3266
Libvirt virtualization library http://libvirt.org


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 604 bytes --]

  reply	other threads:[~2016-02-15 14:53 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-10  1:37 Jonathan Brenster
2016-02-10  2:17 ` Yaakov Selkowitz
2016-02-10 17:14   ` LMH
2016-02-10 17:24     ` Yaakov Selkowitz
2016-02-11 18:09       ` cyg Simple
2016-02-12 19:20         ` Warren Young
2016-02-12 21:58           ` Erik Soderquist
2016-02-12 22:42             ` Warren Young
2016-02-13  0:37               ` Erik Soderquist
2016-02-13 17:41                 ` Tony Kelman
2016-02-14  0:41                   ` Erik Soderquist
2016-02-15 14:53                     ` Eric Blake [this message]
2016-02-13 17:20             ` Corinna Vinschen
2016-02-10  2:20 ` Andrey Repin

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=56C1E676.20808@redhat.com \
    --to=eblake@redhat.com \
    --cc=cygwin@cygwin.com \
    /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 read-only IMAP folder(s) and NNTP newsgroup(s).