That's very great! It seems that the binary i686-pc-linux-gnu.zip could be downloaded, please check that!
Thank you in advance! Cheers, Jie At 2012-08-08 00:48:41,"Rom Walton" <[email protected]> wrote: >Done. > >----- Rom > >-----Original Message----- >From: David Anderson [mailto:[email protected]] >Sent: Friday, August 03, 2012 12:32 PM >To: Rom Walton >Cc: Jai >Subject: Re: [boinc_dev] shared directory problem with vboxwrapper > >Rom: >Remember to post compiled versions of the wrapper (at least for whatever >platforms Jai needs) and to update the doc. >-- David > >On 03-Aug-2012 9:25 AM, Rom Walton wrote: >> I've commited the bug fix and requested change: >> - VBOX: Do not perform the hardware virtualization check when the >> guest VM is 64-bit. 64-bit guest vms require hardware >> virtualization >> and should fail without it. >> - VBOX: Implement the <copy_to_shared/> directive in the >> vbox_job.xml file. >> if <copy_to_shared>init_data.xml</copy_to_shared> is set, the > >> wrapper will >> copy the init_data.xml file to the shared directory before >> the VM is launched. >> >> ----- Rom >> >> -----Original Message----- >> From: [email protected] >> [mailto:[email protected]] On Behalf Of Rom Walton >> Sent: Thursday, August 02, 2012 7:32 PM >> To: Jai; [email protected] >> Subject: Re: [boinc_dev] shared directory problem with vboxwrapper >> >> David's solution is the better solution, I'll get that implemented >> tonight. >> >> Good catch on the bug, your right VirtualBox requires VT-x/AMD-V >> support for 64-bit Guest OSs. I'll fix that too. >> >> I'm a little fuzzy on the exact details, but if I remember correctly >> VirtualBox throws an error when you attempt to create a shared >> directory on the host machine that contains the VM guest image of the >> VM you are modifying. I'll see if I can get the error code. >> >> ----- Rom >> >> -----Original Message----- >> From: [email protected] >> [mailto:[email protected]] On Behalf Of Jai >> Sent: Thursday, August 02, 2012 7:08 PM >> To: [email protected] >> Subject: Re: [boinc_dev] shared directory problem with vboxwrapper >> >> The more ways to share files, the better it is. And It works to use >> <enable_floppyio> to share init_data.xml. >> Also, I don't get what is the problem if we use the slot directory as >> shared directory? Rom, could you please tell me more details? >> >> By the way, I think there is a bug here in file vbox.cpp ( The line >> number: 704): >> >> if ((vm_cpu_count == "1") || >> (!strstr(aid.host_info.p_features, "vmx") && >> !strstr(aid.host_info.p_features, "svm"))) { >> >> if I start a VM with one processor and a 64bits OS, it will fail for >> sure, because 64bits VM requires VT support. Please check that. >> >> >> >> Cheers, >> Jie >> >> >> >> >> >> At 2012-08-03 06:06:44,"David Anderson" <[email protected]> >wrote: >>> Let's add an element to the vbox config file >>> <copy_to_shared>filename</copy_to_shared> >>> telling it to copy the given file into shared/ >>> >>> For VMs that don't use shared/, we could have >>> <copy_to_floppyio>filename</copy_to_floppyio> >>> which is a generalization of <enable_floppyio> >>> >>> -- David >>> >>> On 02-Aug-2012 10:10 AM, Rom Walton wrote: >>> >>>> 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. >>> _______________________________________________
_______________________________________________ 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.
