Date: Mon, 3 Jan 2005 03:48:50 -0600 From: Eric Kjeldergaard <kjelderg@gmail.com> To: "ctodd@chrismiller.com" <ctodd@chrismiller.com> Cc: freebsd-questions@freebsd.org Subject: Re: write state to swap for multi-os boot Message-ID: <d9175cad05010301486588de5d@mail.gmail.com> In-Reply-To: <Pine.BSI.4.58L.0501021355260.7855@vp4.netgate.net> References: <Pine.BSI.4.58L.0412270043140.9248@vp4.netgate.net> <20041227083502.2d865466.wmoran@potentialtech.com> <d9175cad05010201392ac759df@mail.gmail.com> <20050102100949.6d0822d5.wmoran@potentialtech.com> <Pine.BSI.4.58L.0501021355260.7855@vp4.netgate.net>
next in thread | previous in thread | raw e-mail | index | archive | help
> > But it's a great way to boot Linux under Windows, or FreeBSD under > > either, or have multiple OSes running simultaneously under a single > > computer. > > How good is device support from within vmware? Can I get to > serial/usb/audio/network ports seamlessly? Well, these things aren't exactly seamless, but they are doable. In (all?) of these cases, the access to the host's resources are done indirectly via drivers and emulated hardware. An exception to this is USB which can (I think) be done directly allowing a client to utilise the USB devices of the host regardless of the support of the individual device by the host. As far as network, it can be natted or bridged from the controller, and audio is done as a sound device driver that just streams the sound to the parent's sound mechanism. -- If I write a signature, my emails will appear more personalised.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?d9175cad05010301486588de5d>