Hi. So I have my system configured to use two windows VMs, with each running windows ten, using half of the system RAM (4gb) and half the cpu cores (4). Each has its own graphics card, and I am currently going through the install process on each virtual machine.

 

However, I've run into a problem while installing windows on the first virtual machine. I am using the latest virtIO file, and the latest win10 iso. When I boot the system, however, I am greeted with a splash screen saying that windows failed to start, and that "A required file is missing or contains errors." The status code is 0xc0000225. It's telling me to use my windows installation disc to repair my computer, but because this is a VM I cannot do this. What can I do?

post your win10 config xml from one of the vm's please.

Until the install is working and stable, try reducing the number of cores to just a single core.

I'll try all of this tomorrow, & keep you all updated as I do.

XML For one VM:

 

<domain type='kvm'>

  <name>Gabe</name>

  <uuid>9a5ea947-032f-da59-8522-c6939cc4b65b</uuid>

  <description>Gabes box</description>

  <metadata>

    <vmtemplate xmlns="unraid" name="Windows 10" icon="windows.png" os="windows10"/>

  </metadata>

  <memory unit='KiB'>4194304</memory>

  <currentMemory unit='KiB'>4194304</currentMemory>

  <memoryBacking>

    <nosharepages/>

    <locked/>

  </memoryBacking>

  <vcpu placement='static'>1</vcpu>

  <cputune>

    <vcpupin vcpu='0' cpuset='0'/>

  </cputune>

  <os>

    <type arch='x86_64' machine='pc-i440fx-2.5'>hvm</type>

    <loader readonly='yes' type='pflash'>/usr/share/qemu/ovmf-x64/OVMF_CODE-pure-efi.fd</loader>

    <nvram>/etc/libvirt/qemu/nvram/9a5ea947-032f-da59-8522-c6939cc4b65b_VARS-pure-efi.fd</nvram>

  </os>

  <features>

    <acpi/>

    <apic/>

    <hyperv>

      <relaxed state='on'/>

      <vapic state='on'/>

      <spinlocks state='on' retries='8191'/>

      <vendor id='none'/>

    </hyperv>

  </features>

  <cpu mode='host-passthrough'>

    <topology sockets='1' cores='1' threads='1'/>

  </cpu>

  <clock offset='localtime'>

    <timer name='hypervclock' present='yes'/>

    <timer name='hpet' present='no'/>

  </clock>

  <on_poweroff>destroy</on_poweroff>

  <on_reboot>restart</on_reboot>

  <on_crash>restart</on_crash>

  <devices>

    <emulator>/usr/local/sbin/qemu</emulator>

    <disk type='file' device='cdrom'>

      <driver name='qemu' type='raw'/>

      <source file='/mnt/user/ISOs/Windows.iso'/>

      <target dev='hda' bus='virtio'/>

      <readonly/>

      <boot order='2'/>

      <address type='pci' domain='0x0000' bus='0x00' slot='0x04' function='0x0'/>

    </disk>

    <disk type='file' device='cdrom'>

      <driver name='qemu' type='raw'/>

      <source file='/mnt/user/ISOs/virtio-win-0.1.112-1.iso'/>

      <target dev='hdb' bus='ide'/>

      <readonly/>

      <address type='drive' controller='0' bus='0' target='0' unit='1'/>

    </disk>

    <controller type='usb' index='0' model='ich9-ehci1'>

      <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x7'/>

    </controller>

    <controller type='usb' index='0' model='ich9-uhci1'>

      <master startport='0'/>

      <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x0' multifunction='on'/>

    </controller>

    <controller type='usb' index='0' model='ich9-uhci2'>

      <master startport='2'/>

      <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x1'/>

    </controller>

    <controller type='usb' index='0' model='ich9-uhci3'>

      <master startport='4'/>

      <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x2'/>

    </controller>

    <controller type='pci' index='0' model='pci-root'/>

    <controller type='ide' index='0'>

      <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x1'/>

    </controller>

    <controller type='virtio-serial' index='0'>

      <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/>

    </controller>

    <interface type='bridge'>

      <mac address='52:54:00:fe:17:d7'/>

      <source bridge='br0'/>

      <model type='virtio'/>

      <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0'/>

    </interface>

    <serial type='pty'>

      <target port='0'/>

    </serial>

    <console type='pty'>

      <target type='serial' port='0'/>

    </console>

    <channel type='unix'>

      <source mode='connect'/>

      <target type='virtio' name='org.qemu.guest_agent.0'/>

      <address type='virtio-serial' controller='0' bus='0' port='1'/>

    </channel>

    <hostdev mode='subsystem' type='pci' managed='yes'>

      <driver name='vfio'/>

      <source>

        <address domain='0x0000' bus='0x03' slot='0x00' function='0x0'/>

      </source>

      <address type='pci' domain='0x0000' bus='0x00' slot='0x05' function='0x0'/>

    </hostdev>

    <hostdev mode='subsystem' type='pci' managed='yes'>

      <driver name='vfio'/>

      <source>

        <address domain='0x0000' bus='0x02' slot='0x00' function='0x0'/>

      </source>

      <address type='pci' domain='0x0000' bus='0x00' slot='0x06' function='0x0'/>

    </hostdev>

    <hostdev mode='subsystem' type='usb' managed='no'>

      <source>

        <vendor id='0x046d'/>

        <product id='0xc315'/>

      </source>

    </hostdev>

    <hostdev mode='subsystem' type='usb' managed='no'>

      <source>

        <vendor id='0x413c'/>

        <product id='0x3010'/>

      </source>

    </hostdev>

    <memballoon model='virtio'>

      <address type='pci' domain='0x0000' bus='0x00' slot='0x08' function='0x0'/>

    </memballoon>

  </devices>

</domain>

 

This solution might help you.

 

On 1/9/2020 at 2:34 PM, Alexander said:

This solution might help you.

After 3+ years, I'm pretty sure they've moved on by now, either solved it and didn't post back, or gave up.

Yes I know, it is an old thread, sorry.

But when I recently got this problem I searched for that status code error to find a solution.

This is all I found. No good solution.

I want others in the same situation to get help, that's all.

I recently had this issue while trying Unraid for the first time and I found out what caused it at-least for me. When I uploaded my .iso I used the File Manager plugin of Unraid, meaning I uploaded it through my web browser into a folder on one of my storage disks and then used that to boot the VM.

 

This always results in the error shown in this thread. However when I created a share on my Unraid which I accessed from my PC via SMB and uploaded the .iso to my Unraid server through that share it boots successfully, every single time.

 

So I don't know why the uploader failed but I suspect it either corrupted the .iso in a non-obvious way or wiped some metadata from it I'm not sure, but uploading the boot media via a share works and uploading through the WebUI of Unraid does not.

 

I know this is an old thread but when googling the error it's just this thread that comes up and I figure others may benefit from this answer