Did you have any problems when compiling vmware-tools?  I'm running into compilation problems with Deb 2.6.18-4-486...

I do have the kernel source.

any ideas?

Atfer the VM is booted, you shouldn't have network

access since udev binded the "new" ethernet interface

to eth1 or eth2. So to keep your network settings

clean you need to change following file :

 

Re: Losing ethernet interfaces in Debian Etch/Lenny[i]/etc/udev/rules.d/z25_persistent-net.rules[/i][/b]

I can't find the file.  I even tried doing a find for it (with just the word "persistent") and none of the files listed came close except for a "persistent-disk.rules" file.

I also tried the apt-get command and I get this:

"E: Command line option 'r' \[from -r´] is not known."

I'm using the current release of Mepis and currently the main problem that I'm having is that either the serverd locks up (I added a line to turn pshare off, so far that problem seems to be gone) and then the vm keeps "shutting off", then when I turn it back on, no network connection.

Tried using the e1000 device and when booted up, the WinXP vm needs to install drivers for it.  So now I'm stuck.

Any ideas?

­>I also tried the apt-get command and I get this:

"E: Command line option 'r' \[from -r´] is not

known."

 

This is because your using the wrong type of quotes,

if you can't find the right ones (just beside the

number 1 on an american keyboard). Just type

Re: Losing ethernet interfaces in Debian Etch/Lenny[i]uname -r[/i][/b].

 

So, if your getting :

 

Re: Losing ethernet interfaces in Debian Etch/Lenny# uname -r[/b]

Re: Losing ethernet interfaces in Debian Etch/Lenny2.6.18-4-686[/i]

 

That will gives you linux-headers-2.6.18-4-686.

Thank you.  With that, I was still having problems (couldn't find the package), but then I kept backing up on it and tabbing until it gave me what I needed to know.  (Needed an "s" to make it "-headers-" then it installed the essentials)

/etc/udev/rules.d/z25_persistent-net.rules

I can't find the file

 

This might has to do with the fact that Mepis doesn't

use udev the same way as Debian does. So you might

not have to change that file and not use this guide

whatsoever. I never had problems with Ubuntu as guest

eaven if it came from Debian.

Even though Mepis is a flavor of Debian?  I've used a unix-like enviroment before, so I'm not completely new to it, however I'm no where near being well knowledged so please forgive me if there's an obvious answer to that question.

As for your VM shutting off when your turning it on,

check the .log file in the folder of your vm (just

beside the .vmx) for more informations.

What's happening is that it'll power on, work for awhile, then 'shut off'.  Then when restarting it, it has no network connection.  Which is why I tried switching it to e1000, to see if that would help.  From reading another thread, I have changed it to vmxnet.  Is that the same as the default?  If so, then I'm waiting for it to mess up again.  But so far, it's been running for almost 21hours straight without any problems.  However that's not a good indicator, since it's run for over 24 hours before, and then started acting up on me.

Thanks for your assistance on this, I really appreciate it.

What's happening is that it'll power on, work for

awhile, then 'shut off'. Then when restarting it, it

has no network connection.

 

Are you getting errors inside the console of the VM?

I was having similar problem but in fact the VM

crashed by a problem with too many VMs on a sigle

host and the console's "screen-saver" kicked in

before i could see the error messages.

 

It's not much but I hope it helped.

I'm only running the one, and it seems to be random on how long it stays up.  Using the vmxnet, it's giving me the original problem that pshare was supposed to fix.  I'd like to try e1000 but I don't know what I need to do to make it work inside of the VM/WinXPsp2.