- Users - oVirt List Archives

NFS Mount on EMC VNXe3200 / User - Group 36:36 / Permission issue
by jeanbaptiste.coupiac＠nfrance.com 11 Jul '18

11 Jul '18

Hello, I try to mount an NFS Data share from a EMC VNXe3200 export. Unfortunately, NFS share cannot be mount, there is permission error. (Indeed, after the same issue on another NFS ISO repo, I've change exported directory user/group to 36:36, and O-Virt NFS mount was great). So, I think issue with my VNXe3200 is regarding UID / GID owner on VNXe3200 side. After webex with EMC support, change owner / permission on VNXe side seems not possible / supported. Can I mount the NFS share with some options to avoid vdsm:kvm mounting issue ? Can I force mount with root ? Regards, Jean-Baptiste COUPIAC

1 0

Engine Error
by Sakhi Hadebe 11 Jul '18

11 Jul '18

Hi, I have just re-installed centOS 7 in 3 servers and have configured gluster volumes following this documentation: https://www.ovirt.org/blog/2016/03/up-and-running-with-ovirt-3-6/, But I have installed http://resources.ovirt.org/pub/yum-repo/ovirt-release42.rpm package. Hosted-engine --deploy is failing with this error: "rhel7", "--virt-type", "kvm", "--memory", "16384", "--vcpus", "4", "--network", "network=default,mac=00:16:3e:09:5e:5d,model=virtio", "--disk", "/var/tmp/localvm0nnJH9/images/eacac30d-0304-4c77-8753-6965e4b8c2e7/d494577e-027a-4209-895b-6132e6fc6b9a", "--import", "--disk", "path=/var/tmp/localvm0nnJH9/seed.iso,device=cdrom", "--noautoconsole", "--rng", "/dev/random", "--graphics", "vnc", "--video", "vga", "--sound", "none", "--controller", "usb,model=none", "--memballoon", "none", "--boot", "hd,menu=off", "--clock", "kvmclock_present=yes"], "delta": "0:00:00.979003", "end": "2018-07-10 17:55:11.308555", "msg": "non-zero return code", "rc": 1, "start": "2018-07-10 17:55:10.329552", "stderr": "ERROR unsupported configuration: CPU mode 'custom' for x86_64 kvm domain on x86_64 host is not supported by hypervisor\nDomain installation does not appear to have been successful.\nIf it was, you can restart your domain by running:\n virsh --connect qemu:///system start HostedEngineLocal\notherwise, please restart your installation.", "stderr_lines": ["ERROR unsupported configuration: CPU mode 'custom' for x86_64 kvm domain on x86_64 host is not supported by hypervisor", "Domain installation does not appear to have been successful.", "If it was, you can restart your domain by running:", " virsh --connect qemu:///system start HostedEngineLocal", "otherwise, please restart your installation."], "stdout": "\nStarting install...", "stdout_lines": ["", "Starting install..."]} I added the root user to the kvm group. but it ddn't work. Can you please help me out. I have been struggling to deploy the hosted engine. -- Regards, Sakhi

2 3

PXE LOCALBOOT issue
by Michael Deffenbaugh 11 Jul '18

11 Jul '18

Hey all, Provisioning a host with Foreman 1.17.1/Katello 3.6. The host kickstarts fine but when it goes to reboot, iPXE fails to load the local disk when the Foreman local boot kickstart menu ( https://github.com/theforeman/community-templates/blob/develop/provisioning…, line 4-10) sends the command "LOCALBOOT 0". It simply fails and says "No more network devices. No bootable device." Is this a bug in iPXE? Any input would be greatly appreciated! Regards, Mike

1 1

upload disk using python sdk
by 董青龙 11 Jul '18

11 Jul '18

Hi all, I want to upload an disk using python sdk instead of web. Which class should I use? I could not find a "upload" method in "class Disk" an "class Disks" in "brokers.py" Anyone can help? Thanks!

2 1

Re: hosted-engine install fails (was: Engine Error)
by Yedidyah Bar David 11 Jul '18

11 Jul '18

On Tue, Jul 10, 2018 at 11:32 PM, Sakhi Hadebe <sakhi(a)sanren.ac.za> wrote: > Hi, > > I did not select any CPU architecture. It doenst gove me the option to > select one. It only states the number of virtual CPUs and the memory for > the engine VM. > > Looking at the documentation of installing ovirt-release36.rpm....it does > allow you to select te CPU, but not when installing ovirt-release42.rpm > > On Tuesday, July 10, 2018, Alastair Neil <ajneil.tech(a)gmail.com> wrote: > >> what did you select as your CPU architecture when you created the >> cluster? It looks like the VM is trying to use a CPU type of "Custom", how >> many nodes in your cluster? I suggest you specify the lowest common >> denominator of CPU architecture (e.g. Sandybridge) of the nodes as the CPU >> architecture of the cluster.. >> >> On Tue, 10 Jul 2018 at 12:01, Sakhi Hadebe <sakhi(a)sanren.ac.za> wrote: >> >>> Hi, >>> >>> I have just re-installed centOS 7 in 3 servers and have configured >>> gluster volumes following this documentation: >>> https://www.ovirt.org/blog/2016/03/up-and-running-with-ovirt-3-6/, But >>> I have installed >>> >>> http://resources.ovirt.org/pub/yum-repo/ovirt-release42.rpm >>> >>> package. >>> Hosted-engine --deploy is failing with this error: >>> >>> "rhel7", "--virt-type", "kvm", "--memory", "16384", "--vcpus", "4", >>> "--network", "network=default,mac=00:16:3e:09:5e:5d,model=virtio", >>> "--disk", "/var/tmp/localvm0nnJH9/images/eacac30d-0304-4c77-8753- >>> 6965e4b8c2e7/d494577e-027a-4209-895b-6132e6fc6b9a", "--import", >>> "--disk", "path=/var/tmp/localvm0nnJH9/seed.iso,device=cdrom", >>> "--noautoconsole", "--rng", "/dev/random", "--graphics", "vnc", "--video", >>> "vga", "--sound", "none", "--controller", "usb,model=none", "--memballoon", >>> "none", "--boot", "hd,menu=off", "--clock", "kvmclock_present=yes"], >>> "delta": "0:00:00.979003", "end": "2018-07-10 17:55:11.308555", "msg": >>> "non-zero return code", "rc": 1, "start": "2018-07-10 17:55:10.329552", >>> "stderr": "ERROR unsupported configuration: CPU mode 'custom' for x86_64 >>> kvm domain on x86_64 host is not supported by hypervisor\nDomain >>> installation does not appear to have been successful.\nIf it was, you can >>> restart your domain by running:\n virsh --connect qemu:///system start >>> HostedEngineLocal\notherwise, please restart your installation.", >>> "stderr_lines": ["ERROR unsupported configuration: CPU mode 'custom' for >>> x86_64 kvm domain on x86_64 host is not supported by hypervisor", "Domain >>> installation does not appear to have been successful.", "If it was, you can >>> restart your domain by running:", " virsh --connect qemu:///system start >>> HostedEngineLocal", "otherwise, please restart your installation."], >>> "stdout": "\nStarting install...", "stdout_lines": ["", "Starting >>> install..."]} >>> >> This seems to be in the phase where we create a local vm for the engine. We do this with plain virt-install, nothing fancy. Searching the net for "unsupported configuration: CPU mode 'custom'" finds other relevant reports, you might want to check them. You can see the command in bootstrap_local_vm.yml . Please check/share versions of relevant packages (libvirt*, qemu*, etc) and relevant logs (libvirt). Also updating the subject line and adding Simone. Best regards, -- Didi

1 0

Unable to start VM
by Alex K 10 Jul '18

10 Jul '18

Hi all, I did a routine maintenance today (updating the hosts) to ovirt cluster (4.2) and I have one VM that was complaining about an invalid snapshot. After shutdown of VM the VM is not able to start again, giving the error: VM Gitlab is down with error. Exit message: Bad volume specification {'serial': 'b6af2856-a164-484a-afe5-9836bbdd14e8', 'index': 0, 'iface': 'virtio', 'apparentsize': '51838976', 'specParams': {}, 'cache': 'none', 'imageID': 'b6af2856-a164-484a-afe5-9836bbdd14e8', 'truesize': '52011008', 'type': 'disk', 'domainID': '142bbde6-ef9d-4a52-b9da-2de533c1f1bd', 'reqsize': '0', 'format': 'cow', 'poolID': '00000001-0001-0001-0001-000000000311', 'device': 'disk', 'path': '/rhev/data-center/00000001-0001-0001-0001-000000000311/142bbde6-ef9d-4a52-b9da-2de533c1f1bd/images/b6af2856-a164-484a-afe5-9836bbdd14e8/f3125f62-c909-472f-919c-844e0b8c156d', 'propagateErrors': 'off', 'name': 'vda', 'bootOrder': '1', 'volumeID': 'f3125f62-c909-472f-919c-844e0b8c156d', 'diskType': 'file', 'alias': 'ua-b6af2856-a164-484a-afe5-9836bbdd14e8', 'discard': False}. I see also the following error: VDSM command CopyImageVDS failed: Image is not a legal chain: (u'b6af2856-a164-484a-afe5-9836bbdd14e8',) Seems as a corrupt VM disk? The VM had 3 snapshots. I was able to delete one from GUI then am not able to delete the other two as the task fails. Generally I am not allowed to clone, export or do sth to the VM. Have you encountered sth similar. Any advice? Thanx, Alex

1 0

Network Setup Error
by Sakhi Hadebe 10 Jul '18

10 Jul '18

Hi, I have successfully installe oVirtNode 4.2 and gluster storage on CentOS 7. I am now struggling to deploy the hosted engine. [ ERROR ] fatal: [localhost]: FAILED! => {"changed": false, "msg": "Unable to create bridge virbr0: Package not installed"} [ ERROR ] Failed to execute stage 'Closing up': Failed executing ansible-playbook What is the right package for bridging in centOS 7? -- Regards, Sakhi Hadebe

2 2

User permission. All user can access (start, shutdown) all vm in User/VM portal
by florentl 10 Jul '18

10 Jul '18

Hello, There is something I don't understand in permissions. I'm using Ovirt 4.2.3.5-1. I created a user : - ovirt-aaa-jdbc-tool user add etudiant2 --attribute=firstName=Etudiant2 --attribute=lastName=Etudiant2-Lastname - ovirt-aaa-jdbc-tool user password-reset etudiant2 --password-valid-to="2025-01-01 10:30:00Z" On the Administration Portal I gave him (etudiant2) the permission UserVmManager on only one VM and nothing else. But when he logs in the VM Portal he can view, start, stop all the VM. I think it's because all users are member of the group Everyone and this group has by default the UserRole. And in my config (the default/install config) the UserRole can do Basic Operation an VM. Moreover the UserRole is given to the group Everyone on all VM I created, and I can't remove this permission (Remove button is greyed). How can I make a VM "private", only visible by one user ? Thanks in advance, Florent

3 5

OVN ACLs
by Niyazi Elvan 10 Jul '18

10 Jul '18

Hi All, I have started testing oVirt 4.2 and focused on OVN recently. I was wondering whether there is a plan to manage L2->L7 ACLs through oVirt web ui. If not, how could it be possible to manage ACLs except command line tools ? Using opendaylight ?? All the best ! Niyazi -- Niyazi Elvan

3 3

Device Mapper Timeout when using Gluster Snapshots
by hsahmed＠gmail.com 09 Jul '18

09 Jul '18

I am facing this trouble since version 4.1 up to the latest 4.2.4, once we enable gluster snapshots and accumulate some snapshots (as few as 15 snapshots per server) we start having trouble booting the server. The server enters emergency shell upon boot after timing out waiting for snapshot devices. Waiting a few minutes and pressing Control-D then boots the server normally. In case of very large number of snapshots (600+) it can take days before the sever will boot. Attaching journal log, let me know if you need any other logs. Details of the setup: 3 node hyperconverged oVirt setup (64GB RAM, 8-Core E5 Xeon) oVirt 4.2.4 oVirt Node 4.2.4 10Gb Interface Thanks, Hesham S. Ahmed

4 7