On 22 Sep 04 at 0:16, Norberto Bensa wrote:
> Norberto Bensa wrote:
> > It's working now. I had this in fstab:
>
> No, it's not working. After a reboot, same config, same kernel, same mounts,
> same everything -> No vmware.
>
> Just to summarize.
>
> * vmware with 2.6.9-rc1-mm5 works.
> * vmware with 2.6.9-rc2-mm1 doesn't work.
>
> I'll try 2.6.9-rc2 if anyone wants but since not many people answered my
> messages I guess there's no interest in vmware at all.
You said that you are putting large VMware temporary files on tmpfs,
and it is where my interest ends...
If you can provide strace of failed run, I can look at it.
Best regards,
Petr Vandrovec
> > * vmware with 2.6.9-rc1-mm5 works.
> > * vmware with 2.6.9-rc2-mm1 doesn't work.
I have vmware 4.5 running on 2.6.9-rc2-mm1 as well as 2.6.9-rc2-mm1
running within vmware. I must have missed the previous discussion, so
what issues are you having (i.e. how does vmware "not work")?
-- Kyle S.
On Sep 22, 2004, at 23:45, Kyle Schlansker wrote:
>>> * vmware with 2.6.9-rc1-mm5 works.
>>> * vmware with 2.6.9-rc2-mm1 doesn't work.
>
> I have vmware 4.5 running on 2.6.9-rc2-mm1 as well as 2.6.9-rc2-mm1
> running within vmware. I must have missed the previous discussion, so
> what issues are you having (i.e. how does vmware "not work")?
I think all the problems he is having are related to the fact that he
has a "tmpfs" mounted on top of "/tmp". I'm also using VMware with
2.6.9-rc2-mm1 with a plain, disk-based, /tmp directory, with no
problems at all.
Felipe Alfaro Solana wrote:
> > I must have missed the previous discussion, so
> > what issues are you having (i.e. how does vmware "not work")?
>
> I think all the problems he is having are related to the fact that he
> has a "tmpfs" mounted on top of "/tmp".
Exactly, I have tmpfs mounted on /tmp; but why does it work with kernels up to
2.6.9-rc1-mm5? I'm an ignorant on all this so an explanation would be nice.
> I'm also using VMware with
> 2.6.9-rc2-mm1 with a plain, disk-based, /tmp directory, with no
> problems at all.
I'll try a plain /tmp directory, but I'd like to know why I can't use tmpfs
anymore with kernels >=2.6.9-rc2-mm1.
Many thanks in advance,
Norberto
On Sep 23, 2004, at 03:36, Norberto Bensa wrote:
> Felipe Alfaro Solana wrote:
>>> I must have missed the previous discussion, so
>>> what issues are you having (i.e. how does vmware "not work")?
>>
>> I think all the problems he is having are related to the fact that he
>> has a "tmpfs" mounted on top of "/tmp".
>
> Exactly, I have tmpfs mounted on /tmp; but why does it work with
> kernels up to
> 2.6.9-rc1-mm5? I'm an ignorant on all this so an explanation would be
> nice.
>
>
>> I'm also using VMware with
>> 2.6.9-rc2-mm1 with a plain, disk-based, /tmp directory, with no
>> problems at all.
>
> I'll try a plain /tmp directory, but I'd like to know why I can't use
> tmpfs
> anymore with kernels >=2.6.9-rc2-mm1.
That's a question that requires far more knowledge than I have.
Maybe someone here... Andrew?
Felipe Alfaro Solana wrote:
> > I'll try a plain /tmp directory, but I'd like to know why I can't use
> > tmpfs
> > anymore with kernels >=2.6.9-rc2-mm1.
>
> That's a question that requires far more knowledge than I have.
> Maybe someone here... Andrew?
I think I fixed.
It's not a problem of tmpfs. It's a permissions issue.
This:
tmpfs /tmp tmpfs size=256m,noexec,nosuid,nodev 0 0
...gives the "can't allocate memory" message.
Doing:
# mount -o remount,exec /tmp
# /etc/init/vmware restart
Gives a working vmware (I've tried 2.6.9-rc2-mm1-VP-S2)
# mount | grep \ /tmp
tmpfs on /tmp type tmpfs (rw,nosuid,nodev,size=256m)
Now, why the hell does vmware want exec permission on /tmp, only vmware devs
know :(
Thanks everyone,
Norberto
Salut,
On Thu, Sep 23, 2004 at 12:49:10AM -0300, Norberto Bensa wrote:
> Now, why the hell does vmware want exec permission on /tmp, only vmware devs
> know :(
Because of the mmap they do?
Tonnerre