Quantcast
Channel: VMware Communities : Unanswered Discussions - Virtual Disk Development Kit
Viewing all articles
Browse latest Browse all 872

VixDiskLib_Open VIX_E_FILE_NOT_FOUND for Windows 2008 R2

$
0
0

Hi,

In order to connect to virtual disk of windows server 2008 R2 I use VDDK 1.2.1. In order to connect to virtual disk I have followed guide line from http://www.vmware.com/support/developer/vddk/vddk12_api_programming.pdf and the code is working for every VMs, except for a windows server 2008 R2 after a snapshot is taken with quiesce=true and memory = false. This is strange because with all other VM which support quiesce no problem appears.

 

Windows 2008 R2 is "fresh" installed  and the only program installed is vmwaretools (ESXi 4.1 and vmwaretools are updated). VM Windows 2008 R2 was created with ESXi 4.1 and disk.EnableUUID = true (in order to have an application-consistent snapshot)

 

the code in c# is the following (simplified):

 

morefid is the moref of windows server 2008 R2

 

//Crete Snapshot (quiesce option enabled)

 

VDDKMethods.Connect(host, user, password, morefid, ref connPtr);

string diskfilename="[Storage 2T] Win server 2008 R2/Win server 2008 R2.vmdk";

Wrapper.VixError vixError = Wrapper.VixDiskLib_Open(connPtr, diskfilename, Wrapper.VIXDISKLIB_FLAG_OPEN_READ_ONLY, ref diskPtr);

//Remove Snapshot

 

the VixDiskLib_Open error is the following: VIX_E_FILE_NOT_FOUND
this error is strange, because without quiesce option the code is working correctly.
Furthermore: if the VM already contains a quiesce snapshot, it's not possible to connect to disk, until quiesce snapshot is removed.

 

Taking a snapshot of VM "Win Server 2008 R2" with quiesce=true and memory=false two delta files are created:

-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
-rw-------    1 root     root             983552 Jun 14 15:33 Win server 2008 R2-000001-ctk.vmdk
-rw-------    1 root     root           16809984 Jun 14 15:33 Win server 2008 R2-000001-delta.vmdk
-rw-------    1 root     root                416 Jun 14 15:33 Win server 2008 R2-000001.vmdk
-rw-------    1 root     root             983552 Jun 14 15:33 Win server 2008 R2-000002-ctk.vmdk
-rw-------    1 root     root           16809984 Jun 14 15:33 Win server 2008 R2-000002-delta.vmdk

-rw-------    1 root     root                416 Jun 14 15:33 Win server 2008 R2-000002.vmdk
-rw-------    1 root     root         2147483648 Jun 10 15:05 Win server 2008 R2-33bcfcee.vswp
-rw-------    1 root     root              28477 Jun 14 15:33 Win server 2008 R2-Snapshot159.vmsn
-rw-r--r--    1 root     root                139 Jun 14 15:33 Win server 2008 R2-aux.xml
-rw-------    1 root     root             983552 Jun 14 15:05 Win server 2008 R2-ctk.vmdk
-rw-------    1 root     root        16106127360 Jun 14 15:33 Win server 2008 R2-flat.vmdk
-rwx------    1 root     root             169309 Jun 14 15:33 Win server 2008 R2-vss_manifests159.zip
-rw-------    1 root     root               8684 Jun 10 14:07 Win server 2008 R2.nvram
-rw-------    1 root     root                575 Jun  3 13:06 Win server 2008 R2.vmdk
-rw-r--r--    1 root     root                431 Jun 10 10:56 Win server 2008 R2.vmsd
-rwx------    1 root     root               2990 Jun 14 15:33 Win server 2008 R2.vmx
-rw-------    1 root     root                273 Jun 14 15:15 Win server 2008 R2.vmxf

 

-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

Before snapshot process no delta files are present. According to vmware support this is "normal" behaviour for quiesce snapshot on Win Server 2008 R2.

 

Thanks for your help!

 

becco


Viewing all articles
Browse latest Browse all 872

Trending Articles