On your second point about an Export domain, how do you configure oVirt to look in an Export domain for the Run Once setup?
On Thu, Apr 2, 2020 at 3:01 PM Shareef Jalloq <shar...@jalloq.co.uk> wrote: > This doesn't seem, to me, to be an issue with the NAS or the mounts. In > my original post you can see the VFD files in the mounted directory under > /rhev. Is that not what you're asking? > > I have both the ISODomain and two DataDomain's mounted. I have a bunch of > VM's running off this NAS with no issues. The permissions to the VFD files > are all correct and I can create and list files in the ISODomain with no > issue. > > On Tue, Mar 31, 2020 at 9:40 PM <eev...@digitaldatatechs.com> wrote: > >> If you issue the mount command does the path show. >> >> mount |grep <path to vfd> >> >> >> >> It looks like the ISO domain is on a NAS, so I would try a mount of the >> actual folder on the ovirt node to make sure you are able to access it. >> Also, can you place it in an export domain instead and try? >> >> I think version 4.2+ it just needs to be in an export domain. >> >> >> >> Also make sure the NAS path is correct. Most NAS use a data or shares for >> nfs mounts. (nasname:/shares/<file shares> >> >> >> >> >> >> Eric Evans >> >> Digital Data Services LLC. >> >> 304.660.9080 >> >> >> >> *From:* Shareef Jalloq <shar...@jalloq.co.uk> >> *Sent:* Tuesday, March 31, 2020 4:59 AM >> *To:* users@ovirt.org >> *Subject:* [ovirt-users] NFS permissions error on ISODomain file with >> correct permissions >> >> >> >> Hi, >> >> >> >> I asked this question in another thread but it seems to have been lost in >> the noise so I'm reposting with a more descriptive subject. >> >> >> >> I'm trying to start a Windows VM and use the virtio-win VFD floppy to get >> the drivers but the VM startup fails due to a permissions issue detailed >> below. The permissions look fine to me so why can't the VFD be read? >> >> >> >> Shareef. >> >> >> >> I found a permissions issue in the engine.log: >> >> >> >> 2020-03-25 21:28:41,662Z ERROR >> [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] >> (ForkJoinPool-1-worker-14) [] EVENT_ID: VM_DOWN_ERROR(119), VM win-2019 is >> down with error. Exit message: internal error: qemu unexpectedly closed the >> monitor: 2020-03-25T21:28:40.324426Z qemu-kvm: -drive >> file=/rhev/data-center/mnt/nas-01.phoelex.com:_volume2_isostore/41cebb4b-c164-4956-8f44-6426170cd9f5/images/11111111-1111-1111-1111-111111111111/virtio-win_servers_amd64.vfd,format=raw,if=none,id=drive-ua-0b9c28b5-f75c-4575-ad85-b5b836f67d61,readonly=on: >> Could not open >> '/rhev/data-center/mnt/nas-01.phoelex.com:_volume2_isostore/41cebb4b-c164-4956-8f44-6426170cd9f5/images/11111111-1111-1111-1111-111111111111/virtio-win_servers_amd64.vfd': >> Permission denied. >> >> >> >> But when I look at that path on the node in question, every folder and >> the final file have the correct vdsm:kvm permissions: >> >> >> >> [root@ovirt-node-01 ~]# ll /rhev/data-center/mnt/nas-01.phoelex.com: >> _volume2_isostore/41cebb4b-c164-4956-8f44-6426170cd9f5/images/11111111-1111-1111-1111-111111111111/virtio-win_servers_amd64.vfd >> -rwxrwxrwx. 1 vdsm kvm 2949120 Mar 25 21:24 >> /rhev/data-center/mnt/nas-01.phoelex.com: >> _volume2_isostore/41cebb4b-c164-4956-8f44-6426170cd9f5/images/11111111-1111-1111-1111-111111111111/virtio-win_servers_amd64.vfd >> >> >> >> The files were uploaded to the ISO domain using: >> >> >> >> engine-iso-uploader --iso-domain=iso_storage upload virtio-win.iso >> virtio-win_servers_amd64.vfd >> >> >>
_______________________________________________ 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/UMXVXZB6PZMMAGW7TSIXBVQW3LHPDTO6/
