OSR's ntdev List: FsMinifilter : Detecting HyperV VM power-off/power-on and failover-failback

Driver Problems? Questions? Issues?
Put OSR's experience to work for you! Contact us for assistance with:

Creating the right design for your requirements
Reviewing your existing driver code
Analyzing driver reliability/performance issues
Custom training mixed with consulting and focused directly on your specific areas of interest/concern.

Check us out. OSR, the Windows driver experts.

Monthly Seminars at OSR Headquarters

East Coast USA
Windows Internals and SW Drivers, Dulles (Sterling) VA, 13 November 2017

Kernel Debugging & Crash Analysis for Windows, Nashua (Amherst) NH, 4 December 2017

Writing WDF Drivers I: Core Concepts, Nashua (Amherst) NH, 8 January 2018

WDF Drivers II: Advanced Implementation Techniques, Nashua (Amherst) NH, 15 January 2018

		OSR Online Lists > ntdev
FsMinifilter : Detecting HyperV VM power-off/power-on and failover-failback

Welcome, Guest
You must login to post to this list

Message 1 of 2

21 Apr 17 03:34

Anand A

xxxxxx@gmail.com

Join Date: 05 Aug 2014

Posts To This List: 45

FsMinifilter : Detecting HyperV VM power-off/power-on and failover-failback

I am developing a file system minifilter driver for performing incremental backups of HyperV VMs [this is pre-Server 2016]. The changed blocks are not planned to be persisted on storage media for every write operation. For simplicity, assume a 2 node cluster deployment on CSV or SMB on Server 2012 R2 running a single VM. The driver is supposed to be loaded on both the HyperV hosts. When the first backup is initiated for a VM, a user mode component will notify to the driver about files related to the VM that need to be tracked (mostly [A]VHD[X] files related to the VM). 1) Can the driver detect that the VM was powered off ? [I would like to continue incremental tracking of related files when VM is powered on again] a) If the driver was notified to start tracking the files after the VM was powered on, then I cannot do a counter based mechanism to match open and close calls to the file. b) I cannot rely on context cleanup callback for stream contexts due to filesystem caching. Is there any other way to detect this in the driver ? 2) Can the driver detect that the VM failover + failback happened ? [in which case, the next backup for the VM will be a full backup] and distinguish it from power-off / power-on case ? The driver on each host is not interacting with each other. As per the following link, it seems to be possible to track the aforesaid VM state transitions in user mode by using WMI event callback notification (__InstanceModificationEvent) : https://msdn.microsoft.com/en-us/library/cc136822(v=vs.85).aspx I want to understand if the detection mechanism can be implemented in the driver.

Message 2 of 2

01 May 17 04:24

Anand A

xxxxxx@gmail.com

Join Date: 05 Aug 2014

Posts To This List: 45

FsMinifilter : Detecting HyperV VM power-off/power-on and failover-failback

Any help would be much appreciated.

Posting Rules
You may not post new threads You may not post replies You may not post attachments	You must login to OSR Online AND be a member of the ntdev list to be able to post.

All times are GMT -5. The time now is 16:23.

Contact Us - Osr Online Homepage - Top