Using Qemu Tools

While moving virtual machines from my unraid NAS to my new proxmox node way back when, I ended up needing to use a few of the qemu-img tools. This is a toolset for handling virtual disks used by kvm/qemu.

Conversions

Something I hadn’t realized while using unraid as my kvm host was that it wasn’t always using qcow2 format, which was my go to format, despite that the webui saying that the file format was qcow2. There were also a few virtual machines I made that ended up in different forms, so to handle these, I ended up having to convert the machines using the following commands.

The first command is to convert from a raw image to a qcow2 file.

qemu-img convert -f raw - O qcow2 /path/to/file.img

The second command is to convert from a qcow to a qcow2 file.

qemu-img convert -f qcow2 -O qcow2 /path/to/img.qcow

File Information

The other command I made use of was the info command from the qemu-img tool. This gives out useful file information for the file input to the command.

qemu-img info

These are just some useful, small commands in the qemu toolbox that can help significantly when working with the VM disk files directly.

Cleaning up the blog backlog

I have… quite a few blog posts in my backlog, many of them being most of the way done, with others missing information, screenshots I’d like to include etc. These may be short, could probably be expanded upon with more information, but never will be. So in the next few days I’ll be finishing them up to a short quick bite blog post and posting them up (else they’ll never be finished).

Unraid api causing the webui to fail to load

So recently my unraid webui has been running slowly, sometimes not showing the list of drives for a minute or two, or not at all. This finally culminated in an http 500 internal server error when I tried to load the main page. This isn’t good, and I was still able to access the server over ssh and via smb/nfs, so it wasn’t completely dead.

Time to debug over ssh. I first went to top and saw that shfs was at 100%+ CPU usage. This felt like an odd program to be using more than one CPU core of performance. I then went to the syslogs and saw lots of failed login attempts from a specific IP address. This wasn’t one I recognized, but I thought it might be a container I’m running (unraid api specifically).

I then went and ran docker ps to get the list of containers, and more importantly, the name for my unraid API container. I then ran docker inspect on that container and found it had the IP in question. Finally I went and ran docker kill on the container and the unraid webui started responding again. I guess I had misconfigured the container so it was falling to login, and retrying aggressively enough to stall out the webui.

Note to self, apps that scrape the webui should be configured correctly or else they may have some unintended consequences.

Using ntfy.sh to send unRAID notifications

unRAID supports multiple notification platforms for keeping you informed about what the server is doing, the only problem is, I don’t use any of those notification platforms. I have however started using ntfy.sh, which has been working well for my home assistant notifications, and is a very simple platform. What I’d like to do is integrate it into unRAID so that I can make use of it there as well.

Continue reading “Using ntfy.sh to send unRAID notifications”