<br><br><div class="gmail_quote">On Thu, Mar 1, 2012 at 7:31 PM, Jeff Bailey <span dir="ltr"><<a href="mailto:bailey@cs.kent.edu">bailey@cs.kent.edu</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
On 3/1/2012 7:13 PM, Itamar Heim wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
On 03/01/2012 06:02 PM, Terry Phelps wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
1. You said there's "not even support for creating a disk on the export<br>
domain". But when I create a virtual disk, the "new virtual disk" window<br>
that comes up has a field called "Storage Domain", and the dropdown box<br>
shows both "data" and "export".<br>
</blockquote>
<br>
this looks like a bug.<br>
einav - can you see this as well?<br>
</blockquote>
<br>
Could the storage domain have been accidentally created as another data domain instead of an export domain?<br><br></blockquote><div>You're right. I must have not set the domain type to "admin". I re-created it as an export domain.<br>
<br>When I created my VM's disks, before posing my original question, I did specify which of my (accidentally) two data domain I wanted the disk to go, but it did NOT go there. I presume that's a feature and not a bug, right?<br>
</div></div><br>