2009/6/7 Bruno Damour <ll...@ruomad.net>:
> Well there are a couple of things to take into consideration.
> First, I _did_ get some dom0 crashes so that in deed the opensolaris xvm
> code could be responsible for this
> Second, xen version on opensolaris is still 3.1.4, which may also explain
> the difference and the fact that you can't reproduce the crash on CentOS
> (must be 3.3 ?)
Xen version 3.1.2-128.1.10.el5 (mockbu...@centos.org) (gcc version 4.1.2 200807
04 (Red Hat 4.1.2-44)) Thu May 7 10:31:40 EDT 2009
> Third, there has been a heavy development in opensolaris on he virtual
> network interface level (so call crossbow)
I know about crossbow; I've just not looked into it.
> Four, it might also be related to the actual opensolaris driver (which is
> 3rd party, myk for my Marvell yukon Gb), I could try to test if it's the
> same with another one
It -shouldn't- have anything to do with your physical network hardware
but who knows. :) I haven't looked at the opensolaris source at all.
I know for Linux that it is almost 100% abstracted away via the
bridging layer stuff. The only knowledge of the NIC the netfront
driver has is the hardware TX/RX checksum and TSO.
> Four, i386 vs amd64
Right. I'm running 32 bit in 32 bit; you're running 32 bit domU in 64 bit dom0?
> I think it might be useful to copy this thread to the xen mailing list on
Sure. I'm open to discuss ideas but I'm just a bit too busy with paid
work to be spending many more brain cycles on this for the time being.
I'd like you to wrap all of this up and submit a PR please. I'd like
you to include details about your running opensolaris environment,
hardware, xen hypervisor version and such. I can't make any promises
that I'll be able to set up an opensolaris Xen environment with
debugging support to figure this out any time soon but it may be
possible for me to commit some further sanity checks so we can slowly
narrow down the cause.
firstname.lastname@example.org mailing list
To unsubscribe, send any mail to "freebsd-xen-unsubscr...@freebsd.org"