From: Mateusz Loskot <mateusz@loskot.net>
To: Stefan Weil <weil@mail.berlios.de>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Linux as VirtualBox quest OS with QEMU running Solaris
Date: Mon, 10 Jan 2011 11:19:40 +0000 [thread overview]
Message-ID: <4D2AEB4C.90903@loskot.net> (raw)
In-Reply-To: <4D275849.8010205@mail.berlios.de>
On 07/01/11 18:15, Stefan Weil wrote:
> Am 07.01.2011 18:28, schrieb Mateusz Loskot:
>> 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 no experience with QEMU. I've been using x86-only virtualization
>> software like VirtualBox, VMWare and others.
>>
>> I need to run Solaris (SPARC) OS and I'd like to do it under QEMU.
>> Due to hardware constraints, I'm wondering if the following setup
>> would work at all:
>>
>> 1. Quad-core workstation with 16GB RAM with Windows Vista 64-bit
>> as host OS
>> 2. The Windows runs VirtualBox with Linux installed as guest OS.
>> 3. The Linux guest OS runs QEMU
>> 4. QEMU runs Solaris (SPARC)
>>
>> The Linux guest OS can be either Linux x86-32 or x86-64,
>> depending which one is recommended and would perform better.
>>
>> Is this configuration reasonable?
>> Would it work well?
>>
>> 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.
>>
>> [1] http://www.h7.dion.ne.jp/~qemu-win/
>>
>> I'd appreciate any help and sugestions.
>
>
> Using a native windows version of qemu would be more reasonable.
OK, makes sense to me.
> There are no precompiled windows binaries of current qemu,
> so you will have to compile them yourself (which is not difficult
> once you have the correct mingw environment).
Great. I think I should be able to do that.
Which version of QEMU source code should I grab?
Latest stable or development version from Git repo?
Best regards,
--
Mateusz Loskot, http://mateusz.loskot.net
Charter Member of OSGeo, http://osgeo.org
Member of ACCU, http://accu.org
next prev parent reply other threads:[~2011-01-10 11:16 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
2011-01-07 18:15 ` Stefan Weil
2011-01-10 11:19 ` Mateusz Loskot [this message]
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=4D2AEB4C.90903@loskot.net \
--to=mateusz@loskot.net \
--cc=qemu-devel@nongnu.org \
--cc=weil@mail.berlios.de \
/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.