I am using Hyper V host for my prod environment.
1. How can I export clustered VMs check point detail?
2. How can I export hyper V stand alone VM check point detail
Arif
↧
How to pull check point report of Hyper V stand alone as well as clustered VMs
↧
Problem with add VMSwitch type External
Hello,
I have server Windows Server 2019 (core only), with five ethernet interfaces. The first interface is configured for HW management module, second for host OS comunication. In the Virtual Switch Manager select type "External", click on "Create Virtual Switch", in next step enter name "ExtSwitch", select "External network" and select physical ethernet interface 4. After click "Apply" or "OK" I see progress bar "Applying changes" and next message is "Error aplying Virtual Switch Properties changes".
Trying the same configuration in powershell will turn out the same.
Set-VMSwitch ExtSwitch -NetAdapterName"em4" -SwitchType External
Could anyone help me?
Michal
↧
↧
Virtualising file server role in stand-alone Hyper-V host with local storage
I've never installed/configured a Hyper-V host and VMs before, so pls bear with me:
I have a single Hyper-V host with Windows Server 2019 Datacenter as a host OS.
I’m planning on virtualising the following roles:
- AD / DNS (Windows Server 2019 Datacenter VM)
- Application server (Windows Server 2019 Datacenter VM)
- File server (Windows Server 2019 Datacenter VM)
- E-mail server (Ubuntu Server VM with iRedMail)
I have local storage (Hyper-V host) only, consisting of the following:
- 4 NVMe drives (Intel DC P4510 2.5″ 1TB) connected to an HBA (Supermicro AOC-SLG3-4E4T)
- 6 SAS HDD (4x 6TB, 2x 8TB) connected to an HBA (Broadcom SAS 9305-16i)
With those 10 drives, I would like to create a 2-way mirrored tiered storage (NVMe + HDD) and a 3-way mirrored storage (HDD), using Storage Spaces.
I’m puzzled on how to present that storage as shared storage with a virtualised file server on the Hyper-V host. The possibilities I see are:
- creating the Storage Spaces on the Hyper-V host, on which I would store large VHDX virtual disks which would then be attached to the file server VM and offered by this VM as shared storage to AD users. However, if I would put such a VHDX file on the 2-way mirrored tiered storage, the file would either be on the fast tier (NVMe) or on the slow tier (HDD). So when writing to the shared storage (the VHDX file), I would not have the advantage of writing first to the fast tier and then data (as they get ‘cold’) being moved to the slow tier.
- creating the Storage Spaces on the file server VM, passing through the physical disks to the VM. However, I read everywhere that this approach is not recommended and should be avoided.
Or a third possibility could be to not virtualise the file server role and to install that role on the Hyper-V host, even if it’s not best practice to install other roles than Hyper-V on the host?
Thanks in advance for any pointers in the right direction.
↧
HYPER V REPLICATION
hii guys i need your help for my both windows server one is 2012 r2 and one is windows server 2016 and i want to do hyper v replication and i need some guide even i saw some guide on the internet it does not works for me also is there anyone that i cant
talk to ? even i ask the windows support live chat they say they dont know how to solve it
↧
Hyper-V Server 2019 stopped remote management and RDP
I had installed Hyper-V Server 2019 and then setup some VMs.
The hypervisor is not part of a domain, I use my home network (Internet Provider network), while I have a DC configured on a VM, a pfSense VM and other VMs which are connected to an Internal switch. I used OpenVPN to remotely connect to the VMs using a remote tool called MRemoteNG, so no need to connect to them by using Hyper-V Manager.
Previously I was able to connect via RDP to the hypervisor when required and managed to remotely manage the VMs using Hyper-V Manager when creating new VMs.
I was able to do this yesterday but today I am unable to do it.
I disabled firewall on the hypervisor.
Remote Management is enabled on the hypervisor.
But it seems that I can't connect to it anymore.
I tried installing KB4482887 from this link:
But says that it's not applicable to my hypervisor.
I had this issue before and had to rebuild the hypervisor because I thought I messed up some SNMP settings. But this problem repeated and it seems it lasted like 2 months after the rebuild.
Can anyone suggest some possible fixes?
↧
↧
"The application encountered an error while attempting to change the state of xxx"
So I’m trying to do a simple Win 10 quick create on a client workstation but can’t get the VM to boot with default settings.
The workstation is running Win 10 Pro, SSD, 8GB of RAM. I’ve never had it not work before so I’m not sure what to check. I also tried an eval ISO of win 10 with the same error. Virtualization is enabled in the BIOS. Any ideas?
In the Hyper-V worker admin logs the only error I see is “Virtual Machine Worker Process initialization has timed out, and will terminate."
↧
Upgraded from Win2012 Standard to Win2019 Standard - Lost Hyper V Manager Configuration
Did a routine DVD upgrade on server A (from 2012 to 2019), appeared to work fine, all updates applied and while my guest VMs are running (as seen from an alternate server B running HyperV Manager...) this particular server A does not have any guest VMs or configuration "listed" in its own HyperV Manager.
Any suggestions as to how to "restore" the configuration so my guest VMs are seen in the manager?
Also, the replication configuration from server A to B for the guest VM (on A) is not working either; even after resume attempts as well as remove/re-setup (says it's "not in a state to accept replication on the Replica server for the virtual machine").
↧
Can I install Intel HAXM(Hardware Accelerated Execution Manager) in a laptop having a AMD Ryzon 5 3550H processor
I have tried numerous times to enable the Hyper-V from the 'Turn Windows features on or off' panel but I couldn't find the option of Hyper-V.
I think possibly this might be due to the reason as I am using a laptop having a AMD Ryzon 5 3550H processor.
Kindly guide me whether I can do the same or not
↧
Help! BitLocker encrypted VHD is damaged after updating windows10-1909
During the Windows 10 update process, because the local space memory is less than 10GB, the system prompts that an external storage device is needed, so I used a mobile hard disk. This disk is usually connected to my computer. A VHD partition is made separately
for storage Data, and this VHD is encrypted by BitLocker. However, after the update, the VHD file is still there, but the size becomes 0 and it cannot be loaded. The other files on the mobile hard drive have not changed at all.
At present, it has spent a lot of time to restore data (operation on the clone disk, no data is written to the original disk), and there is no result.
I want to ask why such a problem occurs? Is it that the 1909 version does not recognize the 1803 version of vhd? Even if the vhd is deleted or damaged, the data inside should be recoverable, but why can't it be recovered?
The pop-up window during the update, prompting: "Due to insufficient disk space, you cannot install the latest Windows 10 features and security improvements on your computer. Please follow the instructions below to complete the update. Select or connect at least 10.0GB of available External storage device. During the update installation process, use a USB key, SD card or external hard drive to temporarily expand the hard drive. Windows will not reformat your external storage device. "
↧
↧
OBJECT MISSING GENERIC FAIL
when i try and create a vdisk or a vmachine i crash when i try and finish getting an error message saying a may have deleted an object and another one just saying generic error. I cant even import and outside .Iso and use plus all the stock vmachines are
not in the hyper-v folders. how do i get back to normal?
↧
Exporting/Importing VM's Guest Cluster
Hi,
I am looking for some guidance on Exporting & Importing HyperV VM's those are part of cluster.
Scenario 1
- Standalone Win2012 R2 HyperV Host
- Windows 2012R2 VM Two Nodes configured in Failover Guest Cluster with shared VHD's fro Quorum, MSDTC & SQL
- SQL 2012 Cluster named instance
Scenario 2
- Win2012 R2 HyperV Host cluster with 5 nodes
- Windows 2012R2 VM Two Nodes configured in Failover Guest Cluster with shared VHD's fro Quorum, MSDTC & SQL
- SQL 2012 Cluster named instance
Is it possible to Export/Import VM Guest Cluster? what guidelines should be followed?
↧
BSOD reboots
Hi
I have a HyperV server that just rebooted, and took a lot of virtual machines down. This is the second time in the last couple of months. I have a minidump, but can't find the culprit.
This error is in event log:
The computer has rebooted from a bugcheck. The bugcheck was: 0x00020001 (0x0000000000000011, 0x0000000000263077, 0x0000000000001007, 0xffffe8000574ceb0). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 042720-49468-01.
Bluescreenview.exe gives me this, but I don't know how to analyze it...
↧
Bugcheck: 0x0000000a (Windows Server 2008 R2 Entreprise) - Is a VM running on Hyper-V
Event 41, Kernel Power occurred on two consecutive days around the same time causing the system to restart.
(The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly)
Another log was registered as follows:
Event 1001, BugCheck
The computer has rebooted from a bugcheck. The bugcheck was: 0x0000000a (0x0000000000000000, 0x0000000000000002, 0x0000000000000001, 0xfffff80001c597de)
Any idea why it happened?
↧
↧
VDI on Server 2019 4 node cluster
Hi, I'm hoping someone can help me with a really frustrating problem creating a VDI collection.
I have a 4 node Hyper-V cluster running Server 2019 DataCenter.
All VM servers are running ok as is RDS Remote Apps. The problem i have is specifically with VDI
I have installed the RD Virtualization host role on all 4 physical host servers and all show in the RDS section of server Manager as Virtualization hosts.
When I create a VDI collection it completes successfully if I use hosts 2, 3, and 4 in any combination, but if i include host 1 it fails with the error 'The collection was created successfully with the following warnings: Unable to retrieve the details of the virtual desktop collection'
In Server Manager then, under Collections I see the collection name with 'Not Valid' next to it.
The wizard has copied the template but not created any VDI machines.
Also, which may or may not be related. When I successfully create a collection by not including host 1 I can see the VDI machines in Hyper-V Manager, but not in Failover Cluster Manager.
This may be 2 separate issues but any help on either much appreciated.
Thanks
Kevin
↧
Checkpoins are not appearing while I had cancelled it after mistakenly i started merging it-Server 2012
I have two check point of a VM one was created in 2018 and other was in 2019. I had to delete only 2018 Check point but i selected delete tree which started deleting all my check points. But when only 2% was completed, I cancelled merging process. Simple, Right click on VM-->Cancel Merging. But I do not see my check points back.
Please suggest how can I see my check points back, this is really very critical. I see AVHDX files are in snapshot locatin
Arif
↧
I had cancelled Merging process of check point but when see in VM, no check points
I have two check point of a VM one was created in 2018 and other was in 2019. I had to delete only 2018 Check point but i selected delete tree which started deleting all my check points. But when only 2% was completed, I cancelled merging process. Simple, Right click on VM-->Cancel Merging. But I do not see my check points back.
Please suggest how can I see my check points back, this is really very critical. I see AVHDX files are in snapshot locatin
Arif
↧
Integration Services Mismatch - Checking Host version
I´ve installed a Win2012R2 Hyper-V Host and updated as better as possible
I´ve installed a Linux RH6.8 and downloaded and isntalled the latest IS, 4.3.5
Now, the Veeam Backup software is broken because of a "mismatch"
Guest processing skipped (check guest OS VSS state and hypervisor integration components version)Failed to create snapshot (Microsoft Software Shadow Copy provider 1.0) (mode: Crash consistent) Details: Guest processing skipped (check guest OS VSS state and hypervisor integration components version)Error: Guest processing skipped (check guest OS VSS state and hypervisor integration components version) |
It´s hard to make sure host and guest for all VMs are the same, over time, some minimal version differences will occur and worst, how to know the expected version? How ca I tell the IS HOST version?
Wh cant i konw the exact version for the IS components on HOST? The EV errors are abot 4, 3 or 5 version, but with no details on minor versions
Hyper-V Data Exchange connected to virtual machine 'LINUX3', but the version does not match the version expected by Hyper-V (Virtual machine ID 967C2534-9DE7-4643-BC31-19F37F590F4C). Framework version: Negotiated (3.0) - Expected (3.0); Message version: Negotiated (4.0) - Expected (5.0). This is an unsupported configuration. This means that technical support will not be provided until this problem is resolved. To fix this problem, upgrade the integration services. To upgrade, connect to the virtual machine and select Insert Integration Services Setup Disk from the Action menu.
another one, older error
Hyper-V Heartbeat failed to connect to virtual machine 'LINUX1' because the version does not match the version expected by Hyper-V (Virtual machine ID 04A14285-2BA0-41A8-97CE-EDF23A677BE9). Framework version: Negotiated (0.0) - Expected (3.0); Message version: Negotiated (0.0) - Expected (3.1). To fix this problem, you must upgrade the integration services. To upgrade, connect to the virtual machine and select Insert Integration Services Setup Disk from the Action menu.
Other errors:
Hyper-V Data Exchange connected to virtual machine 'VeeamFLR_LINUX3_f29594ac-cf4e-463f-8e97-7c907d4c8043', but the version does not match the version expected by Hyper-V (Virtual machine ID 91615285-00BB-414F-BB9D-4ABEA5F23978). Framework version: Negotiated (3.0) - Expected (3.0); Message version: Negotiated (4.0) - Expected (5.0). This is an unsupported configuration. This means that technical support will not be provided until this problem is resolved. To fix this problem, upgrade the integration services. To upgrade, connect to the virtual machine and select Insert Integration Services Setup Disk from the Action menu.
'SERVER1': The Virtual machine B8A8AF17-9106-4454-AF31-12843A2E00A6 cannot be hot backed up since it has dynamic disks in it
↧
↧
Windows Server 2019 Hyper-V Failover Cluster Intermittent VM Connectivity - VMQ disabled
Hello!
I have a new Windows Server 2019 Hyper-V Failover Cluster where some of the VM's have periodic connectivity loss. I can ping them fine from the Hyper-V host server where they are running, but get intermittent pings from other hosts on the network.
I have a pair of HPE 10/25Gbe 631SFP28 NIC's teamed (Switch Independent) with the Hyper-V Virtual Switch built on that Team. I believe that I have the latest Windows Drivers (Broadcom 10/23/2018 214.0.177.0). I installed the latest HPE firmware for these Adapters.
VMQ is disabled on the Teamed Adapter and two 10/25GB NIC Adapters on both hosts.
The hosts are up-to-date with Windows Updates.
Yet I can get 50% packet loss with a simple ping to these VM's. From some hosts, I can't get any pings to work at all. Yet the correct MAC address shows up in "arp -a".
There is no routing and no VLAN's between the Hyper-V Hosts, VM's, and PC's.
Some VM's appear to have rock solid connectivity, while other (it seems like newly created VM's?) have the connectivity loss. I can live migrate the VM's between hosts and still have ping loss. I admit that the "newly created VM's" idea seems strange, but that's what it seems like. The VM's are using the Hyper-V Synthetic NIC and running patched Windows Server 2019.
Any ideas on what I can try? I would certainly appreciate any help that anyone can offer!
Dave
↧
Memory allocated for packets in a vRss queue (on CPU 0) on switch 6E77ECEF-A708-429D-9445-44A21279DFF6 (Friendly Name: Wan Switch) due to low resource on the physical NIC has increased to 512MB. Packets will be dropped once queue size reaches 512MB.
Hello
I run a Host Hyper-V 2019 with 32 cores and I get this error:
Memory allocated for packets in a vRss queue (on CPU 0) on switch 6E77ECEF-A708-429D-9445-44A21279DFF6 (Friendly Name: Wan Switch) due to low resource on the physical NIC has increased to 512MB. Packets will be dropped once queue size reaches 512MB.
This happens when we have lot of traffic because inside Hyper-V there are many Virtual Machines and this is supposed to happen more when traffic is high in packets - we run 1 Gbps netwrok card and use around 300Mbps when this happens.
VMQ and RSS was enabled in physical card but not VMQ not enabled in VM hardware acceleration option in network card.
When it happens we have timeouts completely which disconnects everything from outside to server - connection is lost completely.
Any idea about it and how to fix ?
THank you
↧
Black spots on remote sessions (mostly on Office/Outlook 2016)
I'm connecting from a terminal client, with Windows 10, to a Server 2016 Hyper-V machine. All works well but from time to time I get black spots in the remote
desktop session.
I found this article https://serverfault.com/questions/641255/mstsc-black-areas-on-remote-desktop,
but that doesn't solve my problem. There are more users connecting to this server and not all are experiencing this problem.
The strange thing is that it mostly happens in Microsoft Office 2016 applications, like for example Microsoft Outlook. See the screen below.
https://i.stack.imgur.com/ZH1Lh.jpg
By using the GPO, I already enabled the “Disable hardware graphics acceleration” option (article https://support.microsoft.com/en-us/help/2768648/display-issues-in-office-client-applications) and, for the specific users, I’ve recreated the Windows and Outlook account, but this also didn’t help fix the issue. Other steps taken:
- Disabled the Enhanced Session Mode under the Hyper-V settings
- Removed the Terminal Server cache
- Enabled the option “disable hardware acceleration” under Outlook
The above steps didn’t solve the issue as well. I’m using a host server with Server 2016 with the following specs:
HPE ML350 Gen9
Intel Xeon CPU-E5-2620 V4 2.1GHz
128GB RAM
2x 300GB in RAID 1
5x 900GB in RAID 5
On the host server Hyper-V is installed, with the following virtual servers:
- Fileserver (domain controller)
- Mail server
- Terminal server
All virtual servers contain Server 2016 and the Terminal server uses Office 2016 Standard.
Is this a known issue and is there any way to solve it? The only way to get rid of the black spots is to close the program, and start it again.
↧