I have a simple feature request for vzdump. Since it has evolved into more of a full backup script and not just a command to be integrated into a custom backup script...
The only thing it doesn't do for for me that my backup script used to is multiple rotated backups for safety's sake.
When I...
Great work, guys. My nice 8-core server is so much more useful due to your software. I just created a CentOS 5 VZ container and installed coldfusion in it for a client who uses that junk. It went nice and smooth after I performed the (also very smooth) update from 0.9b2 to 1.0.
I just updated from Proxmox VE beta1 to beta2 using the apt-get dist-upgrade method. Everything was fine except my Win2k Server KVM. The FreeBSD 6.3/i386 KVM was perfectly fine and happy, it was just the Win2k server KVM that blew up:
So I tried and tried various things to get it running again...
To test my vzdump-generated backups I took my latest backup from a couple of hours ago and restored it to a new CTID.
I shut down the good working CTID and started up the restored CTID (so I didn't have an IP conflict) and things were missing from the restored copy.
/var/log/postgresql was...
FYI, I had to edit /usr/bin/vzdump to change $lvcreate --size 500m to $lvcreate --size 2000m. My vzdump was failing multiple days in a row on my Plesk jail. It has about 60 domains in it and about 30G used, nothing really out of the ordinary. 500m just wasn't enough and it failed and started...
I just started up a second instance of KVM and the second instance's "e1000" virtual adapter was assigned the same default MAC address as the first existing KVM: 52:54:00:12:34:56.
This of course collided with the first KVM...
Both are using the bridging and both were assigned the same MAC...
Has anybody else noticed the I/O scheduler seems to perform very "unfairly" ?
During a vzdump I pretty much see the entire system's load average inside OpenVZ containers and even in the host just skyrocket up to 5-20 easily with no actual load on the system. Apparently everything that is not...
On my Proxmox VE box, netstat on the "host" Debian 4.0 system doesn't seem to be working, it just sits there... even when I use netstat -n -l or netstat -n -a. Anybody else seeing this?
proxmox:~# netstat
Active Internet connections (w/o servers)
Proto Recv-Q Send-Q Local Address...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.