Search results

Thanks! Mild PTSD from prior incidents with fdisk on spinning rust.

This seemed like it should be a fairly straightforward process, but I've hit a snag getting the OS to fill out its available space. I started on the PVE host with: qm resize 104 scsi0 +20G which immediately became visible in root@pve1:~# cat /etc/pve/qemu-server/104.conf ... scsi0...

https://www.phoronix.com/scan.php?page=article&item=linux-2019-features&num=1

Is it possible to direct pveperf to test a specific HDD (other then /dev/mapper/pve-root)?

Found some threads about dnsmasq-base being installed ahead of dnsmasq and creating this sort of conflict, from which came a helpful lsof query, which seems to indicate that systemd-resolve is shimming something: root@pi-hole:~# lsof -Pn +M | grep ':53 (LISTEN)' systemd-r 74 systemd-resolve...

Just tried installing pihole on an LXC here and hit the same blocker. Apparently, port 53 is already bound in the LXC: May 11 17:09:11 pi-hole systemd[1]: Starting dnsmasq - A lightweight DHCP and caching DNS server... May 11 17:09:11 pi-hole dnsmasq[88]: dnsmasq: syntax check OK. May 11...

I noticed the pve-template update this afternoon and was able to build a template using DAB. Looks like it pulled a lot of stuff we don't usually want or need (including some x11 stuff) -- template ended up ~3X the size of others we have. Is there a guide for pruning the appliances of unwanted...

Right -- hence my (at least mostly) confined qualifier above. I've asked the app developers to craft an appropriately limited AppArmor profile, but they have more important priorities. This really seems like something that LXC and Docker should have worked out by now.

Thank you. You guys really do rock this thing -- and Happy Birthday!

I created an LXC of 17.10, edited the /etc/apt/sources.list and did a dist-upgrade (lengthy). Now: # lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu Bionic Beaver (development branch) Release: 18.04 Codename: bionic which looks...

Bionic Beaver ships this week. I would like to start building some test machines and am wondering how to create a template using DAB. Substituting names and numbers into an existing dab.conf returns unsupported debian suite 'bionic' when I try to init. Seems DAB is dependent on some backend...

This started with me trying to find a way to run Docker in an LXC while leaving the container (at least mostly) confined. That turned out to be nontrivial. KVM overhead is significant, so I've been looking at ways to reduce that, along with the hassle of continuously updating VMs. Container...

My first experiment with CoreOS / Container Linux. Spun up a KVM with the current stable ISO as its CDROM. Booted, then created a static.network per https://coreos.com/os/docs/latest/network-config-with-networkd.html and restarted systemd-network. Verified connectivity. Then used sudo...

VLAN-aware switch was blocking tagged VLAN packets. Added 88/tagged to both router and switch ports and we have ignition! Thank you for the help on getting 8021q loaded. I do believe the 8021q module should be configured for loading whenever a VLAN is added to a linux bridge or an OVS bridge...

Link doesn't clearly indicate which post, but if it's the one two posts up (about creating a VM on 10.0.10.0/24) perhaps I wasn't clear -- here's what I tried yesterday: Added vlan_mode=native-untagged to VM OVS options. Rebooted node, started VM106 -> no success connecting from existing VM106...

There is currently no firewall ruleset on that interface and no reference to that /24 anywhere else in the router config. I can delete eth2.88, assign 10.0.10.1/24 as a secondary address on eth2, remove the VLAN tag from the VM network options, start the VM, and it will ping the router interface.

That was next on my list to try. All three modules are loaded, but still no connectivity. Do kernel modules always load before startup scripts are run?

Yet no ping still: root@pve1:~# ping 10.0.10.1 PING 10.0.10.1 (10.0.10.1) 56(84) bytes of data. From 10.0.10.20 icmp_seq=1 Destination Host Unreachable From 10.0.10.20 icmp_seq=2 Destination Host Unreachable From 10.0.10.20 icmp_seq=3 Destination Host Unreachable From 10.0.10.20 icmp_seq=4...

Bingo! root@pve1:~# lsmod | grep 8021q root@pve1:~# modprobe 8021q root@pve1:~# lsmod | grep 8021q 8021q 32768 0 garp 16384 1 8021q mrp 20480 1 8021q Thank you for the help. Perhaps PVE should load this module when/if a VLAN is defined...

And the relevant portion of 'ip addr' on the router (forked from VyOS): 42: eth2.88@eth2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default link/ether 04:18:d6:a0:8d:44 brd ff:ff:ff:ff:ff:ff inet 10.0.10.1/24 brd 10.0.10.255 scope global eth2.88...