oVirt isn't an OS manager, it is a hardware manager. It manages the virtual task of plugging a hard drive in.The OS then needs to manage its hardware within the virtual machine. You manage the OS.You may set up templates and scripts that automate and roll this stuff out for you in future.I don't know of any hypervisor that takes care of in-OS management for you apart from heavily scripted/automated systems usually found in the big cloud providers like AWS.On 30 January 2020 6:57:34 pm Eugène Ngontang <sympavali@gmail.com> wrote:
Hi Joseph.Thanks to your answer, I perfectly know Linux disk management, but I thought it was to Ovirt to manage all attached disk.I'm new to Ovirt ecosystem.Thanks again.Eugène NGLe jeu. 30 janv. 2020 à 03:33, Joseph Goldman <joseph@goldman.id.au> a écrit :Like a normal hard-disk, you will need to format it - currently it is just a 'physical' device (/dev/vdb), you'll need to create a partition table, then a partition, then format that partition to a filesystem. This is not anything specific with oVirt or VM's - just general harddrive management._______________________________________________
(https://www.digitalocean.com/community/tutorials/how-to-partition-and-format-storage-devices-in-linux - guide using parted I found from a quick google)
On 30/1/20 11:54 am, Eugène Ngontang wrote:
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 Blocs Id. Système
/dev/vda1 * 2048 52428766 26213359+ 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------------------------------------------------------------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-leave@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/
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-leave@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/LU5BHFW66FA6GXB7N4Z3I7FTKBSCTZOO/
_______________________________________________Users mailing list -- users@ovirt.orgTo unsubscribe send an email to users-leave@ovirt.orgPrivacy Statement: https://www.ovirt.org/site/privacy-policy/oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/