Search results

Just one hour ago. The machine froze again. The system which rebooted fine multiple times before is now (as per usual) showing "vfio-pci ...... vgaarb: changed VGA decodes: olddecodes=io+mem, decodes=none:eek:wns=none" as the last line on the screen, strangely it reboots almost immediately on...

dmesg -T | grep -e BAR -e Intel -e iommu -e IOMMU -e passthrough -e DMAR -e bug -e Bug may tell you more

Ah, thanks.May i suggest to document that not-mounting bit and such ? OOPS From the page you mentioned, i missed this 3 times. The ESPs are not kept mounted during regular operation, in contrast to grub, which keeps an ESP mounted on /boot/efi. This helps to prevent filesystem corruption to...

Thanks Stoiko. I had a read again on this page now i slept a few hours. Typical as for many open source 'documentation' it is informative, not helpful. That much i could learn with 'man bootctl' and 'man systemd-boot' What has me stumped is systemd-boot works fine but the /boot/efi partition...

also a possiblity is to enable backports on Wheezy or to check with apt-cache policy qemu-guest-agent which versions are available then install with apt install qemu-guest-agent=<versionnumberyouwanthere>

Am i correct in assuming this is simply how systemd-boot works ? The system boots fine now, except for this. bootctl status Couldn't find EFI system partition. It is recommended to mount it to /boot or /efi. Alternatively, use --path= to specify path to mount point. Even after reinstalling...

maybe i am just impatient, may i just lack common sense how on earth does one fix systemd-boot after doing upgrade-grub ? running bootctl simpy lists the partition which holds the ESP mounting this partition on /boot/efi and running bootctl again shows success still, no boot the ESP/EFI...

FYI the only boot parameters resulting in a functioning sytem is to set iommu=off iommu=off text nomodeset .... root=ZFS=mypool/ROOT/....

ok it works, thanks Anakin, thanks Mr. Bean now how to repair systemd-boot May i suggest s6 by skarnet.org as future default init system for proxmox ?

aaah. the sweet agony of systemd-boot. What works once, does not work again. for example module_blacklist=vfio-pci would i dare to consider systemd has somehow something to do with this time consuming event ? because yeah, i did run update-grub and that is not what i was supposed to do, huh

because i fail to understand i share my clumsly learnings with proxmox For some reason or other i wanted to explore how to configure two bridges using a single NIC. Eventually this resulted in the faint hearted decisions to set the gateway of vmbr0 to 0.0.0.0, because who knows, it might just...

" the proxmox system completely froze, zero logs happening, no network, not even a bad write to disk. " not really "the proxmox system completely froze, zero logs happening, no network, not even a bad write to disk. " What i did find is there is one disk, an older sata drive which is showing...

this is no longer an issue now, i have absolutely no idea why not anymore. If it resurfaces i will update the thread. to know, i have not customized vmid.conf in any way, simply using the web interface. The only manual configurations i made were the corrections required after observing the...

this happens for any VM i attempt passthrough with for both GPU and Audio (same ID.x) latest VE 6.2 fully updated qm start simply states the device was allready assigned/associated, which is how i found out about this happening in the first place

While struggeling with PCI passthrouhg (it does work, eventually) i found something peculiar. Sometimes the VM would not boot because the PCI.id for a device was alread in use. This was because the pci-id for the vga and the audio were written as the same. So instead of 0000:17:0.0 and...

It is demanding to get it working but i can say nothing is broken, at least not for my system. This machine is running on Proxmox VE 6.2 since about one month. GPU passthrough is quite demanding in my experience but if it works, it works very close to native speed. Staring a VM from the shell...

Which is in-line with vfio 0000:65:00.0: failed getting region info for VGA region index 8: Invalid argument device does not support requested feature x-vga

this post https://www.linuxquestions.org/questions/linux-virtualization-and-cloud-90/trouble-with-gpu-passthrough-on-slackware-14-2-failed-getting-region-info-for-vga-region-index-8-a-4175601587/ suggests to remove x-vga=1

Ah! I completely missed that error message. cat /etc/pve/qemu-server/107.conf agent: 1 bootdisk: sata0 cores: 10 cpu: host,hidden=1,flags=+pcid args: -cpu 'host,+kvm_pv_unhalt,+kvm_pv_eoi,hv_vendor_id=NV43FIX,kvm=off' hostpci0: 65:00,pcie=1,x-vga=1 ide2: none,media=cdrom machine: q35 memory...

the proxmox system completely froze, zero logs happening, no network, not even a bad write to disk. the first log entry i see after me trying to figure out what happened to the server are logs for the host booting up. * only recent changes to the system was the introduction of huge pages...