<table cellspacing="0" cellpadding="0" border="0" ><tr><td valign="top" style="font: inherit;"><DIV>just a kind remainder, the fix hasn't been checked into svn yet.</DIV>
<DIV> </DIV>
<DIV>We've been running on VHDs with fix for last couple of weeks, seems to be no side effects. </DIV>
<DIV> </DIV>
<DIV>also need to check in the VDCopy patch<BR><BR>--- On <B>Thu, 10/15/09, Klaus Espenlaub <I><Klaus.Espenlaub@Sun.COM></I></B> wrote:<BR></DIV>
<BLOCKQUOTE style="PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: rgb(16,16,255) 2px solid"><BR>From: Klaus Espenlaub <Klaus.Espenlaub@Sun.COM><BR>Subject: Re: [vbox-dev] fixed - VHD not readable by Hyper-V<BR>To: "Huihong Luo" <huisinro@yahoo.com><BR>Cc: "vbox-dev@virtualbox.org" <vbox-dev@virtualbox.org><BR>Date: Thursday, October 15, 2009, 4:24 AM<BR><BR>
<DIV class=plainMail>Huihong Luo wrote:<BR>> found another bug, I've attached the patch<BR>> two bugs:<BR>> (1) parent locators set to zero for base images<BR>> (2) block allocation table to be block-size aligned (2M)<BR>> after these two fixes, vbox vhds works well on Hyper-V, I tested quite some large vhd files from p2v, all works fine now.<BR>> These two fixes should be very safe to check in, (not sure if it may break snapshots, though)<BR><BR>Thanks a lot for those fixes (and the previous ones as well), I'll try to find time myself to apply them in the near future - or find someone else who will handle it.<BR><BR>What I wanted to ask earlier already - did you read <A href="http://www.virtualbox.org/wiki/Contributor_information" target=_blank>http://www.virtualbox.org/wiki/Contributor_information</A> ? Which of the two contribution options (SCA or MIT licensed patches) do you pick?<BR><BR>Again, we're very grateful
for the excellent contributions.<BR><BR>Klaus<BR><BR>> - hl<BR>> <BR>> --- On *Tue, 10/13/09, Huihong Luo /<<A href="http://us.mc343.mail.yahoo.com/mc/compose?to=huisinro@yahoo.com" ymailto="mailto:huisinro@yahoo.com">huisinro@yahoo.com</A>>/* wrote:<BR>> <BR>> <BR>> From: Huihong Luo <<A href="http://us.mc343.mail.yahoo.com/mc/compose?to=huisinro@yahoo.com" ymailto="mailto:huisinro@yahoo.com">huisinro@yahoo.com</A>><BR>> Subject: Re: [vbox-dev] Fwd: VHD not readable by Hyper-V<BR>> To: "<A href="http://us.mc343.mail.yahoo.com/mc/compose?to=vbox-dev@virtualbox.org" ymailto="mailto:vbox-dev@virtualbox.org">vbox-dev@virtualbox.org</A>" <<A href="http://us.mc343.mail.yahoo.com/mc/compose?to=vbox-dev@virtualbox.org" ymailto="mailto:vbox-dev@virtualbox.org">vbox-dev@virtualbox.org</A>><BR>> Date: Tuesday, October
13, 2009, 1:40 PM<BR>> <BR>> I found the vhd bug on vbox implementation. vbox mistakenly sets<BR>> parent locators ("wi2r", etc.) for base vhd image. If setting these<BR>> fields to zeros for base image, Hyper-V is happy. Should be very<BR>> easy to fix, if you need the code diff, let me know<BR>> <BR>> VBox The MS spec states:<BR>> <BR>> Parent Locator Entries<BR>> <BR>> These entries store an absolute byte offset in the file where the<BR>> parent locator for a differencing hard disk is stored. This field is<BR>> used only for differencing disks and should be set to zero for<BR>> dynamic disks.<BR>> <BR>> <BR>> --- On *Tue, 10/13/09, Huihong
Luo /<<A href="http://us.mc343.mail.yahoo.com/mc/compose?to=huisinro@yahoo.com" ymailto="mailto:huisinro@yahoo.com">huisinro@yahoo.com</A>>/* wrote:<BR>> <BR>> <BR>> From: Huihong Luo <<A href="http://us.mc343.mail.yahoo.com/mc/compose?to=huisinro@yahoo.com" ymailto="mailto:huisinro@yahoo.com">huisinro@yahoo.com</A>><BR>> Subject: [vbox-dev] Fwd: VHD not readable by Hyper-V<BR>> To: "<A href="http://us.mc343.mail.yahoo.com/mc/compose?to=vbox-dev@virtualbox.org" ymailto="mailto:vbox-dev@virtualbox.org">vbox-dev@virtualbox.org</A>" <<A href="http://us.mc343.mail.yahoo.com/mc/compose?to=vbox-dev@virtualbox.org" ymailto="mailto:vbox-dev@virtualbox.org">vbox-dev@virtualbox.org</A>><BR>> Date: Tuesday, October 13, 2009, 6:49 AM<BR>> <BR>> <BR>> <BR>>
Sent from my iPhone<BR>> <BR>> Begin forwarded message:<BR>> <BR>>> *From:* Huihong Luo <<A href="http://us.mc343.mail.yahoo.com/mc/compose?to=huisinro@yahoo.com" ymailto="mailto:huisinro@yahoo.com">huisinro@yahoo.com</A>><BR>>> *Date:* October 13, 2009 6:35:42 AM PDT<BR>>> *To:* Shu Wu <<A href="http://us.mc343.mail.yahoo.com/mc/compose?to=superwushu@gmail.com" ymailto="mailto:superwushu@gmail.com">superwushu@gmail.com</A>><BR>>> *Subject:* *Re: [vbox-dev] VHD not readable by Hyper-V*<BR>>> <BR>>> No problem with vpc, vbox also understands vhds from hyper-v<BR>>> <BR>>> It is just that hyper-v
doesn't understand vbox's vhd <BR>>> Sent from my iPhone<BR>>> <BR>>> On Oct 13, 2009, at 2:27 AM, Shu Wu <<A href="http://us.mc343.mail.yahoo.com/mc/compose?to=superwushu@gmail.com" ymailto="mailto:superwushu@gmail.com">superwushu@gmail.com</A>> wrote:<BR>>> <BR>>>> Can your VHD disk be read by Virtual PC or Virtual Server? It<BR>>>> seems that Hyper-V and Virtual-PC share the same vhd format.<BR>>>> One year ago I wrote my own program to generate a vhd file<BR>>>> and make it to be accepted by Virtual PC, just following the<BR>>>> official vhd specification. But I haven't tested it on Hyper-V.<BR>>>>
<BR>>>> Cheers,<BR>>>> <BR>>>> Wu Shu<BR>>>> <BR>>>> 2009/10/13 Klaus Espenlaub <<A href="http://us.mc343.mail.yahoo.com/mc/compose?to=Klaus.Espenlaub@sun.com" ymailto="mailto:Klaus.Espenlaub@sun.com">Klaus.Espenlaub@sun.com</A>><BR>>>> <BR>>>> Huihong Luo wrote:<BR>>>> <BR>>>> None of vbox created vhd disk files are readable by<BR>>>> 2008 Hyper-V.<BR>>>> This is the error: "The file or directory is<BR>>>> corrupted and
unreadable"<BR>>>> I am debugging through the code, trying to change<BR>>>> Footer info, such as version, creator OS, checksun,<BR>>>> etc., to see it can correct the error.<BR>>>> If you know what might be wrong, pls post<BR>>>> <BR>>>> <BR>>>> We only know what Microsoft documents in their VHD format<BR>>>> spec, which we believe to have correctly implemented.<BR>>>> However as usual those specs are incomplete and not<BR>>>>
really precise, so there's plenty of room for different<BR>>>> interpretations.<BR>>>> <BR>>>> Klaus<BR>>>> <BR>>>> <BR>>>> _______________________________________________<BR>>>> vbox-dev mailing list<BR>>>> <A href="http://us.mc343.mail.yahoo.com/mc/compose?to=vbox-dev@virtualbox.org" ymailto="mailto:vbox-dev@virtualbox.org">vbox-dev@virtualbox.org</A><BR>>>> <<A href="http://vbox.innotek.de/mailman/listinfo/vbox-dev" target=_blank>http://vbox.innotek.de/mailman/listinfo/vbox-dev</A>><BR>>>>
<<A href="http://vbox.innotek.de/mailman/listinfo/vbox-dev" target=_blank>http://vbox.innotek.de/mailman/listinfo/vbox-dev</A>><A href="http://vbox.innotek.de/mailman/listinfo/vbox-dev" target=_blank>http://vbox.innotek.de/mailman/listinfo/vbox-dev</A><BR>>>> <BR>>>> <BR>>>> _______________________________________________<BR>>>> vbox-dev mailing list<BR>>>> <A href="http://us.mc343.mail.yahoo.com/mc/compose?to=vbox-dev@virtualbox.org" ymailto="mailto:vbox-dev@virtualbox.org">vbox-dev@virtualbox.org</A><BR>>>> <<A href="http://vbox.innotek.de/mailman/listinfo/vbox-dev" target=_blank>http://vbox.innotek.de/mailman/listinfo/vbox-dev</A>><A href="http://vbox.innotek.de/mailman/listinfo/vbox-dev"
target=_blank>http://vbox.innotek.de/mailman/listinfo/vbox-dev</A><BR>> <BR>> -----Inline Attachment Follows-----<BR>> <BR>> _______________________________________________<BR>> vbox-dev mailing list<BR>> <A href="http://us.mc343.mail.yahoo.com/mc/compose?to=vbox-dev@virtualbox.org" ymailto="mailto:vbox-dev@virtualbox.org">vbox-dev@virtualbox.org</A><BR>> <A href="http://vbox.innotek.de/mailman/listinfo/vbox-dev" target=_blank>http://vbox.innotek.de/mailman/listinfo/vbox-dev</A><BR>> <BR>> <BR>> -----Inline Attachment Follows-----<BR></DIV></BLOCKQUOTE></td></tr></table>