i've been thinking the same thing today, while trying to tweak the kids' new Lucid -- btw, i don't know if there's an easier way to do this (if there is, i hope someone chimes in) -- but on the kids' account, i couldn't ``import'' anything. instead, i had to access the virtual machines i set up from my own account by doing this in VirtualBox Puel v. 3.2.6:
fyi -- this did not work with a live cd i made a ``snapshot'' of (that is still accessible in my account). it only worked with an OS that i installed... dunno why but that's what happened.
S T E P . 1
File >> Virtual Media Manager >> Hard Disks >> Add >>
then i chose the
.vdi file i'd made from my own account earlier >> then hit ``OK''
S T E P . 2
then i created a not really ``New'' virtual machine like this:
New (blue button) >> Next >>
Name | OS | Version (your virtual machine) | Next >> Memory ... | Next >>
Boot Hard Disk (Check) | Use existing hard disk (check radio box) | pick .vdi file previously made >>
Finish
S T E P . 3
hit ``Start'' (green arrow)
- - -
that loaded up the vdi files i had already made and booted straight into the machines i had previously installed (the live cd snapshot gave me a boot error or something). the one thing that irritates me is that i didn't see a software app i had installed on one of the virtual machines. whether that was because it only had ``windows admin'' privileges, i don't know (but it wouldn't surprise me). i have to try another old app to see where that story goes; or perhaps a virtualbox expert could share some tips
ps: in the beginning i thought it was a permissions issue too... the kids' account had ``plugdev'' access so i couldnt figure out why i didn't see the vdi files i made when i went to ``import''. so i changed the permissions on the vdi file (which is probably unnecessary -- i'll have to check) before i found out all i had to do was go into the virtual media manager and repeat the process, minus the OS installation drama.
Bookmarks