Re: Regarding VMWare 3.0 Port and an odd bug that i've beengetting over and over again...
On Sat, 2003-07-12 at 10:40, Scott M. Likens wrote: > On Sat, 2003-07-12 at 07:51, Christopher Nehren wrote: > > The "not implemented" error message suggests to me that the VM (in this > > case, Win2K) is attempting to perform an operation that the emulation > > software (or its underlying operating system -- in this case, Linux > > 2.4.2 under FreeBSD emulation) doesn't know how to perform. I received a > > similar message when attempting to install Windows XP on VMWare 2.x -- > > however, IIRC, mine didn't crash or require a hard reboot. My hypothesis > > is that -- were this a real, modern Linux machine -- that operation > > would succeed. However, since this is a binary emulation situation (one > > that itself manages its own layer of binary emulation), and one that > > more directly interfaces with the underlying hardware than most Linux > > emulated programs, the likelihood for such an operation to fail > > increases. As far as I understand it, the solution involves more fully > > implementing the Linux emulation. > > Actually it's during shutdown that this bug occurs > > It's quite annoying on top of the 'rtc.ko' wanting to dump and creating > a infinite loop panic at shutdown isn't that great either. > > I know i'm not the only person experiencing this, just the only person > who cares. > > So i've come to this conclusion, I'll just need linux. > > You are right thought it's obviously a call it's making like sync() i > imagine that we arn't implementing properly in the emulation. So when > VMWare try's to make this what should exist call, it's not really there > and fudges up. > > Thus leaving crap in the kernel i imagine, and thus creating the > problem. > > > > Either this, or it could just be a plain bug in VMWare -- though I've > > learned from experience that it's always best to blame oneself before > > assuming others are at fault. Nah it's still there with VFS_AIO compiled into the kernel. Obviously it's more then meats the eye, but I don't know where it lacks it, thus why I asked the list to see if I missed it. -- "I think we ought to be out there doing what we do best - making large holes in other people's countries." - George Carlin signature.asc Description: This is a digitally signed message part ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Regarding VMWare 3.0 Port and an odd bug that i've beengetting over and over again...
On Sat, 2003-07-12 at 08:00, Daniel Eischen wrote: > On 11 Jul 2003, Scott M. Likens wrote: > > > I've been using VMWare in 5.1-RELEASE for quite some time and such, and > > have ALWAYS gotten this bug and haven't been able to figure out exactly > > why it does this, but it requires me to reboot. > > > > Anyhow here's the layout of the system. > > > > P3 800Mhz with 512meg of SDRAM > > AHA 2940U2W, Dual 17Gig Ultra Scsi 2's (LVD) > > no IDE devices, IDE is normally disabled, Matrox G400 Dual head without > > HAL. > > Soundblaster PCI 512, (emu10k1) > > > > using waimea as the window manager (or kde doesn't seem to make this bug > > better) > > > > using netgraph bridging, i have the RTC.ko loaded (that's another > > nuisance i'd love to correct maybe when I have more time) > > > > I've tried reinstalling VMWare and even on a fresh FreeBSD install it > > gives this error. > > Do you have VFS_AIO in your kernel (or the AIO module loaded)? > > (I don't use VMWare, just guessing by looking at your error message). I wasn't aware of that module, Thanks. I'll have to rebuild the kernel because it's actually a 'option' not a simple kernel module. But that will make things happier. now if the new scheduler would work with me better, so it doesn't stick to 97% cpu I would be perfectly happy. But alas, that is for another thread. -- "I think we ought to be out there doing what we do best - making large holes in other people's countries." - George Carlin signature.asc Description: This is a digitally signed message part ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Regarding VMWare 3.0 Port and an odd bug that i've beengetting over and over again...
On Sat, 2003-07-12 at 07:51, Christopher Nehren wrote: > The "not implemented" error message suggests to me that the VM (in this > case, Win2K) is attempting to perform an operation that the emulation > software (or its underlying operating system -- in this case, Linux > 2.4.2 under FreeBSD emulation) doesn't know how to perform. I received a > similar message when attempting to install Windows XP on VMWare 2.x -- > however, IIRC, mine didn't crash or require a hard reboot. My hypothesis > is that -- were this a real, modern Linux machine -- that operation > would succeed. However, since this is a binary emulation situation (one > that itself manages its own layer of binary emulation), and one that > more directly interfaces with the underlying hardware than most Linux > emulated programs, the likelihood for such an operation to fail > increases. As far as I understand it, the solution involves more fully > implementing the Linux emulation. Actually it's during shutdown that this bug occurs It's quite annoying on top of the 'rtc.ko' wanting to dump and creating a infinite loop panic at shutdown isn't that great either. I know i'm not the only person experiencing this, just the only person who cares. So i've come to this conclusion, I'll just need linux. You are right thought it's obviously a call it's making like sync() i imagine that we arn't implementing properly in the emulation. So when VMWare try's to make this what should exist call, it's not really there and fudges up. Thus leaving crap in the kernel i imagine, and thus creating the problem. > Either this, or it could just be a plain bug in VMWare -- though I've > learned from experience that it's always best to blame oneself before > assuming others are at fault. -- "I think we ought to be out there doing what we do best - making large holes in other people's countries." - George Carlin ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Regarding VMWare 3.0 Port and an odd bug that i've beengetting over and over again...
The "not implemented" error message suggests to me that the VM (in this case, Win2K) is attempting to perform an operation that the emulation software (or its underlying operating system -- in this case, Linux 2.4.2 under FreeBSD emulation) doesn't know how to perform. I received a similar message when attempting to install Windows XP on VMWare 2.x -- however, IIRC, mine didn't crash or require a hard reboot. My hypothesis is that -- were this a real, modern Linux machine -- that operation would succeed. However, since this is a binary emulation situation (one that itself manages its own layer of binary emulation), and one that more directly interfaces with the underlying hardware than most Linux emulated programs, the likelihood for such an operation to fail increases. As far as I understand it, the solution involves more fully implementing the Linux emulation. Either this, or it could just be a plain bug in VMWare -- though I've learned from experience that it's always best to blame oneself before assuming others are at fault. signature.asc Description: This is a digitally signed message part
