Bug 182884 - [xen] FreeBSD HVMPV domU networking does not work
Summary: [xen] FreeBSD HVMPV domU networking does not work
Status: Closed DUPLICATE of bug 188369
Alias: None
Product: Base System
Classification: Unclassified
Component: kern (show other bugs)
Version: Unspecified
Hardware: Any Any
: Normal Affects Only Me
Assignee: freebsd-xen (Nobody)
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-10-10 22:30 UTC by Hugo Saro
Modified: 2016-05-20 09:04 UTC (History)
2 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Hugo Saro 2013-10-10 22:30:00 UTC
Under a NetBSD 6.1.2/amd64 and Xen 4.2.3, FreeBSD 10.0-ALPHA5 network is unstable/unusable.

Trying to ssh in to the virtual machine does not work.

On the first attempt, ssh from the client hung in connect() and at the
FreeBSD domU console there was a panic[1].

On the dom0 console, the following was shown:
xvif3i0: packet size 1610 too big
xvif3i0: packet size 0 too big
xvif3i0: packet size 1544 too big


Disabling txcsum and rxcsum[2] makes the client hang in select() instead,
but on the FreeBSD we still see "xn_txeof: WARNING: response is -1!",
while simultaneously on the dom0 the following is printed to the system
console: "xvif5i0: packet cross page boundary". The SSH connection is of
course never established.
-----

[1] https://webmail.ami.org.pt/panic.jpg
[2] http://lists.freebsd.org/pipermail/freebsd-xen/2011-May/000940.html --
    I saw & reported this same error on 9.x two years ago. It was fixed.
    Also, I run a 10-CURRENT snapshot from maybe half a year ago and
    everything works as expected there as well.
Comment 1 Mark Linimon freebsd_committer freebsd_triage 2013-10-21 00:07:29 UTC
Responsible Changed
From-To: freebsd-bugs->freebsd-emulation

reclassify and assign.
Comment 2 Dexuan Cui 2015-12-09 10:49:26 UTC
The Subject said "[hyper-v]", but the Description said Xen?
Comment 3 Mark Linimon freebsd_committer freebsd_triage 2016-05-20 07:44:31 UTC
Correct Summary and assignment.
Comment 4 Roger Pau Monné freebsd_committer freebsd_triage 2016-05-20 09:04:45 UTC

*** This bug has been marked as a duplicate of bug 188369 ***