Search results

  1. M

    Spam Report handling after upgrade to PMG 7.0 (missing token?)

    Hi all I have recently done an in place upgrade for our Mail gateway from version 6.x to 7.0, following the excellent instructions here: https://pmg.proxmox.com/wiki/index.php/Upgrade_from_6.x_to_7.0 I would like to say here a big thank for these and former upgrade instructions which are always...
  2. M

    More ClamAV Signatures via DatabaseCustomURL

    We (based in NZ) have been using those for quite a while successfully, thankful for their supply. I have now added the rfxn.com files. Let's see how this goes and will report here, especially if we should see any negative impact.
  3. M

    Win7 VM performance very bad after PVE upgrade from 5.4 to 6.2

    Hi Thomas thanks for your reply. It looks like impact on that VM also while running, not only the backup. We follow all your recommendations like VirtIO SCSI and VirtiIO for NICs plus use the guest agent for all Windows VM installations in recent times. That old Win7 VM goes back to some old...
  4. M

    Win7 VM performance very bad after PVE upgrade from 5.4 to 6.2

    We upgraded PVE on older hardware from version 5.4 to latest 6.2-11 (latest) as in-place upgrade 2 days ago. There are only 2 active VMs on that server currently, a Linux VM which seems to "behave" (perform) as before and an old Win7 VM (hopefully to be decommissioned within the next 4 week)...
  5. M

    [SOLVED] Removed a VM and its virtual disk

    Hi Aaron thanks a lot for clarification and advice. Did exactly as advised (although used rsync rather dd because feeling more comfortable with it) and can report back that the VM is running on its new disk now and data looks to be good. Will definitely rename disk image next time (yes, we have...
  6. M

    [SOLVED] Removed a VM and its virtual disk

    Made a big mistake... We had a VMID 100 some time ago. We then stopped ("retired") that VM and allocated its virtual disk to a new VMID 200 (newer OS version, the virtual disk of the former VM 100 was basically the "data" now allocated to the new OS version). That virtual disk sits in a local...
  7. M

    dist-upgrade trying to uninstall proxmox-ve

    Thanks Jannoke and Fabian. I will try Fabian's suggestion tomorrow night NZ time and as a worst case will follow Jannoke's suggestion to move forward with a fresh install of PVE6 (and backup/restore of previous configuration).
  8. M

    dist-upgrade trying to uninstall proxmox-ve

    I just managed to be stuck with this now as an attempt to upgrade PVE from version 5 to 6. I had not done the original installation and was not aware that this had been an installation with PVE on top of Debian originally. I did not pay attention at the time of "apt dist-upgrade", what...
  9. M

    PVE reinstallation without wiping local storage

    Thank you for your help. We were careful with our selection and it all worked out as planned. The "Data RAID" was untouched in the process as expected.
  10. M

    PVE reinstallation without wiping local storage

    We have a running PVE installation with separated local storage on 2x SSD (Hardware RAID1) for the OS installation and a second hardware RAID array (RAID 10) for all VM storage. Both RAID on the same controller. This was installed about a year ago by a team member in a non-standard way (I...
  11. M

    Strange behavior with backup mail notifications

    Thank you for your finding and reporting here. We (preferring lightweight ssmtp over Postfix on our PVE installations) have been living with this odd issue for a long time across various PVE versions. Manual testing vial "mail" command on the PVE command line never shows a problem ("mail -s...
  12. M

    All incoming ports to VMs blocked since upgrade to PVE 4.3

    Thank you for the reply and confirming what I assumed (no firewall change). I could not figure it out last night (too late) but this morning found it to be a firewall problem. Sorry for the noise and thanks again for a "Sunday response". Great software with excellent culture in the forum = top...
  13. M

    All incoming ports to VMs blocked since upgrade to PVE 4.3

    That sounds odd and I would expect that others would have seen this before and reported here but I have done an upgrade from PVE 3.4 to latest PVE 4.3 today and it looks like public access to all ports on the VMs seems now blocked (by PVE firewall I assume?). Previous upgrades from 3.4 to PVE...
  14. M

    zfs_arc_max does not seem to work

    Maybe by now (2016) both formats (Dec and HEX) might be supported with newer versions? I am just looking at a Proxmox 4.2 (test) installation, upgraded from former 3.x where this is set up (and working as far as I can see) with decimal: cat /etc/modprobe.d/zfs.conf options zfs...
  15. M

    Strange behavior with backup mail notifications

    We experience this issue of doubled up backup emails since we replaced Postfix with sSMTP - and I have not found a workaround to avoid/suppress the second email yet :-(
  16. M

    Root password reset

    I am no expert with this but should the correct command not have been mount -o remount,rw / instead?
  17. M

    rsync (host) performance issues with kernel 2.6.32 on Supermicro platform

    pveversion -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 qemu-server: 1.1-30 pve-firmware: 1.0-11 libpve-storage-perl: 1.0-17 vncterm: 0.9-2 vzctl: 3.0.27-1pve1 vzdump: 1.2-13 vzprocps: 2.0.11-2 vzquota...
  18. M

    rsync (host) performance issues with kernel 2.6.32 on Supermicro platform

    After testing on different systems, it seems to be down to one of the following two BIOS settings: - "Clock speed spectrum" is now set to 'enabled' - "NUMA support" is now set to 'disabled'. I suspect it to be the "NUMA" support setting. There is no help in the BIOS itself about "NUMA" but here...
  19. M

    rsync (host) performance issues with kernel 2.6.32 on Supermicro platform

    We have two more, identical servers at customer sites with the same symptoms (slow rsync perf.). I will repeat the changes there with a step by step approach to isolate the fix. Will take a while to get access and will report back then. Michael
  20. M

    rsync (host) performance issues with kernel 2.6.32 on Supermicro platform

    FTR: The problems are solved with (further) changes on the original BIOS settings (CPU related). Interesting (actually, confusing for me): The combination of "Redhat" kernel + original BIOS settings showed good rsync performance as reported before but it turned out that the VMs created a...