IIRC, there was some sort of locking problem with using the slot directory as the shared directory. VirtualBox explicitly checks for that condition and returns an error.
I suspect it has to do with the disk image being in the same directory. You wouldn't want an 'shared' application to be able to modify the base VM image. You can add the <enable_floppyio/> tag to the vbox config file which will cause the wrapper to create a floppy disk device which contains the contents of the init_data.xml file. You should then be able to read the floppy disk device to get the init_data.xml data. CERN wrote some perl code to do that, see: https://github.com/citizen-cyberscience-centre/cernvmwrapper/tree/master /floppyio-guest I have noticed on some class of machines the block floppy device is marked as read-only, so it is probably best to make a copy of the contents of the floppy device before using it in a read/write fashion. ----- Rom -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Jai Sent: Thursday, August 02, 2012 12:39 PM To: [email protected] Subject: [boinc_dev] shared directory problem with vboxwrapper hi, I am running an application with vboxwrapper. As we know, the wrapper uses the directory "shared" under slot directory to share data between host and guest machine. When the share data is inputs or outputs of the application, everthing should work fine, but if I try to share the data that BOINC client generate, like init_data.xml in slot directory( Actually, my application would like to read this file), it seems there is no way to make it (If you have, please tell me). Also, old versions of BOINC client (it should be before BOINC 7.0, I am not so sure about it) don't support to create a directory in slot direcotry base on logical file name. In other words, old BOINC clients don't support the logical file name like "shared/input1". So, vboxwapper will fail while running with old BOINC client. In summary , to use the "shared" directory under slot directory as the shared directory, it introduces no benifit to the real application except that the slot directory look tidy, only some inconvenience and compatibility problems. So I suggest to directory use the slot as the shared directory, but not the directory under the slot directory. How do you guys think? Cheers, Jie _______________________________________________ boinc_dev mailing list [email protected] http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev To unsubscribe, visit the above URL and (near bottom of page) enter your email address.
