Search results

Sorry it's been a bit to update. I been working on the issue from the source to the VM and we found the initial issue for the dropped packets. The log server's (this is the VM) external ethernet was only receiving data and not transmitting. Thus, it's MAC was being removed from the switch's ARP...

This might be a DUH.. but I have to ask, I was looking up some stuff regarding a problem I was see on port 25 of one of my mail server and ran across this thread. http://forum.proxmox.com/threads/1183-bridge-and-forwarding-routing?highlight=make+a+MAC I decided to look at the bridges and this...

I'm seeing that my one vizor is different form the others. That Visor is using the following: 03:00.0 Ethernet controller [0200]: Broadcom Corporation NetXtreme II BCM5708 Gigabit Ethernet [14e4:164c] (rev 12) = eth0 0c:01.0 Ethernet controller [0200]: Intel Corporation 82541PI Gigabit Ethernet...

Ok here is another addition to the 2.6.18 kernel. Kinds of a rough morning as one the the Visors locked up. The Transmit drops are actually packets being sent to the VM from the Visor. Like I stated earlier, this is fixed with the 2.6.24 Kernel, but the 2.6.24 kernel fails under load. The load...

Here is a bit more, I have a visor which holds most of my development servers and one production server(not that important). I'll give the versions of the Visor with the packets dropping and the veth of the the mail server. this is the Visor with dropping packets: hyp-prox00:~# pveversion -v...

Well, I attempted to move to the 2.6.24-11 kernel and that made a horrible day for me. I have a ton of Ethernet traffic with my two mail servers and then I upgraded to the new kernel I saw long delay times when I telnet to port25 on mail servers. With the upgrade, I had no packets dropping, but...

The first and last part is what I need Dietmar. Tomorrow is our maintenance window, I'll see about getting the kernels changes and reboot the visors then. Will update you with the results. Need to update you on the setup as well, the containers are not physically on the visors they are actually...

Considering you are asking my to try another kernel, you are not seeing the same issue.. At this point I am unable to be changing kernels as I would need to reboot the Visors and these are production. What are you expecting? I choose the 2.6.18 kernel as they are supposed to be the most stable...

pve-manager: 1.5-8 (pve-manager/1.5/4674) running kernel: 2.6.18-2-pve proxmox-ve-2.6.18: 1.5-5 pve-kernel-2.6.18-2-pve: 2.6.18-5 pve-kernel-2.6.18-1-pve: 2.6.18-4 qemu-server: 1.1-11 pve-firmware: 1.0-3 libpve-storage-perl: 1.0-10 vncterm: 0.9-2 vzctl: 3.0.23-1pve8 vzdump: 1.2-5 vzprocps...

I have a strange issue what may or may not be a problem. I am seeing an issue where the Visor is dropping transmit packets from the veth connections like below: veth106.0 Link encap:Ethernet HWaddr 00:18:51:37:d6:6b inet6 addr: fe80::218:51ff:fe37:d66b/64 Scope:Link UP...

Re: Booting from HP SAN Then you guys explain to me this.... here is the Fdisk of the Intall from the one computer that your install works on (not using the debian method) Disk c0d0: 119.9 GB, 119998218240 bytes 255 heads, 32 sectors/track, 28722 cylinders Units = cylinders of 8160 * 512 =...

Re: Booting from HP SAN that boot partition is in the LVM... take it out of the lvm.. the HP bios sees the LVM as a single drive and not as three pieces like you have it.

Re: Booting from HP SAN Ok I found the reason why the HPs won't boot after using the Proxmox install, but boot with no problem on my Debian setup.. Dietmar or Tom, PLEASE GIVE CONTROL OF PARTITIONING SCHEME IN THE INSTALL!!!!!! The problem with the HPs are that they use an interesting...

1. Live Migrations without paying 12,000 Dollars a year!!! 2. Central Management "Clustering" without paying 12,000 Dollars a year!!! 3. Simple Linux implemtation (except for the lack of controll of the partitioning scheme) 4. OPEN-SOURCE!!!!! meaning, don't pay 12,000 dollars a year...

Re: Booting from HP SAN Yep, I use a NetAPP San and NFS for all my VMs and nothing is on my vizors. This is why I'm not even using LVM as it more configuration, especially with the debian install. I use only ext3 on my LUN HPs.

What I ended up doing is the the debian install with proxmox on top.. I'm thinking that the LUNs don't like the way the PROXMOX installs the bootloader and I know that debian has no problem. So, I installed the base system of debian and then followed the WIKI to installing PROXMOX on top of...

well, since I got all three of my servers running and clustered, I'll have to kill one of them to test this cd.. I'll let you know this week. I think part of this issue is the SAN and the HP, but it seems if I use LVM I'm screwed. I'll give the new CD a shot next week. Hell, I want the KSM...

Here is an update on my servers.. WE HAVE LIFT OFF!!!! I finally got both my LUN only HP servers to boot. I believe problem is mixed LVM and possible how the boot loader is configured. I had to use the AMD64 Debian Lenny approch to ge the system to boot, then I followed your how-to and...

The only disk on this is the LUN. The thing that is tripping me up here is that I'm not even booting the OS. It can't find the boot sector. I manually set it and still no. I install Debian64Bit and ended up with the same results. I actually have 2 of the HP 1Us and I'm prepping the second one...

At work now, and I took a 64BIT gentoo live CD to the system. was able to chroot into it and run grub to install on master boot record. still the same problem. I have no clue here.