Maybe some more information... it creates a /tmp/rmt0 file (or whatever 
is required)

-rw-------  1 root     wheel  28672 Jun  6 22:23 ram1

Now, as the message says 24576 + 4096 = 28672

But ktrace shows this:

/tmp/ram1 is in fd 0x05
   5214 vmware   CALL  open(0x81f00e0,0xc2,0x180)
   5214 vmware   NAMI  "/emul/linux/tmp"
   5214 vmware   NAMI  "/tmp/ram0"
   5214 vmware   RET   open 5

  11047 vmware-ui CALL  read(0x5,0xbfbfe8a4,0x20)
  11047 vmware-ui GIO   fd 5 read 32 bytes
 
"\^A\^B\M-.\v\0\0\0\0\M-I\0\240\^B\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\M^@U\
         \M-,\b"
  11047 vmware-ui RET   read 32/0x20
   5214 vmware   CALL  ftruncate(0x5,0x7000)
   5214 vmware   RET   ftruncate 0
   5214 vmware   CALL  mmap(0,0x1000,0x3,0x1,0x5,0x6)
   5214 vmware   RET   mmap -1 errno -22 Invalid argument

Which would presumably the crux of the problem.

So, 0 can be NULL according to man page

0x1000 is 4096, or the size of mmap, presumably ok.

0x3 is prot, becomes: PROT_READ | PROT_WRITE

0x1 is flags, becomes: MAP_SHARED

fd is 0x5, which is the file /tmp/ram1

0x6 is offset, kinda weird I guess. Would this make it fail?


Source for this appears to be:
         pageoff = (pos & PAGE_MASK);
         pos  -= pageoff;
         size += pageoff;                        /* add offset */
         size = (vsize_t)round_page(size);       /* round up */
         if ((ssize_t) size < 0)
                 return (EINVAL);                        /* don't allow 
wrap */



Any help?








Jorgen Lundman wrote:
> 
> NetBSD lundman 1.6T NetBSD 1.6T (netbsd) #0: Mon Jun  2 17:05:03 JST 
> 2003 root@lundman:/usr/src/sys-current-1.6P/sys/arch/i386/compile/netbsd 
> i386
> 
> Grabbed pkgsrc, installed vmware3 and vmware-module3. The latter needed 
> a patch to make the version reply be 30 instead of 10.
> 
> mounted /proc as linux
> 
> So, it starts up, can do the configuration things, click PowerOn and it 
> says:
> 
> 
> Could not mmap 4096 bytes of memory from file offset 24576 at (nil): 
> Invalid argument.
> Cannot allocate user shared log levels.
> 
> ktracing it alas, did not seem to tell me much more (nil is nil after all):
> 
>  11047 vmware-ui CALL  access(0x82f82e0,0x4)
>  11047 vmware-ui NAMI  "xm_error"
>  11047 vmware-ui RET   access -1 errno -2 No such file or directory
> 
> 
> Any suggestions as to how to proceed?
> 
> Lund
> 
> 
> 

-- 
Jorgen "Lord" Lundman <lundman@lundman.net>
Technology Manager, Unix Administrator
Phone: +81 (0)3-3375-1767  Mobile: +81 (0)90-5578-8500
Pager: 09055788500@docomo.ne.jp
"Rare is the person who can weigh the faults of others
without putting his thumb on the scales": Byron J. Langenfeld