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

Recommended pagefile configuration of a replicated guest

$
0
0

Dear all:

Windows expects to have a Pagefile. So if I configure replication for a guest and I don't want to replicate the Pagefile, which is constantly changing, I will have to create the page file on a separate disk which is excluded from replication.

However, there is a problem: If you suspend that guest machine and resume it or you shut it down and restart it, sometimes it freezes. This happens from time to time, say one out of three times. It ONLY happens if the Pagefile is on a separate virtual disk.

Why would that happen? Well, according to https://www.altaro.com/hyper-v/excluding-paging-file-from-hyper-v-replication/"Relocating the paging file to a VHD connected SCSI controller is not supported" and that is what I did, since I had no other choice: this is a hyper-v generation2 guest, which does NOT SUPPORT or offer IDE-connected virtual disks.

Furthermore, https://www.altaro.com/hyper-v/hyper-v-page-file-settings/ explains: "you cannot place a virtual machine’s swap file on a VHD that is attached to the virtual SCSI chain. This is because the SCSI driver is synthetic, so it doesn’t load until after the virtual machine’s operating system has attempted to initialize its page file. You must place swap files for virtual machines on VHDs attached to the IDE chain."

If that is true, who can tell me what I can do to exclude the Pagefile from replication, if possible at all?

(Ah no, I don't want to run a gen1 machine :-)




Debian and Ubuntu server alternative installer report larger disk than the virtual hard disk size

$
0
0

We have Hyper-V running on Windows Server 2016. We created new VM with virtual disk size of 10GB and boot it with corresponding Linux ISO.

The Debian installer and the old Ubuntu Server installer, report the total disk space as 10.7 GB. The same happens when we use VM generation 1 and 2. Tested with Debian 9.6.0-9.9.0 installer and Ubuntu 18.04.2 LTS alternative (old) installer.

The new Ubuntu Server 18.04.2 LTS Installer (Subiquity) reports the correct size of 10GB.


Synthetic SCSI Controller Instance ID GUID Failed to power on with Error

$
0
0

Applied October Update and now getting this:

Synthetic SCSI Controller Instance ID GUID Failed to power on with Error 'A virtual disk support provider for the specified files was not found

What should I do?

VMconnect full screen does not display connection bar when DPI higher than 100% on v1607 14393

$
0
0

VMconnect full screen does not display connection bar when DPI higher than 100% onv1607 14393(issue exists with both the server and the client's VMconnection).

 

It's really inconvenient to use a virtual machine on a full screen at a DPI higher than 100%.

 

Even with the latest updates installed (as of April 2019), the problem persists

 

I hope this issue can be fixed in time, at least for now v1607 14393 Server and Client LTSB versions are still in the mainstream support.

 

How to repo on v1607 14393:

1. Set DPI to above 100%(for example, 125%, 150, or higher), logoff and re-login to the change take effect

2. Start a virtual machine and switch to full-screen mode

3. You'll find the blue connection bar doesn't exist.

4. Set DPI to 100%, logoff and re-login to the change take effect

5. Start a virtual machine and switch to full-screen mode

3. You'll find the blue connection bar does exist on the top.

 

This thread may dou to the same issue:Missing connection bar in Client Hyper V


 

Hyper-V VSS writer missing

$
0
0

Hello,
I'm using Backup Exec 20.1 to perform daily backups of virtual machines, but quite offten the backup end up failing due to error: 

V-79-57344-37935 - Snapshot Technology: Initialization failure on: "VRTSRV::\\backup.blade.local\Hyper-V?Virtual?Machine\DC_b". Snapshot technology used: Microsoft Volume Shadow Copy Service (VSS).

Snapshot technology error (0xE000942F): Cannot capture a snapshot of the virtual machine volumes. Ensure that the Hyper-V Virtual Machine Management Service is running and the status of the Microsoft Hyper-V VSS writer is Stable.

Check the Windows Event Viewer for details.

When i look for the writer in the "vssadmin list writer" output, the writer is not present there. If I restart Virtual machine management service and run vssadmin again, the writer appears.

Sometimes many backups can complete without the writer dissapearing, but then the writer dissapears again. I can't find any error on warning in Windows Event Viewer.

I'm running Windows server 2016 and the VM's are running on the same server as the Backup Exec is installed on.

So is there any sollution to this problem or a way to find out what is happening to the writer ?

Thanks

Martin

VM on Server 2019 Hyper-V rebooted twice today after stable for 2 weeks

$
0
0

Hi all,

Brand new Fujitsu RX2540M4 server with 2 Xeon Silver CPUs, 128GB DDR4 mem and 6 x 480GB SSD in RAID-6. Server 2019 Standard ROK installed, Hyper-V role enabled. There are 2 VM's running on it, both Server 2019 STD, in production since about 2 weeks. SRV1-DC is domain controller with 8GB RAM assigned, SRV2-ADMIN is domain member and hosts a SQL SRV DB and acts as a terminal server for 6 thin client users (Office 365 ProPlus apps and ERP system users), with 96GB assigned to it. NIC team 1 consists of 2 Gbit adapters, used by the Hyper-V host, NIC team 2 consists of 4 Gbit adapters and is used as a virtual switch for the VM's.

Today, SRV2-ADMIN suddenly rebooted twice, the following errors can be found in the Hyper-V events on the HV host:

'SRV2-ADMIN' has encountered a fatal error.  The guest operating system reported that it failed with the following error codes: ErrorCode0: 0x3B, ErrorCode1: 0xC0000005, ErrorCode2: 0xFFFF864C3F0BBAA9, ErrorCode3: 0xFFFF8C0BDAE62250, ErrorCode4: 0x0.  If the problem persists, contact Product Support for the guest operating system.  (Virtual machine ID B6FE9B8F-9129-4B6A-81AB-79BCE490AD6C)

Error code 0x3B assuming a memory access violation

'SRV2-ADMIN' has encountered a fatal error.  The guest operating system reported that it failed with the following error codes: ErrorCode0: 0x50, ErrorCode1: 0xFFFFFC048E600000, ErrorCode2: 0x2, ErrorCode3: 0xFFFFF8005A252377, ErrorCode4: 0x2.  If the problem persists, contact Product Support for the guest operating system.  (Virtual machine ID B6FE9B8F-9129-4B6A-81AB-79BCE490AD6C)

Error code 0x50 PAGE_FAULT_IN_NONPAGED_AREA

The errors make me suspect the RAM in this server, but this is a brand new machine which has 4 sticks of 32GB ECC memory. Before contacting Fujitsu I would like to be 200% sure it's a hardware and not a driver issue.

The Hyper-V host hasn't rebooted, only this one VM. Of course, it's the biggest memory user so if one of the 4 sticks of RAM is going south, chances are high that the errors occur within this VM.

I hope that someone out there recognizes this behavior and is wanting to share his/her experience here.

Thanks!

Kristof

Windows Server 2019 Datacenter boot loops after enabling Hyper-V

$
0
0

I took my Windows Server 2016 Datacenter test server in my home lab (Dell R710 with two X5650s and 32GB of RAM) and installed Server 2019 Datacenter on it to try out the new features that are centered around VMs (Hyper-V) and data deduplication. The OS install went fine, but after enabling Hyper-V in Server Manager, the system goes through its normal reboot that occurs during Hyper-V enablement, then it proceeds to boot loop. Windows Server 2019 install media's boot repair does not fix the issue, and I cannot get in via Safe Mode. Any advice would be greatly appreciated.

Hyper V Host, Memory Limiting, Is it possible?

$
0
0

Hi All,

Hopefully a simple question, my google-fu seems not to be able to find the answer. I wanted to know if it is possible to set a limit on a HV host, that sets the available memory for VM's. However in the event of fail over it would be able to use.

Put another way, basically reserve the necessary memory for one or two host failure, so I can't inadvertently over provision and then wonder what happened when my servers drop because there isn't enough memory in a fail over situation.

Hope that makes sense.

Cheers

Paul.


Unable to create checkpoints-backup getting failed.

$
0
0


 

Hi,

We have Hyper-V on 2012 R2, SCVMM 2012.
Virtual machine is also on 2008R2 OS. Recently Veeam backup started to fail for 2 VM's with below error. 

Failed to create snapshot (Data ONTAP VSS Hardware Provider) (mode: Hyper-V child partition snapshot) Details: Failed to add volume [\\?\Volume{XXXX}\] to the VSS snapshot set
The volume shadow copy provider is not registered in the system.
--tr:Failed to add volumes to the snapshot set.
--tr:Failed to perform pre-backup tasks.  


I have performed below checks:

Verified VSS writers in server.
Restarted services in OS and Hyper-V host.
Validated cluster storage space.
Tried to take manual snapshot, its getting failed with below error:

Error (12700)
VMM cannot complete the host operation on the host because of the error: Checkpoint operation for 'XXXXXXXX' failed. 
Unknown error (0x8001)

Recommended Action
Resolve the host issue and then try the operation again.

Other VM's in the same host are running fine. Not sure how to fix this issue. 

Any suggestions how to solve this issue.?



Abhishek

Impossible to live-migrate VMs with .vhdx

$
0
0

Hello everyone,

I have a Windows Server 2012 R2 and a new server with Server 2019.

I'm trying to live migrate VMs' from Server 2012 R2 to Server 2019 and noticed that VMs with .vhdx fail to be live migrated on the new host. The migration starts and progress until the end (or close to then end ?) of the process and then fail.

- On the 2012 R2 host, I can see the following error in the eventvwr: "Event 21026 Hyper-V-VMMS - Virtual machine migration operation for SERVER_NAME failed at migration destination SERVER_DST. (Virtual machine ID VM_ID)".

- On the 2019 host, I can see the following error in the eventvwr: "The absolute path 'C:\Windows\system32\vmguest.iso' is valid for the " ISO Disk Image pool, but references a file that does not exist.

FYI: The guest OS that we are trying to move are 2008 R2 and 2012 Servers.

Live migration is enabled on both host and I tried to do it via CredSSP.

Migration of .vhd is working fine.

Does anyone have an idea on why this is happening ?

Thank you very much by advance for the help you can provide.

Cheers.

Hyper-V 2019 - Guest VM's shutdown unexpectedly

$
0
0

Hi,

Since upgrading my Hyper-V servers to Windows Server 2019, including KB4471332 from last night, my guest VM's do not power down on restart of the 2019 host.

I can confirm integration components are as up to date as possible, and each guest is configured to shutdown when the host restarts.

Each guest gets the "Why did I shutdown unexpectedly message".

The even viewer yields the following all within 30 seconds of restarting the host:

Shut down physical computer. Stopping/saving all virtual machines...

'ADFS' failed to perform the 'Shutting Down' operation. The virtual machine is currently performing the following operation: 'Shutting Down'. (Virtual machine ID 0CFDF648-EE9D-4141-9EBD-9A6D911C3442)
'ADFS' failed to shut down. (Virtual machine ID 0CFDF648-EE9D-4141-9EBD-9A6D911C3442)

The Update Orchestrator Service service terminated with the following error:
This operation returned because the timeout period expired.

Failed to restore configuration for port 59229EE2-C880-4BF2-9849-89A21EC17772 (Friendly Name: ) on switch 300C0E17-E123-4182-BE62-AAD1860BE841 (Friendly Name: ), status = Object Name not found..

Everything is configured as it was on the 2016 Hyper-V host.

The message ADFS failed to shut down because it is shutting down seems terribly odd to me.  Of course its shutting down, just need the host to wait. (Yes the registry is set to 120 as the default time for the host....)

Fairly simple to recreate....just spin up a 2019 server, install Hyper-V role, throw in a VM and test.

Any help would be appreciated, but my money is on it being another bug.

Hyper-V 2016 VMs stuck 'Creating checkpoint 9%' while starting backups

$
0
0

We have a two clustered W2016 Hyper-V hosts, every couple of days one of the hosts gets stuck when the backup kicks off. In Hyper-V manager the VMs all say 'Creating checkpoint 9%' It's always the same percentage 9%. You can't cancel the operation and the VMMS service refuses to stop, the only way to get out of the mess is to shutdown the VMs, and hard reset the effected node. The backup works for a few days then it all starts again.

The only events I can see on the effected node is:

Event ID: 19060 source: Hyper-V-VMMS

'VMName' failed to perform the 'Creating Checkpoint' operation. The virtual machine is currently performing the following operation: 'Creating Checkpoint'.

Can anybody help please? Cluster validation is clean. Hosts and guests are patched up.

Hyper-V 2012 R2 Virtual Server that crashes every 8 hours, on the dot!

$
0
0

Hey Everyone, We've got a Hyper-V 2012 Virtual Server that has started having issues several weeks ago. If the server is left running, it will crash every 8 hours, sometimes to the SECOND from the previous boot time stamp. Its almost always within a minute of the 8 hour interval. I've checked scheduled tasks, scheduled backups, SQL maintenance.....nothing!

However, if we reboot the server, say at 7 hours and 50 minutes, it will not crash and continue to run happily for another 8 hours.....at which time it will crash again. The only thing we get after a crash is the crappy new blue screen that reports"Registry Error." The event log is incredibly clean with no suggestion as to the cause. We have three other Virtual servers

that are Hyper-V virtual servers and they are working great. We've ran all kinds of virus and malware scans and everything is clean. By the way the Host Server is 2016 R2 Standard

Anyone have any ideas, or seen anything similar?

Hyper-V 2019 VM Cluster Replication

$
0
0
Ever since upgrading our 2 Hyper-V clusters to 2019 from 2012 R2 when trying to set up a new VM replication I get errors. Works for existing VMs replicating that were created before the upgrade but any new VMs fail. Enabling the replication seems to create the VM fine on the replica and creates drives at 4,096KB ready for replication but trying to start the initial replication fails with the error:

Start-VMInitialReplication : Hyper-V failed to start replication for virtual machine 'VM': Operation aborted
(0x80004004). (Virtual machine ID E3E5EDD5-66CA-48AB-8F52-CA63A3A6AEC5)
Hyper-V could not find the virtual machine 'VM' on the Replica server and will connect to the Hyper-V Replica
Broker in the next retry interval. (Virtual machine ID E3E5EDD5-66CA-48AB-8F52-CA63A3A6AEC5)
Replication operation for virtual machine 'VM' failed. (Virtual machine ID
E3E5EDD5-66CA-48AB-8F52-CA63A3A6AEC5) (Primary server: 'Host1', Replica server:
'Broker')
At line:1 char:1
+ Start-VMInitialReplication -VMName 'VM'
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : NotSpecified: (Microsoft.HyperV.PowerShell.VMTask:VMTask) [Start-VMInitialReplication],
   VirtualizationOperationFailedException
    + FullyQualifiedErrorId : OperationFailed,Microsoft.HyperV.PowerShell.Commands.StartVMInitialReplicationCommand


Doing the same process through the failover cluster gui I get a similar error. Says the replication was enabled successfully however initial replication could not be started. And goes on to say Hyper-V could not find the virtual machine on the replica server.

Has this yet to be recognized as a bug in Windows Server 2019?

There are locally mounted VM Error

$
0
0

I am upgrading Hyper-V 2012 to 2016 by using Nutanix. During that upgrade it says there are few locally mounted VMs on one node but when i login to that node i dont see any vm mounted.

Please help me to resolve it.


Live Migration - Between Clusters in Different Forest

$
0
0

Dear All,

I wanted to migrate VMs between clusters and the clusters are in different forest (Forests are Trusted ).

I have tried the "Use live migration without Failover Clustering to move a virtual machine", But its giving error (attached). 

Kindly advice the best possible way to live migrate the VMs between 2 different forests(Forests are Trusted).



Hardware requirements for my server

$
0
0

Hello Guys, 

I need some help with my server hardware requirements : I'm planning to have one physical server running the VMs 

1VM Domain Controller with up to 200 AD accounts

2VM 1 Print/File Server

3VM Exchange Server with up to 200 e-mail address

Or 2 physical servers : first one to run VM domain controller and second VM exchange server. 

and the second physical server for print/ file server ?

which option you think would give best performance? if I go with the second option , how much memory and cpu speed do you suggest ?

Advice on Hyper-v storage set up

$
0
0

Hi Guys,

I'm after some advice please on how to correctly set up storage in a Hyper-v scenario.

I have a few questions if someone wouldnt mind giving me their two cents.

I'm looking for the best solution for performance for my VMs.

  • What RAID configuration is best for performance in a Hyper-v scenario? I've read that RAID10 is best for overall read and write performance particularly for SQL VMs.

  • If I had a RAID1 configuration am I best creating two partitions for OS and Data where HyperV will be stored?

  • I have a customer at the moment who are running VMs on one big C partition on RAID1. Would I get better performance if I partition this volume or would it make no difference?

  • If I have a SQL server VM running on one large partition, would I get any performance benefits If I created additional VHDX and moved SQL data and logs to their own VHDX or would it make no difference if they're on the same array/physical storage?

The top and bottom of my query really is:-

What is the best possible set up I could do to maximise the performance on a server with 1 or 2 RAID1s.

thank you!

Rouge Network Adapter

$
0
0

Hi,

Everything seems to be working however on Server 2016 I seem to have a rouge network adapter which is a Hyper-V Virtual Network Adapter, its disabled and won't start when double clicked is this normal?... Or is it left over... I can't remember if I reset anything up

I have also got a Hyper V Virtual Switch Extension Adapter which has an exclamation mark on it and has an error 10 cannot start error on it, however if I view hidden devices Hyper V Virtual Switch Extension Adapter #2 shows up fine.

I have the Hyper V connectivity working via the second NIC in the server and Allow Management Operating systems to share this network adapter is unticked.

Can all the above be ignored as it seems to be working?

VHDX file got created AVHDX file automatically

$
0
0
Hi Team,

I have a Virtual Machine on Hyper-V for which I have a problem, its VHDX file got created AVHDX file automatically and machine behaving very weired.

We are not able to figure out how to restore it back. 

Could you please help us on this issue.

Regards
Sriman
Viewing all 19461 articles
Browse latest View live


<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>