The VM and associated software licences are part of it and no need for additional licences for the same software on a new machine. Once the licence is part of the VM it becomes inherent and can be installed in a new machine without hindrance. No more having to licence the software that was originally licensed in the original or post original Vbox. I once had a VM that was not accessible and luckily I had a version of it backed up.Īnother added benefit is licencing.
It's very important to have a good working copy of your VM(.ova) available if things should become corrupted or not work for any reason.
I always make sure to have an export of the VM once in a couple of weeks to ensure that if something happens I can re-nstall/import the last working Vbox I had. Additionally I also remote desktop into my work PC and work in my VM that way. Then at home I can import it to do any additional work that I might do. What I usually do is export my current VM(Vbox) to a file (.ova), then save it to a USB or portable drive, my VM is almost 12 gigs now and growing so its not emailable. The OS and software dictate that, but the beauty is being able to run it on any machine as you know. I am an automation engineer and require specific items in order to do my work. It's a great way to allow others to do what you know and share the knowledge of a development or just have the portability and power you need. I have moved my VBox appliance many times from one laptop or desktop computer and simple adjustments are required based on the machine you wish to run it on. Either way you're still not going to share out one disk image for multiple virtualizers accessing it at the same time that I know of. VB also support snapshots, but I've never tried having multiple systems running with remote access since VB usually seemed aimed more for workstations rather than running headless servers. Also remember that if you had a number of people hitting a virtual image you may slow it down to a crawl.Īnother option might be to create a bare-metal VMWare ESXi system, install your virtual machines with snapshots taken of what image you want it saved to and roll it back periodically and enable your virtualized Windows systems to allow remote access to each virtual machine so each developer has their own environment to work in. Otherwise you'd need to keep copying a "template" to the developer's systems, but it's a lot of data to push. Those are the solutions that strike me off the top of my head. You could try using the virtualized image with RDP access (if the guest OS supports multiple access) or you can copy the image out (but it's a LOT of disk space.) Or you can set up a basic image and install something like Deep Freeze or a similar product that would keep "resetting" the image to a clean slate at each reboot. You can't run multiple copies of VB with the same drive image you'd corrupt it. You mean to keep resetting it to a clean slate or.?
0 kommentar(er)
