Search results

Try write back and possibly older drivers. They have less cruft from the new features. Go to device manager and edit the red hat drive controller and set for performance.

I just did a basic copy and paste of a 2016 windows image that is almost 6GB in size and the transfer mustered over 100MB per second. No Cache IO Thread or off didn't make much a difference. It possibly had a little faster end of test speed. 85-125MB per sec Write Back IO Thread 290-300MB per sec

How are you testing performance that I can try to replicate on windows. Also, I logged in started poking around for this virtio driver iso. It looks like the version that I have running is viritio-win-0.1.141.iso. It's quite old and likely left over when I was testing opennebula. My ceph...

Totally just noticed the windows parts. What about using advanced and enable io thread. Go try older virtio drivers. 1.80-85ish. I've not used the latest drivers in years. I vaguely remember trying them along time ago and saw a reduction of speed. How is the virtio iscsi drivers under linux?

Try accessing by using krbd, or turn that off. Seems odd, is your ceph cluster separate or is this controlled by the cluster.

I'm currently struggling to find if this is the home cluster you've slowed down to 5MB or the production cluster. 50MB is very close to 500mbits of bandwidth and your transferring that multiple times across your network. Remember 3 copys. I want to see iperf tests to ensure that you can do the...

https://pve.proxmox.com/wiki/Package_Repositories This is Proxmox VE’s main Ceph repository and holds the Ceph packages for production use. You can also use this repository to update only the Ceph client. File /etc/apt/sources.list.d/ceph.list deb...

I have 5.4 VE connected to external Nautilus cluster. Not seen any problem yet.

Prior to migrating to proxmox from opennebula, we had assigned a vlan tag for private networking for every customer. Currently, we don't have an excessive amount of customers and private vlans are still an easy way for us to manage inter VM communication.

I would like to see if we can have scheduled operations for migrations of compute and disk. I like to do my migrations late at night and it would be really nice to schedule a time for a disk to move.

I might have read this all wrong as I was busy watching BsdNow podcast but if your looking for the older Virtio drivers you can use the "Archive" directory from the fedora ftp server http://alt.fedoraproject.org/pub/alt/virtio-win/ I just downloaded all of them back to 1.3 to try on some...

I too thought that you had to reboot then I did a little searching the system and found that if I ran "cat /proc/mounts" it would still show my ghost connection to the nfs server. Was simple to fix for me by "umount -l /mnt/pve/store_name". If you still have the mount configured in the GUI it...

Not exactly stellar performance but copying a 800mb folder doing the windows copy paste went from 4ish mb/s to 16mb/s so the virtIO storage driver seems to have worked. I had taken a snap shot so I was able to roll back. The first time install I let windows load the correct driver <--- Mistake...

I just checked and there was only NetKVM in Vista > AMD64 http://alt.fedoraproject.org/pub/alt/virtio-win/latest/images/bin/virtio-win-0.1-52.iso Someone tell me I'm not missing something.

I have been working with trying to solve some performance issues with windows vista 64 bit. This was a ESXI VM image that I converted to qcow2. I had already been running the E1000 nic driver so just to get the VM back up and running I setup the new VM with the E1000 nic and the drive as sata...

mir thanks for the suggestions. Ive done the converting of vmdk from a bunch of virtualbox vms so thats not going to be a problem. I just wasn't wanting to take the servers off line for the time to convert the images. I'll setup the NFS mount on freenaz as I hope this is not broken. I didn't...

can we bump?

Your going to need to view this file, make sure do not edit it unless you need to change the names of the certificate. Use your favorite editor You can use nano or vi, if you a vi user i suggest that you apt-get install vim-nox as vi in debian has some weird tendencies...

Sounds like ECC registered RAM, You only have half of what you install. Older Intel hardware?

Please run the following and post back uname -r free -m grep MemTotal /proc/meminfo The first will check to see if you have a 32 bit or 64 bit kernel the other 2 are just memory command.