Yes, as long as you have the key. Very important, make frequent backups of the Window 10 virtual machine vdi file.
I thought these version were specially made for VM's. So Win 10 will still work if not activated? Is this a full Win 10 version?
Of course, At least on Virtual Box (which i use), im not sure on VMware Workstation, i heard that you need a legit license. Pre-configurated Win10 Enterprise.
I'm running Mint Cinnamon 19. I've installed Windows 7 in a vbox container. Windows 7 is all up to date, drivers and such. When I'm trying to play my purchased movies through Itunes, I get sound, but no picture. I've tried downloading codecs, but nothing seems to work. Do you think it's the vbox gpu driver can't handle this? I have 128mb of gpu memory dedicated to this .vdi. I'm using a Intel Nuc Skull Canyon. Specs: CPU: Intel Core i7-6770HQ Skylake-H RAM: 16gb SSD: Samsung 950 512gb EVO Series GPU: Intel Iris Pro Graphics 580
You should not need any codecs for iTunes. Do you have the Guest Additions installed in the Windows 7 virtual machine? If you do, did you enable Direct3D Support (Experimental) when you installed the Guest Additions (disabled by default). When you check the box for Direct3D Support you will get a prompt (at least I do) asking if you want to install basic Direct3D support instead, the correct answer to that Yes/No prompt is "No", so it will install Direct3D. I don't have any movies to watch, but I played several trailers within iTunes and they a played perfectly.
Zero Day vulnerability found in Virtualbox. General Information Vulnerable software: VirtualBox 5.2.20 and prior versions. Host OS: any, the bug is in a shared code base. Guest OS: any. VM configuration: default (the only requirement is that a network card is Intel PRO/1000 MT Desktop (82540EM) and a mode is NAT). https://github.com/MorteNoir1/virtualbox_e1000_0day
On Ubuntu host, with secure boot enabled, I can't get my VMs to run. When I turn off secure boot, everything works. I assume there are some drivers that need to be signed or registered or something? How to do that?
I remember running into this problem in the past, I think this post helped me https://stegard.net/2016/10/virtualbox-secure-boot-ubuntu-fail/ Here's the post content in case the link dies in the future Spoiler Here are the steps I did to enable VirtualBox to work properly in Ubuntu with UEFI Secure Boot fully enabled*. The problem is the requirement that all kernel modules must be signed by a key trusted by the UEFI system, otherwise loading will fail. Ubuntu does not sign the third party vbox* kernel modules, but rather gives the user the option to disable Secure Boot upon installation of the virtualbox package. I could do that, but then I would see an annoying “Booting in insecure mode” message every time the machine starts, and also the dual boot Windows 10 installation I have would not function. *Ubuntu 16.04 on a Dell Latitude E7440 with BIOS A18, and with a dual boot Windows 10 installation. Credit goes to the primary source of information I used to resolve this problem, which applies specifically to Fedora/Redhat: http://gorka.eguileor.com/vbox-vmware-in-secureboot-linux-2016-update/ And a relevant Ask Ubuntu question: http://askubuntu.com/questions/7606...rade-to-ubuntu-16-04-and-i-want-to-keep-secur Steps to make it work, specifically for Ubuntu/Debian Install the virtualbox package. If the installation detects that Secure Boot is enabled, you will be presented with the issue at hand and given the option to disable Secure Boot. Choose “No”. Create a personal public/private RSA key pair which will be used to sign kernel modules. I chose to use the root account and the directory /root/module-signing/ to store all things related to signing kernel modules. $ sudo -i # mkdir /root/module-signing # cd /root/module-signing # openssl req -new -x509 -newkey rsa:2048 -keyout MOK.priv -outform DER -out MOK.der -nodes -days 36500 -subj "/CN=YOUR_NAME/" [...] # chmod 600 MOK.priv Use the MOK (“Machine Owner Key”) utility to import the public key so that it can be trusted by the system. This is a two step process where the key is first imported, and then later must be enrolled when the machine is booted the next time. A simple password is good enough, as it is only for temporary use. # mokutil --import /root/module-signing/MOK.der input password: input password again: Reboot the machine. When the bootloader starts, the MOK manager EFI utility should automatically start. It will ask for parts of the password supplied in step 3. Choose to “Enroll MOK”, then you should see the key imported in step 3. Complete the enrollment steps, then continue with the boot. The Linux kernel will log the keys that are loaded, and you should be able to see your own key with the command: dmesg|grep 'EFI: Loaded cert' Using a signing utility shippped with the kernel build files, sign all the VirtualBox modules using the private MOK key generated in step 2. I put this in a small script /root/module-signing/sign-vbox-modules, so it can be easily run when new kernels are installed as part of regular updates: #!/bin/bash for modfile in $(dirname $(modinfo -n vboxdrv))/*.ko; do echo "Signing $modfile" /usr/src/linux-headers-$(uname -r)/scripts/sign-file sha256 \ /root/module-signing/MOK.priv \ /root/module-signing/MOK.der "$modfile" done # chmod 700 /root/module-signing/sign-vbox-modules Run the script from step 5 as root. You will need to run the signing script every time a new kernel update is installed, since this will cause a rebuild of the third party VirtualBox modules. Use the script only after the new kernel has been booted, since it relies on modinfo -n and uname -r to tell which kernel version to sign for. Load vboxdrv module and fire up VirtualBox: # modprobe vboxdrv The procedure can also be used to sign other third party kernel modules, like the nvidia graphics drivers, if so is required. (I have not tested that myself.)
Thanks. It is a bit complicated for the uninitiated. I got stuck on step 5, I didn't understand how to create and run the suggested script.
Copy and save the script in a text editor and save as <scriptname>.sh then from terminal use cd command to get to where you saved the script file, then do chmod u+x <scriptname>.sh then do command: sudo ./<scriptname>.sh To make it autostart with the OS, in Ubuntu there are several front-end tools for autostart management, it should be installed by default, I don't remember exactly its name but it could be "Startup Applications".