There may be a version mismatch between this computer and the destination server or VHD.
This error is appearing while installing Hyper-V in 2016. Please help us on this
↧
There may be a version mismatch between this computer and the destination server or VHD.
↧
Azure Site Recovery with Hyper-V: Error 0x8079FFFF
Hello!
I have a customer who has been replicating three VM's to Azure Site Recovery for a few years. A week ago the replication stopped working - Azure showed the Hyper-V server was disconnected and I when trying to update the Azure Vault keys on the Hyper-V Server I was getting an error message about the keys not being the correct type. After finding very little information on the web regarding the specific error I decided to disable the replication on Azure and followed these steps (https://docs.microsoft.com/en-us/azure/site-recovery/site-recovery-manage-registration-and-protection) on the Hyper-V Server to manually disable replication of the VM's. Hyper-V Manager showed that the VM's were no longer being replicated.
So I re-added the Hyper-V Server to Azure, installed the Microsoft Azure Recovery Services Agent & Microsoft Azure Site Recovery Provider in addition to the Azure keys on the Hyper-V Server. Azure then could see the Hyper-V Server and VM's and I thought I was good to go.
However, when I try to start the replication from Azure, I get an error message "Protection couldn't be enabled", The details show:
Error ID70094
Error Message Protection couldn't be enabled for the virtual machine.
Provider error Provider error code: 31343
Provider error message:
The operation failed with the error: Enable replication failed for virtual machine 'XXXX'. Service returned an error. (Error Code '8079ffff'). (Virtual Machine ID 7e2bd32e-a5e2-4812-838e-3ca66792e282, Data Source ID 17593282809274,
Task ID 09022f76-3239-4ae3-b064-b77dce2d0477)
I looked on the Hyper-V Server (in various Event Logs) and can't find any further detail other than the 0x8079ffff error code shown above. I get this same error whether I am trying to replicate one of the VM's which had previously been replicating or a new VM which hadn't been replicating to Azure previously.
Does anyone have any suggestions for where I should look?
Thanks! Dave
↧
↧
External Network with Hyper-V
I have 2 Windows servers 2016 connected to an internal switch (192.168.10.1) on Windows 10. 1 of my server is a domain controller with AD DS, DNS and DHCP services installed. On my second server, I have installed Hyper-V. Neasted virtualization is already activated on my virtual machine. When i create an external switch on this server (with powershell or Hyper-V manager) and connect it to a virtual machine, there is a problem. My virtual machine doesn't receive any IP address fom my DNS. If i gave a my machine a static IP address, it can ping my virtual switch, but it doesn't go any further.
My configuration
Domain Controller (static)
IP address : 192.168.10.2
Subnet mask : 255.255.255.0
Default gateway : 192.168.10.1
Preferred DNS server : 127.0.0.1
Hyper-V server (static)
IP address : 192.168.10.3
Subnet mask : 255.255.255.0
Default gateway : 192.168.10.1
Preferred DNS server : 192.168.10.2
My DHCP Server work properly. If I choose to obtain an IP address automatically on my external switch, I receive it.
Do you have an idea why my VM cannot go further than my virtual switch?
thank
Laflèche Chevrette
↧
Enhanced session mode for Ubuntu on Windows 2016 Hyper-V, not working
Hi, I created an Ubuntu VM on Win10 Pro 1909 and it runs in Enhanced Session mode with no problems. I have the XRDP login and can use multiple monitors, copy&paste, drive sharing and so on.
I need to put this machine on a Windows 2016 Server with Hyper-V.
Exporting the VM results in a v9 config, unsupported on Win2016 that is limited to v8.
So I just copied the VM diskon the 2016 server and recreated the VM, copying each of the setting from the Win10 VM.
Now, the VM starts and runs but I cannot use Enhanced session mode on it, just regular vmconnect session.
Hyper-V on win2016 is configured to use Enhanced session mode (Enhanced session policy and Enhanced session mode flagged).
I ran the set-vm -EnhancedSessionTransportType HvSocket command to modify the newly created Ubuntu machine.
From the Win2016 host I can access Win10 machines in Enhanced mode.
From the Win2016 host I can connect the HyperV on the Win10 machine, and open the Ubuntu machine in Enhanced session mode.
So, basically, I'm pretty sure the Win2016 host is fine and configured and machines can run in Enh.Session mode, if they are Windows machines.
My question is: are Ubuntu VMs supported in Enhanced Session mode when running in Hyper-V on Windows 2016? I just find people referring to Windows guests.
If supported, what am I missing on my Win2016 host?
Thanks
↧
Failed to map guest I/O buffer for write access with status 0xC0000044
Hi,
In our environment we have a Windows 10 virtual machine which resides on server 2019 hyper-v server.
We are taking backup of this virtual machine through DPM server which is also installed on a virtual machine.
An error is logging constantly on hyper-v server which is as below..
Failed to map guest I/O buffer for write access with status 0xC0000044. Device name = E:\Hyper-V\Win10-06\Virtual Hard Disks\Win10-06.vhdx
I'm unable to find a satisfying answer for this error.
Is there anyone who can help us regarding this issue?
Thanks.
In our environment we have a Windows 10 virtual machine which resides on server 2019 hyper-v server.
We are taking backup of this virtual machine through DPM server which is also installed on a virtual machine.
An error is logging constantly on hyper-v server which is as below..
Failed to map guest I/O buffer for write access with status 0xC0000044. Device name = E:\Hyper-V\Win10-06\Virtual Hard Disks\Win10-06.vhdx
I'm unable to find a satisfying answer for this error.
Is there anyone who can help us regarding this issue?
Thanks.
↧
↧
Hyper-V 2012 R2 - Cannot Install Software on Windows 10 VMs
This is a very strange problem and I hope someone out there in TechNet has an idea what is going on.
I have a Windows Server 2012 R2 Hyper-V Failover Cluster that I am helping a friend with.
We have a number of virtual servers running in the cluster with no issue.
When I attempt to load a Windows 10 virtual machine (version 1903 or 1909), the virtual machine installs just fine but I cannot installany software. I have tried loading multiple software packages, but every time I will get the UAC prompt and then nothing happens.
Also, in the task manager, I have a large number of WERFault.exe instances. I am getting no notifications of any problems from the OS or really any thread to pull on in event viewer.
I have tried different methods of licensing the VM including KMS and MAK. Both work fine. The Hyper-V host is licensed with a Windows Server Datacenter key.
Is there anything baked in Windows 10 that would prevent software installs after the install of the OS? Has anyone seen this before??
Thanks very much!!
Syst3m32 https://www.sysadminsoup.com
↧
Correct Way for Teaming
Hi,
May we have some suggestions about using Windows Teaming Method with Hyper-V and stacked network switches. Currently, we are using the below settings which we believe sometimes causing connectivity problems with Virtual Machines because we are losing connectivity
to Virtual Machines and then we have to remove the virtual nic from VM and add it again.
1. Two Physical NICs Teamed for Server Management (No Virtual Switch)
2. Two Physical NICs Teamed for Domain Connected Virtual Machines (One Virtual Switch for Teamed Interface)
3. Two Physical NICs Teamed for DMZ Connected Virtual Machines (One Virtual Switch for Teamed Interface)
↧
Hide Connection Bar in Virtual Machine Connection
Hello All,
I am reading this article:
https://ravingroo.com/1097/captain-obvious-log-hide-remote-desktop-connection-bar/
And am trying to do this with my Hyper-V Virtual Machine Connection windows, but do not see this available in the place that I would expect it via the dialogs found in the above article.
Where is this hiding? :)
Thank you,
Michael
↧
Have created Hyper V home lab on laptop. Cannot use "Enhanced Session Mode" to login
enhanced session mode is on on my guest Server (domain), and guest workstation. I have turned on remote desktop on workstation. I have added domain user account to remote desktop users group from workstation using domain admin credentials. Still getting
same stupid message about having to belong to the group. I have already tried rebooting. basic login works fine. What is the problem?
↧
↧
A Problem with Hyper-V on Windows10 Pro
Hi, I used the Ubuntu 18.04 Virtual Machine in Hyper-V offered by Window10 Pro. However, I met a problem and could not connect with it now. And it shows that "Video of remote operation disconnected" As I am a Chinese student, so my description may not be very accurate and I am sorry for that. Thank you very much!
↧
Using a COM Port on a VM
I run a UPS which is monitored via a USB connection to a physical machine.
I have now replaced the Physical machine with a VM (Hyper-V)
But despite reading the various posts I do not see/understand how I can link the VM's COM port to the physical USB port on the VM Host.
I think the only way to link the UPS to the computer is via a USB cable
Looking at Device Manager on the VM I can see COM1 and COM2 listed and marked "Working Normally".
On the Settings Page of the VM I started by setting a pipe name VCOM1 \\.\pipe\VCOM1
But that's where I grind to a halt.
I am sure the answer is buried in one of the many threads but I cannot see the wood for the trees
Help would be very appreciated,
Jean
↧
Hyper-V, internal switch, ICS, no internet
Hello,
I'm hoping you can help: I am running:
Windows 10 Pro Build 18363. I have created a VM in hyper-V. I have created an internal switch and am sharing my internet connection to my ethernet adapter (NIC).
My internal switch looks like this:
inside my vm. The network adapter looks like this:
I have no internet and cannot ping my gateway:
All of the reading that I have done says this should work. Does anyone have any ideas?
thanks.
Terry
↧
VMs with Shared VHD sets fail while migrating or after a few days of creation.
We are running a brand new DELL R470 cluster with 4 hosts.
Dell handled and verified the installation of the operating system - Windows 2019 server, withstorage spaces direct - and installation of the Failover cluster with all storage divided into 4CSVs.
On top of it we are trying to run a guest FC with shared VHD sets.
Now, this is where things get interesting.
Creating the VMs and adding shared VHDs works and at the first glance there are no problems or issues with it.
After the cluster creation, we have tested the Live/Quick migration of the VMs from one host to another - no issues.
That was friday.
On monday, a completely different story.
VMs Fail to start after migration. Error we are getting is:
´An error occurred for resource VM-TEST1.` check the info details for more.
In Information details it says:
Event id: 1069
Cluster resource 'Virtual Machine VM-TEST1' of type 'Virtual Machine' in clustered role 'VM-TEST1' failed. The error code was '0x780' ('The file cannot be accessed by the system.').
Event id:21502
´Virtual machine failed to start´
From our tests, the only way to resolve this is remove all shared disks from the VMs involved, copy them over to a newfolder and reattach them. VMs work again - for a few days when the error recurrs.
Trying to add the disks from the same location throws an error in FCM after clicking Apply: Adding the device ´hdd bla bla´ failed.
NOTE: it is not only the migration that triggers something like this, VMs have issues even without migration - visible after a few days. As long as you are not migrating them or updating their configuration (adding another drive, removing an ISO image perhaps) it is ok, but as long as you are going to change the configuration it breaks sayingAn error occurred while updating the VM config settings. In the meantime the guest cluster works like a charm and there are no issues.
Most of the event logs related to Hyper-V point to some problem but none say directly what it might be
Hyper-vShared-VHDXadminEvent ID 128Error opening handle for initiator. Initiator: {00000000-0000-0000-0000-000000000000}. Hostname: HOST1. File: \HYPER-V\VM-CLTEST-SPTEST\VM-CLTEST_TEST_USERDATA.VHDS:SharedVirtualDisk. Error: The layered file system driver for this IO tag did not handle it when needed..
Hyper-v-vmms adminEvent ID 15268
Failed to get the disk information.
Hyper-V-Workeradminevent id 12030
'VM-TEST1' failed to start. (Virtual machine ID D072D735-89FD-45EC-BD76-5D6A0AC0DCC5)
Hyper-v-workeradminevent id 12010
The description for Event ID 12010 from source Microsoft-Windows-Hyper-V-Worker cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.
If the event originated on another computer, the display information had to be saved with the event.
The following information was included with the event:
VM-TEST1
D072D735-89FD-45EC-BD76-5D6A0AC0DCC5
Synthetic SCSI Controller
%%2147944320
0x80070780
5EA505E4-42AC-4802-B74B-F896ED8B2218
The locale specific resource for the desired message is not present
The description for Event ID 12140 from source Microsoft-Windows-Hyper-V-SynthStor cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.
If the event originated on another computer, the display information had to be saved with the event.
The following information was included with the event:
VM-TEST1
D072D735-89FD-45EC-BD76-5D6A0AC0DCC5
C:\ClusterStorage\Volume04\TEST\SHARED DISK\Shared_disk1.vhds
%%2147944320
7864368
80070780
The locale specific resource for the desired message is not present
Hyper-v-vmms operationalEvent ID 1106
vm\service\vmmgr\vmmsrealizedvirtualmachine.cpp(10448)\vmms.exe!00007FF6742C1711: (caller: 00007FF67462BE36) LogHr(553) tid(338c) 80041001 Msg:[vm\service\vmmgr\vmmsrealizedvirtualmachine.cpp(10368)\vmms.exe!00007FF674308803: (caller: 00007FF6741CD1F5) Exception(1393) tid(338c) 80041001 ]
vm\service\vmmgr\vmmsrealizedvirtualmachine.cpp(10368)\vmms.exe!00007FF674308803: (caller: 00007FF6741CD1F5) Exception(1393) tid(338c) 80041001
vm\service\fr\frutilities.cpp(11526)\vmms.exe!00007FF67449BA4A: (caller: 00007FF67449A6EB) LogHr(552) tid(338c) 80070002 The system cannot find the file specified.
Msg:[vm\service\fr\frutilities.cpp(11496)\vmms.exe!00007FF67449B882: (caller: 00007FF67449A6EB) Exception(1389) tid(338c) 80070002 The system cannot find the file specified.
]
vm\service\fr\frutilities.cpp(11496)\vmms.exe!00007FF67449B882: (caller: 00007FF67449A6EB) Exception(1389) tid(338c) 80070002 The system cannot find the file specified.
vm\service\ethernet\vmethernetconnectionresourcepool.cpp(2035)\vmms.exe!00007FF674329E86: (caller: 00007FF674205EED) Exception(1387) tid(338c) 80070002 The system cannot find the file specified.
Any ideas anyone?
Thank you very much
↧
↧
How to manage Azure backups on Hyper-V Server (Core)
I've successfully been able to setup Azure backups for my Hyper-V Server 2016 server using Windows Admin Centre but post setup I'm not able to change my policy or schedule because all the docs state I need to run the MABS software on the server (which
I cant as it doesn't have a GUI and the powershell DPM commands I've tried don't seem to be installed).
The fact I'm not able to edit the policy also (from what I can see) means I wouldn't be able to restore the backup which makes them pretty much useless.
Having reviewed most of the docs for supported OS Hyper-V doesn't really get a mention so its possible this just isn't possible but it would be good to get another opinion on it - I have seen Datacentre core listed and the fact the backups have been setup is giving me hope.
I've considered installing the backup software on another server (details here ms downloads id=55269) but if that doesn't allow me to connect to the Hyper-V Core instance and manage the backup there it would be pointless.
Any suggestions on how best to proceed with this one would be appreciated.
Version: Microsoft Hyper-V Server 2016
The fact I'm not able to edit the policy also (from what I can see) means I wouldn't be able to restore the backup which makes them pretty much useless.
Having reviewed most of the docs for supported OS Hyper-V doesn't really get a mention so its possible this just isn't possible but it would be good to get another opinion on it - I have seen Datacentre core listed and the fact the backups have been setup is giving me hope.
I've considered installing the backup software on another server (details here ms downloads id=55269) but if that doesn't allow me to connect to the Hyper-V Core instance and manage the backup there it would be pointless.
Any suggestions on how best to proceed with this one would be appreciated.
Version: Microsoft Hyper-V Server 2016
↧
Live Migration Fails Only On Configuration Version 9.0 VM's
We have a brand new built cluster on Server 2019. After the initial configuration live migration was working flawlessly. Now all of a sudden we're running into issues with Live Migration. I've narrowed it down to only Configuration Version 9.0 machines. There are a handful of configuration version 5.0 machines from our old cluster that we've migrated over and they still are able to Live Migrate without any issues. We can still quick migrate the version 9.0 machines. The only thing that was recently done was that the machines all had storage migrated to another CSV and back to the original one so we could rename it. I've attempted moving one 9.0 machine to the new CSV and still have the same issues. I've even upgraded previously working 5.0 machine to 9.0 and it immediately starting having the same issues.
The error that is listed is simply: Live migration of 'Virtual Machine Hostname' failed.
Source: Microsoft-Windows-Hyper-V-High-Availability
Event ID: 21502
Any help would be greatly appreciated. Searching so far has not turned up anything.
↧
Hyper-V Maximize Window instead of Full Screen Mode
Windows 10 Host, Windows 10 Guest. Clicking "Maximize" of the guest window does not maximize the window but instead goes to full screen mode. Is there a way to get the Hyper-V VM to be maximized instead of going into full-screen mode?
I know you can RDP to the VM which allows use of RDC-Manager and I can achieve almost the same thing that way, but it would be nice to be able to open the default Hyper-V connection to maximized window.
↧
Cluster node - Event 252 - cluster service crashed
We have a 4 node Windows Server 2016 Hyper-V Cluster. Over the weekend, one node of the cluster reported this in the System event log:
"Memory allocated for packets in a vRss queue (on CPU 14) on switch 620355C8-4D29-4D91-BE80-B840921EDC4A (Friendly Name: Team_Trunked) due to low resource on the physical NIC has increased to 256MB. Packets will be dropped once queue size reaches 512MB."
Seven seconds later it reported that it had increased to 512MB, then two seconds later the LiveMigration NIC reported it had begun resetting, then a few seconds later a reset was issued to \device\raidport1 (source: ql2300). After two minutes of this and a few other repeats, I started getting warnings of CSVs no longer being able to access this cluster node and then the Cluster service shut down on this node and all VMs are shut down and migrated to other nodes in the Cluster.
Our weekly DPM backups of the VMs had started about 1.5 hours before this occurred so there was some additional strain on the NICs at this time, though that should have gone through the NIC the OS is running on so I don't know why that would have affected the other NICs where the VMs general data was going through (Team_Trunked) and the LM NIC.
Does it make sense that the first warning about Event 252 would have caused all this or is there more to this?
↧
↧
Dismount-VmHostAssignableDevice : The required virtualization driver (pcip.sys) failed to load.
Hello,
i am testing discrete device assignment in hyper-v 2016.
fresh install of host, fresh vm, unmounting a gpu from host and assigning to vm, works fine.
then after some reboots of the vm, it BSOD, and suddenly i can no longer mount/unmount the device on the host.
PS C:\Users\Administrator> Dismount-VmHostAssignableDevice -LocationPath $locationPath -Force -Verbose
VERBOSE: Dismount-VmHostAssignableDevice will dismount an assignable device so it can be assigned to a virtual machine.
Dismount-VmHostAssignableDevice : The operation failed.
The required virtualization driver (pcip.sys) failed to load.
The operation failed.
The required virtualization driver (pcip.sys) failed to load during a device dismount operation. The dismount
operation has been cancelled.
At line:1 char:1
no matter what i tried (restarting host several times, enabling/disabling the device with powershell commands - Disable-PnpDevice - Enable-PnpDevice), i can't fix it
update:
tried removing the device with devcon.exe, tried installing the official amd driver for the card on the host. still the same problem.
so, what is causing this issue? how can it be fixed?
↧
Windos Server 2019 - Hyper-V Machine random reboot - Kernel-Power 41
Good day, we have configured S2D cluster on Windows Server 2019 1809 (17763.1039) cluster successly pass tests via Test-Cluster and working with no problem, but if we moving virtual machive using live migration from other S2D cluster ( Windows Server 2016 ). After migration, vm working some time ( random 1 - 8 hours ) and rebooting with errors.
- <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
- <System><Provider Name="Microsoft-Windows-Kernel-Power" Guid="{331C3B3A-2005-44C2-AC5E-77220C37D6B4}" /> <EventID>41</EventID> <Version>4</Version> <Level>1</Level> <Task>63</Task> <Opcode>0</Opcode> <Keywords>0x8000400000000002</Keywords> <TimeCreated SystemTime="2020-02-14T18:43:25.917237000Z" /> <EventRecordID>352436</EventRecordID> <Correlation /> <Execution ProcessID="4" ThreadID="8" /> <Channel>System</Channel> <Computer>vm.example.com</Computer> <Security UserID="S-1-5-18" /> </System>
- <EventData><Data Name="BugcheckCode">265</Data> <Data Name="BugcheckParameter1">0xa39ff768722a4831</Data> <Data Name="BugcheckParameter2">0xb3b703eec4ab58f9</Data> <Data Name="BugcheckParameter3">0x2000001a0</Data> <Data Name="BugcheckParameter4">0x7</Data> <Data Name="SleepInProgress">0</Data> <Data Name="PowerButtonTimestamp">0</Data> <Data Name="BootAppStatus">0</Data> <Data Name="Checkpoint">0</Data> <Data Name="ConnectedStandbyInProgress">false</Data> <Data Name="SystemSleepTransitionsToOn">0</Data> <Data Name="CsEntryScenarioInstanceId">0</Data> </EventData></Event><Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
- <System><Provider Name="Microsoft-Windows-WER-SystemErrorReporting" Guid="{ABCE23E7-DE45-4366-8631-84FA6C525952}" EventSourceName="BugCheck" /> <EventID Qualifiers="16384">1001</EventID> <Version>0</Version> <Level>2</Level> <Task>0</Task> <Opcode>0</Opcode> <Keywords>0x80000000000000</Keywords> <TimeCreated SystemTime="2020-02-14T18:43:29.303375100Z" /> <EventRecordID>352517</EventRecordID> <Correlation /> <Execution ProcessID="0" ThreadID="0" /> <Channel>System</Channel> <Computer>vm.example.com</Computer> <Security /> </System>
- <EventData><Data Name="param1">0x00000109 (0xa39ff768722a4831, 0xb3b703eec4ab58f9, 0x00000002000001a0, 0x0000000000000007)</Data> <Data Name="param2">C:\Windows\MEMORY.DMP</Data> <Data Name="param3">681c7c75-c8ec-42ae-ad15-008309d23974</Data> </EventData></Event>
after rebooting vm works correctly.If stop vm on one cluster manually move files and start vm works correctly.
↧
Remotely Manage a Non-Domain Hyper-V Server from Domain Joined PC
Helou guys,
pls for help with managing a non-domain Hyper-V server from domain joined PC.
Client= Windows 10 1903 (Domain Joined) IP= 192.168.20.52
Hyper-V host= Hyper-V Core Server 2019 (Workgroup) IP= 192.168.20.177
Here is a config from Server (Workgroup)
Here is a config from Client (Domain Joined)
When I'm trying to connect to Hyper-V, I'm getting an error
Thanks for advice guys!
↧