Michael Monnerie-5 wrote:
>
> Dear admins,
>
> about once or twice a week I receive an e-mail like this from your
> mailing list. It seems it's a part of the message with headers in the
> text. I am subscribed to a whole lot of mailing lists of various
> sources, and never had this problem before. So it must be a problem
> between our two servers. We use standard postfix with
> amavis/spamassassin, and I cannot see an error in the logs.
>
> Anybody else got this problem?
>
> mfg zmi
>
> ---------- Forwarded message from Wenqiang Song: ----------
>
> Betreff:
> Datum: Dienstag, 18. November 2008
> Von: "Wenqiang Song" <
wsong.cn@
gmail.com>
> An:
xen-users@xxxxxxxxxxxxxxxxxxx
>
> --------------------------------------------------
> 0.00 HTML_MESSAGE BODY: HTML included in message
> Subject: [Xen-users] strange domU network behavior
> X-BeenThere:
xen-users@xxxxxxxxxxxxxxxxxxx
> X-Mailman-Version: 2.1.5
> Precedence: list
> List-Id: Xen user discussion <
xen-users.lists.xensource.com>
> List-Unsubscribe: <
http://lists.xensource.com/mailman/listinfo/xen-
> users>,
> <mailto:
xen-users-request@xxxxxxxxxxxxxxxxxxx?subject=unsubscribe>
> List-Post: <mailto:
xen-users@xxxxxxxxxxxxxxxxxxx>
> List-Help: <mailto:
xen-users-request@xxxxxxxxxxxxxxxxxxx?subject=help>
> List-Subscribe: <
http://lists.xensource.com/mailman/listinfo/xen-users>,
> <mailto:
xen-users-request@xxxxxxxxxxxxxxxxxxx?subject=subscribe>
> Sender:
xen-users-bounces@xxxxxxxxxxxxxxxxxxx
> Errors-To:
xen-users-bounces@xxxxxxxxxxxxxxxxxxx
> Return-Path:
xen-users-bounces@xxxxxxxxxxxxxxxxxxx
> MIME-Version: 1.0
> Content-Type: multipart/mixed;
> boundary="===============1784523744=="
>
> --===============1784523744==
> Content-Type: multipart/alternative;
> boundary="----=_Part_50167_13681018.1227014230308"
>
> ------=_Part_50167_13681018.1227014230308
> Content-Type: text/plain; charset=UTF-8
> Content-Transfer-Encoding: 7bit
> Content-Disposition: inline
>
> Hi all,
>
> I have a domU with two vifs, when I run 'tcpdump -i eth1' and ping
> eth1's IP
> address from another machine I found that there is no packet captured.
> In
> fact, all traffic went to eth0.
> Another strange thing is that if I ping eth1 from another VM(I tried
> both
> Xen VM and VMware VM), it can't even go through.
>
> My dom0 has only one NIC.
>
> Any idea?
>
> Thanks
>
> ------=_Part_50167_13681018.1227014230308
> Content-Type: text/html; charset=UTF-8
> Content-Transfer-Encoding: 7bit
> Content-Disposition: inline
>
