`<div dir="ltr"><div class="gmail_extra"><div><div class="gmail_signature"><div dir="ltr">On 1 August 2017 at 12:37, Peter Tribble <span dir="ltr"><<a href="mailto:peter.tribble@gmail.com" target="_blank">peter.tribble@gmail.com</a>></span> wrote:<br></div><div dir="ltr">[..]</div></div></div><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><span class="gmail-"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div><div>All what you need is create such image. On top of the Solaris is it quite easy. All what you need is VBox.</div><div>Such method is quite handy because using VboxManage command is possible to create, setup blank VM and boot it in batch mode.</div><div><br></div><div>Below is fragment of my script which could be used as template. It is for install Linux inside but it can be adapted to install any OS (Solaris as well)</div></div></div></blockquote><div><br></div></span><div>Have you tried this with Solaris or illumos?<br></div></div></div></div></blockquote><div><br></div><div>As client OS inside VM? No.</div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><div></div><div>It doesn't work, because the root ZFS pool embeds the physical paths<br></div><div>to the disk inside the pool, and the emulated disk devices that VBox<br></div><div>provides don't match what comes in an EC2 instance. So yes, you can<br></div><div>create an image, but at some point you need to fix the pool to have the<br></div><div>correct metadata.</div></div></div></div></blockquote><div><br></div><div>Still it should be possible to do this somehow after detaching image from VBox and uploading it to AWS bucket or by emulate the same physical path inside VBox instance.<br>IIRC in vmdk image effective image starts from offset 32256 so it should be possible to extract it using dd command -> attach extracted image over lofiadm and import rpool -> correct rpool path -> join corrected image with vmdk header.</div><div><br></div><div>Do you know what exactly needs to be corrected or what is wrong with this physical path to disk inside zpool?</div><div><br></div><div>kloczek</div><div>-- </div><div><div><div class="gmail_signature"><div dir="ltr">Tomasz Kłoczko | LinkedIn: <span style="text-decoration-line:underline;font-size:13px;font-family:Arial;background-color:transparent;vertical-align:baseline;white-space:pre-wrap"><a href="http://lnkd.in/FXPWxH" target="_blank" style="text-decoration-line:none">http://lnkd.in/FXPWxH</a></span></div><div><br></div></div></div></div></div></div></div>
`