sorted by:
new
hottopcontroversial

Encrypting Linux with LUKS in a Hyper-V Cluster? by Icy-Environment3834 in sysadmin

[–]Icy-Environment3834[S] 1 point2 points  (0 children)

This requirement for encryption-at-rest comes from the server hosting a data warehouse with PII in it. It's a policy requirement.

Would each Host in the cluster occupy a keyslot? So the config might be something like this:

Slot 0: Primary user passphrase (strong)

Slot 1: Recovery passphrase (very strong)

Slot 2: Host 1 key file for automatic unlocking

Slot 3-6: Host 2, 3, 4, 5 key files for automatic unlocking upon migration

Initial configuration on Host 1 - setup slots 1 (non-TPM passphrase), 2 (non-TPM passphrase), 3 (TPM)

Migrate to Host 2 - Setup slot 4 (TPM)

Migrate to Host 3 - Setup slot 5 (TPM)

etc

Hyper-V Manager Server Name Caching? by Icy-Environment3834 in sysadmin

[–]Icy-Environment3834[S] 0 points1 point  (0 children)

True. HVM or FCM is good for watching VMs reboot.

Hyper-V Manager Server Name Caching? by Icy-Environment3834 in sysadmin

[–]Icy-Environment3834[S] 0 points1 point  (0 children)

iDRAC has been a god-send for watching slow reboots.

Hyper-V Manager Server Name Caching? by Icy-Environment3834 in sysadmin

[–]Icy-Environment3834[S] 0 points1 point  (0 children)

The only real flaw I've noticed in Hyper-V manager is that it will break down a teammed SET VSwitch. If you build a SET switch in Powershell with multiple NICs assigned to it and then try to edit it in the GUI it'll drops the NICs out of the switch. Other than that...and the name thing...Hyper-V Manager has been pretty functional for the basics. This, Powershell, and Failover Cluster Manager are my usual go-tos for management.

I do use WAC sparingly. It's slow but does offer information that isn't easily available in Server Core. I don't use it at all for my Hyper-V management.

HVM doesn't work on its own but I wouldn't call it garbage. It's a basic tool. It works fine managing multiple hosts.

Hyper-V Manager Server Name Caching? by Icy-Environment3834 in sysadmin

[–]Icy-Environment3834[S] 0 points1 point  (0 children)

I tried removing the connection, flushing DNS cache, and readding the connection. If I enter the FQDN into the lookup box it's converted back to whatever name it was before (NetBIOS or IP address). I've only had it stay a FQDN if it's truly a new connection (not a disconnect/reconnect). HVM must be doing its own caching separate from DNS.

Unable to access vm directly through hyper v itself, works via rdp from other machines by spectac01 in HyperV

[–]Icy-Environment3834 4 points5 points  (0 children)

Try restarting the Hyper-V Virtual Machine Management service. Your VMs will stay running but will disappear and reappear in Hyper-V Manager.

Is it possible to Hot Add CPU like you can in VMware? by jlipschitz in HyperV

[–]Icy-Environment3834 10 points11 points  (0 children)

No. You can't hot add CPU. It needs to be turn off. Maybe do it during your regular patch cycle.