Recent content by pixel

I also tested with ceph, but my cloud init template only has one nic. Two other nics were added after the clones initial boot. The webui shows blank entries for those nics in cloudinit data, but qm config does not. pvesh get .../cloudinit only shows the added nics even though get .../config...

This is on pve 8.2.4, no-subscription (testing for work, where we do have a subscription) When making cloud init clones, they can be live migrated as long as they only have one nic. With more nics, we get this error root@pve1:~# qm migrate 104 pve2 --online 2024-09-16 22:03:56 ERROR: migration...

Wed like to automate enough of the proxmox installation to take over with ansible after. this means default storage, setting up network, adding ssh keys etc. with ubuntu, i usually make a modified iso for the target machine with preseeded answers and a post install script. is it possible to do...

We script and use pvesh for almost everything. either on the command line or called from python. these python scripts are slow from multiple get calls. are there any hidden pitfalls, race conditions, etc that could happen with getting data by parsing the config files in /etc/pve as opposed to...

which certs should be deleted when the template is made?

thanks! i noticed in the case of this vagrant file, the hosts line reads: 10.12.13.21 node1 node1 pvelocalhost could this cause any problems later on? the vagrantfile could be modified if so. regarding vagrant recreating /etc/hosts, thats not a problem. the hostmanager plugin can be disabled...

heres vagrant setup i have running. if you make the proxmox box, remember to checkout the pve-5 branch. this one didnt fail until trying to use the web-ui. then, the cluster service was killed and /etc/pve was gone. here is the packer file so you dont have to scroll back to find it...

it happened again. this time im keeping the vagrant session running, so you can ask me to do more diagnostics. after vagrant up, i ran "pvesh get /storage" and "ls /etc/pve" to make sure those worked. then tried to log in with the webui. it let me in, but with the node error, the red circle...

it if happens again, ill try that and keep the instance running so other things can be tried.

it happend again while trying to get ceph running. ill try to make the vagrant run reproducible, but heres requested output, root@node1:/home/vagrant# systemctl list-units --failed UNIT LOAD ACTIVE SUB DESCRIPTION ● pve-cluster.service...

wish i could. they were vagrant runs. long gone now. i tried re running vagrant in the conditions that caused the problems, but they no longer do. if it helps, today it all worked, yesterday was when i could reliably cause them. did not update the proxmox image in that time, and none of the...

now i cant get it back in the failed state, which kinda worries me. i hope its because something was fixed. Thanks for the fast responses! Ill try that and revisit this thread if it happens again.

# pvesh create /storage -storage vmspace -type dir -content rootdir,images -path /vmspace if that gets executed after the proxmox vm is up, the gui works. if it is run as part of the provision script, the gui will let you log in, but node1 has the red circle with an x in it. in either case...