Disk2vhd and VirtualBox woes
-
@Bill-Kindle said:
@technobabble said:
So I understand that using Hyper-V, I should be able to Insert Intergration Services Setup Disk so I can use the mouse in the VM while remoteing into the PC with Hyper-V.
Sounds easy enough,, Start the VM, click on Action, then click on Insert Integration Services Setup Disk. BUT, it's not there...it's not even greyed out, it's just not there.
So is Hyper-V missing key pieces in the W10 Technical Preview?
I'm using W10 in Hyper-V 2012 R2 without issue. The Integration services iirc were already present in the TP, no additional installation was required.
In my scenario, the PC's main OS is W10 TP and it's running Hyper-V which I have the Vista VHD running finally. That Vista VHD has no Insert Services Setup Disk.
Is there another way to get the Insert Integration Services started?
-
So after a lot of Googling...Insert Integration Services Setup Disk is NOT available in Windows Server TP nor in W10 TP, see link here.
-
@technobabble said:
So after a lot of Googling...Insert Integration Services Setup Disk is NOT available in Windows Server TP nor in W10 TP, see link here.
Makes sense.
-
Ok, I must not be reading or comprehending what I am reading. What does this mean:
Integration Services delivered through Windows Update
Starting shortly after the release of the Windows Server Technical Preview, updates to integration services for Windows guests will begin being distributed through Windows Update. For service providers and private cloud hosters, this will put control of updates into the hands of the tenants who own the virtual machines. Tenants can now update their Windows virtual machines with all updates, including the integration services, using a single method. For information about integration services for Linux guests, see Linux and FreeBSD Virtual Machines on Hyper-V .
Does this mean W10 will deliver the integration services via an update?
-
And the biggest reason I ask these integration questions, I cannot connect my VM to the internet as the VM's network adapter shows not connected in settings. Rest of the settings in image below:
-
At this point, can I export the VM with the attached VHD to something else so I can try to run the VM in another virtual manager?
The VM needs to have internet access so I can run the database conversion to Quickbooks, which can only be done on the same PC running an instance of the Microsoft Accounting program.
-
Can you select a virtual switch to attach it to?
-
@scottalanmiller said:
Can you select a virtual switch to attach it to?
no other choice but not connected
-
The VM wants to do driver updates, but without a internet connection it can't find whatever drivers it's looking for.
-
@technobabble said:
The VM wants to do driver updates, but without a internet connection it can't find whatever drivers it's looking for.
have you installed the VirtualBox tools using the virtual ISO?
-
I have the VM running under Hyper-V on a Windows 10tp PC
-
Can I run a virtual machine within a virtual machine? IE: W10PE is my physical PC and I want to install W8.1 as a VM and then launch the VM of Vista in W8.1.
-
@technobabble said:
Can I run a virtual machine within a virtual machine? IE: W10PE is my physical PC and I want to install W8.1 as a VM and then launch the VM of Vista in W8.1.
I don't believe you can with Hyper-V... you probably can with Virtualbox or other type-2 hypervisors since they don't directly interact with the hardware.
-
@coliver Thanks for the info. I will install VirtualBox on the W10PE machine and see if I can get my VHD to run in VB. I really need to be able to remote into the box and access the VM, and Hyper-V is missing the tools in the W10PE build.
-
@scottalanmiller Ah ha...finally I figured it out...I couldn't connect to a virtual switch because I hadn't created one yet.
I found this tutorial on Hyper-V, http://www.tenforums.com/tutorials/2087-hyper-v-virtualization-setup-use-windows-10-a.html
Part Three explains how to create a virtual switch.
Part Five explains that Vista (and earlier) VMs have to be created as a legacy Windows VM. Which means having to "add hardware" in the VM settings and choose Legacy Network Adapter.
And finally I was also able to enable quest services via Integration Services under the Management tab.
