lazarus Posted September 19, 2004 Report Share Posted September 19, 2004 I am running MD 10.1 (host) with vmware 4.5.2. After running vmware-config.pl, all works as it should. On later boot of machine, starting vmware I get a message that vmware is not configured properly for my running kernel. Hence, I run the config script again and it works fine. anyone have ideas why I need to rerun the config script with every boot. It worked fine with MD 10.0 and kernel 2.6.4 Link to comment Share on other sites More sharing options...
Guest maury77 Posted October 12, 2004 Report Share Posted October 12, 2004 I have the same problem have you idea ? I configured vmware and it's Ok but after boot it don't run briged Starting VMware services: Virtual machine monitor OK ] Virtual ethernet OK ] Bridged networking on /dev/vmnet0 [FAILED ] Host-only networking on /dev/vmnet1 (background) OK ] e WHEN I RUN WMARE, it tell me: 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. So I must reconfgure vmware evry boot of machine if i wanto use it I try to use the vmware with Host-Only and not briged but I virtual machine doesn't navigate in the lan. Help me S.O Mandrake 10.1 kernel 2.6.8.1 eth0 for local lan eth1 for ADSL This confuguration works with mandrake 10 and kernel 2.6.4 Link to comment Share on other sites More sharing options...
Guest maury77 Posted October 14, 2004 Report Share Posted October 14, 2004 I found the solution of the problem http://wiki.archlinux.org/index.php/Installing%20Vmware With this vmware works fine Link to comment Share on other sites More sharing options...
Guest mythief Posted November 23, 2004 Report Share Posted November 23, 2004 i have same problem but i cant still solve it pls help ... can u write answer here ... how can i configure my vmware ? Link to comment Share on other sites More sharing options...
Guest maury77 Posted November 28, 2004 Report Share Posted November 28, 2004 i have same problem but i cant still solve it pls help ... can u write answer here ... how can i configure my vmware ? <{POST_SNAPBACK}> VMware installs on ArchLinux pretty well, but its not totally straight forward. 1) First you need to create some folders. mkdir /etc/rc.d/vmware.d mkdir /etc/rc.d/vmware.d/rc0.d mkdir /etc/rc.d/vmware.d/rc1.d mkdir /etc/rc.d/vmware.d/rc2.d mkdir /etc/rc.d/vmware.d/rc3.d mkdir /etc/rc.d/vmware.d/rc4.d mkdir /etc/rc.d/vmware.d/rc5.d mkdir /etc/rc.d/vmware.d/rc6.d 2) Start the vmware installation 3) When it asks where the directories for rc0.d thru rc6.d are, use /etc/rc.d/vmware.d 3) When it asks where the init directory is, use /etc/rc.d 4) It will probably say that the modules supplied dont match the kernal version and asks you if you want to compile it, do yes. 5) If it complains that the gcc compiler is of a different version and that if you use it, your virtual machines will likely crash, select yes as it seems to work anyway. You cannot complete the installation if you say no to this. 6) The rest of the install should work pretty well. 7) There is now a vmware init script in /etc/rc.d. you can add this to your daemons list if you want. I personally dont do this, but if you intend to use the vmware network's when not actually using vmware, then you will need to do this. You will need to start it before you can run vmware though. 8) To start vmware, you just do vmware from a console window, or create a shortcut or menu item however you like. Leave the /etc/rc.d/vmare.d/ folders there, because it is needed whenever you perform vmware-config.pl. Remember, if the kernel is changed or updated, you will need to run vmware-config.pl again. There is a problem with vmware unable to run correctly after a reboot. I am trying to find a permenant fix to this, but have managed to get by with running vmware-config.pl again each time I reboot. I'll update when I have a better solution. Kernel 2.6 and udev. Follow the steps above and then: 1 - modify udev config. edit /etc/udev/rules.d/00-myrules.rules and add 2 lines: # tty devices KERNEL="tty[0-9]*", NAME="vc/%n", SYMLINK="%k" # floppy devices KERNEL="fd[0-9]*", NAME="floppy/%n" , SYMLINK="fd%n" 2 - start/stop script it takes care of devices and start vmware, also stop vmware and remove dev entries), call it, for examples, mkvmdev, chmod it 755 and put in /etc/rc.d: #!/bin/sh . /etc/rc.conf . /etc/rc.d/functions case "$1" in start) stat_busy "Creating /dev entries for vmware and start" mknod /dev/vmnet0 c 119 0 mknod /dev/vmnet1 c 119 1 mknod /dev/vmnet2 c 119 2 mknod /dev/vmnet3 c 119 3 mknod /dev/vmnet4 c 119 4 mknod /dev/vmnet5 c 119 5 mknod /dev/vmnet6 c 119 6 mknod /dev/vmnet7 c 119 7 mknod /dev/vmnet8 c 119 8 mknod /dev/vmnet9 c 119 9 chmod 0600 /dev/vmnet0 chmod 0600 /dev/vmnet1 chmod 0600 /dev/vmnet2 chmod 0600 /dev/vmnet3 chmod 0600 /dev/vmnet4 chmod 0600 /dev/vmnet5 chmod 0600 /dev/vmnet6 chmod 0600 /dev/vmnet7 chmod 0600 /dev/vmnet8 chmod 0600 /dev/vmnet9 mknod /dev/parport0 c 99 0 mknod /dev/parport1 c 99 1 mknod /dev/parport2 c 99 2 mknod /dev/parport3 c 99 3 chmod 0600 /dev/parport0 chmod 0600 /dev/parport1 chmod 0600 /dev/parport2 chmod 0600 /dev/parport3 mknod /dev/vmmon c 10 165 chmod 0660 /dev/vmmon /etc/rc.d/vmware start ;; stop) stat_busy "Removing /dev entries and stop vmware" /etc/rc.d/vmware stop rm /dev/vmnet0 rm /dev/vmnet1 rm /dev/vmnet2 rm /dev/vmnet3 rm /dev/vmnet4 rm /dev/vmnet5 rm /dev/vmnet6 rm /dev/vmnet7 rm /dev/vmnet8 rm /dev/vmnet9 rm /dev/parport0 rm /dev/parport1 rm /dev/parport2 rm /dev/parport3 ;; restart) $0 stop $0 start ;; *) echo "usage: $0 {start|stop|restart}" esac exit 0 2 - Modify /etc/rc.conf Add mkvmdev to daemons in your rc.conf, and remember to remove vmware from rc.conf. If you prefere delete the lines that launch vmware from mkvmdev and leave in rc.conf, you choose. Last edited on Wednesday, August 25, 2004 4:24:25 pm. Link to comment Share on other sites More sharing options...
Guest Cbrduck Posted December 9, 2004 Report Share Posted December 9, 2004 I had a quite similar problem, solved by this.... You are running udev or devfs. At the beginning of /etc/init.d/vmware, add the following line immediately below lines starting with '#' for a in `seq 0 9`; do mknod /dev/vmnet$a c 119 $a; done Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now