Hello,

We've a very stange problem. 
The C:\ Partition has 49GB Free space left, but we can't create a folder on it.

Error message:
There is not enough space on Local Disk (C:)
0 bytes needed to perform this operation. Delete or move files so you have enough space.

Local Disk C:\
Space Free:49.1 GB
Total size: 199 GB.

We've tryed:
Safe mode: Same problem
Sfc /scannow: Windows Resource Protection could not start the repair service
DISM /Online /Cleanup-Image /CheckHealth: ERROR 3. could not create directory.
Shadow Copy is disabled.

Yesterday we've restored backup in a new Hyper-V and everything was running fine until this morning, same problem again.

We're using a Windows server 2016 Host and multiple Windows server 2016 guest. Only 1 is affected with this issue. 

Edit: At recovery mode, we are able to create folders on C:\ with the command prompt. 

I am using Remote Desktop Client: 6.3.9000

The environment has three virtual servers running in Hyper-V.  One domain controller that is running DHCP, and DNS as well.  One terminal server that users connect to so I assume this is the host/connection broker.  Both of those servers are 2008 R2.  There is also a Server 2012 R2 that is an application server.

The Intermittent loss of connectiovity involves connecting to the terminal server. Both with RDP and through Hyper V manager console.

Can someone help?

I have a Win10 machine, enabled Hyper-V and built a VM.  Used external switch to get networking to the VM, but now my SMB shares on the Host cannot be reached from other computers on my LAN.  Any ideas?

I can get to my own shares, using the "internal" IP address on "this side" of the switch.

I am guessing this would also be the case if my VM happens to add shares.

If this has been posted please redirect me.

I have two identical Dell Poweredge Server with Hyper-v Server 2016 as the OS. I would like to configure High Availability, and not have a GUI is a bit of a challenge.

I am curious to know if anyone could point me to resource to help me accomplish this task.

Greetings all. I have a customer with a two node Server 2016 Hyper-V cluster. System was installed in Dec 2017 and ran fine for probably 7 to 8 months when we began experiencing issues. Hosts are identical Dell R830s each with two dual port QLogic 57810 10Gb adapters. The adapters are using DAC cables to connect to the respective ports of an EMC Unity 300 SAN. Each adapter has one copper cable going to one port of a storage processor on the SAN as depicted in the attached JPG.

The hosts were recently updated with the latest firmware, drivers, and OS updates for server 2016 in an attempt to rectify the intermittent iSCSI timeouts we're experiencing.

Users began noticing that VMs will sometimes "freeze" or become un responsive for a minute or two and then resume. We occasionally get application level errors about I/O that completed but "took an abnormally long time".

The Windows system event log will often record iSCSIprt errors event ID 9 that the "Target did not respond in time for a SCSI request".

We get these on both hosts and to two different LUNs on the Unity. Typically the events occur in bursts all with the same timestamp and sometimes a few events are recorded and sometimes dozens.

Since everything has now been updated to the latest available firmware and drivers we're not sure where to go from here. MPIO is installed on the hosts but the targets were not configured for MPIO because there is no switch in the mix. These hosts are direct connected to storage.

If anyone has seen behavior like this or has a suggestion for additional troubleshooting I'd welcome your comments.

Thanks.

Good evening,

I have a dedicated server with 2 IP addresses assigned on one NIC. Server is hosting a Hyper-V Role with few VMs installed. I would like to know how can I configure a Hyper-V Switch (or roles on the main server, if needed) to access a VM from the Internet using one of the assigned IP addresses (the second one would be for RDP connections to the main server).

I have a VM that has a 1.5TB empty disk volume that I want to remove and have the space go back to the physical host.

I think the correct steps would be to first use Disk Management in the VM to Delete Volume and then Hyper-V Manager to remove it from the VM itself.  

Can anyone confirm these steps?

Thanks!

It shows that a user has previously logged out of a RDS session, and then tries to log back in, however the UPD for that user was “in use” so the user receives a temporary profile instead. Im using 2016 windows server

Also please don’t forget that at the same time we started experiencing these errors, we started having performance issues for the users as well.

When a user first connects, there is a delay (sometimes up to 3-7min) to get a desktop. Then the user will usually open Outlook to check their emails. There is a large delay doing this as well.

It seems like for about 15 min or so after a user logs in, the system/session is EXTREMELY slow. Then after the first 15 min or so, it picks up and runs like normal (speeds).

I have responsibility for multiple large-ish Hyper-V failover clusters. I very occasionally see an issue where the 'ISALIVE:0' check will fail for a virtual machine (via the vmclusres.dll library) and the Resource Hosting Subsystem will terminate, bringing down multiple machines with it.

There are multiple pieces of contradictory information on the internet about what is actually happening here. Some sources suggest that fail-over clustering will attempt to isolate the resource which first failed the health check into its own process (suggesting this protects the other resources running under the same RHS).

This categorically does not happen on a fully patched Windows 2016 Hyper-V cluster. What appears to happen is that the failing RHS is terminated, killing any and all compute that is running under the same process. The logs make mention of the offending virtual machine resource being isolated, but I can actually see no evidence of this occurring (in the properties of that resource), but even if this does happen, the default config has still resulted in one resource effectively causing an outage.

I can sort of add credence to this summary of behavior but forcing the resource to run in their own separate monitors myself. If I do this on a lab I've stood up:

Get-ClusterResource -Name "*Virtual Machine blah*"

foreach ($resource in $cluster_resources) {$resource.SeparateMonitor}

... I can see they are all using the default setting, which is to not run in a separate monitor. Fine.

If i set them all to run in their own monitor:

foreach ($resource in $cluster_resources) {$resource.SeparateMonitor = 1}

...and count the RHS processes there is no difference. As you would kinda expect, if I now restart the machines I suddenly have lots of RHS processes popping up, one for each VM.

So this suggests that resource cannot magically flip between RHS parent processes while they are running\switched on, so the out-of-the-box configuration can indeed bring down a whole node when there is a problem with a single resource. Could anybody anywhere tell me if I am right here?

Also, trying to go back to the why behind the original problem. Does anyone know where I can get information about what the ISALIVE check for the vmclusres.dll library is actually doing? There is no information anywhere about what kind of check failed, if it is a VM state check, some kind of IC communication check etc The VM didn't dump inside the guest, it just 'failed' and caused an outage, which is kinda scary. I know from some research that the ISALIVE check is the five-minute check which is supposed to be the more in-depth check of the two that are run, but I can find no documentation saying what it is actually checking, therefore I have no way of working backward.

Thank you.

Hi,

We have a windows 2016 server running hyper v that crashes when moving data around from the host with users logged into one of the hyper-vs (its the only common factor we can think that might be causing it). It currently runs 2 hyper-vs, one is a print server and the other is a terminal server.

The server is a hp ProLiant DL360 Gen9 bios version P89

Looking at the dmp files via bluescreenview I can see hal.dll and ntoskrnl.exe are popping up as the cause of the issue - happy to provide these files on request. ( http://www.filedropper.com/013119-16687-01_1<---  link for one of the small dmp files)

Any assistance would be appreciated.

Oliver

I have 3 DCs, 2 sites.  Main site 1 DC standalone hardware, 1 DC Hyper V guest, remote site 1 DC Hyper V guest.  Hyper V guest DC at main site will not process GP with error 1096 and only error 1001 in the application log. 

DC has all functionality except that it cannot browse it's own shares or any other network shares.  All other computers in the forest can browse the shares on this DC fine, the DC itself just cannot access the SYSVOL share to process GP.  It can surf the internet and ping the world.  It's not DNS.

The DC was working for years without issue.  All of a sudden just lost internet connectivity.  I removed and readded both the NIC and the virtual bus and that resolved the internet issue, but the DC still will not process GP.  I can go to the DC's C: drive and browse to see that the SYSVOL structure is there and intact.

I've checked registry entries and everything else I can think of.  I am reading posts that people have unjoined/rejoined, reinstalled, etc., and the issue persists.  All other Hyper V guests on two hosts across two sites work without issue.  I have no idea why this DC's NIC just stopped being able to browse.  This is not a new environment, nothing new was introduced to cause the problem.

Any assistance would be appreciated.  DCs are Windows 2008 R2.  

I have been searching blog after blog and trying everything I have seen but I cannot seem to get Cluster Aware Updating past the below error. 

Rule ID 3, "Windows Powershell remoting should be enabled on each failover cluster node". Through my testing it seems to be something to do with kerberos. I am fairly new to Hyper-V and PowerShell, so a lot of this is shooting in the dark with what I am testing.

When I run: Test-CauSetup -ClusterName clustername

When I try connecting with WBEMTestit connects fine with the host name and FQDN.

Enter-PSSession -Computername HV1   fails

Enter-PSSession -Computername HV.domain   (FQDN) connects

I can use computer manager and server manager remotely without any issues. I have gone through each machine and ran Enable-Psremoting -force. I have also tried putting in the remove server in the trusted host list via IP, host name and * even though they are on the same domain. 

Is there a way to have the CAU use the FQDN or am I missing something else? 

I really appreciate any help you can provide. 

Thank you,

Steve

I have a Hyper-V VM setup on my desktop system. This VM is running a Shared PC setup and it is configured to not allow remote connections. I thought this wouldn't be an issue since I am trying to access it directly via the host machine, not through any sort of RDP client, however whenever I try to login it always says that Remote Desktop connections are not permitted.

Does this mean that even when connecting to a VM hosted on the same machine, that the connection is still technically running through some type of RDP?

I have two virtual machines A, and B in my hyper-v management panel. B is cloned from A. And let says A has internal ip: 172.31.104.26 and B has Ip address 172.31.104.27. They both binding some web application on their 80 port.

1. If I request "localhost/mypage" on A will showing a page contains "I am Page A", and I request "localhost/mypage" on B will showing "I am Page B" 
2. If I request "172.31.104.26/mypage" from host machine will showing "I am Page A" and request "172.31.104.27/mypage" will showing "I am Page B"
3. However, If I request "172.31.104.27/mypage" from Machine A I will be redirected to "localhost/mypage" and showing "I am page A". Here, I am expected the page will show "I am page B"

Some one know how to properly configure that and the machine A can request to machine B?

Thanks

I've looked a couple of posts, but I can't seem to find the issue to my satisfaction.  I've already wasted a week on this and I don't feel like wasting one more second.  Hopefully, someone here can help.

The environment:

Host machine: Windows 10 v1809 64 bit, AMD Ryzen 3, 2200G (3.5GHz) 16.0GB RAM (14.9 usable)

Guest Machine 1: (This machine is fine) CentOS v7 64-bit.  Assign 127GB VHD dynamic, a second 64GB VHD dynamic, and an optical drive, 4GB RAM

Guest Machine 2: (The Problem Child!) Windows 10 v170? (v1803 won't install), Assigned 127 GB VHD dynamic, an optical drive, 4GB RAM.  I have manually installed the runtime version of .Net Framework 4.7.2, which is required for the software I'm working on.

The problem: I install the initial software, change all text files I need to change, and generally get the system into a condition that I want to be the "starting point" setup.  Over the course of this process, I make about 4 to 6 snapshots and restart 2 or 3 times without an issue.  After I'm in my starting point state, regardless of what i do, the next time I make even the most insignificant change and choose "Shutdown" or "Restart", be it from the Hyper V guest menu, or from inside the operating system's screen, this guest WILL NOT restart!  The system shows as running in the Hyper V manager, and even shows the login screen in the miniature screen capture.  Attempting to run the interactive client, which is absolutely necessary, starts an infinite process.

Initially, I see the Hyper V screen, with the Windows 10 "chase dots" at the bottom of the screen.  The screen then changes to the "Connecting to {guest name}" screen, waits about 30 seconds, then switches to what should be the login screen for Windows 10...but it never appears.  The screen resizes to the correct size, but the screen never appears.  After about 45 seconds of a black screen, the interactive screen for the VM returns to the "Connecting to {guest name}" screen, where the process start again.  It goes through this four or five times, burning about 6 minutes, then, on the last "Connecting to {guest name}" screen, a pop-up dialog appears reading that something couldn't be started, with the options to "retry" or "cancel".

Choosing "Retry" starts another 6 minute cycle of screen switching, resulting in the same dialog box popping up.  Choosing "Cancel" dismisses the interactive screen, even though Hyper V Manager still shows the guest is running and shows the login screen as the active screen.

I've tried most of the suggestions on a similar issue posted about two weeks ago, (the system won't let me post the link).  I do not have the ability to repartition my main hard drive.  I've also uninstalled and reinstalled Hyper V twice.  I found it interesting that, both times when Hyper V installation was complete, it was able to find the previous VMs, even though those weren't installed in the standard directory; I placed the VMs and their respective VHDs on a separate drive, because I didn't want to hunt around in "C:\Program Files" to find them.  I just thought it was odd that, after uninstalling and reinstalling, the system could find my previous setup, checkpoints and hard drives.  Maybe that's part of it, maybe not.

Additionally, I've tried recreating the guest with the image, and also recreating the hard drives, and both of those things together: all have the same result: On the fifth or sixth snapshot, even the most insignificant change, the one that has me frustrated enough to finally post is I changed one, four letter word in a text file to a five letter word, causes the infinite boot process I described above.  I may not even be a boot problem, but a graphics problem, since Hyper V manager is showing the system is booted to the login screen, and that the system is running.  It's just trying to run the interactive session that's an issue.

Other colleagues on my team have this entire system running fine.  No one here has any clue about my problem, let alone how to solve it.  I keep getting "that's really weird" as a response from pretty much everyone here.  I've followed the exact steps they've told me, and I seem to be the only person with this issue.

I'm hoping I'm not really alone in the world.  Because that's a really scary place to be.

Any and all reasonable responses will be considered.  I'm going to reinstall Hyper-V now.  I tried VirtualBox, but that system...their support forums leaves MUCH to be desired.

***EDIT***

The pop-up diaglog reads: "The session was disconnected.  If you want to continue, try to connect again.  If the problem persists, contact your system administrator.  Would you like to try to reconnect? Reconnect/Exit"

Hi All,

I have a strange issue, 2 vms which are configured with 16 CPU's are displaying the below from System Information within the guest OS, has anyone seen this behavior before and is there a fix?

Thanks for your help