Recent content by Jorem

I updated to kernel pve-kernel-2.6.32-13-pve and had no more kernel panics.

Same problem here. During backup of a large VM I got a kernel panic and system freezed. Is there a solution allready? Or is a downgrade to 10 the only option? Running kernel 2.6.32-12-pve now. # lscpu Architecture: x86_64 CPU op-mode(s): 32-bit, 64-bit CPU(s)...

I fixed the "problem". I deleted all the iptable rules. Restarted cman, pve-manager and pve-cluster. Now both servers are up again. There were probably still some rules in the iptables files that where blocking something from syncing. The iptables rules that I used, maybe someone has a idea...

The cluster worked fine till I tried new firewall settings. The second node went offline in the control panel. After removing the iptables the node came back online. Tried again with other firewall settings, node offline again and I removed the firewall settings again, but now the second node...

Found the solution. vi /etc/default/grub # add nomodeset GRUB_CMDLINE_LINUX_DEFAULT="quiet splash nomodeset" # update grub update-grub reboot

My logs are full with this message every 10 seconds. May 26 14:51:47 c1 kernel: [drm:drm_edid_block_valid] *ERROR* EDID checksum is invalid, remainder is 128 May 26 14:51:47 c1 kernel: Raw EDID: May 26 14:51:47 c1 kernel: <3>ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................ May...

But I was able to do a live migration in the past. I moved to a new server and did a live migration of 2 servers without problems. I always used the local storage. Is this changed after 1.4?

In PROXMOX VE 1.4 I never set the Shared value but online migration worked great. I am now using 1.6 and online migration does not work anymore. I searched the forum and read that the local storage needs to be shared to do a online migration. But my local storage is not shared now. When I edit...

Thanks for the Clonzilla tip. I will have a trie with that. Looks pretty risk free to me :).

It works great, but I wondered if you can run the 'qemu-img convert' command also on a running system?

Can the qemu-img command be used to do this? Like : qemu-img convert -O qcow2 vm-101-disk.qcow2 vm-101-disk.qcow2.new This should free up all the 0's on the drive. On Windows you first have to overwrite the old empty space with 0's to free it with the qemu-img command. Is this also the case...

I have a KVM VM with CentOS and I used to be 20GB in size. After a few local backups the size changed to 69GB. I removed the backups now and the size of the files is 20GB again. But the size of the qcow2 image file is still 69GB and is not reducing according to the size of the VM. Is that...

It is fast here (The Netherlands). Do you still have the problem?

Firewall How-To I used and works great: http://www.montanalinux.org/node/1098 Don't forget to restart the firewall after every newly added container. I setup SSH in the cluster so that only the other nodes in my cluster can access each other with root. edit /etc/pam.d/sshd and add the...

If all drives are not being picked up correctly than I think you RAID card i software RAID, en not hardware RAID. So check if your card i hardware RAID. Is it on the motherboard? (software raid)