Recent content by proxymoxy

ok, thanks for clarifying. I thought you meant "proxmox is not a distribution". What I meant that the installer doesn't include software raid support. But of course it is possible to use software raid (I have done it), but the installer doesn't support it (in fact installation stops) and it is...

Well Dietmar, you should also tell the peope at Distrowach.com about this ;-) http://distrowatch.com/?newsid=06878 Martin Maurer has announced the release of Proxmox 1.9 "Virtual Environment" edition, a Debian-based distribution designed for running virtual appliances and virtual...

I agree completely :-) Some people (also from the proxmox team) argue with the "data consistency"/"power off" issue in software raid ("no bbu"). This is true to some extent, but other important tools like vzdump create backups using snapshots which is somewhat like a backup after "power...

Well, I reinstalled everything, and now iotop doesn't work in any container (even one that was not restored). I am not able anymore to run iotop successfully in any container with sl6 (but it works fine on the host). In other words vzdump/vzrestore work fine and there is no bug at all.

Yes, that is the version I tried. No, idea why I wrote 1.2.3 :-) Latest entry in the change log was: 2011-05-24 Proxmox Support Team <support@proxmox.com> * OpenVZ.pm (resume_vm): remove --skiplock flag

Is this is potential bug in vzdump/vzrestore? Here is what I did: Install sl6 precreated template from openvz.org vzctl enter 101 - yum update - yum install iotop - exit vzctl enter 101 - iotop [works fine] - exit vzdump --stop --dumpdir /root 101 vzctl destroy 101 vzrestore...

I recommend htop. When you build it, run ./configure --enable-openvz

Why does is pre-restart triggered before snapshot and resume_vm (in snapshot mode)? The order is currently 1. pre-restart 2. snapshot 3. resume_vm (optional) I expected 1. snapshot 2. pre-restart 3. resume_vm (optional) Is this a bug?

I think I am finished. How should I deliver the patch?

Ok, will do. Will try (need to learn about patching first ;-) Just to make sure I am on the right path. This is basically the only important part in VZDump.pm? my $mode = $running ? $opts->{mode} : 'stop';

Understand, but if a user uses the option snapshot (and not stop), then it should run in snapshot mode. I think if the user uses the snapshot mode the user aware of the additional disk space requirement. Would it be possible to add an option for this in the next version (I guess the only...

See also the follwoing output [root@myserver ~]# vzdump --snapshot 101 --tmpdir /tmp --dumpdir /root INFO: starting new backup job: vzdump --snapshot 101 --tmpdir /tmp --dumpdir /root INFO: Starting Backup of VM 101 (openvz) INFO: CTID 101 exist unmounted down INFO: status = CTID 101 exist...

Just FYI I downloaded vzdump_2011-06-17 and installed it on Scientific Linux 6.1 x86_64. Then I created a test container using the SL x86 precreated template. After that I tried vzdump --suspend --dumpdir /mymount 101 but vzdump failed because of the following error message INFO: vm is...

Dietmar, thanks. Now I understand 100% "vzdump snapshot behave like a power loss on physical hardware". It also answers my question, what happens when a user edits some text with a simple text editor and the system is dumped.

I did search before asking, but didn't find an explicite answer. The closest one is "http://forum.proxmox.com/threads/2769-Question-about-snapshots?highlight=vzdump". But this was two years ago and the answer was I also read other topics and used my favorite search engine, but still not sure...