Date: Mon, 18 Mar 2013 11:17:33 +0100 From: Fleuriot Damien <ml@my.gd> To: "Eugene M. Zheganin" <emz@norma.perm.ru> Cc: "freebsd-net@freebsd.org" <freebsd-net@freebsd.org> Subject: Re: carp regression in 9.1 ? Message-ID: <D32D7487-7996-4D18-A3F5-9B60125440EE@my.gd> In-Reply-To: <39FC9737-4F34-4978-BDFE-17410CD2E5C4@my.gd> References: <3B04FCB1-D0D4-4BC9-BB15-5221F438738C@my.gd> <514594D7.1020202@norma.perm.ru> <39FC9737-4F34-4978-BDFE-17410CD2E5C4@my.gd>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mar 18, 2013, at 9:23 AM, Damien Fleuriot <ml@my.gd> wrote: >=20 > On 17 Mar 2013, at 11:03, "Eugene M. Zheganin" <emz@norma.perm.ru> = wrote: >=20 >> Hi. >>=20 >> On 14.03.2013 20:47, Fleuriot Damien wrote: >>> I'm experiencing this odd behavior with 9.1 r24791 for amd64. >> You should definitely sit on 8.x until 10.x will become stable, or = upgrade to 10.x from 9.x (at least this is what I do). >> Carp is entirely rewritten in 10.x branch. In the same time, in 9.x = carp seems to be desperately broken: for example I was experiencing = weird panics on boot, weird behaviour, and, when enabling WITNESS, lots = of carp-related LORs. Furthermore, I was completely unable to boot up = with a ipv6-enabled carp - I had to initialize it in multiuser with a = custom script. All of this doesn't happen on 10.x, which I had to = upgrade to. Right now, if we're talking about carp, my 10.x production = works like a charm. 9.x branch just isn't destined to production. The = situation is a bit improved on 9.1, but still I can compare this release = to 4.6 or 5.0. >>=20 >> Eugene. >>=20 >=20 >=20 > I'm afraid I can't afford 10.x, this is for production, although I = acknowledge the problems you're faced with. >=20 > Regarding 8.x, this is a guest VM running on proxmox 2.3 which doesn't = support stock 8.x (need the virtio kernel option, I'll get a thread = reference when I hit work). >=20 >=20 > So yeah I'm kinda fucked here... ;) The link to the thread on the proxmox forum where many people report 8.x = not working with proxmox 2.3: http://forum.proxmox.com/threads/13013-Error-pfsense-freebsd Apparently it's now a known bug and is related to a KVM bios update. A dirty and temporary fix is to use an old bios (say from 2.0 or 2.2) in = the vm config: =3D=3D=3D args: -bios /usr/share/kvm/bios_old.bin =3D=3D=3D It seems a fix has been submitted by the devs and it reportedly works: = http://forum.proxmox.com/threads/13013-Error-pfsense-freebsd?p=3D71136#pos= t71136 I confirm the updated BIOS (which has already been committed to the = debian packages) fixes the problems and allows 8.x to boot. So, I guess I'm going to happily revert that 9.1 to 8.3 eh=85 Still doesn't explain the CARP regressions though :(
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?D32D7487-7996-4D18-A3F5-9B60125440EE>