You are not logged in.
Pages: 1
I just want to get confirmation that I've correctly understood this as I've never done anything with virtualization before. I'll explain it the way that I think it works and would like you to correct me where I'm wrong.
I'm running Arch x86_64. If I install virtualbox, I could create a second system within my system, including a 32-bit system. I could, for example, install WinXP and run anything that runs on WinXP, or install a 32-bit Arch to gain access to native 32-bit applications such as Flash and Skype. The "hard disks" of the virtual system are actually files on the real system. It should be possible to encrypt these in order to have a fully encrypted virtual system. A virtual system can also be used as a sandbox for testing configurations etc.
Is that accurate?
Also, are there any clear pitfalls to watch out for? Would anyone recommend something other than virtualbox? (virtualbox seemed to have the most features, but I'm not sure that I'm looking at the right things on the comparisons that I've seen)
My Arch Linux Stuff • Forum Etiquette • BBCode and Emoticons • Community Ethos - Arch is not for everyone
Offline
for example, install WinXP and run anything that runs on WinXP
The main exception here would be anything requiring 3D acceleration.
Would anyone recommend something other than virtualbox?
Vbox didn't support amd64 guests until the recent 2.0, so I used to use qemu mostly. I'm still more comfortable with qemu cli parameters since there are some things unavailable in the vbox gui (tcp forwarding.. if there's a way, I still haven't figured it out). I assume VBoxManage can also provide the same functionality, if not more.. I just haven't taken the time to learn it.
Offline
Thanks AD28.
(even though I'd subscribed to this thread, I somehow missed your reply)
My Arch Linux Stuff • Forum Etiquette • BBCode and Emoticons • Community Ethos - Arch is not for everyone
Offline
Pages: 1