I have a windows 10 host operating system that supports virtualization. Next, I have an Ubuntu 16.04 virtual machine I created using virtualbox. For development purposes, I need to create a virtual machine inside my guest Ubuntu virtual machine. Unfortunately, I can't enable VT-x option in my guest Ubuntu machine to create a create a virtual machine inside my Ubuntu guest. Any information on how enable VT-x option on my virtual box inside my virtual Ubuntu machine would be appreciated.
Edit: I had that this may be accomplished through PCI Passthrough for VirtualBox. If so please detail how.
Lastly, my problem is similar to this guy's but with exception I can't seem to create an UBuntu32bit box.
Any information on how enable VT-x option on my virtual box inside my virtual Ubuntu machine would be appreciated.
You simply CAN'T.
VT-x is a hardware capability:
In 2006, both Intel (VT-x) and AMD (AMD-V) introduced limited hardware virtualization support that allowed simpler virtualization software but offered very few speed benefits. Greater hardware support, which allowed substantial speed improvements, came with later processor models.
Since VT-x requires hardware capabilities to work, there's no way for the "outer" virtual machine in your nested VMs to provide that capability to the "inner" VM. The "outer" VM doesn't have any actual hardware.
If you have to run a VM inside your VM that requires some of the capabilities that VT-x provides - such as the ability to run a 64-bit OS - you can try QEMU for the "inner" virtual machines. It'll be slower since it's an emulator and not true virtualization, though.
Related
So I have this work computer that I'd like to play fortnite on, but it doesn't have the latest version of directX installed in it so I can't just install fortnite to my flashdrive and play.
So I've been researching on getting a portable Windows 10 Virtual Machine on my flashdrive, which has fortnite installed in the VM. However, apparently Virtual Machines don't utilize the host's GPU by default. I'm trying to find out a way to let the Virtual Machine use the native GPU. I've seen that it's completely doable on a Linux host, but I can't find anything about GPU passthrough on a windows10 host.
Note: my work computer does support VT-d, and it is locked down so I can't do anything to it that requires elevated privileges like installing stuff, changing the BIOS, or booting off an external harddrive.
Suppose in my pc I have Ubuntu as Host OS. Now I installed a Virtual Machine say VirtualBox (hypervisor) and then deployed a centos and a redhat os inside that as guest OS.
Suppose CentOS and redhat has 2 processes running and Ubuntu is running 3 processes. So following are my questions:
There are how many processes that Ubuntu is having?
Is there any difference between GuestOS and HostOS processes?
If all guestos runs as a process then they will get less time as compared to other process running on host os.
Please clear my doubts here.
Thank you.
Well let me clear your doubts,
First of all there aren't any specific number of process for an OS, its called as cores or threads, technically you can define how many cores or threads you want to use on your virtual machine and it depends on the system configuration you use.
Secondly Guest OS is what you have created in the virtual machine and host is what your laptop or pc actually run. Host OS uses the actual hardware for the working whereas the Guest OS uses the virtual hardware like number of cores and type and size of hard drive defined by the user while adding a virtual machine.
Third, as I mentioned earlier Guest and Host OS works on the configurations used by you, if you user higher amount of cores/ threads in setting your virtual machine the Guest OS will get higher speed.
Ideally the virtual machines are used to test and create some functionality of the Operating Systems without affecting the internal OS, so you can think of it as a your parents house where you can live and grow but at the end you cannot go away from the fact that their contribution is more and so you cannot go beyond their features without leaving it and making your own home.
Linux operating systems are multi-threaded operating system. The host OS would consider virtual box as a thread. You can define number of cores and virtual hard disk size for guest OS by using virtual box.
Since virtual box runs in separate thread and other operations of host OS runs in separate threads, there would be less effect on speed of processing. But I've observed big variances in processing speed in systems which have low memory. Each and every thread needs specific allocation of memory for its smooth operation. So systems having more than 2 GB RAM managed virtual box very well.
We've physical machine on which several virtual machines are installed using vm player. Now we are trying to install tool on one of these virtual machines, the tool require vm player, so we installed vmplayer 4.0.0 on the virtual machine. But the vmplayer gives error while installing tool like "Virtualization is incompatible with long mode on this platform. Without long mode support the virtual machine will not be able to run 64 bit code.
The visualization option on the physical machine is already enabled.
Any help on this.
I managed to get long mode working in Vmware by uninstalling Virtual PC.
No nesting or something, it simply started working.
I don't think it's possible with VMWare Player on the host since the VT is not virtualized.
According to http://www.virtuallyghetto.com/2011/07/how-to-enable-support-for-nested-64bit.html?m=1
you could do it with VMWare vSphere 5
I want to give a demo for my customers use virtual machine, but I don't want the customer to install the virtual machine software, can I make a demo which bundle the virtual machine software and my virtual machine, then just a click to run the virtual machine. It will be cool. is there any tool can do that?
I'm not aware of a virtual machine that doesn't need to be installed. If using Windows, the Microsoft Virtual PC is a relatively compact, free, quick-to-install option for a VM.
One other option would be to install an OS and your demo onto a USB flash drive. As long as the computer used can boot from USB (which is pretty common in newer computers), then you can have complete control over the OS in this fashion.
EDIT: Sun VirtualBox is free VM software. You do have to install it, but I've found that it works well, plus it's free.
You could try using Portable VirtualBox as per this forum thread. I have not tried it myself but it seems like some people have had luck with it.
I'm running Server 2008 64bit with Hyper-V. I've created a virtual machine with Vista 64bit and installed it. I can't get the Vista virtual machine to see the network adapter.
I've set-up an external network on the Virtual Network Manager (Hyper-V) and associated that with the virtual machine (Vista). I've also tried using a Legacy Network Adapter but that didn't work either although that time the Vista machine saw the network card but couldn't connect through it.
This is (obviously) the first time I've tried to set-up a virtual machine.
Any ideas?
EDIT: I notice that this question has been voted down a couple of times. I know that it's not a programming question but I'm a developer setting up a virtual machine to test my C#/ASP.NET code on and thought that other developers may hit this problem as well when they're doing this...
I don't know Hyper-V, but I know in VMWare you can create a network connection in Bridged mode (meaning the VM will get it's own IP address via DHCP if that's enabled) or host-only mode (meaning the VM can only communicate with the host). When Vista could see the card, could it communicate with the host machine (which would indicate a host-only connection was specified)? What kind of IP address did it have (I would guess Hyper-V has a built-in DHCP server like VMWare does?) -- that might give additional clues.
Sorry I don't know Hyper-V better...
Make sure you have the Hyper-V Tools installed on the Guest VM. You shouldn't need the legacy adapter.
You also may want to make sure you have all of the latest updates which may have addressed your issue. Particularly, KB950050
http://support.microsoft.com/kb/950050
It turns out that Vista x64 running as a VM through Hyper-V doesn't support the virtual network connection/card and that you have to set it up as a legacy network card. When I eventually got the config settings correct for the legacy network and disable the virtual network it connected.
Thanks for the help guys - much appreciated!