|
VMWareImageDebian051
Debian VMWare Image contributed by Federico Tomasczik
Package: http://webbase-design.de/projekte/Debian4.0r2-OpenMeetings0.5.1.zip Debian4.0r2-OpenMeetings0.5.1.zip MD5: 165a78cb62cf61539d8a318dd1b1df80 Users and passwords User root: root Password: openmeetings Other user: User: openmeetings Password: openmeetings User root MySQL: User: root Password: openmeetings DB Name for OpenMeetings: openmeetings User name for DB: openmeetings Password name for DB: openmeetings User for administrator in Openmeetings User: openmeetings Password: openmeetings Notes: Below are pre-requisites for running the OpenMeetings with VMWare. 1) You need to download VMWare Player: http://www.vmware.com/products/player/ 2) In order to run the OpenMeetings VMWare Image you would need to be either on a DHCP Network so the OpenMeetings VMWare Image can acquire an IP Address or you need to have a static IP Address which can be assigned to the OpenMeetings VMWare Image. If your network is a DHCP Enabled Network the OpenMeetings VMWare Image would automatically be assigned an IP Address at the time of loading, once the VMWare Image is loaded please login to the VMImage and follow the below steps. a) You can know the IP Address of the VMWare Image by typing ifconfig from the terminal. Example: openmeetings# ifconfig eth0 The output will look like: eth0 Link encap:Ethernet direcciónHW 00:16:d4:99:24:51 inet dirección:10.2.1.181 Difusión:10.2.255.255 Máscara:255.255.0.0 dirección inet6: fe80::216:d4ff:fe99:2451/64 Alcance:Vínculo ARRIBA DIFUSIÓN CORRIENDO MULTICAST MTU:1500 Metric:1 RX packets:274854 errors:0 dropped:0 overruns:0 frame:0 TX packets:469015 errors:0 dropped:0 overruns:0 carrier:0 colisiones:0 txqueuelen:1000 RX bytes:40619186 (38.7 MB) TX bytes:690781270 (658.7 MB) Interrupción:16 The IP address for the above example is 10.2.1.181 You can go to this URL http://<YouIPAddress>:5080/openmeetings/ to start/join the OpenMeetings Web Meeting. You can login to OpenMeetings using following data: Username : openmeetings Password : openmeetings If the OpenMeetings VMWare Image do not get the IP address automatically then you need to assign an IP Address to the OpenMeetings VMWare Image: Please follow the below steps to assign a static IP Address to your VMWare Image: Open the file by typing the below command from a terminal openmeetings# pico /etc/network/interfaces This will look like: # The loopback network interface auto lo iface lo inet loopback # The primary network interface auto eth0 iface eth0 inet static address 10.1.0.4 netmask 255.255.0.0 network 10.1.0.0 broadcast 10.1.255.255 gateway 10.1.1.18 dns-nameservers 10.1.0.2 Please note that the hardware address should remain the same as it is for the vmware image. 2. Specify Name Server IP Address in resolv.conf - Open the file by typing the below command from a terminal openmeetings# pico /etc/resolv.conf - Modify the below parameters in the file. nameserver XXX.XXX.XXX.XXX nameserver XXX.XXX.XXX.XXX Restart the Network Service. - Type the below command to restart the network service. openmeetings# /etc/init.d/networking restart Confirm IP Address of your VMWare Image - Type the below command to check IP Address of your VMWare Image openmeetings# ifconfig eth0 Please ensure that you have provided the proper netmask / broadcast ip address / default gateway/ dns server address. Notes: 1) You can enter to Virtual Machine via ssh with root or openmeetings user. 2) If networking not working: rm /etc/udev/rules.d/z25_persistent-net.rules and then reboot (fixed in new image). |
Sign in to add a comment
Awesome, thanks for this. 2 tiny issues I noticed, could be just me. The VMX file needed execute permissions set (on a linux VMware server), or it would error out "Unable to connect to the MKS: You need execute access in order to connect with the VMware Server Console" when opening the VMware console. Also, the network adapter (eth0) disappears from the OS if I change the virtual machine UUID. It still shows in the config but doesn't show in the OS, not sure what the deal is on that...
Hey,
For some reason eth0 won't come up. When trying to start networking I get these errors: SIOCSIFADDR: No such device eth0: ERROR while getting interface flags: No such device eth0: ERROR while getting interface flags: No such device Bind socket to interface: No such device Failed to bring up eth0
Using DHCP. Any ideas? Thanks for this!
Im linx newbie but i hope to be of help as i have faced that issue a few times. This is what i have done to get it working.
1st make sure that your virtual machine as a network card installed. On that specific VM
Then you will need to be root to edit the interfaces file.
in the cmd terminal type $~ nano /etc/network/interfaces
Make sure it looks something like this
# This file describes the network interfaces available on your system # and how to activate them. For more information, see interfaces(5).
# The loopback network interface auto lo iface lo inet loopback
# The primary network interface auto eth0 iface eth0 inet static
If it doesn't modify it, nothing to loose as it will make your machine have a static ip address.
Change the ip address's to match your local ip's.
Then do this cmd $~ /etc/init.d/networking restart
If that fails then try the following -
where it says "eth0" change it to "eth1" followed by $~ /etc/init.d/networking restart. You can change that number until it works. Unlike me please make sure that you have a network card install specifically on that Virtual Machine. :D
Hope this is of any help.
Cheers
Josh @imalltech.com
I also encountered the same problem that Grether did. But i did notice that the issue is with Vmware itself. I have had the same issue happen to me using different linux distro's in VM testings. In fact every time i move the VMX file to a different station i have to reconfigure the nic interfaces.
Well at least it seems to me that its a vmware setting of some sort. Hope this was of any help!
Cheers
Josh @imalltech.com
ppt not workin
I’m using Debian Etch as a guest OS under VMWare. When you copy the VM (to another machine or another instance on the same machine), VMWare wants to give it a new UID (you should let it so you don’t end up with duplicate machines). A side effect is that you get a new ethernet MAC address. In Debian Etch, a side effect of that is that it thinks you have a new network card but it doesn’t forget about the old network card, so instead of the network interface being eth0, it is now eth1. And the next time you copy the VM, it is eth2, and so on.
It is really a pretty simple fix, once you know where to look. The clue is that udev is what is remembering the old MAC address. In my VMs, the addresses were in:
/etc/udev/rules.d/z25_persistent-net.rules
It is just a plain text file. Delete the lines with the old MAC addresses and change the last one to be eth0.
I'm downloading image right now and unfortunatelu the speed isn't really that much. Could you share the file via ie. bittorrent -network so we could both get the image faster and participate to sharing.
Thanks, chinket.yap, your suggestion worked a treat. Just worth mentioning that you need a system restart of the vmware instance before the settings take effect. I tried /etc/init.d/networking restart and this wasn't enough ...
Thanks