2-node 2016 Cluster with problems accessing the cluster storage: This morning I noticed that only the node owning the CSV can access it.

If I try to browse it from the other host I get "Location is not available. C:clusterstoragevolume1 is not accessible. The referenced account is currently locked out and may not be logged on to".

If I change ownership of the CSV from node2 to node1, then node 1 can access it, but not node2.

I suspect that the AD administrator has altered the setting for password and lockout, but I cannot figure out how to resolve this. Both nodes are domain members.

Read full post . . . .

Hi, 

I’m exploring hyper v replica solution for system center, sccm, sco & scsm. How can i calculate how much bandwidth will be require? 

At the moment i don’t have the environment to test out. 

https://www.microsoft.com/en-us/download/details.aspx?id=39057

Read full post . . . .

I configured 2 host with Hyper-V Manager , Host 1 (192.168.1.20) - VM1 (192.168.1.8) & VM2  (192.168.1.9) and Host 2 (192.168.1.100) - Vm3 (192.168.1.101) & Vm4 (192.168.1.104), and my computer 192.168.1.80 and gatway 192.168.1.1. Now Vm1
is able ping to their host & other VM hosted on same host and other computers and gateway n vice versa, but unable to ping other host 192.168.1.100 and thier vm and vice versa. please let me possible solution.

Read full post . . . .

Installing this on a fully (firmware) updated HP Prolient DL380 Gen9 SD card causes an ‘inaccessible_boot_device’ blue screen on boot just after the install finishes. 

Server 2019 Standard installs and works fine.

Read full post . . . .

Hi,

We have a server having 2 Processors with total of 32 Cores and 64 Logical Processors. We need to distribute these cores among 11 Windows Servers 2012 and 2016 VMs having different server roles like Applications, SQL DB Servers and RDS Services. Currently
we have assigned 4 Cores to each VM which becomes 11×4=44. The servers are working fine but we need to follow the best practices and add more servers if required.

Any Suggestions?

Thanks.

Read full post . . . .

Whenever I put a host in maintenance mode via scvmm, it starts migrating all VMs to other host, but once it gets to the last 3-4 VMs, the host that is going into maintenance mode crashes and reboots before being fully evacuated.

I’ve learned to manually migrate important VMs before putting into maintenance mode because it does this every time. If there are only a few VMs on the host when I turn on maintenance mode, it evacuates just fine. I’m not sure what the magic number is that
makes it crash. I was installing updates today, which was why I was going into maintenance mode, but it rebooted before I could even start on that.

What should I look for to find the cause of the reboots?

Hyper-V Server 2012 R2

SCVMM 2016

2-node cluster

Dell Compellent Fiber Channel shared storage

~35 running VMs

Read full post . . . .

A Server Core installation of Server 2019 Standard / Datacenter allows ‘Features on Demand’ to be installed (mmc, event viewer, etc, plus optionalliy IE11). Does anyone know whether it’s possible to install the features on the stand-alone (free) Hyper-V
Server 2019? I’ve just tried running the Powershell commands to install them (listed here: https://docs.microsoft.com/en-us/windows-server/get-started-19/install-fod-19) - it reports as completed successfully, but the commands don’t seem to be available and
a search on the C drive for the relevant .exe files doesn’t locate anything.

It may well be that, given that Hyper-V Server is free, the features aren’t available - but it would be useful to know for sure.

Thanks

David

Read full post . . . .

Hi,

We have a Hyper-V server 2012 r2 that has issues shutting down and starting up vm guests.

The host and guest are fully patched and their is not hardware issues.

Please can someone provide assistance.

tx

Nuno

Read full post . . . .

I have 4 VMS replicating happily for years in production between two 2012 servers.  I am in the process of bring in a new 2019 server into the mix.  My plan was to replicate a production VM to the new 2019 server and then switch the primary and
replica server and spin up the VM on the 2019 server and then replicate back down.  Essentially moving production to the flashy new hardware and having the current hardware with Windows 2012 as my fail-over.  

I was able to replicate up just fine and spin the server up.  All that works perfectly.  However - when I then try to reverse the replication and replicate back down to the 2012 server I get the following error: the operating system version
on the replica server must be the same as or newer than the version on the primary server.

The seems pretty cut and dry.  However internet searches makes it seem like it might not be.  From a chart that I have seen posted on similar threads - as long as I keep the VM version at 5, then it should be possible?  If so, how do I get
around this error? I have not upgraded the configuration version of the VM. 

Currently I do not have another server to spin up with 2019.  If I could get everything off one of the production servers I could upgrade one to 2019, but that isn’t something I can do quickly since they are both in production. 

Read full post . . . .

KVM (hidden state=’on’ ) and Vmware(hypervisor.cpuid.v0) both provide a way to hide to the vm, the fact they are virtualized.

I’ve done:

ExposeVirtualizationExtensions : True

But it doesn’t seem to have the same effect. The goal is to pass a nvidia geforce 1080 to a linux vm for the purpose of tensorflow. I’ve successfully done the passthrough, and it shows in lspci, but nvidia-smi returns "Unable to determine the device
handle for GPU". In a windows guest I believe this manifests it’s self as error 43. KVM and Vmware handle this by simply hiding that the system is virtualized. This fixes the issue in both windows and ubuntu on either virtualization platform

How can I achieve this with Hyper-V and an Ubuntu guest?

Read full post . . . .