I'm having a crazy time getting my Guest to use it's own IP address. It continues to use my Host IP. I already have two Guests running with their own IP. Maybe it's how I have my network configured. Suggestions?
I've attached some screenshots of my network-related setups.
Host: Win 10 Pro x64 1903
Existing Guests: both are Win 10 x64
New Guest: hasso.io
The problem:
Yesterday we had a power outage.
Fried the system disk (c:) on the host machine.
I had configured all the virtual drives and virtual machines on a second, data disk (d:); thankfully this survived.
Everything was working fine prior to the incident.
I popped in a new c: drive, and re-installed server 2012 r2, and added hyper-v.
created a new machine, using the old drives, and hooray, the vm booted with all the software intact.
*however!* the vm doesn't have internet access, nor can it be pinged.
Salient Details
Once again everything was working prior to the power outage.
I have two physical nics (nic1 nic2) in the box. Nic1 is dedicated to the host, and it's ip is statically allocated (192.168.1.25). Nic2 is supposed to be dedicated to the vm, and I didn't bother assigning an IP to it. Both are connected to the network.
When I first added the Hyper-V role though Server Manager, I noticed that the server name/ip it came up with was ServerName/[dynamically allocated IP of nic2]; that is, hyper-V seemed to be wanting to configure the server with nic2, rather than nic1. Is this right? There was no option to select 'ServerName/[nic1 IP]
In HyperV after the reboot, I created a virtual switch with nic 2. Then I created a new VM, but used the vhx file which was on the surviving physical D: drive. I attached the virtual switch tp the new VM.
The VM booted. All the files were there. However, the network icon in the system tray always indicates 'Unidentified network/limited' under 'Connections'
What I've Tried:
I found i had to reset the ipv4 static ip on the new virtual machine, as well as the dns host specification.
I tried removing the HyperV role, disabling nic2, and re-adding the HyperV role. This time the server it came up with was ServerName/[NIC1 IP]. Then re-enabled nic2, used it to create a virtual switch, and attached that to yet another created VM.
My next try, as a diagnostic, is to create a completely new VM with a new install of the OS. I'm doing this as a diagnostic, but forsaking the old disks has pretty unpleasant implications.
It's got to be something simple! Any help would be truly appreciated.
thanks in advance
dmc_lat47
For the last month, something strange is happening with our new Hyper-V server. During the summer holidays we bought and installed a new physical server with Windows Server 2019 Essentials installed on it; on which we also enabled and configured the Hyper-V role. On that physical Hyper-V, we have three VM's running, which are:
1. Domain controller;
2. File sharing server, part of the domain;
3. App server, also part of the domain.
All of the three VM's also have Windows Server 2019 Essentials as OS. Each WS2K19 Essentials server has its own dedicated license.
Each monday between 9:30 am and 10:30 am the Hyper-V power downs both the File and App servers. When we look in the logs there isn't anything that explains the power down of the VM's. Updates are also disabled to make sure that isn't the culprit.
Does someone has any ideas of what might be wrong or where to look in what direction? I've been looking for over a month now and can't seem to find anything.
Thanks!
We have a two clustered W2016 Hyper-V hosts, every couple of days one of the hosts gets stuck when the backup kicks off. In Hyper-V manager the VMs all say 'Creating checkpoint 9%' It's always the same percentage 9%. You can't cancel the operation and the VMMS service refuses to stop, the only way to get out of the mess is to shutdown the VMs, and hard reset the effected node. The backup works for a few days then it all starts again.
The only events I can see on the effected node is:
Event ID: 19060 source: Hyper-V-VMMS
'VMName' failed to perform the 'Creating Checkpoint' operation. The virtual machine is currently performing the following operation: 'Creating Checkpoint'.
Can anybody help please? Cluster validation is clean. Hosts and guests are patched up.
I have Hyper-V setup on 2 * Server 2016 servers. I have vm replication working over an MPSL WAN.
I've noticed that every time I reboot the Primary server, for Windows updates or whatever, the replication fails with the below error.
If I right click on the VMs from Hyper-V Manager, it appears as if the replication is paused, but clicking "Resume Replication" has no effect.
The only way I can get it going again is to completely remove the VMs on the secondary server, and setup the replication from scratch, which is ridiculous because it then has to copy all the VMs in their entirety which puts a huge strain on the network.
How can I resume the replication, or even better, have it automatically resume after a reboot?
Hello.
I have very bad network performance on Hyper-V (Windows Server 2019 Standard) external virtual switch. File transfer speed from Virtual machine to physical machine is about 40MB/s, while file transfer from Hyper-V host to same physical machine is aobut 120 MB/s. Server is new, Proliant DL 380 Gen10. 1 physical network card is for management and other three are in Nic Teaming connected to external virtual switch. I've already tried to use without network teaming and speed is still slow. I read about some problems using VMQ and Broadcom network cards(HPE Ethernet 1Gb 4-port 331i Adapter), but this problem was known few years ago. SR-IOV is not enabled, because ethernet card does not support it. Driver release is latest. All suggestions to fix my problem are welcome.
Regards,
Marko
Greetings,
Since December 2018, Hyper-v on Windows Server 2019 users have been reporting this issue. I am posting a new thread because the original thread on the topic had a potentially misleading headline. And most of the ensuing thread consisted of repeated requests for more information when in fact that information had already been provided. And yet, even after an MS representative confirmed through his own testing that the (serious) problem exists, no further information has been provided for over five months.
The problem, in a nut-shell is this: Guest VMs do not shut down gracefully when the Hyper-v host is shut down or restarted, regardless of guest VM settings.
Even when a guest VM is set to "shut down the guest operating system" as its default behavior for the "Automatic Stop Action", the Hyper-v host doesnot actually shut down the guest VM(s) as it shuts itself down. Rather, the VMs are just terminated as though power is cut. Upon rebooting, the guest VMs will report no attempt to be shut down, and instead report that the prior shutdown was unplanned.
This behavior is easily reproduced. Merely. . .
. . .you will find that the guest VM was merely switched off ungracefully.
Microsoft, please acknowledge this issue and give us an ETR. I'm sure I'm not the only person putting their server upgrades on hold after running into this issue. Various work-arounds (using "save state" instead of "shut down") are not a viable option for me. Please, give us some news and hope (after an inexplicably long period of waiting) that a fix is imminent.
Best Regards,
Brian
OS: Windows2019. Can't initialize second node.
> Initialize-HgsServer -HgsServerIPAddress 192.168.0.111 LogPath: C:\Windows\Logs\HgsServer\190917155513\DOMAIN-HGS2 ValidateSetHgsServerBindings : Host Guardian Service can only be changed to use HTTP and HTTPS together. If any ports or certificates are being altered, flags must be present for all active protocol types. At line:1 char:1+ ValidateSetHgsServerBindings @parameters+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~+ CategoryInfo : NotSpecified: (:) [Write-Error], WriteErrorException+ FullyQualifiedErrorId : Microsoft.PowerShell.Commands.WriteErrorException,ValidateSetHgsServerBindings
Log:
> gc C:\Windows\Logs\HgsServer\190917155513\DOMAIN-HGS2\InitializeHgsServer.txt 9/17/2019 3:55:13 PM DEBUG: Initialize-HgsServerInternal @PSBoundParameters
I cleaned hgs configuration by Clear-HgsServer and reinstall hgs, but this did not lead to success.
Hi Support,
Host Server 2012 r2 automatically rebooting and showing the error message for hyper-v manager.
Please find the event id and help to share the resolution:
* Event Id: 16000Hi Guys
I have two SAN units, Netgear 5200s. I currently have three servers connected to these SANS. Each server has it's own LUN on each SAN. I am using these two SANS as mirror'd drives on the servers.
Using two SAN units, what is the best way to setup failover hyper-v? Is there a best way or should I just use one SAN and not use the other SAN?
Any suggestions would be appreciated
Thank You
Hi Experts,
We have a requirement here to re IP all our VM's as we are moving to a new data center.
While trying to do so, I found a very good script from vmnomad.blogspot.com which I later customized to our need.
Script is running fine with the required parameters & updates, but its not able to change the IP address, though it says, it changed the
IP address.
Command syntax from PowerCLI: NewreIP1.ps1 -Inventory .\Test-Inventory5.csv -VC vCenter
Initially we had issues running the command:
his command syntax invoke-vmscript -ScriptText $changingIp -ScriptType bat -VM $vm.ServerName -GuestUser $vm.Username -GuestPassword $vm.Password using 'netsh.exe in the guest VM.
Later on its found that the script runs perfectly if we disable UAC for our test VM's.
With UAC enabled, it cannot run.
We need to disable UAC for 300 plus VM's & if we do so, we need to restart as well, which is not possible in one go.
Is there a way to disable UAC for all the VM's & run something like 'net stop server && net start server '& avoid restart through Power shell or by any means?
Please let me know, that would be very helpful.
Thanks
Arindam
I have a Hyper-V machine running on a server with 20GB of RAM available (according to resource monitor). When I try to start it with more than 4GB of RAM it fails with this error. I tried creating a new VM, using a different VHD file, all create the same error. Before I updated Hyper-V it used to report insufficient memory. What am I missing?
Thanks!
Mike
I just purchased a new HP Proliant DL360 GEN10. It has (2) 16 core processors.
This server will be a dedicated Hyper-V HOST running Server 2019 STD, for a mission critical SQL database VM running Server 2019 STD.
My question is what is the maximum amount of processors I can assign the VM? I would like to have as much processing power as possible.
I have allocated 352GB of RAM to the VM. Total RAM on the HOST is 384GBs.
Attached are the current settings of the VM. Any recommendations on how to optimize performance would be appreciated.
Brian Modlin
Hi there,
I have successfully configured the Hyper-v cluster but I realized after that I need to configure more cluster networks. Specially, I want to add another network for Live Migration. I can't seem to figure out how to configure additional cluster networks. I can see available network interfaces but can't see how to add more cluster network to utilize those available NIC's.
Can someone explain what I am missing here?
Thank you.
Hello
I have a three node failover cluster. Two nodes are local, and connected to the same SAN. The other node is at a remote location connected to a different SAN that is a mirror of the local SAN, over a 1Gb E-Line connection.
When I live migrate a role between the two local nodes everything is fine. When I migrate a role from the remote node to a local node, everything is fine. When I migrate a role from a local node to the remote node, the migration takes the expected amount of time but once the migration is complete, it takes about ten more minutes for the network to come up.
I have disabled encryption on the E-Line for testing purposes and it didn't help.
I can connect to the role via the console while it is in this no network state and Windows says that it is connected to my network but the connection is limited. I can ping the network adapter but cannot ping the gateway.
Has anyone else seen symptoms like this before?
Hutch