Recent content by faceless

Ah. Well, if corosync requires it then I guess I'm out of luck. As for the "debian way", perhaps I'm overstating this. A fresh install doesn't leave /etc/hosts like that and I've never had to do it before. But hey ho, whatever. Might be worth noting this step, and the requirement for a static...

Thanks FinnTux While that does fix the immediate problem, it's not ideal as it essentially forces me to run with a static IP address. It's also not really the "debian way" - see 5.1.2. The hostname resolution. Obviously this is what beta testing is for so hopefully the Proxmox team will find a...

Hi all I'm testing Proxmox 2.0 on a new machine, or hoping to. I've followed the instructions at http://pve.proxmox.com/wiki/Install_Proxmox_VE_on_Debian_Squeeze exactly but my install has failed. This is on a brand new install - I've installed zsh, avahi-utils and sudo, but other than that...

Tom, you read my mind!

Just tested - no difference I'm afraid. However I think this is caused by the same "events/0" processing locking at 100% problem that I've seen reported elsewhere on this forum...

Just tested the 2.6.32 kernel as well, and this seems to be fine. Here's pverversion -v pve-manager: 1.8-18 (pve-manager/1.8/6070) running kernel: 2.6.32-4-pve proxmox-ve-2.6.32: 1.8-33 pve-kernel-2.6.32-4-pve: 2.6.32-33 pve-kernel-2.6.35-1-pve: 2.6.35-11 pve-kernel-2.6.24-12-pve: 2.6.24-25...

Have now run the upgrade. Exactly the same results. Here's pveversion -v pve-manager: 1.8-18 (pve-manager/1.8/6070) running kernel: 2.6.35-1-pve proxmox-ve-2.6.35: 1.8-11 pve-kernel-2.6.35-1-pve: 2.6.35-11 pve-kernel-2.6.24-12-pve: 2.6.24-25 qemu-server: 1.1-30 pve-firmware: 1.0-11...

Thanks Tom, but I'm not asking for support with 2.6.24. I'm asking for support with 2.6.35, which is causing my VMs to hang, as described in my first message.

Bbecause it's working better than 2.6.35 :-) I must have missed the the 2.6.32 while looking for the kernel versions to downgrade to, will try that this evening and let you know the results. However the point of my post is that 2.6.35 isn't working, rather than 2.6.24 is working.

Sorry - I'd installed the packages making up proxmox-ve-2.6.24, including pve-qemu-kvm, but not the metapackage itself, and pve-version seems to look for that package. I've installed proxmox-ve-2.6.24, it didn't add or delete any other packages and now pveversion -v gives pve-manager: 1.8-17...

Hi all I think I'm hitting the same issue mentioned in http://forum.proxmox.com/threads/5046-Error-kvm-cpu0-unhandled-wrmsr-amp-unhandled-rdmsr but I'm starting a new thread because I'm not sure it's related to the "cpu0 unhandled wrmsr: 0x198" message. I have a box with 2 x Xeon 5300, for a...

Just create the logical volume, then add it to the guest - personally I'd just add it directly to the file in /etc/qemu-server/???.conf. The line would look something like this: virtio1: /dev/mapper/volgroup0-lvname then in the guest you should have the partition shared as /dev/vdb (note this...

A quick feature request: it would be useful to be able to select which disks to include in a VM backup. Currently all disks are included, but I have a large scratch disk on one VM that has been blowing out my backups and it would be nice to be able to skip it. Cheers... Mike