Search results

I see I'm a bit late to the party here, however I also can report that the VM reboot problem has been successfully resolved. What remains to be seen is if this fixes node reboots we are observing. Oh, and had libjpeg8 dependency problem too. Thanks for your help!

We don't have a knife to our throats yet, but can't wait indefinitely either :) Of course we can try things; that's why we went with BETA - to help even a bit with hammering out bugs. One question tough, will doing this break any upgrade path from beta to stable? ie. will apt-get update &&...

Any idea on an ETA for a fix on this issue? Or even next beta? If it isn't solved soon, we will need to revert to 3.4 and no more feedback :(

Can't believe nobody mentioned netxms - most thought-through monitoring software, once you understand how it works :)

No. Any machine that's q35 won't boot more than once per vm start/stop cycle. This isn't relevant to PCI Passthrough. On that note, is there any performance gain/loss between q35 and 'normal' machine type? Which one is better for general use if one does not need PCI passthrough?

There's always a quorum, since it's a single node :) - I'm observing and reporting what I can. Right now I can only report that 0.6.4.2 has fixed major problems with ZFS compared to 0.6.4.1 -- hot-pulling a drive caused a kernel panic on 0.6.4.1 (shipped with Proxmox), and is working as intended...

Thank you for your reply. Not sure. I did apt-get update, upgrade, dist-upgrade. # pveversion -v proxmox-ve: 4.0-7 (running kernel: 4.1.3-1-pve) pve-manager: 4.0-26 (running version: 4.0-26/5d4a615b) pve-kernel-3.19.8-1-pve: 3.19.8-3 pve-kernel-4.1.3-1-pve: 4.1.3-7 lvm2: 2.02.116-pve1...

After few days of using 4b1: ZFS became usable only after upgrading to 0.6.4.2 (0.6.4.1 is shipped with beta1), qemu q35 machines don't work correctly (failing to reboot), and few minutes ago node rebooted for no reason at all. PCIe cards behave erratically after some uptime. (virtual machines...

As in title, on Proxmox 4 beta 1 q35 machines are unable to reboot without stop/start cycle. After reboot (from within VM), it fails to boot, instead hanging forever at SeaBIOS, just after printing "Press F12 for boot menu.", before stating that it will boot from hard disk. PCI passthrough...