From owner-freebsd-emulation Sun Dec 19 15:58:56 1999 Delivered-To: freebsd-emulation@freebsd.org Received: from wireless.net (wireless.net [207.137.156.159]) by hub.freebsd.org (Postfix) with ESMTP id 2E09F14BF2 for ; Sun, 19 Dec 1999 15:58:54 -0800 (PST) (envelope-from dbutter@wireless.net) Received: from db.wireless.net (db.wireless.net [209.75.70.101]) by wireless.net (8.9.3/8.9.3) with ESMTP id QAA11903 for ; Sun, 19 Dec 1999 16:04:21 -0800 (PST) Received: from wireless.net (dbm.wireless.net [192.168.0.2]) by db.wireless.net (8.9.3/8.9.3) with ESMTP id PAA08790 for ; Sun, 19 Dec 1999 15:58:18 -0800 (PST) (envelope-from dbutter@wireless.net) Message-ID: <385D7198.1AB14969@wireless.net> Date: Sun, 19 Dec 1999 16:00:24 -0800 From: Devin Butterfield X-Mailer: Mozilla 4.7 [en] (X11; I; Linux 2.2.5 i386) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-emulation@FreeBSD.ORG Subject: Re: VMware: Questions...(not /dev/rtc) References: <385D67A5.7E7D948B@wireless.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-emulation@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Devin Butterfield wrote: > > Guido van Rooij wrote: > > > > On Sat, Dec 18, 1999 at 08:44:39PM -0500, Vladimir N. Silyaev wrote: > > > > 2. When running VMware I see many messages saying: "linux: syscall > > > > setresuid is obsoleted or not implemented (pid=255)" going to the > > > > console. > > > I think you were ran vmware not from root? > > > > The binary is setuid to root so that should not be a problem. > > > > > > > > > 3. Perhaps related to 2., I notice that windows seems to freeze for 2-3 > > > > seconds (with disk activity during this freeze and more messages like in > > > > 2. going to the console) every 3-4 minutes. > > > Probably 3. and 2. are non related. > > > > > > > Is this somehow related to > > > > VMware needing a /dev/rtc device? If so, is there any practical way to > > > > satisfy this need? > > > I don't know what exactly VMware want from a /dev/rtc. The RTC already used in > > > kernel, so it doesn't have any chance to port a linux code. > > > > I am seeing the same freezes. I am running NT4 on a virtual drive. > > >From time to time, the NT in vmware freezes. The IDE light on the vmware > > screen is off, yet there is a tremendous amount of disk activity > > going on (as seen from iostat or systat -vmstat). I am seeing > > 100 transaction per second. There is no paging or swapping going on > > (as seen by FreeBSD), so I can only assume that something is happening > > inside the virtual drive. But it is NOT NT doing that because > > otherwise we'd see the IDE pseudo led on... > > > > Are there any people that run NT in vmware on a Linux box listening > > here? If so: do the see the same disk activity? > > > > -Guido > > I tried recently to run the same configuration I am using with BSD on a > Linux box (I actually copied the virtual disk and config file over) and > there were no problems. So, this is clearly only a problem under BSD. > When I was first setting up VMware under FreeBSD I remember a dialog box > which warned me that because I was missing a /dev/rtc device, menus in > windows may be jerky and or hesitate, and windows would loose time. I am > thinking that this may be the problem. I will try disabling VMware's > access to /dev/rtc under Linux and see if that exhibits the same > behavior. I'll post my results. > > -- > Regards, Devin. > Well, I just tried VMware under linux without the /dev/rtc device, and VMware does complain in a dialog box, but I am able to run windows just fine without any freezing. So, this suggests that the problem is not related to FreeBSD's lack of a /dev/rtc. -- Regards, Devin. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-emulation" in the body of the message