> "ID" == Ian Dowse <[EMAIL PROTECTED]> writes:
ID> In message <[EMAIL PROTECTED]>, CHOI Junho writes:
>
> I'll try. Oh, I forget to say I appiled des's linux_ioctl patch.
>
ID> Ah, that's different then. I assumed from the error that you had
ID> revision 1.76 of li
In message <[EMAIL PROTECTED]>, CHOI Junho writes:
>
>I'll try. Oh, I forget to say I appiled des's linux_ioctl patch.
>
Ah, that's different then. I assumed from the error that you had
revision 1.76 of linux_ioctl.c, but if that patch applied then you
don't. Try updating your sources again; revi
>>>>> "ID" == Ian Dowse <[EMAIL PROTECTED]> writes:
ID> In message <[EMAIL PROTECTED]>, CHOI Junho writes:
>
> Hmm.. I have experienced another problem(-current of 19 Nov.) with
> vmware. When it runs it comes up with the follo
In message <[EMAIL PROTECTED]>, CHOI Junho writes:
>
>Hmm.. I have experienced another problem(-current of 19 Nov.) with
>vmware. When it runs it comes up with the following dialog:
>
> "Encountered an error while initializing the ethernet address.
> You probably
>>>>> "HM" == Hellmuth Michaelis <[EMAIL PROTECTED]> writes:
HM> After this, vmware comes up and then complains about not able to use
HM> /dev/rtc (/dev/rtc is present in /compat/linux and is kld-loaded) but
HM> then continues to start up and
; in /usr/local/etc/rc.d/vmware.sh
>
> - replace /compat/linux/dev/vmnet1 with a symlink to /dev/vmnet1
> (perhaps the previous step would be unnecessary by this one)
>
> After this, vmware comes up and then complains about not able to use
> /dev/rtc (/dev/rtc is pre
>From the keyboard of Georg-W. Koltermann:
> At Sun, 18 Nov 2001 09:37:12 +0100 (MET),
> Hellmuth Michaelis wrote:
> >
> > Thought i update my current this morning and ran into two problem with
> > vmware:
> >
> > 1) when starting vmware, vmware.sh ab
In message <[EMAIL PROTECTED]>, "Georg-W. Koltermann" writes
:
>I also tried to update /compat/linux/dev/vmnet1 to match the
>/dev/vmnet1, and that got me just a litte bit farther. I now get
>"Could not get address for /dev/vmnet1: Invalid argument
>Failed to configure ethernet0." I added some pr
At Sun, 18 Nov 2001 09:37:12 +0100 (MET),
Hellmuth Michaelis wrote:
>
> Thought i update my current this morning and ran into two problem with
> vmware:
>
> 1) when starting vmware, vmware.sh aborts with
>
>vmware.sh: cannot create /compat/linux/dev/vmnet1: no such d
Thought i update my current this morning and ran into two problem with
vmware:
1) when starting vmware, vmware.sh aborts with
vmware.sh: cannot create /compat/linux/dev/vmnet1: no such device or address
2) after that i tried to recompile/reinstall the vmware2 port and ran into
/usr
[EMAIL PROTECTED] writes:
> Has anyone seen similar problem on recent -current or has someone an
> idea why vmware is issuing a SIOCGIFCONF ioctl without providing an
> interface name?
>
> Oct 19 18:04:53 mp /boot/kernel/kernel: linux_ioctl_socket(): ioctl 35093 on
To clarif
it says
>> something like could not get bridgin status of /dev/vmnet1...)
>
> Can you send me a ktrace? I suspect my linux_ioctl.c commits may be
> at fault.
Does anyone know where to get an eval license for vmware2, to run it as
root?
Has anyone seen similar problem on recent -
(using host-only conf. under vmware) and host-only
configuration.
The error
Could not get address for /dev/vmnet1: argument is invalid
Failed to configure ethernet0
is all I get... (this is the host-only case, for bridged it says
something like could not get bridgin status of /dev
Vmware has started hanging on current versions of current. The binary
start properly, but when I try and start one of my virtual machines the
process hangs in "devbuf". The disk seems to access periodically. I
tried ktracing the process but it didn't get very far. Has a
now that we've removed block devices, there must be a hack
to allow us to read block devices from vmware.
can someone tell me what it is?
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Andrew Gallatin wrote:
>
> Andrew Gallatin writes:
> >
> > Dag-Erling Smorgrav writes:
> > > Julian Elischer <[EMAIL PROTECTED]> writes:
> > > > I believe that vmware mmaps a region of memory and then somehow syncs
> > > >
Andrew Gallatin writes:
>
> Dag-Erling Smorgrav writes:
> > Julian Elischer <[EMAIL PROTECTED]> writes:
> > > I believe that vmware mmaps a region of memory and then somehow syncs
> > > it to disk. (It is certainly doing something like it here).
David Malone wrote:
>
> On Thu, Feb 08, 2001 at 02:47:59PM +, Josef Karthauser wrote:
> > > what does systat -vmstat or vmstat 1
> > > show?
> > > Better still, I guess we could do a linux-truss
> > > and see what it's doing...
> >
> > I believe that it's strace under linux. If someone can p
Dag-Erling Smorgrav writes:
> Julian Elischer <[EMAIL PROTECTED]> writes:
> > I believe that vmware mmaps a region of memory and then somehow syncs
> > it to disk. (It is certainly doing something like it here).
>
> Theory: VMWare mmaps a region of memory c
> On Thu, Feb 08, 2001 at 04:58:17AM -0800, Julian Elischer wrote:
> >=20
> > Looks like some way of clustering this might achieve a lot.
> >=20
> > what does systat -vmstat or vmstat 1
> > show?
> > Better still, I guess we could do a linux-truss
> > and see what it's doing...
>
> I believe that
On Thu, Feb 08, 2001 at 02:47:59PM +, Josef Karthauser wrote:
> > what does systat -vmstat or vmstat 1
> > show?
> > Better still, I guess we could do a linux-truss
> > and see what it's doing...
>
> I believe that it's strace under linux. If someone can provide me
> with a binary of this to
On Thu, Feb 08, 2001 at 04:58:17AM -0800, Julian Elischer wrote:
>
> Looks like some way of clustering this might achieve a lot.
>
> what does systat -vmstat or vmstat 1
> show?
> Better still, I guess we could do a linux-truss
> and see what it's doing...
I believe that it's strace under linux
Julian Elischer <[EMAIL PROTECTED]> writes:
> I believe that vmware mmaps a region of memory and then somehow syncs
> it to disk. (It is certainly doing something like it here).
Theory: VMWare mmaps a region of memory corresponding to the virtual
machine's "physical&qu
Josef Karthauser wrote:
>
> On Thu, Feb 08, 2001 at 04:08:12AM -0800, Julian Elischer wrote:
> > Josef Karthauser wrote:
> > >
> > > 714 root -14 0 123M 79192K inode0:45 25.29% 25.29% vmware
> > >
> > > When this happens the whole mac
On Thu, Feb 08, 2001 at 04:08:12AM -0800, Julian Elischer wrote:
> Josef Karthauser wrote:
> >
> > 714 root -14 0 123M 79192K inode0:45 25.29% 25.29% vmware
> >
> > When this happens the whole machine freezes also. Processes run, but
> > new proce
Josef Karthauser wrote:
>
> The slowdown during start up appears to be in biowr; this is probably
> because of IDE write caching being switched off. More seriously
> the vmware hangs during various phases of it's boot process.
Write caching is incompaible with soft update
three days (probably about 36 hours excluding suspends) on a
> > > 366MHz laptop with a ATA33 disk.
> >
> > Would it be possible for someone experiencing this slowdown to try to
> > narrow down the day (or even the week) on which it occurred?
>
> I've experien
ATA33 disk.
>
> Would it be possible for someone experiencing this slowdown to try to
> narrow down the day (or even the week) on which it occurred?
I've experienced a substantial slowdown in VMware since bumping forwards
from -STABLE on my workstation. As I recently commented on -e
, but I'm not sure which day's I
> > updated the kernel.
> >
> > I'll try some builds.
>
> Ok. The problem definitely began between -D2001-01-29 and -D2001-01-30.
> I'll try and binary chop to workout what caused it.
If you have ata disks, try &q
On Wed, Feb 07, 2001 at 08:56:14PM +, Josef Karthauser wrote:
> On Wed, Feb 07, 2001 at 08:26:15PM +0100, Dag-Erling Smorgrav wrote:
> > Brian Somers <[EMAIL PROTECTED]> writes:
> > > Indeed. I've been doing a ``make build'' on an OpenBSD-current vm
> > > for three days (probably about 36 ho
On Wed, Feb 07, 2001 at 08:26:15PM +0100, Dag-Erling Smorgrav wrote:
> Brian Somers <[EMAIL PROTECTED]> writes:
> > Indeed. I've been doing a ``make build'' on an OpenBSD-current vm
> > for three days (probably about 36 hours excluding suspends) on a
> > 366MHz laptop with a ATA33 disk.
>
> Wo
On Wed, Feb 07, 2001 at 08:26:15PM +0100, Dag-Erling Smorgrav wrote:
> Brian Somers <[EMAIL PROTECTED]> writes:
> > Indeed. I've been doing a ``make build'' on an OpenBSD-current vm
> > for three days (probably about 36 hours excluding suspends) on a
> > 366MHz laptop with a ATA33 disk.
>
> Wo
Brian Somers <[EMAIL PROTECTED]> writes:
> Indeed. I've been doing a ``make build'' on an OpenBSD-current vm
> for three days (probably about 36 hours excluding suspends) on a
> 366MHz laptop with a ATA33 disk.
Would it be possible for someone experiencing this slowdown to try to
narrow down t
does not explain why Windows2000 and the Boot
> loader
> both slowed down by a factor or 3->6 over teh last 2 weeks.
>
> It's even slower to start up, before it has even started any emulation..
>
> This feels like the system is massively slowing down page activations or
>
ast 2 weeks.
It's even slower to start up, before it has even started any emulation..
This feels like the system is massively slowing down page activations or
some other sort of exceptions that are standard for vmware.
The same vmware with the same guest OS (not been updated) is now much slow
ure
I noticed this too. It's about 3 x slower for me. Even the startup sequence
when we haven't even loaded the bootblocks is MUCH slower..
I'm using vmware 1.0.x and running FreeBSD on it for kernel debugging.
--
__--_|\ Julian Elischer
/ \ [EMAIL PROTECTED]
(
On Wed, Feb 07, 2001 at 02:40:27AM +1100, Bruce Evans wrote:
> > Could someone please hit me with a clue-bat :)
>
> Read your freebsd-emulation mail :-).
/me wanders off to subscribe to freebsd-emulation.
Thanks Bruce.
Joe
PGP signature
On Tue, 6 Feb 2001, Josef Karthauser wrote:
> I'm wondering what's changed recently to cause vmware2 running on
> the linuxemu to lose a lot of performance with disk I/O.
Use of cmpxchg and possibly other SMP pessimizations.
> A couple of weeks ago I could boot win2000 under vmware2 in a matter
Hi,
I'm wondering what's changed recently to cause vmware2 running on
the linuxemu to lose a lot of performance with disk I/O.
A couple of weeks ago I could boot win2000 under vmware2 in a matter
of minutes; on today's kernel it takes 5 or 10 minutes to boot,
and disk I/O is through the roof.
On Tue, Sep 12, 2000 at 04:44:41PM +0200, Reinier Bezuidenhout wrote:
> Let me first ask ... do you use the "suspend/resume" option??
Yep.
> This caused the same "lockup" every few seconds on my machine too -
> a much slower 400 PII. As soon as I "shutdown" Win9X and rebooted
> it worked fine.
> Greg Lehey wrote:
> >
> > FWIW, I was never happy with the removal of block devices either. I
> > was shouted down with "can you point to any one use they are?", to
> > which I replied "just because I don't know of one doesn't mean there
> > isn't one, or that there will never be one in the fu
Mike Smith wrote:
>
> >
> > Doesn't Oracle run MUCH better when given raw block disk devices to store
> > data on?
>
> Oracle wants to cache it's own data, it doesn't want the buffer cache
> behind it.
Yes, now it's all coming back. It's amazing how much you can forget in
the space of a decad
Greg Lehey wrote:
>
> FWIW, I was never happy with the removal of block devices either. I
> was shouted down with "can you point to any one use they are?", to
> which I replied "just because I don't know of one doesn't mean there
> isn't one, or that there will never be one in the future". This
On Wed, Sep 13, 2000 at 10:48:20AM -0400, Brian A. Seklecki - Stargate Industries, LLC
- NOC wrote:
> You're running vmware sucsessfully in --current?
Yes. -current from August 18th, and I'm running the vmware2-2.0.2.621 port.
Installing Win98 took about 4 hours though -- mos
T)
> From: Reinier Bezuidenhout <[EMAIL PROTECTED]>
> To: "Brian A. Seklecki - Stargate Industries, LLC - NOC"
> <[EMAIL PROTECTED]>
> Cc: [EMAIL PROTECTED]
> Subject: Re: VMWare on -current, how fast should I expect it to be?
>
> Hi ..
>
> I d
Brian A. Seklecki - Stargate Industries, LLC - NOC wrote:
>
> You're running vmware sucsessfully in --current? I sync'd up the last
> time I was in the office (last...Friday?) and the linux emulation package
> refused to build in --current; complaining about an incopatibl
You're running vmware sucsessfully in --current? I sync'd up the last
time I was in the office (last...Friday?) and the linux emulation package
refused to build in --current; complaining about an incopatible kernel
module. In fact, i had to comment out the linux proc file system
.
I am. The information above is the disk underlying the UFS filesystem that
VMWare is then splatting it's files to.
N
--
Internet connection, $19.95 a month. Computer, $799.95. Modem, $149.95.
Telephone line, $24.95 a month. Software, free. USENET transmission,
hundreds if not thousands
On Tuesday, 12 September 2000 at 10:13:16 -0400, Thomas David Rivers wrote:
>
> Julian Elischer ([EMAIL PROTECTED]) wrote:
>>
>> Nik Clayton wrote:
>>>
>>> Hi guys,
>>>
>>> For those of you running VMWare (2) on -current, how fast do
On Tue, Sep 12, 2000 at 02:27:45PM +0100, Nik Clayton wrote:
> For those of you running VMWare (2) on -current, how fast do you expect it to
> be?
I'm running it on my PIII 366 laptop. It's not great, but it's usable.
The biggest factors I've seen effecting perf
ough I may be out of date it's been a while.
> So, if Vmware runs on Linux, and Linux doesn't have any block devices,
> why would Vmware need block devices?
Vmware needs buffering for performance. ISTR some discussion when
this came up (a while ago) of having buffered devi
I have seen this too ...
Let me first ask ... do you use the "suspend/resume" option??
If Yes then :)
This caused the same "lockup" every few seconds on my machine too -
a much slower 400 PII. As soon as I "shutdown" Win9X and rebooted
it worked fine.
I guess
Julian Elischer ([EMAIL PROTECTED]) wrote:
>
> Nik Clayton wrote:
> >
> > Hi guys,
> >
> > For those of you running VMWare (2) on -current, how fast do you expect it to
> > be?
> >
> > I'm running it quite successfully on a 750MHz PII
Nik Clayton wrote:
>
> Hi guys,
>
> For those of you running VMWare (2) on -current, how fast do you expect it to
> be?
>
> I'm running it quite successfully on a 750MHz PIII w/ 128MB RAM, and the
> following disk controller / disk
>
> atapci0: port
Hi guys,
For those of you running VMWare (2) on -current, how fast do you expect it to
be?
I'm running it quite successfully on a 750MHz PIII w/ 128MB RAM, and the
following disk controller / disk
atapci0: port 0xfc90-0xfc9f at device 7.1 on pci0
ata0: at 0x1f0 irq 14 on at
Has anyone managed to fake out vmware WRT block devices?
it REQUIRES a block device to be able to read raw disks,
and in fact, if you manage to divert the read to raw devices, the
performance SUCKS because they don't cache.
--
__--_|\ Julian Elischer
/ \ [EMAIL PROT
Julian Elischer wrote:
>
> Julian Elischer wrote:
> >
> > David Malone wrote:
> > >
> > > On Fri, Sep 08, 2000 at 11:57:46PM -0700, Julian Elischer wrote:
> > >
> > > > sh vmware.sh start
> > > > kldload: can't
Julian Elischer wrote:
>
> David Malone wrote:
> >
> > On Fri, Sep 08, 2000 at 11:57:46PM -0700, Julian Elischer wrote:
> >
> > > sh vmware.sh start
> > > kldload: can't load /usr/local/lib/vmware/lib/modules/vmmon.ko: Exec
> > > format e
David Malone wrote:
>
> On Fri, Sep 08, 2000 at 11:57:46PM -0700, Julian Elischer wrote:
>
> > sh vmware.sh start
> > kldload: can't load /usr/local/lib/vmware/lib/modules/vmmon.ko: Exec
> > format error
> > kldload: can't load /usr/local/lib/vmware/
On Fri, Sep 08, 2000 at 11:57:46PM -0700, Julian Elischer wrote:
> sh vmware.sh start
> kldload: can't load /usr/local/lib/vmware/lib/modules/vmmon.ko: Exec
> format error
> kldload: can't load /usr/local/lib/vmware/lib/modules/vmnet.ko: Exec
> format error
>
>
Julian Elischer wrote:
>
> Just a warning, that the current vmware 1.x port doesn;t compile
> under -current.
> I'm looking at it at the moment (as I only have a licence for 1.x)
>
responding to myself:
the linux include files that have moved to /sys/compat/linux
nee
Just a warning, that the current vmware 1.x port doesn;t compile
under -current.
I'm looking at it at the moment (as I only have a licence for 1.x)
julian
--
__--_|\ Julian Elischer
/ \ [EMAIL PROTECTED]
( OZ) World tour 2000
---> X_.---._/ presently in
Munehiro Matsuda writes:
> :: Make all Ethernet drivers attach using ether_ifattach() and detach using
> :: ether_ifdetach().
>
> After the commit, VMware seems to hang the system at boot time.
> The "vmnet" module, that comes with VMware, needs the included patch.
es the operations of if_attach(), ng_ether_attach(),
:: and bpfattach(). The latter consolidates the corresponding detach operations.
::
:: Reviewed by:julian, freebsd-net
Hello,
After the commit, VMware seems to hang the system at boot time.
The "vmnet" module, that comes with V
In message <[EMAIL PROTECTED]> Mike Smith writes:
: As far as the loader is concerned, though, neither of these are on the
: boot path, so we can typically wait until the kernel's up and we can use
: some "real real" drivers. 8)
Well, I have seen boards that support booting off pccard devices..
> In message <[EMAIL PROTECTED]> Mike Smith writes:
> : > a larger issue. It is not the loader's job to detect the underlying
> : > hardware configuration.
> :
> : Actually, in a broad fashion, it _is_. This is why the loader
> : understands PCI and PnP, for example.
>
> How hard would it be t
In message <[EMAIL PROTECTED]> Mike Smith writes:
: > a larger issue. It is not the loader's job to detect the underlying
: > hardware configuration.
:
: Actually, in a broad fashion, it _is_. This is why the loader
: understands PCI and PnP, for example.
How hard would it be to add usb and pc
In <[EMAIL PROTECTED]>, Luoqi Chen wrote:
> > In <[EMAIL PROTECTED]>, Luoqi Chen wrote:
> > > It is not the loader's job to detect the underlying
> > > hardware configuration.
> >
> > I disagree. I would like to tell which machine I am booting on to
> > choose an appropriate kernel.
> >
> Eve
> In <[EMAIL PROTECTED]>, Luoqi Chen wrote:
> > It is not the loader's job to detect the underlying
> > hardware configuration.
>
> I disagree. I would like to tell which machine I am booting on to
> choose an appropriate kernel.
>
Eventually (it may take a while) we should be able to boot any
> > > a larger issue. It is not the loader's job to detect the underlying
> > > hardware configuration.
> >
> > Actually, in a broad fashion, it _is_. This is why the loader
> > understands PCI and PnP, for example.
> >
> Why do we want to do that? Are we going to offload device probe routines
> > a larger issue. It is not the loader's job to detect the underlying
> > hardware configuration.
>
> Actually, in a broad fashion, it _is_. This is why the loader
> understands PCI and PnP, for example.
>
Why do we want to do that? Are we going to offload device probe routines to
the loader
> a larger issue. It is not the loader's job to detect the underlying
> hardware configuration.
Actually, in a broad fashion, it _is_. This is why the loader
understands PCI and PnP, for example.
--
\\ Give a man a fish, and you feed him for a day. \\ Mike Smith
\\ Tell him he should learn h
> Given the way VMware works, I'd have nothing against making it a FICL
> words, except...
>
> ...VMware is a port. For some reason, I dislike the idea of having
> support targetted at exclusively one specific port. Though we have
> features added specifically to deal w
At 10:47 AM -0700 6/11/00, Mike Smith wrote:
>It's not a port, it's a platform. We probably want to add extra
>words to detect other platform features, eg. i386, alpha, ia64,
>etc. but that doesn't invalidate the basic idea.
For instance, I might be running the vmware pr
> Mike Smith wrote:
> >
> > > ...VMware is a port. For some reason, I dislike the idea of having
> > > support targetted at exclusively one specific port. Though we have
> > > features added specifically to deal with certain ports, they were all
> > &g
Mike Smith wrote:
>
> > ...VMware is a port. For some reason, I dislike the idea of having
> > support targetted at exclusively one specific port. Though we have
> > features added specifically to deal with certain ports, they were all
> > more generic features.
&
Peter Wemm wrote:
>
> > 2) Add the VMware detecting to FICL, as originally suggested.
>
> Why make #2 vmware specific? Why not set $emulation to native,vmware,bochs,
> etc. This is applicable to any platform that may have some sort of emulator.
> Putting it in an environ
> Mike Smith wrote:
> >
> > > VMware intercepts the inb/outb instruction to port 0x5658 when the eax
> > > register is set to a magic value, otherwise it would be handled as any
> > > other ports.
> >
> > I think, again, that adding an i386-speci
"Daniel C. Sobral" wrote:
> Mike Smith wrote:
> >
> > > VMware intercepts the inb/outb instruction to port 0x5658 when the eax
> > > register is set to a magic value, otherwise it would be handled as any
> > > other ports.
> >
> > I th
> Mike Smith wrote:
> >
> > > VMware intercepts the inb/outb instruction to port 0x5658 when the eax
> > > register is set to a magic value, otherwise it would be handled as any
> > > other ports.
> >
> > I think, again, that adding an i386-speci
Mike Smith wrote:
>
> > VMware intercepts the inb/outb instruction to port 0x5658 when the eax
> > register is set to a magic value, otherwise it would be handled as any
> > other ports.
>
> I think, again, that adding an i386-specific word that detects the
> pre
> > As for setting registers ti specific values... huh? Why does this
> > matter? Can you explain exactly what your code does and how?
> >
> VMware intercepts the inb/outb instruction to port 0x5658 when the eax
> register is set to a magic value, otherwise it would b
> As for setting registers ti specific values... huh? Why does this
> matter? Can you explain exactly what your code does and how?
>
VMware intercepts the inb/outb instruction to port 0x5658 when the eax
register is set to a magic value, otherwise it would be handled as any
other po
Luoqi Chen wrote:
>
> > We have inb and outb. Can't vmware be written in Forth? If inl cannot be
> > replaced with inb, I'd rather add inl than vmware.
> But we can't set registers to specific values before inb/outb, which also
> means our inb/outb are quite
> We have inb and outb. Can't vmware be written in Forth? If inl cannot be
> replaced with inb, I'd rather add inl than vmware.
>
But we can't set registers to specific values before inb/outb, which also
means our inb/outb are quite useless in making BIOS calls.
>
Luoqi Chen wrote:
>
> Would anyone object if I add a ficl word to detect whether we're booting
> from a vmware virtual machine? I find it extremely useful when I'm running
> FreeBSD as a guest under NT. Because it is a dual cpu box, I can't use a
> single kernel t
Peter Wemm wrote:
>
> Christopher Masto wrote:
> > On Fri, Jun 09, 2000 at 01:14:35PM -0400, Jeroen C. van Gelderen wrote:
> > > I'm not sure it is a good idea to name this variable VMWare as
> > > that is implementation specific. It may be better to have a
Christopher Masto wrote:
> On Fri, Jun 09, 2000 at 01:14:35PM -0400, Jeroen C. van Gelderen wrote:
> > I'm not sure it is a good idea to name this variable VMWare as
> > that is implementation specific. It may be better to have a var
> > named 'emulation' set
> > extern void ficlOutb(FICL_VM *pVM);
> > extern void ficlInb(FICL_VM *pVM);
I'm an idiot.
--
Christopher Masto Senior Network Monkey NetMonger Communications
[EMAIL PROTECTED][EMAIL PROTECTED]http://www.netmonger.net
Free yourself, free your machine, free the d
On Fri, Jun 09, 2000 at 01:14:35PM -0400, Jeroen C. van Gelderen wrote:
> I'm not sure it is a good idea to name this variable VMWare as
> that is implementation specific. It may be better to have a var
> named 'emulation' set to 'none' or 'vmware' o
Luoqi Chen wrote:
>
> Would anyone object if I add a ficl word to detect whether we're booting
> from a vmware virtual machine? I find it extremely useful when I'm running
> FreeBSD as a guest under NT. Because it is a dual cpu box, I can't use a
> single kernel t
> Would anyone object if I add a ficl word to detect whether we're booting
> from a vmware virtual machine?
Sounds good to me!
--
\\ Give a man a fish, and you feed him for a day. \\ Mike Smith
\\ Tell him he should learn how to fish himself, \\ [EMAIL PROTECTED]
\\ and he'l
Would anyone object if I add a ficl word to detect whether we're booting
from a vmware virtual machine? I find it extremely useful when I'm running
FreeBSD as a guest under NT. Because it is a dual cpu box, I can't use a
single kernel to boot both directly or inside the virtual mac
guess I can understand the large number of silo overflows. I noticed
that I can't seem to get any mails when I have vmware working, and I wish
that wasn't so. The part that really worries me, tho, is the virtual
memory warning. I was doing a lot of Windows software installation (w
On Sun, Mar 05, 2000 at 01:35:27PM +, Nick Sayer wrote:
> Ah! I found it!
>
> --- linux_ioctl.h.orig Mon Feb 28 11:50:23 2000
> +++ linux_ioctl.h Mon Feb 28 11:24:08 2000
> @@ -32,6 +32,25 @@
> #define_LINUX_IOCTL_H_
This patch is fubar'ed. Your mailer wrapped lines and tur
Ah! I found it!
--- linux_ioctl.h.orig Mon Feb 28 11:50:23 2000
+++ linux_ioctl.h Mon Feb 28 11:24:08 2000
@@ -32,6 +32,25 @@
#define_LINUX_IOCTL_H_
/*
+ * disk
+ */
+#define LINUX_BLKROSET 0x125d
+#define LINUX_BLKROGET 0x125e
+#define LINUX_BLKRRPART
Andrew Atrens wrote:
>
> A missing (not implemented) linux ioctl is breaking VMWare 2.0 -
>
> > linux: 'ioctl' fd=13, cmd=1260 ('^R',96) not implemented
I implemented this ioctl. It's not as hard as you think. You do a
DIOCGDINFO and return d_secperuni
At Sun, 5 Mar 2000 01:32:39 -0500 (EST),
Andrew Atrens <[EMAIL PROTECTED]> wrote:
>
> A missing (not implemented) linux ioctl is breaking VMWare 2.0 -
>
> > linux: 'ioctl' fd=13, cmd=1260 ('^R',96) not implemented
>
>
> After rummaging
A missing (not implemented) linux ioctl is breaking VMWare 2.0 -
> linux: 'ioctl' fd=13, cmd=1260 ('^R',96) not implemented
After rummaging around in the 2.3 kernel, I found the following in
`linux/include/linux/fs.h':
/* the read-only stuff doesn't really be
I just cvsup'd today (and I did also recompile the vmware modules,
just in case)... and the vmware binary started failing with the
message:
[2:18:318]dgilbert@strike:/u7/dgilbert/vmware/FreeBSD> vmware
(USER) Dictionary_Create: unable to allocate memoryPanic without a VM
Segmentation fa
201 - 300 of 363 matches
Mail list logo
