Re: Xen 3.3/NetBSD 5.1 DOM0: bridge not working if vcpus>1

["Cherry G. Mathew" <cherry.g.mathew%gmail.com@localhost>]

On 10 November 2011 09:35, Ron McDowell <rcm%fuzzwad.org@localhost> wrote:
>
> Cherry G. Mathew wrote:
>
> On 10 November 2011 01:16, Ron McDowell <rcm%fuzzwad.org@localhost> wrote:
> ...
>
>
> *.vcpu1 works fine, *.vcpu4 does not, only change to the config file  is
> /vcpus/s/1/4/
>
>
>
>
> The logs looks ok to me - when you say "does not work", this means
> that you can't access your virtual network adapter from "outside" when
> vcpus > 1, yes ?
>
>
> correct.  ping and/or ssh to the DOMU works if vcpus=1; if vcpus >1 ping/ssh
> acts like DOMU is powered off.
>
> If you have console on the domU, are you able to access the network
> via the bridge, when vcpu > 1 ?
>
> no. but when vcpu=1 everything [ping/ssh/wget] is fine.
>
> Also, are you able to run other domU
> OSes successfully with vcpus > 1 via the NetBSD dom0 ?
>
>
> Now THAT, it turns out, is the money question. :)  The only DOMU I really
> wanted more than 1 vcpu for is, of course, the only one exhibiting this
> behavior.  It's FreeBSD 8.2-RELEASE amd64.  Other DOMUs here are OpenBSD-4.8
> amd64 and Ubuntu 10.04 amd64, and they work with 1 or more vcpus.  I quickly
> threw on a FreeBSD 9.0-RC1 amd64, and it works fine with 4 vcpus.
>
> While I'm still kinda puzzled by why changing A can make X quit working, I
> can easily settle for upgrading the errant DOMU to 9.0.  It's just odd...
>
>

From a NetBSD PoV, one thing that could help is to try to reproduce
this with a non-NetBSD dom0.

-- 
~Cherry