buoyant plover
I’m trying to use QEMU/KVM User Session and virt-manager to get a working windows vm.
I can create a new virtual machine just fine using virt manager from a windows 10 ISO. I get as far as the windows startup screen before the blue screen of death.
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
The VM then reverts to a black screen with some text (Arch SeaBIOS) that ends with the following:
booting from hard disk…
boot failed: not a bootable diskno bootable device
buoyant plover
Update: changed virtual cpu to some other ones got me new error “Unsupported processor”
Below is me just trying different processors and recording the error
Opteron_G3 = Unsupported
qemu64 = System thread
coreduo = ???
core2duo = system thread
Opteron_G1 = black screen
steady veldt
host-model / host-passthrough?
buoyant plover
host-model / host-passthrough?
host-model reverts to Opteron_G3 which otherwise cannot be selected in the menu
Which exits with blue screen + unsupported processor
Opteron_G2 = System thread
host-passthrough:
for x86_64 qemu domain on x86_64 host is not supported by hypervisor
steady veldt
are you using qemu instead of kvm for the hypervisor? that's not hardware accelerated
buoyant plover
It’s QEMU/KVM
steady veldt
can you post your xml
buoyant plover
it's really long
<domain type="qemu">
<name>win10</name>
<uuid>beb1d480-3336-4ea0-9ee8-1f0632bfe8ca</uuid>
<metadata>
<libosinfo:libosinfo xmlns:libosinfo="http://libosinfo.org/xmlns/libvirt/domain/1.0">
<libosinfo:os id="http://microsoft.com/win/10"/>
</libosinfo:libosinfo>
</metadata>
<memory unit="KiB">8388608</memory>
<currentMemory unit="KiB">4096000</currentMemory>
<vcpu placement="static">16</vcpu>
<os>
<type arch="x86_64" machine="pc-q35-7.1">hvm</type>
</os>
<features>
<acpi/>
<apic/>
<hyperv mode="custom">
<relaxed state="on"/>
<vapic state="on"/>
<spinlocks state="on" retries="8191"/>
</hyperv>
<vmport state="off"/>
</features>
<cpu mode="host-model" check="partial"/>
<clock offset="localtime">
<timer name="rtc" tickpolicy="catchup"/>
<timer name="pit" tickpolicy="delay"/>
<timer name="hpet" present="no"/>
<timer name="hypervclock" present="yes"/>
</clock>
<on_poweroff>destroy</on_poweroff>
<on_reboot>restart</on_reboot>
<on_crash>destroy</on_crash>
<pm>
<suspend-to-mem enabled="no"/>
<suspend-to-disk enabled="no"/>
</pm>
<devices>
<emulator>/usr/bin/qemu-system-x86_64</emulator>
that's the first bit
buoyant plover
there's also this warning message when creating a vm
not sure if it's related, I already made sure kvm was enabled by systemd though it didn't fix it
steady veldt
do you have virtualization enabled in bios
buoyant plover
There’s no plain KVM hypervisor.
The ones listed are
“QEMU/KVM”
“QEMU/KVM user session”
“Libvirt-LXC”
or an option for custom URL
LC_ALL=C lscpu | grep Virtualization
Returns
Virtualization: AMD-V
Let me go into bios and see my settings
steady veldt
ok, and is it a custom kernel
steady veldt
did you find it in bios
buoyant plover
I didn’t see anything to do with virtualization in bios
although I didn’t know where to look specifically
uname -s
Linux
steady veldt
it should be somewhere related to cpu or advanced options/features, or "svm"
buoyant plover
svm?
steady veldt
that's how it's called on amd
but since you're already on Linux
look for kvm: in dmesg
buoyant plover
Oh fuck
Many lines support for ‘kvm_amd’ disabled by bios
Needless to say I’m trying bios again
Ok I found in bios “SVM Mode” which is disabled, enabling it now
I’m back to virt-manager trying it again
now I have a new error from trying out a few different virtual cpu options including host-model/pass through
Error starting domain: Requested operation is not valid: network ‘default’ is not active
Now I got passed that error through enabling default with virsh
And I get blue screen of death “unsupported processor”
(:
no I’m not upset in the slightest 😅😭
UPDATE
————
I tried deleting and remaking the virtual machine, suspecting that due to it being made while bios had svm disabled meant it might not have gotten set up correctly
Result is promising
