[ovirt-users] Re: [External] : Can't create shared disk after upgrade to 4.5.4

2024-04-10 Thread Marcos Sungaila via Users
Hi Igor,

When creating a virtual disk, in 4.5 (oVirt & OLVM), the "New Virtual Disk" 
dialog brings the "Enable Incremental Backup" automatically checked.
The "Shareable" and "Enable Incremental Backup" options can not be set 
simultaneously.
To create a shareable virtual disk, click the "Shareable" option and unclick  
the "Enable Incremental Backup" option.

Marcos

-Original Message-
From: Igor Filipovic via Users  
Sent: Sunday, March 31, 2024 3:08 PM
To: users@ovirt.org
Subject: [External] : [ovirt-users] Can't create shared disk after upgrade to 
4.5.4

Hi,
In my lab I'm using OLVM ( I know ... it's not original oVirt but it is based 
on it ). I was using 4.4.10, and after upgrade to 4.5.4 I'm no longer able to 
create shared disks, on any storage domain (nfs or fc). When I was on previous 
release I was able to create and use shared disks (required for cluster 
systems), but after upgrade when I try to create shared disk (preallocated) I'm 
getting an error saying : Error while executing action: Cannot add Virtual 
Disk. Disk's volume format is not supported for shareable disk.
In engine log I can see only this :
2024-03-31 20:04:28,997+02 WARN  
[org.ovirt.engine.core.bll.storage.disk.AddDiskCommand] (default task-37) 
[b8bc1831-260a-4253-b6fe-e0c81a6f81b6] Validation of action 'AddDisk' failed 
for user admin@internal-authz. Reasons: 
VAR__ACTION__ADD,VAR__TYPE__DISK,SHAREABLE_DISK_IS_NOT_SUPPORTED_BY_VOLUME_FORMAT

Does anyone have idea what could be the reason or how to solve this?
Thanks in advance and best regards
Igor
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org Privacy Statement: 
https://urldefense.com/v3/__https://www.ovirt.org/privacy-policy.html__;!!ACWV5N9M2RV99hQ!L20R9crrO5U83hLh7CeaT_gS2u23u3YCoCwD0PbazERUAUQzSAHav4mjEaMxXASXfUKVYMPXrQs6_-j6_A$
oVirt Code of Conduct: 
https://urldefense.com/v3/__https://www.ovirt.org/community/about/community-guidelines/__;!!ACWV5N9M2RV99hQ!L20R9crrO5U83hLh7CeaT_gS2u23u3YCoCwD0PbazERUAUQzSAHav4mjEaMxXASXfUKVYMPXrQtEz9MLvg$
List Archives: 
https://urldefense.com/v3/__https://lists.ovirt.org/archives/list/users@ovirt.org/message/XONPBNWWQMCL2QEPNTC347CUXXXTBEMV/__;!!ACWV5N9M2RV99hQ!L20R9crrO5U83hLh7CeaT_gS2u23u3YCoCwD0PbazERUAUQzSAHav4mjEaMxXASXfUKVYMPXrQupLODmjQ$
 
___
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/JNRHEWQKFTHQOVEVMTO4WG2WJZMGYOG4/


[ovirt-users] Re: HPE Oneview KVM appliance 8.8.0 / 8.7.0

2024-04-10 Thread Gianluca Cecchi
On Wed, Apr 10, 2024 at 12:29 PM Angus Clarke  wrote:

> Hi Gianluca
>
> The software is free from HPE but requires a login, I've shared a link
> separately.
>
> Thanks for taking an interest
>
> Regards
> Angus
>

Apart from other considerations we are privately sharing, in my env that is
based on Cascade Lake cpu on the host, with local storage domain on
filesystem, the appliance is able to boot and complete the initial
configuration phase using your settings: Chipset i440FX w/Bios for the IDE
disk type, OS: RHEL7 x86_64. In my env graphics protocol=VNC, video type=VGA
The constraint for your tweaks is caused by the appliance's operating
system where all the virtio modules are compiled as modules and they are
not included into the initramfs.
So the system doesn't find the boot disk if you set it as virtio or
virtio-scsi.
The layout is of bios type with one partition for /boot and other
filesystems on LVM, / included.
To modify the qcow2 image you can use some tools out there, or use manual
steps this way:

. connect the disk to an existing rhel 7 / CentOS 7 helper VM where you
have lvm2 package installed
In my case my VM has one disk named /dev/sda and the HPE qcow2 disk when
added is then seen as /dev/sdb and its partitions as /dev/sdb1, ...
IMPORTANT: change the disk names below as it appears the appliance disk in
your env, otherwise you risk to compromise your existing data!!!
IMPORTANT: inside the appliance disk there is a volume group named vg01.
Verify there is no vg01 volume group already defined in your helper VM
otherwise you get into troubles

. connect to the helper VM as root user

. the LVM structure of the added disk (PV/VG/LV) should be automatically
detected
run the command "vgs" and you should see vg01 volume group listed
run the command "lvs vg01" and you should see some logical volumes listed

. mount the root filesystem of the appliance disk on a directory in your
helper VM (on /media directory in my case)
# mount /dev/vg01/lv_root /media/

. mount the /boot filesystem of the appliance disk under /media/boot
# mount /dev/sdb1 /media/boot/

. mount the /var filesystem of the appliance disk under /media/var
# mount /dev/vg01/lv_var /media/var/

. chroot into the appliance disk env
# chroot /media

. create a file with new kernel driver modules you want to include in the
new initramfs
# vi /etc/dracut.conf.d/virtio.conf

its contents have to be this one line below (similar to the already present
platform.conf):
# cat /etc/dracut.conf.d/virtio.conf
add_drivers+="virtio virtio_blk virtio_scsi"

. backup the original initramfs
# cp -p /boot/initramfs-3.10.0-1062.1.2.el7.x86_64.img
/boot/initramfs-3.10.0-1062.1.2.el7.x86_64.bak

. replace the initramfs
# dracut -fv /boot/initramfs-3.10.0-1062.1.2.el7.x86_64.img
3.10.0-1062.1.2.el7.x86_64
...
*** Creating image file done ***
*** Creating initramfs image file
'/boot/initramfs-3.10.0-1062.1.2.el7.x86_64.img' done ***
#

. verify the new contents include virtio modules

# lsinitrd /boot/initramfs-3.10.0-1062.1.2.el7.x86_64.img | grep virtio
-rw-r--r--   1 root root 7876 Sep 30  2019
usr/lib/modules/3.10.0-1062.1.2.el7.x86_64/kernel/drivers/block/virtio_blk.ko.xz
-rw-r--r--   1 root root12972 Sep 30  2019
usr/lib/modules/3.10.0-1062.1.2.el7.x86_64/kernel/drivers/char/virtio_console.ko.xz
-rw-r--r--   1 root root14304 Sep 30  2019
usr/lib/modules/3.10.0-1062.1.2.el7.x86_64/kernel/drivers/net/virtio_net.ko.xz
-rw-r--r--   1 root root 8188 Sep 30  2019
usr/lib/modules/3.10.0-1062.1.2.el7.x86_64/kernel/drivers/scsi/virtio_scsi.ko.xz
drwxr-xr-x   2 root root0 Apr 10 21:14
usr/lib/modules/3.10.0-1062.1.2.el7.x86_64/kernel/drivers/virtio
-rw-r--r--   1 root root 4552 Sep 30  2019
usr/lib/modules/3.10.0-1062.1.2.el7.x86_64/kernel/drivers/virtio/virtio.ko.xz
-rw-r--r--   1 root root 9904 Sep 30  2019
usr/lib/modules/3.10.0-1062.1.2.el7.x86_64/kernel/drivers/virtio/virtio_pci.ko.xz
-rw-r--r--   1 root root 8332 Sep 30  2019
usr/lib/modules/3.10.0-1062.1.2.el7.x86_64/kernel/drivers/virtio/virtio_ring.ko.xz

. exit the chroot environment
# exit

. Now you exited from the chroot env, umount the appliance disk filesystems
# umount /media/var /media/boot
# umount /media

. disconnect the disk from the helper VM

. create a Red Hat 7.x VM in your oVirt/OLVM env as Q35 / Bios VM with the
appliance disk configured as virtio or virtio-scsi disk

. boot the VM and it should work, apart from the current problem of the
display in your env

Eventually if it boots ok and at the end it works, push HPE to add virtio
modules that are quite the standard for disk in Qemu/KVM based env.
The virtio network starts already ok because it is activated after boot as
a module and it is not needed in the initrd phase but only after it.

Gianluca
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org

[ovirt-users] Re: [External] : Singe host installation

2024-04-10 Thread Marcos Sungaila via Users
If you are not planning to have a second KVM host in the future, I should use a 
stand-alone KVM host managed by the Cockpit web UI.

Marcos

-Original Message-
From: Jakov Sosic  
Sent: Friday, April 5, 2024 7:50 AM
To: users 
Subject: [External] : [ovirt-users] Singe host installation

Hi guys,

I want to run oVirt on a single host, is that possible?


Running external engine is a possibility.


Thanks,

Jakov
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org Privacy Statement: 
https://urldefense.com/v3/__https://www.ovirt.org/privacy-policy.html__;!!ACWV5N9M2RV99hQ!NDzjKoQ1HOMknCBr53-LYlH8FlzozS_sJUiKjub8NOKHCbNvHwR9XxNmtVQbREmch3w9tJq6L-QxKA3gzg$
oVirt Code of Conduct: 
https://urldefense.com/v3/__https://www.ovirt.org/community/about/community-guidelines/__;!!ACWV5N9M2RV99hQ!NDzjKoQ1HOMknCBr53-LYlH8FlzozS_sJUiKjub8NOKHCbNvHwR9XxNmtVQbREmch3w9tJq6L-R_ABjeoQ$
List Archives: 
https://urldefense.com/v3/__https://lists.ovirt.org/archives/list/users@ovirt.org/message/KHUW2AWDZY2YCNSCHS2PACOVCEZVAFNO/__;!!ACWV5N9M2RV99hQ!NDzjKoQ1HOMknCBr53-LYlH8FlzozS_sJUiKjub8NOKHCbNvHwR9XxNmtVQbREmch3w9tJq6L-RAWaSD0Q$
 
___
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/IJ76OBJCDU34CTAM65X6HJJIZ6TVWELZ/


[ovirt-users] Re: HPE Oneview KVM appliance 8.8.0 / 8.7.0

2024-04-10 Thread Angus Clarke
Hi Gianluca



The software is free from HPE but requires a login, I've shared a link 
separately.



Thanks for taking an interest



Regards

Angus







 On Wed, 10 Apr 2024 11:56:54 +0200 Gianluca Cecchi 
 wrote ---



On Wed, Apr 10, 2024 at 11:47 AM Angus Clarke  wrote:

Hello folks



I realise this probably isn't the place for this but someone might be 
interested or have some knowledge.



I deployed the KVM version of HPE Oneview 8.8 to oVirt 4.5 (OLVM 4.5) It came 
as a single QCOW2 disk image.







Is the image download publicly available? Or does it need any form of 
subscription ?



Gianluca___
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/JYCE3ZTGJHGY2IM2FKEAWGBQFLKAHV7Z/


[ovirt-users] Re: HPE Oneview KVM appliance 8.8.0 / 8.7.0

2024-04-10 Thread Gianluca Cecchi
On Wed, Apr 10, 2024 at 11:47 AM Angus Clarke  wrote:

> Hello folks
>
> I realise this probably isn't the place for this but someone might be
> interested or have some knowledge.
>
> I deployed the KVM version of HPE Oneview 8.8 to oVirt 4.5 (OLVM 4.5) It
> came as a single QCOW2 disk image.
>
>
Is the image download publicly available? Or does it need any form of
subscription ?

Gianluca
___
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/YXYGVCRH6QURQPOVTOSZTEY7ZT2AYMGQ/


[ovirt-users] HPE Oneview KVM appliance 8.8.0 / 8.7.0

2024-04-10 Thread Angus Clarke
Hello folks



I realise this probably isn't the place for this but someone might be 
interested or have some knowledge.



I deployed the KVM version of HPE Oneview 8.8 to oVirt 4.5 (OLVM 4.5) It came 
as a single QCOW2 disk image.



The VM I created needed a couple of tweaks to get it to boot (Chipset: i440FX 
w/Bios for the IDE disk type, OS: RHEL7 x86_64.) The VM boots and the graphical 
environment starts but sticks not long after (left over weekend, no change.) I 
did boot into the rescue environment to look at logs, I can see all the logical 
volumes mounted ok so no issue there, I see apps repeatedly trying to start 
with no obvious reason. Very similar outcome when I tried the previous 8.7 
Oneview version.



We also run a VMWare estate so the sad thing is that I've fallen back to 
deploying the ESXi version of Oneview 8.8 - it works fine, which is a shame as 
I am trying to persuade our internal teams to start using oVirt/OLVM instead of 
VMWare!



Any feedback gladly received.



Thanks

Angus___
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/APKACZOR7H63EH6DIYVKJL3XDTEBLGQG/


[ovirt-users] Re: Recreate engine without backup

2024-04-10 Thread Igor Filipovic via Users
Hi, I managed to resolve this issue.
Long story short :

- take configuration details from hosts about disks (especially if direct disks 
are being used, commands like multipath -ll, lsblk, blkid...) 
- take a xml dump from all running VM's 
- install new standalone engine
- add existing hosts to new image (running machines were detected with prefix 
"external"
- configure logical networks after checking hosts network adapters
- if direct disks exists in your configuration, create virtual disks for them 
by using xml dump files and info from hosts 
- shutdown running vm's (all with prefix "external")
- shutdown all kvm hosts and left only one kvm host running (to prevent sanlock)
- import existing storage domain from running host
- use VM import tab in Storage domain to view vm's available for import
- delete machines with prefix "external" because import detect machines with 
same VM ID
- run import VM's from storage domain, one by one ... and that's it, after 
import run the machines

***If there are no VM's listed in VM import tab after adding storage domain, 
than you need to import disks from Disk import tab in storage domain, and then 
manually create virtual machines with information from xml dump files (to be 
able to configure disks,networks,cpu,ram ... like it was originally 
configured). After creating VM's you should be able to run them.***   

Maybe it can help someone. 
Best regards, Igor
___
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/YLNLWVYZJN3RIZ66VKTNMOHNQMGUVP5Z/