Search results

Last run I did I deleted my old VM, followed the tutorial to the best of my abilities (given that my proxmox is newer) and I still ended up with a BSOD after clean shutdown. Same error, HAL_INITIALIZATION_FAILED. After reset, I'm now stuck (again) where I started the thread: Could this be...

Followed that to a tee and no dice, same error as mentioned before :)

Was using: GRUB_CMDLINE_LINUX_DEFAULT="quiet amd_iommu=on iommu=pt kvm_amd.npt=1 kvm_amd.avic=1 Will try: GRUB_CMDLINE_LINUX_DEFAULT="quiet amd_iommu=on iommu=pt" But not until later tonight when I can reboot the host :-)

Something is very odd, I have made tweaks to the GRUB command line to enable GPU passthru and since then, the only CPU I can chose is the "host" option. All other options yield kvm: warning: host doesn't support requested feature: CPUID.01H:ECX.x2apic [bit 21] kvm: Host doesn't support...

Nope, while SeaBIOS will let the machine do the complete install with reboots in-between, once you shut it down, the next boot will blue screen. Starting it again seems to work. Some more testing shows that any time I do a graceful shutdown, the machine will BSOD on next power up: Once it has...

Third try since last post... Same result. Last thing to try is non-UEFI which defeats this purpose but now I'm curious. I'm deleting EFI and system drive between runs.

Well, actually, I used i440fx on the working one and here I use q35 because I need passthru working

(and I've compared notes and see nothing different) This is my current setup which failed after the first reboot

A Already tried :( made no difference. It's as if the boot sector on the virtual drive cannot be written or something. Only Win10 that I have working is an image I imported from a VMWare ESXi system

First reboot after installing to SATA lands me in UEFI and I have to launch the EFI loader myself. Shutdown followed by power on and my boot drive is gone again.

I've tried Virt SCSI, Virt IO and now on SATA ... Iso is straight from MS themselves and I've used it multiple times with VMWare Workstation and real computers. So I think I'm just doing something wrong with Proxmox. I'll let you know in 10-20min what the result is this time. Key to trigger it...

Tried reinstalling this time using VirtIO instead of Virt SCSI. All seemed to go well except it wouldn't automatically boot windows, I had to launch fs0:\efi\boot\bootx64.efi (or similar) from the UEFI shell. After a few sessions of that, I shut down the VM completely and started it again. Now...

I installed Win10 Pro on the following machine: And once it was updated to the latest version of Windows 10, it simply got stuck after reboot: I've tried switching to sata and ide with no luck. I've changed the machine from q35 to i440fx. It just shows this screen and gets stuck...

I found a solution which is the "least" hacky: 1. Add your NFS server to the proxmox hosts file (FQDN and just hostname as usual) 2. Edit storage.cfg so you point to the FQDN Step 2 is critical, without it, this wont work. Once this is done, you can confirm functionality by running showmount...