Search results

fwiw, 1. Some user was me. The original issue was experienced with DRBD (VMs with swaps were sometimes hanging when migrating from one Proxmox VE host to another). 3. Test case writen by me (Stanislav) as a PoC

> Next version will include cloud-init support, but that needs special/prepared VMs. Nice. This would allow to do full cycle management through API. I'm thinking to write CPI for Proxmox and inability of managing VM IPs is one of blockers.

Hi, Is there any way to assign a network configuration including IP address while creating a VM through API? Best regards, Stanislav

iperf is doing half-duplex test by default. As I remember from times when I played around with traffic shapers it was easy to slow down outgoing traffic but not easy for incoming. And the only way to limit incoming traffic was to drop some packets.

Hi Sakis, What if you try another direction? Stanislav

Hello all, I would like to draw more attention on this usability issue: https://bugzilla.proxmox.com/show_bug.cgi?id=360 Please have a look and share your opinion on this. I would like to know if other users also struggle with themselves not to remove something accidentally or this is just my...

Hello everybody, Here is an update with reproducible test case: http://pve.proxmox.com/pipermail/pve-devel/2015-May/015201.html Best regards, Stanislav German-Evtushenko

Hi Marco, I've checked noVNC demo and found scaling possible however it seems to be not implemented in Proxmox so far. Best regards, Stanislav

I guess you have most of space occupied by /dev/mapper/pve-data. If so the easiest way to get more space would be: 1. Unmount and reduce file system size at /dev/mapper/pve-data 2. Reduce size of LVM volume /dev/mapper/pve-data (Be careful here. If you make the volume smaller then the FS size...

You should be careful with ext4 and sparse files: https://access.redhat.com/articles/41313

Generally writeback cache mode for qemu is not safe and can cause data loss on power failure. My previous message was only related to DRBD and out of sync blocks.

Hi There, I have some updates regarding the issue. Recent tests shows that all cache modes with O_DIRECT produce out of sync blocks and modes without O_DIRECT do not produce out of sync blocks. So both writethrough and writeback can be considered safe in relation to this issue. Best regards...

Hi there, I would like to contribute to this starting. My company mostly uses VMware on different locations around the world but on one of locations I have installed Proxmox long time ago. Recently one of my colleagues who did VMware administration needed to install a VM remotely (from Germany...

Hi There, I have some updates regarding the issue. 1) Upgrading to the latest DRBD 8.4 does not help and the issue is reproducible easily 2) I most cases directsync prevented out of sync for me however I've got a single VM where directsync did not help. However (!), switching to writethrough...

This is more about I/O subsystem then about network. I would choose not more than 1/3 or even 1/4 of maximum possible I/O throughput.

Hello, Just a remark: such a big resync-rate can cause I/O starvation and big issues afterwards. Stanislav

This is very unusual. I've never experienced this problem since I switched to cache=writethrough. Can you try to reproduce the issue with data-integrity-alg disabled? In theory data-integrity-alg can catch false-positive results. Stanislav

I'm not using the latest virtio drivers yet but there is an important general recommendation: check exact version of installed drivers and compare to what is in drivers directories because it is possible to install, for example, Windows 7 driver for Windows 2003 and vice versa that can make...

1. Post VM config here. 2. Try to monitor iops on the host.

Check exact virtio driver version for virtio block device. Sometimes Windows can install wrong one automatically. Also I have never changed scsi-controller to virtio as I'm not sure what the advantage is in compare to configuring virtio for particular drive directly.