virtualbox, was: Re: Kali Linux

[John G Heim]

I am using virtualbox to try to create a version of grml that comes up 
I've been using virtualbox to try to create a version of grml that comes 
up talking. I have virtual machines for straight debian, grml32, and 
grml64. It's pretty nice. I'm not sure if I  prefer virtualbox or vmware 
player. Virtualbox has a really powerful and well docummented command 
line interface. So I was able to script the process of creating virtual 
machines.  Virtualbox stores it's config files in an xml file and it has 
a warning at the top of each file not to edit it. VMware stores it 
config files in plain text that is easily edited in any text editor. 
I've many times changed the boot order of a virtual machine by just 
going in and editing it in the config file. But if you're not 
intimidated by xml, you could probably edit the config files for 
virtualbox too.

One other thing that I really liked about virtualbox was that you can 
get a screen capture. At first, when I have having trouble getting 
virtual machines to start, I'd take a screen cap and run it through 
tesseract to see why it was stuck. I was even able to check the network 
configuration on a Windwos virtual machine this way. I was pretty sure 
the Windows virtual machine was running so I pressed the keys to open a 
command window, windows+r, cmd. Then in the command window, I type 
"ipconfig /all". Then I got the screen cap and was able to check the 
network config. Pretty cool.

But it turns out vmware can do that too.
http://stackoverflow.com/questions/2255477/how-to-make-screenshots-using-vmware-tool-vmrun


On 05/03/2015 05:27 PM, Igor Gueths wrote:
> I'm actually running VirtualBox on a Debian host:
> igueths at holly:~$ uname -a
> Linux holly 3.16.0-4-amd64 #1 SMP Debian 3.16.7-ckt7-1 (2015-03-01) x86_64
> GNU/Linux
> On Fri, May 01, 2015 at 10:23:31PM -0700, Don Raikes wrote:
>> So vbox works with nvda but not with jaws?  I am a jaws user primarily, but I could if necessary switch to nvda for working with vbox I suppose.
>> -----Original Message-----
>> From: Gregory Nowak [mailto:greg at gregn.net]
>> Sent: Friday, May 01, 2015 3:42 PM
>> To: Speakup is a screen review system for Linux.
>> Subject: Re: virtualbox, was: Re: Kali Linux
>>
>> Early on, virtualbox was using qt3 under which the GUI was indeed not accessible. This has changed since they started using qt4, and that was at least two years ago if not more. When I used to use the builds of virtualbox using qt4 under windows xp, and wineyes 6.1, it was quiet accessible. Nowadays, I'm using virtualbox 4.3.x on windows7 home premium with the latest nvda, and that is quiet accessible also.
>>
>> Greg
>>
>>
>> On Fri, May 01, 2015 at 08:29:01AM -0700, Don Raikes wrote:
>>> Igor et al,
>>>
>>> How are you getting virtualbox to work on windows? The last time I tried it (about a year ago) the gui was totally inaccessible with jaws.  I would really appreciate knowing how others are getting it to work since my laptop can't handle vmware workstation maybe it will handle virtualbox instead.
>>
>>
>> --
>> web site: http://www.gregn.net
>> gpg public key: http://www.gregn.net/pubkey.asc
>> skype: gregn1
>> (authorization required, add me to your contacts list first) If we haven't been in touch before, e-mail me before adding me to your contacts.
>>
>> --
>> Free domains: http://www.eu.org/ or mail dns-manager at EU.org _______________________________________________
>> Speakup mailing list
>> Speakup at linux-speakup.org
>> http://linux-speakup.org/cgi-bin/mailman/listinfo/speakup
>> _______________________________________________
>> Speakup mailing list
>> Speakup at linux-speakup.org
>> http://linux-speakup.org/cgi-bin/mailman/listinfo/speakup
>>
>> --
>> This message has been scanned for viruses and
>> dangerous content by MailScanner, and is
>> believed to be clean.
>>
>

-- 
John Heim, jheim at math.wisc.edu, skype:john.g.heim