As stated a user migrated 3 VMs with the exact settings. He can connect to the console do finalize the migration BUT on the 3rd VM he cannot open the console and it kept prompting for a login.
Any tips?
Hello,
We have a two node Azure local cluster, a specific VM around 3.5 tb of size, was attempted to migrated from VMware to Azure local cluster through Azure Migrate, for some reason the sync from VMware to Azure local made the VM fill around 35-40 tb instead of 3.5 tb (Maybe because there is alot of files written and deleted on this VM all the time).
That filled up the cluster virtual disk, after we stopped and deleted the azure migrate process, it released the claimed space in the clustered virtual disk, but the Used space in the cluster pool is still showing 39,3 tb out of 48.9 tb total so a free space of 9,56.
Even though there is plenty of space in both our cluster virtual disks, infact around 20 tb., the free space of the cluster pool still shrinks everytime we deploy anything.
We really need to get that "wasted space" back, how to do it?
Does anyone have expirience to split a vhdx that's already replicated?
I know, it's not offered by design, but at least it's only editing xml?
Hello!
I'm going to purchase 3 physical servers (2x16 core processors) and combine them into 1 cluster. The choice fell on Hyper-V, because in any case, I plan to purchase OEM licenses for windows server standart 2022/2025 16-core.
Counting the number of licenses, I got confused. According to the information that I found, 1 license for 16 cores covers 2VM and + the possibility of using a hypervisor on a physical server.
Given my configuration, I planned to buy 6 standart licenses to cover all 96 cores. Then the difficulties began - what number of windows VMs will be available to me? Google AI reports that a 16-core license entitles you to 2 VMs, and if you license a 32-core server using 2 licenses, 4 VMs will become available. In the meantime, I entered the same data into Copilot, and it informed me that no matter how many licenses are activated on the physical server, eventually I will still have 2 VMs available.
I plan to run 7 Win VM on my cluster, and also leave the option to migrate servers in case of problems. But according to Copilot, in this scenario, I can only use 4 Windows VMs and have the fault tolerance of 1 server. According to Google search AI, 6 licenses entitle me to 12 VM Windows and my initial plan is fully covered.
Help me find the right answer, the budget is limited, and I have no right to make mistakes.
So I use a VM through HyperV for work and I have been running the same VM for about three years now. I have always had issues with slow startup and I have tried a number of tweaks with no or short-lived success.
I am at a stage now where I want to just start from the bones. The problem is that I have little to no idea what is going on with the bones or why I set it that way at some point in the past. Hoping for some input and guidance so it won't take 30 minutes to open outlook in the morning.
I am not sure what the 5.44 GB UDF drive is?
RAM has been set as high as 16gb, which is half of what I have. That made no difference so I set it back to four and let it take more if needed.
Processors have also been all over the place. I read some suggestions that having too many is counterproductive so I rolled it back to 1 and went up from there, but again did not see anything positive.
No clue what is going on with the boot drives beyond that the VM runs windows 11 pro and that's the .iso I used for it.
Hey,
I could start this with "I built a ..." just to trigger the AI-slop-sensitive part of the community :P - but I won't. I just wanted to show you something which I'm using for troubleshooting/debuging Hyper-V.
Coming from VMware enviros, I really missed the esxtop functionality on Hyper-V. If you don't know it, it's a TUI driven performance monitor for ESXi hosts. Fast, very specific, but gives you the most important metrics without any GUI or webservice or plugin requirements.
I can't find anything close enough for Hyper-V (or Windows, for that matter) - you'd need to juggle Hyper-V Manager, Performance Monitor, Task Manager, Resource Monitor and who knows what else to check what's killing a host's performance.
(I know, WAC will do it for you with a nice GUI, but that's exactly what I didn't want).
While I am quite handy with Powershell, and I have crafted my basic reporting PS scripts to get data similar to esxtop's, I soon realized PS isn't the right tool for this type of data/metric gathering, it's just too slow to give reasonably precise feedback about what's happening.
So. Enter Codex.
(Now you can boo me. Really. I get it. But if you don't want to use it, then just don't. Of course you can still drop the usual AI-slop comment if that makes you happier. I don't mind.)
So hvtop now is a C# utility, able to check the basics (CPU/RAM/DISK/NETWORK), and some more detailed info as well. It can drill down to VM or Storage or vSwitch level for more information, and it works with Failover Clusters.
you can check it out here (open source):
https://github.com/mazvazzeg/hvtop
Hey there.
I'm brand new to Hyper-V. In fact I didn't even install it yet, but I'm planning to do it. From what I read there doesn't seem to be any viable alternatives left on Windows without disabling Hyper-V and therefore harming the host systems security.
One issue I have with Hyper-V in comparison to VMware is 3d or video acceleration/performance.
But I found out that you can passthrough or partition your gpu so that Hyper-V can utilize it.
Is it possible to passthrough my Ryzen 7 9700x CPU's AMD iGPU? It's just idling around and I never used it before. That way I could use my whole main GPU for the LLM Backend that I run on the Windows 10 Pro host.
Thank you for reading and any suggestions or advices!
Last week I was doing upgrade testing on our Exchange Server. I imported copies of 2 domain controllers, the Exchange Server, a new exchange server, and a workstation onto a Hyper-V server and isolated them all on a private network. I have done this countless of times over the years / decades that I've been using Hyper-V.
I did the schema and domain preps on the new server and a full install of Exchange - all went with no issues. I then moved my mailbox over to the new server and had no problems. The CEO of this client has a 76 gig mailbox, so I moved that overnight and the next day it was fine. I believe it was Friday night and I decided to move over all of the mailboxes that didn't have online archive files, I kicked it off and went to bed.
Saturday morning I checked on it and everything had gone fine.
Keep in mind this was duplicate VM's all in a private Hyper-V network. The actual real environment was running with no issues in the real world. Several people accessed mail in the real world during all of this.
I didn't do anything else that day, Sunday I decided to run it through again, so I restored all of the Checkpoints on all of my test machines and started doing the install over again. I redid the schema and domain preps and kicked off the installation. It was mother's day, and I left to take my mom out, and while I was driving I got notified that people weren't getting any mail...
When I opened a computer, I logged into the live exchange server and everything looked ok, but when I logged into a workstation and tried to open Outlook, it wouldn't open. I tried to open Outlook Web Access and it told me that I needed to open my mailbox using the name of the server I was running in the test environment....
In short, somehow that I don't understand, what I did in the test had corrupted the real world. All of the mailboxes I moved were now showing as being on the new server, which to my knowledge had never been on the network. I had restored the checkpoints on all of those servers, so I couldn't even examine them to see what could have happened, and all of the mailboxes were gone.
I spent the rest of the long long night getting things back as best as I could, but now I am faced with the problem of wanting to test this upgrade again, and I'm afraid to do it now.
I have been trying to download the servers to my network here this week, but it's well over a terabyte, and it just hasn't finished yet. I really need to upgrade the Exchange server this weekend and I really want to run more testing, and I don't know if my downloads will complete.
So... Can anybody think of anyway this could have happened, and more importantly how to make sure it doesn't happen again. Like I said, I've been doing testing like this for years and years and I've never had anything like this happen. How could it be at all possible that the changes I made in the private network got through to the public network?
Anyone else run into this after a Windows update a few months back? My Hyper-V host CPU in Task Manager shows ~2% utilization no matter what my VMs are doing. A few months back it felt accurate — if a VM was under load, you'd see it on the host. Now it's completely disconnected.
To reproduce it, I wrote a Python script to max out every vCPU on a guest VM. htop inside the VM confirms all cores pinned at 100% (see screenshot — 12 threads running, load average 6.15). Meanwhile, the host Task Manager barely moves. The host is an Intel Xeon Gold 6526Y with 32 logical processors and 128GB RAM, so it's not a resource ceiling issue.
My theory is that a Windows update changed how Hyper-V reports guest CPU activity to the host's performance counters, or something shifted in the hypervisor scheduling layer. The VM is clearly doing real work — the host just stopped caring to report it.
Has anyone found a fix or rollback path? I'd rather not start bisecting months of cumulative updates blind.
Possibly dumb question but I've been testing out Hyper V since (like many people) we've been finding VMware alternatives.
I'm setting up Storage Spaces Direct just using this:
But I can't seem to get anything other than triple replication for storage -- is it possible to set this to double replication? We only have 3 physicals for the trial we're doing so that might mess with it but I can't really commit more physical servers to test that theory out.
Hey all
wondering what people do for storing their VMs
I havent used hyperv in about a decade - old company used to lump disks in one folder and the other files all lumped into another.
What are people doing these days?
