From: Programmingkid <programmingkidx@gmail.com>
To: "Daniel P. Berrange" <berrange@redhat.com>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
Eric Blake <eblake@redhat.com>,
Peter Maydell <peter.maydell@linaro.org>,
qemu-devel qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] Adding Save States menu items
Date: Fri, 7 Oct 2016 10:39:30 -0400 [thread overview]
Message-ID: <38DD30EC-49B5-46B8-8524-67B6DD1EF7C0@gmail.com> (raw)
In-Reply-To: <20161007091404.GD26332@redhat.com>
On Oct 7, 2016, at 5:14 AM, Daniel P. Berrange wrote:
> On Fri, Oct 07, 2016 at 09:21:36AM +0200, Paolo Bonzini wrote:
>>
>>
>> On 06/10/2016 22:26, Eric Blake wrote:
>>>>> Doesn't virt-manager already do this? What do we gain by duplicating
>>>>> GUI functionality at this level that is already implemented at higher
>>>>> levels? Not that I'm opposed to the idea, but having a solid reason why
>>>>> it is useful is important.
>>>>
>>>> Virt-manager is a Linux exclusive. This program doesn't run on Windows or
>>>> Mac OS.
>>>
>>> Not true. I've seen it ported to Windows, and I'm sure Cole would
>>> welcome a port to Mac.
>>
>> I don't think that included a port of libvirtd, so you'd still need a
>> Linux system to run the VMs on.
>
> I would expect libvirtd to pretty much "just work" for the most part.
> Any part of libvirt which depends on Linux specific APIs has conditional
> compilation, or portability layers. OS-X is BSD underneath so majority
> of functionality will trivially work - unlike windows where making libvirtd
> work is very hard due to missing fork/exec paradigm. There's likely to be
> gremlins hiding in the libvirt QEMU driver just because 99% of all work is
> done in Linux, but we'd be more than happy with patches to fix any OS-X
> portability problems.
I have actually tried to port Virt-manager and libvirt to Mac OS X. It does
anything but work. Sorry to have to say this but it was a nightmare trying
to make Virt-manager run. The number of dependencies involved makes installing
QEMU from scratch look easy. Virt-manager is a long ways off from running in
Mac OS X.
next prev parent reply other threads:[~2016-10-07 14:39 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-06 14:22 [Qemu-devel] Adding Save States menu items Programmingkid
2016-10-06 14:28 ` Peter Maydell
2016-10-06 14:42 ` Programmingkid
2016-10-06 15:35 ` Paolo Bonzini
2016-10-06 15:48 ` Programmingkid
2016-10-06 15:49 ` Paolo Bonzini
2016-10-06 16:04 ` Programmingkid
2016-10-06 16:17 ` Paolo Bonzini
2016-10-06 17:43 ` Programmingkid
2016-10-06 17:49 ` Peter Maydell
2016-10-06 17:51 ` Programmingkid
2016-10-06 20:03 ` Eric Blake
2016-10-06 19:59 ` Eric Blake
2016-10-06 20:10 ` Programmingkid
2016-10-06 20:26 ` Eric Blake
2016-10-07 7:21 ` Paolo Bonzini
2016-10-07 9:14 ` Daniel P. Berrange
2016-10-07 14:39 ` Programmingkid [this message]
2016-10-06 20:47 ` Peter Maydell
2016-10-06 21:07 ` Programmingkid
2016-10-07 8:46 ` Kevin Wolf
2016-10-07 9:09 ` Daniel P. Berrange
2016-10-07 14:55 ` Programmingkid
2016-10-07 14:57 ` Daniel P. Berrange
2016-10-07 14:59 ` Peter Maydell
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=38DD30EC-49B5-46B8-8524-67B6DD1EF7C0@gmail.com \
--to=programmingkidx@gmail.com \
--cc=berrange@redhat.com \
--cc=eblake@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--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).