Search results

Hi, As you know, I'm quickly trying to move all our new servers to Debian squeeze. One of the last pending issues is to adapt the OpenVZ and PVE init scripts to the new policy, which basically means adding LSB init headers and not using just a symlink but do a real script install so it's not...

Sorry for the noise, a bit more of tampering revealed it was a transient error, but only with ftp.de.debian.org. All other mirrors appeared to be OK.

Hi, I have been experimenting with creating a Squeeze template and have managed to create a usable template, with some init errors which I'll look at in the following hours. However, today dab fails at `dab bootstrap`, with the following error: bvsh04:~/iti# dab bootstrap initialize VE...

Tom, would this help? The following patch adds an igb target to the 2.6.18 (current preferred PVE kernel) build system, similar to the AoE target. It currently depends on igb release 2.1.9, available at...

Tom, dont' get me wrong, I fully understand that and have no problems accepting it. I'm not sure how many people are paid for working on PVE, but I think your patience and care when replying to most threads on the forum is really admirable. I'll see what we do in our systems to make sure the...

Hi again, With no intention to harass or annoy, it would be helpful if the proxmox team can indicate if this will be considered for the next kernel release, because if it's not going to I'll have to hack my own solution, be it a package that diverts the old module in favour of the new one, or...

Hi Tom, Well, the module will be overwritten on the next PVE kernel update, and I'll have to do the process manually every time there's an ABI bump. Besides, I assume more people will end up getting this same hardware and will find Proxmox VE does not work for them (unless they use 2.6.32)...

Hello PVE team! Very recently, our Blade 6048 got a few new blades. We've discovered that the hardware differs a bit from those we already had, and one of the differences appears to be a different network card. Old blade model: 08:00.0 Ethernet controller: Intel Corporation 80003ES2LAN Gigabit...

Hi Dietmar, A recent change in vzlist added trailing spaces to the output of "vzlist -Ho status $veid", thus breaking some scripts (monitoring, backup) we've developed in-house. The change is minimal: before it printed "running", while it now prints "running ". I've reported this as...

Wow, I realize this box is running an ancient PVE version (etch based!) which we're trying to empty to reinstall, and I suspect this bug must be fixed already in the current versions. If so, sorry about the noise.

Hi, We had several PVE backup jobs in a server, which had a OpenVZ container and three KVMs. We recently moved one of the KVMs to a second host (in another PVE cluster) and destroyed the OpenVZ container. Since then, we get the following: Subject: [Sysadmin] Cron <root@admon01> vzdump...

Hi Dietmar, Just for you to know I haven't forgotten about this; we have not been able to reboot the server yet. We will do this test as soon as possible. Thanks!

It's not very easy in this setup, as the NFS server is also running the head node of a computing cluster (Torque server) and we won't be able to stop it in a while. Hopefully we can setup a mini cluster for testing soon. By the way, thanks for reintroducing initrd autogeneration in 2.6.24-10-pve!

The NFS server is running 2.6.24-9-pve.

The kernel server is the standard lenny kernel server: ii nfs-kernel-ser 1:1.1.2-6lenny support for NFS kernel server I haven't been able to test without the wrapper. We'll try to setup a test box ASAP that we can crash at will, as I've restarted the whole cluster using 2.6.24-10-pve...

I'm starting a new thread for the discussion started in http://proxmox.com/forum/showthread.php?p=16824#post16824. Yesterday, an update of the 2.6.18 PVE kernel from pvetest brought down our entire cluster within minutes; all the hosts were locked with a kernel panic apparently related to...

Re: New Proxmox VE Kernels (2.6.18 - 2.6.24 - 2.6.32) Ok, the good news is that I can very easily reproduce this just a few seconds after starting the container in that PVE install. The bad news is that I can't get any more kernel panic output than what I already posted. If you need more...

Re: New Proxmox VE Kernels (2.6.18 - 2.6.24 - 2.6.32) Weird, it failed in cascade on all nodes after upgrading the kernel to -4, and after no problems with -3 for days. Ok. For now, all I can do is post a screenshot of the ILOM from one of the crashed ndoes. The panic error isn't show...

Re: New Proxmox VE Kernels (2.6.18 - 2.6.24 - 2.6.32) Hi Dietmar, We're in the middle of our migration from 2.6.24 to 2.6.18 due to the socket problems described in http://www.proxmox.com/forum/showthread.php?p=15976#post15976. While the 2.6.18-1-pve kernel resolves this issue, the latest...

Then I'll use the 2.6.18 kernel, thanks a lot for your help.