[opensuse] Update of VMware ?
Hi. When I want to upgrade VMware on my opensuse 10.2, i get the following:
rpm -Uvh VMware-workstation-5.5.4-44386.i386.rpm
error: can't create transaction lock on /var/lib/rpm/__db.000 How do I continue from here ? -- Med venlig hilsen / Best regards Erik Jakobsen erik_ja@mail.tele.dk openSuSE 10.2 (i586) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Erik Jakobsen escribió:
Hi.
When I want to upgrade VMware on my opensuse 10.2, i get the following:
rpm -Uvh VMware-workstation-5.5.4-44386.i386.rpm
error: can't create transaction lock on /var/lib/rpm/__db.000
How do I continue from here ?
you need to be root to perform that operation ;) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Cristian Rodriguez R. wrote:
you need to be root to perform that operation ;)
Hi Cristian. I had the idea I was, but I wasn't. Now it works. Thanks! -- Med venlig hilsen / Best regards Erik Jakobsen erik_ja@mail.tele.dk openSuSE 10.2 (i586) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Erik Jakobsen wrote:
Hi Cristian.
I had the idea I was, but I wasn't. Now it works. Thanks!
I now have that problem: You must read and accept the End User License Agreement to continue. Press enter to display it. Do you accept? (yes/no) yes Thank you. Configuring fallback GTK+ 2.4 libraries. In which directory do you want to install the mime type icons? [/usr/share/icons] What directory contains your desktop menu entry files? These files have a .desktop file extension. [/usr/share/applications] In which directory do you want to install the application's icon? [/usr/share/pixmaps] Trying to find a suitable vmmon module for your running kernel. None of the pre-built vmmon modules for VMware Workstation is suitable for your running kernel. Do you want this program to try to build the vmmon module for your system (you need to have a C compiler installed on your system)? [yes] yes Using compiler "/usr/bin/gcc". Use environment variable CC to override. What is the location of the directory of C header files that match your running kernel? [/lib/modules/2.6.18.8-0.3-xen/build/include] Extracting the sources of the vmmon module. Building the vmmon module. Using 2.6.x kernel build system. make: Entering directory `/tmp/vmware-config0/vmmon-only' make -C /lib/modules/2.6.18.8-0.3-xen/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. modules make[1]: Entering directory `/usr/src/linux-2.6.18.8-0.3-obj/i386/xen' make -C ../../../linux-2.6.18.8-0.3 O=../linux-2.6.18.8-0.3-obj/i386/xen modules CC [M] /tmp/vmware-config0/vmmon-only/linux/driver.o CC [M] /tmp/vmware-config0/vmmon-only/linux/hostif.o /tmp/vmware-config0/vmmon-only/linux/hostif.c: In function ‘HostIF_APICBase’: /tmp/vmware-config0/vmmon-only/linux/hostif.c:2479: error: ‘FIX_APIC_BASE’ undeclared (first use in this function) /tmp/vmware-config0/vmmon-only/linux/hostif.c:2479: error: (Each undeclared identifier is reported only once /tmp/vmware-config0/vmmon-only/linux/hostif.c:2479: error: for each function it appears in.) /tmp/vmware-config0/vmmon-only/linux/hostif.c: In function ‘HostIF_APIC_ID’: /tmp/vmware-config0/vmmon-only/linux/hostif.c:2531: error: ‘FIX_APIC_BASE’ undeclared (first use in this function) make[4]: *** [/tmp/vmware-config0/vmmon-only/linux/hostif.o] Error 1 make[3]: *** [_module_/tmp/vmware-config0/vmmon-only] Error 2 make[2]: *** [modules] Error 2 make[1]: *** [modules] Error 2 make[1]: Leaving directory `/usr/src/linux-2.6.18.8-0.3-obj/i386/xen' make: *** [vmmon.ko] Error 2 make: Leaving directory `/tmp/vmware-config0/vmmon-only' Unable to build the vmmon module. For more information on how to troubleshoot module-related problems, please visit our Web site at "http://www.vmware.com/download/modules/modules.html" and "http://www.vmware.com/support/reference/linux/prebuilt_modules_linux.html". Execution aborted. I have run the: cd /usr/src/linux make cloneconfig make prepare What's wrong ? -- Med venlig hilsen / Best regards Erik Jakobsen erik_ja@mail.tele.dk openSuSE 10.2 (i586) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Saturday 30 June 2007 10:54:13 Erik Jakobsen wrote:
Erik Jakobsen wrote:
Hi Cristian.
I had the idea I was, but I wasn't. Now it works. Thanks!
I now have that problem:
<snipped>
make[4]: *** [/tmp/vmware-config0/vmmon-only/linux/hostif.o] Error 1 make[3]: *** [_module_/tmp/vmware-config0/vmmon-only] Error 2 make[2]: *** [modules] Error 2 make[1]: *** [modules] Error 2 make[1]: Leaving directory `/usr/src/linux-2.6.18.8-0.3-obj/i386/xen' make: *** [vmmon.ko] Error 2 make: Leaving directory `/tmp/vmware-config0/vmmon-only' Unable to build the vmmon module.
For more information on how to troubleshoot module-related problems, please visit our Web site at "http://www.vmware.com/download/modules/modules.html" and "http://www.vmware.com/support/reference/linux/prebuilt_modules_linux.html"
First of all, can you double check that your running kernel version matches the kernel source as above. You're not running the Xen kernel by any chance are you?
Execution aborted.
I have run the:
cd /usr/src/linux make cloneconfig make prepare
What's wrong ?
At the very simplest, the script cannot build the vmmon kernel module :-) The real question, of course, is why is it exiting out. VMware workstation is pretty straightforward on 10.2. If it's still failing miserably, you could try using the any-any update from here: http://en.opensuse.org/Setting_up_VMware_on_SUSE_Linux#Download_and_Apply_vm... Hope this helps, Jon -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Jonathan Ervine wrote: Hi Jon and thanks for your reply.
the kernel source as above. You're not running the Xen kernel by any chance are you?
First of all, can you double check that your running kernel version matches Sure I can:
Linux lajka3 2.6.18.8-0.3-default #1 SMP Tue Apr 17 08:42:35 UTC 2007 i686 athlon i386 GNU/Linux But I'm not sure it should be SMP, and cannot remember what SMP is ? I'm not sure, that I ran Xen kernel at the point of updating VMware. Could be, because after a reboot -yes you are reading right :-) - I could run the vmware-config.pl ok
At the very simplest, the script cannot build the vmmon kernel module :-) The real question, of course, is why is it exiting out. VMware workstation is pretty straightforward on 10.2. If it's still failing miserably, you could try using the any-any update from here: http://en.opensuse.org/Setting_up_VMware_on_SUSE_Linux#Download_and_Apply_vm...
Hope this helps, Jon
Then I came to the point where I could start up VMware, but got this: "The network bridge on device /dev/vmnet0 is temporarily down because the bridged Ethernet interface is down". What should I do now ? -- Med venlig hilsen / Best regards Erik Jakobsen erik_ja@mail.tele.dk openSuSE 10.2 (i586) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
I would not install VMWare from the RPM packages, I've never had much luck with that. Download the source and install (it's still very simple). Once this is done then run the any-any-update and you should be fine. Also what version of VMWare are you trying to install? Ben On Saturday 30 June 2007 08:00, Erik Jakobsen wrote:
Jonathan Ervine wrote:
Hi Jon and thanks for your reply.
the kernel source as above. You're not running the Xen kernel by any chance are you?
First of all, can you double check that your running kernel version matches
Sure I can:
Linux lajka3 2.6.18.8-0.3-default #1 SMP Tue Apr 17 08:42:35 UTC 2007 i686 athlon i386 GNU/Linux
But I'm not sure it should be SMP, and cannot remember what SMP is ?
I'm not sure, that I ran Xen kernel at the point of updating VMware.
Could be, because after a reboot -yes you are reading right :-) - I could run the vmware-config.pl ok
At the very simplest, the script cannot build the vmmon kernel module :-) The real question, of course, is why is it exiting out. VMware workstation is pretty straightforward on 10.2. If it's still failing miserably, you could try using the any-any update from here: http://en.opensuse.org/Setting_up_VMware_on_SUSE_Linux#Download_and_Apply _vmware-any-any-update
Hope this helps, Jon
Then I came to the point where I could start up VMware, but got this:
"The network bridge on device /dev/vmnet0 is temporarily down because the bridged Ethernet interface is down".
What should I do now ?
-- Med venlig hilsen / Best regards Erik Jakobsen erik_ja@mail.tele.dk openSuSE 10.2 (i586)
-- How much can you know about yourself, you've never been in a fight? I don't wanna die without any scars. So come on; hit me -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Ben Kevan wrote:
I would not install VMWare from the RPM packages, I've never had much luck with that.
Download the source and install (it's still very simple).
Once this is done then run the any-any-update and you should be fine.
Also what version of VMWare are you trying to install?
Ben
Hi Ben. Thanks for your reply. As you can read from my reply, it succeded with the rpm package. The VMware version I installed is the: VMware-workstation-5.5.4-44386.i386.rpm -- Med venlig hilsen / Best regards Erik Jakobsen erik_ja@mail.tele.dk openSuSE 10.2 (i586) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Saturday 30 June 2007 16:00:07 Erik Jakobsen wrote:
Jonathan Ervine wrote:
Hi Jon and thanks for your reply.
the kernel source as above. You're not running the Xen kernel by any chance are you?
First of all, can you double check that your running kernel version matches
Sure I can:
Linux lajka3 2.6.18.8-0.3-default #1 SMP Tue Apr 17 08:42:35 UTC 2007 i686 athlon i386 GNU/Linux
But I'm not sure it should be SMP, and cannot remember what SMP is ?
I'm not sure, that I ran Xen kernel at the point of updating VMware.
Could be, because after a reboot -yes you are reading right :-) - I could run the vmware-config.pl ok
OK - good to know that the script itself is now working as expected.
At the very simplest, the script cannot build the vmmon kernel module :-) The real question, of course, is why is it exiting out. VMware workstation is pretty straightforward on 10.2. If it's still failing miserably, you could try using the any-any update from here: http://en.opensuse.org/Setting_up_VMware_on_SUSE_Linux#Download_and_Apply _vmware-any-any-update
Hope this helps, Jon
Then I came to the point where I could start up VMware, but got this:
"The network bridge on device /dev/vmnet0 is temporarily down because the bridged Ethernet interface is down".
What should I do now ?
After running the vmware-config.pl script, did it build the networking module correctly? (vmnet.ko) The script should build vmnet.ko and then make sure it is loaded. The VMware daemon should also be automatically started by the script as well. Try running /etc/init.d/vmware start as root to make sure this is running. Also does lsmod | grep vmnet show that vmnet.ko is listed? If not, maybe modprobe vmnet might help (but this shouldn't be necessary). As regards the comment about using the tarball for VMware - you can do this, but I've never had any problems with the RPM that couldn't be fixed with the any-any patch. My own opinion is that the RPM install is the easiest way to run VMware on RPM based distributions. Jon -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Jonathan Ervine wrote:
Could be, because after a reboot -yes you are reading right :-) - I could run the vmware-config.pl ok
OK - good to know that the script itself is now working as expected.
Yes nice to know.
After running the vmware-config.pl script, did it build the networking module correctly? (vmnet.ko) The script should build vmnet.ko and then make sure it is loaded. The VMware daemon should also be automatically started by the script as well. Try running /etc/init.d/vmware start as root to make sure this is running. Also does lsmod | grep vmnet show that vmnet.ko is listed? If not, maybe modprobe vmnet might help (but this shouldn't be necessary).
As regards the comment about using the tarball for VMware - you can do this, but I've never had any problems with the RPM that couldn't be fixed with the any-any patch. My own opinion is that the RPM install is the easiest way to run VMware on RPM based distributions.
Here's the result, and this is nothing to yell hurrah for :-) # locate vmnet.ko /lib/modules/2.6.18.8-0.3-default/misc/vmnet.ko lajka3:~ # /etc/init.d/vmware start Starting VMware services: Virtual machine monitor failed Virtual ethernet failed Bridged networking on /dev/vmnet0 failed Host-only networking on /dev/vmnet1 (background) done Host-only networking on /dev/vmnet8 (background) done NAT service on /dev/vmnet8 failed lajka3:~ # lsmod | grep vmnet vmnet 45484 12 lajka3:~ # modprobe vmnet FATAL: Module vmnet not found. Then Jon, what's the next step now ?
Jon
-- Med venlig hilsen / Best regards Erik Jakobsen erik_ja@mail.tele.dk openSuSE 10.2 (i586) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Erik Jakobsen wrote:
lajka3:~ # modprobe vmnet FATAL: Module vmnet not found.
Try running depmod -a as root. It sounds like it doesn't know about the new module. -- Joe Morris Registered Linux user 231871 running openSUSE 10.2 x86_64 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Joe Morris (NTM) wrote:
Erik Jakobsen wrote:
lajka3:~ # modprobe vmnet FATAL: Module vmnet not found.
Try running depmod -a as root. It sounds like it doesn't know about the new module.
Hello Joe, and thanks for the info. The result: # depmod -a lajka3:~ # modprobe vmnet lajka3:~ # /etc/init.d/vmware start VMware Workstation is installed, but it has not been (correctly) configured for the running kernel. To (re-)configure it, invoke the following command: /usr/bin/vmware-config.pl. lajka3:~ # lsmod | grep vmnet vmnet 45484 12 I tried to run the vmware-config.pl, but had no success with it ! # vmware-config.pl Making sure services for VMware Workstation are stopped. Stopping VMware services: Virtual machine monitor done Bridged networking on /dev/vmnet0 done DHCP server on /dev/vmnet1 done Host-only networking on /dev/vmnet1 done DHCP server on /dev/vmnet8 done NAT service on /dev/vmnet8 done Host-only networking on /dev/vmnet8 done Virtual ethernet failed Unable to stop services for VMware Workstation Execution aborted. lajka3:~ # /etc/init.d/vmware stop Stopping VMware services: Virtual machine monitor done Bridged networking on /dev/vmnet0 done DHCP server on /dev/vmnet1 done Host-only networking on /dev/vmnet1 done DHCP server on /dev/vmnet8 done NAT service on /dev/vmnet8 done Host-only networking on /dev/vmnet8 done Virtual ethernet failed lajka3:~ # vmware-config.pl Making sure services for VMware Workstation are stopped. Stopping VMware services: Virtual machine monitor done Bridged networking on /dev/vmnet0 done DHCP server on /dev/vmnet1 done Host-only networking on /dev/vmnet1 done DHCP server on /dev/vmnet8 done NAT service on /dev/vmnet8 done Host-only networking on /dev/vmnet8 done Virtual ethernet failed Unable to stop services for VMware Workstation Execution aborted. What am I to do now ?. -- Med venlig hilsen / Best regards Erik Jakobsen erik_ja@mail.tele.dk openSuSE 10.2 (i586) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Saturday 30 June 2007, Erik Jakobsen wrote:
Unable to stop services for VMware Workstation
Execution aborted.
What am I to do now ?.
reboot. -- _____________________________________ John Andersen -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
John Andersen wrote:
reboot.
Hi John. Nice to see all my friends being here :-) I did the reboot, and now I can run the vmware-config.pl. But it's not runnig quite ok: # vmware-config.pl Making sure services for VMware Workstation are stopped. Stopping VMware services: Virtual machine monitor done Bridged networking on /dev/vmnet0 done DHCP server on /dev/vmnet1 done Host-only networking on /dev/vmnet1 done DHCP server on /dev/vmnet8 done NAT service on /dev/vmnet8 done Host-only networking on /dev/vmnet8 done Virtual ethernet done Configuring fallback GTK+ 2.4 libraries. In which directory do you want to install the mime type icons? [/usr/share/icons] What directory contains your desktop menu entry files? These files have a .desktop file extension. [/usr/share/applications] In which directory do you want to install the application's icon? [/usr/share/pixmaps] Trying to find a suitable vmmon module for your running kernel. None of the pre-built vmmon modules for VMware Workstation is suitable for your running kernel. Do you want this program to try to build the vmmon module for your system (you need to have a C compiler installed on your system)? [yes] Using compiler "/usr/bin/gcc". Use environment variable CC to override. What is the location of the directory of C header files that match your running kernel? [/lib/modules/2.6.18.8-0.3-default/build/include] Extracting the sources of the vmmon module. Building the vmmon module. Using 2.6.x kernel build system. make: Entering directory `/tmp/vmware-config1/vmmon-only' make -C /lib/modules/2.6.18.8-0.3-default/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. modules make[1]: Entering directory `/usr/src/linux-2.6.18.8-0.3-obj/i386/default' make -C ../../../linux-2.6.18.8-0.3 O=../linux-2.6.18.8-0.3-obj/i386/default modules CC [M] /tmp/vmware-config1/vmmon-only/linux/driver.o CC [M] /tmp/vmware-config1/vmmon-only/linux/hostif.o CC [M] /tmp/vmware-config1/vmmon-only/common/cpuid.o CC [M] /tmp/vmware-config1/vmmon-only/common/hash.o CC [M] /tmp/vmware-config1/vmmon-only/common/memtrack.o CC [M] /tmp/vmware-config1/vmmon-only/common/phystrack.o CC [M] /tmp/vmware-config1/vmmon-only/common/task.o CC [M] /tmp/vmware-config1/vmmon-only/common/vmx86.o CC [M] /tmp/vmware-config1/vmmon-only/vmcore/moduleloop.o LD [M] /tmp/vmware-config1/vmmon-only/vmmon.o Building modules, stage 2. MODPOST CC /tmp/vmware-config1/vmmon-only/vmmon.mod.o LD [M] /tmp/vmware-config1/vmmon-only/vmmon.ko make[1]: Leaving directory `/usr/src/linux-2.6.18.8-0.3-obj/i386/default' cp -f vmmon.ko ./../vmmon.o make: Leaving directory `/tmp/vmware-config1/vmmon-only' The module loads perfectly in the running kernel. This program previously created the file /dev/vmmon, and was about to remove it. Somebody else apparently did it already. This program previously created the file /dev/parport0, and was about to remove it. Somebody else apparently did it already. This program previously created the file /dev/parport1, and was about to remove it. Somebody else apparently did it already. This program previously created the file /dev/parport2, and was about to remove it. Somebody else apparently did it already. This program previously created the file /dev/parport3, and was about to remove it. Somebody else apparently did it already. This program previously created the file /dev/vmnet0, and was about to remove it. Somebody else apparently did it already. This program previously created the file /dev/vmnet1, and was about to remove it. Somebody else apparently did it already. This program previously created the file /dev/vmnet8, and was about to remove it. Somebody else apparently did it already. You have already setup networking. Would you like to skip networking setup and keep your old settings as they are? (yes/no) [no] Do you want networking for your virtual machines? (yes/no/help) [yes] This program previously created the file /dev/vmnet2, and was about to remove it. Somebody else apparently did it already. This program previously created the file /dev/vmnet3, and was about to remove it. Somebody else apparently did it already. This program previously created the file /dev/vmnet4, and was about to remove it. Somebody else apparently did it already. This program previously created the file /dev/vmnet5, and was about to remove it. Somebody else apparently did it already. This program previously created the file /dev/vmnet6, and was about to remove it. Somebody else apparently did it already. This program previously created the file /dev/vmnet7, and was about to remove it. Somebody else apparently did it already. This program previously created the file /dev/vmnet9, and was about to remove it. Somebody else apparently did it already. Would you prefer to modify your existing networking configuration using the wizard or the editor? (wizard/editor/help) [wizard] The following bridged networks have been defined: Do you wish to configure another bridged network? (yes/no) [no] Do you want to be able to use NAT networking in your virtual machines? (yes/no) [yes] The following NAT networks have been defined: Do you wish to configure another NAT network? (yes/no) [no] Do you want to be able to use host-only networking in your virtual machines? [yes] The following host-only networks have been defined: Do you wish to configure another host-only network? (yes/no) [no] Extracting the sources of the vmnet module. Building the vmnet module. Using 2.6.x kernel build system. make: Entering directory `/tmp/vmware-config1/vmnet-only' make -C /lib/modules/2.6.18.8-0.3-default/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. modules make[1]: Entering directory `/usr/src/linux-2.6.18.8-0.3-obj/i386/default' make -C ../../../linux-2.6.18.8-0.3 O=../linux-2.6.18.8-0.3-obj/i386/default modules CC [M] /tmp/vmware-config1/vmnet-only/driver.o CC [M] /tmp/vmware-config1/vmnet-only/hub.o CC [M] /tmp/vmware-config1/vmnet-only/userif.o CC [M] /tmp/vmware-config1/vmnet-only/netif.o CC [M] /tmp/vmware-config1/vmnet-only/bridge.o CC [M] /tmp/vmware-config1/vmnet-only/procfs.o CC [M] /tmp/vmware-config1/vmnet-only/smac_compat.o SHIPPED /tmp/vmware-config1/vmnet-only/smac_linux.x386.o LD [M] /tmp/vmware-config1/vmnet-only/vmnet.o Building modules, stage 2. MODPOST WARNING: could not open /tmp/vmware-config1/vmnet-only/includeCheck.h: Invalid argument CC /tmp/vmware-config1/vmnet-only/vmnet.mod.o LD [M] /tmp/vmware-config1/vmnet-only/vmnet.ko make[1]: Leaving directory `/usr/src/linux-2.6.18.8-0.3-obj/i386/default' cp -f vmnet.ko ./../vmnet.o make: Leaving directory `/tmp/vmware-config1/vmnet-only' The module loads perfectly in the running kernel. Starting VMware services: Virtual machine monitor done Virtual ethernet done Bridged networking on /dev/vmnet0 done Host-only networking on /dev/vmnet1 (background) done Host-only networking on /dev/vmnet8 (background) done NAT service on /dev/vmnet8 done The configuration of VMware Workstation 5.5.4 build-44386 for Linux for this running kernel completed successfully. You can now run VMware Workstation by invoking the following command: "/usr/bin/vmware". Enjoy, --the VMware team # lsmod | grep vmnet vmnet 45484 12 lajka3:/home/erikja # modprobe vmnet I still have the problem with the bridged Ethernet -- Med venlig hilsen / Best regards Erik Jakobsen erik_ja@mail.tele.dk openSuSE 10.2 (i586) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Sunday 01 July 2007, Erik Jakobsen wrote: ...snip So all of the snipped stuff looks more or less normal.
lajka3:/home/erikja # modprobe vmnet
I still have the problem with the bridged Ethernet
Exactly what problems? Try Nat Ethernet and see if that works for you. You should be able to fire up a virtual machine and change its settings to Nat for a test to see if it will work. Bridged has the additional requirement of having to alias your nic so that it can obtain two IPs on the same network interface. I have seen several instances where that would not work, usually because the ISP would only allow one IP per nic, but also with really cheap routers that had poor dhcp servers. (Some Dlink models). Then if Nat works we can start working on Bridged. -- _____________________________________ John Andersen -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
John Andersen wrote:
Exactly what problems?
Sorry John, I thought I have shown that more up in this thread. Here the message is: "The network bridge on device /dev/vmnet0 is temporarily down because the bridged Ethernet interface is down. The virtual machine may not be able to communicate with the host or with other machines on your network."
Try Nat Ethernet and see if that works for you.
Yes, that works.
You should be able to fire up a virtual machine and change its settings to Nat for a test to see if it will work.
I now can access for instance the Internet.
Bridged has the additional requirement of having to alias your nic so that it can obtain two IPs on the same network interface. I have seen several instances where that would not work, usually because the ISP would only allow one IP per nic, but also with really cheap routers that had poor dhcp servers. (Some Dlink models).
Ok, I cna tell you, that I have not had probs before running with 2 IP's. But that was when I ran it all via a server. Now I use a Netgear WGR614v6 router. For the LAN, I run fixed IP's, as I also did running the server.
Then if Nat works we can start working on Bridged.
I think the time has come :-) -- Med venlig hilsen / Best regards Erik Jakobsen erik_ja@mail.tele.dk openSuSE 10.2 (i586) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
John Andersen wrote:
Then if Nat works we can start working on Bridged.
John!... Will you help me with the Bridged, to see if it can come up ? -- Med venlig hilsen / Best regards Erik Jakobsen erik_ja@mail.tele.dk openSuSE 10.2 (i586) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Sunday 01 July 2007 09:06:18 Erik Jakobsen wrote:
John Andersen wrote:
reboot.
<snipped>
Starting VMware services: Virtual machine monitor done Virtual ethernet done Bridged networking on /dev/vmnet0 done Host-only networking on /dev/vmnet1 (background) done Host-only networking on /dev/vmnet8 (background) done NAT service on /dev/vmnet8 done
The configuration of VMware Workstation 5.5.4 build-44386 for Linux for this running kernel completed successfully.
You can now run VMware Workstation by invoking the following command: "/usr/bin/vmware".
Enjoy,
--the VMware team
As John Andersen mentioned, this all looks pretty much correct. When you run through this script, and define the bridged network(s) - how many have you set up? How many physical ethernet devices do you have? What I've had happen is to have my wired interface (eth0) bridged and then tried to run VMware when on a wireless network. When this has been done, obviously the wired network is not available and you can get a message similar to the one you are reporting. If you want to send along the output of ifconfig -a and ps -eaf | grep vmnet-bridge that might help.
# lsmod | grep vmnet vmnet 45484 12 lajka3:/home/erikja # modprobe vmnet
I still have the problem with the bridged Ethernet
The above is fine - the vmnet module is already loaded, so modprobe vmnet is not necessary. Jon -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Jonathan Ervine wrote:
Bridged networking on /dev/vmnet0 done Host-only networking on /dev/vmnet1 (background) done Host-only networking on /dev/vmnet8 (background) done NAT service on /dev/vmnet8 done
As John Andersen mentioned, this all looks pretty much correct. When you run through this script, and define the bridged network(s) - how many have you set up? How many physical ethernet devices do you have? What I've had happen is to have my wired interface (eth0) bridged and then tried to run VMware when on a wireless network. When this has been done, obviously the wired network is not available and you can get a message similar to the one you are reporting. If you want to send along the output of ifconfig -a and ps -eaf | grep vmnet-bridge that might help.
Hi again Jon. You can see above, that I have set up 2 bridged network. Vmnet1 and vmnet 8. I have one physical ethernet device. Here's the outputs: # ifconfig -a eth3 Link encap:Ethernet HWaddr 00:0B:6A:EC:05:21 inet addr:192.168.1.9 Bcast:255.255.255.255 Mask:255.255.255.0 inet6 addr: fe80::20b:6aff:feec:521/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:15626 errors:0 dropped:0 overruns:0 frame:0 TX packets:12703 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:15271791 (14.5 Mb) TX bytes:1321587 (1.2 Mb) Interrupt:185 Base address:0xc000 lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:1359 errors:0 dropped:0 overruns:0 frame:0 TX packets:1359 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:41221 (40.2 Kb) TX bytes:41221 (40.2 Kb) sit0 Link encap:IPv6-in-IPv4 NOARP MTU:1480 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) vmnet1 Link encap:Ethernet HWaddr 00:50:56:C0:00:01 inet addr:192.168.185.1 Bcast:192.168.185.255 Mask:255.255.255.0 inet6 addr: fe80::250:56ff:fec0:1/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:6 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) vmnet8 Link encap:Ethernet HWaddr 00:50:56:C0:00:08 inet addr:172.16.104.1 Bcast:172.16.104.255 Mask:255.255.255.0 inet6 addr: fe80::250:56ff:fec0:8/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:6 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) # ps -eaf |grep vmnet-bridge root 3323 1 0 07:10 ? 00:00:00 /usr/bin/vmnet-bridge -d /var/run/vmnet-bridge-0.pid /dev/vmnet0 eth0 root 4872 4817 0 09:32 pts/1 00:00:00 grep vmnet-bridge
# lsmod | grep vmnet vmnet 45484 12 lajka3:/home/erikja # modprobe vmnet
I still have the problem with the bridged Ethernet
The above is fine - the vmnet module is already loaded, so modprobe vmnet is not necessary.
Very good. -- Med venlig hilsen / Best regards Erik Jakobsen erik_ja@mail.tele.dk openSuSE 10.2 (i586) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Monday 02 July 2007 08:33:38 Erik Jakobsen wrote:
Jonathan Ervine wrote:
Bridged networking on /dev/vmnet0 done Host-only networking on /dev/vmnet1 (background) done Host-only networking on /dev/vmnet8 (background) done NAT service on /dev/vmnet8 done
As John Andersen mentioned, this all looks pretty much correct. When you run through this script, and define the bridged network(s) - how many have you set up? How many physical ethernet devices do you have? What I've had happen is to have my wired interface (eth0) bridged and then tried to run VMware when on a wireless network. When this has been done, obviously the wired network is not available and you can get a message similar to the one you are reporting. If you want to send along the output of ifconfig -a and ps -eaf | grep vmnet-bridge that might help.
Hi again Jon.
You can see above, that I have set up 2 bridged network. Vmnet1 and vmnet 8. I have one physical ethernet device.
No. The above shows that you have two host-only networks; vmnet1 and vmnet8. Bizarrely you have a NAT network also on vmnet8. Seems a bit odd to me. Your bridged network is running on vmnet0.
Here's the outputs:
# ifconfig -a eth3 Link encap:Ethernet HWaddr 00:0B:6A:EC:05:21 inet addr:192.168.1.9 Bcast:255.255.255.255 Mask:255.255.255.0 inet6 addr: fe80::20b:6aff:feec:521/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:15626 errors:0 dropped:0 overruns:0 frame:0 TX packets:12703 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:15271791 (14.5 Mb) TX bytes:1321587 (1.2 Mb) Interrupt:185 Base address:0xc000
<snipped>
# ps -eaf |grep vmnet-bridge root 3323 1 0 07:10 ? 00:00:00 /usr/bin/vmnet-bridge -d /var/run/vmnet-bridge-0.pid /dev/vmnet0 eth0 root 4872 4817 0 09:32 pts/1 00:00:00 grep vmnet-bridge
OK - so you have a physical ethernet card on eth3 according to ifconfig. Yet VMware is trying to bridge eth0 according to the output above. You'll need to re-run the config script and this time specify eth3 as the brideged device. Hope this helps, Jon -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Mon, 2007-07-02 at 09:00 +0100, Jonathan Ervine wrote:
Here's the outputs:
# ifconfig -a eth3 Link encap:Ethernet HWaddr 00:0B:6A:EC:05:21 inet addr:192.168.1.9 Bcast:255.255.255.255 Mask:255.255.255.0 inet6 addr: fe80::20b:6aff:feec:521/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:15626 errors:0 dropped:0 overruns:0 frame:0 TX packets:12703 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:15271791 (14.5 Mb) TX bytes:1321587 (1.2 Mb) Interrupt:185 Base address:0xc000
<snipped>
# ps -eaf |grep vmnet-bridge root 3323 1 0 07:10 ? 00:00:00 /usr/bin/vmnet-bridge -d /var/run/vmnet-bridge-0.pid /dev/vmnet0 eth0 root 4872 4817 0 09:32 pts/1 00:00:00 grep vmnet-bridge
OK - so you have a physical ethernet card on eth3 according to ifconfig. Yet VMware is trying to bridge eth0 according to the output above. You'll need to re-run the config script and this time specify eth3 as the brideged device.
Have you changed the physical ethernet card because this would occur because of /etc/udev/30-net_persistent_names.rules? -- Dave Cotton <dcotton@linuxautrement.com> -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Dave Cotton wrote:
Have you changed the physical ethernet card because this would occur because of /etc/udev/30-net_persistent_names.rules?
Hi Dave. Yes I have, as it's not the mainboard I originally ran: SUBSYSTEM=="net", ACTION=="add", SYSFS{address}=="00:69:00:0e:10:8f", IMPORT="/lib/udev/rename_netiface %k eth0" SUBSYSTEM=="net", ACTION=="add", SYSFS{address}=="00:0b:6a:66:8b:82", IMPORT="/lib/udev/rename_netiface %k eth1" SUBSYSTEM=="net", ACTION=="add", SYSFS{address}=="00:09:5b:bc:a6:88", IMPORT="/lib/udev/rename_netiface %k eth2" SUBSYSTEM=="net", ACTION=="add", SYSFS{address}=="00:0b:6a:ec:05:21", IMPORT="/lib/udev/rename_netiface %k eth3" Can I change it to eht0, and if so how to do that ? -- Med venlig hilsen / Best regards Erik Jakobsen erik_ja@mail.tele.dk openSuSE 10.2 (i586) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Mon, 2007-07-02 at 10:49 +0200, Erik Jakobsen wrote:
Dave Cotton wrote:
Have you changed the physical ethernet card because this would occur because of /etc/udev/30-net_persistent_names.rules?
Hi Dave.
Yes I have, as it's not the mainboard I originally ran:
SUBSYSTEM=="net", ACTION=="add", SYSFS{address}=="00:69:00:0e:10:8f", IMPORT="/lib/udev/rename_netiface %k eth0" SUBSYSTEM=="net", ACTION=="add", SYSFS{address}=="00:0b:6a:66:8b:82", IMPORT="/lib/udev/rename_netiface %k eth1" SUBSYSTEM=="net", ACTION=="add", SYSFS{address}=="00:09:5b:bc:a6:88", IMPORT="/lib/udev/rename_netiface %k eth2" SUBSYSTEM=="net", ACTION=="add", SYSFS{address}=="00:0b:6a:ec:05:21", IMPORT="/lib/udev/rename_netiface %k eth3"
Can I change it to eht0, and if so how to do that ?
-- Med venlig hilsen / Best regards Erik Jakobsen erik_ja@mail.tele.dk openSuSE 10.2 (i586)
If the other cards no longer exist in the machine delete their details and then change eth3 to eth0 using your favorite editor. Then either reboot or restart the network. -- Dave Cotton <dcotton@linuxautrement.com> -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Dave Cotton wrote:
If the other cards no longer exist in the machine delete their details and then change eth3 to eth0 using your favorite editor.
Then either reboot or restart the network.
Hi Dave. Very nice, and now it works the bridged :-) With this I want to say thanks to all of you, that has helped me. -- Med venlig hilsen / Best regards Erik Jakobsen erik_ja@mail.tele.dk openSuSE 10.2 (i586) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Jonathan Ervine wrote:
Bizarrely you have a NAT network also on vmnet8. Seems a bit odd to me. Your bridged network is running on vmnet0.
Is beacuse I temp. has set VMware to use NAT.
No. The above shows that you have two host-only networks; vmnet1 and vmnet8.
Here's the outputs:
# ifconfig -a eth3 Link encap:Ethernet HWaddr 00:0B:6A:EC:05:21 inet addr:192.168.1.9 Bcast:255.255.255.255 Mask:255.255.255.0 inet6 addr: fe80::20b:6aff:feec:521/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:15626 errors:0 dropped:0 overruns:0 frame:0 TX packets:12703 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:15271791 (14.5 Mb) TX bytes:1321587 (1.2 Mb) Interrupt:185 Base address:0xc000
<snipped>
# ps -eaf |grep vmnet-bridge root 3323 1 0 07:10 ? 00:00:00 /usr/bin/vmnet-bridge -d /var/run/vmnet-bridge-0.pid /dev/vmnet0 eth0 root 4872 4817 0 09:32 pts/1 00:00:00 grep vmnet-bridge
OK - so you have a physical ethernet card on eth3 according to ifconfig. Yet VMware is trying to bridge eth0 according to the output above. You'll need to re-run the config script and this time specify eth3 as the brideged device.
I tried to change to eth3, but did not get the chance to do it I think when I ran the config script: Would you like to skip networking setup and keep your old settings as they are? (yes/no) [no] Do you want networking for your virtual machines? (yes/no/help) [yes] The following bridged networks have been defined: -- Med venlig hilsen / Best regards Erik Jakobsen erik_ja@mail.tele.dk openSuSE 10.2 (i586) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
<snip>
Hello Joe, and thanks for the info.
The result:
# depmod -a lajka3:~ # modprobe vmnet lajka3:~ # /etc/init.d/vmware start VMware Workstation is installed, but it has not been (correctly) configured Unable to stop services for VMware Workstation What am I to do now ?. Erik, This may sound like a dumb question, but are you *sure* you are running WORKSTATION version of VMWare? That version is a not-for-free version (which is certainly worth the money). The correct version for most hobbiest/home/non-commercial people would be VMWare-SERVER which is free. I made a very similar error to what I am seeing with your
Erik Jakobsen wrote: problems and when I tried to stop the free version with my newly downloaded, updated WORKSTATION version, I got the exact same error about not being able to stop Workstation....which is correct, it wasn't running, the free version of SERVER was actually running so of course the script couldn't stop a version not running, hence the error. This *may* be your problem. I was so bull-headed that at first, I downloaded and installed the 'correct' workstation version....then my key wouldn't work. Now, I had paid for a workstation key earlier but I didn't qualify for the upgrade to the new version and I was starting to get angry until I realized I should be angry at myself for being so myopic. If I had read the fine print, I'd have realized that the features I wanted in my paid for version of an earlier version of 'workstation' were now contained in the free version now called 'server'. Richard -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Joe Morris (NTM) wrote: I'm not sure if I'm running the right kernel too. What is the SMP kernel ? -- Med venlig hilsen / Best regards Erik Jakobsen erik_ja@mail.tele.dk openSuSE 10.2 (i586) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Sunday 2007-07-01 at 09:27 +0200, Erik Jakobsen wrote:
I'm not sure if I'm running the right kernel too.
What is the SMP kernel ?
The default kernel is now the smp kernel. If you want the previous style of non smp kernel you have to compile it yourself. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (GNU/Linux) Comment: Made with pgp4pine 1.76 iD8DBQFGh43ptTMYHG2NR9URAhu/AJ4rL3Xw2X7U54pdQKFzqbgXpOTL8ACfb0KH VqcHsORfkSpCkuvZhG5dals= =47G2 -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Carlos E. R. wrote:
The default kernel is now the smp kernel. If you want the previous style of non smp kernel you have to compile it yourself.
Thanks for the information Carlos -- Med venlig hilsen / Best regards Erik Jakobsen erik_ja@mail.tele.dk openSuSE 10.2 (i586) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
participants (9)
-
Ben Kevan -
Carlos E. R. -
Cristian Rodriguez R. -
Dave Cotton -
Erik Jakobsen -
Joe Morris (NTM) -
John Andersen -
Jonathan Ervine -
Richard Creighton