Search results

Are you sure that UEFI does not give a lot of troubles if UEFI install was used?

I'm interested also in a SAN as storage, but keep in mind that with iscsi you can't have snapshots, that is a very important feature to me, see https://pve.proxmox.com/wiki/Storage I've seen VmWare similar setup but they have snapshots instead, sigh

Did you issued a apt update to update your local repository first?

I think that the decision was made when you, correctly, removed DRBD9 support after they changed the license of a vital component of it. After that they reverted their decision and went back to a FOSS license again, but you did not re-included DRBD9. Since is FOSS, they can't forbid you to...

It's simple, Proxmox already uses a lot of technologies other have create (i.e. ceph), but provides the necessary plugin, adjustments and corollary software support / compatibility check/fix that makes 'the whole package' work smoothly, especially when you update a server. Let's say you...

Sorry if I repeat myself, but really proxmox team should consider to support DRBD9 AGAIN. We that are very small can't afford Ceph (that officially requires at least 3 nodes, but not in production because is not "safe" this way), while with DRBD9 you can have 2 storage node and one very small PC...

I can't tell you the solution but only that an easy way to find other part of the configuration where your old public IP could be saved is something like rgrep 41.213.15 /etc so you can find all the occurrence of the IP in all the files under /etc and it's subdirs but don't know if it can be...

Yes, sorry, I'm wrong, I confused it with ionice

note that -bwlimit works only for the "cfq" scheduler, now the default is "deadline" that works much better IMHO but makes the bwlimit option useless,

Just a shot in the dark: have you disabled all the power-savings / hybernate / whatever INSIDE the vm? Set to "power hungry/high performance" profile and fine tune sub-settings that can cause anything to go in sleep mode.

Don't know if I'm facing the same issue, but I've run in 5.1 "dormient" Win10 VM, with spice and virtio 141, created pre-5.1. If I start the vm, I've a sort of blue screen after the "window" icon splash and some time of the sort of hourglass-substitute, before the login. If I take a snapshot of...

Just to add that for .lzo compressed files the syntax is like this (the -c in lzo is fundamental to have output in stdout): lzop -d -c file.vma.lzo | vma config - I got it from Storage.pm, having the source code is GREAT, long life to FOSS :)

I do need this feature too! In addition, if you have 2 vdi and only one is flagged for backup, you are not able to restore only that one, you have to restore the "entire" vm (after you have deleted it) loosing the disk that was not backed up. So think about a OS disk + data disk, you do the...

They made the mistake to change license, but they have reverted their decision after a short amount of time but Proxmox never reconsidered DRBD9. As far as I know, drbd9 is the only way you could have a 2 storage node + 1 quorum node cluster, reducing a lot the cost of a HA solution. Also DRBD9...

Don't know about upgrades, but fresh 5.0 install uses CFQ chedule, while 4.x abandoned it in favour of Deadline variant, that for me worked far better. check what scheduler you have # cat /sys/block/sda/queue/scheduler noop anticipatory [deadline] cfq (above deadline is the active one) If you...

Not a solution, but I briefly tested this some days ago, and I had it working only *after* having FIRST connected through Web GUI and spice console, then closed that console, and tried with the script. After that it worked with the script, but I did not tried a reboot of Proxmox to test if is...

I don't understand if you were able to make your omping test work (you have to run it at the same time in all nodes), from your pasted output seems it just failed (or you did not it right).

You should use apt dist-upgrade, not only "upgrade", see the wiki, otherwise you risk that some package are not updated at all.

Just for curiosity, how can you tell so? I mean, grepping I find no "prox03" and only 2 lines with it's IP (192.168.1.3) that are: Aug 9 11:34:03 prox01 corosync[2539]: [TOTEM ] A new membership (192.168.1.3:24356) was formed. Members joined: 3 ... Aug 9 12:09:16 prox01 corosync[2539]...

Q.: How much time does omping replies need to complete? (especially, when you see the failed to receive messages) A.: since the problem does not happen at the same time, I can't test during the failed to receive without some luck. I've tested now (and everything is fine now) with this result #...