December 2019 - Users - oVirt List Archives

unable to connect to the graphic server console.vv
by Pradeep Danthi 11 Dec '19

11 Dec '19

Dear Ovirt Team, Kindly help with this issues that I am facing in my Redhat Virtualization servers. I am unable to access my VM through console, I am getting this error when I right click and try connecting console. My observation is, this is happening after renewing the self-signed ssl certificate in all the nodes as nodes were non responsive before renewing the ssl lcertificate. Kindly help as we are unable to access the VMs through console (console.vv) Regards, Pradip 9900056579 ________________________________ This email was scanned by Bitdefender

1 0

Re: OVN communications between hosts
by Strahil 11 Dec '19

11 Dec '19

Hi Pavel, Can you explain how did you find the issue. I'm new in OVN and I experience the same symptoms . I'm not sure what will be the best approach to start cleanly with OVN. Best Regards, Strahil NikolovOn Dec 10, 2019 19:06, Pavel Nakonechnyi <pavel(a)gremwell.com> wrote: > > Hi Pavel Nakonechnyi, > > > > > However, if such VMs are on different hosts, then no packets are received on both VMs. > > > > Could you please suggest me a way to properly debug and fix this problem? I would like to be able to distribute several VMs connected to the single virtual network across hosts. > > > > It appears that the problem was (as usual) with my setup which is a bit messy as it was based on experimental environment. The issues was triggered by changing the IP address of one of the hosts. I actually just added an alias to ovrtmgmnt interface and then changed the IP via oVirt engine... > > Anyway, command `ovs-vsctl list Interface` showed that one of the switch peers was still referenced by the old, unused IP address. The easiest way to fix it for me was to re-add the host to cluster. After that cross-host communication between VMs started to work properly. > > > _______________________________________________ > Users mailing list -- users(a)ovirt.org > To unsubscribe send an email to users-leave(a)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/XC6UEXHBEEX2I…

2 1

Re: OVN communications between hosts
by Strahil 10 Dec '19

10 Dec '19

Hi All, It seems that I have several devices listed in 'ovs-vsctl list interface' despite removing all networks except ovirtmgmt. Can someone tell me which devices I should leave (so I can remove the rest) ? Thanks in advance. Best Regards, Strahil Nikolov On Dec 10, 2019 21:50, Strahil <hunter86_bg(a)yahoo.com> wrote: > > Hi Pavel, > > Can you explain how did you find the issue. > > I'm new in OVN and I experience the same symptoms . > > I'm not sure what will be the best approach to start cleanly with OVN. > > Best Regards, > Strahil NikolovOn Dec 10, 2019 19:06, Pavel Nakonechnyi <pavel(a)gremwell.com> wrote: > > > > Hi Pavel Nakonechnyi, > > > > > > > > However, if such VMs are on different hosts, then no packets are received on both VMs. > > > > > > Could you please suggest me a way to properly debug and fix this problem? I would like to be able to distribute several VMs connected to the single virtual network across hosts. > > > > > > > It appears that the problem was (as usual) with my setup which is a bit messy as it was based on experimental environment. The issues was triggered by changing the IP address of one of the hosts. I actually just added an alias to ovrtmgmnt interface and then changed the IP via oVirt engine... > > > > Anyway, command `ovs-vsctl list Interface` showed that one of the switch peers was still referenced by the old, unused IP address. The easiest way to fix it for me was to re-add the host to cluster. After that cross-host communication between VMs started to work properly. > > > > > > _______________________________________________ > > Users mailing list -- users(a)ovirt.org > > To unsubscribe send an email to users-leave(a)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/XC6UEXHBEEX2I…

1 0

ovirtsdk4 error
by jeremy_tourville＠hotmail.com 10 Dec '19

10 Dec '19

I have a server which runs a project from Github called SecGen. SecGen uses Vagrant to provision VMs from templates. When I go to my project folder and run vagrant up I get an error. user@localhost:~/bin/SecGen/projects/SecGen20191207_183811$ vagrant up Bringing machine 'escalation' up with 'ovirt4' provider... ==> escalation: Creating VM with the following settings... ==> escalation: -- Name: SecGen-default-scenario-escalation ==> escalation: -- Cluster: Default ==> escalation: -- Template: Vcentos77 ==> escalation: -- Console Type: spice ==> escalation: -- Memory: ==> escalation: ---- Memory: 512 MB ==> escalation: ---- Maximum: 512 MB ==> escalation: ---- Guaranteed: 512 MB ==> escalation: -- Cpu: ==> escalation: ---- Cores: 1 ==> escalation: ---- Sockets: 1 ==> escalation: ---- Threads: 1 ==> escalation: -- Cloud-Init: false ==> escalation: An error occured. Recovering.. ==> escalation: VM is not created. Please run `vagrant up` first. /home/user/.vagrant.d/gems/2.4.9/gems/ovirt-engine-sdk-4.0.12/lib/ovirtsdk4/reader.rb:272:in `read': Can't find a reader for tag 'html' (OvirtSDK4::Error) from /home/user/.vagrant.d/gems/2.4.9/gems/ovirt-engine-sdk-4.0.12/lib/ovirtsdk4/service.rb:66:in `check_fault' from /home/user/.vagrant.d/gems/2.4.9/gems/ovirt-engine-sdk-4.0.12/lib/ovirtsdk4/services.rb:35570:in `add' from /home/user/.vagrant.d/gems/2.4.9/gems/vagrant-ovirt4-1.2.2/lib/vagrant-ovirt4/action/create_vm.rb:67:in `call' from /opt/vagrant/embedded/gems/2.2.6/gems/vagrant-2.2.6/lib/vagrant/action/warden.rb:50:in `call' from /opt/vagrant/embedded/gems/2.2.6/gems/vagrant-2.2.6/lib/vagrant/action/builtin/before_trigger.rb:23:in `call' from /opt/vagrant/embedded/gems/2.2.6/gems/vagrant-2.2.6/lib/vagrant/action/warden.rb:50:in `call' from /opt/vagrant/embedded/gems/2.2.6/gems/vagrant-2.2.6/lib/vagrant/action/builtin/after_trigger.rb:26:in `call' from /opt/vagrant/embedded/gems/2.2.6/gems/vagrant-2.2.6/lib/vagrant/action/warden.rb:50:in `call' from /home/user/.vagrant.d/gems/2.4.9/gems/vagrant-ovirt4-1.2.2/lib/vagrant-ovirt4/action/set_name_of_domain.rb:17:in `call' from /opt/vagrant/embedded/gems/2.2.6/gems/vagrant-2.2.6/lib/vagrant/action/warden.rb:50:in `call' from /opt/vagrant/embedded/gems/2.2.6/gems/vagrant-2.2.6/lib/vagrant/action/builtin/before_trigger.rb:23:in `call' from /opt/vagrant/embedded/gems/2.2.6/gems/vagrant-2.2.6/lib/vagrant/action/warden.rb:50:in `call' from /opt/vagrant/embedded/gems/2.2.6/gems/vagrant-2.2.6/lib/vagrant/action/warden.rb:121:in `block in finalize_action' from /opt/vagrant/embedded/gems/2.2.6/gems/vagrant-2.2.6/lib/vagrant/action/warden.rb:50:in `call' from /opt/vagrant/embedded/gems/2.2.6/gems/vagrant-2.2.6/lib/vagrant/action/builder.rb:116:in `call' from /opt/vagrant/embedded/gems/2.2.6/gems/vagrant-2.2.6/lib/vagrant/action/runner.rb:102:in `block in run' from /opt/vagrant/embedded/gems/2.2.6/gems/vagrant-2.2.6/lib/vagrant/util/busy.rb:19:in `busy' from /opt/vagrant/embedded/gems/2.2.6/gems/vagrant-2.2.6/lib/vagrant/action/runner.rb:102:in `run' from /opt/vagrant/embedded/gems/2.2.6/gems/vagrant-2.2.6/lib/vagrant/action/builtin/call.rb:53:in `call' from /opt/vagrant/embedded/gems/2.2.6/gems/vagrant-2.2.6/lib/vagrant/action/warden.rb:50:in `call' from /opt/vagrant/embedded/gems/2.2.6/gems/vagrant-2.2.6/lib/vagrant/action/builtin/before_trigger.rb:23:in `call' from /opt/vagrant/embedded/gems/2.2.6/gems/vagrant-2.2.6/lib/vagrant/action/warden.rb:50:in `call' from /opt/vagrant/embedded/gems/2.2.6/gems/vagrant-2.2.6/lib/vagrant/action/builtin/after_trigger.rb:26:in `call' from /opt/vagrant/embedded/gems/2.2.6/gems/vagrant-2.2.6/lib/vagrant/action/warden.rb:50:in `call' from /home/user/.vagrant.d/gems/2.4.9/gems/vagrant-ovirt4-1.2.2/lib/vagrant-ovirt4/action/connect_ovirt.rb:31:in `call' from /opt/vagrant/embedded/gems/2.2.6/gems/vagrant-2.2.6/lib/vagrant/action/warden.rb:50:in `call' from /opt/vagrant/embedded/gems/2.2.6/gems/vagrant-2.2.6/lib/vagrant/action/builtin/before_trigger.rb:23:in `call' from /opt/vagrant/embedded/gems/2.2.6/gems/vagrant-2.2.6/lib/vagrant/action/warden.rb:50:in `call' from /opt/vagrant/embedded/gems/2.2.6/gems/vagrant-2.2.6/lib/vagrant/action/builtin/after_trigger.rb:26:in `call' from /opt/vagrant/embedded/gems/2.2.6/gems/vagrant-2.2.6/lib/vagrant/action/warden.rb:50:in `call' from /opt/vagrant/embedded/gems/2.2.6/gems/vagrant-2.2.6/lib/vagrant/action/builtin/config_validate.rb:25:in `call' from /opt/vagrant/embedded/gems/2.2.6/gems/vagrant-2.2.6/lib/vagrant/action/warden.rb:50:in `call' from /opt/vagrant/embedded/gems/2.2.6/gems/vagrant-2.2.6/lib/vagrant/action/builtin/before_trigger.rb:23:in `call' from /opt/vagrant/embedded/gems/2.2.6/gems/vagrant-2.2.6/lib/vagrant/action/warden.rb:50:in `call' from /opt/vagrant/embedded/gems/2.2.6/gems/vagrant-2.2.6/lib/vagrant/action/builder.rb:116:in `call' from /opt/vagrant/embedded/gems/2.2.6/gems/vagrant-2.2.6/lib/vagrant/action/runner.rb:102:in `block in run' from /opt/vagrant/embedded/gems/2.2.6/gems/vagrant-2.2.6/lib/vagrant/util/busy.rb:19:in `busy' from /opt/vagrant/embedded/gems/2.2.6/gems/vagrant-2.2.6/lib/vagrant/action/runner.rb:102:in `run' from /opt/vagrant/embedded/gems/2.2.6/gems/vagrant-2.2.6/lib/vagrant/machine.rb:238:in `action_raw' from /opt/vagrant/embedded/gems/2.2.6/gems/vagrant-2.2.6/lib/vagrant/machine.rb:209:in `block in action' from /opt/vagrant/embedded/gems/2.2.6/gems/vagrant-2.2.6/lib/vagrant/environment.rb:613:in `lock' from /opt/vagrant/embedded/gems/2.2.6/gems/vagrant-2.2.6/lib/vagrant/machine.rb:195:in `call' from /opt/vagrant/embedded/gems/2.2.6/gems/vagrant-2.2.6/lib/vagrant/machine.rb:195:in `action' from /opt/vagrant/embedded/gems/2.2.6/gems/vagrant-2.2.6/lib/vagrant/batch_action.rb:86:in `block (2 levels) in run' Here is the top part of my Vagrantfile. # -*- mode: ruby -*- # vi: set ft=ruby : # This file was generated by SecGen # 2019-12-07 18:38:19 +0000 # Based on scenarios/default_scenario.xml VAGRANTFILE_API_VERSION = "2" Vagrant.configure(VAGRANTFILE_API_VERSION) do |config| config.vm.define "escalation" do |escalation| #oVirt provider begin escalation.vm.provider :ovirt4 do |ovirt| ovirt.username = 'admin@internal' ovirt.password = 'admin' ovirt.url = 'https://engine.cyber-range.lan/ovirt-engine/' ovirt.cluster = 'Default' ovirt.template = 'Vcentos77' ovirt.memory_size = '512 MB' ovirt.console = 'spice' # ovirt.filtered_api = true ovirt.insecure = true ovirt.debug = true end # oVirt provider end Can anyone tell me what is wrong?

2 2

OVN communications between hosts
by Pavel Nakonechnyi 10 Dec '19

10 Dec '19

Hi all, I have a working setup of oVirt (currently 4.3.7) as self-hosted engine consisting of three virtualization hosts. Each of them has several VMs with public IP addresses which work fine. The problem is with virtual networks created on "ovirt-provider-ovn". I can create a new network with the corresponding vNIC and attach two VMs to this vNIC. If both VMs are on the same host, virtual network works, VMs can exchange packets. However, if such VMs are on different hosts, then no packets are received on both VMs. With tcpdump I see traffic going from sender VM over "ovirtmgmnt" interface. The traffic successfully leaves one host and arrives to another, so I conclude that firewall is configured properly to allow UDP 6081 traffic. What I noted are the following messages in /var/log/openvswitch/ovs-vswitchd.log (on one of the hosts): 2019-12-10T12:10:11.177Z|00009|tunnel(handler4)|WARN|receive tunnel port not found (arp,tun_id=0x2,tun_src=172.18.53.254,tun_dst=172.18.53.202,tun_ipv6_src=::,tun_ipv6_dst=::,tun_gbp_id=0,tun_gbp_flags=0,tun_tos=0,tun_ttl=64,tun_erspan_ver=0,tun_flags=csum|key,in_port=2,vlan_tci=0x0000,dl_src=56:6f:03:4b:00:1f,dl_dst=ff:ff:ff:ff:ff:ff,arp_spa=10.1.1.102,arp_tpa=10.1.1.1,arp_op=1,arp_sha=56:6f:03:4b:00:1f,arp_tha=00:00:00:00:00:00) Here 172.18.53.254 is IP of host1, 172.18.53.202 -- host2 (having this log), 10.1.1.102 -- VM IP on host1 and 10.1.1.1 -- VM IP on host2. Could you please suggest me a way to properly debug and fix this problem? I would like to be able to distribute several VMs connected to the single virtual network across hosts. Thanks in advance! -- WBR, Pavel +32478910884

1 1

Re: katello-host-tools-3.5.1 and Red Hat Satellite 6.4
by Matthias Leopold 10 Dec '19

10 Dec '19

thanks, but all this is given other CentOS 7 hosts (with katello* packages provided by the Satellite server) are OK at the moment I'm looking into https://access.redhat.com/solutions/3517471 I'll ask our Satellite admin tomorrow Regards Matthias Am 10.12.19 um 17:28 schrieb Staniforth, Paul: > Hello Matthias, > > The oVirt hosts need to be registered in redhat satellite as a content > host and the satellite host will need to have the centos and oVirt yum > repositories added so they can create a content view. The first step I > would do is ask whoever manages your satellite server if they are > managing any Centos hosts. > > > > > Regards, > Paul S. > ------------------------------------------------------------------------ > *From:* Matthias Leopold <matthias.leopold(a)meduniwien.ac.at> > *Sent:* 10 December 2019 14:33 > *To:* users <users(a)ovirt.org> > *Subject:* [ovirt-users] katello-host-tools-3.5.1 and Red Hat Satellite 6.4 > Hi, > > I'm trying to register hosts running CentOS 7.6 and oVirt 4.3.5 to a Red > Hat Satellite 6.4 server. The oVirt hosts have katello-host-tools-3.5.1 > packages from oVirt repos, which seem to be too new for the Red Hat > Satellite 6.4 server, Satellite says: > > Errata: > Could not calculate errata status, ensure host is registered and the > katello-host-tools package is installed > > Is there a way to get around this? > Downgrade katello-host-tools? -> is this OK for oVirt? > Upgrade Red Hat Satellite? -> server not under my control... > Is there a compatibility matrix for katello-host-tools and Red Hat > Satellite versions? > > I'm new to this topic.... > > thx > Matthias > _______________________________________________ > Users mailing list -- users(a)ovirt.org > To unsubscribe send an email to users-leave(a)ovirt.org > Privacy Statement: > https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ovirt… > oVirt Code of Conduct: > https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ovirt… > List Archives: > https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.ovi… > To view the terms under which this email is distributed, please go to:- > http://leedsbeckett.ac.uk/disclaimer/email/ > -- Matthias Leopold IT Systems & Communications Medizinische Universität Wien Spitalgasse 23 / BT 88 /Ebene 00 A-1090 Wien Tel: +43 1 40160-21241 Fax: +43 1 40160-921200

1 0

Re: Issue deploying self hosted engine on new install
by Robert Webb 10 Dec '19

10 Dec '19

Just wanted to close this out. Now that I have solved my NFS issues, I completed a clean install of oVirt node on two Dell R410's and ran the self hosted engine wizard on one of them. The install went flawless and I now have a working setup. Thanks for the time and patience from everyone who helped. ________________________________________ From: Robert Webb <rwebb(a)ropeguru.com> Sent: Tuesday, December 10, 2019 8:10 AM To: Yedidyah Bar David Cc: Nate Revo; users(a)ovirt.org Subject: [ovirt-users] Re: Issue deploying self hosted engine on new install I have a thread going reference the NFS permission issue. Going to move all my replies into that since it is not a direct issue with the hosted engine. Thanks for your replies. ________________________________ From: Yedidyah Bar David <didi(a)redhat.com> Sent: Tuesday, December 10, 2019 1:46 AM To: Robert Webb <rwebb(a)ropeguru.com> Cc: Nate Revo <nrevo(a)redhat.com>; users(a)ovirt.org <users(a)ovirt.org> Subject: Re: [ovirt-users] Re: Issue deploying self hosted engine on new install On Mon, Dec 9, 2019 at 3:06 PM Robert Webb <rwebb(a)ropeguru.com> wrote: > > Nate, > > > > Thanks for the tip, but the NAS is Debian based. > > > > > > Is it potentially an SELinux denial? I seem to recall an SELinux Boolean that needs to be set on the nfs server. You might want to check audit log on both nfs server and your host. What error do you get in vdsm.log? > > > > On Sun, Dec 8, 2019, 4:00 PM Robert Webb <rwebb(a)ropeguru.com> wrote: > > Didi, > > Apologies for the delayed reply. > > I tracked the issue down after giving up on the self hosted install. I installed it to a VM running CentOS 7 running on another platform and then added my hosts. > > After adding the hosts and dploying a VM on oVirt, everything deployed perfectly, I could never get the VM to start. Digging further, I found that it is apparently a NFS permission on my NAS. What is odd is that I can add the Storage domain with no issues, I can create a VM, but the VM will never start due to a permission issue on the disk image. > > On my NAS if I just go into the shared folder permissions and not change anything but just tell it to apply configured permissions to all files and folders, the newly created VM runs just fine. For some reason when oVirt creates new files in storage, it is leaving off the execute for the vdsm user. I also notice that for the image and lease files, it also leaves off any permisson for "other" . NOt sure why the permissions are not being applied correctly. But that is an issue for me to figure out on my NAS, OpenMediaVault. > > drwxrwsrwx+ 2 vdsm kvm 4096 Dec 7 23:53 . > drwxrwsrwx+ 8 vdsm kvm 4096 Dec 7 23:13 .. > -rw-rw----+ 1 vdsm kvm 53687091200 Dec 7 23:13 0605d785-f4df-49b1-af27-1f035148921c > -rw-rw----+ 1 vdsm kvm 1048576 Dec 7 23:13 0605d785-f4df-49b1-af27-1f035148921c.lease > -rw-rw-rw-+ 1 vdsm kvm 251 Dec 7 23:53 0605d785-f4df-49b1-af27-1f035148921c.meta > _______________________________________________ > Users mailing list -- users(a)ovirt.org > To unsubscribe send an email to users-leave(a)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/FQGIOYW36MWWW… > > _______________________________________________ > Users mailing list -- users(a)ovirt.org > To unsubscribe send an email to users-leave(a)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/TBHWVVP67DDLF… -- Didi

1 0

Clusters: Clarification needed on the ballooning memory feature and its affects on the physical hosts memory
by donagh.moran＠oracle.com 10 Dec '19

10 Dec '19

Hi For test purposes I'm configuring cluster with ballooning enabled and memory over-commit set to 200% with one host (total memory 128600 MB) connected. I then create 4 linux based VM's and I set the following on each: memory size: 62000MB, max memory: 248000MB (default value set when memory size is set) and a guaranteed memory value of 31000MB (default value set when memory size is set). This all works as expected, I can start 4 VM's with a total memory size that double the physical memory available on the host. What I don't understand is when I view the general info on my host I see that the available memory is much higher than expected. Physical Memory:128600 MB total, 11574 MB used, 117026 MB free. When researching the set up required to test this feature I came across this post https://lists.ovirt.org/pipermail/users/2017-October/084675.html. It states the hosts memory load needs to exceed 80%. I was hoping that the allocation of physical memory to each VM would satisfy this condition but I am not sure it does. I have a few questions on this Should setting the physical memory to each VM would satisfy the greater than 80% conditions? Given we have guaranteed memory for each VM of 31000MB should the total of 124000Mb exceed the free memory on the host? Does the hosts used physical memory only represent each VM's disk 4Gb virtual size? Will the hosts free memory only decrease as the VM's consume storage? Any clarification on the above questions would be most appreciated. Regards Donagh

2 1

Re: Cannot obtain information from export domain
by Strahil 10 Dec '19

10 Dec '19

Hi can you describe your actions? Usually the export is like this: 1. You make a backup of the VM 2. You migrate the disks to the export storage domain 3. You shut down the VM 4. Set the storage domain in maintenance and then detach it from the oVirt 5. You atttach it to the new oVirt 6. Once the domain is active - click on import VM tab and import all VMs (defining the cluster you want them to be running on) 7. Power up VM and then migrate the disks to the permanent storage. Best Regards, Strahil NikolovOn Nov 26, 2019 19:41, Arthur Rodrigues Stilben <arthur.stilben(a)gmail.com> wrote: > > Hello everyone, > > I'm trying to export a virtual machine, but I'm getting the following error: > > 2019-11-26 16:30:06,250-02 ERROR > [org.ovirt.engine.core.bll.exportimport.GetVmsFromExportDomainQuery] > (default task-22) [b9a0b9d5-2127-4002-9cee-2e3525bccc89] Exception: > org.ovirt.engine.core.common.errors.EngineException: EngineException: > org.ovirt.engine.core.vdsbroker.irsbroker.IRSErrorException: > IRSGenericException: IRSErrorException: Failed to GetVmsInfoVDS, error = > Storage domain does not exist: > (u'5ac6c35d-0406-4a06-a682-ed8fb2d1933f',), code = 358 (Failed with > error StorageDomainDoesNotExist and code 358) > > 2019-11-26 16:30:06,249-02 ERROR > [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] > (default task-22) [b9a0b9d5-2127-4002-9cee-2e3525bccc89] EVENT_ID: > IMPORTEXPORT_GET_VMS_INFO_FAILED(200), Correlation ID: null, Call Stack: > null, Custom ID: null, Custom Event ID: -1, Message: Failed to retrieve > VM/Templates information from export domain BackupMV > > The version of the oVirt that I am using is 4.1. > > Att, > > -- > Arthur Rodrigues Stilben > _______________________________________________ > Users mailing list -- users(a)ovirt.org > To unsubscribe send an email to users-leave(a)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/Z6FQ45UVQODSR…

2 1

Still having NFS issues. (Permissions)
by Robert Webb 10 Dec '19

10 Dec '19

So I have doubled checked everything I can think of and am still having issues. I have an NFS Storage Domain attached and I can now create, modify, and remove VM's with no issues. The issue I am having is when it is time to power on the VM. The issue is that when oVirt tries to access the image, access is being denied. I have double checked the documentation against my setup and it all looks right. I have the VDSM user and KVM group created with id's of 36. New files are being created with permissions of 755, just as the documentation describes. What I have found out though, is that in order for oVirt to have access to the files, the "other" permission has to be a 7. So effectiviely I need to have 757, rwx, on the files. Is there a user that I am missing from the documentation, or a user on oVirt that should be in a group, that isn't? Someone previously mentioned the sanlock user, but I do not see anything special that is required for it. This is my last hurdle before really being able to dig into oVirt.

3 4