Search results

VM 104 is the problem child on this host, but I have this same similar problem on multiple hosts at multiple sites. The problem seems to stem from the line in syslog that reads like this:kernel: vmbr1: port 2(tap104i1) entering disabled stateI've searched the forums and this seems to be a common...

Hi all. Long thread, but hopefully lots of info on a problem than has puzzled me for some time. I've reported the problem previously and it went unsolved, but figured I'd try again. Essentially, I have 2 KVM windows 2008 vm's on one PVE host. This box has been in production since PVE .9 beta...

I'm using a hook-script. The drive is emptied as the backup begins. I'm not using --maxfiles anymore, because it's useless with the limited size of the USB drive combined with the new vzdump naming convention. We rotate the usb drives daily and I have a cron script to mount them by UUID to...

Last night's backup: 101: Jan 20 19:15:01 INFO: Starting Backup of VM 101 (qemu) 101: Jan 20 19:15:01 INFO: running 101: Jan 20 19:15:01 INFO: status = running 101: Jan 20 19:15:02 INFO: backup mode: snapshot 101: Jan 20 19:15:02 INFO: bandwidth limit: 14000 KB/s 101: Jan 20 19:15:02...

Nope, haven't deleted any VM's, PVE host has always just had the same two KVM VM's. Still having very Strange things happening with vzdump. Newest backup logs: January 18th, Backup begins at 8:00 PM CST: root@volt ext# cat vzdump-qemu-101-2010_01_18-20_09_46.log Jan 18 20:09:46 INFO...

Thanks, this did the trick. I went back and re-read the man pages again and found everything I needed. Sorry, I was wrong about this. Any chance you guys could explain the INFO messages about removing stale snapshots below: Jan 12 22:00:03 INFO: trying to remove stale snapshot...

Added! root@volt ~# cat /etc/vzdump.conf size: 2048 I've read the man pages serveral times on vzdump. I know it's your perl script, Diet. I've seen references to /etc/vzdump.conf in the actual /usr/sbin/vzdump script itself, but the manpages don't really explain anything about vzdump.conf. Is...

The problem is essentially vzdump is filling up every bit of disk space on my external USB drive while trying to backup to KVM VM's. The USB drive is 500GB (/mnt/ext), and this process worked fine prior to my last dist-upgrade to pve 1.4. Here's all the good info: volt:~# pveversion -v...

sorry for the double post. not sure how I did that. vzdump works again now.

Resolved: vzdump no longer "sees" KVM VM's Problem resolved. /etc/apt/sources.list was incorrect and out of date. I checked another PVE host and updated my repos: deb http://ftp.us.debian.org/debian lenny main contrib # PVE packages provided by proxmox.com deb...

I think my sources.list was way out of date. Just did a dist-upgrade and it looks to have upgraded correctly. Rebooting server now. Will test vzdump shortly.

I also need to point out that someone else seems to be having the same problem as me with vzdump. My host is also a single node, but I do not have any OpenVZ VM's, just the two KVM VM's: -----Original Message----- From: pve-user-bounces@pve.proxmox.com...

volt:~# apt-get dist-upgrade Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done The following packages have been kept back: proxmox-ve pve-manager qemu-server 0 upgraded, 0 newly installed, 0 to remove and 3 not upgraded...

I've run into a problem where vzdump no longer recognizes or "sees" the two KVM virtual machines on my PVE host. Several other things are also concerning me. I'll post the all of the output and see if anyone here can help me or decipher what is going on. vzdump stopped functioning after apt-get...

I've been having problems with this method and described my problems here. Sorry for the double post, I saw this after I started the new thread.

Hello! Have been attempting to migrate some test machines to Proxmox VE and I'm running into problems everytime. I have followed the Wiki on several different machines and I always end up with the same result: Once I try to start the VM after all of the steps are complete, the console just...

The upgrade process from alpha to newest should be the same as the process from beta to newest. It's going to be a repository upgrade using apt. http://pve.proxmox.com/wiki/Downloads#Update_a_running_Proxmox_Virtual_Environment_V0.9beta2 Will still apply. Stop your VMs, check your boot...

vzdump reply thanks for the reply tom. I wasn't expecting it. First off, I would like to say that I wasn't "downing" proxmox in any way, I love it's packaging and KVM/VZ seem to blow the other hypervisors out of the water right now. We use it on our production equipment and recommend it to...

Overcommiting RAM is bad It is possible to over commit RAM, just learned this by doing so accidentally. PVE host on poweredge 2900, 2 KVM guests, both windows - SBS 2008 and Server std. 2008. Server has 8gb of ram total, but a little less actually available to OS (PVE). The VMs were not setup...