Search results

Try use lastest Proxmox (i use 3.4) with 3.10 kernel and with VM options: Sockets 2, Enable Numa it completely solved the problem of high CPU load for me

I have the same performance problems with Windows Server 2012. Please be advised that it is better to do in my case: I have a host server with 2 processors E5-2630v2 (6 physical cores) RAM 128GB with kernel 2.6.32-30 I run a virtual machine with 96Gb of RAM, what settings are best to use: a) 1...

Please share own experiences. Is there a marked improvement compared with the firefly? (Does increased performance?) Ready for production? Do you think are now upgrade from giant firefly on or wait for the next release? Thank U.

What would prevent problems with the activation of business applications after update qemu I did as advised in this thread http://forum.proxmox.com/threads/19743-ProxMox-3-2-to-3-3-impressions-and-a-problem?p=100629#post100629 apt-mark hold pve-qemu-kvm and upgrade to 3.3 after that I can not...

I use jumbo frames (ifconfig eth0 mtu 8982) Do I need to necessary to set cman options in /etc/pve/cluster.conf: <totem netmtu="8982" window_size="25"/> or I can continue to work with the default settings? What else can you recommend settings for a 10 gigabit network and jumbo frames?

Explain please. In wiki (https://pve.proxmox.com/wiki/Proxmox_VE_2.0_Cluster) says: What does that mean exactly? New name, new ip address, or both? For example, if I remove the "node1" with ip 192.168.0.1, reinstall pve, I must: 1) change the name such as "node1a", but can leave same ip...

Yeah, just great! but does not solve the problem

real 0m7.443s

somebody of the developers can tell where in the source code possible to increase the timeout? if i change "blocksize 4k" to "blocksize 8k" in /etc/pve/storage.cfg it will not cause problems with already working disks?

yes, i did it all small operations do not cause problems: I can see the contents of the storage (list of raw disks) in the web interface, I can change the size of the disk in the web interface I can log in to Nexenta through ssh without password I can create a disk via ssh...

yes

I can not migrate the disk, I can not restore from backup. After 5 seconds the operation fails: got timeout TASK ERROR: storage migration failed: command '/usr/bin/ssh -o 'BatchMode=yes' -i /etc/pve/priv/zfs/172.16.99.15_id_rsa root@172.16.99.15 zfs create -b 4k -V 62914560k...

It seems that the problem is solved. Thank you very much.

yes extract and compress a large archive (14Gb) without problems

I did a lot of tests. To create a load using various utilities (stress, fio, bonnie++, dbench) and in our case, the best was "dbench -s 128" inside VM (Key "-s" very important) and start backup process with GZIP !!!, without compression or LZO - VM don't crush Where from does not matter (iSCSI...

NexentaStor 3.1.3.5 via ZFS plugin (12x2Tb SAS + SSD for ZIL and ARC) 10Gb network backup to local SATA disk 3Tb

Dear developers! You were able to reproduce this error? Will you fix this bug? Maybe I can help you more than to localize a problem? Maybe we can go back to the previous algorithm where the backup did not have this bug? Thank you.

Info from gdb: Program received signal SIGSEGV, Segmentation fault. 0x00007f8bf77ce61a in ?? () (gdb) backtrace #0 0x00007f8bf77ce61a in ?? () #1 0x00007f8bf77ced75 in ?? () #2 0x00007f8bf77ce4f1 in ?? () #3 0x00007f8bf77ce888 in ?? () #4 0x00007f8bf781cc4d in ?? () #5 0x00007f8bf76b2e8a...

root@pve-node3:~# /usr/bin/kvm -id 1080 -chardev socket,id=qmp,path=/var/run/qemu-server/1080.qmp,server,nowait -mon chardev=qmp,mode=control -vnc unix:/var/run/qemu-server/1080.vnc,x509,password -pidfile /var/run/qemu-server/1080.pid -name ftp -smp sockets=1,cores=2 -nodefaults -boot menu=on...

If used Ceph RBD only as a storage for KVM machines (i do not use openvz). Do I need configure fencing in this case? (i use fence_ipmilan)