qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Mateusz Loskot <mateusz@loskot.net>
To: Michal Suchanek <hramrach@centrum.cz>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Linux as VirtualBox quest OS with QEMU running Solaris
Date: Mon, 10 Jan 2011 11:17:39 +0000	[thread overview]
Message-ID: <4D2AEAD3.7050107@loskot.net> (raw)
In-Reply-To: <AANLkTinxbpoh3UVotjd8NbUHR56+Gk_hmANeFqAvW5Fa@mail.gmail.com>

On 07/01/11 17:36, Michal Suchanek wrote:
> On 7 January 2011 18:28, Mateusz Loskot<mateusz@loskot.net>  wrote:
>> Hi,
>>
>> First, I'm sorry if my question does not belong here. The qemu-devel
>> says it's "devel", but I can't find any qemu-users mailing list.
>
> I have seen it once but could not find it either when searching for a
> qemu mailing list to subscribe to.


I see.

>> I have found the "QEMU on Winows" [1] but I'm not sure if this is an
>> official project and if it's "production ready".
>> I need to have fairly stable environment for building and
>> testing software on SPARC architecture.
>
>
> If you can find a build of recent qemu for Windows it should preform
> as well as qemu on Linux for emulating a SPARC (= different
> architecture).

I will try to find or build it.

> Adding another layer of virtualization is going to hurt performance at
> least and could potentially introduce additional issues.

Yes, that's what I am worried about.

> However, the device emulation is different on Windows compared to
> Linux so you may find that networking and screen emulation works
> differently compared to Linux.

I see. Actually, I do not need to access Solaris with any GUI, text mode 
will do well.


Thanks for the hints.

Best regards,
-- 
Mateusz Loskot, http://mateusz.loskot.net
Charter Member of OSGeo, http://osgeo.org
Member of ACCU, http://accu.org

  reply	other threads:[~2011-01-10 11:14 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-07 17:28 [Qemu-devel] Linux as VirtualBox quest OS with QEMU running Solaris Mateusz Loskot
2011-01-07 17:36 ` Michal Suchanek
2011-01-10 11:17   ` Mateusz Loskot [this message]
2011-01-07 18:15 ` Stefan Weil
2011-01-10 11:19   ` Mateusz Loskot
2011-01-10 17:08     ` Stefan Weil
2011-01-10 17:59       ` Mateusz Loskot
2011-01-10 21:04         ` Artyom Tarasenko
2011-01-12 11:47           ` Mateusz Loskot
2011-01-12 11:57             ` Artyom Tarasenko
2011-01-12 12:32               ` Mateusz Loskot
2011-01-12 14:28                 ` Mateusz Loskot
2011-01-12 14:40                   ` Artyom Tarasenko
2011-01-12 15:21                     ` Mateusz Loskot
2011-01-12 16:48                       ` Michal Suchanek
2011-01-12 17:15                         ` Mateusz Loskot
2011-01-12 19:00                           ` Blue Swirl
2011-01-12 23:34                           ` Mateusz Loskot
2011-01-13 10:13                             ` Michal Suchanek
2011-01-13 12:40                               ` Mateusz Loskot
2011-01-13 16:01                                 ` Mateusz Loskot
2011-01-10 22:18         ` Stefan Weil
2011-01-12 11:38           ` Mateusz Loskot
2011-01-12 12:30             ` Mateusz Loskot
2011-01-12 19:05               ` Stefan Weil
2011-01-12 19:17                 ` Stefan Weil
2011-01-12 21:37                   ` Michal Suchanek
2011-01-12 21:46                     ` Stefan Weil
2011-01-07 20:37 ` Blue Swirl
2011-01-10 11:22   ` Mateusz Loskot
2011-01-13 15:32 ` [Qemu-devel] " Mateusz Loskot

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=4D2AEAD3.7050107@loskot.net \
    --to=mateusz@loskot.net \
    --cc=hramrach@centrum.cz \
    --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).