Search results

Hi, this is not a real kernel panic, this is your vms kernel which send error message, because the storage is not responding or too slow. Maybe your storage is overloaded when this happen ?

Hi,another way could be to disable motherboard watchdog,to use the hp ilo watchdog by default. edit: /etc/default/grub GRUB_CMDLINE_LINUX_DEFAULT="nmi_watchdog=0" #update-grub #reboot

I also found a note here: https://lkml.org/lkml/2014/4/25/184 "hpwdt can not work as expected if hp-asrd is running simultaneously.+Because both hpwdt and hp-asrd update same iLO watchdog timer." Do you have an hp-asrd daemon running ? (maybe from some hp management packages ?)

ubuntu has also disable it by default. https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1432837 But, It could be a problem of ilo configuration when watchdog is enable by hpwdt. Maybe they are a ilo timeout configuration somewhere in ilo ?

I think we could try qemu 2.3 with kernel 4.2. It could help to see if the problem come from qemu 2.4 or kernel. If it's don't work, try again qemu 2.3 but with kernel 4.1 http://download.proxmox.com/debian/dists/jessie/pvetest/binary-amd64.beta1/pve-kernel-4.1.3-1-pve_4.1.3-7_amd64.deb or...

Note that you don't need to mount your fs with discard=on, to use fstrim. if you use discard=on, trim will be done at each delete in your filesystem, and this can be quite slow. It's better to simply add a cron, daily for example, which launch fstrim. (without any discard=on)

It'll not be stable until 1.X . Currently they are still cluster format changes between release 0.8 -> 0.9, need to backup/restore for example.

Proxmox don't add nothing special to the distro, only qemu 2.4 is used instead default qemu 2.1 in debian jessie. you can install proxmox 3.4, qemu 2.2 , on proxmox 4.0 if you want. wget...

I could be great to see if it's working with proxmox qemu 2.4 + jessie 3.16 kernel for example. I think it's a kvm bug in last kernels, but I would like to be sure that's it's not a regression in qemu.

you can change the repository in /etc/apt/sources.list.d/ceph.list (https://download.ceph.com/debian-infernalis/) Please read the upgrade procedure: http://ceph.com/releases/v9-2-0-infernalis-released/ because they are some file permissions change with infernalis. (was root:root previously...

tablet is disabled when spice is used, because it's cause mouse problem in spice session.

Hi, which kernel and qemu version ? (proxmox 4.0 use ubuntu willy kernel + qemu 2.4)

>>1. just update the gluster and keep using the PVE GUI for the mount If you are happy with gluster 3.7,yes, you can simply add 3.7 debian repository to proxmox http://download.gluster.org/pub/gluster/glusterfs/LATEST/Debian/jessie/ They are no specific proxmox patches on current packages...

you can try to pass args: -cpu ..... but, it's really not recommanded to use core2duo vcpu on amd host cpu. This can give you vm instability/crash because of missing cpu flags.

you can do it, with specify size=0 for the disk. (but they are no quota like openvz in this case)

I think this is because the memory stats are coming from query-balloon qmp, and it's not yet aware of hotpluged memory. It should be fixed in coming qemu 2.3

if your restart the ceph osd with /etc/init.d/ceph osd restart, it don't umount /var/lib/ceph/osd/ceph-0 , so the new mount options are not applied. you can do /etc/init.d/ceph osd stop umount /var/lib/ceph/osd/ceph-* /etc/init.d/ceph osd start or do a remount manually mount -o...

Could you try with a windows client with virt-viewer 1.0 ? https://fedorahosted.org/released/virt-viewer/virt-viewer-x64-1.0.msi I would like to be sure it's a client problem before try to investage on qemu side.

Just to be sure, are the 2 switchs linked together ?

>> Ubuntu 12.04 OpenVZ instance. veth (bridged) or venet (routed)? (veth is known to be slower, but not so slow) I don't known if you can test between 2 kvm guests ?