Search results

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

thanks. what other operations take storage-wide locks? is this lock on proxmox or ceph side?

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

needed an automated check. using this for now. [ `ls -tr /boot/initrd* | tail -1 | cut -d '-' -f 2-` != `uname -r` ] for ansible users:

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?

couldnt find it in the gui, but its in pct.

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.

telnet? do you mean ssh? can you show the output of "ss -plnt"?

another approach is to use configuration management such as puppet or ansible for vms and only backup data.

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

the first time, i did try twice. then turned off both the ceph cluster and proxmox. turned them back on again to try again, and it worked fine the first time. made two more containers, then delete both, and that worked fine too. note that i did not build from git, just made the one line change...

Just tried removing the vm and container. vm removed fine. container could not remove the rbd, saying the image still has watchers. 2016-06-14 04:35:12.051159 7f7c8845a780 -1 did not load config file, using default settings. Removing all snapshots: 100% complete...done. 2016-06-14...

updated proxmox test machine on pve-no-devel and applied your patch by hand. both lxc and kvm worked. can you post here when the fix is applied to subscription? then ill try it at work.

yes.

just tried with proxmox 4.2 pve-no-subscription and ceph 10.2.1 on ubuntu xenial. the ceph storage summary is correct in storage space, so that parts working. but, when i try to create a vm or container, 2016-06-13 02:39:38.758477 7f72dde10780 -1 did not load config file, using default...

By soon can you give a rough estimate to help with planning? We plan on running in test / dev mode for 2-3 weeks before production. P.s. thanks for such a fast response on a weekend! Did not expect that

http://pve.proxmox.com/wiki/User_Management theres also a "protected" setting for virtual machines to prevent accidental deletion. its safer to just give his own server, or a virtual machine with nested virtualization enabled.

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

If we already have a ceph cluster running jewel, is it possible to use it with proxmox without breaking your future plans? theres no /etc/ceph directory, or ceph.conf anywhere, so where are these things set? i tried installing jewel from cephs repository, and it worked just fine for both kvm...

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.