[Date Prev][Date Next] [Thread Prev][Thread Next]
[Thread Index]
[Date Index]
[Author Index]
RE: OT: vmware over Linux question
- From: "Mark W. Knecht" <mknecht controlnet com>
- To: <redhat-install-list redhat com>
- Subject: RE: OT: vmware over Linux question
- Date: Thu, 6 Jun 2002 13:10:45 -0700
Rick,
Yes, you're right and I understand that. My hope would be that I could
configure vmware so that a specific OS has unlimited use of a piece of
hardware, and then either not tell the others that it's there at all, or
tell them not to do anything with the card. Since this is a PCI card, if I
load not Linux driver then Linux doesn't need to know anything other than
what's required to set up the PCI addressing of the card. I'm not familiar
with this part of Linux, but under Windows I can just let BIOS do that and
not have Windows mess with it, or the interrupt routings at all.
Obviously, responding to interrupts from this card would be an interesting
issue, because vmware would have to take the interrupt and then decide that
it belongs to my specific guest OS, but I presume that it knows how to do
that today.
This sort of comes down to the idea of installing multiple sound cards in
the same system, and then giving a different sound card to different
applications, or in this case, different OS's.
Anyway, I'll try to get a note off to vmware today and see what I can learn.
Thanks for your help.
Mark
-----Original Message-----
From: redhat-install-list-admin redhat com
[mailto:redhat-install-list-admin redhat com]On Behalf Of Rick Stevens
Sent: Thursday, June 06, 2002 11:19 AM
To: redhat-install-list redhat com
Subject: Re: OT: vmware over Linux question
Mark W. Knecht wrote:
> Rick,
> Cool, I'll give them a ring.
>
> My hope was that vmware might allow a piece of hardware NOT seen by
Linux
> to be accessed by the guest OS. I only want a single guest OS to talk to
it,
> so there really shouldn't be any arbitration from the Linux point of view.
> Clearly different than a keyboard or a disk.
Well, yeah, but remember that each of those guest OSes think they have
the system all to themselves. SOMEONE has to keep them from fighting
over hardware resources regardless of what those resources are.
That's the host OS's job.
----------------------------------------------------------------------
- Rick Stevens, SSE, VitalStream, Inc. rstevens vitalstream com -
- 949-743-2010 (Voice) http://www.vitalstream.com -
- -
- To understand recursion, you must first understand recursion. -
----------------------------------------------------------------------
_______________________________________________
Redhat-install-list mailing list
Redhat-install-list redhat com
https://listman.redhat.com/mailman/listinfo/redhat-install-list
[Date Prev][Date Next] [Thread Prev][Thread Next]
[Thread Index]
[Date Index]
[Author Index]