[ovirt-users] Virtual disk shareable checkbox is greyed out when using GlusterFS storage domains

[Ken Holmes]

Is there a work around that will allow multiple VM's to share a disk with out 
using the network? 
I read Dave White's Thread but saw no resolution except maybe using NetApp.
Thanks
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/TP4FHRA4DR55X3KN63VVXB4EZAL6HZVH/

[ovirt-users] Virtual disk attached to VM showing in the Webui but not identified by the system

[Eugène Ngontang]

Hi,

I'm facing a virtual disk behavior I don't understand.

Currently my VMs are spun up with a Boot disk of 25GB and an additional
disk of 215/45/65 GB depending.

When logged to the webui I see the two disks, but when I ssh to VM we only
see the primary boot disk, the other one can't get a *UUID* and then cannot
and is not mounted

I also noticed in the webui the second disk doesn't have a logical name as
you can see in the screenshot.

Pleas can someone explain this behavior please?

Here is my disk management commands outputs

[root@fp-gpu-node3 centos]# fdisk -l
>
>
> Disque /dev/vda : 26.8 Go, 26843545600 octets, 52428800 secteurs
>
> Unités = secteur de 1 × 512 = 512 octets
>
> Taille de secteur (logique / physique) : 512 octets / 512 octets
>
> taille d'E/S (minimale / optimale) : 512 octets / 512 octets
>
> Type d'étiquette de disque : dos
>
> Identifiant de disque : 0x000b6061
>
>
> Périphérique Amorçage  Début Fin  BlocsId. Système
>
> /dev/vda1   *20485242876626213359+  83  Linux
>
>
> Disque /dev/vdb : 48.3 Go, 48318382080 octets, 94371840 secteurs
>
> Unités = secteur de 1 × 512 = 512 octets
>
> Taille de secteur (logique / physique) : 512 octets / 512 octets
>
> taille d'E/S (minimale / optimale) : 512 octets / 512 octets
>
>
> [root@fp-gpu-node3 centos]# blkid
>
> /dev/vda1: UUID="3ef2b806-efd7-4eef-aaa2-2584909365ff" TYPE="xfs"
>
> [root@fp-gpu-node3 centos]# lsblk -f
>
> NAME   FSTYPE LABEL UUID MOUNTPOINT
>
> sr0
>
> vda
>
> └─vda1 xfs  3ef2b806-efd7-4eef-aaa2-2584909365ff /
>
> vdb
>

Thanks for your help.
-- 
LesCDN 
engont...@lescdn.com

*Aux hommes il faut un chef, et au*

* chef il faut des hommes!L'habit ne fait pas le moine, mais lorsqu'on te
voit on te juge!*
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/IMKAO46PZ5UXOM27L7G7SD444OGFFQYF/

Re: [ovirt-users] virtual Disk

[Taste-Of-IT]

Hello Ala,

yes i refere to vm disk size. I tried both and the result is the same 
like you described. So only extend size field is working. Yes i think 
the field should grayed out or disabled.


Thx for your replay - question is answered - happy holiday

Maik

Am 2015-12-22 14:33, schrieb Ala Hino:

Typo:
I am referring to the UI ...

- Original Message -

From: "Ala Hino" <ah...@redhat.com>
To: "Taste-Of-IT" <kont...@taste-of-it.de>
Cc: users@ovirt.org
Sent: Tuesday, December 22, 2015 3:28:38 PM
Subject: Re: [ovirt-users] virtual Disk

Hello,

Are referring to vm disk size?
If so and I am referring here to the I:
I just tried both options and found that even though it is possible to 
change
the size field, the size isn't changed. Probably this field should be 
graded

out and only display the current size.
However, the "Extend size by(GB)" field does extend the disk size.

- Original Message -
> From: "Taste-Of-IT" <kont...@taste-of-it.de>
> To: users@ovirt.org
> Sent: Monday, December 21, 2015 11:06:49 PM
> Subject: [ovirt-users] virtual Disk
>
> Hello,
> i testing oVirt 3.6 as Self-Hosted-Engine and create a virtual machine.
> Now i want to change the size of the disk and found the possibilities to
> change the size of the disk and a field to grow the disk. In ovirt
> manual it is descripted to change the value of the grow field. My
> question is what is the difference and what are the results of that. E.g
> what happend if i only change the disk size from 8 to 10? is it the same
> like i change the grow size from 0 to 2?
>
> thx for technical explanation.
> ___
> Users mailing list
> Users@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] virtual Disk

[Ala Hino]

Hello,

Are referring to vm disk size?
If so and I am referring here to the I:
I just tried both options and found that even though it is possible to change 
the size field, the size isn't changed. Probably this field should be graded 
out and only display the current size.
However, the "Extend size by(GB)" field does extend the disk size.

- Original Message -
> From: "Taste-Of-IT" <kont...@taste-of-it.de>
> To: users@ovirt.org
> Sent: Monday, December 21, 2015 11:06:49 PM
> Subject: [ovirt-users] virtual Disk
> 
> Hello,
> i testing oVirt 3.6 as Self-Hosted-Engine and create a virtual machine.
> Now i want to change the size of the disk and found the possibilities to
> change the size of the disk and a field to grow the disk. In ovirt
> manual it is descripted to change the value of the grow field. My
> question is what is the difference and what are the results of that. E.g
> what happend if i only change the disk size from 8 to 10? is it the same
> like i change the grow size from 0 to 2?
> 
> thx for technical explanation.
> ___
> Users mailing list
> Users@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
> 
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

[ovirt-users] virtual Disk

[Taste-Of-IT]

Hello,
i testing oVirt 3.6 as Self-Hosted-Engine and create a virtual machine. 
Now i want to change the size of the disk and found the possibilities to 
change the size of the disk and a field to grow the disk. In ovirt 
manual it is descripted to change the value of the grow field. My 
question is what is the difference and what are the results of that. E.g 
what happend if i only change the disk size from 8 to 10? is it the same 
like i change the grow size from 0 to 2?


thx for technical explanation.
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] virtual disk terminology in oVirt/RHEV improvements needed?

[Sven Kieske]

Hi,

i just want to +1 this.

I often have to lookup this information myself and it is not that
clear at all which storage does use which file format and so on.

Great writeup!

-- 
Mit freundlichen Grüßen / Regards

Sven Kieske

Systemadministrator
Mittwald CM Service GmbH  Co. KG
Königsberger Straße 6
32339 Espelkamp
T: +49-5772-293-100
F: +49-5772-293-333
https://www.mittwald.de
Geschäftsführer: Robert Meyer
St.Nr.: 331/5721/1033, USt-IdNr.: DE814773217, HRA 6640, AG Bad Oeynhausen
Komplementärin: Robert Meyer Verwaltungs GmbH, HRB 13260, AG Bad Oeynhausen
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] virtual disk terminology in oVirt/RHEV improvements needed?

[Christopher Young]

Definitely a +1.  I've had/felt these frustrations from my management when
trying to convince them on oVirt, so any more technically detailed,
flow-charted, better explained verbiage would be most welcome.

2015-02-10 10:56 GMT-05:00 Sven Kieske s.kie...@mittwald.de:

 Hi,

 i just want to +1 this.

 I often have to lookup this information myself and it is not that
 clear at all which storage does use which file format and so on.

 Great writeup!

 --
 Mit freundlichen Grüßen / Regards

 Sven Kieske

 Systemadministrator
 Mittwald CM Service GmbH  Co. KG
 Königsberger Straße 6
 32339 Espelkamp
 T: +49-5772-293-100
 F: +49-5772-293-333
 https://www.mittwald.de
 Geschäftsführer: Robert Meyer
 St.Nr.: 331/5721/1033, USt-IdNr.: DE814773217, HRA 6640, AG Bad Oeynhausen
 Komplementärin: Robert Meyer Verwaltungs GmbH, HRB 13260, AG Bad Oeynhausen
 ___
 Users mailing list
 Users@ovirt.org
 http://lists.ovirt.org/mailman/listinfo/users

___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

[ovirt-users] virtual disk terminology in oVirt/RHEV improvements needed?

[Gianluca Cecchi]

Hello,
in my opinion the terms

raw, qcow2, thin provisioned, sparse, preallocated

are used in sub optimal way in oVirt and RHEV documentation and create
confusion for the new incoming user (but not only to him/her)

My referrals for them are:

oVirt Admin Guide at:
http://www.ovirt.org/OVirt_Administration_Guide

and the draft RHEV 3.5:
https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Virtualization/3.5-Beta/html/Administration_Guide/chap-Virtual_Machine_Disks.html

Sometimes I have to come back to docs to clear my doubts and I'm never
fully satisfied.

I report below only some excerpts to explain my findings

oVirt
1) Virtual disks can have one of two formats, either Qcow2 or RAW. The type
of storage can be either Sparse or Preallocated. Snapshots are always
sparse but can be taken for disks created either as RAW or sparse.

-- From above one concludes that format is one thing and type is
another thing and that all the mix format/type are in general possible
(depending on storage layout... see below): Qcow2/Sparse, RAW/Prellocated,
Qcow2/Preallocated, RAW/Sparse


But then, both in Ovirt and RHEV page
2) A virtual disk with a preallocated (RAW) format has significantly faster
write speeds than a virtual disk with a thin provisioning (Qcow2) format.
Thin provisioning takes significantly less time to create a virtual disk.
The thin provision format is suitable for non-IO intensive virtual machines.

-- now one concludes instead that format==type and that so
preallocated==RAW
thin provisioning==Qcow2

and also indirectly that thin provisioning == sparse because in point 1)
the term sparse was the one used..
Indeed later, in section 12.2 of RHEV and in section Understanding Virtual
Disks of oVirt guide there is the classification of the 2 types again,
Preallocated and Thin Provisioned and the latter contains:
For sparse virtual disks backing storage is not reserved and is allocated
as needed during runtime. This allows for storage overcommitment ...
And this confirms that sparse==thin provisioned

In the same part for both docs

3) Table 11.1. Permitted Storage Combinations for oVirt and
Table 12.1. Permitted Storage Combinations for RHEV

Again there are almost-all the combinations described:
For file based storage (NFS) only Qcow2/Preallocated is not contemplated
For iSCSI/SAN only RAW/Sparse is not contemplated

4) Gluster
last but not least, It is not clear in my opinion where should be put
Gluster (file based or SAN based)... I think that depending on
POSIXFS_DOMAIN (pre 3.5, correct?) or GLUSTERFS_DOMAIN usage it could match
both of them
As far as format, it seems both qcow2 and raw are possible

This message is just to share my uncertainty when I have to deal with disks
in oVirt and explain/compare with VMware, to make it possible to simplify
life to new users.
Coming from VMware world they know about:

- thin provision
- thick provision (lazy zeroed)
- thick provision (eager zeroed)

see also:
https://pubs.vmware.com/vsphere-50/index.jsp?topic=%2Fcom.vmware.vsphere.storage.doc_50%2FGUID-4C0F4D73-82F2-4B81-8AA7-1DD752A8A5AC.html

In my opinion it could be useful to have a preface with a short description
of all the terminology that will be used

HIH improving docs,

Gianluca
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users