Is it possible to run a windows guest in a linux host on KVM in google cloud nested virtualization?
We know Google now provides for nested virtualization, in theory they say you can run a linux guest on a linux host using kvm hypervisor as explained in the link below. Does this allow for windows guest?
https://cloud.google.com/compute/docs/instances/enable-nested-virtualization-vm-instances
In nested virtualization it doesn't matter what virtual machines you run (as level 2) in the nested hypervisor. Google is saying that you can only run Linux and KVM as the nested hypervisor (level 1) and that they do not support ESXi, Xen or Windows at level 1. You can run anything you want at level 2, even operating systems not otherwise possible to run in Google Cloud.
Nested Windows 10 at L2 is working. But if you are using libvirt, you have to enable HPET / high precision event timer (libvirt adds -no-hpet, and with this flag, you have boot problems). You can solve this issue by editing the xml file and change <timer name='hypervclock' present='no'/> to <timer name='hypervclock' present='yes'/>.
For windows Versions below 10, this is not requied.
At this point, the doc says:
Nested virtualization does not currently support Windows instances.
Related
I have the following task:
I installed Linux for Windows in Windows 10 Pro computer;
I installed Ubuntu 18.04 LTS;
I have a separate volume in Windows computer, which doesn't have a drive letter assigned to it;
I need to find a way to mount this Windows volume without letter in WSL Ubuntu.
I know the volume id in case it is required.
Any ideas how to achieve this?
Thx, Vlad.
First of all, my question wasn't completely right, I wrote Linux for Windows but in fact I was talking about "Windows Subsystem for Linux".
The idea is to have 1 disk drive as hardware configured RAID 0 storage which is built with 2x Samsung SSD 1Tb. But for protection of data on RAID 0, I want to use HDD which will sync data with rsync or any cloud service. I selected ownCloud.
Finally, I want to hide the HDD from the system and configure WSL to use it.
Hereby how it works for me:
1) I created a folder here: c:\Users\Public\wsl
2) I mounted the HDD in the folder created above.
3) After the HDD is mounted, I created a subfolder for my favorite Linux distribution: c:\Users\Public\wsl\ubuntu
4) I installed Ubuntu 18.04 in this folder as it described here: Installing WSL on Windows 10 without MS Store
5) The point above allows to install ownCloud server on hidden HDD. Now, in order to get it running at system boot, one can create scripts as described here: how to autoload apache2 and mysql in WSL at Windows boot
6) And finally, to get ownCloud Server running at system boot, even before any user login, one needs to do as follows:
*) Open Windows task scheduler;
*) add a task which runs autostart.sh (see how to make this script on a link above) on system boot;
*) use wscript.exe (from windows system32) as the command to run and the vbs script as parameter. Check this link if you need more details;
7) Finally, we need to setup ownCloud client on the computer and connect it with the server by using http://localhost as the server url.
So, as result of this setup, one gets faster disk system based on 2x SSH configured in RAID 0 and to protect data, one uses a local cloud server in virtual machine to get personal content synchronized with standard HDD.
If the system uses actively SSD, the cloud won't get time for syncing data. But as soon as resources are available, system will sync data in background mode into the HDD, which requires more time to write the same data.
This setup allows to use SSD system at full speed as it is required by applications and it does not limit dramatically the performance of SSD subsystem while keep syncing data in slow HDD as computer resources are available and SSD resources are available.
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.
Currently running Windows 10 (native) and VMware Workstation 12 Player. I am running various LTS releases of Ubuntu in VMware.
I am wondering if there is way for me to run SikuliX on my main OS, Windows 10, and have the script interact with a virtual machine, running an Ubuntu OS, that I have open.
The quickstart documentation on the download site isn't very specific about the limitations of SikuliX on this topic. It simply says that you can't run it on a headless system (which VMware is not), and you need to have a monitor - the only problem is that I have no idea if SikuliX considers VMware to be a legitimate monitor or not.
I am aware of the fact that you can install Sikulix on the virtual machine itself, but this is not preferable as I would have to possibly reconfigure my VM settings to allocate more memory OR just deal with running the script at a slower pace.
Any help would be greatly appreciated.
The answer is yes, if you run SikuliX on a native host, it is possible to interact with the the interface of the virtual machine the same as running SikuliX on the virtual machine itself.
Now that I think about it, I should have probably tested this out before posting the question, but hey, if anyone has the same question as I do, now you know.
I am trying to deploy a cent-os 7 VM on a vcenetr from pyvmomi python library and then before powering on the VM I am trying to setup static IP and DNS for the VM.
VM creation goes fine , but guest customization fails, givimg following error:
**Customization of the guest operating system 'rhel6_64Guest' is not sup
ported in this configuration. Microsoft Vista (TM) and Linux guests with Logical
Volume Manager are supported only for recent ESX host and VMware Tools versions
. Refer to vCenter documentation for supported configurations."
faultCause =
faultMessage = (vmodl.LocalizableMessage) []
uncustomizableGuestOS = 'rhel6_64Guest'
Now this customization problem goes away if the VM is just rebooted once. After that we can do the guest customization.
But this reboot takes around 30 seconds of time and for our case , we need to get VMs up and running faster than this time.
Any body who faces similar problem and has some context on it will be very helpful.
Also I don't understand how rebooting the VM solves this problem.
Please share your thoughts even if you don't have exact solutions .
On further Investigation I found that open-vm-tools does not work until the VM is powered on atleast once.
When Machine is powered on , the HOST system detects the open-vm-tools running on guest OS , and from there on open-vm-tools works.
So open-vm-tools can not be used for initial provisioning as it will just not work at the start up.
Cloud-init is the alternative solution which should be used for initial provisioning.
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