CEDEUS Server Setup - Revision history

StefanS: /* general info */

2014-12-28T16:08:23Z

‎general info

StefanS: /* Assigning VM parameters */

2014-12-17T20:26:53Z

‎Assigning VM parameters

StefanS: /* Assigning VM parameters */

2014-12-17T20:25:46Z

‎Assigning VM parameters

StefanS: /* Assigning VM parameters */

2014-12-17T20:25:08Z

‎Assigning VM parameters

StefanS: /* Assigning VM parameters */

2014-12-17T20:23:24Z

‎Assigning VM parameters

StefanS: /* Testing the serial connection on host computer */

2014-12-17T19:14:53Z

‎Testing the serial connection on host computer

StefanS: /* Assigning VM parameters */

2014-12-17T17:19:24Z

‎Assigning VM parameters

StefanS: /* Assigning VM parameters */

2014-12-17T17:17:31Z

‎Assigning VM parameters

StefanS: /* Assigning VM parameters */

2014-12-17T15:44:52Z

‎Assigning VM parameters

StefanS: /* Assigning VM parameters */

2014-12-17T15:07:38Z

‎Assigning VM parameters

@@ Line 4: / Line 4: @@
 == general info ==
-* both machines have 12 cores and 32GB RAM
+* both machines have 12 cores (6 real ones) and 32GB RAM
 * cedeusdb has 4 TB as Raid10 (4 HDs with 2TB)
 * cedeusgeonode has 2 TB as Raid 1 (2 HDs with 2TB)

@@ Line 124: / Line 124: @@
 <pre>
   COMMAND     PID     USER   FD   TYPE DEVICE SIZE/OFF NODE NAME
-  VBoxHeadl 28951 ssteinig   19u   CHR   4,64      0t0 1114 /dev/ttyS1
+  VBoxHeadl 30378 ssteinig   19u   CHR   4,65      0t0 1113 /dev/ttyS1
 </pre>
 :=> this means that the VBox VM accesses the serial port.
 :=> Note: if the VM is '''shutdown''', then the command <code>"sudo lsof /dev/ttyS*"</code> will not show anything - as the VM does '''not access the serial port!'''

@@ Line 109: / Line 109: @@
 ** <code>VBoxManage modifyvm --uart< 1-N > off|< I/O base > < IRQ ></code> : to set the serial parameters for the client system
 ** <code>VBoxManage modifyvm --uartmode< 1-N > < arg > </code> : to decide how the serial connection is used on the host system (e.g. disconnected, routing to physical serial device on the host, write to file, pipe...)
-* As my APC UPS is connected to tts1 I used then (taken from http://www.linuxquestions.org/questions/slackware-14/virtualbox-serial-port-setup-frustration-586971/):
+* As my APC UPS is connected to ttyS0 I used then (taken from http://www.linuxquestions.org/questions/slackware-14/virtualbox-serial-port-setup-frustration-586971/):
 **<code>VBoxManage modifyvm opensuse132 --uart1 0x2f8 3</code>  => to set up ttyS1/COM1
 **<code>VBoxManage modifyvm opensuse132 --uartmode1 /dev/ttyS1</code> => to link it to physical port ttyS1

@@ Line 110: / Line 110: @@
 ** <code>VBoxManage modifyvm --uartmode< 1-N > < arg > </code> : to decide how the serial connection is used on the host system (e.g. disconnected, routing to physical serial device on the host, write to file, pipe...)
 * As my APC UPS is connected to tts1 I used then (taken from http://www.linuxquestions.org/questions/slackware-14/virtualbox-serial-port-setup-frustration-586971/):
-**<code>VBoxManage modifyvm opensuse132 --uart1 0x2f8 4</code>  => to set up ttyS1/COM1
+**<code>VBoxManage modifyvm opensuse132 --uart1 0x2f8 3</code>  => to set up ttyS1/COM1
 **<code>VBoxManage modifyvm opensuse132 --uartmode1 /dev/ttyS1</code> => to link it to physical port ttyS1
 * when trying to startup the VM, I got this message:
@@ Line 118: / Line 118: @@
 *: Hence, I added myself to the group ''dialout'' with <code>sudo usermod -a -G dialout ssteinig</code>. Important: do a logout and then  login again to activate the new settings.
 * So after my opensuse132 VM did start now, I did another <code>dmesg | grep ttyS</code> on the ''opensuse132'' VM, an it did return the following info below - while previously it did not return anything:
-*: <pre>[    1.251960] 00:03: ttyS1 at I/O 0x2f8 (irq = 4, base_baud = 115200) is a 16550A</pre>
+*: <pre>[    1.251960] 00:03: ttyS1 at I/O 0x2f8 (irq = 3, base_baud = 115200) is a 16550A</pre>
 *: Hence, it seems like serial port access is working now :)
 * Testing:

@@ Line 109: / Line 109: @@
 ** <code>VBoxManage modifyvm --uart< 1-N > off|< I/O base > < IRQ ></code> : to set the serial parameters for the client system
 ** <code>VBoxManage modifyvm --uartmode< 1-N > < arg > </code> : to decide how the serial connection is used on the host system (e.g. disconnected, routing to physical serial device on the host, write to file, pipe...)
-* so I used then (taken from http://www.linuxquestions.org/questions/slackware-14/virtualbox-serial-port-setup-frustration-586971/):
+* As my APC UPS is connected to tts1 I used then (taken from http://www.linuxquestions.org/questions/slackware-14/virtualbox-serial-port-setup-frustration-586971/):
-**<code>VBoxManage modifyvm opensuse132 --uart1 0x3f8 4</code>  => to set up ttyS0/COM1
+**<code>VBoxManage modifyvm opensuse132 --uart1 0x2f8 4</code>  => to set up ttyS1/COM1
-**<code>VBoxManage modifyvm opensuse132 --uartmode1 /dev/ttyS0</code> => to link it to physical port ttyS0
+**<code>VBoxManage modifyvm opensuse132 --uartmode1 /dev/ttyS1</code> => to link it to physical port ttyS1
 * when trying to startup the VM, I got this message:
 *: ''Error: failed to start machine. Error message: Cannot open host device '/dev/ttyS0' for read/write access. Check the permissions of that device ('/bin/ls -l /dev/ttyS0'): Most probably you need to be member of the device group. Make sure that you logout/login after changing the group settings of the current user (VERR_ACCESS_DENIED).''
-** using <code>/bin/ls -l /dev/ttyS0</code> I got this output:
+** using <code>/bin/ls -l /dev/ttyS1</code> I got this output:
-*: <pre>crw-rw---- 1 root dialout 4, 64 Dec 15 13:55 /dev/ttyS0</pre>
+*: <pre>crw-rw---- 1 root dialout 4, 64 Dec 15 13:55 /dev/ttyS1</pre>
 *: Hence, I added myself to the group ''dialout'' with <code>sudo usermod -a -G dialout ssteinig</code>. Important: do a logout and then  login again to activate the new settings.
 * So after my opensuse132 VM did start now, I did another <code>dmesg | grep ttyS</code> on the ''opensuse132'' VM, an it did return the following info below - while previously it did not return anything:
-*: <pre>[    1.251960] 00:03: ttyS0 at I/O 0x3f8 (irq = 4, base_baud = 115200) is a 16550A</pre>
+*: <pre>[    1.251960] 00:03: ttyS1 at I/O 0x2f8 (irq = 4, base_baud = 115200) is a 16550A</pre>
 *: Hence, it seems like serial port access is working now :)
 * Testing:
@@ Line 124: / Line 124: @@
 <pre>
   COMMAND     PID     USER   FD   TYPE DEVICE SIZE/OFF NODE NAME
-  VBoxHeadl 28951 ssteinig   19u   CHR   4,64      0t0 1114 /dev/ttyS0
+  VBoxHeadl 28951 ssteinig   19u   CHR   4,64      0t0 1114 /dev/ttyS1
 </pre>
 :=> this means that the VBox VM accesses the serial port.
 :=> Note: if the VM is '''shutdown''', then the command <code>"sudo lsof /dev/ttyS*"</code> will not show anything - as the VM does '''not access the serial port!'''

@@ Line 100: / Line 100: @@
 </code>
-* in earlier test we could also connect (unfortunately only once) to the UPS with <code>minicom -s -c on</code> . and then doing the appropriate settings (9600bps, 8N1, no flow control)
+* in earlier test we could also connect to the UPS with <code>minicom -s -c on</code> . and then doing the appropriate settings (9600bps, 8N1, no flow control)
 * in theory (using a modem or so) on can also do <code>echo "id" > /dev/ttyS0</code>

@@ Line 126: / Line 126: @@
   VBoxHeadl 28951 ssteinig   19u   CHR   4,64      0t0 1114 /dev/ttyS0
 </pre>
-*: this means that the VBox VM accesses the serial port.
+:=> this means that the VBox VM accesses the serial port.
-*: Note: if the VM is '''shutdown''', then the command <code>"sudo lsof /dev/ttyS0"</code> will not show anything - as the VM does '''not access the serial port'''!
+:=> Note: if the VM is '''shutdown''', then the command <code>"sudo lsof /dev/ttyS0"</code> will not show anything - as the VM does '''not access the serial port!'''