All of lore.kernel.org
 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: Wed, 12 Jan 2011 23:34:04 +0000	[thread overview]
Message-ID: <4D2E3A6C.5060809@loskot.net> (raw)
In-Reply-To: <4D2DE1BE.7040701@loskot.net>

On 12/01/11 17:15, Mateusz Loskot wrote:
> On 12/01/11 16:48, Michal Suchanek wrote:
>> On 12 January 2011 16:21, Mateusz Loskot<mateusz@loskot.net>  wrote:
>>>
>>> Thinking of future, could anyone estimate when it will be possible to
>>> boot Solaris 10 installation from ISO disks, if at all?
>>> To summary, what OS alternative for SPARC we have got apart from Debian
>>> which are known to work under QEMU? *BSD systems?
>>>
>>
>> I can run NetBSD sparc install CD just fine.
>>
>> It supports sparc32 in the latest release.
> 
> Thanks. Great, I'll try.
> 
> One of the problems I found with Debian Etch is the package repositories
> are no longer supported and the installer
> can easily mess with those for Lenny.
> The only solution is to have all CDs for Etch available and run complete
> offline installation.
> 
> I guess the NetBSD option is more up to date here.

I have tried the recent NetBSD and it boots without problems,
however I can't configure networking to install via FTP/HTTP.
Strangely, I don't get question about DHCP.

I think it's unrelated to SPARC support discussed in this thread,
so I posted my full story to the QEMU forum:

http://qemu-forum.ipi.fi/viewtopic.php?f=14&t=5949

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

  parent reply	other threads:[~2011-01-12 23:34 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
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 [this message]
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=4D2E3A6C.5060809@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 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.