Search results

@jo der bohrer That you decided to keep working with ProxMox, learn how to setup and further troubleshoot and seek help, shows you are in fact growing your knowledge, and creating your own steps and best practices. Keep up the great work! :) ProxMox is VERY powerful (and flexible) software, and...

If it's running a really old version of ProxMox, I assume it's probably running on a really old server. I would prioritize backing up the VM's and VM data before it's too late. Some things to try for troubleshooting, adjust VM settings to 1 socket/1 or 2 cores, and drive cache="writeback" and...

Have you checked the hard drive SMART status using smartctl? Hopefully it's not failing. Since we're in rescue mode, what I would do first is create a backup of each VM by mounting an internal hard drive (or USB hard drive) and add to proxmox storage as directory...

Sounds like a space issue, I would probably make a full backup your VM, install new/larger drive/s and install proxmox, then restore the VM to your host. I would leave the original hard drive intact, just in case. If you go to ProxMox main menu, highlight your host (proxmox), go "task history"...

@cranky, that's great news! Here is what my pve-no-subscription repository looks like using nano -w (edit config file and turn off text wrapping to prevent corruption) #nano -w /etc/apt/sources.list #nano -w /etc/apt/sources.list.d I'm unfamiliar with mc, but definitely start a new...

I also confirm similar message when running W2k16 Essentials on a test system (Intel Core2Duo E8400) with latest 4.13.x pve-test repository/updates as of 3/17/2018 #dmesg -T kvm [2313]: vcpu0, guest rIP: 0xfffff8012397ac53 kvm_set_msr_common: MSR_IA32_DEBUGCTLMSR 0x1, nop Tried changing OS...

"Could this be a problem with the kernel or upstream?" Not sure. However I also had issue with Athlon XII B24 where after new 5.1 install, system would not start after 1st reboot. I ended up trying an older Dell PC (Core2Duo E8400) and it worked fine. You could try the newer 4.15 kernel, YMMV...

Sounds like the SSH client is set to use wrong character set? If you use putty, try this: https://serverfault.com/questions/178334/weird-symbols-always-appearing-in-command-line-putty-zsh https://serverfault.com/questions/475925/how-to-fix-putty-showing-garbled-characters If this is happening...

Does anyone know if Server 2016 Essentials is part of the Windows Evaluations download? I'm going to try and replicate this on a test system. [EDIT] Yes Server 2016 essentials is part of free Windows evaluations. Downloading now, will report back..

Something to try, what if you mount FreeNAS storage as an SMB/CIFS share instead of NFS and retry backup? Do you get the same lags/stutters in this setup? https://servernetworktech.com/2013/03/proxmox-and-using-samba-for-shared-storage/

@zombiezacvh8 : What is your current ProxMox/VM cpu & storage setup? Single disk or Raid1/ Raid 10? How much total memory does server have? If you're running standard SATA, make sure BIOS storage is also set to AHCI or RAID/AHCI instead of IDE emulation. If you SSH into ProxMox, do you have...

@MattE you are correct sir! I wish the terminology in the 'backup' section was changed to "live mode" instead of snapshot mode

That's good to hear. BTW this post might better explain the snapshot vs stop modes when doing full backups: https://forum.proxmox.com/threads/backup-vs-snapshot.24332/#post-122684 also https://wiki.qemu.org/Features/Snapshots https://pve.proxmox.com/wiki/Backup_and_Restore "Creating...

Are you backing up to a local or external hard drive? I would run smartctl (short offline test) on your backup drives to check for possible drive errors. If possible, can you try adding another hard drive locally, and see if it backs up fine...

Are you using dynamic (balloon) memory for the VM configs, and/or combination with ZFS pool? This might help: https://forum.proxmox.com/threads/kvm-cannot-allocate-memory.13914/#post-118664 The solution in was make sure the sum total of all VM config memory (not actual used memory) did not...

Are you running qemu-img convert from the ovirt node or on the proxmox node? I would copy the original ovirt raw file unto proxmox host, and then run the proxmox qemu-img convert on the host locally. If that doesn't work, boot the original ovirt VM with the ISO of Clonezilla, make it device...

Sorry didn't mean to resurrect this old thread. You mentioned you did a P2V conversion? Did the original machine have static network IP before P2V? What if there is still a "hidden" NIC in device manager with static IP still assigned? You could try this...

The WD Black can be used in Raid1 or Raid 10. As for consumer SSD, that's totally up to you balancing risks/costs. You should probably run ASUS hardware diagnostics on your server to make sure SATA controllers/ports/cables are working normally. If the motherboard is old and starting to flake...

For traditional spinners, 10k/15K SAS drives with SAS controllers in direct HBA/IT mode will get the most out of ZFS. For traditional SATA, I would go with enterprise drives like Seagate "Constellation", Western Digital "RE4" series, Hitachi "Ultrastar" and always in raid1 (absolute minimum) or...

@MattE you might want to reconsider the brand/type of SSD for Proxmox. It's never a good idea to use "consumer" SSD for production servers. But here's a list of recommended SSDs https://forum.proxmox.com/threads/proxmox-slow-with-ssd-disks-on-lsi-9260-8i.39127/#post-193743 Also consider a...