Recent content by AxxelH

I have a Ubuntu 24.04 LXC built using the latest template. The intention is to have this run Steam and other gaming binaries, not all of which come from the Ubuntu repos (some downloaded deb files, like Heroic Launcher). These are running over VNC (if this is relevant let me know and I can...

Thanks for clarifying the limitations. Filed both: https://bugzilla.proxmox.com/show_bug.cgi?id=6468 https://bugzilla.proxmox.com/show_bug.cgi?id=6469

I have a rarely used VM configured for GPU passthrough, this VM is manually started when needed. The same GPU is passed through to an LXC container that is running most of the time. I have hookscripts on both VM and LXC that stop the other when one is starting. This works pretty well. As part...

Same problem here, virtiofsd's sandboxed child process exits for me as soon as the guest VM tries to initialize _something_. Unclear what triggers it precisely and I can find what the child is logging anywhere. The good news, however, is that enabling the NUMA args in the options list in the...

OK, I've tried multiple installs and upgrade sequences in a VM, and I can't get to the same place. OTOH, based just on behavior I believe I can describe the sequence. - Older versions of Proxmox do not install /etc/default/grub.d/zfs.cfg (I tested 5.4 and 6.4). Instead they generate...

As mentioned in my later post adding the addition disks and pools is not related. I could ultimately reproduce the problem with just the two disks of rpool attached. If you'd still like redacted copies of the files let me know, but I'm reasonably sure that nothing in the additional pools is...

Great, thanks for clarifying. It seems we agree this is something that Proxmox needs to address via some mechanism outside the installer, which was my primary concern.

Understood. My system can boot either method. I was trying EFI boot to test if the problem was specific to Grub. As it turns out, it is specific to Grub, but I mistakenly associated the bug with EFI boot in an earlier post because my system doesn't have the necessary /etc/kernel/cmdline, So...

Thank you, that was the hint I needed. In particular, the parsing of rpool and bootfs. I had previously failed to notice that pve-boot-manager was producing this: Instead of this: Without the pool name, the import doesn't run at all, which explains the lack of error messages. The incorrect...

The rsync worked, though some of the containers won't start for unclear reasons. I'll restore them from backup to fix them I expect. Just to be thorough, I then replaced the working rsync with a zfs send of the same content, and that fails to boot. So whatever is going on seems specific to the...

I've removed the zpool.cache and rebuilt initramfs, no change. I'm now trying to copy (rsync) the old pool content on top of a working 8.0-installer-created rpool, followed by a proxmox-boot-tool refresh. I'll post here how it goes. Its increasingly looking to me like something about the ZFS...

This gets weirder and weirder... 1) Install Proxmox 8.0 from ISO to a new drive using legacy boot. Using 8.0 instead of 8.1 so the rpool doesn't have ZFS features too new for my rescue disk (SysRescue with ZFS). 2) System boots normally with GRUB. 3) Use ZFS send/recv to replicate my old rpool...

No dmesg about disk hardware problems, late or not. And again, adding rootdelay=60 to Grub (via the "e" to edit options during setup) had no effect, so I don't think it's a slow disk (these are SATA SSDs). A different machine with EFI boot has no problems, and I've confirmed this machine will...

Nothing seems amiss in dmesg, and the pool is healthy. Again, the busybox "Command" "Message" and "Error" fields are all blank. Is it possible the zpool.cache is at issue? I'm unclear how that interacts with rpool at boot time specifically, but I see in it the initramfs.

Thank you for the hint, it seems like: > zpool import -N rpool > mkdir -p ROOT/pve-1 > mount -o zfsutil -t zfs rpool/ROOT/pve-1 ROOT/pve-1 Allows the machine to boot into Proxmox. However running "proxmox-boot-tool refresh" doesn't fix the issue, the same thing happens at the next boot. Any...