Virtualbox QPKG V and +

Transcription

1 Virtualbox QPKG V and April 2012 Purpose of this document : Explain the news in QPKG management I Create an Escape solution to Disable, at boot time, virtualbox, without the need to accede the QNAP. II New modules management (using dkms/depmod) III Return to standard init shell in Virtualbox IV Optional change the default PATH for VM V Use a configuration file for parameters during installation Open a door for updating yourself virtualbox and phpvirtualbox in the future (if you don't want waiting for QPKG Update) in around ten commands. Father_Mande 1/5 13. April 2012

2 I The Escape solution : The problem is : if you want to disable a QPKG during boot phase, for example if you load the bad modules and crash the QNAP, you have only the possibility to quick as possible do a telnet or ssh connect and try to change qpkg.conf using setcfg or an editor you have the time between the end of first boot phase and the moment when QPKG start few second The solution is : do during QPKG starting phase, a test (try a connection) and if the test is OK (connection established) disable immediately the QPKG so nothing is started. The previous solution (that, in fact, don't work) was to test a file in USB device, but this don't work as well. The actual solution is pretty easy : A ) download or install on a PC a version of nc (netcat) B ) open a console (cmd in windows) C ) start nc with waiting for login on a certain port ex. : nc -l -p 5555 This command start nc waiting for a connection on port 5555 from anywhere. Windows 7 special if you have an error, try again with a L (uppercase) and wait for firewall message, after you can start the normal command. D ) start the QNAP, during QPKG starting phase, QPKG try to open a connection to an IP IP_Escape (IP of the PC running nc -l) and a port Port_Escape, if it's OK, the connection is closed in 1 sec the nc on PC stop, the QPKG is disabled if it's NOT OK nothing in done the QPKG continue to run Parameters : IP_Escape, Port_Escape can be set using vboxmgr command in QNAP or using the parameters file (qpkgvbox.ini) during install (see hereafter). IP_Escape= (any real IP) Port_Escape=5555 Father_Mande 2/5 13. April 2012

3 II New modules management : Remember : Due to low level of some system call, in modules the modules can't be the same for all x86 models as usual. We have identify four (4) family (based on kernel) QNAP running in 32 bits old : TS-x39 ; SS-xxx ; TS-509 new : TS-259 and TS-459 QNAP running in 64 bits old : TS-809 new TS-x59 (from 559) ; TS-x79 It's independent of Processor capabilities. Before we use insmod to load the modules, and create modules by hand (manual compile) In we use depmod, and use dkms to create the modules and the depmod descriptors. Dkms (Dynamic Kernel Module Support) is the standard mode use by virtualbox to create modules. How you can validate parameters to choice the good modules and inform the installation script : In a console do : uname -a (search i686 (32 bits) or x86_64 (64 bits)) cat /etc/config/model_name.conf (Internal Model name) based on result and table here before enter parameters (qpkgvbox.ini) : Processor=x86 (or x86_64) QNAP_Model=new (or old) Father_Mande 3/5 13. April 2012

4 III Init shell : Under /etc/init.d (inside the chroot vbox) before we use modified shell qnapvboxdrv qnapvboxweb-service In and above we use the standard one provide by virtualbox team so no risk to add an error. IV Change the PATH for VM : (user request) Before the Path to put VM are /share/my_vm and it's a shared resource In and above you can (first install) change the default Path, if you decide to change it, you MUST create it in a safe place (not /share for ex.) BEFORE install. The folder must have full access for all (chmod 777. ). If you Upgrade from a previous version. 1 first export your existing Virtual Machine. 2 start virtualbox, so the new folder is empty (no VM available). 3 import the VM This is OPTIONAL, so if the parameters in installation file is not set the default (shared resource) /share/my_vm is keep. Parameters (qpkgvbox.ini) is like : VM_PATH=/share/My_VM (here I declare the same, so it's equal to omit the parameter) (TODO migration from shared resource to private Path) Father_Mande 4/5 13. April 2012

5 V Install configuration file : QNAP don't have method to change parameters during QPKG installation process. To do this, You (must) create a file in /share/public and named the file qpkgvbox.ini (lowercase) The file can be created in DOS / Windows (bloc-note) or Linux format (CRLF or LF delimited). Sample : [qpkgvbox] # x86 or x86_64 Processor=x86 # old or new # old TS-x09 TS-x39 SS-xxx # new TS-x59 TS-x79 QNAP_Model=new # IP of system running nc to escape IP_Escape= # Port nc listen Port_Escape=5556 # Path of where are VM VM_PATH=/share/MD0_DATA/my_own_vm_place The file is optional, if the file don't exist QPKG try to identify the model and processor (but the list is limited to model I know) IP_Escape is set to (so not usable) Port_Escape is set to 5555 VM_PATH is set to /share/my_vm If the file exist (and is readable) The [qpkgvbox] is mandatory QNAP_Model and Processor are mandatory Others are optional (default are same that line here before) # are comment Father_Mande 5/5 13. April 2012