<table cellspacing="0" cellpadding="0" border="0" ><tr><td valign="top" style="font: inherit;">I found the vhd bug on vbox implementation. vbox mistakenly sets parent locators ("wi2r", etc.) for base vhd image. If setting these fields to zeros for base image, Hyper-V is happy. Should be very easy to fix, if you need the code diff, let me know<br><br>VBox The MS spec states:<br><br><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><meta name="ProgId" content="Word.Document"><meta name="Generator" content="Microsoft Word 11"><meta name="Originator" content="Microsoft Word 11"><link rel="File-List" href="file:///C:%5CUsers%5Chuisinro%5CAppData%5CLocal%5CTemp%5Cmsohtml1%5C01%5Cclip_filelist.xml"><!--[if gte mso 9]><xml>
<w:WordDocument>
<w:View>Normal</w:View>
<w:Zoom>0</w:Zoom>
<w:PunctuationKerning/>
<w:ValidateAgainstSchemas/>
<w:SaveIfXMLInvalid>false</w:SaveIfXMLInvalid>
<w:IgnoreMixedContent>false</w:IgnoreMixedContent>
<w:AlwaysShowPlaceholderText>false</w:AlwaysShowPlaceholderText>
<w:Compatibility>
<w:BreakWrappedTables/>
<w:SnapToGridInCell/>
<w:WrapTextWithPunct/>
<w:UseAsianBreakRules/>
<w:DontGrowAutofit/>
</w:Compatibility>
<w:BrowserLevel>MicrosoftInternetExplorer4</w:BrowserLevel>
</w:WordDocument>
</xml><![endif]--><!--[if gte mso 9]><xml>
<w:LatentStyles DefLockedState="false" LatentStyleCount="156">
</w:LatentStyles>
</xml><![endif]--><style>
<!--
/* Font Definitions */
@font-face
{font-family:"MS Mincho";
panose-1:2 2 6 9 4 2 5 8 3 4;
mso-font-alt:"ＭＳ 明朝";
mso-font-charset:128;
mso-generic-font-family:modern;
mso-font-pitch:fixed;
mso-font-signature:-536870145 1791491579 18 0 131231 0;}
@font-face
{font-family:"\@MS Mincho";
panose-1:2 2 6 9 4 2 5 8 3 4;
mso-font-charset:128;
mso-generic-font-family:modern;
mso-font-pitch:fixed;
mso-font-signature:-536870145 1791491579 18 0 131231 0;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{mso-style-parent:"";
margin:0in;
margin-bottom:.0001pt;
mso-pagination:widow-orphan;
font-size:10.0pt;
font-family:Arial;
mso-fareast-font-family:"MS Mincho";}
p.DT, li.DT, div.DT
{mso-style-name:"DT\,Term1";
mso-style-link:"DT Char\,Term1 Char";
mso-style-next:"DL\,Def1";
margin-top:0in;
margin-right:0in;
margin-bottom:0in;
margin-left:9.0pt;
margin-bottom:.0001pt;
mso-pagination:widow-orphan;
page-break-after:avoid;
font-size:10.0pt;
font-family:Arial;
mso-fareast-font-family:"MS Mincho";
font-weight:bold;
mso-bidi-font-weight:normal;}
p.DL, li.DL, div.DL
{mso-style-name:"DL\,Def1";
mso-style-link:"DL Char\,Def1 Char";
mso-style-next:"DT\,Term1";
margin-top:0in;
margin-right:0in;
margin-bottom:4.0pt;
margin-left:.25in;
mso-pagination:widow-orphan lines-together;
font-size:10.0pt;
font-family:Arial;
mso-fareast-font-family:"MS Mincho";}
span.DTChar
{mso-style-name:"DT Char\,Term1 Char";
mso-style-locked:yes;
mso-style-link:"DT\,Term1";
font-family:Arial;
mso-ascii-font-family:Arial;
mso-fareast-font-family:"MS Mincho";
mso-hansi-font-family:Arial;
mso-bidi-font-family:Arial;
mso-ansi-language:EN-US;
mso-fareast-language:EN-US;
mso-bidi-language:AR-SA;
font-weight:bold;
mso-bidi-font-weight:normal;}
span.DLChar
{mso-style-name:"DL Char\,Def1 Char";
mso-style-locked:yes;
mso-style-link:"DL\,Def1";
font-family:Arial;
mso-ascii-font-family:Arial;
mso-fareast-font-family:"MS Mincho";
mso-hansi-font-family:Arial;
mso-bidi-font-family:Arial;
mso-ansi-language:EN-US;
mso-fareast-language:EN-US;
mso-bidi-language:AR-SA;}
@page Section1
{size:8.5in 11.0in;
margin:1.0in 1.25in 1.0in 1.25in;
mso-header-margin:.5in;
mso-footer-margin:.5in;
mso-paper-source:0;}
div.Section1
{page:Section1;}
-->
</style><!--[if gte mso 10]>
<style>
/* Style Definitions */
table.MsoNormalTable
{mso-style-name:"Table Normal";
mso-tstyle-rowband-size:0;
mso-tstyle-colband-size:0;
mso-style-noshow:yes;
mso-style-parent:"";
mso-padding-alt:0in 5.4pt 0in 5.4pt;
mso-para-margin:0in;
mso-para-margin-bottom:.0001pt;
mso-pagination:widow-orphan;
font-size:10.0pt;
font-family:"Times New Roman";
mso-ansi-language:#0400;
mso-fareast-language:#0400;
mso-bidi-language:#0400;}
</style>
<![endif]-->
<p class="DT">Parent Locator Entries</p>
<p class="DL" style="page-break-after: avoid;">These entries store an absolute byte
offset in the file where the parent locator for a differencing hard disk is
stored. This field is used only for differencing disks and should be set to
zero for dynamic disks. </p>
<br><br><br>--- On <b>Tue, 10/13/09, Huihong Luo <i><huisinro@yahoo.com></i></b> wrote:<br><blockquote style="border-left: 2px solid rgb(16, 16, 255); margin-left: 5px; padding-left: 5px;"><br>From: Huihong Luo <huisinro@yahoo.com><br>Subject: [vbox-dev] Fwd: VHD not readable by Hyper-V<br>To: "vbox-dev@virtualbox.org" <vbox-dev@virtualbox.org><br>Date: Tuesday, October 13, 2009, 6:49 AM<br><br><div id="yiv438658739"><div><br><br>Sent from my iPhone</div><div><br>Begin forwarded message:<br><br></div><blockquote type="cite"><div><b>From:</b> Huihong Luo <<a rel="nofollow" ymailto="mailto:huisinro@yahoo.com" target="_blank" href="/mc/compose?to=huisinro@yahoo.com">huisinro@yahoo.com</a>><br><b>Date:</b> October 13, 2009 6:35:42 AM PDT<br><b>To:</b> Shu Wu <<a rel="nofollow" ymailto="mailto:superwushu@gmail.com" target="_blank" href="/mc/compose?to=superwushu@gmail.com">superwushu@gmail.com</a>><br><b>Subject:</b> <b>Re:
[vbox-dev] VHD not readable by Hyper-V</b><br><br></div></blockquote><div></div><blockquote type="cite"><div><div>No problem with vpc, vbox also understands vhds from hyper-v<br><br></div><div>It is just that hyper-v doesn't understand vbox's vhd </div><div><br>Sent from my iPhone</div><div><br>On Oct 13, 2009, at 2:27 AM, Shu Wu <<a rel="nofollow" ymailto="mailto:superwushu@gmail.com" target="_blank" href="/mc/compose?to=superwushu@gmail.com"></a><a rel="nofollow" ymailto="mailto:superwushu@gmail.com" target="_blank" href="/mc/compose?to=superwushu@gmail.com">superwushu@gmail.com</a>> wrote:<br><br></div><div></div><blockquote type="cite"><div>Can your VHD disk be read by Virtual PC or Virtual Server? It seems
that Hyper-V and Virtual-PC share the same vhd format. One year ago I
wrote my own program to generate a vhd file and make it to be accepted
by Virtual PC, just following the official vhd specification. But I
haven't tested it on Hyper-V.<br>
<br>Cheers,<br><br>
Wu Shu<br><br><div class="gmail_quote">2009/10/13 Klaus Espenlaub <span dir="ltr"><<a rel="nofollow" ymailto="mailto:Klaus.Espenlaub@sun.com" target="_blank" href="/mc/compose?to=Klaus.Espenlaub@sun.com"></a><a rel="nofollow" ymailto="mailto:Klaus.Espenlaub@sun.com" target="_blank" href="/mc/compose?to=Klaus.Espenlaub@sun.com"></a><a rel="nofollow" ymailto="mailto:Klaus.Espenlaub@sun.com" target="_blank" href="/mc/compose?to=Klaus.Espenlaub@sun.com">Klaus.Espenlaub@sun.com</a>></span><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div><div></div><div class="h5">Huihong Luo wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
None of vbox created vhd disk files are readable by 2008 Hyper-V.<br>
This is the error: "The file or directory is corrupted and unreadable"<br>
I am debugging through the code, trying to change Footer info, such as version, creator OS, checksun, etc., to see it can correct the error.<br>
If you know what might be wrong, pls post<br>
</blockquote>
<br></div></div>
We only know what Microsoft documents in their VHD format spec, which we believe to have correctly implemented. However as usual those specs are incomplete and not really precise, so there's plenty of room for different interpretations.<br>
<br>
Klaus<br>
<br>
<br>
_______________________________________________<br>
vbox-dev mailing list<br>
<a rel="nofollow" ymailto="mailto:vbox-dev@virtualbox.org" target="_blank" href="/mc/compose?to=vbox-dev@virtualbox.org"></a><a rel="nofollow" ymailto="mailto:vbox-dev@virtualbox.org" target="_blank" href="/mc/compose?to=vbox-dev@virtualbox.org"></a><a rel="nofollow" ymailto="mailto:vbox-dev@virtualbox.org" target="_blank" href="/mc/compose?to=vbox-dev@virtualbox.org">vbox-dev@virtualbox.org</a><br>
<a rel="nofollow" target="_blank" href="http://vbox.innotek.de/mailman/listinfo/vbox-dev"></a><a rel="nofollow" target="_blank" href="http://vbox.innotek.de/mailman/listinfo/vbox-dev"></a><a rel="nofollow" target="_blank" href="http://vbox.innotek.de/mailman/listinfo/vbox-dev">http://vbox.innotek.de/mailman/listinfo/vbox-dev</a><br>
</blockquote></div><br>
</div></blockquote><blockquote type="cite"><div><span>_______________________________________________</span><br><span>vbox-dev mailing list</span><br><span><a rel="nofollow" ymailto="mailto:vbox-dev@virtualbox.org" target="_blank" href="/mc/compose?to=vbox-dev@virtualbox.org"></a><a rel="nofollow" ymailto="mailto:vbox-dev@virtualbox.org" target="_blank" href="/mc/compose?to=vbox-dev@virtualbox.org">vbox-dev@virtualbox.org</a></span><br><span><a rel="nofollow" target="_blank" href="http://vbox.innotek.de/mailman/listinfo/vbox-dev"></a><a rel="nofollow" target="_blank" href="http://vbox.innotek.de/mailman/listinfo/vbox-dev">http://vbox.innotek.de/mailman/listinfo/vbox-dev</a></span><br></div></blockquote></div></blockquote></div><br>-----Inline Attachment Follows-----<br><br><div class="plainMail">_______________________________________________<br>vbox-dev mailing list<br><a ymailto="mailto:vbox-dev@virtualbox.org"
href="/mc/compose?to=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></div></blockquote></td></tr></table>