Windows 10: VM's - What VM OS'es /hosts / virt progs are you using

Hi folks

I was just amazed that on a topic on XP I got over 10,000 views and another one over 14,000 -- so I thought would be interesting to get an idea of what VM's people are running, on what type of HOST system and what Virtualisation platform they are using -- I know quite a few run the various W10 insider builds on a VM (makes sense too). I'd be interested if people were running W7 builds, VISTA builds or even Millenium edition builds.

I've some legacy hardware that needs XP but I think I might be able to "Poodle fake" some of the drivers so it might work on W7 which IMO would be better but I was amazed too see the number of views for XP !!!!!!

Not creating a POLL on this topic as there's far too many options and combinations -- I'm just interested to know what people are running as VM's.

Cheers
jimbo

:)

 

Account failed logon 4625 on VM guest when clicking the entry of VM guest on failover cluster Manager on VM Host

Issue:

We found a multiple failed logon events on VM guest (evert ID 4625) with account (the account you logon on VM host) when we clicking the entry of VM guest on failover cluster manager console on VM host with Integration servers (Data Exchange) is enabled.



How to reproduce:

1. Check the “Data Exchange” is enabled on a VM guest (Enabled by default, right?)
2. Open Failover Cluster Manager Console on VM host.
3. Click the VM guest entry
4. Then you may found multiple failed logon events on that VM guest.

Reference:

Hyper-V Integration Services



Question:

1. Does the multiple failed logons are normal or necessary?
2. If the failed logons are normal and necessary to be happened and the “Data exchange” function is good to be enabled to gather data from VM guest, any recommendation for us to correct or avoid these failed logon?

Please advise.



Constrain:

We have no chance to use same account and password on VM hosts and VM guests (because all account are managed by password management) and the Audit Policy of Audit Credential Validation must be enabled.

 

VM Licenses

I'm using a Dell PC with a factory installed OEM version of Windows 10 Pro.

My work requires me to use program editing software from many different vendors, these software titles often don't work well and can cause issue with the PC they are installed on. My thought is to isolate them by using VMs with the software for each vendor
installed on it's own VM - isolated from my Host and the other VMs I would use for other editors.

My new PC with Win10 OEM would be the host. Only 1 VM would be used on the host at a time but there would be as many as 10 different VMs I could run on the host.

Can I copy my host OS to the VM with my OEM license?

If I can't, and I need a new license for the VMs can I use 1 license for the multiple VMs?

Is there an upgrade from OEM to FPP ?

Pat

 

Can you allow the host to use the VM network connection?

If you use a VM...

this is possible although not immediately obviously useful. My situation was one where the vm os was able to change settings on a wireless network adapter which allowed me to pick up the signal at a useable strength. The host could not do this. So I was in the weird situation where the vm os - backtrack - had internet but the host - osx 10.6 - did not. Annoying.

Easily corrected as follows:
1. connect the vm to the network, in my case this was wireless so wlan0
2. set up the vm so that is has a local network with the host, make sure the host can ping the vm. In my case this meant enabling eth0 in the vm
3. set up ip forward and iptables masquerade rules on the vm.
4. change the default route of the host to be the vm local ip
5. enjoy the vm network via the host


now I imagine some readers will want more detail on ip forward and masquerade with iptables but there are a lot of tutorials out there for this stuff. It depends on the vm os but if you are using linux then

ip forward with:
$ echo 1 > /proc/sys/net/ipv4/ip_forward

iptables rules something like this
iptables -t nat -A POSTROUTING -s $PRIVATE -o eth0 -j MASQUERADE

{clearly $PRIVATE is your private subnet, set the rules up to run at ifup}

*Smile