Thank you for taking your time to explain things in details and tell us how things are related and affecting each other. This is what we really need. I am appreciate you A LOT!!!
24:02 Tagging the .iso file: There is an easy way (well, I am running VirtualBox Version 5.2.20 r125813 (Qt5.6.2), and it is easy). After creating your virtual machine, you can simply start it, without telling VirtualBox anythink about an .iso file. Upon this first, initial start, VirtualBox will prompt you for the .iso file. You simply click the folder icon, and navigate to your .iso file, and then continue with the boot process. Cheers!
I'm a Windows guy and recently transferred over to our HPC team that works primarily out of Linux.. it's been a challenge, but fun. I think I enjoy doing this more than the Windows side, although I still have a ton to learn. Thanks for the video, Eli.
@18:06 (various networking options): If I understand the bridging option, it works like this: Assume you have two physical computers behind your physical router, and your router protects your two computers via NAT. However, your two computers can see each other. This is a common home setup. When you have VirtualBox add a VM, and choose the bridging option, VirtualBox creates the VM as a third computer, that also sits behind your physical router. This means you now have three computers (two physical and one virtual) that are all protected by your physical router's NATing -- but all three of your computers can see each other. This differs from VirtualBox's NAT networking option. With the NAT networking option, VirtualBox acts as yet another NAT router, keeping your host (physical machine) from seeing the VM. In this setup, if you create two or more VMs, then those VMs can see each other, but your host machine cannot see the VMs. And in VirtualBox's default NAT option, it acts similarly to the NAT networking option, except that if you create two or more VMs, then those VMs will not see each other. In all cases described above, all machines (physical and virtual) can access the internet. Did I get this right? I would like to know, because I would like to be sure that my understanding is not flawed. Please correct any mistakes. Cheers!
I run Virtualbox on a 16 GB Ryzen 3 2200G since May 2019, the years before I used a 8 GB Phenom II X4 B97 (4x 3.2 GHz from 2009). I you use Virtualbox for one desktop, it works fine. Normally you are the only one to start up work and whether you do that on one PC or divide it over 2 or 3 VMs the load effect on a modern CPU will be almost the same. After installing a VM you should install in the VM, the Virtualbox Guest Additions to get the full advantages of Virtualbox. To complement the good video. My Vbox settings for Linux Desktop VMs are: - I allow the copy/paste between host and VM and vice versa. - I assign all cores (in my cases 4) to the VM to run the VM at max speeds. The Host Linux scheduler can handle high load and overloads of the VM if needed. It is like dealing with overload on a single OS with some high load processes. - For the display I assign the max size 128 MB and I choose 3D acceleration to play simple games like "Extreme Tux Racer" in the VM. - I use 1.5 GB of RAM for most Linux OSes, but 1 GB for e.g. Peppermint, Windows XP and Lubuntu. I only use 2 GB, if I keep many application open at the same time in that VM. For Windows 7 and 10 I use now 3 GB and in the past 2 GB. - I use Bridged Networking since it is more efficient. On the Phenom it saved me between 5 and 10% of the CPU load during transfers. In bridged networking the VM talks more directly to your Router. - I always set the USB to 3.0 and - I always use one shared folder, to have an easy way to share data between Host and VM and between VMs. I share all my data between Host and VMs (music, videos, emails, downloads, office docs etc) and thus I limit the Vbox disk size to 16 GB for Linux. Normally only half of the Vbox disk is used, since I store all data in the Shared Folder.
It will fail and tell you to do that. A quick google will get the specifics. A pain in the butt if you did not know though. like right now I cannot remember exactly what setting you change. I think security tab and then enable 7 something. smh
@@absolutethinker7764 if eli had only done vms on a mac or a pc that already had virtualisation switched on, he may not be aware of it, it caught me out
Great video. I noticed that if you leave the virtual optical disk blank and when you launch the VM and there is no OS already installed then it will prompt your for a ISO to mount. Just browse to try the ISO and it will boot off of it.
I have an AMD 2400g APU, the iGPU, that I want to use for the host OS and a dedicated GPU that I want to use exclusively for my Windows 10 virtual machine. My question is do I connect the first monitor for the host OS directly to the motherboard and the second monitor to the graphics card for the virtual machine and do I have to enable integrated graphics for the APU in the BIOS in order to use it because it is disable by default if a graphics card is detected in the PCI slot?
Like thinking back in the early 2000s when you have single and dualcore serverblades with max 512mb-1gb ram which housed 1 server you can now with virtualization and modern XEONS or EPYC and 10-40GBps run like 30 servers or more
thank you for taking your time on this subject, most people make this process a 5 min video
Thank you for taking your time to explain things in details and tell us how things are related and affecting each other. This is what we really need. I am appreciate you A LOT!!!
24:02
Tagging the .iso file:
There is an easy way (well, I am running VirtualBox Version 5.2.20 r125813 (Qt5.6.2), and it is easy).
After creating your virtual machine, you can simply start it, without telling VirtualBox anythink about an .iso file.
Upon this first, initial start, VirtualBox will prompt you for the .iso file. You simply click the folder icon, and navigate to your .iso file, and then continue with the boot process.
Cheers!
I'm a Windows guy and recently transferred over to our HPC team that works primarily out of Linux.. it's been a challenge, but fun. I think I enjoy doing this more than the Windows side, although I still have a ton to learn. Thanks for the video, Eli.
@18:06 (various networking options):
If I understand the bridging option, it works like this:
Assume you have two physical computers behind your physical router, and your router protects your two computers via NAT.
However, your two computers can see each other.
This is a common home setup.
When you have VirtualBox add a VM, and choose the bridging option, VirtualBox creates the VM as a third computer, that also sits behind your physical router.
This means you now have three computers (two physical and one virtual) that are all protected by your physical router's NATing -- but all three of your computers can see each other.
This differs from VirtualBox's NAT networking option.
With the NAT networking option, VirtualBox acts as yet another NAT router, keeping your host (physical machine) from seeing the VM. In this setup, if you create two or more VMs, then those VMs can see each other, but your host machine cannot see the VMs.
And in VirtualBox's default NAT option, it acts similarly to the NAT networking option, except that if you create two or more VMs, then those VMs will not see each other.
In all cases described above, all machines (physical and virtual) can access the internet.
Did I get this right?
I would like to know, because I would like to be sure that my understanding is not flawed.
Please correct any mistakes.
Cheers!
I run Virtualbox on a 16 GB Ryzen 3 2200G since May 2019, the years before I used a 8 GB Phenom II X4 B97 (4x 3.2 GHz from 2009). I you use Virtualbox for one desktop, it works fine. Normally you are the only one to start up work and whether you do that on one PC or divide it over 2 or 3 VMs the load effect on a modern CPU will be almost the same.
After installing a VM you should install in the VM, the Virtualbox Guest Additions to get the full advantages of Virtualbox.
To complement the good video. My Vbox settings for Linux Desktop VMs are:
- I allow the copy/paste between host and VM and vice versa.
- I assign all cores (in my cases 4) to the VM to run the VM at max speeds. The Host Linux scheduler can handle high load and overloads of the VM if needed. It is like dealing with overload on a single OS with some high load processes.
- For the display I assign the max size 128 MB and I choose 3D acceleration to play simple games like "Extreme Tux Racer" in the VM.
- I use 1.5 GB of RAM for most Linux OSes, but 1 GB for e.g. Peppermint, Windows XP and Lubuntu. I only use 2 GB, if I keep many application open at the same time in that VM. For Windows 7 and 10 I use now 3 GB and in the past 2 GB.
- I use Bridged Networking since it is more efficient. On the Phenom it saved me between 5 and 10% of the CPU load during transfers. In bridged networking the VM talks more directly to your Router.
- I always set the USB to 3.0 and
- I always use one shared folder, to have an easy way to share data between Host and VM and between VMs. I share all my data between Host and VMs (music, videos, emails, downloads, office docs etc) and thus I limit the Vbox disk size to 16 GB for Linux. Normally only half of the Vbox disk is used, since I store all data in the Shared Folder.
l did not hear you mention that you may have to go into the bios to enable virtualisation in linux and windows computers
It will fail and tell you to do that. A quick google will get the specifics. A pain in the butt if you did not know though. like right now I cannot remember exactly what setting you change. I think security tab and then enable 7 something. smh
@@absolutethinker7764 if eli had only done vms on a mac or a pc that already had virtualisation switched on, he may not be aware of it, it caught me out
Great video. I noticed that if you leave the virtual optical disk blank and when you launch the VM and there is no OS already installed then it will prompt your for a ISO to mount. Just browse to try the ISO and it will boot off of it.
Eli, I am subscribing to your website today. thanks for the content
Nice !
we need more details about 'Virtual Network Adapters' and how to play with Virtual box with GNS3 ?
thank you for doing what you do
I have an AMD 2400g APU, the iGPU, that I want to use for the host OS and a dedicated GPU that I want to use exclusively for my Windows 10 virtual machine. My question is do I connect the first monitor for the host OS directly to the motherboard and the second monitor to the graphics card for the virtual machine and do I have to enable integrated graphics for the APU in the BIOS in order to use it because it is disable by default if a graphics card is detected in the PCI slot?
can you make a deep dive video on linux file structure and repos... stuff ..? it will be very helpful for me...
Bro it's amazing.
I tried this program in school... The computers were so old and crappy that it was impossible to get anything done in the lab.
Virtual Box!✌😃
This vid is interesting.
Do you need to download Linux before virtualbox
it doesn't run on android , or at least not that i have found,
i was looking for it for android x86
How to increase the size of virtual hard drive FROM 30 GIGABYTES TO 50 GIGABYTES.
THANKS.
Doesn't instancing and sharding in games work the same way? Like in MMOs
Like thinking back in the early 2000s when you have single and dualcore serverblades with max 512mb-1gb ram which housed 1 server you can now with virtualization and modern XEONS or EPYC and 10-40GBps run like 30 servers or more
LOL I use VirtualBox to run Windows on my Ubuntu machine just for some apps that don’t run on Linux.
May i know if vdi file can use on vmware / hyperv???
decent puppet
I know you can on VMware workstation. I haven’t tried to use .vdi on hyper-v but I’d imagine so.
thnx SO SO much!!
What happened to your ear???