<br><br><div class="gmail_quote">On Thu, Mar 1, 2012 at 10:40 AM, Itamar Heim <span dir="ltr"><<a href="mailto:iheim@redhat.com">iheim@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
On 03/01/2012 04:21 PM, Terry Phelps wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
I have a new ovirt installation that I am playing with. If it matters, I<br>
built it by installing and patching Fedora 16, installing the<br>
ovirt-engine RPM and then configuring this same machine as my "node", or<br>
host, or whatever you call it.<br>
<br>
I created 3 NFS shares on this machine for the 3 required domains, and<br>
then created those domains in the ovirt-engine. I have uploaded a ISO<br>
and created a couple of VMs and they work.<br>
<br>
HOWEVER, when create a virtual disk for my VMs, I specifiy the "data<br>
domain" as its location, and have then found, twice in three tries, that<br>
the virtual disk is placed on the "export domain". I am quite sure I am<br>
specifying my "data domain" when I create the disk. But then when I<br>
click on the VM, and then open the "General" tab, the "Resides on<br>
Storage Domain" field says "export".<br>
<br>
And when I look at the host, the virtual disk really IS in the export<br>
domain:<br>
<br>
[root@oravm2 exportdomain]# find . -type f | xargs ls -l<br>
...<br>
-rw-rw---- 1 vdsm kvm 10737418240 Mar 1 09:17<br>
./0efcc135-2a17-4cfd-ba7d-<u></u>c3735349d455/images/fda97fda-<u></u>f0ca-4926-9a3e-af836466b5b1/<u></u>9167e3a9-1e98-4f11-a99c-<u></u>616adbe52f95<br>
<br>
I can't imagine what I might be doing wrong to make this happen. There<br>
is no domain placement when I create the VM, as best I can tell.<br>
Placement is given only when I create the virtual disk.<br>
<br>
Anyone have an idea on this?<br>
</blockquote>
<br>
actually, there is not even support for creating a disk on the export domain, only on data domain, so indeed very strange.<br>
backend/vsdm logs from an "add disk" command?<br>
</blockquote></div><br>I don't know exactly where to look for "backend/vsdm logs from an "add disk" command". If you'll tell me, I'll forward them.<br><br>But here's some more information:<br>
<br>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".<br>
<br>2. Here's an except from /var/log/libvirt.log, which shows where the new disk is:<br><br>2012-03-01 14:13:45.170+0000: 32549: debug : virDomainCreateXML:1833 : conn=0x7f884402e2b0, xmlDesc=<?xml version="1.0" encoding="utf-8"?><br>
<domain type="kvm"><br> <name>fedora17</name><br> <uuid>cde75b43-7607-47b1-9c27-c506e79986f7</uuid><br> <memory>1048576</memory><br> <currentMemory>1048576</currentMemory><br>
<vcpu>1</vcpu><br> <devices><br>...<br> <disk device="disk" type="file"><br> <source file="/rhev/data-center/4a224f0c-62ed-11e1-a7d2-001a64db74a4/0efcc135-2a17-4cfd-ba7d-c3735349d455/images/fda97fda-f0ca-4926-9a3e-af836466b5b1/9167e3a9-1e98-4f11-a99c-616adbe52f95"/><br>
<target bus="virtio" dev="vda"/><br> <serial>fda97fda-f0ca-4926-9a3e-af836466b5b1</serial><br> <driver cache="none" error_policy="stop" io="threads" name="qemu" type="raw"/><br>
</disk><br><br>And here's some shell commands from the host, that (as best I can tell) shows the disk path name from above to be in the export domain:<br><br># pwd<br>/rhev/data-center/4a224f0c-62ed-11e1-a7d2-001a64db74a4<br>
<br>[root@oravm2 4a224f0c-62ed-11e1-a7d2-001a64db74a4]# ls -l<br>total 16<br>lrwxrwxrwx 1 vdsm kvm 88 Feb 29 14:01 0efcc135-2a17-4cfd-ba7d-c3735349d455 -> /rhev/data-center/mnt/oravm2.acbl.net:_exportdomain/0efcc135-2a17-4cfd-ba7d-c3735349d455<br>
lrwxrwxrwx 1 vdsm kvm 85 Feb 29 14:01 862e4be6-8aca-4c68-ac52-d9e73151b468 -> /rhev/data-center/mnt/oravm2.acbl.net:_isodomain/862e4be6-8aca-4c68-ac52-d9e73151b468<br>lrwxrwxrwx 1 vdsm kvm 86 Feb 29 14:01 cacfa958-dc71-49ae-b1cd-a51bde0f860d -> /rhev/data-center/mnt/oravm2.acbl.net:_datadomain/cacfa958-dc71-49ae-b1cd-a51bde0f860d<br>
lrwxrwxrwx 1 vdsm kvm 86 Feb 29 14:01 mastersd -> /rhev/data-center/mnt/oravm2.acbl.net:_datadomain/cacfa958-dc71-49ae-b1cd-a51bde0f860d<br><br><br>