[ovirt-users] Re: New VM from Template and Storage size
It is reasonable flow that you inherit the configuration from the template, but you can change most of the settings during the creation of the VM, I just don't understand why not to be able to change the disk size and name. Why disk size? You can say the same thing with any other settings, so just make a template for any different setting you need for different VMs based on that same OS. This flow of changing the disk size is supported in any other platforms take a few, OpenStack, VMWare, Xen and any other Cloud providers. I don't see a reason why to do this in two API calls, one for VM creation and then another one for just expanding the disk size. I do understand if you create a VM based on a thin template which is just a link that there's no other way. Another "issue" is that it creates the new of the new disk for the VM based on the template name instead of "vmname_Disk1" etc... I have a customer with many different disk sizes, varying from 50GB up to 200GB, If I go and create a template for an OS based on that, I will probably have 10 templates, it's not scalable if you need to just modify something in the template as well. So the only option right now is to use OpenStack Glance for saving images or create a new feature in Foreman/Satelite for that. On 16/06/2020, 20:53, "Nir Soffer" wrote: On Tue, Jun 16, 2020 at 5:32 PM Erez Zarum wrote: > > Hey, > > I have created a template that the disk is a thick (raw) with a size of 15GB. > > I am trying to create a VM from that template but having the disk with a much larger size, both template and the VM are set to use thick and I create the new VM with the clone option, so there’s no link between the new VM and the template. > > So far the only solution I managed to find is to adjust the size after creating the VM. This looks like reasonable flow. You create the vm from a template, so you inherit the disk size from the template. Then you modify the disk to the required size. > For example, this situation causes a problematic step when using Foreman/Satelite as trying to provision a VM based on a template but with different size for the OS disk. Why is this problematic? > I assume that one of the ways to solve it is to convert the template somehow into an “image”? like using OpenStack Glance as a place to store “templates” as images? Any other way besides using Glance? If you always need to resize the template, why not create another templated with the right size based on this template? Nir ___ 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/46IFRJCTZNZZHRYVDIYGVJFBNSOJNPVX/
[ovirt-users] Re: Ansible ovirt_disk module: how to attach disk without activation
Hi Gianluca,
this looks like an issue in the module.
I have created PR which should fix the problem [1].
Please check it out. You can manually create an ansible library to which
you would copy the module and add the fix there or wait till it is added to
ansible 2.9.
Further issues/requests recommend to create on the repo.
[1] https://github.com/oVirt/ovirt-ansible-collection/pull/61
Martin Necas
On Mon, Jun 15, 2020 at 11:57 PM Gianluca Cecchi
wrote:
> On Mon, Jun 15, 2020 at 11:47 PM Gianluca Cecchi <
> gianluca.cec...@gmail.com> wrote:
>
>>
>> register: disk_attach_info
>>
>> But going to see registered variable it contains "active: true":
>>
>> "disk_activate_info": {
>> "changed": false,
>> "id": "6f7cdf02-cf8b-4fa8-ac00-6b47f6e0c827",
>> "diskattachment": {
>> "href":
>> "/ovirt-engine/api/vms/b5c67c93-bd5d-42b6-a873-05f69cece2f1/diskattachments/6f7cdf02-cf8b-4fa8-ac00-6b47f6e0c827",
>> "id": "6f7cdf02-cf8b-4fa8-ac00-6b47f6e0c827",
>> "active": true,
>> "bootable": false,
>> "disk": {
>>
>>
>>
> Unfortunately I copied two times the disk_activate_info registered value
> in the previous e-mail.
> Here below the correct disk_attach_info var contents that contains
> "active: true":
>
> "disk_attach_info": {
> "changed": true,
> "id": "6f7cdf02-cf8b-4fa8-ac00-6b47f6e0c827",
> "diskattachment": {
> "href":
> "/ovirt-engine/api/vms/b5c67c93-bd5d-42b6-a873-05f69cece2f1/diskattachments/6f7cdf02-cf8b-4fa8-ac00-6b47f6e0c827",
> "id": "6f7cdf02-cf8b-4fa8-ac00-6b47f6e0c827",
> "active": true,
> "bootable": false,
> "disk": {
> "href":
> "/ovirt-engine/api/disks/6f7cdf02-cf8b-4fa8-ac00-6b47f6e0c827",
> "id": "6f7cdf02-cf8b-4fa8-ac00-6b47f6e0c827"
> },
> ...
>
> 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/ANQCN5GFPSWJG36LH7PJJU3BU477HBPM/
>
___
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/5ALPQ2KGXEHKEKCIZMGHZYLS5QGHPKCH/
[ovirt-users] Re: oVirt-4.4 on CentOS 8.2
On Mon, Jun 15, 2020 at 10:20 PM Dominik Holler wrote: > Hello, > CentOS 8.2 was released before oVirt was prepared for CentOS 8.2 . > Currently oVirt-4.4 fails to install on CentOS 8.2 . > This will be fixed soon. > An updated version of ovn and ovs is available already on some mirrors. Please let me know if you have any problems regarding ovs/ovn on CentOS 8.2. > Dominik > ___ 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/OJANYWGYNIXTXOLE2EKSJ3PNPUV6EG5Z/
[ovirt-users] Re: oVirt-4.4 on CentOS 8.2
On Tue, Jun 16, 2020 at 12:51 PM Dominik Holler wrote: > > > > On Mon, Jun 15, 2020 at 10:20 PM Dominik Holler wrote: >> >> Hello, >> CentOS 8.2 was released before oVirt was prepared for CentOS 8.2 . >> Currently oVirt-4.4 fails to install on CentOS 8.2 . >> This will be fixed soon. > > > An updated version of ovn and ovs is available already on some mirrors. > Please let me know if you have any problems regarding ovs/ovn on CentOS 8.2. Tried OST He-basic master and it still failed: https://jenkins.ovirt.org/job/ovirt-system-tests_he-basic-suite-master/1640/artifact/exported-artifacts/mock_logs/script/stdout_stderr.log Error: Problem: package ovirt-hosted-engine-setup-2.4.6-0.0.master.20200609105658.git1e950f2.el8.noarch requires vdsm-python >= 4.40.0, but none of the providers can be installed - package vdsm-python-4.40.18-13.gitd65c4a6c2.el8.noarch requires vdsm-network = 4.40.18-13.gitd65c4a6c2.el8, but none of the providers can be installed ... - package vdsm-network-4.40.20-4.git180b82120.el8.x86_64 requires openvswitch >= 2.7.0, but none of the providers can be installed - cannot install the best candidate for the job - nothing provides librte_bitratestats.so.2()(64bit) needed by openvswitch-2.11.1-5.el8.x86_64 - nothing provides librte_bus_pci.so.2()(64bit) needed by openvswitch-2.11.1-5.el8.x86_64 ... Is this the version you built? Are there other missing stuff (deps, dnf modules, etc.)? Thanks, -- Didi ___ 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/5E2AHQOYW5LCHOLZO66IXP6GK5DWC3NC/
[ovirt-users] Update to Ovirt 4.3.10-4-1 causes XFS issue
Hi All I think I have come across this bug: https://access.redhat.com/solutions/5075561 Updating Ovirt to 4.3.10 shows that the kernel installed on the hosts is the version that has the issue: 3.10.0-1127.8.2.el7.x86_64 The RedHat article suggests updating to kernel-3.10.0-1127.10.1.el7 but running engine-upgrade-check now shows no updates available from my engine manager. Is this something I can fix myself or would the updated kernel be available? Appreciate the advice as new to Ovirt. Normally I would point the hosts to the new kernel but I think it should be updated through Ovirt manager, correct? Thanks! Chaz ___ 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/FFJOL4UKXJ2K5IDWYHLPG2ZBDEW3BAO4/
[ovirt-users] Re: Update to Ovirt 4.3.10-4-1 causes XFS issue
Hi, "Chaz Vidal" writes: > Hi All > I think I have come across this bug: > > https://access.redhat.com/solutions/5075561 > > Updating Ovirt to 4.3.10 shows that the kernel installed on the hosts > is the version that has the issue: > > 3.10.0-1127.8.2.el7.x86_64 > > The RedHat article suggests updating to kernel-3.10.0-1127.10.1.el7 > but running engine-upgrade-check now shows no updates available from > my engine manager. > > Is this something I can fix myself or would the updated kernel be available? > > Appreciate the advice as new to Ovirt. Normally I would point the > hosts to the new kernel but I think it should be updated through Ovirt > manager, correct? On the engine my update method is the following: engine-setup yum upgrade engine-setup reboot So basically run engine-setup which will update the Ovirt packages, then you can "yum upgrade" to upgrade the base system, then re-run engine-setup just to be sure nothing broke. Then you can reboot into the new kernel. The reason I do this is that engine-setup wont upgrade the full OS (including kernel) -- it will only update the ovirt packages. Hope this helps, > Thanks! > Chaz -derek -- Derek Atkins 617-623-3745 de...@ihtfp.com www.ihtfp.com Computer and Internet Security Consultant ___ 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/JLYO3LZG6QYKEEWDTF5ZSOWU7JXP3CZQ/
[ovirt-users] Re: oVirt 4.4 Self-hosted Engine and Intel Skylake CPUs
Thanks, so during an upgrade from 4.3.10 to 4.4 there should not be any issues as I have already established a Cluster and a CPU type? On 15/06/2020, 23:01, "Anton Gonzalez" wrote: Hey. Yup, this is a known issue. You can reference the following threads: https://lists.ovirt.org/archives/list/users@ovirt.org/thread/KZHDCDE6JYADDMFSZD6AXYBP6SPV4TGA/ https://lists.ovirt.org/archives/list/users@ovirt.org/thread/5LBCJGWTVRVTEWC5VSDQ2OINQ3OHKQ7K/ ___ 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/BY77QHD4TXXEUFCQWBOYLRQUSYSAE5P5/ ___ 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/4KPUBEJMGA7OBF5XALZHQCNJ6DFJGUQV/
[ovirt-users] New VM from Template and Storage size
Hey, I have created a template that the disk is a thick (raw) with a size of 15GB. I am trying to create a VM from that template but having the disk with a much larger size, both template and the VM are set to use thick and I create the new VM with the clone option, so there’s no link between the new VM and the template. So far the only solution I managed to find is to adjust the size after creating the VM. For example, this situation causes a problematic step when using Foreman/Satelite as trying to provision a VM based on a template but with different size for the OS disk. I assume that one of the ways to solve it is to convert the template somehow into an “image”? like using OpenStack Glance as a place to store “templates” as images? Any other way besides using Glance? 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/5K3OSY2SLB3BOOXIBAKQHT77VP5YZ4RZ/
[ovirt-users] Re: Weird problem starting VMs in oVirt-4.4
On Wed, Jun 10, 2020 at 6:32 PM Joop wrote:
>
> On 8-6-2020 19:55, Joop wrote:
> > On 8-6-2020 17:52, Strahil Nikolov wrote:
> >> Are you using ECC ram ?
> > No, but what are the chances that starting a VM by using Run directly vs
> > using the Boot wait menu and it hitting that bad bit each and every time?
> > BTW: this setup worked perfectly for over 9 months using 4.3.X.
> >
> > Joop
> >
> Correction, we are using ecc and ran memtest and didn't find anything wrong.
>
> Reinstalled the server and I have the same problem again.
>
> Started reading up on vdsm-hooks because I could get my VM up
> consistently when using bootmenu=enabled.
When you edit a VM in the UI, there is a "[ ] Enable menu to select boot device"
in the "Boot Options" tab. Did you try it?
Nir
> So wrote this small piece of code, most of it is copy pasted:
>
> #!/usr/bin/python3
> #
> #
> from __future__ import absolute_import
>
> import os
> import sys
> import subprocess
> import hooking
>
>
> if hooking.tobool(os.environ.get('boot_timeout', True)):
> domxml = hooking.read_domxml()
>
> os = domxml.getElementsByTagName('os')[0]
> bootelem = domxml.createElement('bootmenu')
> bootelem.setAttribute('timeout', '1000')
> bootelem.setAttribute('enable', 'yes')
> os.appendChild(bootelem)
>
> hooking.write_domxml(domxml)
> # pretty_xml_as_string = os.toprettyxml()
> # sys.stderr.write('%s\n' % pretty_xml_as_string)
>
> Saved it in /usr/libexec/vdsm/hooks/before_vm_start as 90_wait
> Played around with the timeout but lower than 1000 (1sec) and the
> problem reappears.
> For the time being I'm going forward with this workaround.
>
> For good measure I'll include my versions of ovirt/vdsm/gluster/engine
> cockpit-ovirt-dashboard-0.14.6-1.el8.noarch
> ovirt-ansible-engine-setup-1.2.4-1.el8.noarch
> ovirt-ansible-hosted-engine-setup-1.1.4-1.el8.noarch
> ovirt-host-4.4.1-1.el8.x86_64
> ovirt-host-dependencies-4.4.1-1.el8.x86_64
> ovirt-hosted-engine-ha-2.4.3-1.el8.noarch
> ovirt-hosted-engine-setup-2.4.4-1.el8.noarch
> ovirt-imageio-client-2.0.6-0.el8.x86_64
> ovirt-imageio-common-2.0.6-0.el8.x86_64
> ovirt-imageio-daemon-2.0.6-0.el8.x86_64
> ovirt-provider-ovn-driver-1.2.30-1.el8.noarch
> ovirt-release44-4.4.0-2.el8.noarch
> ovirt-vmconsole-1.0.8-1.el8.noarch
> ovirt-vmconsole-host-1.0.8-1.el8.noarch
> python3-ovirt-engine-sdk4-4.4.3-1.el8.x86_64
> python3-ovirt-setup-lib-1.3.0-1.el8.noarch
>
> vdsm-4.40.16-1.el8.x86_64
> vdsm-api-4.40.16-1.el8.noarch
> vdsm-client-4.40.16-1.el8.noarch
> vdsm-common-4.40.16-1.el8.noarch
> vdsm-gluster-4.40.16-1.el8.x86_64
> vdsm-hook-ethtool-options-4.40.16-1.el8.noarch
> vdsm-hook-fcoe-4.40.16-1.el8.noarch
> vdsm-hook-openstacknet-4.40.16-1.el8.noarch
> vdsm-hook-vhostmd-4.40.16-1.el8.noarch
> vdsm-hook-vmfex-dev-4.40.16-1.el8.noarch
> vdsm-http-4.40.16-1.el8.noarch
> vdsm-jsonrpc-4.40.16-1.el8.noarch
> vdsm-network-4.40.16-1.el8.x86_64
> vdsm-python-4.40.16-1.el8.noarch
> vdsm-yajsonrpc-4.40.16-1.el8.noarch
>
> gluster-ansible-cluster-1.0.0-1.el8.noarch
> gluster-ansible-features-1.0.5-6.el8.noarch
> gluster-ansible-infra-1.0.4-10.el8.noarch
> gluster-ansible-maintenance-1.0.1-3.el8.noarch
> gluster-ansible-repositories-1.0.1-2.el8.noarch
> gluster-ansible-roles-1.0.5-12.el8.noarch
> glusterfs-7.5-1.el8.x86_64
> glusterfs-api-7.5-1.el8.x86_64
> glusterfs-cli-7.5-1.el8.x86_64
> glusterfs-client-xlators-7.5-1.el8.x86_64
> glusterfs-events-7.5-1.el8.x86_64
> glusterfs-fuse-7.5-1.el8.x86_64
> glusterfs-geo-replication-7.5-1.el8.x86_64
> glusterfs-libs-7.5-1.el8.x86_64
> glusterfs-rdma-7.5-1.el8.x86_64
> glusterfs-server-7.5-1.el8.x86_64
> libvirt-daemon-driver-storage-gluster-5.6.0-10.el8.x86_64
> python3-gluster-7.5-1.el8.x86_64
> qemu-kvm-block-gluster-4.1.0-23.el8.1.x86_64
> vdsm-gluster-4.40.16-1.el8.x86_64
>
> ipxe-roms-qemu-20181214-3.git133f4c47.el8.noarch
> libvirt-daemon-driver-qemu-5.6.0-10.el8.x86_64
> qemu-img-4.1.0-23.el8.1.x86_64
> qemu-kvm-4.1.0-23.el8.1.x86_64
> qemu-kvm-block-curl-4.1.0-23.el8.1.x86_64
> qemu-kvm-block-gluster-4.1.0-23.el8.1.x86_64
> qemu-kvm-block-iscsi-4.1.0-23.el8.1.x86_64
> qemu-kvm-block-rbd-4.1.0-23.el8.1.x86_64
> qemu-kvm-block-ssh-4.1.0-23.el8.1.x86_64
> qemu-kvm-common-4.1.0-23.el8.1.x86_64
> qemu-kvm-core-4.1.0-23.el8.1.x86_64
>
> libvirt-admin-5.6.0-10.el8.x86_64
> libvirt-bash-completion-5.6.0-10.el8.x86_64
> libvirt-client-5.6.0-10.el8.x86_64
> libvirt-daemon-5.6.0-10.el8.x86_64
> libvirt-daemon-config-network-5.6.0-10.el8.x86_64
> libvirt-daemon-config-nwfilter-5.6.0-10.el8.x86_64
> libvirt-daemon-driver-interface-5.6.0-10.el8.x86_64
> libvirt-daemon-driver-network-5.6.0-10.el8.x86_64
> libvirt-daemon-driver-nodedev-5.6.0-10.el8.x86_64
> libvirt-daemon-driver-nwfilter-5.6.0-10.el8.x86_64
> libvirt-daemon-driver-qemu-5.6.0-10.el8.x86_64
> libvirt-daemon-driver-secret-5.6.0-10.el8.x86_64
> libvirt-daemon-driver-storage-5.6.0-10.el8.x86_64
> libvirt-daemon-driver-storage-core-5.6.0-10.el8.x86_64
> libvirt-daemon-driver-storage-disk-5.6.0-10.el8.x86_64
[ovirt-users] Re: Weird problem starting VMs in oVirt-4.4
On 3-6-2020 14:58, Joop wrote: > Hi All, > > Just had a rather new experience in that starting a VM worked but the > kernel entered grub2 rescue console due to the fact that something was > wrong with its virtio-scsi disk. > The message is Booting from Hard Disk > error: ../../grub-core/kern/dl.c:266:invalid arch-independent ELF maginc. > entering rescue mode... > > Doing a CTRL-ALT-Del through the spice console let the VM boot > correctly. Shutting it down and repeating the procedure I get a disk > problem everytime. Weird thing is if I activate the BootMenu and then > straight away start the VM all is OK. > I don't see any ERROR messages in either vdsm.log, engine.log > > If I would have to guess it looks like the disk image isn't connected > yet when the VM boots but thats weird isn't it? > As a follow up I tried a couple of other things: - installed CentOS-7 and oVirt 4.3.10 using HCI and same problem (the previous install of 4.3 was a upgraded version. Don't know the start versie) - did some testing with copying large files into the engine gluster volume through /rhev/datacenter using 'cp' and no problems - used qemu-img convert with the engine gluster volume as destination --> problems - had a good look through lots of logfiles and stumbled across an error about missing shard which aligned with qemu-img errors - turned features.shard off on the volume and restarted the volume - reran the tests with qemu-img --> no problems any more. - reinstalled Centos8.2 + oVirt-4.0, turned off sharding before starting the engine install --> no problems installing, no problems importing, no problems starting vms, sofar I need to install another server tomorrow, so I'll do that with sharding enabled and see if it crashes too and then get the logs some place safe. Regards, Joop ___ 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/6TNJYNVBJWCB2NXDYMBYVNDQUWKBJJYU/
[ovirt-users] Re: Weird problem starting VMs in oVirt-4.4
Hey Joop, are you using fully allocated qcow2 images ? Best Regards, Strahil Nikolov На 16 юни 2020 г. 20:23:17 GMT+03:00, Joop написа: >On 3-6-2020 14:58, Joop wrote: >> Hi All, >> >> Just had a rather new experience in that starting a VM worked but the >> kernel entered grub2 rescue console due to the fact that something >was >> wrong with its virtio-scsi disk. >> The message is Booting from Hard Disk >> error: ../../grub-core/kern/dl.c:266:invalid arch-independent ELF >maginc. >> entering rescue mode... >> >> Doing a CTRL-ALT-Del through the spice console let the VM boot >> correctly. Shutting it down and repeating the procedure I get a disk >> problem everytime. Weird thing is if I activate the BootMenu and then >> straight away start the VM all is OK. >> I don't see any ERROR messages in either vdsm.log, engine.log >> >> If I would have to guess it looks like the disk image isn't connected >> yet when the VM boots but thats weird isn't it? >> >As a follow up I tried a couple of other things: >- installed CentOS-7 and oVirt 4.3.10 using HCI and same problem >(the previous install of 4.3 was a upgraded version. Don't know the >start versie) >- did some testing with copying large files into the engine gluster >volume through /rhev/datacenter using 'cp' and no problems >- used qemu-img convert with the engine gluster volume as destination >--> problems >- had a good look through lots of logfiles and stumbled across an error >about missing shard which aligned with qemu-img errors >- turned features.shard off on the volume and restarted the volume >- reran the tests with qemu-img --> no problems any more. >- reinstalled Centos8.2 + oVirt-4.0, turned off sharding before >starting >the engine install >--> no problems installing, no problems importing, no problems starting >vms, sofar > >I need to install another server tomorrow, so I'll do that with >sharding >enabled and see if it crashes too and then get the logs some place >safe. > >Regards, > >Joop > >___ >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/6TNJYNVBJWCB2NXDYMBYVNDQUWKBJJYU/ ___ 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/6P5RUFXZYGOQZBOQ6FNYMUNC6G727X77/
[ovirt-users] Re: help: renamed master volume
On Tue, Jun 16, 2020 at 8:31 PM Philip Brown wrote: > > nevermind.. found the answer myself thank goodness. > > had to rename the volume back to the value of the msdUUID. not the spUUID, > which I already tried. > > If its fatal to rename that volume... > would be nice to have it lockedout or something? Did you rename the volume from within oVirt UI? Can you give clear reproduction instructions, how to break your storage domain by renaming a volume? Nir > - Original Message - > From: "Philip Brown" > To: "users" > Sent: Tuesday, June 16, 2020 10:21:12 AM > Subject: help: renamed master volume > > Im pretty new to ovirt. Trying to upgrade an old install from 4.1 to 4.3 > > on the way, I browsed into the Storage area, in one of the nodes. > > Noticed under the "Volume groups", area that the volumes were named after > some loong ID string. > > Saw there was a "rename" button. > figured it would be just like renaming a VM. thigns would just get auto > adjusted. > > but after I renamed to something in english, the cluster is freaking out, > > "cant find master domain: u'spUUID=xxx, msdUUID=xxx' " > > and under Storage: Storage DOmains, the Data(Master) is down. > How can I recover from this ASAP? :-( > ___ > 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/ZTDLZ7W4TQAON7U27IWJSOLYJBMKAB3V/ ___ 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/WM3G77V6FXPDFSNIVWVWHIKHL5J7ZCQH/
[ovirt-users] Re: help: renamed master volume
nevermind.. found the answer myself thank goodness. had to rename the volume back to the value of the msdUUID. not the spUUID, which I already tried. If its fatal to rename that volume... would be nice to have it lockedout or something? - Original Message - From: "Philip Brown" To: "users" Sent: Tuesday, June 16, 2020 10:21:12 AM Subject: help: renamed master volume Im pretty new to ovirt. Trying to upgrade an old install from 4.1 to 4.3 on the way, I browsed into the Storage area, in one of the nodes. Noticed under the "Volume groups", area that the volumes were named after some loong ID string. Saw there was a "rename" button. figured it would be just like renaming a VM. thigns would just get auto adjusted. but after I renamed to something in english, the cluster is freaking out, "cant find master domain: u'spUUID=xxx, msdUUID=xxx' " and under Storage: Storage DOmains, the Data(Master) is down. How can I recover from this ASAP? :-( ___ 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/ZTDLZ7W4TQAON7U27IWJSOLYJBMKAB3V/
[ovirt-users] help: renamed master volume
Im pretty new to ovirt. Trying to upgrade an old install from 4.1 to 4.3 on the way, I browsed into the Storage area, in one of the nodes. Noticed under the "Volume groups", area that the volumes were named after some loong ID string. Saw there was a "rename" button. figured it would be just like renaming a VM. thigns would just get auto adjusted. but after I renamed to something in english, the cluster is freaking out, "cant find master domain: u'spUUID=xxx, msdUUID=xxx' " and under Storage: Storage DOmains, the Data(Master) is down. How can I recover from this ASAP? :-( ___ 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/SV3UUFKOVVYABL7UFVIFSDIMH2442YQ6/
[ovirt-users] Re: New VM from Template and Storage size
On Tue, Jun 16, 2020 at 5:32 PM Erez Zarum wrote: > > Hey, > > I have created a template that the disk is a thick (raw) with a size of 15GB. > > I am trying to create a VM from that template but having the disk with a much > larger size, both template and the VM are set to use thick and I create the > new VM with the clone option, so there’s no link between the new VM and the > template. > > So far the only solution I managed to find is to adjust the size after > creating the VM. This looks like reasonable flow. You create the vm from a template, so you inherit the disk size from the template. Then you modify the disk to the required size. > For example, this situation causes a problematic step when using > Foreman/Satelite as trying to provision a VM based on a template but with > different size for the OS disk. Why is this problematic? > I assume that one of the ways to solve it is to convert the template somehow > into an “image”? like using OpenStack Glance as a place to store “templates” > as images? Any other way besides using Glance? If you always need to resize the template, why not create another templated with the right size based on this template? Nir ___ 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/GMD6O263TMEAMGVKNIBSRIILVZ6NCZ6S/
[ovirt-users] Re: Weird problem starting VMs in oVirt-4.4
On Tue, Jun 16, 2020 at 11:01 PM Joop wrote: > > On 16-6-2020 19:44, Strahil Nikolov wrote: > > Hey Joop, > > > > are you using fully allocated qcow2 images ? > > > > Best Regards, > > Strahil Nikolov > > > I noticed that when I use import VM from an Export domain I see that it > sometimes uses preallocated and sometimes thin-provisioned for the disk(s). > Don't know why and I don't think there is a pattern. Maybe the system selects a different storage domain? On block storage the default is preallocated, but on file based storage the default is thin. > Old VMs from 3.3 or > new ones from 4.2/3, its mixed. > I almost always use thin-provisioned but one or two could have been > preallocated by accident. > > How do I check? If the question was about creating images with: qemu-img create -f qcow2 -o preallocation=metadata ... Then it is easy, ovirt does not create such images. > Joop > > > > > На 16 юни 2020 г. 20:23:17 GMT+03:00, Joop написа: > >> On 3-6-2020 14:58, Joop wrote: > >>> Hi All, > >>> > >>> Just had a rather new experience in that starting a VM worked but the > >>> kernel entered grub2 rescue console due to the fact that something > >> was > >>> wrong with its virtio-scsi disk. > >>> The message is Booting from Hard Disk > >>> error: ../../grub-core/kern/dl.c:266:invalid arch-independent ELF > >> maginc. > >>> entering rescue mode... > >>> > >>> Doing a CTRL-ALT-Del through the spice console let the VM boot > >>> correctly. Shutting it down and repeating the procedure I get a disk > >>> problem everytime. Weird thing is if I activate the BootMenu and then > >>> straight away start the VM all is OK. > >>> I don't see any ERROR messages in either vdsm.log, engine.log > >>> > >>> If I would have to guess it looks like the disk image isn't connected > >>> yet when the VM boots but thats weird isn't it? > >>> > >> As a follow up I tried a couple of other things: > >> - installed CentOS-7 and oVirt 4.3.10 using HCI and same problem > >> (the previous install of 4.3 was a upgraded version. Don't know the > >> start versie) > >> - did some testing with copying large files into the engine gluster > >> volume through /rhev/datacenter using 'cp' and no problems > >> - used qemu-img convert with the engine gluster volume as destination > >> --> problems > >> - had a good look through lots of logfiles and stumbled across an error > >> about missing shard which aligned with qemu-img errors > >> - turned features.shard off on the volume and restarted the volume > >> - reran the tests with qemu-img --> no problems any more. > >> - reinstalled Centos8.2 + oVirt-4.0, turned off sharding before > >> starting > >> the engine install > >> --> no problems installing, no problems importing, no problems starting > >> vms, sofar > >> > >> I need to install another server tomorrow, so I'll do that with > >> sharding > >> enabled and see if it crashes too and then get the logs some place > >> safe. > >> > >> Regards, > >> > >> Joop > >> > >> ___ > >> 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/6TNJYNVBJWCB2NXDYMBYVNDQUWKBJJYU/ > ___ > 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/7BPONTX2FDDNBMUK3ZBU3ZFK5DTESGYF/ ___ 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/NARCCR7LYDFKLTQDSD27JNLQW3FML6S2/
[ovirt-users] Re: help: renamed master volume
On Tue, Jun 16, 2020 at 10:18 PM Philip Brown wrote: > > > Okay, since you asked: > > (note: this is in node 4.3.10. but hosted-engine is 4.2 > I'd LIKE to upgrade it. but the upgrade process is broken. > thats a whole nuther story, aobut how postgresql10 doesnt show up even > though its required for > yum update 'ovirt*setup' > :-/) > > > 1. go to individual node UI. > 2. Click on Storage > 3. Look at the right-sdie aera for "Volume Groups". click on the one that is > for your master data volume > 4. Click on the Rename button on the top right. Pick something sensible OK, so you are renaming logical volumes *outside* of oVirt. The node UI is *not* part of oVirt. This is just like running: # lvrename ... In the shell. I think this is one of the issues caused by not having lvm filter in the host. With a proper lvm filter, the node UI will not be able to access the logical volumes used by oVirt, that should be managed only by oVirt. Please try this: 1. Open a rootshell in the node (using ssh or node UI) 2. Create lvm filter: vdsm-tool config-lvm-filter Answer "yes" when the tool asks to confirm. 3. Go to the node UI - you should not be able to see or modify logical volumes managed by oVit. > 5. wait a while, and eventually your cluster logs will freak out. > > Happily for me, since our VMs are very lightly loaded, this did not > immediately cause a crash. > But the cluster freaked out.. engine log spewed those errors after a while.. > and in the cluster(engine) UI, it eventually showed > Storage->Domains > as offline. > (well it shows the master as offline, and it didnt even know about the other > ones any more, until I renamed it back) > > > > > > > - Original Message - > From: "Nir Soffer" > To: "Philip Brown" > Cc: "users" > Sent: Tuesday, June 16, 2020 10:56:45 AM > Subject: Re: [ovirt-users] Re: help: renamed master volume > > On Tue, Jun 16, 2020 at 8:31 PM Philip Brown wrote: > > > > nevermind.. found the answer myself thank goodness. > > > > had to rename the volume back to the value of the msdUUID. not the spUUID, > > which I already tried. > > > > If its fatal to rename that volume... > > would be nice to have it lockedout or something? > > Did you rename the volume from within oVirt UI? > > Can you give clear reproduction instructions, how to break your storage domain > by renaming a volume? > > Nir > > > - Original Message - > > From: "Philip Brown" > > To: "users" > > Sent: Tuesday, June 16, 2020 10:21:12 AM > > Subject: help: renamed master volume > > > > Im pretty new to ovirt. Trying to upgrade an old install from 4.1 to 4.3 > > > > on the way, I browsed into the Storage area, in one of the nodes. > > > > Noticed under the "Volume groups", area that the volumes were named after > > some loong ID string. > > > > Saw there was a "rename" button. > > figured it would be just like renaming a VM. thigns would just get auto > > adjusted. > > > > but after I renamed to something in english, the cluster is freaking out, > > > > "cant find master domain: u'spUUID=xxx, msdUUID=xxx' " > > > > and under Storage: Storage DOmains, the Data(Master) is down. > > How can I recover from this ASAP? :-( > > ___ > > 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/ZTDLZ7W4TQAON7U27IWJSOLYJBMKAB3V/ > ___ 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/C3RGGEWEV2XLWGBPDLDAZOSSQC76GDYU/
[ovirt-users] Re: Weird problem starting VMs in oVirt-4.4
On 16-6-2020 19:44, Strahil Nikolov wrote: > Hey Joop, > > are you using fully allocated qcow2 images ? > > Best Regards, > Strahil Nikolov > I noticed that when I use import VM from an Export domain I see that it sometimes uses preallocated and sometimes thin-provisioned for the disk(s). Don't know why and I don't think there is a pattern. Old VMs from 3.3 or new ones from 4.2/3, its mixed. I almost always use thin-provisioned but one or two could have been preallocated by accident. How do I check? Joop > > На 16 юни 2020 г. 20:23:17 GMT+03:00, Joop написа: >> On 3-6-2020 14:58, Joop wrote: >>> Hi All, >>> >>> Just had a rather new experience in that starting a VM worked but the >>> kernel entered grub2 rescue console due to the fact that something >> was >>> wrong with its virtio-scsi disk. >>> The message is Booting from Hard Disk >>> error: ../../grub-core/kern/dl.c:266:invalid arch-independent ELF >> maginc. >>> entering rescue mode... >>> >>> Doing a CTRL-ALT-Del through the spice console let the VM boot >>> correctly. Shutting it down and repeating the procedure I get a disk >>> problem everytime. Weird thing is if I activate the BootMenu and then >>> straight away start the VM all is OK. >>> I don't see any ERROR messages in either vdsm.log, engine.log >>> >>> If I would have to guess it looks like the disk image isn't connected >>> yet when the VM boots but thats weird isn't it? >>> >> As a follow up I tried a couple of other things: >> - installed CentOS-7 and oVirt 4.3.10 using HCI and same problem >> (the previous install of 4.3 was a upgraded version. Don't know the >> start versie) >> - did some testing with copying large files into the engine gluster >> volume through /rhev/datacenter using 'cp' and no problems >> - used qemu-img convert with the engine gluster volume as destination >> --> problems >> - had a good look through lots of logfiles and stumbled across an error >> about missing shard which aligned with qemu-img errors >> - turned features.shard off on the volume and restarted the volume >> - reran the tests with qemu-img --> no problems any more. >> - reinstalled Centos8.2 + oVirt-4.0, turned off sharding before >> starting >> the engine install >> --> no problems installing, no problems importing, no problems starting >> vms, sofar >> >> I need to install another server tomorrow, so I'll do that with >> sharding >> enabled and see if it crashes too and then get the logs some place >> safe. >> >> Regards, >> >> Joop >> >> ___ >> 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/6TNJYNVBJWCB2NXDYMBYVNDQUWKBJJYU/ ___ 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/7BPONTX2FDDNBMUK3ZBU3ZFK5DTESGYF/
[ovirt-users] Re: cant edit ISO domain in any way
I need to change everything. the server name the mount path (and eventually, the contents ;) - Original Message - From: "Strahil Nikolov" To: "users" , "Philip Brown" Sent: Tuesday, June 16, 2020 4:37:30 PM Subject: Re: [ovirt-users] cant edit ISO domain in any way What do you want to change ? На 17 юни 2020 г. 0:36:49 GMT+03:00, Philip Brown написа: >oVirt 4.3: Okay, I found documentation that I cant have more than one >"ISO" type storage domain. >I can kinda understand that. > >But, I cant even edit or delete the existing one? >Even when logged in to the oVirt GUI as admin@internal? > >Is this some kind of bug or something? >___ >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/DXSU32CVV6AQJNKUV7JL7TW2NRAZDMLG/ ___ 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/DCA363RSLNDPT44F3JHQQO7GZJVHWM7N/
[ovirt-users] Re: EXTERNAL - Re: Update to Ovirt 4.3.10-4-1 causes XFS issue
Thank you for the response! I tried to do another upgrade again on the ovirt manager and can confirm that it is now in the supposedly fixed version of the kernel. However, when I try to update the hosts using the prescribed gui style method they do report back as no updates available. Should I force an update on the kernel on the hosts or is this not advised? Thanks Chaz Chaz Vidal | ICT Infrastructure | Tel: +61-8-8128-4397 | Mob: +61-492-874-982 | chaz.vi...@sahmri.com -Original Message- From: Derek Atkins Sent: Tuesday, 16 June 2020 11:02 PM To: Chaz Vidal Cc: users@ovirt.org Subject: EXTERNAL - [ovirt-users] Re: Update to Ovirt 4.3.10-4-1 causes XFS issue [External email: Use caution with links and attachments] Hi, "Chaz Vidal" writes: > Hi All > I think I have come across this bug: > > https://access.redhat.com/solutions/5075561 > > Updating Ovirt to 4.3.10 shows that the kernel installed on the hosts > is the version that has the issue: > > 3.10.0-1127.8.2.el7.x86_64 > > The RedHat article suggests updating to kernel-3.10.0-1127.10.1.el7 > but running engine-upgrade-check now shows no updates available from > my engine manager. > > Is this something I can fix myself or would the updated kernel be available? > > Appreciate the advice as new to Ovirt. Normally I would point the > hosts to the new kernel but I think it should be updated through Ovirt > manager, correct? On the engine my update method is the following: engine-setup yum upgrade engine-setup reboot So basically run engine-setup which will update the Ovirt packages, then you can "yum upgrade" to upgrade the base system, then re-run engine-setup just to be sure nothing broke. Then you can reboot into the new kernel. The reason I do this is that engine-setup wont upgrade the full OS (including kernel) -- it will only update the ovirt packages. Hope this helps, > Thanks! > Chaz -derek -- Derek Atkins 617-623-3745 de...@ihtfp.com www.ihtfp.com Computer and Internet Security Consultant ___ 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/JLYO3LZG6QYKEEWDTF5ZSOWU7JXP3CZQ/ ___ 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/QANBSL7IYX7SY7DHWDZM2F4J5FNHEKRT/
[ovirt-users] Re: Weird problem starting VMs in oVirt-4.4
Hey Nir, in ovirt 4.3.something the default behaviour for Gluster changed from thin to fully allocated. My guess is that the shard xlator cannot catch up with the I/O. Do you think that I should file a RFE to change the shard size ? As far as I know RedHat support only 512MB shard size, while gluster's default is only 64MB. Best Rregards, Strahil Nikolov На 16 юни 2020 г. 23:22:53 GMT+03:00, Nir Soffer написа: >On Tue, Jun 16, 2020 at 11:01 PM Joop wrote: >> >> On 16-6-2020 19:44, Strahil Nikolov wrote: >> > Hey Joop, >> > >> > are you using fully allocated qcow2 images ? >> > >> > Best Regards, >> > Strahil Nikolov >> > >> I noticed that when I use import VM from an Export domain I see that >it >> sometimes uses preallocated and sometimes thin-provisioned for the >disk(s). >> Don't know why and I don't think there is a pattern. > >Maybe the system selects a different storage domain? On block storage >the >default is preallocated, but on file based storage the default is thin. > >> Old VMs from 3.3 or >> new ones from 4.2/3, its mixed. >> I almost always use thin-provisioned but one or two could have been >> preallocated by accident. >> >> How do I check? > >If the question was about creating images with: > >qemu-img create -f qcow2 -o preallocation=metadata ... > >Then it is easy, ovirt does not create such images. > >> Joop >> >> > >> > На 16 юни 2020 г. 20:23:17 GMT+03:00, Joop >написа: >> >> On 3-6-2020 14:58, Joop wrote: >> >>> Hi All, >> >>> >> >>> Just had a rather new experience in that starting a VM worked but >the >> >>> kernel entered grub2 rescue console due to the fact that >something >> >> was >> >>> wrong with its virtio-scsi disk. >> >>> The message is Booting from Hard Disk >> >>> error: ../../grub-core/kern/dl.c:266:invalid arch-independent ELF >> >> maginc. >> >>> entering rescue mode... >> >>> >> >>> Doing a CTRL-ALT-Del through the spice console let the VM boot >> >>> correctly. Shutting it down and repeating the procedure I get a >disk >> >>> problem everytime. Weird thing is if I activate the BootMenu and >then >> >>> straight away start the VM all is OK. >> >>> I don't see any ERROR messages in either vdsm.log, engine.log >> >>> >> >>> If I would have to guess it looks like the disk image isn't >connected >> >>> yet when the VM boots but thats weird isn't it? >> >>> >> >> As a follow up I tried a couple of other things: >> >> - installed CentOS-7 and oVirt 4.3.10 using HCI and same problem >> >> (the previous install of 4.3 was a upgraded version. Don't know >the >> >> start versie) >> >> - did some testing with copying large files into the engine >gluster >> >> volume through /rhev/datacenter using 'cp' and no problems >> >> - used qemu-img convert with the engine gluster volume as >destination >> >> --> problems >> >> - had a good look through lots of logfiles and stumbled across an >error >> >> about missing shard which aligned with qemu-img errors >> >> - turned features.shard off on the volume and restarted the volume >> >> - reran the tests with qemu-img --> no problems any more. >> >> - reinstalled Centos8.2 + oVirt-4.0, turned off sharding before >> >> starting >> >> the engine install >> >> --> no problems installing, no problems importing, no problems >starting >> >> vms, sofar >> >> >> >> I need to install another server tomorrow, so I'll do that with >> >> sharding >> >> enabled and see if it crashes too and then get the logs some place >> >> safe. >> >> >> >> Regards, >> >> >> >> Joop >> >> >> >> ___ >> >> 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/6TNJYNVBJWCB2NXDYMBYVNDQUWKBJJYU/ >> ___ >> 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/7BPONTX2FDDNBMUK3ZBU3ZFK5DTESGYF/ >___ >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/NARCCR7LYDFKLTQDSD27JNLQW3FML6S2/ ___ 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
[ovirt-users] Re: cant edit ISO domain in any way
What do you want to change ? На 17 юни 2020 г. 0:36:49 GMT+03:00, Philip Brown написа: >oVirt 4.3: Okay, I found documentation that I cant have more than one >"ISO" type storage domain. >I can kinda understand that. > >But, I cant even edit or delete the existing one? >Even when logged in to the oVirt GUI as admin@internal? > >Is this some kind of bug or something? >___ >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/DXSU32CVV6AQJNKUV7JL7TW2NRAZDMLG/ ___ 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/2KAGPHN3HKP4FMNSZNGOEY4GF6OKJNNF/
[ovirt-users] Information requested on oVirt + RDO/OpenStack
I am hoping to try out adding RDO to oVirt after things with CentOS 8.2 settle down. I've done deployments of RDO on KVM before without any issues (TripleO Quickstart), but this would be my first time trying it on oVirt. Since oVirt recently updated to the openstack-java 3.2.9 packages, is there a specific version of OpenStack (Train or Ussuri) that runs on CentOS 8.x that I need? Are there any issues with the fact that oVirt already uses and/or provides some OpenStack services? Does the fact that OpenStack deployments are now more "containerized" present any issues I should be aware of? Are there initiatives for further convergence between oVirt, RDO/OpenStack and OKD/OCP that are changing this space where it would make sense to follow and/or participate in those efforts? I'm starting out with oVirt to get an understanding of the capabilities that it brings to the table, but interested in the convergence of the other technologies that would benefit from having oVirt as, or a part of, the foundation. Best Regards, Glenn ___ 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/5MPEU357TFRCJBM5U2VO4KXXCKCHJN56/
[ovirt-users] Re: help: renamed master volume
Okay, since you asked: (note: this is in node 4.3.10. but hosted-engine is 4.2 I'd LIKE to upgrade it. but the upgrade process is broken. thats a whole nuther story, aobut how postgresql10 doesnt show up even though its required for yum update 'ovirt*setup' :-/) 1. go to individual node UI. 2. Click on Storage 3. Look at the right-sdie aera for "Volume Groups". click on the one that is for your master data volume 4. Click on the Rename button on the top right. Pick something sensible 5. wait a while, and eventually your cluster logs will freak out. Happily for me, since our VMs are very lightly loaded, this did not immediately cause a crash. But the cluster freaked out.. engine log spewed those errors after a while.. and in the cluster(engine) UI, it eventually showed Storage->Domains as offline. (well it shows the master as offline, and it didnt even know about the other ones any more, until I renamed it back) - Original Message - From: "Nir Soffer" To: "Philip Brown" Cc: "users" Sent: Tuesday, June 16, 2020 10:56:45 AM Subject: Re: [ovirt-users] Re: help: renamed master volume On Tue, Jun 16, 2020 at 8:31 PM Philip Brown wrote: > > nevermind.. found the answer myself thank goodness. > > had to rename the volume back to the value of the msdUUID. not the spUUID, > which I already tried. > > If its fatal to rename that volume... > would be nice to have it lockedout or something? Did you rename the volume from within oVirt UI? Can you give clear reproduction instructions, how to break your storage domain by renaming a volume? Nir > - Original Message - > From: "Philip Brown" > To: "users" > Sent: Tuesday, June 16, 2020 10:21:12 AM > Subject: help: renamed master volume > > Im pretty new to ovirt. Trying to upgrade an old install from 4.1 to 4.3 > > on the way, I browsed into the Storage area, in one of the nodes. > > Noticed under the "Volume groups", area that the volumes were named after > some loong ID string. > > Saw there was a "rename" button. > figured it would be just like renaming a VM. thigns would just get auto > adjusted. > > but after I renamed to something in english, the cluster is freaking out, > > "cant find master domain: u'spUUID=xxx, msdUUID=xxx' " > > and under Storage: Storage DOmains, the Data(Master) is down. > How can I recover from this ASAP? :-( > ___ > 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/ZTDLZ7W4TQAON7U27IWJSOLYJBMKAB3V/ ___ 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/TVFA2Z6CFJ3ESQFQJMM4A43TSDI2RIVQ/
[ovirt-users] Re: Weird problem starting VMs in oVirt-4.4
On Mon, Jun 8, 2020 at 3:10 PM Joop wrote: > > On 3-6-2020 14:58, Joop wrote: > > Hi All, > > > > Just had a rather new experience in that starting a VM worked but the > > kernel entered grub2 rescue console due to the fact that something was > > wrong with its virtio-scsi disk. > > The message is Booting from Hard Disk > > error: ../../grub-core/kern/dl.c:266:invalid arch-independent ELF maginc. > > entering rescue mode... > > > > Doing a CTRL-ALT-Del through the spice console let the VM boot > > correctly. Shutting it down and repeating the procedure I get a disk > > problem everytime. Weird thing is if I activate the BootMenu and then > > straight away start the VM all is OK. > > I don't see any ERROR messages in either vdsm.log, engine.log > > > > If I would have to guess it looks like the disk image isn't connected > > yet when the VM boots but thats weird isn't it? > > > > > As an update to this: > Just had the same problem with a Windows VM but more importantly also > with HostedEngine itself. > On the host did: > hosted-engine --set-maintenance --mode=global > hosted-engine --vm-shutdown > > Stopped all oVirt related services, cleared all oVirt related logs from > /var/log/..., restarted the host, ran hosted-engine --set-maintenance > --mode=none > Watched /var/spool/mail/root to see the engine coming up. It went to > starting but never came into the Up status. > Set a password and used vncviewer to see the console, see attached > screenschot. The screenshot "engine.png" show gluster bug we discovered a few weeks ago: https://bugzilla.redhat.com/1823423 Until you get a fixed version, this may fix the issues: # gluster volume set engine performance.stat-prefetch off See https://bugzilla.redhat.com/show_bug.cgi?id=1823423#c55. Krutica, can this bug affect upstream gluster? Joop, please share the gluster version in your setup. > hosted-engine --vm-poweroff, and tried again, same result > hosted-engine --vm-start, works > Let it startup and then shut it down after enabling maintenance mode. > Copied, hopefully, all relevant logs and attached them. > > A sosreport is also available, size 12Mb. I can provide a download link > if needed. > > Hopefully someone is able to spot what is going wrong. > > Regards, > > Joop > > > ___ > 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/VJ7ZOXHCOKBNNUV4KF5OS7TKU2TXNN3I/ ___ 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/WTB3QIIR72SSPJ53C4HFB7UXNKSTRR4E/
[ovirt-users] cant edit ISO domain in any way
oVirt 4.3: Okay, I found documentation that I cant have more than one "ISO" type storage domain. I can kinda understand that. But, I cant even edit or delete the existing one? Even when logged in to the oVirt GUI as admin@internal? Is this some kind of bug or something? ___ 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/DXSU32CVV6AQJNKUV7JL7TW2NRAZDMLG/
