View Single Post
Posts: 1,225 | Thanked: 1,905 times | Joined on Feb 2011 @ Quezon City, Philippines
#17
Originally Posted by davedickson View Post
Oh, and on second thoughts (now I have had my morning coffee) you wouldn't need to chop up the hardware, pre-allocated space, memory and load balancing might help with that, you wouldn't have to assign memory/other resources on a VM by VM basis, if your using one VM it would run with all the hardware available, until you wanted to use the other one, and unless your loading (running apps on) both at the same time it wouldn't be an issue, but for most people it would be a case of only using one VM at a time anyway......

Like the other day, I was messing around with workstation (which is installed on my works Win7) and I wanted to convert .vdi to .vmdk
Dynamic allocation
...means a bigger HV, probably a balloon driver for the guests too. BTW, I just ran Maverick this morning on an old Celeron machine with 128 MB RAM. It was painful, even if I had a MX440 to help out.

I really don't know what you'd like to run in a HV that you can't run in a chroot. Probably quick-switching between {Android,Desktop-Ubuntu/Debian/Gentoo/LFS/Redhat/Fedora/Arch,MeeGo,Maemo}. BRB, buying a 64 GB uSDXC. I think we're going to need the r/w speeds and raw flash size.
__________________
N9 PR 1.3 Open Mode + kernel-plus for Harmattan
@kenweknot, working on Glacier for Nemo.