Second post in the thread when I replied to myself. Perhaps it's not showing in your mail viewer.
Cheers. Actually, 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 On Sun, Mar 29, 2020 at 9:44 PM <[email protected]> wrote: > You said you get a pop up and think it’s a strange permission issue, but I > don’t see where you posted the error message…If I missed it I apologize. > Can you repost it? > > > > Eric Evans > > Digital Data Services LLC. > > 304.660.9080 > > > > *From:* Shareef Jalloq <[email protected]> > *Sent:* Sunday, March 29, 2020 3:20 PM > *To:* [email protected] > *Cc:* [email protected] > *Subject:* Re: [ovirt-users] Re: How to debug a failed Run Once launch > > > > See my second reply to this thread. > > > > On Fri, Mar 27, 2020 at 12:21 PM <[email protected]> wrote: > > Can you give the exact error message or a screenshot? Check the engine.log > as well for error messages. > > > > Eric Evans > > Digital Data Services LLC. > > 304.660.9080 > > > > *From:* Shareef Jalloq <[email protected]> > *Sent:* Friday, March 27, 2020 6:30 AM > *To:* [email protected] > *Cc:* [email protected] > *Subject:* [ovirt-users] Re: How to debug a failed Run Once launch > > > > So just to confirm all the options when I'm setting up the VM. This is > Windows Server 2019 so I'm selecting: > > > > - General:Operating System = Windows 2019 x64 > > - System:Memory Size = 16GB > > - System:Total Virtual CPUs = 8 > > - BootOptions:First Device = CD-ROM > > - BootOptions:Second Device = Hard Disk > > > > Then in the Run Once config I'm attaching both the floppy and CD as well > as updating the predefined boot sequence. > > > > When I installed the virtio-win package there are multiple VFD files in > /usr/share/virtio-win/. I'm assuming the win_amd64.vfd version is for > non-server Windows installs so I picked virtio-win_servers_amd64.vfd. > > > > Assuming that's all ok, it just seems to be a strange permissions issue... > > > > > > On Fri, Mar 27, 2020 at 8:59 AM Shareef Jalloq <[email protected]> > wrote: > > Yep. > > > > On Thu, Mar 26, 2020 at 7:25 PM <[email protected]> wrote: > > The Windows Server 2019 needs to be the first boot device on the run once. > Is it set that way in the boot options? > > > > Eric Evans > > Digital Data Services LLC. > > 304.660.9080 > > > > *From:* Shareef Jalloq <[email protected]> > *Sent:* Thursday, March 26, 2020 2:25 PM > *To:* [email protected] > *Subject:* [ovirt-users] How to debug a failed Run Once launch > > > > Hi, > > > > I'm trying to create a Windows Server 2019 VM and having found the > virtio-win package that needed to be installed am facing the next hurdle. > > > > I've followed the documentation and I'm using the Run Once option with the > following boot options: > > > > Attach Floppy: virtio-win_servers_amd64.vfd > > Attach CD: Win 2029 ISO > > CD-ROM at top of Predefined Boot Sequence > > > > Clicking OK starts the VM but it immediately fails with a Failed Launching > pop up. > > > > How do I go about debugging this? > > > > Shareef. > > > > > > > >
_______________________________________________ Users mailing list -- [email protected] To unsubscribe send an email to [email protected] 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/[email protected]/message/GCAGGSTAZR4Y47ARGJMWEL2P2O4SA6NW/
