Recent content by tessus

This is my problem. I do not have a descriptive name for them. These 2 physical adapters are used in a LACP (bond0) . The descriptive name that is used right now make the most sense, because they even describe the location of the adapters. Maybe I just call them link1 and link2. I read that...

What are my options then? Better yet, how do I keep my current if names? I guess only interface names for physical adapters would change. The bond and vbr names should not be touched, correct? So the best course of action would be to use the pinning tool and change the generated interface names...

Thanks for the info, Stoiko. Ok, I ran pve8to9 --full, but it didn't complain about systemd-boot. I got 2 warnings: one that VMs are running and the other that the amd64-microcode package was not installed. Both of which I will take care of when I upgrade. However, I am more concerned about my...

It rebooted but the Proxmox upgrade doc suggests to remove it. The only reason I manually installed it was because I was told so in this topic.... So what shall I do? Do I unstall it or not? And when? Before or after the upgrade?

After booting a Proxmox node, a VM that was set to autostart failed to do so due to storage 'iscsi-storage' is not online As you can see from my great naming, the storage is an iSCSI disk image. Usually that storage is always available, unless I boot up the NAS with the iSCSI target at the same...

Thanks, I've installed it now. Let's see, if it really reboots the next time. Haha. ;)

Thanks for the reply. I've been running 8.x since it was released (upgraded from 7), so I am still a bit fuzzy on why I see this message only now. Either way, the output of proxmox-boot-tool status is the following: # proxmox-boot-tool status Re-executing '/usr/sbin/proxmox-boot-tool' in new...

I got the following error message during today's apt-get dist-upgrade: E: bootctl is not available - make sure systemd-boot is installed As far as I remember this is the first time seeing this message during a kernel update. I haven't modified the system by uninstalling random packages, so I...

I would open a new issue in the forum and maybe start a poll. As mentioned before, automatic folder structuring was not my initial feature request and I still would like to see my initial request to be implemented at one point. Although it seems that using tags is the devs' only way going...

Interesting addition. Personally I was looking for creating folders manually and adding VMs to those folders manually as well. I wanted to use a combination of folders and tags. Your solution by creating a folder structure based on tags is also nice, but doesn't fit my use case. But I can see...

Thanks for the reply. Yes and no. Yes, as in you can use tags for bulk actions and color coding your VMs. No, because you currently still have potentially hundreds of VMs within a single folder. This is not very manageable. It's not too user friendly either. I'm not saying it absolutely...

I was wondering whether a feature request is possible or even feasible. I have a lot of VMs and I have noticed that managing them via the UI can become rather tedious. Thus it would be very useful to be able to create folders, in which I can put the VMs. The possibility to add tags was a step...

Perfect, that worked. Btw, I wrote the command this way on purpose. It's supposed to test using quotes, a pipe, and a redirect. ;-) The following worked: pct exec 803 -- bash -c 'echo "test" |cat >/tmp/t'

Hmm, ok, let me try this again: I want to run the following command in the container via pct exec: echo "test" |cat >/tmp/t Thus after running this command there should be a file t in the /tmp directory of the container.

I've been reading the documentation, but I don't get pct exec to work. The documentation seems a bit off as well. It says: pct exec <vmid> [<extra-args>] [OPTIONS] Hmm, so where is the command supposed to go? How does escaping|piping work? There are no examples whatsoever in the entire...