Recent content by blueduckdock

Thanks for the reply aaron. I did get some time to mess with it and I think I've "solved" it (not really- it's just impossible at this time to do what I'm looking to do.) For reference for anyone wishing to do the same- you can template out and clone qcow2 easily enough (using linked clones...

I did some searches but didn't quite see what I'm looking for. Right now I use the terraform proxmox provider to provision Fedora CoreOS nodes (among other things.) This all works decently well save the fact that clone is quite slow (when doing multiple at once). This basically (I think) is due...

For those who don't wish to use the nfs from zfs, I found this. I haven't yet tested it but I tried the same avenue as OP and it failed. https://askubuntu.com/questions/988968/which-zfs-command-systemd-unit-to-depend-on-to-ensure-that-a-mountpoint-is-avail The basic premise is to just create a...

As an update, this was solved by a reboot. Didn't think there should be much difference as after I edited the fstab I just did a mount -a. But yeah, a reboot fixed it and now the node sees all the containers just fine.

So I used a mount point as outlined here: https://forum.proxmox.com/threads/mount-nfs-on-node-works-on-lxc-debian-container-not.33899/ The NFS mount to the host is mounted simply via fstab on the host (not through the proxmox gui) and then presented to the container which appears just fine. The...

I know this is not the best practice but is just for a homelab. I'm not looking for HA really in the sense I want automatic migrations and such- just would like to have 2 nodes that can distribute the workload and I can migrate when I go to upgrade one node, then migrate back, upgrade the other...

Perfect. Thanks mate. I'll give that a go.

Hey all, had this going in a container for a long time but was using this: lxc.aa_profile: lxc-container-default-with-nfs I think it had been yelling at me that it was deprecated for some time and lo and behold, after an upgrade it stopped working. I commented it out and the container starts...

That is an awesome video. Very easy to follow along, etc. I'll keep this in mind for a project I'm working on. Thanks

Had the same issues but not in Linux. Not sure why but my Windows boxes are sucking with it but not FF on Linux (Fedora.) I'll try to check if e10 is enabled on just Windows for some reason (kinda makes no sense as both sides have the same addons.) Edit- My windows does NOT have e10 enabled...

Is there any issue with mouse movement with a noVNC console now? I am running the latest updates on the non-subscriber repo on my homelab. Used to be just fine (no new VMs) but now is not transferring anything to them. Qemu agent is installed on some, not on others. Keyboard still works. I do...

Making progress- Add this little magic to your conf (changing for your case) hostpci0: 03:00.0,pcie=1,driver=vfio hostpci1: 03:00.1,pcie=1,driver=vfio Thanks to all for the help. Just not seeing the interfaces in pfsense now. Not sure why.

Much appreciated. Pro tip people- don't forget the underscore between intel and iommu (literally the only mistake.) But now I'm getting () kvm: -device vfio-pci,host=03:00.0,id=hostpci0.0,bus=pci.0,addr=0x10.0,multifunction=on: vfio: failed to set iommu for container: Operation not permitted...

Now I'm getting "iommu group can not be found- the file or folder doesn't exist" Now if I do the # find /sys/kernel/iommu_groups/ -type l I do not have anything there. Been through a couple reboots but no joy. Do I need to modify the kernel in any way? I thought I remember reading that the...

bootdisk: ide0 cores: 2 ide0: local:115/vm-115-disk-1.qcow2,size=34G ide2: none,media=cdrom machine: q35 memory: 2048 name: pfsense numa: 0 onboot: 1 ostype: other smbios1: uuid=416b260d-f5ab-47b7-baf7-75ff6d3cac84 sockets: 1 startup: order=1 Edit- well that's odd. Not sure where my hostpci...