Date: Wed, 17 Mar 2010 16:40:48 -0400 From: Steve Polyack <korvus@comcast.net> To: Erik Norgaard <norgaard@locolomo.org> Cc: questions@freebsd.org Subject: Re: FreeBSD and vmware Message-ID: <4BA13E50.8050503@comcast.net> In-Reply-To: <4BA13CE3.4010803@locolomo.org> References: <4BA13CE3.4010803@locolomo.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 03/17/10 16:34, Erik Norgaard wrote: > Hi: > > I have a dual boot Windows/FreeBSD which I use for work, I just tried > today to create a virtual machine with vmware on windows to start up > the installed FreeBSD. > > This works except for three problems: > > - The disk device is renamed, I suppose I can just dublicate the > entries in the fstab, the devices not found won't be mounted, I'll get > an error but problem solved? > I think your best solution for this is to use glabel(8) to setup permanent labels on the drives. You can then mount the label in fstab by replacing the device name with the appropriate /dev/label/labelname entry. This will prevent the changes in disk device numbering or naming from causing you any more grief. > - I can't see the network devices from vmware Do you mean you can't see a NIC from within FreeBSD on top of VMware? You will have to choose "Other (64-bit)" for the OS type and/or choose the e1000/Intel1000 device within VMware for the virtual network card. FreeBSD has great support for this card, virtual attempt physical. > > - I can't start xwindows, no monitor is found Try /usr/ports/x11-drivers/xf86-video-vmware > > Any clues? > > Thanks, Erik > >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4BA13E50.8050503>