4:21 p.m.
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?
5:40 p.m.
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?
6:02 p.m.
On Thu, Mar 1, 2012 at 10:40 AM, Itamar Heim <iheim(a)redhat.com> wrote:
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?
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.
But here's some more information:
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".
2. Here's an except from /var/log/libvirt.log, which shows where the new
disk is:
2012-03-01 14:13:45.170+0000: 32549: debug : virDomainCreateXML:1833 :
conn=0x7f884402e2b0, xmlDesc=<?xml version="1.0"
encoding="utf-8"?>
<domain type="kvm">
<name>fedora17</name>
<uuid>cde75b43-7607-47b1-9c27-c506e79986f7</uuid>
<memory>1048576</memory>
<currentMemory>1048576</currentMemory>
<vcpu>1</vcpu>
<devices>
...
<disk device="disk" type="file">
<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"/>
<target bus="virtio" dev="vda"/>
<serial>fda97fda-f0ca-4926-9a3e-af836466b5b1</serial>
<driver cache="none" error_policy="stop"
io="threads" name="qemu" type="raw"/>
</disk>
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:
# pwd
/rhev/data-center/4a224f0c-62ed-11e1-a7d2-001a64db74a4
[root@oravm2 4a224f0c-62ed-11e1-a7d2-001a64db74a4]# ls -l
total 16
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
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
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
lrwxrwxrwx 1 vdsm kvm 86 Feb 29 14:01 mastersd ->
/rhev/data-center/mnt/oravm2.acbl.net:
_datadomain/cacfa958-dc71-49ae-b1cd-a51bde0f860d
2:13 a.m.
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?
2:31 a.m.
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?
_______________________________________________
Users mailing list
Users(a)ovirt.org
http://lists.ovirt.org/mailman/listinfo/users
5:41 p.m.
----- Original Message -----
From: "Jeff Bailey" <bailey(a)cs.kent.edu>
Subject: Re: [Users] New virtual disks will NOT reliably be placed where I specified
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?
I tried to reproduce, but couldn't: We offer in the GUI to create the disk only on
active Data domains (all other storage domains are filtered out - I also checked the
code).
It also seems strange that the backend hasn't blocked this from happening; therefore,
I assume that Jeff's reasoning below is probably the case here.
Could the storage domain have been accidentally created as another
data
domain instead of an export domain?
> _______________________________________________
> Users mailing list
> Users(a)ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
_______________________________________________
Users mailing list
Users(a)ovirt.org
http://lists.ovirt.org/mailman/listinfo/users
4658
days inactive
4661
days old
5 comments
4 participants
participants (4)
-
Einav Cohen -
Itamar Heim -
Jeff Bailey -
Terry Phelps