Opened 8 years ago
Last modified 8 years ago
#16684 new defect
VBoxManage.exe extpack command exhausts StdOut buffer
| Reported by: | Schimkat | Owned by: | |
|---|---|---|---|
| Component: | other | Version: | VirtualBox 5.1.20 |
| Keywords: | Cc: | ||
| Guest type: | other | Host type: | Windows |
Description
After having added a license agreement to the extension pack, automating has become quite the challenge. The problem is that the license message hits a 4K limit of the stdout/stderr buffer (which I actually didn't know existed until today).
Consider the following:
%comspec% /C "C:\Program Files\Oracle\VirtualBox\VBoxManage.exe" extpack install --replace Oracle_VM_VirtualBox_Extension_Pack-5.1.20-114628.vbox-extpack 1> %temp%\1.txt 2> %temp%\2.txt
.. which should write the entire license agreement into the %temp%\1.txt file. That does not happen, as the output (and VBoxmanage.exe) halts when hitting a 4K limit. My guess is that the message is sent as one big chunck of data, instead of being flushed each line.
(At first I though that it was my VBS script having trouble, as WScript.Shell actually does a have 4K limit with StdOut / StdErr, but the limit seems to exist in the shell itself)
No .. using --accept-license=xyz.. to circumvent the issues isn't an option (at least I think), as Im automating installation for multiple customers. Please have a look at this strange behavior, and let me know what you think.
Being in automatic installation for multiple users sounds to me like you should not use the PUEL-licensed Extension Pack. Please read the PUEL license and the corresponding FAQ.