Search results

This weekend I upgraded a Proxmox VE 3.4 cluster to Proxmox VE 4.1. Everything works as expected, but on the 3.4 cluster we had "hpet=disable" in the /etc/default/grub because if we don't, we get many (strange) log entries about hpet. After the upgrade I removed the "hpet=disable", to see if the...

Hmm, I don't see anything odd in the .conf of your non-booting VM. However, regarding the fact a new VM is booting, you might think it must be in the non-booting VM config. How much I want to help you solve this, I have no idea right now. I hope someone from the Proxmox team, or another forum...

Hmm, very strange. Are you absolutely sure there are no files being healed currently by Gluster (gluster volume heal <DATASTORE> info)? If you create a new VM, will that one start? Can you show the .conf of a VM that doesn't start (/etc/pve/nodes/<NODENAME>/qemu-server/<VMID>.conf)

1. From what version are your upgrading? 2. Can you try to remove HA from the VM and see if it starts? 3. Do you see any errors about a locked VM? If yes, try to execute "qm unlock <VMID>" 4. What does "pvecm status" show?

Dutch is my native language (because of the similarities I understand a little German), and I'm sure there are many people here with lots of other native languages. If we all write in our own native language this forum will be a mess and lots of people don't understand. Therefore it's highly...

Anyways, if not using VIRTIO currently (which I think is the case here), switch to VIRTIO and try again. You will see much better results. If you stop the VM and remove the HDD, the HDD will be listed as "Unused disk" in Proxmox VE, then you can select the disk and set it to use VIRTIO. This way...

I mean the virtual HDD you added in Proxmox VE to the VM:

What storage driver do you use for the VM (IDE, SATA, VIRTIO, SCSI)?

If im right, today, April 15, 2016, is Proxmox VE's 8th birthday! So, I was wondering when we are welcome at Proxmox HQ to eat cake? ;) Happy Birthday and congrats to you all guys, and keep up the good work!

Thanks!

Uptime of a Proxmox VE node doesn't bother me, I prefer to have newer (but stable) software running, the version you are running is way too old. Only thing that does bother me is that the HA-cluster have a 100% uptime since day 1 (and with this the VM's running on it)...which it have (except...

Currently we use the pve-no-subscription repo, but since we are very happy with Proxmox VE we are planning to buy subscriptions soon. How about the change to pve-enterprise repo? Will packages installed from pve-no-subscription be updated from pve-enterprise (when we remove the...

Nothing in logfiles on the Proxmox VE node, only this entry in kern.log, messages and syslog: Apr 13 10:51:41 node1 pvedaemon[4550]: <wosp@pve> update VM 100: -vcpus 9 -delete cpulimit,cpuunits On the physical server intel-microcode wasn't installed, this is a basic Proxmox VE installation...

How about your memory usage? Is this node running VM's or is it only Proxmox VE that is installed?

With host microcode you mean just the intel-microcode and iucode-tool in the VM? Underlying hardware is a Dell PowerEdge R610 with dual Xeon X5650 CPU's. BIOS version running is 6.4.0, which is the latest. Absolutely true, but offcourse I don't like errors like these in my logs so would be...

Almost the same result, but error message is a bit different (intel-ucode/06-2c-02 instead of intel-ucode/0f-06-01):

Sure, here it is: boot: dc bootdisk: virtio0 cores: 12 hotplug: disk,network,usb,memory,cpu ide2: none,media=cdrom memory: 10240 name: jessie-vm net0: virtio=3A:3D:20:B9:E2:D7,bridge=vmbr0100 numa: 1 onboot: 1 ostype: l26 protection: 1 scsihw: virtio-scsi-pci smbios1...

Okay, first of all, a 1- or 2-node setup is not a good idea for a (HA) production environment, for a serious HA-cluster setup you need at least 3 nodes, so you always keep majority when one node fails. If you have a 2-node HA-cluster you are always at risk of a split-brain situation. When you...

Yes, I did. Otherwise the hotplugging would not work at all. :) Any other ideas?

So, you have a cluster running, want to add a new node, move the VM's on the cluster to the new node and remove the new node from the cluster? After that you have a empty cluster and one server running the VM's. Right? First: If you remove a node from a cluster, it must never come back online...