[vbox-dev] Is there any APIs to read/write VDI directly?

[Shu Wu]

Yes, I see it. You helped me a lot. Thank you so much!

2009/7/15 Huihong Luo <huisinro at yahoo.com>

> those APIs are provided from VBoxDDU.dll, you just need to link with
> VBoxDDu.lib, no need to use the disk source files in your project.
>
> Since they are low level APIs, I think make perfect sense not doing throug
> COM, so you can operate without vbox installations. In our case, we used
> those apis to do virtual disks, so .vdi/.vhd/.vmdk files can be mounted,
> partitioned, or formatted, etc.
>
> --- On *Wed, 7/15/09, Shu Wu <superwushu at gmail.com>* wrote:
>
>
> From: Shu Wu <superwushu at gmail.com>
> Subject: Re: [vbox-dev] Is there any APIs to read/write VDI directly?
> To: "Huihong Luo" <huisinro at yahoo.com>
> Date: Wednesday, July 15, 2009, 8:19 AM
>
>
> Yeah, thank you. But those in VBoxHDD.h are not APIs provided by VirtualBox
> SDK, that is, cannot called through COM or web services. If the prototypes
> in VBoxHDD.h change in new version, I have to change my code, too. So is
> there any plan to add new vdi APIs to the SDK?
>
> 2009/7/15 Huihong Luo <huisinro at yahoo.com<http://us.mc343.mail.yahoo.com/mc/compose?to=huisinro@yahoo.com>
> >
>
>>   VBoxHDD.h is the direct APIs you can use.
>>
>> --- On *Wed, 7/15/09, Shu Wu <superwushu at gmail.com<http://us.mc343.mail.yahoo.com/mc/compose?to=superwushu@gmail.com>
>> >* wrote:
>>
>>
>> From: Shu Wu <superwushu at gmail.com<http://us.mc343.mail.yahoo.com/mc/compose?to=superwushu@gmail.com>
>> >
>> Subject: [vbox-dev] Is there any APIs to read/write VDI directly?
>> To: vbox-dev at virtualbox.org<http://us.mc343.mail.yahoo.com/mc/compose?to=vbox-dev@virtualbox.org>
>> Date: Wednesday, July 15, 2009, 7:20 AM
>>
>> Hi, buddies. Is there any APIs in SDK to read or write data (in block or
>> byte) to vdi? I mean, if I want to perform partitioning and formatting
>> operations in a vdi, I have to run an OS to do that. But I want to do it
>> outside VirtualBox. Analysizing and operating on the structure of the vdi
>> should be tough, so is there a better way provided by VirtualBox? Thanks!
>>
>> -----Inline Attachment Follows-----
>>
>> _______________________________________________
>> vbox-dev mailing list
>> vbox-dev at virtualbox.org<http://us.mc343.mail.yahoo.com/mc/compose?to=vbox-dev@virtualbox.org>
>> http://vbox.innotek.de/mailman/listinfo/vbox-dev
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.virtualbox.org/pipermail/vbox-dev/attachments/20090716/ae096fdc/attachment.html>