Hyper-V

Go-Que offers news and technical knowledge articles from all IT visualization software brands. Go-que is sponsored by go-que.net & go-que.nl.

Managementos Virtual Adapters do not receive IP address from ICS DHCP Server

Hey,

The goal of the project that I am working on is to create a subnet, with DHCP and NAT, of virtual adapters on the management OS.

(Please do not question why I would do such a thing)

To accomplish this I created a hyper-v Internal Virtual Switch with the command

New-VMSwitch -SwitchName "V Switch" -SwitchType Internal

and I also created multiple virtual adapters connected to that switch.

Add-VMNetworkAdapter -ManagementOS -Name "V Adapter1" -SwitchName "V Switch”
Add-VMNetworkAdapter -ManagementOS -Name "V Adapter2" -SwitchName "V Switch”
Add-VMNetworkAdapter -ManagementOS -Name "V Adapter3" -SwitchName "V Switch”

Then connected a physical adapter (connected to the internet) to the internal virtual switch using Internet connection sharing (ICS). Which turned the internal virtual switch’s adapter into a gateway with Ip address 192.168.137.1. The other adapters, V Adapter1
ect…, should be apart of the subnet and get an Ip address in the range 192.168.137.xxx but they do not get responses from Internet connection sharing’s DHCP server and have APIPA addresses.

I tested to see if I could get an Ip address from a VM attached to the internal virtual switch and the VM was able to get the Ip address 192.168.137.142 from the DHCP server just fine.

I also tested to see if I could get an Ip address using the ManagementOs virtual adapter "V Adapter1" by using a custom protocol driver that spoofed the source mac address (send DHCP discover with different MAC) and set the adapter in promiscuous
mode(Receive messages with MACs other than the adapters own MAC). It was also able to get an Ip address.

Does anyone have any idea why the ManagementOs virtual adapters are not able to get an Ip address from ICS’s DHCP server?

Also forgot to mention that if I set a static Ip address for the ManagementOs virtual adapters they work all perfectly fine. It just seems like the DHCP discover message is ignored by ICS if it is from the ManagementOs virtual adapters.

Any ideas of why this happens or a way to get Ip address for ManagementOs virtual adapters from the ICS DHCP server would be a great help.

Thanks!

Read full post . . . .

Is there a tool that converts VMDK from vSAN to VHD files

Hello, does a tool exist that I can connect my hyperv machine to an existing vmware environment and run it so it can convert the virtual machines into a VHD format. 

I’m being asked this question and unfortunately I don’t know the answer. If it does exist, is there one that runs like vmware converter where it does it on the fly while the machine is on and I simply have to turn the machine on after it is done converting?

Thanks!

Read full post . . . .

Hyper-v replica between hyper-v server 2016 and windows server 2019?

Hi,

Is it possible to have hyper-v replica between hyper-v server 2016 (core) and windows server 2019?

Consider that VM
configuration versions
are the same.

Read full post . . . .

Detecting VM boot to desktop

Hi all,

Looking around I haven’t seen any elegant way to determine that a VM has booted successfully to the desktop (assuming autologon).

Is there a Microsoft approved way of detecting this? Or is it only "check if a service is running", etc semi-hacks?

Thanks for any insights

m

Read full post . . . .

Server problem. ProLiant DL360 Gen9 – VM Windows Server 2016 – Randomly Freezes

Hi.

For some time I have a problem with VM (Windows Server 2016) on the HP Proliant DL360 Gen9 server.

The machine has been freezing for some time. I can’t get to it through RDP, SSH. When I want VM shutdown on Hypervisor, I get the error "VM state does not allow it to close".

I get errors on VM:

DCOM 10010 - "The server did not register in DCOM within the required time."

and

WAS 5010 - "The process serving the application pool did not respond to the ping command. The process identifier.

The problem repeats every few days or once a month.

The problem usually lasts 30 minutes.

I have already tried many solutions. Unfortunately, no result …

Thanks for any help.

Read full post . . . .

WS2106 Evaluation > change host

Hi,

Can i move virtual machine with Windows Server 2016 evaluation (180days) from one Hyper-V host to other?

Will I lost my evaluation time? I had to do lot of changes and installed many programs so I don’t want to do it again, but i have to move this machine to other host.

Read full post . . . .

Connecting Hyper-V servers from Win 2016 console to Win servers Hyper V Cluster 2008

Hello Everyone:

Actually i have a Hyper-v cluster on Windows Server 2012 and i have a server that i use for connecting to this using Hyper-v tools .  Connection in this schema is fine.  Few month we created a new cluster on Windows Server 2016 and in this case
i have other server with win server 2016 that we are using for connecting us to this.  Final idea, would be, this new server allows me connecting to Windows Server 2012 hosts (from first cluster) and Windows Server 2016 (Corresponding new cluster).

Using Failover and trying to connecting me from Win server 2016 to Host on Windows server 2012 (Node or nodes from first cluster).  I obtain the following error:

Actually when i am trying to connect me from Win 2016 (Hyper V Console Server) to Win server 2008 hosts via hyper v Manager and i am not using an administrator user i get the following error

But, if i use a server administrator and i am trying using same console i can to access both servers: Win 2016 and win 2008

So my questions are: 

1) Win 2016 Hyper V Manager Console is not compatible for connecting me old versions hosts?

2) If connection could be possible Would i need a special priviledges?. Because when i trying to do the same connection with an Administrator the error doesn’t appear

Please help me with this

Kind regards

Read full post . . . .

Connecting Hyper-V servers from Win 2016 console to Win servers Hyper V Cluster 2008

Hello Everyone:

Actually i have a Hyper-v cluster on Windows Server 2012 and i have a server that i use for connecting to this using Hyper-v tools .  Connection in this schema is fine.  Few month we created a new cluster on Windows Server 2016 and in this case
i have other server with win server 2016 that we are using for connecting us to this.  Final idea, would be, this new server allows me connecting to Windows Server 2012 hosts (from first cluster) and Windows Server 2016 (Corresponding new cluster).

Using Failover and trying to connecting me from Win server 2016 to Host on Windows server 2012 (Node or nodes from first cluster).  I obtain the following error:

Actually when i am trying to connect me from Win 2016 (Hyper V Console Server) to Win server 2008 hosts via hyper v Manager and i am not using an administrator user i get the following error

But, if i use a server administrator and i am trying using same console i can to access both servers: Win 2016 and win 2008

So my questions are: 

1) Win 2016 Hyper V Manager Console is not compatible for connecting me old versions hosts?

2) If connection could be possible Would i need a special priviledges?. Because when i trying to do the same connection with an Administrator the error doesn’t appear

Please help me with this

Kind regards

Read full post . . . .

Issues connecting to Hyper-V server in WORKGROUP

I might be in the wrong category for this but my issue is really about enabling WinRM so that I can connect to my hyper-v server.

I have set my network connection type to private, but when I try to do winrm quickconfig it reports that it wont work because its public.

PS C:Windowssystem32> Get-NetConnectionProfile                                                                        

Name             : Network
InterfaceAlias   : Ethernet
InterfaceIndex   : 13
NetworkCategory  : Private
IPv4Connectivity : Internet
IPv6Connectivity : NoTraffic

PS C:Windowssystem32> winrm quickconfig                                                                               WinRM service is already running on this machine.
WSManFault
    Message
        ProviderFault
            WSManFault
                Message = WinRM firewall exception will not work since one of the network connection types on this machine is set to Public. Change the network connection type to either Domain or Private and try again.

Error number:  -2144108183 0x80338169
WinRM firewall exception will not work since one of the network connection types on this machine is set to Public. Change the network connection type to either Domain or Private and try again.

I’m really stuck on this one. Maybe it would help to connect through a domain but my plan was to run my domain server on this hyper-v host that I’m unable to connect to.

Read full post . . . .

Unstable Hyper-V behaviours when access through Remote desktop

I’m asking this in Windows Server sub-forum because my actual host OS Windows 10 does not have a dedicated Hyper-V sub-forum.

Late last year I was running a couple of Windows 10 client VMs on my home desktop PC to test Windows Autopilot and MDM. I would access my home computer from outside via RDC and had no problems operating the VMs (Virtual Machine Connection).

This year, I’m not exactly sure what’s changed, but it seems like accessing the VM display console cannot succeed. Either the VMC window would get stuck resizing the window to the VM’s desktop resolution and eventually close by itself, or it’d hang with
corrupted display.

There are corresponding crash events in Application log.

Log Name:      Application
Source:        .NET Runtime
Date:          15/1/2020 15:22:16
Event ID:      1026
Task Category: None
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      HYPERVHOST
Description:
Application: VmConnect.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: exception code c0000005, exception address 00007FFA5C994060

Event Xml:

 
   
    1026
    2
    0
    0x80000000000000
   
    42127
    Application
    HYPERVHOST
   
 

 
    Application: VmConnect.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: exception code c0000005, exception address 00007FFA5C994060

 

Log Name:      Application
Source:        Application Error
Date:          15/1/2020 15:22:16
Event ID:      1000
Task Category: (100)
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      HYPERVHOST
Description:
Faulting application name: VmConnect.exe, version: 10.0.18362.1, time stamp: 0xa8d2f2dc
Faulting module name: atidxx64.dll, version: 26.20.15003.5016, time stamp: 0x5df7d2d3
Exception code: 0xc0000005
Fault offset: 0x0000000000014060
Faulting process id: 0x32b4
Faulting application start time: 0x01d5cb7481d2a7df
Faulting application path: C:WINDOWSsystem32VmConnect.exe
Faulting module path: C:WINDOWSSystem32DriverStoreFileRepositoryc0349841.inf_amd64_d70567d658937ff8B349895atidxx64.dll
Report Id: e506f08b-f1b7-418f-a14e-5a7df056b38a
Faulting package full name: 
Faulting package-relative application ID: 
Event Xml:

 
   
    1000
    2
    100
    0x80000000000000
   
    42128
    Application
    HYPERVHOST
   
 

 
    VmConnect.exe
    10.0.18362.1
    a8d2f2dc
    atidxx64.dll
    26.20.15003.5016
    5df7d2d3
    c0000005
    0000000000014060
    32b4
    01d5cb7481d2a7df
    C:WINDOWSsystem32VmConnect.exe
    C:WINDOWSSystem32DriverStoreFileRepositoryc0349841.inf_amd64_d70567d658937ff8B349895atidxx64.dll
    e506f08b-f1b7-418f-a14e-5a7df056b38a
   
   

   
   

 

Worse is if that corrupt VMC window appears, I could very well lose RDC connection to my computer.

I have to get back home to re-gain access to the OS via physical monitor displays. In the physical logon session, I have connect and vmconnect.exe can render the VM screens. The error below probably explains the RDC failure.

Log Name:      System
Source:        Microsoft-Windows-DriverFrameworks-UserMode
Date:          15/1/2020 17:21:51
Event ID:      10110
Task Category: User-mode Driver problems.
Level:         Critical
Keywords:      
User:          SYSTEM
Computer:      HYPERVHOST
Description:
A problem has occurred with one or more user-mode drivers and the hosting process has been terminated.  This may temporarily interrupt your ability to access the devices.
Event Xml:

 
   
    10110
    1
    1
    64
    0
    0x2000000000000000
   
    29917
   
   
    System
    HYPERVHOST
   
 

 
   
      {b125172c-e769-468f-ac22-28b8331ebce8}
      8
      2
      0
      1879048193
      0
      4294967295
   

 

Log Name:      System
Source:        Microsoft-Windows-DriverFrameworks-UserMode
Date:          15/1/2020 17:21:51
Event ID:      10111
Task Category: User-mode Driver problems.
Level:         Critical
Keywords:      
User:          SYSTEM
Computer:      HYPERVHOST
Description:
The device Microsoft Remote Display Adapter (location (unknown)) is offline due to a user-mode driver crash.  Windows will attempt to restart the device 5 more times.  Please contact the device manufacturer for more information about this problem.
Event Xml:

 
   
    10111
    1
    1
    64
    0
    0x2000000000000000
   
    29918
   
   
    System
    HYPERVHOST
   
 

 
   
      {b125172c-e769-468f-ac22-28b8331ebce8}
      Microsoft Remote Display Adapter
      (unknown)
      SWDREMOTEDISPLAYENUMRDPIDD_INDIRECTDISPLAY&SESSIONID_0001
      5
   

 

And even worse scenario is when I get the corrupted VMC window, lose connection, and cannot even get into the OS via physical means; the monitors keep sleeping and waking with blank screens. I might be able to connect to the VMs via RDC Manager (with VM
mode) from another computer to interact and shut them down, but since the host OS is inaccessible at this state I have to hard reset the computer.

I later found scores of display driver restarts, and even broken dwm.exe which likely explains the loss of physical access.

Log Name:      System
Source:        Display
Date:          15/1/2020 22:31:50
Event ID:      4101
Task Category: None
Level:         Warning
Keywords:      Classic
User:          N/A
Computer:      HYPERVHOST
Description:
Display driver amdkmdap stopped responding and has successfully recovered.
Event Xml:

 
   
    4101
    3
    0
    0x80000000000000
   
    30166
    System
    HYPERVHOST
   
 

 
    amdkmdap
   
   

 

Log Name:      Application
Source:        Application Error
Date:          15/1/2020 22:31:53
Event ID:      1000
Task Category: (100)
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      HYPERVHOST
Description:
Faulting application name: dwm.exe, version: 10.0.18362.387, time stamp: 0x8e064b77
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0xe0464645
Fault offset: 0x0000000000000000
Faulting process id: 0x4718
Faulting application start time: 0x01d5cbb05c00d5c0
Faulting application path: C:WINDOWSsystem32dwm.exe
Faulting module path: unknown
Report Id: 350b442b-5588-4cee-a1ca-cf09d0254be7
Faulting package full name: 
Faulting package-relative application ID: 
Event Xml:

 
   
    1000
    2
    100
    0x80000000000000
   
    42330
    Application
    HYPERVHOST
   
 

 
    dwm.exe
    10.0.18362.387
    8e064b77
    unknown
    0.0.0.0
    00000000
    e0464645
    0000000000000000
    4718
    01d5cbb05c00d5c0
    C:WINDOWSsystem32dwm.exe
    unknown
    350b442b-5588-4cee-a1ca-cf09d0254be7
   
   

   
   

 

Log Name:      Application
Source:        Dwminit
Date:          15/1/2020 22:32:00
Event ID:      0
Task Category: None
Level:         Warning
Keywords:      Classic
User:          N/A
Computer:      HYPERVHOST
Description:
The Desktop Window Manager process has exited. (Process exit code: 0x000000ff, Restart count: 1, Primary display device ID: )
Event Xml:

 
   
    0
    3
    0
    0x80000000000000
   
    42332
    Application
    HYPERVHOST
   
 

 
    0x000000ff
    1
   
   

 

Log Name:      Application
Source:        Application Hang
Date:          15/1/2020 22:33:20
Event ID:      1002
Task Category: (101)
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      HYPERVHOST
Description:
The program dwm.exe version 10.0.18362.387 stopped interacting with Windows and was closed. To see if more information about the problem is available, check the problem history in the Security and Maintenance control panel.
 Process ID: 3fdc
 Start Time: 01d5cbb044188c04
 Termination Time: 20308
 Application Path: C:WindowsSystem32dwm.exe
 Report Id: 0d04efe7-c646-4105-aa35-9c80142c42ea
 Faulting package full name: 
 Faulting package-relative application ID: 
 Hang type: Unknown

Event Xml:

 
   
    1002
    2
    101
    0x80000000000000
   
    42352
    Application
    HYPERVHOST
   
 

 
    dwm.exe
    10.0.18362.387
    3fdc
    01d5cbb044188c04
    20308
    C:WindowsSystem32dwm.exe
    0d04efe7-c646-4105-aa35-9c80142c42ea
   
   

   
   

    Unknown
    55006E006B006E006F0077006E0000000000
 

Seems like I’m forced to work with Hyper-V only through physical display now. What is it about Hyper-V services and components that can make it (now) unsuitable for control over RDC?


The melody of logic will always play out the truth. ~ Narumi Ayumu, Spiral

Read full post . . . .

Go Que Newsroom Categories

Fatal error: Allowed memory size of 67108864 bytes exhausted (tried to allocate 36 bytes) in /home/content/36/8658336/html/goquecom/wp-includes/wp-db.php on line 1996