Recent content by davec

  1. D

    Unable to start VMs

    That's great news. Glad you got it sorted out. :)
  2. D

    Unable to start VMs

    Did you install the intermediate cert for your own cert ?? This will cause issues if you don't. This post alludes to that as well.: https://forum.proxmox.com/threads/certificate-startup-problems.25815/
  3. D

    Unable to start VMs

    From some google searches and forum searches I see you might try: https://forum.proxmox.com/threads/cannot-start-kvm.25085/page-2 systemctl stop 100.scope qm start 100 No idea if the above will work though. This might also help...
  4. D

    VirtIO = task xxx blocked for more than 120 seconds.

    Having JUST experienced this same issue, I think that your disk speed/disk cache isn't enough to handle the io when data is dumped.... you don't mention what your disk is. I can see it's "local" in one of the images, but if it's not an SSD, I'm guessing that it's disk/io error. For me, my...
  5. D

    qcow2 VM's running on zfs nfs are slow.

    Ok, update....... FREAKING AMAZING RESULTS !! I finally got in my sata connectors and my SSD's. Added a 60 GB Kensington SSD for log Added a 254 GB Samsung SSD for cache now... i have the following to report from pveperf: root@prox1:~# pveperf /mnt/pve/NAS-isos/ CPU BOGOMIPS: 140799.12...
  6. D

    qcow2 VM's running on zfs nfs are slow.

    Ok, small update. I haven't got the cache or log drives installed yet, but I did increase the ram yesterday. I went from 8 GB's to 32 GB's. This DID make a difference. Before when upgrading a vm, I would often see lines like " INFO: task jbd2/dm-0-8:387 blocked for more than 120 seconds."...
  7. D

    qcow2 VM's running on zfs nfs are slow.

    Ok, I have some SSD's ordered for the NAS to add in log and cache, and am going to double the ram. I will post back once that is installed. I did clone my template to a raw format, and the speed increase was considerable. Since I'm on ZFS already with the vm living on the nas, and the nas...
  8. D

    qcow2 VM's running on zfs nfs are slow.

    Thanks for your thoughts. I will look into getting a SSD for logging, hopefully that will at least improve things. ;)
  9. D

    qcow2 VM's running on zfs nfs are slow.

    Hrm... after doing even MORE searching, I've come across this post: http://ninjix.blogspot.com/2011/02/get-those-fsync-numbers-up-on-your-zfs.html ........ I think I need to add an SSD for logging... thoughts ? nas4free: ~ # zpool status NAS pool: NAS state: ONLINE scan: scrub in...
  10. D

    qcow2 VM's running on zfs nfs are slow.

    Have a C7000 with NAS4FREE NFS storage .... The issue is that upgrades on my vm's are taking 35 minutes ... but on my crappy T400 laptop, the same upgrade will take less than 3 minutes. Sigh. The one blade on the C7000 running the proxmox host shows 0 iowait time... the vm shows like 95+%...
  11. D

    ZFS Deduplication

    I'm going to have to encourage you to NOT enable deduplication, it can cripple your system with the overhead it takes to do this. If you don't follow this advice, you better have boatloads of RAM. Even on our production NAS at work where we have hundreds of gigs of ram, we do NOT run...
  12. D

    [Solved] qemu-img convert gives error: Unsupported image type 'seSparse'

    Re: qemu-img convert gives error: Unsupported image type 'seSparse' OK, that pointed me in the right direction... and I was able to get it to work. Posting here what I did to convert this VmWare VM to Proxmox and qcow2 format. ON PROXMOX GUI: create the new vm. ON the ESXI host: vmkfstools...
  13. D

    [Solved] qemu-img convert gives error: Unsupported image type 'seSparse'

    Any idea what I can do to correct this to make it work ? Google searchs have proven elusive in search for an answer. root@prox2:/mnt/pve/NAS-VMWARE/daveskb# ls -latrh total 6.8G -rw-r--r-- 1 root root 0 Apr 22 2014 daveskb.vmsd -rw-r--r-- 1 root root 262 Apr 22 2014 daveskb.vmxf...