https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=188369
Roger Pau Monné changed:
What|Removed |Added
CC||h...@barafranca.com
--- Comment
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=188369
miguelmcl...@gmail.com changed:
What|Removed |Added
Resolution|--- |FIXED
Severity|A
so disabling txcsum stops the panic when I try ssh-in but I stil see the
"xn_txeof: WARNING: response is -1" message and it eventually times out.
--
You are receiving this mail because:
You are the assignee for the bug.
___
freebs
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=188369
--- Comment #11 from miguelmcl...@gmail.com ---
Is the kgbd info helpful? Any extra info I can add?
--
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-xen@freeb
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=188369
--- Comment #10 from miguelmcl...@gmail.com ---
As requested in freebsd-xen mailing list:
this is from a core dumb after reboot (saved to /var/crash)
KDB: stack backtrace:
#0 0x8095b070 at kdb_backtrace+0x60
#1 0x8091f765
load the kernel in to gdb or kgdb and type: i li *xn_intr+0x74 to get
the offending line number
On Sat, Jan 31, 2015 at 6:44 AM, wrote:
> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=188369
>
> --- Comment #9 from miguelmcl...@gmail.com ---
> One thing to note is that the panic is not relat
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=188369
--- Comment #9 from miguelmcl...@gmail.com ---
One thing to note is that the panic is not related to the "mbuf already on the
free list" anymore:
Fatal trap 12: page fault while in kernel mode
cpuid = 0; apic id = 00
fault virtual address
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=188369
--- Comment #8 from miguelmcl...@gmail.com ---
PARTICULARY THIS:
+/* GSO Prefix descriptor. */
+#define _NETRXF_gso_prefix (4)
+#define NETRXF_gso_prefix (1U<<_NETRXF_gso_prefix)
+
GSO is not supported by the netbsd backend I had
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=188369
--- Comment #7 from miguelmcl...@gmail.com ---
Dunno if this will help in anyway... I lack C skills and I certainly don't know
much about the Xen code...
In anycase I will post my findings:
I decided to compare the changes on 9 and 10, be
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=188369
--- Comment #6 from miguelmcl...@gmail.com ---
And since FreeBSD10 comes with XENHVM precompiled/loaded any freebsd10+ guest
starts in a none working state! :(
I should clarify that statement by saying:
It start in a non working sate in reg
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=188369
--- Comment #5 from miguelmcl...@gmail.com ---
NOTE: NetBSD just announced support for Xen 4.5.
I've tested with FreeBSD 9.3 which works fine but anything 10.0+ fails with
this error!
And since FreeBSD10 comes with XENHVM precompiled/loade
Old Synopsis: FreeBSD 10 XENHVM panic under NetBSD Dom0 (xn_txeof: WARNING:
response is -1)
New Synopsis: [xen] [panic] FreeBSD 10 XENHVM panic under NetBSD Dom0
(xn_txeof: WARNING: response is -1)
State-Changed-From-To: open->open
State-Changed-By: linimon
State-Changed-When: Sun Apr 20 01
On 05/29/11 14:11, K. Macy wrote:
> Just to verify, other guests (e.g. Linux || NetBSD) don't exhibit this
> problems? It sounds almost as if xend isn't configuring the domain
> properly.
>
Hello,
I'm not sure about Linux but a NetBSD 5.1 PV domU works fine. Others are
running Linux PV on NetBSD
Just to verify, other guests (e.g. Linux || NetBSD) don't exhibit this
problems? It sounds almost as if xend isn't configuring the domain
properly.
-Kip
On Sun, May 29, 2011 at 1:02 PM, Hugo Silva wrote:
> On 05/25/11 17:20, Hugo Silva wrote:
>> On 05/24/11 21:14, Hugo Silva wrote:
>>> On 05/24/
On 05/25/11 17:20, Hugo Silva wrote:
> On 05/24/11 21:14, Hugo Silva wrote:
>> On 05/24/11 14:45, Hugo Silva wrote:
>>> Trying to ssh to the VM produces the error in the subject line on the
>>> FreeBSD domU; It's impossible to login.
>>>
>>
>> Some more information for those looking to reproduce th
On 05/24/11 21:14, Hugo Silva wrote:
> On 05/24/11 14:45, Hugo Silva wrote:
>> Trying to ssh to the VM produces the error in the subject line on the
>> FreeBSD domU; It's impossible to login.
>>
>
> Some more information for those looking to reproduce this: the above is
> with rxcsum and txcsum di
On 05/24/11 14:45, Hugo Silva wrote:
> Trying to ssh to the VM produces the error in the subject line on the
> FreeBSD domU; It's impossible to login.
>
Some more information for those looking to reproduce this: the above is
with rxcsum and txcsum disabled in the xn interface: Without that, the
s
Hello,
NetBSD -current dom0
FreeBSD 8.2-STABLE domU.
Trying to ssh to the VM produces the error in the subject line on the
FreeBSD domU; It's impossible to login.
I found a few references in google, but nothing conclusive.
___
freebsd-xen@freebsd.org
18 matches
Mail list logo
