qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Jim C. Brown" <jbrown106@phreaker.net>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] OT: Running qemu without host os?
Date: Fri, 21 Jan 2005 23:05:45 -0500	[thread overview]
Message-ID: <20050122040545.GA4374@jbrown.mylinuxbox.org> (raw)
In-Reply-To: <Pine.GSO.4.58.0501212333150.26096@bilbo.dd.chalmers.se>

On Fri, Jan 21, 2005 at 11:45:11PM +0100, Peter Karlsson wrote:
> On Fri, 21 Jan 2005, Jim C. Brown wrote:
> 
> > What exactly do you mean by "virtualise the hardware" ?
> 
> virtual_os(hardware access) -> vm -> hardware

That would be interesting. Qemu can't do that yet (it shares hardware via
the help of the host OS, of course, but not direct access).

If you had qemu running multiple OSes, and all of them could access the same
hardware "virtually directly", that would be simply amazing. Not quite sure
how one could go about doing this though..

> 
> > No, that would be the intriquing part. (Actually, a linux host CAN give that
> > access, as long as it is a PCI card you are giving the guest access to - but
> > then only the guest can use it exclusively. Of course Qemu needs to run in X so
> > this isn't yet possible .. unless you have 2 graphics cards, one of them is
> > PCI, and the linux host is using the other graphic card.)
> 
> Would the other way around work (i.e. linux using pci gfx card and the
> guest os using agp)? Anyway that's good to know. Thanks!

No, it currently only works with PCI. ISA, AGP, USB, and traditional hardware
can't be accessed directly yet (tho it is theoreticly possible).

> 
> Best regards
> 
> Peter K
> 
> -- 
> We Can Put an End to Word Attachments:
> http://www.fsf.org/philosophy/no-word-attachments.html
> 
> 
> _______________________________________________
> Qemu-devel mailing list
> Qemu-devel@nongnu.org
> http://lists.nongnu.org/mailman/listinfo/qemu-devel
> 

-- 
Infinite complexity begets infinite beauty.
Infinite precision begets infinite perfection.

  reply	other threads:[~2005-01-22  4:28 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-21 16:10 [Qemu-devel] OT: Running qemu without host os? Peter Karlsson
2005-01-21 17:02 ` Jim C. Brown
2005-01-21 18:03   ` Peter Karlsson
2005-01-21 19:23     ` Jim C. Brown
2005-01-21 21:30       ` [Qemu-devel] " Ben Pfaff
2005-01-21 22:33         ` Karl Magdsick
2005-01-22  1:23           ` Peter Karlsson
2005-01-21 22:36         ` Jim C. Brown
2005-01-21 22:42           ` Ben Pfaff
2005-01-21 22:45       ` [Qemu-devel] " Peter Karlsson
2005-01-22  4:05         ` Jim C. Brown [this message]
2005-01-22 14:29           ` Karl Magdsick
2005-01-22 15:16             ` Paul Brook
2005-01-22 21:09             ` Peter Karlsson
2005-01-22 21:47               ` Jim C. Brown
2005-01-22 23:13                 ` Peter Karlsson
2005-01-23  1:49               ` Mark Williamson
2005-01-22 20:46           ` Peter Karlsson
2005-01-22 13:15 ` venkateshp
2005-01-22 20:56   ` Peter Karlsson
2005-02-17 11:41     ` [Qemu-devel] anybody working on smp..? venkateshp

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=20050122040545.GA4374@jbrown.mylinuxbox.org \
    --to=jbrown106@phreaker.net \
    --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).