Quantcast
Channel: Hyper-V forum
Viewing all 19461 articles
Browse latest View live
↧

Event ID 12240 - Cannot open VM attachment - Veeam Backup

November 27, 2019, 3:43 pm
$
0
0

Hi all, I apologies for the lengthy post, and any irrelevant information. I'm trying to provide as much information as I can.

I have been asked to log this ticket by Veeam, as they determine it is a Microsoft issue.

We use Veeam Backup and Replication to backup all of our Hyper-V guests.

We also use VeeamONE to report on issues.

Our environment is:

 - a standalone physical server running our Veeam software

 - two clustered servers with Fibre Channel storage (Cluster Shared Volumes) hosting our VMs (approx. 20 guests VMs)

For the most part, this all runs fine. Occasionally, however, VeeamONE reports the following error:

Description
Fired by event: 12240 Microsoft-Windows-Hyper-V-VMMS
Event description: '': Attachment 'C:\ClusterStorage\ServerName\Virtual Hard Disks\diskname_E40FF910-B414-4DFA-BDC3-BE02ACDCF27A.avhdx' not found. Error: 'The system cannot find the file specified.' (0x80070002). (Virtual machine ID )
Initiated by: DOMAIN\BackupAdmin
Knowledge
Cannot open VM attachment

It happens to random servers, on random dates, so no pattern to the issue.

The AVHDX files that is "not found" is the snapshot file created by Veeam during the Backup process.

Veeam uses an API to take the snapshot, then another one to remove it when the backup is complete.

So, in effect, the error is correct, as the file no longer exists, but why is it being logged, if the API is removing the snapshot correctly, should Windows be able to detect this and not log the error?

My main concern is that this then logs an error with VeeamONE, and makes our reports and KPIs look bad, with all these false reports.

I know that the easy solution is to turn off that Alert, but I would like to catch legitimate issues, not the false positives.

If relevant:

 - All servers fully patched and restarted

 - Integration services are up to date on most servers (issue happens regardless of version)

Again, I apologies for lengthy post. In summary, my question is: Why does Windows/Hyper-V log that error for a temporary Snapshot disk? Is it a bug in the API call? Is Veeam initiating the API call incorrectly?

↧
Search

Hyper-V failover fails for some virtual machines on replica server

January 8, 2020, 7:37 am
$
0
0

I have a simple setup for Hyper-V replication. Primary server is "Server1" and replication server is "Server2". Four VMs are replication to Server 2, the replication is successful, the machine are replicating and changes are updates in the replica server.

My issue is that two of these VMs fails when executing a failover or test failover with the error:"Hyper-V failed to enable test failover for 'VM1'. The system cannot find the file specified. (0x80070002). (Virtual Machine ID....)" "Replication operation for virtual machine'VM1' failed: The system cannot find the file specified. (0x80070002)....."

The two VMs replicas that fail were created the same way as the other two that work without problems. One thing i noticed is that when the replica is created for "VM1" there is always an error event related to Hyper-V-VMM:"Failed to load Hyper-V state for virtual machine 'VM1' from the configuration: The device is not ready. (0x80070015).(Virtual machine ID ....). Hyper-V may not work properly. An attempt to reload the configuration will be made in a few minutes."

Have anyone faced this issue before?



↧
↧

Virtual Domain Controller Problems

January 8, 2020, 8:53 am
$
0
0

I have installed and configured Active Directory and DNS on a virtual machine running Windows Server 2019.

The vNIC is configured as "External", with "Allow management operating systems to share this network adapter" unticked.

I am having a problem in that I have "No Internet" displaying in the bottom right of the taskbar. 



It's not really stopping anything from a functionality standpoint as the DNS server can still resolve external domain names like Google and Microsoft; I can browse the web too (checked to test).

There is obviously a reason why it's displaying, and I would appreciate some help resolving the issue.

Thanks in advance 

Couple of shots of my settings:





↧

Windows Server 2019 DDA

January 8, 2020, 12:02 pm
$
0
0
So, I'm trying to pass-through my RX 590 onto a windows 10 guest. I followed the Microsoft DDA document and managed to dismount my gpu and assign it to the VM but when I try starting it, it gives me the following error: The operation failed because the object was not found. After digging through the logs, I found a more detailed error message saying: Could not allocate the PCI Express device with the Plug and Play Device Instance path 'PCIP\VEN_1002&DEV_67DF&SUBSYS_C4111462&REV_E1\4&288640B9&0&001A' because it is already in use by another VM.

The thing is, I definitely don't have another virtual machine. I did enable IOMMU, ACS and SR-IOV beforehand.

Here are my specs:
MB: X570 Taichi
CPU: Ryzen 3900X
GPU1: RX 5700 XT
GPU2: RX 590
↧

Updating VM Configuration Version on Virtual Failover Clusters

January 9, 2020, 5:06 am
$
0
0

Hi all,

I've just completed a rolling cluster upgrade from 2012 R2 to 2016 on one of my Hyper-V clusters and am going through the process of upgrading the Configuration Version of the VMs from version 5.0 to version 8.0.

This is fine for the majority of the VMs (I have a nice PowerShell script for this that is scheduled to run out of office hours), but I have two virtualised failover clusters that have shared virtual hard disks and want to know the best approach for upgrading the Configuration Version on these systems.  I was thinking I'd just pause one node and shut it down, update the VM configuration and power back on.  Then I'll resume the node and fail the roles back. Repeat for the second node.

Needless to say, the business can be quite twitchy about these systems (they run SQL), so I'm proceeding with caution on this one. Anyone have any views on whether my method will work OK or if there is a better approach to take?

Ultimately, I could leave them at version 5.0 - we back them up as though they were physical systems and we can't take checkpoints because of the shared vhdx's anyway - so the only benefits I'll get are no longer having to perform Integration Component updates and a binary configuration file. 


↧
↧

Failover Hyper-V without Shared Storage

September 12, 2019, 1:46 pm
$
0
0

Hi Guys

            I have two brand new servers with 6 drives. 2 in Mirror, 3 Raid 5 with 1 hot spare. Both servers are identical and running Windows 2019 Datacenter. Both servers are running Hyper-V. I do not have any NAS/SAN devices being shared between these servers. I will call these servers server1 and server2 (for this example)

Is there a way to make it so that if a virtual machine on server1 dies and shuts off the replicated virtual machine on server2 will boot up automatically? The whole purpose of these servers is for virtual machine failover, I would like to do it per VM versus entire physical server. I can also format the Hyper-V partition since these servers are new and not running anything just yet.

Is Storage Spaces Direct (S2D) the answer I'm looking for? If so, how? Looks like Clustering needs as a requirement shared disks (SAN/NAS).

What do you guys think?

Thank You

Eddie

 

↧

Microsoft Virtual System Migration Service Missing

November 22, 2017, 5:10 am
$
0
0

Hi!

We're running two Windows Server 2012 R2 servers with Clustering and Hyper-V installed. We've been running a test-setup for a few weeks now and it's been working perfectly. Last week we tried to configure Kerberos authentication for live migrations. Here we ran into issues when configuring constrained delegations. It appears that the "Microsoft Virtual System Migration Service" is missing from services. We've tried to configure the spns manually but the commands wont go through and from what we can tell it's because the services isn't actually present on the servers. 

Running the following commands doesn't work, but if we change the service names to services we can see in services.msc it goes through and the services are visible on our domain controller when we configure delegations on the computer objects.

setspn -S "Microsoft Virtual System Migration Service/Servername" Servername

setspn -S "Microsoft Virtual System Migration Service/Servername.fqn" Servername

Anyone got any idea what can be wrong? We've tried reinstalling Hyper-V but that doesn't resolve the issue.

Best Regards.

↧

Hyper-V drops connection to VM on NAS.

January 9, 2020, 7:17 am
$
0
0

Hi.

We recently purchased a QNAP TS-883XU-RP to use as our mass storage for our company storing the vhdx files for 2 files servers with my HP DL385 Gen8 as the host server. During testing I was able to connect to the NAS using iSCSI and copy 4TB+ of data with no issues. Now it is on site and with iSCSI connecting it to the HP server (Server 2012 R2) and it remains stable until I start to move data. Using robocopy, I am attempting to move our archive data, ~4TB, to the new VM but after a short period of time, the connection drops.

Our HP server has 4 onboard NICs, all are teamed, the team is configured as switch independent and dynamic load balancing. The NAS also has 4 onboard NICs and they to are teamed for 802.3ad dynamic and the switch has also been configured as per this KB article.

This is what originally happened.

  • Connected NAS to server using iSCSI and created the VMs.
  • 2 new VMs, one will be archive data and the other will be live data. Both have 2 drives, OS and data storage and all are on the QNAP NAS.
  • Joined the VM to the domain and fully updated the Servers (both Server 2019). During this period, no issues at all.
  • Started the transfer of data from old servers to new VMs using robocopy - both at the same time.
  • After about 10GB of transfer, the host server lost connection to the VM and I am unable to RDP to the host VM but I can RDP to the domain controller that is kept on the same host server and from the DC, I can RDP to the host server.
  • The host server loses connectivity to the NAS but I can ping and access the NAS web front end with no issues and the performance is fine.
  • iSCSI initiator shows the NAS is disconnected and from the host server I am unable to ping the NAS or any device outside of the Hyper-V vSwitch.
  • A host server restart brings everything back to normal.

I then found a site that recommended changing the iSCSI settings to use Microsoft iSCSI Initiator and not the default setting and this removed a 113 warning I had in the Server logs and I enabled jumbo frames. I then tested transferring data on just one server and again I got a disconnect from the VM but this time, I remained connected to the host server but one of my DCs became unavailable and I was able to ping the gateway and internet servers (8.8.8.8).

I believe this is an issue/mis-configuration on the vSwitch or the server NICs but I can find any information related to it.

Look forward to your insight and support!

J.

↧
Search

Get-MPIOSettings

January 9, 2020, 9:40 am
$
0
0

Hello everyone,

So, I just wonder - which MPIO Settings do you prefer for your Hyper-V 2016/2019 Clustering, running with Fibrechannel and MPIO?

Default values should be : 

Get-MPIOSetting

PathVerificationState     : Disabled
PathVerificationPeriod    : 30
PDORemovePeriod           : 20
RetryCount                : 3
RetryInterval             : 1
UseCustomPathRecoveryTime : Disabled
CustomPathRecoveryTime    : 40
DiskTimeoutValue          : 60

↧
↧

Hyper-V server tries to act as gateway for whole network

January 9, 2020, 9:50 am
$
0
0

Hello,

I have installed Hyper-V onto a Windows 10 Pro installation. I can setup up VM's without any issue; however, other computers on the network keep getting the Windows 10 computer's IP as their default gateway that then prevent them from accessing the internet.

It doesn't happen to all computers all the time but when they refresh their ip address. I am assuming that there is a DHCP setup automatically but I am not sure where or how since I don't set one up.

If someone could point me in the right direction that would be great! Thank you in advance.

↧

Raid on hyper-v guest running windows server 2016

January 9, 2020, 9:50 am
$
0
0

Hi I want to buy a PC-desktop with the following:

core i7 9700, 32GB Ram , 1SSD 500GB,4 HDD 1TB, which support raid 0,1,10,5, intel rapid storage technology,windows 10 prof EN 64bit

I want to install windows server 2016 as a guest and that will be my production server, and a testing Ubuntu desktop 18.04 LTS.

I want to configure the raid for the VM guest with windows server only ...

1) How can I configure RAID to four HDD (4x1TB) disks?

2) Do I need a software raid or it is enough with the raid controller?

3) What levels of RAID should I use for the guest VM?

4)If I want to Raid my SSD in an 6th disk what level should I use?

5)In the above questions except for technical information please consider and performance...

Thanks in advance!!! 


↧

Server 2016 - Unable to apply checkpoints

September 11, 2017, 6:38 am
$
0
0

We have a Server 2016 Hyper-V cluster (fully patched) with which we are experiencing issues applying checkpoints. If we manually create a production or standard checkpoint in Hyper-V manager on 2012R2/Server 2016 VMs we are unable to revert back to it. The error message we get is "An error occured while attempting to apply the checkpoint". 

To simplify troubleshooting we have moved a Server 2016 VM out of the cluster and onto local storage, but with the same results. There doesn't appear to be much else to go on in the event viewer. Can anyone suggest a resolution please?


↧

VHDS sets

January 9, 2020, 12:09 pm
$
0
0
If I have a Guest cluster can I migrate (not live migrate) a VHDS set disk to another volume on the guest cluster? In 2012 R2 you have to remove the disk from the hosts reconnect as a non-shared disk  move it then reconnect as a shared disk but in 2016 I don't see the ability to make it a vhdx it is only available as a vhds.  
↧
↧

Live migration error: Mirror operation failed. General access denied error. 0x80070005

January 2, 2020, 9:24 am
$
0
0

I keep getting an error when performing a live migration from one host to another. There were 5 VMs on the source host. I moved 4 of them to the destination host without issue. For some reason, the last one keeps failing. It will perform the migration, and once it gets to 100%, it errors out and fails. After the failure, the VM reboots on the source host and comes back up normally (hard reset). There is no VM on the destination host, but there is a vhdx file in the proper location that is the same size as the source vhdx file.

The only difference that I can tell between the machines is that the one that is failing is 650GB (takes around 8 hours to migrate). The next highest is 350GB (no issues).

Both hosts on the same domain. Both hosts are running Hyper-V Server 2012 R2 (not Windows Server).

Both hosts are configured with the default options and locations (mostly).

Both hosts using local storage (no NAS/SAN/shared storage).

File permissions of source vhdx look identical to all other vhdx files on my other hosts.

I have 15 other hosts set up similarly on the same domain/network. I've done hundreds of live migrations between them, and never had an issue (up until this one).

Things I've tried:

1) Migrating to a different destination host. Same issue.

2) Shutting down the VM. Deleting the VM. Creating a new VM. Attaching the same vhdx file. Same issue.

3) Migrating a different VM from the destination host to the source host, then back again. Works just fine... The issue seems to be only with this VM and/or vhdx file.

Full error:
There was an error during move operation.

Virtual machine migration operation failed at migration source.

Mirror operation failed.

Virtual machine migration operation for 'VM-NAME' failed at migration source 'SOURCE-HOST'.

Migration did not succeed. Mirror operation failed for the source VHD file 'C:\users\public\Documents\hyper-v\Virtual hard disks\VM-NAME.VHDX' to the destination file '\\DESTINATION-HOST\SOURCE-HOST.1856233294$\C\users\public\Do...\Virtual hard disks\VM-NAME.VHDX': 'General access denied error' ('0x80070005').

Thoughts on possible issues:

1) Is it possible that the permissions/kerberos tickets expire due to the long migration time?

2) Is there an issue with this path: \\DESTINATION-HOST\SOURCE-HOST.1856233294$\C\users\public\Do...\Virtual hard disks\VM-NAME.VHDX' ?   The destination path should be \\DESTINATION-HOST\c$\users\public\documents\hyper-v\virtual hard disks\VM-NAME.VHDX . I am not sure if this is some temporary share created by hyper-v, or if this is where the error is occurring. The file seems to transfer to the correct location, but maybe the final commands after it reaches 100% are using the wrong path so it fails?

3) Some other issue? Any ideas would be appreciated. If you know of anywhere I can look to get more details (logs), please let me know. If you need what is in the logs, please be specific (as there are many logs and places to look).

I wish I could call Microsoft so they could help me with this bug, but unfortunately, there is noone to call.

↧

Isolate local test lab traffic from office network

December 6, 2019, 12:27 pm
$
0
0

I have just set up a Hyper-V test lab on my office workstation for the purpose of testing network changes prior to implementation. The lab has a host server running Windows Server 2016 with DHCP, DNS, Windows Deployment Service and Active Directory. There are also 2 clients running Windows 10. Currently the lab is on a Private switch, so there is no risk of its traffic bleeding into my office network. I'm at the point where I need to connect this test lab to the internet, but in a way that there is no risk of introducing its traffic, rogue DHCP servers, DNS explosions or any other assorted goodies onto my office's production network. My workstation hosting this test network is a client on my office network which has a Windows 2012 R2 server also running DHCP, DNS and AD, so there's plenty to go wrong if don't do this properly. I've set my lab on a different subnet, 192.168.10.# vs the office's 192.168.20.#. I'm not sure if this is sufficient, or if there's more that I'm missing. 

I know I'm not the first person to do this, but despite all my searching, I can't seem to find anything that addresses my particular configuration. I'm still new to this, though, so maybe I'm not searching the right terms. Also, if someone knows a good tutorial to point me toward, that would be great too.

Thanks.


↧
Search

Licensing Windows Server 2012 R2 VMs in Hyper-V Windows Server 2008 R2

January 10, 2020, 12:25 pm
$
0
0

I have 6 WS2012 R2 Standard VMs installed on the Hyper-V WS2008 R2 Datacenter server.

My question is: To properly license these VMs do I need to consider vCPU or only 6 licenses of WS2012 R2 Standart solve my problem? Or do I need to take some other factor into consideration?

Rafael.

↧

Windows server 2016 - Hyper-V

January 10, 2020, 2:05 pm
$
0
0

Hi

Is there a Limit for no. of Hyper-V server to be installed on a single Windows server 2016 standard?

Do we need Hyper-V License for each Virtual Machine on Win server 2016?

How many Hyper-V Virtual machine License comes with Windows server 2016 datacenter ?

↧
↧

Orphaned AVHDX files

January 10, 2020, 9:27 pm
$
0
0
I have a series of about 20 AVHDX files that I want to merge into one and finally into the main VHDX disc Itself. I start with the oldest whose parent file is the next one younger, the problems comes when I noticed that the parent of this last file is the youngest of them all leaving the other 18 files completely orphan, how can I merge the information from the 18 remaining files into the main VHDX so this data doesn't get lost?
↧

Hyper-v full screen not working

November 29, 2009, 9:51 am
$
0
0
I want to make a hyper-v guest os full screen.

I select view->fullscreen (or ctlr+alt+break) from Virtual Machine Connection and when the screen transitions to full-screen mode the guest os screen is the same size as before, but with the blue full-screen toolbar at the top. Any suggestions would be appreciated.

Thanks,
Kamran
↧

Windows Server 2019 DDA

January 8, 2020, 12:02 pm
$
0
0
So, I'm trying to pass-through my RX 590 onto a windows 10 guest. I followed the Microsoft DDA document and managed to dismount my gpu and assign it to the VM but when I try starting it, it gives me the following error: The operation failed because the object was not found. After digging through the logs, I found a more detailed error message saying: Could not allocate the PCI Express device with the Plug and Play Device Instance path 'PCIP\VEN_1002&DEV_67DF&SUBSYS_C4111462&REV_E1\4&288640B9&0&001A' because it is already in use by another VM.

The thing is, I definitely don't have another virtual machine. I did enable IOMMU, ACS and SR-IOV beforehand.

Here are my specs:
MB: X570 Taichi
CPU: Ryzen 3900X
GPU1: RX 5700 XT
GPU2: RX 590
↧
Viewing all 19461 articles
Browse latest View live
Search
<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>