Follow

I am configuring a internet switch on the hyper V to have internet access on the VMs. The internet start working properly on the VMs. Suddenly, after 10 to 15 minutes the internet connection disconnected and on the VMs as well and start getting APIPA address 

Read full post . . . .

Follow

hello

I have a question about virtualization of windows server 2019 standard.

I purchased windows 2019 standard edition with 16core licenses and trying to figure out how to utilize it in the best way.

I know that with the standard edition i can install hyper-v role and on top of it run 2x windows server 2019 or older as virtual machines.

but

1) do I need 2 more windows 2019 licenses for those VM-s if I want to run 2x instances of 2019 as VM-s? or it is included with my windows 2019 standard license already?

2) instead of running windows 2019 as VM-s on top of Hyper-V standard can I run 2x windows 2019 VM-s on ESXi or Hyper-v server 2019 free using my 2019 standard license? Or in this cases I need to purchase 2 whole windows 2019 standard editions with 16cores
licenses?

thanks in advance for any help

Read full post . . . .

Follow

I replicated Windows 2012 R2 VM from Windows 2012 R2 Hyper-V host to Windows 2019 Hyper-V.

Then removed replication and enabled replication of the same VM to another Windows 2012 R2 host. Initial replication succeed and in general it works fine, but every morning it stops with the following error messages and requires resynchronisation:

Hyper-V could not perform the change tracking action for virtual machine ‘VM Name’. (Virtual machine ID C30836E4-6AA2-4253-BADF-4560AB3EF737)

Failed to switch the change tracking log file for virtual machine ‘VM Name’. (Virtual machine ID C30836E4-6AA2-4253-BADF-4560AB3EF737) - Error: Size of change tracking file exceeded the maximum size limit. (0xC03A0021) 

Virtual machine ‘VM Name’ requires resynchronization to get back into an operational state. (Virtual machine ID C30836E4-6AA2-4253-BADF-4560AB3EF737)

Hyper-V failed to generate delta for virtual machine ‘VM Name’: Operation aborted (0x80004004). (Virtual machine ID C30836E4-6AA2-4253-BADF-4560AB3EF737)

I suspect it happens due to full MSSQL server backup taking place inside the VM overnight into one of its disks and that disk is a part of the replication. The size of the backup disk is 1Tb.

Having said that this has been working fine for a number of years on the original Windows 2012 R2 host and the same VM with all the disks (including 1Tb backup disk) was happily being replicated to another Win 2012 R2 host without any issues. The only change
now is that this VM is now on Win 2019, so why would it fail to work on Win 2019?

Read full post . . . .

Follow

Hi, I just created an Ubuntu 20.04 VM (using Quick Create) in hyper-v on a Windows 10 Pro machine (version 1903, build 18362.836)

and while I can ping/telnet to other hosts (both on my local lan and also on the internet) DNS resolution does not work.

I am using the "default switch" for the VM with the default settings. The host machine has no issues with DNS resolution.

I also have an ubuntu console via WSL, and it has no issues with DNS resolution.

For example in the Ubuntu VM:

>nslookup microsoft.com

I get:

;; connection timed out; no servers could be reached

When I try name resolution with an external DNS server (e.g. cloudflare)

>nslookup microsoft.com 1.1.1.1

I get:

;; connection timed out; no servers could be reached

Or when I try this:

>dig @1.1.1.1 microsoft.com

I get:

; <<>> DiG 9.16.1-Ubuntu <<>> @1.1.1.1 microsoft.com
; (1 server found)
;; global options: +cmd
;; connection timed out; no servers could be reached

(both of these commands work find in my Ubuntu WSL console, and nslookup works find in the windows CMD terminal)

From within the Ubuntu VM:

I can ping the cloudflare DNS server using the ip address (e.g. ping 1.1.1.1) so networking and ICMP is working.

I can telnet to 1.1.1.1 on port 53, so TCP is working (other IPs work as well)

…and this works:

>nc -z -v -u 1.1.1.1 53

Connection to 1.1.1.1 53 port [udp/domain] succeeded!

So I can reach an external DNS server via UDP on port 53, and that works too, so doesn’t seem like it can be a problem with networking, firewalls, VPNs, whatever… (I’ve tried several other public DNS servers, including google (8.8.8.8) with the same results.

…and yet no attempt to resolve a hostname (or even a reverse lookup) works.

Interestingly, if I force a TCP connection for dig with the +tcp flag, I can get hostnames to resolve, but only with external servers. In other words:

This works: >dig @1.1.1.1 microsoft.com +tcp

This does not: >dig microsoft.com +tcp

/etc/resolv.conf is:

nameserver 127.0.0.53

options edns0

search mshome.net

and the output of systemd-resolve -status is:

Global
       LLMNR setting: no
MulticastDNS setting: no
  DNSOverTLS setting: no
      DNSSEC setting: no
    DNSSEC supported: no
          DNSSEC NTA: 10.in-addr.arpa
                      16.172.in-addr.arpa
                      168.192.in-addr.arpa
                      17.192.in-addr.arpa
                      18.192.in-addr.arpa
                      19.192.in-addr.arpa
                      20.192.in-addr.arpa
                      21.192.in-addr.arpa
                      22.192.in-addr.arpa
                      23.192.in-addr.arpa
                      24.192.in-addr.arpa
                      25.192.in-addr.arpa
                      25.192.in-addr.arpa
                      27.192.in-addr.arpa
                      28.192.in-addr.arpa
                      29.192.in-addr.arpa
                      30.192.in-addr.arpa
                      31.192.in-addr.arpa
                      corp
                      d.f.ip6.arpa
                      home
                      internal
                      intranet
                      lan
                      local
                      private
                      test

Link 2 (eth0)
      Current Scopes: DNS
DefaultRoute setting: yes
       LLMNR setting: yes
MulticastDNS setting: no
  DNSOverTLS setting: no
      DNSSEC setting: no
    DNSSEC supported: no
  Current DNS Server: 192.168.150.81
         DNS Servers: 192.168.150.81
          DNS Domain: ~.
                      mshome.net

(note: 192.168.150.81 is the IP address of the "vEthernet (Default Switch)" Ethernet adapter)

Everything (hyper-V, the default switch, Ubuntu, etc.) is using default settings. I’m at a loss. I could understand if simply doing a name lookup via nslookup using the default name servers didn’t work, as that is probably a resolver configuration problem.
However, specifying an external, reachable DNS sever, and it STILL fails to resolve (at least with the default UDP), and ONLY with the VM — everything else, including WSL, works fine… I don’t get it.

Anyone have any ideas?

Read full post . . . .

Follow

Good morning,

In the world of VMWare where I’m far more comfortable, it’s always been best practice to run I/O intensive applications (Read: SQL, SQL, SQL, and maybe large file servers w/Windows Dedupe enabled) with a dedicated virtual storage controller (namely a pvscsi)
for the VVOL/VMDKs

I can’t find any documentation anywhere, from anyone on what the Hyper-V synthetic/virtual SCSI Controller limits and/or best practices are for such workloads, let alone where the tipping point is to adding another one.

Thoughts or links to material I could go through?  I feel like I’ve exhausted Google and Microsoft’s material.

Read full post . . . .

Follow

Hi, 

I am setting up some event ID monitoring for the Hyper V server and could not find a proper list of all Error and Critical event IDs.  

Is there any Microsoft official documentation which list all Error and Critical event IDs to monitor in Hyper-V-VMMS/Admin log? 

Thanks in advance 

Read full post . . . .

Follow

Hello, I’m new here. Do correct me if I mess up. 

There were 2 VMs in the Hyper-V on Server 2012. It was all good till I added one more VM from a virtual hard disk. When I turned the VM, I lost connectivity to the Sever machine (I was using RDP). I logged in to the machine
physically and saw that the connection was broken. There’s no hardware issues that I can think of. LAN cable is good and strong. 

Physical NIC shows "Network cable unplugged" and virtual nic shows "Unidentified network". I used the External switch in Hyper V. 

Also, I need the AD in the VMs to access network paths.

It would be a LOT of help if you could give me a hand here.

Read full post . . . .