Search results

Some PGs where in undersized status, It's now fixed. But my main question on how to find out the commands which is being ran by each task is not answered yet. do you know how to?

I just tried to create a VM on CEPH via GUI but it got timeout from RBD, after that I've tried to create VM via command line and it seems to be OK, so I wonder if there's any way to find the command which GUI is running to create VM on CEPH? TASK ERROR: unable to create VM 102 - error with cfs...

I'm planning for a Proxmox cluster consisting of 3 nodes for compute and 3 different nodes for Ceph with SSD, And it's important for me to have HA but I'm concerned about possibility of starting an already running VM on different node by HA controller in case of a network issue. Does proxmox...

qm suspend doesn't hibernate the VM, it just halt it.

I didn't find proper qm command options to hibernate or resume a VM via terminal, Would you please let me know what are the options if any?

Because of our custom code on top of Proxmox, which presumes the fist disk is from 1, If there's no way starting it from 1, we will adapt our code. is there?

Recently I can see in latest Proxmox version, it's making disk files from 0 index while previously it was from 1, Is there any way to ask it for creating disks from number 1? The command which I'm using for creating new VMs via SSH is: /usr/sbin/qm create 100 --name s100 --net0...

it's my sources.list file: deb http://ftp.nl.debian.org/debian stretch main contrib deb http://download.proxmox.com/debian/pve stretch pve-no-subscription # security updates deb http://security.debian.org stretch/updates main contrib But installed ceph is 10.2.5

I'm using latest Proxmox 5.1 but `pveceph install --version luminous` is installing ceph 10.2.5 which is jewel not luminous And therefor it can't mage ceph-mgr so the setup fails. Is there anything more than what this link guided that I should do to setup proper ceph luminous on Proxmox...

Please take a look at VMWare snapshot best practice, https://kb.vmware.com/s/article/1025279 "Do not use a single snapshot for more than 72 hours." It's not just VMWare or me, I've headed the same opinion from many sys admins, do you keep snapshots for long period of time out of lab?

In production, snapshots are temporary files, therefor creating a qcow2 file for few hours and then merging it back to RAW file will not make much of performance issue, while it offer flexibility. for example I want to upgrade the database server version in that case I can create a snapshot, do...

Did you try `blockdev-snapshot-sync` command? You can use it like this: ( while drive-ide0 is a RAW file ) { "execute": "blockdev-snapshot-sync", "arguments": { "device": "drive-ide0", "snapshot-file": "/var/lib/vz/images/100/vm-100-disk-1-snap-1.qcow2", "format": "qcow2" } } This will create a...

As the RAW files has the best IO performance comparing to other supported file formats bye Qemu, I prefer to use it for my database VMs, But Proxmox doesn't support snapshot of RAW files while there's a command in Qemu `blockdev-snapshot-sync` which can successfully handle snapshots of RAW...

Any experience on this case? Does vzdump have any option for it?

I've a VM on a disk with I/O error, I want to make backup of that VM while it's running, therefor it's not possible to use dd, Is that possible to ask vzdump to continue on I/O error of source disk?

I want to try the sample below but I cant run some commands http://wiki.qemu.org/Features/Snapshots2 The commands that I've issue with are: change -l drive-ide0 file=/var/lib/vz/images/101/tempdisk.img -> which lead the -l is not a device merge_disk -> unknown...

I've asked in dev mailing list why they didn't implement it yet, but no one answered. Other people who are in need of this feature or interested in it please ask in mailing list why it's not in road-map of Proxmox this way maybe they change their mind to implement this need of enterprise feature.

It's not good, because it will compare the backup with live disk of server and make incremental backup, while the Qemu has dirty bitmap feature which will remove the compare part of incremental backup process, So with the patch you've mentioned an incremental backup will also take long time and...

I am ready to donate for this feature to be implemented in Proxmox, Please let us know Tom ( or other Proxmox dev team ) if you want to add this feature to Proxmox

I found these which are not useful that much. http://pve.proxmox.com/pipermail/pve-devel/2014-September/012776.html http://pve.proxmox.com/pipermail/pve-devel/2014-February/009916.html