virtualbox.org

Greetings. Before I put in a suggestion that "VBoxManage list" should have a --machinereadable optiton like "VBoxManage shwovminfo" does, I wanted to check if anyone knows of a way to automate the info, particularly from "bridgedifs".

Why do you need machinereadable in the list option?
To automate anything in Linux you write a script and run it.

I use a script in my backup routine that reads the "VBoxManage showvminfo" output. It's generated by a program, so all the data should ultimately be in the same places, depending on the line you need to read. Just do some experiments, find out what you want to input and see what showvminfo outputs, and write your program to extract the data:

Perryg wrote:Why do you need machinereadable in the list option?
To automate anything in Linux you write a script and run it.

The "machinereadable" option lets you parse the output better than screen scraping. In the example I gave, bridgedifs, you need to parse the information for each element by looking for blank lines and sucking up spaces at the beginning of each line that doesn't start at the left column. Your argument would also apply to showvminfo, which someone was nice enough to add machinereadable to.