From: "Andreas Färber" <andreas.faerber@web.de>
To: lee.essen@me.com
Cc: stefanha@gmail.com, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Illumos/SmarOS support
Date: Thu, 15 Mar 2012 14:12:34 +0100 [thread overview]
Message-ID: <4F61EAC2.3030004@web.de> (raw)
In-Reply-To: <7ab5e7ea-4f3c-cf51-f550-d1b511424550@me.com>
Something went wrong with your reply... While it contains a quote it
does not reference the mail you replied to, that way messages get lost
among the constant chatter on qemu-devel.
Am 15.03.2012 13:39, schrieb lee.essen@me.com:
> On 15/03/2012 11:56, Stefan Hajnoczi wrote:
>>> Anyway, couple of questions…
>>>
>>> 1. Are you happy to accept patches that enable this?
>>> - There are a few build related things that don't work … assumption of sh
>>> being bash, missing -64 argument to dtrace etc.
>> Sounds good, but have you checked the Joyent qemu-kvm Illumos port to
>> see what fixes they already have?
>>
>> https://github.com/joyent/illumos-kvm-cmd
>
> Yes, they have solved the same problems .. however the build mechanism
> seems to be sufficiently different that things need to be done slightly
> differently for qemu.git.
>
> These aren't complex changes and amount to generally only a couple of lines.
>
> The illumos-kvm-cmd tree seems to be only updated to address joyent
> live-image build requirements, and hasn't really moved in about 7
> months. I've been posting profusely on the smartos mailing list and they
> also don't seem that concerned about this work.
At FOSDEM, I talked to a Bryant from illumos who wanted to forward my
business card to their KVM/QEMU guys re upstreaming, but I haven't heard
back from anyone so far.
> So for each binary created you need to do something like...
>
> dtrace -o <binary>-dtrace.o -G -s <dtrace-source>
> <all-the-objects-used-by-the-binary>
>
> ... then include the specific <binary>-drace.o when linking the main
> binary.
Same as on Solaris 10. There was some alternative trick to "glom"
objects together to avoid linking in that extra object, don't remember
exactly. Hopefully there's an archive of the old Sun blogs somewhere.
Concerning KVM, there was some resentment on the Red Hat side againt the
SmartOS KVM port due to the legal issue of whether GPL'ed KVM may be
combined with CDDL. But that is independent of currently broken QEMU
host support in userland.
Andreas
next prev parent reply other threads:[~2012-03-15 13:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-15 12:39 [Qemu-devel] Illumos/SmarOS support lee.essen
2012-03-15 12:57 ` Stefan Hajnoczi
2012-03-15 13:12 ` Andreas Färber [this message]
2012-03-15 15:48 ` Lee Essen
2012-03-15 15:59 ` Andreas Färber
-- strict thread matches above, loose matches on Subject: below --
2012-03-15 11:19 Lee Essen
2012-03-15 11:56 ` Stefan Hajnoczi
2012-03-15 12:23 ` 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=4F61EAC2.3030004@web.de \
--to=andreas.faerber@web.de \
--cc=lee.essen@me.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@gmail.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 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.