Search results

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...

running proxmox 5beta2 in vagrant (libvirt/kvm) using this packer build, https://github.com/rgl/proxmox-ve/tree/pve-5 when running any pvesh commands from the provision script, the gui seems to be disabled. the first time i look, the node is replaced by a red "node1", after logging out and back...

trying to get data on a volume, $ ssh root@prox1 pvesh get /nodes/prox1/storage/ceph/content/ceph:vm-108-disk-1 Can't locate object method "root@pam" via package "PVE::RPCEnvironment" at /usr/share/perl5/PVE/API2/Storage/Content.pm line 222. root@prox1:~# uname -a Linux prox1 4.4.35-2-pve #1...

using ceph for storage, when trying to delete more than one container or vm at the same time, the task fails with (in the tasks log) Error: unexptected status details of that entry: trying to aquire cfs lock 'storage-ceph' ...TASK ERROR: got lock request timeout proxmox version 4.4, linux...

on ubuntu, i just look for /var/run/reboot-required. just did an update on proxmox machines, and saw that the kernel was updated. but theres no /var/run/reboot-required. is there another file to look for?

for lxc containers, it would be nice to have an option for ssh-keys and disabled root password. we did this at work by making a custom lxc template. it has our keys and disables the password on boot. but, i think it would be a nice option for other users.

its there at work (subscription repo), but not at home (pve-no-subscription repo). only 9 available templates show.

For using proxmox 4.2 with an existing jewel cluster, from the ceph jewel release notes, you need "rbd default features = 1" in the client section of ceph.conf. but i dont see a ceph.conf anywhere. is there somewhere else this can be set? in a test cluster of virtual machines, did proxmox 4.2...

is it possible to script the download of an lxc template? https://pve.proxmox.com/wiki/Linux_Container has everything but that step on the command line. i see it at http://download.proxmox.com/images/system/ but not the signature to verify it.

As the title says, can you make an option for lxc to use ssh keys instead of passwords? I realize you can set this manually, but i like to keep things automated. or, workaround (easier than dab): untar a template (with 'p' to preserve permissions), add your ssh key, and add "/usr/bin/passwd...

after installing proxmox4 to vm for testing, removed the enterprise repo, and added the no subscription one. first apt-get update gets a gpg error. and, i cant install unzip, which is in the main debian repository, https://packages.debian.org/jessie/unzip. also tried parted. is there something...

https://gist.github.com/xahare/116034564973ab7648cb have fun.

Can someone well versed in the pve cluster stack please write a cluster troubleshooting guide? in http://forum.proxmox.com/threads/16814-RGManager-won-t-start?p=86859#post86859 maybe, by default this should start with "<rm/>" when i did my test, i had to start rgmanager by hand. (ansible...

Im sure this is covered somewhere, i just cant find it. How do you make a quorum only node in a cluster that you intend to upgrade to 4.0 (so not using a quorum disk)? in other words, a node thats only there to maintain quorum and wont run any instances. in my case, i have 3 real nodes, and id...

we have a real cluster (3.4 supported version with kernel 3.10) and ubuntu 14.04 / ceph giant where this stuff works. test "cluster" is single proxmox 3.4 (kernel 3.10) node connected to 3 node ceph cluster, all are vmware fusion virtual machines. guests on them run fine with local storage...

We have 3 nodes of proxmox 3.4 under support and a separate ceph cluster running in ubuntu 14.04. would like to update to hammer on the server. will the clients be ok with the pve repo or should we add the wheezy ceph repo to the pve nodes?

has anyone run proxmox IN lxc? i was thinking of trying that for testing as it would reduce one layer of virtualization if it works.

microsoft wants a separate license for each possible physical node a vm can run on. the software is licensed per physical computer. is there a way to limit the failover node so we only pay twice as much for windows server licences instead N times as much?