[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 <shareef(a)jalloq.co.uk> wrote:
Yep.
On Thu, Mar 26, 2020 at 7:25 PM <eevans(a)digitaldatatechs.com> 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 <shareef(a)jalloq.co.uk>
> *Sent:* Thursday, March 26, 2020 2:25 PM
> *To:* users(a)ovirt.org
> *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.
>
>
>
Attachments:
- image002.jpg (image/jpeg — 3.4 KB)
- image001.png (image/png — 34.6 KB)
- attachment.html (text/html — 6.6 KB)
