Search results

Hmm, okay... From working kernel "ip a" 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope...

I did not know I had to do `apt dist-upgrade` when I did the original update. Anyway, I updated through the UI this time. I no longer get those messages... but I still cannot access to the UI or SSH into the server. I discovered that if I use the older kernel `5.13.19-6-pve` everything is...

I recently did some updates to proxmox, everything worked great until I restarted the server a couple of days later. Now: the web UI is not available cannot SSH into proxmox server can login locally, but cannot execute any commands The local monitor is filled with this message (although the...

Resolved! Thank you @_gabriel ! These are the exact steps and commands I used. Hopefully this will help someone else in the future. With hdd set to sata, boot to Windows Open elevated cmd prompt Execute the following command bcdedit /set {default} safeboot network Restart Windows (just to...

Disabling fast boot didn't work... How can I get to safe mode? I thought it was supposed to be in this menu. I also attempted to use the installation disk to repair the operating system, which also fails to repair.

This is what I see before the blue screen crash.

I'm able to get back to the OS just fine if switching back to sata. As you can see in the attached image, I have 2 drives attached (and working) that are "QEMU QEMU HARDDISK SCSI Disk Device"... These are not even dummy disks, but drives I'm actually using for storage... But switching the boot...

One issue that I am still having is I cannot use GeForce Experience game streaming with a dummy dongle, although it does work if I connect to a physical monitor. I am not sure what is going on here as the driver (Generic PnP Monitor) is installed for the dongle, and I know it works on bare metal...

I spent a couple of days getting this all working so I thought I would post here in order to help others who may be struggling. Most of this is in the docs here, but some things are not obvious: https://pve.proxmox.com/wiki/Pci_passthrough /etc/modprobe.d/kvm.conf options kvm ignore_msrs=1...

Occasionally, after the VM reboots automatically due to the blue screen it will attempt to do a "startup repair"; however it always fails.

Yes I have done exactly as the instructions say. The weird thing is that I also have 2 other virtual disks in the machine that are using SCSI (although these were created that way since the beginning). But as soon as I switch the boot disk to SCSI I get a blue screen before the Login Screen...

I have a Windows 11 guest, with the main hard drive as a sata drive. I would like to change this over to a scsi drive. When I attempt to change it to a SCSI or VirtIO Block I get a blue screen when booting the VM. I have followed the instructions here...