![virtualbox linux image small virtualbox linux image small](https://i.stack.imgur.com/5v9Ra.png)
- #Virtualbox linux image small update
- #Virtualbox linux image small driver
- #Virtualbox linux image small full
- #Virtualbox linux image small windows 10
- #Virtualbox linux image small portable
It is a professional, enterprise grade solution that runs on Windows, Linux, Macintosh, and Solaris hosts. sonicsteve Posts: 5 Joined: 8.VirtualBox is a Net Reliant favorite when it comes to virtualization. That led me to wonder about doing the same with Windows, and the portability that might be gained from using virtual machines. It creates a virtual disk and boots from it. The closest I could compare to would be WUBI from Ubuntu. The next question I wanted to answer is this, what would a windows guest perform like if it hypothetically had no host OS sucking power from it. It's exactly that question that caused me to wonder if this might work. I'm not sure exactly how much overhead would be needed to load up just the necessary linux host software in order to get a fully functioning Windows guest. Sure, this approximation of type 1 might save you a bit of memory and a bit of disk space on the host, but I'm not convinced that is very important.
#Virtualbox linux image small full
Even though you are running a Linux with no gui, you still need full graphics drivers, otherwise you have no functionality to provide the guest (unless of course the guest also has no GUI!).įrankly, I don't see what the big deal is.
![virtualbox linux image small virtualbox linux image small](https://i.stack.imgur.com/FtFI0.png)
Sonicsteve wrote:Run a Linux Host with no gui, it would have latest Kernel, video drivers, sound, networking etc, they would all preload
#Virtualbox linux image small windows 10
Sep 2008, 17:09 Primary OS: MS Windows 10 VBox Version: PUEL Guest OSses: Mostly XP mpack Site Moderator Posts: 35364 Joined: 4. However AFAICS there would be no static linking, so hopefully no confusion between the two projects. Linux is the epitome of GPL projects, VirtualBox is a proprietary license. I assume there would be no legal impediments: i.e.
#Virtualbox linux image small portable
You are right that a particular OS image could be portable between hypervisors (that is true whether type 1 or 2 is used), but ISTM that with a type 1 minimal Linux you have to pay more attention to the host OS, not less, as this host OS is not one your new users will have installed already, nor will it be supported by someone else: you would have to maintain this host OS as a separate project (it sounds to me like a spinoff distro of some existing Linux).
![virtualbox linux image small virtualbox linux image small](https://www.pcmobitech.com/wp-content/uploads/2016/01/Install-guest-edition.png)
#Virtualbox linux image small driver
You don't, for example, get network or graphics card functions by magic: somebody has to write the device driver which supports a particular card. The appropriate functionality (proper device drivers) has to be implemented by somebody, so if not the guest then it has to be the host. They do care, they just don't run directly on the real hardware. Sonicsteve wrote:Virtual machines don't care about the hardware they are run on I know there would be problems and cons to deal with but nothing ventured nothing gained. So it seemed like an interesting idea to try out in theory at least. With Virtual machines I don't believe I would need nearly as many images, to restore a system I copy a vdi file. For each different configuration I need a new image. Some of the boards have multiple images because some were imaged using sata drives, some with IDE, some with XP some with windows 7. I have 150 computers and likely 10 different motherboards spread across the 150. Virtual machines don't care about the hardware they are run on, while at present I have a different clonezilla image for each mainboard in school.
#Virtualbox linux image small update
and also update the version of Virtualbox. From time to time you would update the Linux version, like kernels etc. If you can load a super minimalist Linux, that then loads virtualbox, that would then load your OS of choice, you would have a platform that could make deployment of the OS much easier. Here are my reasons for wanting to test this idea. So can this be done, or do we need to wait for the hypervisor that virtualbox is working on? Re-installation would be a snap, just copy a VDI file or re-image the drive with a clonezilla image of a preloaded virtualbox. Instead one image for each purpose would work instead of multiple images for multiple purposes, on each different hardware configuration.Ģ. I would no longer need to have multiple windows images on my clonezilla server for every different hardware configuration. It would be a virtualbox linux of sorts I suppose.ġ. However I would love to test an Idea like this out. Is there a way to boot up a scaled down Linux, that directly loads Virtualbox, that then can load various images on a local hard drive? I know that there would be various disadvantages to doing this, such as 3d support and perhaps even many others that I'm not yet aware of. I know that Virtualbox is developing it's own hypervisor, but I have a related question from a slightly different angle.