Recent content by sgargel

Seems also that pveperf is running better than qcow2 vms...

I'll read your link. No raid controller, the storage pool is ZFS Zraid2 on freenas 9.3 Mount option is: 192.168.100.200:/mnt/volume0-zr2/proxmox1/ on /mnt/pve/freenas2-proxmox1 type nfs4...

root@lnxvt10:~# pveperf /mnt/pve/freenas2-proxmox1/ CPU BOGOMIPS: 105594.48 REGEX/SECOND: 1231068 HD SIZE: 6290.13 GB (192.168.100.200:/mnt/volume0-zr2/proxmox1/) FSYNCS/SECOND: 14.31 DNS EXT: 52.26 ms DNS INT: 2002.66 ms (xxx) root@lnxvt10:~# pveperf CPU BOGOMIPS: 105594.48...

I'm running 3 proxmox 3.4 nodes using NFS shared storage with a dedicated 1GB network switch. root@lnxvt10:~# pveversion pve-manager/3.4-11/6502936f (running kernel: 2.6.32-43-pve) root@lnxvt10:~# mount | grep 192.168.100.200 192.168.100.200:/mnt/volume0-zr2/proxmox1/ on...

Ok... i've isolated the stand-alone server and no errors are displayed. So.. maybe that upgrading proxmox only activate the logging of the issue. But the issue resides very probably on the network side. Edit: seems the same as...

I've the same (or similar) problem. I've experienced it after upgrade my proxmox nodes. I've upgraded 3 nodes in cluster to "pve-manager/3.4-11/6502936f (running kernel: 3.10.0-14-pve)" and one stand-alone to "pve-manager/4.1-1/2f9650d4 (running kernel: 4.2.6-1-pve)" <code> [56601.876509]...

+1 :)

Really no one has any suggestions ? It 'an unfortunate situation that makes windows guests unusable. :(

I'm not sure if this is consequential of the proxmox upgrade but my Windows guests do not allocate correctly the RAM. The amount of ram is recognized (2GB) but guests wont use more than 512 MB. Strangely PVE Summary (the RRDtools graph) display that whole RAM is being used. I've tried to...

Many thanks for the hint :) Not the same as "disconnected cable" but is doing what I need... For the upcoming 2.3 do you plan to put in the GUI a switch for "set_link net0 [on/off]" or a "cable connection" control?

I'm looking for it too. Have you found any solution?

I fond those messages too... after some search i found: https://bugzilla.redhat.com/show_bug.cgi?id=507085 and seems that is not a real bug or critical issue.

Ok... I found this: http://comments.gmane.org/gmane.linux.pve.user/524 so.. if by now something like 'virsh save' is not yet implemented there is a workaround:

Was something like this what you was looking for? Did you find any solution?

I want to share what happened to me: While moving a 2k3 server from Virtualbox to PVE I encountered a the BSOD error INTERNAL_POWER_ERROR. The vm boots fine in Safe Mode. I followed those instruction http://virtuallyfun.superglobalmegacorp.com/?p=370 but I had no luck. Solution for...