[ovirt-users] Re: How to debug a failed Run Once launch

2020-03-30 Thread Shareef Jalloq
messages. > > > > Eric Evans > > Digital Data Services LLC. > > 304.660.9080 > > > > *From:* Shareef Jalloq > *Sent:* Friday, March 27, 2020 6:30 AM > *To:* eev...@digitaldatatechs.com > *Cc:* users@ovirt.org > *Subject:* [ovirt-users] Re: How to d

[ovirt-users] Re: How to debug a failed Run Once launch

2020-03-29 Thread eevans
To: eev...@digitaldatatechs.com Cc: users@ovirt.org 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 mailto:eev...@digitaldatatechs.com> > wrote: Can you give the exact error message or a screenshot?

[ovirt-users] Re: How to debug a failed Run Once launch

2020-03-29 Thread Shareef Jalloq
> > *From:* Shareef Jalloq > *Sent:* Friday, March 27, 2020 6:30 AM > *To:* eev...@digitaldatatechs.com > *Cc:* users@ovirt.org > *Subject:* [ovirt-users] Re: How to debug a failed Run Once launch > > > > So just to confirm all the options when I'm

[ovirt-users] Re: How to debug a failed Run Once launch

2020-03-27 Thread eevans
-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

[ovirt-users] Re: How to debug a failed Run Once launch

2020-03-27 Thread Shareef Jalloq
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

[ovirt-users] Re: How to debug a failed Run Once launch

2020-03-27 Thread Shareef Jalloq
Yep. On Thu, Mar 26, 2020 at 7:25 PM 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 > *Sent:* Thursday, March 26,

[ovirt-users] Re: How to debug a failed Run Once launch

2020-03-26 Thread eevans
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 Sent: Thursday, March 26, 2020 2:25 PM To: users@ovirt.org Subject: [ovirt-users] How to debug

[ovirt-users] Re: How to debug a failed Run Once launch

2020-03-26 Thread Shareef Jalloq
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