Hi

I am trying to enable VSS daemon, but having issues, so I can not backup this VM,

the error message below,

[root@LANSID3CMPL01 ~]# /etc/init.d/hv_vss_daemon start
Starting Hyper-V VSS daemon                                [  OK  ]

[root@LANSID3CMPL01 ~]# /etc/init.d/hv_vss_daemon status
hv_vss_daemon is stopped

here is my system information and LIS version,

[root@LANSID3CMPL01 ~]# cat /etc/centos-release
CentOS release 6.8 (Final)
[root@LANSID3CMPL01 ~]# uname -a
Linux LANSID3CMPL01 2.6.32-642.6.1.el6.i686 #1 SMP Tue Oct 4 22:41:38 UTC 2016 i686 i686 i386 GNU/Linux

[root@LANSID3CMPL01 ~]# modinfo hv_vmbus
filename:       /lib/modules/2.6.32-642.6.1.el6.i686/weak-updates/microsoft-hyper-v/hv_vmbus.ko
version:        4.1.2
license:        GPL
srcversion:     82B9AE7A2B6BFE26B1AC6A4
alias:          acpi*:VMBus:*
alias:          acpi*:VMBUS:*
depends:
vermagic:       2.6.32-642.el6.i686 SMP mod_unload modversions 686

so any fixes available ?

Please help me, thanks ！

-- Hank

I have configured for 'Production only' checkpoint for a VM in Hyper-V 2016. After taking a checkpoint, when I use Get-VMSnapshot command, it shows 'CheckpointType' and 'SnapshotType' as 'Standard'. Also, the enum type fields does not have a field called 'Production' explicitly. Here are the powershell commands I ran:

PS C:\> Get-VM -Name vm1 | select CheckpointType

CheckpointType
--------------
ProductionOnly

PS C:\> Checkpoint-VM -Name vm1

PS C:\> $snap=Get-VMSnapshot -VMName vm1

PS C:\> $snap | select CheckpointType, SnapshotType

CheckpointType SnapshotType
-------------- ------------
      Standard     Standard

PS C:\> $snap.CheckpointType.GetType().DeclaredFields | select Name

Name
----
value__
Standard
Recovery
Planned
Missing
Replica
AppConsistentReplica
SyncedReplica

Is there a KB update required?

We have noticed that a referenced drive associated with a VM that was started but the user never logged in ended up having the reference disk grow to the size of the parent disk.

This is actually happening for all of our referenced drives as time goes one.

Because the parent is 120GB of information, this behavior is eating away our disk space.

Am I wrong to expect that the differencing drive would only contain the modified portions of the parent disk plus any additions, thereby minimizing overall disk usage?

Hi, got a 2008 r2 vm machine running on a 2008 std server w/hyper-v, it worked fine for years, but last week show this symptom black screen after boot up and when I press ctrl-alt-del shows a blank login screen. I could browse the files, can ping but can’t do rdc or use any app installed. Check all the forum and try all possible solution they said with negative results. Any suggestion or advice would be appreciated.

Which OS can have a live migration?

James

Hello,

I have Standalone Hyper V 2012 R2 Server i have a question

- can i do in-place upgrade to Hyper V 2016 Server or Windows 2016 Hyper V

- Can i Run Windows 2016 Nano server with Hyper V Package on to physical Server

Thanks

FZ2H

When using Hyper-V Server 2012 R2 (Server Core) I was able to use the following command to encrypt the boot drive (C:) -

manage-bde -on C: -rp

The motherboards I've been using have a TPM 2.0 installed.  With Server 2012 R2 I was able to encrypt the C: drive with either a BIOS or UEFI configuration.

But now with Hyper-V Server 2016 (Server Core) I get the following error message when I try to use the same command to encrypt the boot drive (C:) -

C:\>manage-bde -on C: -rp
BitLocker Drive Encryption: Configuration Tool version 10.0.14393
Copyright (C) 2013 Microsoft Corporation. All rights reserved.

Volume C: []
[OS Volume]
ERROR: Specifying the parameter '-StartupKey' or '-Password' is required to BitLocker-protect the OS volume.

Type "manage-bde -on -?" for more information.

NOTE: If the -on switch has failed to add key protectors or start encryption,
you may need to call "manage-bde -off" before attempting -on again.

With Hyper-V 2016 the motherboard is configured for UEFI and Secure Boot and I used MSINFO32 to confirm both are on as expected.

I have a single RAID10 drive that has a logical C: (Boot) and D: (Data) drive on it.  With Hyper-V Server 2012 R2 the C: drive only needed the TPM to be encrypted and for the D: drive I entered the following commands which allowed it to be automatically unencrypted via the C: drive.

manage-bde –on d: -pw (entered password - which I believe was stored on the encrypted C: drive?)
manage-bde –autounlock –enable d:

The motherboard configuration was setup to automatically reboot if there was a power outage.  

With the Sever 2016 limitation it looks like I cannot use the TPM alone to encrypt the boot drive?  I'd have to use a method like one of those below to encrypt the boot drive and automatically reboot after a power outage?

a) I could either add a 3rd logical drive (for example X:) to my RAID10 drive and use that to store the recovery key for the C: drive.  Or I could leave a USB drive plugged in at all times and it would also contain the recovery key to allow the C: drive to boot.

But in both cases it seems I would be leaving something potentially exposed in an unencrypted location that a hacker could potentially exploit (given both the X: or USB drives would be unencrypted)?

b)  I could use the -TPMAndPIN, -TPMAndStartupKey, or -TPMAndPINAndStartupKey options to encrypt the C: drive.  But that would require me to manually enter in some additional information in order to allow the Hyper-V Server 2016 to reboot (which would be a nuisance).

With Hyper-V Server 2016 is there some way to encrypt the boot drive (C:) with the TPM alone such that these type of issues (a and b above) aren't a problem? Or am I overlooking something in how this can be done on Hyper-V Server 2016?

Thanks for any insight you can provide.

P.S.  I saw there was an option (-sid) that looked like it might depend upon something in an AD domain to allow the C: drive to be encrypted/unencrypted.  But I just have a small home office network and don't have that type of sophisticated environment.

WindOfChange

Hi, here is my problem.

I've set up 3 hyper-v hosts windows 2012 R2 in a Cluster.  My problem arise when i try to backup my VM's with Veeam, i can take a crash consistent backup but when i try to use the "Application Aware Processing" it fails.  

Here is the error reported by Veeam :
Unable to create snapshot (Microsoft CSV Shadow Copy Provider) (mode: Veeam application-aware processing). Details: Writer 'Microsoft Hyper-V VSS Writer' is failed at 'VSS_WS_FAILED_AT_PREPARE_SNAPSHOT'. The writer experienced a transient error. If the backup process is retried, the error may not reoccur. --tr:Failed to verify writers state. --tr:Failed to perform pre-backup tasks.
Make sure VM does not have 'iSCSI Software Target Storage Provider' feature installed.
Retrying snapshot creation attempt (Writer 'Microsoft Hyper-V VSS Writer' is failed at 'VSS_WS_FAILED_AT_PREPARE_SNAPSHOT'. The writer experienced a transient error. If the backup process is retried, the error may not reoccur. --tr:Failed to verify writers state. --tr:Failed to perform pre-backup tasks.)
Unable to allocate processing resources. Error: Writer 'Microsoft Hyper-V VSS Writer' is failed at 'VSS_WS_FAILED_AT_PREPARE_SNAPSHOT'. The writer experienced a transient error. If the backup process is retried, the error may not reoccur. --tr:Failed to verify writers state. --tr:Failed to perform pre-backup tasks.

 I've reboot my hosts multiple time and retry the backup job multiple times to.I can see, when i use "diskshadow", that the VM's are excluded from backup because the volume is not in the shadow copy set:

I have no problem taking backups with Veeam from my Windows 2008 R2 Hyper-V Cluster

Can somebody help me figure out this issue ?

Thank you

Hi,

I'm testing cluster upgrade from Hyper-V Server 2012 R2 to 2016. I evicted first node, clean-instaled 2016 and joined it back. Everything seems to work fine, except live migration. I cannot perform the migration from a 2012 R2 host to the new 2016 host because I'm getting processor incompatibility error. I don't have compatibility enabled on my VMs because the hardware is 1:1 the same, especially processors are the same (exactly the same model). Live migrations used to work just fine between 2012 R2 nodes.

Am I missing something? What can I check?

Thanks!

Hi,

I've got a Windows Server 2012 R2 Cluster which consists of two hosts. I'm trying to live migrate everything from the second host onto the first host however nothing will live migrate unless it is switched off / offline.

I've tried live migrating from Failover Cluster manager and from within VMM and both times I get the same error messages.

The error message from Failover Cluster Manager is here -

I've rebooted Host1 to see if that would help and it hasn't. I've also run the Cluster Validation Wizard to try and see if this would highlight any problems but again it hasn't shown anything up.

I've done a lot of googling into these error messages and the only possible solution I can seem to find is the following -

https://support.microsoft.com/en-us/kb/2853203

This link fits the error and fix but not all of the symptoms or product version.

Any help would be greatly appreciated...

Thanks

Hello,

I have a VM lab with Windows 2012 and Hyper-V. Overall it has been awesome, but I have one small glitch:

The VMs on server A replicate to server B. The new Hyper-V replication feature works perfectly, except for my one problem. When I shut down and then restart the servers, replication does not always automatically resume for all VMs. Some VMs will resume replication on their own and some will require a manual resume - and it seems to be random. I can always restart replication by right clicking and the hitting Replication --> Resume Replication, but I rather hoped that this would happen automatically, all of the time.

Has anyone else experienced this? Is there a cure?

Hi,

Setting up simple two node windows failover cluster 2012 r2. while configuring quorum disk, we are getting below message,

No Quorum witness has been configured for the cluster. 1 GB disk is there as "Available Storage" under cluster disk console.

Regards,

Trying to access Hyper-V running on Server 2012 R2 from Windows 10 LTSB 2016 and I only get an error:

The Hyper-V Management Tools could not access an expected WMI class on computer....

Same server accessed from Windows 8.1 H-V Management Tools is working fine.

Anybody any idea?

According to this it should be no issue

Seb

Hi,

We have some problem with error messages in our Clustered Scale Out File servers in combination with Clustered Hyper-V environment.

We have 2 SOFS cluster with 2 host each.

Each Server is configured  with 2 Volume with 16,9 TB 

This Volume are shared in the Cluster as Cluster Shared Volumes  

And this share are shared to Hyper-V cluster and on this Shares we have the VM:s

The problem (error messages ) we got on the SOFS Servers is following

EventID 12289:

Volume Shadow Copy Service error: Unexpected error while calling GetStorageDependencyInformation. hr = 0x8007048f, The device is not connected.

.

Operation:

  Automatically choosing a diff-area volume

  Processing EndPrepareSnapshots

Context:

  Execution Context: System Provider

Error-specific details:

  Error: (0x8007048f) The device is not connected.

EventID 8193:

Volume Shadow Copy Service error: Unexpected error calling routine GetVolumePathName is fail on the path \\fasofs01.your.domain.com\vdisk01, winerror 0x0000007b.. hr = 0x8007007b, The filename, directory name, or volume label syntax is incorrect.

We got this error on every SOFS Host every day but different times.

And the amount off the error messages are different on the servers and the times too.

I have tried to find anything on the Internet but not find a good solution.

We use Veeam has a backup system and the backup seems to work from a Veeam perspective.

So what do we have to do to get rid of this errors

Best Regards

Jörg Wiesemann

I have a hyper-v guest that is displaying an odd behavior.  Both Host and Guest are running 2012 R2 server core.   The guest is a DC/DNS/DHCP/Print server.  Printing is very low volume.  Both host and guest are current on updates, including integration services.  

The guest is configured with Dynamic Memory using the following settings:

Startup: 1024
Minimum: 512
Maximum: 6144
Buffer: 20%

The issue is that the Memory Demand reported by the host doesn't reflect the memory current in use on the guest. Here is an example:
Guest Memory Available: 1.6 GB
Guest Memory Usage:1.6GB (100%)
Host Assigned Memory: 1682MB (1.6GB)
Host Memory Demand: 1446MB (1.4GB)

You will note that I have 6GB available to the the guest, which its not using, and a 20% buffer that its not getting.  It appears to me that the Host is behaving correctly because it thinks the guest is at 85 percent utilization (it ticked up to 1.7GB Assigned shortly after this reading).  What I can't figure out is why the host thinks this guest is using less than it is.  What is also interesting is that it seems to scale with increased memory.

Any ideas?

Joshua Shaw

Hi all,

I am totally new to hyper-V replication so the questions below might sound silly (while i am trying to understand a basic level of how it works)

Initial Replication
q1)how does the initial replication over the network works while the VM is actually receiving writes at the same time when it is being copied over to the replica site ? - wouldn't the initial replica be totally inconsistent or the copy is done base on snapshot created ?

Hyper-V replication log
q2) Came across this phrase in technet
"The log file is replayed in reverse order to the replica VHD in accordance with the replication frequency"

If i have make the following changes
T1) change dataA  -- captured in HRL#1
T2) change dataB  -- captured in HRL#2

Wouldn't i need to replay the HRLs in proper order (#1, then #2), instead of reversed ?? What's the point of replaying the log in reversed (from the latest to the earliest) ?

Regards,
Noob

I have generation 2 Hyper-V VM (windows server 2012 r2 client and host). I'm trying to export it to location. While exporting it's status is running, but I can't connect it using rdp or http. It stucks. When I cancel export it resumes. Status is always running (no paused or saved). All updates are installed.

Don't have any issue on centos  located on that host.

Hello,

I have created a hyper-v replica setup as described in: http://www.vkernel.ro/blog/configuring-hyper-v-replica-using-certificate-based-authentication-https

The following does apply to my setup:

1. I use a domain CA
2. I have 2 clusters with 2012 R2 hyper-v
3. SCVMM is used to manage the hosts, but I configured everything on the hyper-v console and failover cluster manager
4. I have created a  group policy for auto-enrollment of the computer certificate of the hyper-v hosts
5. I installed the replica broker role with name LOK1HA2BRK.domain.local for cluster LOK1HA2
6. I installed the replica broker role with name LOK3HA2BRK.domain.local for cluster LOK3HA2
7. I created a certificate template (duplicate computer template) as stated in the article and requested certificate for the replica broker with CN as LOK1HA2BRK.wessanen.local and LOK3HA2BRK.wessanen.local on 1 cluster host and imported the certificate on all other hosts in the clusters.
8. I have a replica broker certificate with a subject CN = LOK1HA2BRK.domain.local for the replica broker role on LOK1HA2
9. I have a replica broker certificate with a subject CN = LOK3HA2BRK.domain.local for the replica broker role on LOK3HA2

The replica role setup was successfull, but when I want to enable replication on a VM on LOK1HA2 and use replica server LOK3HA3BRK.domain.local, I get the error message:

Hyper-v could not validate certificate with thumbprint <thumbprint of broker certificate LOK1HA2BRK>. The certificate could not be verified upto the trusted certification authority. The certificate cannot be verified upto the trusted certification authroity. Error: A certificate chain processed, but terminated in a root certificate which is not trusted by the trust provider. (0x800B0109).

You would think "well just add the root certificate to the Trusted Root Certification Authorities store...", but because I use an Enterprise CA, this is already done ofcourse. There are some certificates in the Personal store of the hyper-v hosts, which also have the CN of the host itself, but they seem to be self signed. I don't know if I can remove them, because I suspect that SCVMM created them for some reasons. Secondly, i don't think it is the problem, becuase if the certificate thumbprint of the error is the thumbprint of the broker certificate. 

What I do think is strange, is that the certificate i can select for the replica server connection is only the AMS1HA2BRK certificate and NOT the computer certificate, as described in the article. I would not think that is incorrect, but it is a difference.

Windows Server 2012 r2

i'm building a sql server cluster and one of the recommendations from our dba are the following:

• to format a guest hd with 64kb allocation unit
• to create a RAID10 for the data disks in D:, E:

i'm asking because i'm of the impression that the above is under the control of the hyper-v master and SAN storage respectively?

• The virtual machine is shut down
• the Hyper-V console says the machine Does Not Have Any Snapshots
• there IS a snapshot file in the machines's snapshot folder, last written at 8:02 this AM, now 3.5 hours ago
• the VM's vhd was last written at 8:02 AM as well
• the disks are merging ("merge in progress")
• there is no disk activity on either of the files, verfied with the resource monitor

I'm afraid to try anything right now because I don't want to damage the server.  Could someone please suggest a fix for this?

Thanks,

Ingram Barclay