Category: General Computing

I recently acquired a new Proxmox PVE host and wanted to migrate my existing VM’s without doing anything too crazy with PBS (proxmox back up service) or other storage devices. I also only have local storage, no SAN/NAS setup for the proxmox host. It is a single host, nothing clustered at home right now. So I wanted a simple solution to just lift and migrate. The quickest way I came up with is to use SSHFS to mount on the new box, and then copy the disk and config file over, done. Nothing complicated about it.

Some pre-requisites. The hosts are on the same LAN, configured to use the same subnet and VLAN already. Both PVE are already updated and ready to go on Proxmox 8.4.12.

TL;DR Commands for QCOW2

apt install sshfs -y
mkdir /mnt/pve-target
sshfs root@target:/var/lib/vz /mnt/pve-target
qm shutdown
rsync -ah /var/lib/vz/images// /mnt/pve-target/images//
scp /etc/pve/qemu-server/.conf root@target:/etc/pve/qemu-server/
umount /mnt/pve-target

Step-by-Step Guide

1. Install SSHFS (on source or destination)

On the node where you’ll mount the remote PVE:

apt update && apt install sshfs -y

2. Create mount point and mount remote storage

On source node (where VM currently lives), mount the target PVE via SSHFS:

mkdir /mnt/pve-target
sshfs root@<target-node-ip>:/var/lib/vz /mnt/pve-target

Replace <target-node-ip> with your destination PVE’s IP.

3. Stop the VM to ensure consistent disk

qm shutdown <vmid>

Check if it’s down:

qm status <vmid>

4. Move VM disk(s) to SSHFS mount

Assuming the VM disk is on local storage (/var/lib/vz/images/<vmid>/):

rsync -ah --progress /var/lib/vz/images/<vmid>/ /mnt/pve-target/images/<vmid>/

If the directory doesn’t exist on target:

mkdir /mnt/pve-target/images/<vmid>

You can also use scp instead of rsync, but rsync gives progress and is resumable.

5. Copy VM config

Configs are stored in /etc/pve/qemu-server/<vmid>.conf.

Copy it over:

scp /etc/pve/qemu-server/<vmid>.conf root@<target-node-ip>:/etc/pve/qemu-server/

6. Unmount SSHFS

umount /mnt/pve-target

7. Start VM on target node

Log into target PVE and run:

qm start <vmid>

Check:

qm status <vmid>

Optional Cleanup

If you want to delete the VM from the source PVE:

qm destroy <vmid>

Make sure the migration is successful before doing this.

Tips

• If your VM uses local-lvm, you’ll need to:
  • Convert the disk to a raw file (with qemu-img convert)
  • Or attach the disk as a block device and copy it differently.
    Let me know if that’s your setup, and I’ll walk you through that too.

I am migrating from pfsense to a Unifi Fiber gateway. The first thing I needed to do was to figure out how I was going to get away from the feature rich pfBlockerNG. That thing was a beast, combined with unbound, very customizable. But i’ve been using it for 6+ years, it’s had its quirks and I am ready to try something new. The internet seems to be saying AdGuard Home is the new champion in DNS for selfhosters. It is no longer pi-hole (thick and heavy php stack requirements), nor is it technitium (to new, not open source) and I would never use nextdns due to its cloud/internet requirement. AdGuard Home is written in go, has a sleak reporting function and it has DOH and DOT built in, unlike Pi-Hole. For whatever reason, the developers of Pi-Hole do not think DNS needs to be encrypted, so they’re off the list.

Setup of AdGuard Home was super simple. I threw it on a pi running latest raspian. Went through the quick wizard and off I went. First step was to setup my upstream DNS servers. I chose these:

https://dns10.quad9.net/dns-query
https://dns.cloudflare.com/dns-query
https://dns.mullvad.net/dns-query
https://dns.google/dns-query

To get DOH to work, you need to do a 53 DNS lookup. I did not like that idea. So in the bootstrap section, you can actually use an 853 TLS/DOT look up. So I put these in:

tls://1.1.1.1
tls://8.8.8.8

I watched the traffic with tcpdump on my current router, and boom, all 853 to 443 traffic for lookups. I blocked all 53 traffic on WAN and it’s functioning perfectly.

I then dumped in my custom DNS black lists I have accumulated over the years. As well as a few DNS rewrites and then my preferred DNSBL. If you need help with a good set of lists, I would start with the green section for firebog:

https://firebog.net

That was it, now i’ll let AdGuard Home slowly cover all my internal DNS needs and watch it work. So far I enjoy the metrics over pfBlockerNG. I will miss pfBlockerNG, but it’s nice having something built quite simply.

I run into this a lot when I travel, or live in different parts of the world for a little bit. Example, my search results are showing up as BE while I am in Thailand. And as of Sep 22 2023, it looks like Google changed the way you modify this. So this is an update to what I previously posted November of 2022:

Same issue, slightly different way to fix it. Caveats, you will need to be logged into a Google account to fix. And protip, set your homepage to ncr, as that will not give you a region lock either: https://www.google.com/ncr

Click on Settings then Search settings in the bottom left:

Select other settings on the left, and then Language & region

Then select results region

Then search for and select your region and click on confirm

Then you are good to go. Enioy your search results.

This started happening a few days ago. Super annoying and takes up an extra folder or two in my bookmarks bar. But it can be removed. You can remove it by opening a new tab and typing:

 about://flags

Scroll to “Power bookmarks side panel” and change it to disabled. It will require a chrome relaunch.