Hi all I have a question I have an old server run windows 2012 Hyper-V standalone that runs virtual machines 2012 and I want to transfer them to a new server run Windows server 2016 Hyper-V standalone what is the right way to do it
Thank you
sofy
↧
Hi all I have a question I have an old server run windows 2012 Hyper-V 2012 standalone that runs virtual machines 2012 and I want to transfer them to a new server run Windows server 2016 Hyper-V standalone what is the right way to do it Thank you
↧
Hyper-V Server Licensing
I have a developer that wants to install a service in Hyper-V Server because it doesn't require a Windows license. Does the license agreement of Hyper-V Server allow this - to use the operating environment for a purpose, different than running Hyper-V virtual machines?
↧
↧
External Ethernet Adapter is already bound to the microsoft virtual switch protocol
Hi,
I have a Virtual Switch that already bound to a Physical Adapter, and I would like to create another Virtual Switch to be bound to the same Physical Adapater, but I'm getting an error: "External Ethernet Adapter is already bound to the microsoft virtual switch protocol" Any help?
↧
Windows Server 2019 BugCheck139
Hi,
I've been miserable with this BugCheck139 on freshly installed Hyper-v.
I have Windows Server2019 at work and this machine is running several VM in Hyper-v.
One VM is running Windows Server 2019 as well and activated with the AVMA key.
so, This machine sometimes crash randomly with BugCheck code 139.
I googled and researched a lot, and this seems something I cannot fix by myself.
I know I need to upload memory.dmp, but how should I upload this? i 7z the file and still 400MB big.
here's the error messages.
The computer has rebooted from a bugcheck. The bugcheck was: 0x00000139 (0x0000000000000003, 0xffffce8bbc89d990, 0xffffce8bbc89d8e8, 0x0000000000000000). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 17911e96-6cc3-427e-a409-a5108f0d0dc2.
I've been miserable with this BugCheck139 on freshly installed Hyper-v.
I have Windows Server2019 at work and this machine is running several VM in Hyper-v.
One VM is running Windows Server 2019 as well and activated with the AVMA key.
so, This machine sometimes crash randomly with BugCheck code 139.
I googled and researched a lot, and this seems something I cannot fix by myself.
I know I need to upload memory.dmp, but how should I upload this? i 7z the file and still 400MB big.
here's the error messages.
The computer has rebooted from a bugcheck. The bugcheck was: 0x00000139 (0x0000000000000003, 0xffffce8bbc89d990, 0xffffce8bbc89d8e8, 0x0000000000000000). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 17911e96-6cc3-427e-a409-a5108f0d0dc2.
↧
Hyper-V VM unable to network in external network
An issue that is bothering me.
The host is a Windows 2012 R2 server, the Hyper-V VM running on it is also Windows 2012 R2. The virtual switch is configured to be external network. The VM is able to network on the external network only for 3 minutes, after that it automatically becomes internal network effectively, as it can only communicate with the host. Now, if I go and do are reset by setting the virtual switch to become internal then set it back to external, the VM is able to communicate to external network, but only for 3 minutes, after that it again falls back to internal. I removed the virtual switch and re-create a new one, the symptom is the same - 3 minutes external, then become effectively internal.
There are 600 + computers on the network with similar configuration, this VM is the only one having this problem.
The MAC address is statically assigned, so far I have not seen any duplicate in MAC address on the network.
Any suggestion?
Valuable skills are not learned, learned skills aren't valuable.
↧
↧
Hyper-V 2016 BPA Error about ECC Memory even though ECC Memory is in use
BPA Error "USE RAM THAT PROVIDES ERROR CORRECTION"
But the system is running ECC ram
wmic memphysical get memoryerrorcorrection returns:
"""
MemoryErrorCorrection
6
6
"""
Per https://docs.microsoft.com/en-us/windows/win32/cimwin32prov/win32-physicalmemoryarray this means that Multi-bit ECC is in use
How do I fix this? What is the problem?
↧
Black Screen after boot of Windows Server 2012 VM
Dear TechNet-Community,
a strange case, where I need your help:
From today we have the issue, that one of our virtual machine in Hyper-V can't boot.
The Windows Logo appears and after hat there is just a black screen.
I already searched some solutions in the internet and tried the following:
- Create new virtual machine and add the VHD-File to it
- Adding additional HDD-Size
- Run CHKDSK /F - Command
- Booting without network adapter
- Turn Off/On again
- Repaired MBR
- Just waited, if something appears ...
- I also saw the possible solution with editing the registry keys, but I don't have this possibility.
I tried "all" known solutions but nothing helped, do you have any ideas, what I could try?
Many thanks in advance!
Best Regards,
Legio
↧
"Hyper-V failed to enable replication"
Good morning!
I'm running into a problem with Hyper-V and I don't have a lot of information to troubleshoot off of. I'm hoping the experience and knowledge here will help me zero in on a solve for this.
Basics:
I'm trying to enable replication of a single VM'd server from my client's office in Dothan to their office in Auburn (War Eagle!). I'm also trying tore-enable replication of two user VMs from Auburn to Dothan. Dothan's hypervisor is MS Hyper-V running in Windows Server 2019 DE. Auburn's hypervisor is MS Hyper-V running in WS2016 DE. The VM to be replicated
from Dothan is WS2019 DE acting as a DC and an file server. The VMs being replicated from Auburn are Win10 Pro workstations. The purpose of all replication is simple redundancy; offsite backup of each VM in case of catastrophe. The WAN infrastructure is VPN
over broadband. The organization uses ADDS with all users and machines in one domain.
History:
I'd successfully set up replication of the two VMs from Auburn to Dothan a few weeks ago. I ran into issues with Kerberos that were solved by editing the registry on each hypervisor so that Kerberos had to use TCP, and eliminating packet fragmentation at the
VPN routers. Those VMs were replicating consistently until this past weekend.
During the weekend, I had to reformat the volume where the VMs are stored in Dothan. The Auburn server is a mess that I inherited from the last IT guy, nothing is virtualized on this machine and I want some redundancy, so I was going to use DFS to replicate critical files from this server to Dothan. However, when I built Dothan I used ReFS for the storage volume, and since DFS won't run on ReFS, I decided to back up Dothan, burn down the storage volume, reformat with NTFS and restore. I used Win Server Backup in WS2019 to perform a bare metal (full) backup to an external disk. Before running the backups, I merged all checkpoints back into each VHD and created new thin-provisioned VHDs from my thick-provisioned VHDs. I successfully tested each VM with the thin-prov VHDs attached before shutting all VMs down and running the backup set.
Problem:
After formatting the storage volume NTFS, I ran into issues restoring Hyper-V directly from WSB. Instead, I restored the VHDs, built new VMs for my 1 server VM and 2 replicated user VMs, and reconnected the VHDs. Everything boots up in Hyper-V and the machines
run normally. The server VM is up and running with no issues. All the data is there and I can remote into each machine. Once the dust had settled, I attempted to enable replication of the server VM from Dothan to Auburn but received the following error: https://1drv.ms/u/s!Av-G2MTFk-0ZgupOcDu6lQhOgOmLUQ?e=52vnr2
This is proving to be maddening for me because there's no data associated with the error. No code or whatnot. I'm not receiving any errors from the replication wizard in terms of "unable to determine configuration", authentication errors, or anything during the process to make me think these two servers can't talk to each other. They're talking about this replication, they're just not kicking it off.
In an attempt to control for other variables, I decided to re-enable replication of the two VMs from Auburn to Dothan. When I tried, I got this error: https://1drv.ms/u/s!Av-G2MTFk-0ZgupPTJzbNDNF_oiPgw?e=hWtNbE
Unspecified errors are a joy...
I've done my rounds on search engines and tried everything I can think of, but I just keep running into this wall. These VMs were replicating fine before all of this.
Misc:
The Dothan server uses two volumes for Hyper-V. Hyper-V configuration files and small VHDs are stored on E:, which is SSD-based. The Dothan server VM uses a small VHD on E: for it's operating system, and it's smart paging file is parked there too.
Large VHDs and all Hyper-V Replica (inbound-replicated VMs) is stored on D:. The Dothan server VM uses a VHD stored on D: for data storage in its role as a file server. Both my Auburn VMs are stored on D: when they replicate to Dothan, which is exactly how they were before I made all these changes over the weekend.
I've rebooted both hypervisors and I've checked all the VSS writers. No errors there. I can create standard and production checkpoints for each VM, the two VMs in Auburn and the server VM in Dothan.
If anybody can help point me in the right direction on this, I would greatly appreciate it, and I'd be happy to take you for a beer anytime you're in this part of the American south!
-MB
↧
Copy or Cut (and paste) to a Virtual Machine...
Hello!
im nu here and im nu to the use of Hyper-V so please be tolerant :P
The problem is that I can't copy and paste or cut and paste files or directories from desktop (or other locations ) to an opened virtual machine's window, even dragging the object with the mouse, the pointer become the prohibited icon.
So how can I activate this function (if it is possible)?
Read you Soon
Andrea
P.S.: If already exist a topic with this issue, please redirect me ;)
im nu here and im nu to the use of Hyper-V so please be tolerant :P
The problem is that I can't copy and paste or cut and paste files or directories from desktop (or other locations ) to an opened virtual machine's window, even dragging the object with the mouse, the pointer become the prohibited icon.
So how can I activate this function (if it is possible)?
Read you Soon
Andrea
P.S.: If already exist a topic with this issue, please redirect me ;)
↧
↧
Windows 2008 R2/2012 R2 Proc to Core 2016/2019 Licensing
Hi I am trying to License 2008 R2 Enterprise/standard/Datacenter or 2012 R2 Standard/Datacenter with 2016/2019 Standard/Datacenter.
I am just not sure how do we license it from proc to core what is the conversion metrics?
It would be helpful if you can explain with an example.
↧
Slow speed replication hyper-v on 10gb/s network
Hi,
I have a question about replication hyper-v 2019, its have speed limit?.I am asking because it is not operating at full speed.
I tested the speed network iperf and shows - 9,77Gb/s,but when im start replication it only has 1,5Gb/s. Why?.
Thanks for help.
↧
Hyper-V open .vmcx
Dear sir/Madam
I need to open and edit a .vmcx file, is there any application that can help to do so
↧
issue with windows backup
Hi
i am facing this issue while i am taking windows backup for hyper v virtual machine.
backup failed to complete. Backup of file from both csvfs and non csvfs formatted volume in the same backup not support.
any one can help.
↧
↧
I can't install Windows10 on Hyper-V via MDT
Hi,
I also asked this question to the MDT group.
I am currently trying to install Windows 10 via MDT on my Hyper-V Server. Unfortunatly, my installation stops during the " Install Operating System " step. MDT gave me these errors :
Could not mount offline registry
FAILURE ( 5624 ): 1450: Rune DISM: /Apply-Image /ImageFile:"\\Path\to\my\install.wim" /index:1 /ApplyDir:D:
Litetouch deployment failed, Return Code = -2147467259 0x80004005
Failed to save environment to (80070057)
Failed to run the action: Install Operating System.
Unknown error (Error: 000015F8; Source: Unknown)
The execution of the group (install) has failed and the execution has been aborted. An action failed.
Operation aborted (Error: 80004004; source: Windows)
Failed to run the last action: Install Operating system. Execution of task sequence failed.
Unknown error (Error: 000015F8; Source: Unknown)
Task Sequence ENgine Failed! Code: enExecutionFail
Task Sequence execution failed with error code 80004005
RegQueryValuExW is unsuccessful for software\Microsoft\SMS\Task Sequence,
SMSTSEndProgram
GetTsRegValue() is unsuccessful. 0x80070002
Error Task Sequence Manager failed to execute task sequence. Code 0x80004005
I have reseach this, but have found no solution. I hope you can help me? Maybe there is a security on Hyper-V or something like that.
Thanks
Laflèche Chevrette
↧
Change ChassisType for VM Guest
Hi,
I can't seem to find any info about doing this if it's even possible (I know you can change BIOSGUID, Serial, Tag, etc.). I'm looking for a way to change the ChassisType exposed to the VM Guest operating system. I'm building a new client reference image and rather than use physical hardware I'm doing it through Hyper-V (Server 2019).
The problem with this is on deployment of Windows 10, it's detecting the ChassisType as 3 (Desktop) and I need to build the image as a Laptop/Portable type.
In short, is there any way I can change the ChassisType of a VM guest to Laptop/Portable etc?
Thanks
↧
Hyper-V failed to enable replication relationship on the Replica server: Unspecified error (0x80004005).
Event IDs on B2
Event ID 16300 Cannot load a virtual machine configuration: Unspecified error (0x80004005). (Virtual machine ID A10F389C-C365-4829-A748-36EAA9009690)
Event ID 33686 Hyper-V failed to enable replication relationship on the Replica server: Unspecified error (0x80004005).
Event IDs on B1
Hyper-V failed to enable replication for virtual machine 'VMNAME: Unspecified error (0x80004005). (Virtual machine ID A10F389C-C365-4829-A748-36EAA9009690)
This only happens to some VMs, those that previously used Certificate based replication.
- Domain A VMs are replicated to Domain B via certificate based replication.
- Domain A servers are running Hyper-V Server 2012R2 or 2016.
- VM version is 5.
- VM is failed over to Domain B Hyper-V replica server B1 running WS2019 Datacenter host and started, no errors.
- VM is replicated to a different WS2019 Datacenter host B2 in Domain B and is failed over. It's still using certificate based replication.
- Replication is removed on all hosts.
- VM is deleted on but B2.
- VM is shutdown and upgraded to version 9. VM starts and works fine.
- VM is deleted from B1.
- Enable replication fails from B2 to B1 with errors above.
- I can create new VMs on B2 and replicate them with or without certificate based replication without error.
- I have searched and removed all files/folders with A10F389C-C365-4829-A748-36EAA9009690 in their name on B1.
- Where is B1 still storing information about A10F389C-C365-4829-A748-36EAA9009690?
-=Chris
↧
Hyper-v and SVM/Virtualization cant run at once in AMD Ryzen 3750
im never use AMD to run docker in my laptop, and now im using it and need run both of SVM/Virtualization and hyper-v at once.. but everytime im enable it i got stuck when about to enter on my OS (im using windows 10 pro)..
can you explain and help me? thanks
can you explain and help me? thanks
↧
↧
Hyper-V Server 2019 - RDP not working
Hi,
So I am testing with Hyper-V Server 2019, which I deployed to three brand new HP Proliant gen10 machines. I'll test on them for a while before putting them in production. Installation was a breeze, as with Hyper-V 2016. However, I can't seem to enable RDP on Hyper-V Server 2019. When I enable through the menu, it says it's done so, but alas, netstat -a reveals there isn't even a process listenening on port 3389.
I checked the registry, HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Terminal Server is correct. The required services are running. Firewall is completely disabled through netsh for testing. Remote administration is working fine, RDP is not listening at all.
Anyone else ran into this?
↧
Automatic virtual machine activation (AVMA) of Windows 2019 guest running on 2016 Datacenter host
The following documentation...
https://docs.microsoft.com/en-us/windows-server/get-started-19/vm-activation-19
...suggests that it should be possible to activate (via AVMA) a Windows Server 2019 Standard guest VM, running on a Windows 2016 Datacenter Hyper-V host.
I've run the slmgr /ipk <AVMA_key> command at an elevated command prompt with several of the keys in the document, however Windows on the guest VM refuses to activate.
The following is recorded in the Application event log on the VM...
License Activation (slui.exe) failed with the following error code:hr=0xC004FD03
Command-line arguments:
RuleId=a5b3220c-2d48-42e8-9733-0374090e4a25;Action=AutoActivate;AppId=55c92734-d682-4d71-983e-d6ec3f16059f;SkuId=e936f630-5125-4a39-b1de-544d6c036491;NotificationInterval=120;Trigger=UserLogon;SessionId=1
I want to confirm whether...
1. It IS possible to activate Windows 2019 guests on a Windows 2016 host.
2. And if so, what's wrong with the activation in this case.
Thanks!
↧
Hyper-V easy manager tool to manage VM
Hi community,
after your authorization,
i m very happy to present my contribution to you, it is a free tool created by myself, to help everyone use Hyper-V on local or remote server, and encourage the people to use Hyper-V.
all your feedback is welcome,
this is the link :
https://gallery.technet.microsoft.com/Hyper-Virtual-Easy-Manager-6384c1c6
if anyone has any suggestions or improvement, please feel free to give me the advice
↧