Search results

no no real benchmark. Its just a comparison with a local disk (pure SATA-HDD no SSD) based virtual box during a docker container installation. Our Setup is a Dell Server with 10G Link to a Oracle Storage ZS3-2, I expect much more than just 30MBit/s. But ok. Which tool would be good to test...

sure and we do have a working setup but the feeling is that it is quite slow and doesnt use the performance our storage solution is able to provide

Are there any mount proposals for a NFS share ? all disk images stored on a NFS share mount says about the current mount: 10.0.10.254:/export/Storage on /mnt/pve/Storage type nfs...

Ok I'm not reall sure if that one is the log you requested... root@prox05:~# cat /var/log/pve/tasks/C/UPID:prox05:00007F9E:00710065:559FACDC:qmsnapshot:143:root@pam: Formatting '/mnt/pve/Storage/images/143/vm-143-state-powerfail.raw', fmt=raw size=6966738944 snapshot create failed: starting...

same here.. proxmox 3.4-6/102d4547 root@prox05:~# cat /etc/pve/nodes/prox05/qemu-server/143.conf balloon: 1536 boot: dc bootdisk: virtio0 cores: 2 hotplug: disk,network ide0: none,media=cdrom memory: 3072 name: GRFV8021--10.0.1.209 net0: virtio=4E:1E:27:CA:C4:27,bridge=vmbr2 numa: 0 onboot: 1...

are there any way to analyze why a snapshot fails ? or doesnt finished ? snapshot done via HTML Interface inclusive RAM on KVM Vm stored on storage via Nfs4 172.16.0.6:/export/Storage /mnt/pve/Storage nfs4...

HI, you wrote a long time ago a statement about suspend-to-disk and kvm.... https://forum.proxmox.com/threads/6485-qm-suspend-shows-no-result?p=36767#post36767 Did you anything for 2.x or later version ? suspend 2 disk would be seen still as necessary

Ok thats clear to me... But as far as I know there is no automatically way for that right ? Probably someone already implemented such thing

Hi, Are there any proposal how to snapshot all the VMs I have on a server (52!) to disk in case of UPS initiated shutdown. Shutdown would break the shutdown timeframe and destroy some running tools.... Mainly it could be done by script. But how to handle the restore if power comes back ? Immo

http://www.networkupstools.org/acknowledgements.html#Eaton Ok my UPS is a bit bigger 3kVA 5PX 3000 / 11KVA EX11RT I'll give it atry... anyway

Are there anybody who use Eaton/MGE USV with proxmox ? the networkupstools eaton support sticks since eaton steps out of thsis project... regards and happy easter

Re: could not bring up yfs iscsi storage based vms Ok script extendet to get the right Lun back from function ... but this doesnt help. Were are the iscsi string is created for kvm start ? 13,21d12 < my $InitiatorName; < my $fh = IO::File->new('/etc/iscsi/initiatorname.iscsi') || return undef...

Re: could not bring up yfs iscsi storage based vms We can bring up the vm if we add the Lun Number direct behind the iscsi target slash (Red Zero) /usr/bin/kvm -id 102 -chardev 'socket,id=qmp,path=/var/run/qemu-server/102.qmp,server,nowait' -mon 'chardev=qmp,mode=control' -vnc...

thats the error I got if I start the vm which is based on a zfs storage kvm: -drive file=iscsi://10.0.16.90/iqn.1986-03.com.sun:02:b23b291b-79f5-c3b3-9583-9ccb49a7fc30/,if=none,id=drive-scsi0,aio=native,cache=none,detect-zeroes=on: could not open disk image...

HI Due to missing response I have to be more clearly KVM/QEMU libvirt-bin provides a feature save. This saves the current running state into a file which can be loaded after a while with resume and runs right away nearly instantly from the previous save state. This feature would be nice to get...

Are there any way to suspend my 50VMs and save the state for a host reboot? After the reboot the vms should just resume. This would help to reduce the Shutdown time and could keep my VMs somehow "running". This is important for long duration tests of our software....

HI, we have a huge storage for all ISOs we ever got for installing. I would like to use this directly for installing new VMs. But howto ? the way seems to be to define a directory as root share this as ISO storage and afterwards mount the ISO Storage into ./template/iso Immo