Search results

Okay. Like i said. Do both vm and hardware.

1. do not reboot until you understand what you did 2. /boot/efi should be mounted to see if it contains an entry for grub or loader now you know 3. if it reads grub and you know grub, you should be fine 4. if it read loader and contains loader.conf you are using systemd-boot, use pve-efiboot-mgr...

for hire as IT and Cybersecurity analyst and coach

Not much to to work with here, indeed, all looks good. Not sure if this line should read passthrough instead, i know it shows passthrough with my setup. [Sat Jun 20 00:01:24 2020] iommu: Default domain type: Translated In the past i noticed reordering kernel boot paramters does make a...

Very nice specs. Much more than you need for 5 VPN connections :) Running a firewall in a vm is okay but if the VM server is in a highly sensitive area i would advise against it. Just because VM breakouts happen and if it takes the server down there is no more firewall. You could consider...

Running with a 1700x 8 cores and 32GB of ram, a 1.13TB zfs pool built on 3 cheap ssd drives (2x sata, 1x nvme) works great, but i think 64GB or even 48GB would be just right. CPU is amazingly little in use, RAM is forced to run at 2666Mhz instead of 3200Mhz since upgrading to 32GB from 16GB...

WTF! while /etc/network/interface has the bridge configured and a bridge.vlanid configured it now does not know the bridge interface anymore when looking with brctl show the file /var/log/error shows a kernel: mce: [Hardware Error]: CPU 11: Machine Check: 0 Bank 5: bea...... kernel: mce...

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...