On 03/01/2012 04:21 PM, Terry Phelps wrote:
I have a new ovirt installation that I am playing with. If it
matters, I
built it by installing and patching Fedora 16, installing the
ovirt-engine RPM and then configuring this same machine as my "node", or
host, or whatever you call it.
I created 3 NFS shares on this machine for the 3 required domains, and
then created those domains in the ovirt-engine. I have uploaded a ISO
and created a couple of VMs and they work.
HOWEVER, when create a virtual disk for my VMs, I specifiy the "data
domain" as its location, and have then found, twice in three tries, that
the virtual disk is placed on the "export domain". I am quite sure I am
specifying my "data domain" when I create the disk. But then when I
click on the VM, and then open the "General" tab, the "Resides on
Storage Domain" field says "export".
And when I look at the host, the virtual disk really IS in the export
domain:
[root@oravm2 exportdomain]# find . -type f | xargs ls -l
...
-rw-rw---- 1 vdsm kvm 10737418240 Mar 1 09:17
./0efcc135-2a17-4cfd-ba7d-c3735349d455/images/fda97fda-f0ca-4926-9a3e-af836466b5b1/9167e3a9-1e98-4f11-a99c-616adbe52f95
I can't imagine what I might be doing wrong to make this happen. There
is no domain placement when I create the VM, as best I can tell.
Placement is given only when I create the virtual disk.
Anyone have an idea on this?
actually, there is not even support for creating a disk on the export
domain, only on data domain, so indeed very strange.
backend/vsdm logs from an "add disk" command?