[SOLVED] W10 OVMF installation impossible

[jackydany]

Hi alltogether,

i am running proxmox 6.1 latest updates freshly installed a couple of days ago on a fuji tx300 s7.
2x SSD 40gb for root ZFS base system (OS).
5x 1TB ZFS for ecverything else on raid controller in IT Mode SAS 2008
128gb ram
2x xeon e5 2640
only this node, no HA etc....
have 2 LXC up and running, pihole, motioneye
2 VMs, zoneminder in ubuntu and iobroker in ubuntu.
working flawlessly. no issues.

My goal is to get a good server and a w10 VM with gpu passthrough up and running, but so far i got stuck very heavily.

I cant get a working installation of a w10 VM with OVMF done.
q35
scsi
efi disk
OVMF as Bios
8gb ram
8 cpus (default and tried host cpu)
no network card
guest agent activated (also tried deactivated)
45gb disk
balooning activated (also tried deactivated)
2x ide dvd (win10 iso and virtio iso)

options
boot order: only disk left after first installation

windows installs perfectly fine, starts up the first time.
i install the desired drivers like balooning and serial and the guest agent...
reboot....
i start the VM an it directly fails with a blue screen, HAL Error message.
It collects data and shuts down.
after reboot, it stucks in boot logo with uefi message :
bdsdce: loading Boot0005 "Windows Boot Manager" ............................................

and thats it... not more!

original MS Iso, i installed a hardware maschine with this iso.
also seabios is working, but with seabios i cant get gpu passthrough to work (another construction site, but later!)

I tried to attach a network card, virotio and Intel... same result.
i tried balooning off, same result
i tried cpu default and host, same result

at this stage i am not passing through anything!
i just want to get windows on uefi up and running first. omvf is best practice for gpun passthrough.


I hope you can help me out.


Thanks!

Stefan

 

[jackydany]

also after some more tests yesterday, the ram usage of the host climbed up to 25gb.
the VMs and LXC alltogether didnt take more than 4gb. So i had to reboot the complete Host to get back to normal.
Now its back to 6gb at the moment.

 

[jackydany]

Nobody running a WIndows 10 VM on UEFI (OVMF) ?

 

[jackydany]

And push

 

[dcsapak]

please do not bump your thread if you do not provide any additional information

also, please post your pveversion -v, your vm config (qm config ID)
and any actual error message (as exact as possible, maybe attach a screenshot)

also you wrote about gpu passthrough but did not mention which gpu
(in that case please also provide lspci, iommu group and dmesg output)

 

[jackydany]

Hi,

here are the informations you asked for:

proxmox-ve: 6.1-2 (running kernel: 5.3.18-3-pve)
pve-manager: 6.1-8 (running version: 6.1-8/806edfe1)
pve-kernel-helper: 6.1-7
pve-kernel-5.3: 6.1-6
pve-kernel-5.3.18-3-pve: 5.3.18-3
pve-kernel-5.3.18-2-pve: 5.3.18-2
pve-kernel-5.3.10-1-pve: 5.3.10-1
ceph-fuse: 12.2.11+dfsg1-2.1+b1
corosync: 3.0.3-pve1
criu: 3.11-3
glusterfs-client: 5.5-3
ifupdown: residual config
ifupdown2: 2.0.1-1+pve8
ksm-control-daemon: 1.3-1
libjs-extjs: 6.0.1-10
libknet1: 1.15-pve1
libpve-access-control: 6.0-6
libpve-apiclient-perl: 3.0-3
libpve-common-perl: 6.0-17
libpve-guest-common-perl: 3.0-5
libpve-http-server-perl: 3.0-5
libpve-storage-perl: 6.1-5
libqb0: 1.0.5-1
libspice-server1: 0.14.2-4~pve6+1
lvm2: 2.03.02-pve4
lxc-pve: 3.2.1-1
lxcfs: 4.0.1-pve1
novnc-pve: 1.1.0-1
openvswitch-switch: 2.12.0-1
proxmox-mini-journalreader: 1.1-1
proxmox-widget-toolkit: 2.1-3
pve-cluster: 6.1-4
pve-container: 3.0-23
pve-docs: 6.1-6
pve-edk2-firmware: 2.20200229-1
pve-firewall: 4.0-10
pve-firmware: 3.0-6
pve-ha-manager: 3.0-9
pve-i18n: 2.0-4
pve-qemu-kvm: 4.1.1-4
pve-xtermjs: 4.3.0-1
qemu-server: 6.1-7
smartmontools: 7.1-pve2
spiceterm: 3.1-1
vncterm: 1.6-1
zfsutils-linux: 0.8.3-pve1

cat 150.conf
cat: 150.conf: No such file or directory
root@prox:/etc/pve/qemu-server# cat 105.conf
agent: 1
bios: ovmf
boot: c
bootdisk: scsi0
cores: 4
cpu: host
efidisk0: wonderland-zfs:vm-105-disk-0,size=1M
ide0: local:iso/virtio-win-0.1.171.iso,media=cdrom,size=363020K
ide2: local:iso/Windows_10_x64_original.iso,media=cdrom
machine: q35
memory: 8192
name: test2
numa: 0
ostype: win10
parent: fertigfrisch
scsi0: wonderland-zfs:vm-105-disk-1,cache=writeback,size=45G
scsihw: virtio-scsi-pci
smbios1: uuid=84c9763f-87a3-426a-b8d2-6190f7466437
sockets: 2
vmgenid: e4f0fba3-2db1-4cfa-989a-a552cbd2e78e

[snap3]
agent: 1
bios: ovmf
bootdisk: scsi0
cores: 4
cpu: host
efidisk0: wonderland-zfs:vm-105-disk-0,size=1M
ide0: local:iso/virtio-win-0.1.171.iso,media=cdrom,size=363020K
ide2: local:iso/Windows_10_x64_original.iso,media=cdrom
machine: q35
memory: 8192
name: test2
numa: 0
ostype: win10
parent: snap2
runningmachine: pc-q35-4.1+pve0
scsi0: wonderland-zfs:vm-105-disk-1,cache=writeback,size=45G
scsihw: virtio-scsi-pci
smbios1: uuid=84c9763f-87a3-426a-b8d2-6190f7466437
snaptime: 1585781495
sockets: 2
vmgenid: 693b8a99-6b50-4fcb-99a0-7b8167fafc65
vmstate: wonderland-zfs:vm-105-state-fertigfrisch

[snap1]
agent: 1
bios: ovmf
bootdisk: scsi0
cores: 4
cpu: host
efidisk0: wonderland-zfs:vm-105-disk-0,size=1M
ide0: local:iso/virtio-win-0.1.171.iso,media=cdrom,size=363020K
ide2: local:iso/Windows_10_x64_original.iso,media=cdrom
machine: q35
memory: 8192
name: test2
numa: 0
ostype: win10
runningmachine: pc-q35-4.1+pve0
scsi0: wonderland-zfs:vm-105-disk-1,cache=writeback,size=45G
scsihw: virtio-scsi-pci
smbios1: uuid=84c9763f-87a3-426a-b8d2-6190f7466437
snaptime: 1585780913
sockets: 2
vmgenid: 693b8a99-6b50-4fcb-99a0-7b8167fafc65
vmstate: wonderland-zfs:vm-105-state-frisch

[snap2]
agent: 1
bios: ovmf
bootdisk: scsi0
cores: 4
cpu: host
efidisk0: wonderland-zfs:vm-105-disk-0,size=1M
ide0: local:iso/virtio-win-0.1.171.iso,media=cdrom,size=363020K
ide2: local:iso/Windows_10_x64_original.iso,media=cdrom
machine: q35
memory: 8192
name: test2
numa: 0
ostype: win10
parent: snap1
runningmachine: pc-q35-4.1+pve0
scsi0: wonderland-zfs:vm-105-disk-1,cache=writeback,size=45G
scsihw: virtio-scsi-pci
smbios1: uuid=84c9763f-87a3-426a-b8d2-6190f7466437
snaptime: 1585781267
sockets: 2
vmgenid: 693b8a99-6b50-4fcb-99a0-7b8167fafc65
vmstate: wonderland-zfs:vm-105-state-usereingegeben

And as i mentioned before.... i didnt event ry GPU passthrough yet.
I just cant get an OVMF VM running, so first things first

What kind of error messages du you mean?
I jsut get a bluescreen in windows after booting.

Thanks!


ps: If you want me to install a new VM with your preferred preferences, just tell me. Willing to try anything thats helps.

 

[dcsapak]

I jsut get a bluescreen in windows after booting.

what bluescreen? which error?
did you try another windows iso already? another virtio driver version?

 

[jackydany]

Which driver in special? Network, Display, SCSI? Or all of them. I just downloaded the latest virio driver iso. If i need different drivers, where to get older ones?
Also with seabios everything works fine.
Iso is downloaded via microsoft tool.
I will download a new iso and make a foto of the bluescreen.

 

[jackydany]

i tested a bit more.
VM:
16gb ram, network card virtion, cpu=host, 2 sockets, 8 cores.
bios=OVMF
IMPORTANT: network card disconnected!

installed fine, run fine.
I could install all drivers
reboot, fine. everything fine!
I shutdown the maschine and connected the network card in the hardware tab.
now i got a bluescreen

after reboot, nothing. the maschine wont boot past bios message.


Thats it! Even changing back, so disconnecting the network card again wont help.
I can rollback to a snapthot, thats working.


So i tested further.
Everything seems to work, rebooting no problems...
As soon as i change anything in the hardware tab, the maschine wont boot past Bios message anymore.
change ram from 8gb to 16gb... no boot, revert the change... no boot.
add und revert CPU cores. no more booting.

doestn matter if i have a vm with 8gb ram and 8 cores or 16gb ram and 16 cores... behavior is the same.
I didnt change the drivers or ISO yet. Do you still think this would be an driver / iso problem?

 

[dcsapak]

I didnt change the drivers or ISO yet. Do you still think this would be an driver / iso problem?

yes that is possible..

how does the network card config look like? (in your configs, i see no network card at all?)

 

[jackydany]

In the first Config there was no card.
That was the second test.
It was VirtIO Card, disconnected.
Everything fine as long as i dont change anything in the hardware-tab.
Doesnt matter if its CPU, Ram or Network. After changing Hardware Specs for the VM the VM wohnt boot past the Bios Message i took the Screenshot from.

I donwoladed a new ISO and will have a new test later on.
Also a different VirtIO Drivers ISO, Snapshot and latest stable for testing now. But i dont think the drivers are any issue because even without any driver, if i change Hardware, the Maschine stops working. Couldnt be any driver-issue though.

Thanks for your help.

ps: maybe you tell me Specs for a maschine to set up, and i post the config files and then we move on to testing? So we have a specific point to start from and we both know what point it is?

 

[jackydany]

Well ok, i think you got it right!

I changed the ISO image AND the driver from 1.7.1(stable) to 1.7.3.
Now everything seems to work fine!
I created a new W10 maschine and edited a lot now. Added CPUs, Ram, Network enabled etc...
Also changing the Diaplay from default to standard vga worked.

I will have one last test to verify, change only the iso and only the drivers, not both at the same time to check what caused this issue.

Thanks a lot for your help!

 

[t.lamprecht]

Ok, so I marked this thread as solved (as thread creator you can do so yourself for future threads, FYI)

 

[jackydany]

Ok, so I marked this thread as solved (as thread creator you can do so yourself for future threads, FYI)

yeah well, i know, just forgot it, sorry