9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: "Catalin(ux aka Dino) BOIE" <util@deuroconsult.ro>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] Emulating plan9 in bochs, vmware, qemu fails (fwd)
Date: Fri, 28 Jan 2005 15:11:01 +0200	[thread overview]
Message-ID: <Pine.LNX.4.62.0501281510110.3893@webhosting.rdsbv.ro> (raw)
In-Reply-To: <006c01c5053a$5a3434a0$0200000a@urjc1>

[-- Attachment #1: Type: TEXT/PLAIN, Size: 881 bytes --]

On Fri, 28 Jan 2005, Gorka Guardiola Múzquiz wrote:

> http://www.cs.bell-labs.com/wiki/plan9/vmware4/index.html

Thanks!
On vmware I removed cdrom support and seems that is working (still 80% 
host cpu eat).

But what about qemu & bochs?
I don't really like vmware...

> ----- Original Message ----- From: "Catalin(ux aka Dino) BOIE" 
> <util@deuroconsult.ro>
> To: <9fans@cse.psu.edu>
> Sent: Friday, January 28, 2005 1:51 PM
> Subject: [9fans] Emulating plan9 in bochs, vmware, qemu fails (fwd)
>
>
>> Hello!
>> 
>> I tried hard to run plan9 in a lot of virtual machines and every time it 
>> fails. After detecting hard disks/cdrom, the host CPU goest to 99% and 
>> stays there. It is a known bug? Any workaround?
>> What options to remove from kernel?
>> 
>> 
>

---
Catalin(ux aka Dino) BOIE
catab at deuroconsult.ro
http://kernel.umbrella.ro/

  reply	other threads:[~2005-01-28 13:11 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-28 12:51 Catalin(ux aka Dino) BOIE
2005-01-28 13:07 ` Gorka Guardiola Múzquiz
2005-01-28 13:11   ` Catalin(ux aka Dino) BOIE [this message]
2005-01-28 13:53     ` Tiit Lankots
2005-01-28 14:02       ` Catalin(ux aka Dino) BOIE
2005-01-28 14:06         ` Tiit Lankots
2005-01-28 15:06         ` Russ Cox
2005-01-31 12:27           ` Catalin(ux aka Dino) BOIE

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=Pine.LNX.4.62.0501281510110.3893@webhosting.rdsbv.ro \
    --to=util@deuroconsult.ro \
    --cc=9fans@cse.psu.edu \
    /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).