Search results

Added both of those changed. It actually made things worse. The transfer bailed at 11.37% done. transferred: 4884463616 bytes remaining: 38065209344 bytes total: 42949672960 bytes progression: 11.37 % trying to aquire lock...Removing all snapshots: 100% complete...done. image has watchers -...

On which Proxmox server shall I perform these steps? The one connected to for UI, the one where the VM is located, or all Proxmox servers in the cluster?

That could be. Timeouts and UI errors do often pop up when deleting large, unused ceph volumes via the UI. (But they do eventually delete behind the scenes.) However, we have tried separating the migration and deleting the old volume, and while the success rate seems slightly higher, it...

Speaking only for myself, we do not.

This happens to us at least 50% of the time as well. It seems to have 2-3 different failure modes that vary in the details, but in all cases it is the same in general: it goes through the entire process and then fails at the very end. Here is one example: transferred: 8589934592 bytes...

I have a very similar problem. On serial console, the boot pauses at exactly the same place with very similar gibberish, but I must type CTRL-C to resume, at which point it boots normally. Did you ever find the cause? INIT: version 2.88 booting Using makefile-style concurrent boot in...

If your VM ID is 101, then it would be /etc/pve/qemu-server/101.conf . Naturally your VM needs to be powered off before hand-changes to this file will take effect.

Oh, if only that were true. :)

vSphere has a feature "Enter Maintenance Mode" where a host can be marked for maintenance, which causes all vm's running on that host to queue up and migrate to other hosts in the cluster in an orderly fashion (i.e. not all at once) so it can be safely rebooted for updates and config changes...

The login was also easier. Which was important because it also logged you out after like 3 seconds of inactivity. :)

Converting our very oldest Proxmox cluster to 3.1. Grabbed this screenshot before shutting the last machine down: http://imageshack.us/f/692/vdpl.png/

Yes, selectively applying only self-tested updates that are confirmed to address a problem you actually have is more difficult than blindly clicking "update all" and hoping for a good result. It is also much better judgement, regardless of what repository you are using. This is enterprise...

Yes, they are very brusque. They are from Austria. This is them, telling you how it is as directly as they can. Without trying to feed into stereotypes, that is how things are done in Austria. They are not trying to be rude. They may slip a little bit in light of the tremendous rudeness...

Both positions are stated maybe a little too strongly. Actuality is somewhere between them. Based on what Dietmar said, packages in the pve-no-subscription repo have been through all of their internal testing. A packages advances from pve-no-subscription to pve-enterprise based on the...

Cannot afford 50 EUR subscription because you are buying too many quad socket servers (minimum!)? OK, but, how much sympathy are you really expecting?

If you say so, I believe you. The KVM source is quite beyond my understanding. :)

It's not clear to what you are referring. Here is the kvm(1) man page: According to this, the telnet and unix backends are exclusive alternatives, not options. Does the kvm source say something different? PORT_NUM = BASE_PORT + VMID seems to work for us as VMID's also share this...

Sure, but as this is a documented feature of the KVM telnet backend and not listed for the socket backend, my hopes are not high. Maybe nobody cares about this but me. If so, probably it is not worth the effort. Of course I would prefer you do the work of assigning and managing port numbers...

The same, ASCII character code 26. CTRL-anything is just a character. Serial break is not a character, it is a signal. It is electrically different (on physical serial ports) and to virtualize it requires special agreement on how to encode it between both sender and recipient, as provided by...

No, that is something completely different, CTRL-C is ASCII character code 3. Serial break is an out of band signal, representing holding the TX line to 0 for a whole frame. Hence it must be emulated.