Re: [gentoo-user] vmware workstation daemon problem
On 1/15/06, Brett I. Holcomb [EMAIL PROTECTED] wrote: Where do I find docs that go into all of this? Select Help-Contents. I'm not sure about player, but for workstation the HTML help is in /opt/vmware/workstation/lib/help. The networking help is file:/opt/vmware/workstation/lib/help/workstation/networking.htm You can also find some help online (although I couldn't find anything decent for player): http://www.vmware.com/support/ws55/doc/ws_net.html -Richard -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] vmware workstation daemon problem
I had the unloadable modules. I then reran config today and it worked - config.pl created a new setup. I turned the system on this morning so maybe that did it. Can you explain host vs bridge vs other network options? I want to have vmplayer use the same IP address as the system it's running on. Thanks. On Sunday 15 January 2006 01:46, Halo0784 (sent by Nabble.com) wrote: do you have module unloading compiled into your kernel? if not this is needed because of how the /etc/vmware/init.d/vmware script works also a debug check list first check for your vm modules lsmod this should show you your vmmon / vmnet modules also check your /dev folder for your vm files ls -l /dev/vm* this should show you vmmon / vmnet / vmnet0 and so on lastly if you find that you have module unloading support and all the above check out fine do rc-update add vmware default then just reboot a very windows approach to this i know but im lzy and it will do 2 things... 1) shows you that your install is goin good (if u reboot and vmware does'nt work then it aint a good install) 2) deals with any modules that may be loaded in as perment, im sure there may be a better way but ... im lzy =) as you reboot you should see the vm services load with the typical [ok] login then run your vmware as you would normally. -- View this message in context: http://www.nabble.com/vmware-workstation-daemon-problem-t720417.html#a23869 00 Sent from the gentoo-user forum at Nabble.com. -- Brett I. Holcomb -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] vmware workstation daemon problem
On 1/15/06, Brett I. Holcomb [EMAIL PROTECTED] wrote: Can you explain host vs bridge vs other network options? I want to have vmplayer use the same IP address as the system it's running on. The closest to what you said would be NAT networking. In this case, the guest receives an address on a private network, but can communicate with the outside world using the host's address. However, nothing on the outside can get services from your guest. If you want your guest to provide services to the rest of your network, you need bridged networking. In this case, both the host and the guest show up on the network at different MAC addresses, and thus can get different IP addresses. It is just like if they were separate computers. Host networking is only if you do not want the guest to communicate with the outside at all. The only machine it can communicate with is the host (or other guests) on a private network. You can actually create multiple network cards for the guest using any combination of the above. I have used host-only networking to provide samba shares to the guest, without exporting them to the rest of the world, plus a bridged network connection for the guest to participate in the LAN. -Richard -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] vmware workstation daemon problem
Hmm, I'll have to think about this. At work I'm running vmplayer on XP and at home I have it on Gentoo. For work, at this point I just want to have the vmplayer session to run Linux mail and news clients (because Windows doesn't have anything worthwhile). This is at work and I have a static IP address that is allowed through to the outside so I have to use the address of the host. Where do I find docs that go into all of this? Thank you for the explanation. On Sunday January 15 2006 20:05, Richard Fish wrote: On 1/15/06, Brett I. Holcomb [EMAIL PROTECTED] wrote: Can you explain host vs bridge vs other network options? I want to have vmplayer use the same IP address as the system it's running on. The closest to what you said would be NAT networking. In this case, the guest receives an address on a private network, but can communicate with the outside world using the host's address. However, nothing on the outside can get services from your guest. If you want your guest to provide services to the rest of your network, you need bridged networking. In this case, both the host and the guest show up on the network at different MAC addresses, and thus can get different IP addresses. It is just like if they were separate computers. Host networking is only if you do not want the guest to communicate with the outside at all. The only machine it can communicate with is the host (or other guests) on a private network. You can actually create multiple network cards for the guest using any combination of the above. I have used host-only networking to provide samba shares to the guest, without exporting them to the rest of the world, plus a bridged network connection for the guest to participate in the LAN. -Richard -- Brett I. Holcomb -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] vmware workstation daemon problem
well for the temp fix i did a simple tweak that seemed to work fine backup purpose mv /etc/init.d/vmware /etc/init.d/old-vmware then just link in the vmware file ln -s /etc/vmware/init.d/vmware /etc/init.d/vmware run the config script vmware-config.pl follow the instructions View this message in context: Re: vmware workstation daemon problem Sent from the gentoo-user forum at Nabble.com.
Re: [gentoo-user] vmware workstation daemon problem
On 1/14/06, Halo0784 (sent by Nabble.com) [EMAIL PROTECTED] wrote: well for the temp fix i did a simple tweak that seemed to work fine backup purpose mv /etc/init.d/vmware /etc/init.d/old-vmware then just link in the vmware file ln -s /etc/vmware/init.d/vmware /etc/init.d/vmware This sounds a bit dangerous to me...if you re-install or update vmware you could get the file intended for /etc/init.d/vmware written to /etc/vmware/init.d/vmware, and then an recusive loop as /etc/init.d/vmware recursively executes itself. -Richard -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] vmware workstation daemon problem
well for /etc/init.d/vmware all it does is makes a pretty output to a call to the /etc/vmware/init.d/vmware file but an append to my earlier post after following the instructions for the install created by the vmware-config script we can use the following commands to clean up what tweak we did mv /etc/init.d/old-vmware /etc/init.d/vmware rc-update add vmware default now it is safe to reboot with the original gentoo script ive done this tweaked install on 3 systems so far and all have been 100% safe and installed correctly infact im useing IE6 in a full windows xp install running in vmware as i post this =) all with a very big smile to know that windows will no longer die when i dont want it to View this message in context: Re: vmware workstation daemon problem Sent from the gentoo-user forum at Nabble.com.
Re: [gentoo-user] vmware workstation daemon problem
This post came at a good time. I had just installed vmplayer on my XP box at work so I could run Linux and have some real mail and news programs. So I decided to try it on gentoo. Emerged it and it wouldn't configure - kept whining it couldn't stop vmware - of course not it wasn't running. I did what you suggested in the first post and got it to configure. I then did what you suggested here. However, when I do /etc/init.d/vmware the first time it did this: * Starting VMware services: [ ok ] * Virtual machine monitor [ !! ] * Virtual ethernet [ !! ] * Bridged networking on /dev/vmnet0 [ !! ] * Host-only networking on /dev/vmnet1 (background)[ ok ] * Host-only networking on /dev/vmnet8 (background)[ ok ] * NAT service on /dev/vmnet8 [ !! ] After that I get this when I try and start vmware. [EMAIL PROTECTED] init.d # /etc/init.d/vmware start VMware Player is installed, but it has not been (correctly) configured for the running kernel. To (re-)configure it, invoke the following command: /opt/vmware/player/bin/vmware-config.pl. If I run vmware-config.pl it complains it can't stop it. I even repeated the steps in your first post. Any ideas on what might be wrong? Thanks. On Sunday 15 January 2006 00:50, Halo0784 (sent by Nabble.com) wrote: well for /etc/init.d/vmware all it does is makes a pretty output to a call to the /etc/vmware/init.d/vmware file but an append to my earlier post after following the instructions for the install created by the vmware-config script we can use the following commands to clean up what tweak we did mv /etc/init.d/old-vmware /etc/init.d/vmware rc-update add vmware default now it is safe to reboot with the original gentoo script ive done this tweaked install on 3 systems so far and all have been 100% safe and installed correctly infact im useing IE6 in a full windows xp install running in vmware as i post this =) all with a very big smile to know that windows will no longer die when i dont want it to -- View this message in context: http://www.nabble.com/vmware-workstation-daemon-problem-t720417.html#a23866 92 Sent from the gentoo-user forum at Nabble.com. -- Brett I. Holcomb -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] vmware workstation daemon problem
do you have module unloading compiled into your kernel? if not this is needed because of how the /etc/vmware/init.d/vmware script works also a debug check list first check for your vm modules lsmod this should show you your vmmon / vmnet modules also check your /dev folder for your vm files ls -l /dev/vm* this should show you vmmon / vmnet / vmnet0 and so on lastly if you find that you have module unloading support and all the above check out fine do rc-update add vmware default then just reboot a very windows approach to this i know but im lzy and it will do 2 things... 1) shows you that your install is goin good (if u reboot and vmware does'nt work then it aint a good install) 2) deals with any modules that may be loaded in as perment, im sure there may be a better way but ... im lzy =) as you reboot you should see the vm services load with the typical [ok] login then run your vmware as you would normally. View this message in context: Re: vmware workstation daemon problem Sent from the gentoo-user forum at Nabble.com.
Re: [gentoo-user] vmware workstation daemon problem
There is file in the directory /etc/vmware which you have to delete after a configure, for some strange reason. It's a blank file, but unfortunately I can't remember the filename anymore. Pbb something with config in its name. I believe it is called notconfigured and yes it is zero length. The file is /etc/vmware/not_configured. The problem is that /etc/init.d/vmware and /etc/vmware/init.d/vmware disagree about whether the daemons are running or not. When you run vmware-config.pl, it starts the daemons by running /etc/vmware/init.d/vmware. Running /etc/init.d/vmware status will show the daemons are not running, but trying to start that script will fail because they actually are running. This can result in either the not_configured file being recreated, or simply failing to start some of the services. This also seems to be fixed for the current version of VMWare Workstation. -Richard Ok, thanks everyone. That seems like a bug that should be fixed for 4.5 and not require an upgrade. - Grant -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] vmware workstation daemon problem
On 12/11/05, Grant [EMAIL PROTECTED] wrote: Hello, the vmware workstation daemon has always seemed a bit touchy, but it's being persistent this time. When I run: /opt/vmware/workstation/bin/vmware-config.pl the daemon is started properly and I can fully use the application. But when Gentoo tries to start the daemon, 2 of the processes always fail and vmware-config.pl must be run again for it to start properly. Even trying to run 'rc' right after a successful completion of vmware-config.pl fails. When I was using workstation 4.5, I found the best results if you run /etc/vmware/init.d/vmware stop after vmware-config.pl: vmware-config.pl -default /etc/vmware/init.d/vmware stop /etc/init.d/vmware start HTH, -Richard -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] vmware workstation daemon problem
2005/12/11, Richard Fish [EMAIL PROTECTED]: On 12/11/05, Grant [EMAIL PROTECTED] wrote: Hello, the vmware workstation daemon has always seemed a bit touchy, but it's being persistent this time. When I run: /opt/vmware/workstation/bin/vmware-config.pl the daemon is started properly and I can fully use the application. But when Gentoo tries to start the daemon, 2 of the processes always fail and vmware-config.pl must be run again for it to start properly. Even trying to run 'rc' right after a successful completion of vmware-config.pl fails. When I was using workstation 4.5, I found the best results if you run /etc/vmware/init.d/vmware stop after vmware-config.pl: vmware-config.pl -default /etc/vmware/init.d/vmware stop /etc/init.d/vmware start HTH, -Richard -- gentoo-user@gentoo.org mailing list There is file in the directory /etc/vmware which you have to delete after a configure, for some strange reason. It's a blank file, but unfortunately I can't remember the filename anymore. Pbb something with config in its name. Jan -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] vmware workstation daemon problem
At Sun, 11 Dec 2005 23:33:31 +0100 Jan Callewaert [EMAIL PROTECTED] wrote: 2005/12/11, Richard Fish [EMAIL PROTECTED]: On 12/11/05, Grant [EMAIL PROTECTED] wrote: Hello, the vmware workstation daemon has always seemed a bit touchy, but it's being persistent this time. When I run: /opt/vmware/workstation/bin/vmware-config.pl the daemon is started properly and I can fully use the application. But when Gentoo tries to start the daemon, 2 of the processes always fail and vmware-config.pl must be run again for it to start properly. Even trying to run 'rc' right after a successful completion of vmware-config.pl fails. When I was using workstation 4.5, I found the best results if you run /etc/vmware/init.d/vmware stop after vmware-config.pl: vmware-config.pl -default /etc/vmware/init.d/vmware stop /etc/init.d/vmware start HTH, -Richard -- gentoo-user@gentoo.org mailing list There is file in the directory /etc/vmware which you have to delete after a configure, for some strange reason. It's a blank file, but unfortunately I can't remember the filename anymore. Pbb something with config in its name. I believe it is called notconfigured and yes it is zero length. allan -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] vmware workstation daemon problem
On 12/11/05, Allan Gottlieb [EMAIL PROTECTED] wrote: At Sun, 11 Dec 2005 23:33:31 +0100 Jan Callewaert [EMAIL PROTECTED] wrote: 2005/12/11, Richard Fish [EMAIL PROTECTED]: On 12/11/05, Grant [EMAIL PROTECTED] wrote: Hello, the vmware workstation daemon has always seemed a bit touchy, but it's being persistent this time. When I run: /opt/vmware/workstation/bin/vmware-config.pl the daemon is started properly and I can fully use the application. But when Gentoo tries to start the daemon, 2 of the processes always fail and vmware-config.pl must be run again for it to start properly. Even trying to run 'rc' right after a successful completion of vmware-config.pl fails. When I was using workstation 4.5, I found the best results if you run /etc/vmware/init.d/vmware stop after vmware-config.pl: vmware-config.pl -default /etc/vmware/init.d/vmware stop /etc/init.d/vmware start HTH, -Richard -- gentoo-user@gentoo.org mailing list There is file in the directory /etc/vmware which you have to delete after a configure, for some strange reason. It's a blank file, but unfortunately I can't remember the filename anymore. Pbb something with config in its name. I believe it is called notconfigured and yes it is zero length. The file is /etc/vmware/not_configured. The problem is that /etc/init.d/vmware and /etc/vmware/init.d/vmware disagree about whether the daemons are running or not. When you run vmware-config.pl, it starts the daemons by running /etc/vmware/init.d/vmware. Running /etc/init.d/vmware status will show the daemons are not running, but trying to start that script will fail because they actually are running. This can result in either the not_configured file being recreated, or simply failing to start some of the services. This also seems to be fixed for the current version of VMWare Workstation. -Richard -- gentoo-user@gentoo.org mailing list
