Search results

Interested too for my "workstation" :)

Basically your containers are running the host kernel, therefore we're just bind-mounting the host kernel modules into the container (readonly). You'll need to repeat this step after an pve host kernel update.

Try; pct set xxx --mp0 /lib/modules/$(uname -r),mp=/lib/modules/$(uname -r),ro=1

Awesome and thank you for your hard work!

Hm...you could just install a lightweight desktop environment like xcfe or mate and use the Proxmox server as desktop. Some hints: https://pve.proxmox.com/wiki/Developer_Workstations_with_Proxmox_VE_and_X11

oot@barney:~# cat /etc/pve/storage.cfg dir: local path /var/lib/vz content images,iso,vztmpl,rootdir maxfiles 0 zfspool: rpool-vm pool rpool/vm content rootdir,images sparse 1 zfspool: rpool-non-critical-vm pool rpool/non-critical-vm content images,rootdir sparse 1...

root@barney:~# qm config 9000 balloon: 1024 boot: c bootdisk: scsi0 cores: 2 ide2: barney:9000/vm-9000-cloudinit.qcow2,media=cdrom memory: 2048 name: cloudinit-template-ubuntu net0: virtio=E6:13:14:1F:0C:A9,bridge=vmbr0 scsi0: barney:9000/base-9000-disk-0.raw,size=2252M scsihw: virtio-scsi-pci...

I've got a template created like this: qm create 9000 --balloon 1024 --memory 2048 --cores 2 --net0 virtio,bridge=vmbr0 -name cloudinit-template-ubuntu qm importdisk 9000 /mnt/pve/barney/template/ubuntu-18.04-minimal-cloudimg-amd64.img barney qm set 9000 --scsihw virtio-scsi-pci --scsi0...

Yes, container templates are working this way, but I'm talking about KVM templates.

Hi! I really love the cloud-init integration and with the templating, it's really easy to spawn new vms. However, i'm unable to create a template for the whole cluster. I'd like to have a template on some kind of shared storage (like NFS) and create full clones of this template on all nodes...

Looks good so far. Does hostname --ip-address return the correct ip of the server?

Okay, just tried with spanish debian, also works without hassle here. Can you post your /etc/hosts and /etc/network/interfaces before setting up the cluster?

I don't think so, but hey, i've seen many bogus things in my career already ;)

Status: Quorum information ------------------ Date: Fri Sep 7 14:51:36 2018 Quorum provider: corosync_votequorum Nodes: 3 Node ID: 0x00000001 Ring ID: 1/12 Quorate: Yes Votequorum information ---------------------- Expected votes: 3...

Jip, this was the file before adding all the other nodes. I've added 2 other nodes and the cluster was working.

Okay, tried and it worked. Installed with Debian with english language. Installation failed first time with errors, but that was due to wrong /etc/hosts. - Make sure to follow the steps...

I'm pretty sure they know as Proxmox is based of the same system, just a different installer ;) I can try to tinker with the problem tomorrow in our lab.

Anyway you could try to test if it's working using omping ... Might be that PVE installer sets other kernel or sysctl vars which are likely missing in Debian stock setup and might affect this.

Multicast issues probably? https://pve.proxmox.com/wiki/Multicast_notes https://pve.proxmox.com/wiki/Multicast_notes#Using_omping_to_test_multicast

Just tried to build the latest ubuntu packages for stretch. Builds and installs fine: https://nextcloud.morph027.de/s/cloud-init-stretch