Recent content by Nico Haase

Why should it be dangerous? In some years, its much more dangerous to stay on an outdated Debian version....

Even if I don't monitor my VM all the time, I cannot think of anything happening within that causes a stable load of 60 MB/s on the I/O over three hours. As this happens during the night, there should be anything running that hard. But let's see, I pulled the handbrake down to 35MB/s.....

As I stated some times: IO that happens on the VM host system should never, never affect the IO or load of the guest system. My server should be able to handle this without problems. Data by pveperf: root@proxmox:~# pveperf CPU BOGOMIPS: 31997.08 REGEX/SECOND: 839138 HD SIZE...

So, even after having updated to Proxmox v3.2 and a reboot for all changes to take place, running a backup to a NFS share still causes high load (~3.0) within a virtual machine. I have not monitored that machine for more detailled problems occuring within it, but even the high load should not...

Sorry, macamba, but if you state you know what apt-get does, but do not understand that apt-get updates does nothing more than updating the internal database of apt-get, I cannot see where you have understood apt-get... Of course, a apt-get upgrade upgrades packages (that's why its called that...

You should take a look into the basics of apt-get. This is no proxmox related question...

....still no news about it?

Hi there! I have seen some discussions on the developers list, but as fas as I see there is no official fix yet. Do you have any ETA for it?

Sorry, even if I am a student of computer science, I have no time to get into your stuff. Telling people who have a problem with your software they can fix it themself if they want to see it fixed sounds weird. If I wanted to do it myself, there would be no need to use your software...

Sorry to ask so silly, but you just claim that everything is alright and there can be no problem even if we have one? Of course, not everyone of us is a paying subscriber, but how can you be that little helpful for a problem like this which seems to affect some users seriously?

Once more: actions in the VM host should not affect any VM internals. The backup happening in the host should be invisible for the virtual machine. Otherwise, something is very wrong...

Sorry for the delay, I got other problems to work on. I just wanted to see the problem arising while looking at it. I started a new backup without any further modifications, the load within the VM got up far beyond 10, the VM-internal disk got into read-only mode, applications crashed. On...

I'm not only talking about a load of 2 for some moments, but also about a much higher load that only occurs during the backup and makes our server nearly unusable for some hours...

Okay, it's fine to know that. But do you have any idea what causes the problem?

Yes, we use a current system, but the log starts with the following lines: vzdump 111 --quiet 1 --mailto @adress --mode snapshot --compress lzo --storage nfs --node proxmox 111: Nov 06 22:50:02 INFO: Starting Backup of VM 111 (qemu) 111: Nov 06 22:50:02 INFO: status = running 111: Nov 06...