Posts

On AlmaLinux, the guest-tool for XCP-ng is provided by a package named xe-guest-utilities-latest, which in turn is available from the epel-release repository. The following list a few steps to get XCP-ng guest-tool installed on a VM running AlmaLinux 9. Enable epel-release repository if not yet enabled by first installing a package called epel-release. In my case, the repo has been already enabled. [root@xoa1 ~]# rpm -q epel-release epel-release-9-7.el9.noarch Install the guest-tool. If you’re unable to remember the full name of the package, just search for xe-guest. [root@xoa1 ~]# dnf search xe-guest Last metadata expiration check: 3:41:49 ago on Mon 16 Oct 2023 16:34:47. =================== Name Matched: xe-guest ================================== xe-guest-utilities-latest.x86_64 : XAPI Virtual Machine Monitoring Scripts [root@xoa1 ~]# dnf install xe-guest-utilities-latest -y ... Installed: xe-guest-utilities-latest-7.30.0-7.el9.x86_64 [root@xoa1 ~]# rpm -q xe-guest-utilities-latest xe-guest-utilities-latest-7.30.0-7.el9.x86_64 Finally, enable and start the xe-linux-distribution service. [root@xoa1 ~]# systemctl enable --now xe-linux-distribution.service Created symlink /etc/systemd/system/multi-user.target.wants/xe-linux-distribution.service → /usr/lib/systemd/system/xe-linux-distribution.service. [root@xoa1 ~]# systemctl status xe-linux-distribution.service ● xe-linux-distribution.service - Linux Guest Agent Loaded: loaded (/usr/lib/systemd/system/xe-linux-distribution.service; enabled; preset: disabled) Active: active (running) since Mon 2023-10-16 20:20:11 AEDT; 12s ago Process: 1714 ExecStartPre=/usr/sbin/sysctl net.ipv4.conf.all.arp_notify=1 (code=exited, status=0/SUCCESS) Process: 1715 ExecStartPre=/usr/sbin/xe-linux-distribution /var/cache/xe-linux-distribution (code=exited, status=0/SUCCESS) Main PID: 1720 (xe-daemon) Tasks: 9 (limit: 23054) Memory: 7.1M CPU: 42ms CGroup: /system.slice/xe-linux-distribution.service ├─1720 /usr/sbin/xe-daemon └─1723 logger -t xe-daemon -p debug Oct 16 20:20:11 xoa1 systemd[1]: Starting Linux Guest Agent... Oct 16 20:20:11 xoa1 sysctl[1714]: net.ipv4.conf.all.arp_notify = 1 Oct 16 20:20:11 xoa1 systemd[1]: Started Linux Guest Agent. The guest-tool for XCP-ng has now been installed on a VM running AlmaLinux (9). ...

Do you know? Well, before today, neither did I. I’m pretty late to Kubernetes. I heard about it many hears ago, but unfortunately, I had no need to use it at home or at work. Even today, there is no workload that requires a Kubernetes cluster to run on. However, I think I can’t ignore Kubernetes any longer, and I need to learn about it now, well “better be late than never”, right? ...

I use ’tmux’ on anything that runs it, from FreeBSD, macOS and Linux. On some of my Linux servers, noticeably openSUSE ones, when I connect to them via SSH, I would receive the following warning: ... Have a lot of fun... warning: Could not set up terminal. warning: TERM environment variable set to 'tmux-256color'. warning: Check that this terminal type is supported on this system. warning: Using fallback terminal type 'ansi'. What worse is that, when I switch to root account, the backspace key doesn’t work correctly. For example, hitting backspace will produce a space instead. ...

During the upgrade of Fedora 38 to Fedora 39 (beta) on my main desktop, the first attempt failed due to insufficient free disk space on the root volume. After some manual intervention such as vacuuming the journald logs, I was able to perform the successful upgrade. Not that it matters, but I’m writing this blog post on the same desktop running Fedora 39 Beta. This post is to record how I increase the root volume on my desktop with the help of a few tools such as growpart, lsblk, resize2fs,…etc. Like always, if you stumble on this post and want to follow along, please do not just copy and pate the commands from here and run on your system. Try to understand what each command does, if you don’t, then you definitely must not copy and pate these commands! ...

In this post, I’ll document how to use AWS CLI to delete a few Lightsail resources. I have never done this before, so this would be a good exercise for me. To make it less boring, I’m writing this post while I’m deleting these resources. First step, I need to look for the instance name [1]. ❯ aws lightsail get-instances --query 'instances[].name' [ "WordPress-1" ] The above output is the name of the instance I’d like to delete. With its name, the instance can be deleted using the following command line [2]: ...