[Users] SOLVED: New virtual disks will NOT reliably be placed where I specified

Terry Phelps tgphelps50 at gmail.com
Mon Mar 5 22:26:17 UTC 2012


On Thu, Mar 1, 2012 at 7:31 PM, Jeff Bailey <bailey at cs.kent.edu> wrote:

> On 3/1/2012 7:13 PM, Itamar Heim wrote:
>
>> On 03/01/2012 06:02 PM, Terry Phelps wrote:
>>
>>>
>>> 1. You said there's "not even support for creating a disk on the export
>>> domain". But when I create a virtual disk, the "new virtual disk" window
>>> that comes up has a field called "Storage Domain", and the dropdown box
>>> shows both "data" and "export".
>>>
>>
>> this looks like a bug.
>> einav - can you see this as well?
>>
>
> Could the storage domain have been accidentally created as another data
> domain instead of an export domain?
>
> You're right. I must have not set the domain type to "admin". I re-created
it as an export domain.

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?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ovirt.org/pipermail/users/attachments/20120305/75e5dac2/attachment-0001.html>


More information about the Users mailing list