Date: Sun, 12 Dec 1999 21:59:33 -0500 (EST) From: Andrew Gallatin <gallatin@cs.duke.edu> To: "Vladimir N. Silyaev" <vsilyaev@mindspring.com> Cc: freebsd-emulation@FreeBSD.ORG Subject: Re: vmware questions Message-ID: <14420.22891.749447.645628@grasshopper.cs.duke.edu> In-Reply-To: <19991212204415.A18746@jupiter.delta.ny.us> References: <14420.14744.875394.54896@grasshopper.cs.duke.edu> <19991212204415.A18746@jupiter.delta.ny.us>
next in thread | previous in thread | raw e-mail | index | archive | help
Vladimir N. Silyaev writes: > On Sun, Dec 12, 1999 at 07:25:51PM -0500, Andrew Gallatin wrote: > > This is tremendous. Thank you for doing this! > Thank you for trying this port. > > > I'm running your > > latest port & I've run Win98 and have installed NT4 under vmware. > > It seems very solid. I was expecting my machine to crash at least > > once, but it did not ;-) > Really it's very easy, just try to launch second vmware copy ;-(. > It's easy to fix this, and enable only one vmware session per > host, but I'm looking for better solution. I'll keep this in mind. Thanks :-) <..> > > - Is sound supposed to work? I have sound configured as: > > > Oh no, I never tried to use sound. Ok it's added into my TODO list. Cool. Thanks! > > - Are SCSI CD-ROM's supposed to work? When attempting to use one, > > Windows claims the device is not available & I see many messages on > > console: > > > > Dec 11 16:00:26 grasshopper /kernel: (cd0:ahc0:0:5:0): ILLEGAL REQUEST asc:24,0 > > Dec 11 16:00:26 grasshopper /kernel: (cd0:ahc0:0:5:0): Invalid field in CDB > > Dec 11 16:00:37 grasshopper /kernel: (cd0:ahc0:0:5:0): READ SUB-CHANNEL. CDB: 42 0 40 1 0 0 8 0 18 0 > > > > After ripping the SCSI CDROM drive out & replacing it with an ATAPI > > drive, everything works just dandy. > I don't have a SCSI CDROM, so I can't to test this. I suppose that vmware use > ioctl to read subchannel, and SCSI cdrom driver complained about it. Sounds like it. I wonder if this is vmware's problem, or if it is a general linux-emu problem.. <..> > > > > I have appended a small patch to linprocfs_misc so that linprocfs > > reports memory size correctly. > Really this is patch must be addressed to Pierre Beyssac. > If you are interested on more correctly work of .../meminfo I have > just another patch, probably much more correct (probably only one leak > in swap info). Nice. I was wondering to myself why you need sysctl, but then I realized that you need it for meminfo.mem_shared.. Thanks! Drew ------------------------------------------------------------------------------ Andrew Gallatin, Sr Systems Programmer http://www.cs.duke.edu/~gallatin Duke University Email: gallatin@cs.duke.edu Department of Computer Science Phone: (919) 660-6590 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-emulation" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?14420.22891.749447.645628>