Hi andrew,
Le 3 mai 2010 à 17:48, Andrew Kolchoogin a écrit :
> Hm-m-m-m-m-m...
>
> It seems to me that FreeBSD paravirtualised network drivers are buggy.
>
> First of all, try to convert your virtual machine back to HVM mode, re-build
> kernel with /sys/amd64/XENHVM kernel configuration file and attach virtual
> Xen network interface to guest.
>
> I've done steps I've spoken about, and network stops working. Well, not
> really COMPLETELY stops: packets can pass back and forth between FreeBSD DomU
> and network, but any TCP connection stalls immediately just after so-called
> "three-way handshake".
>
> Analysing Dom0 log files gives strange errors like "unknown flag 0x04
> received". I'm really not a Xen hacker but do know FreeBSD kernel well enough
> to analyse /sys/dev/xen and figure out that this flag is about LRO. Well, it
> is more than clear that it is fairly stupid to "off-load" anything to
> software emulator of network hardware :), but due to some unclear reason I
> can't turn off this behaviour even with sysctl and interface reset ("ifconfig
> xn0 down && ifconfig xn0 up").
>
> Anyway, FreeBSD v8.0/paravirtualised is completely unusable for now -- when
> you try to create more than one virtual network interface in DomU, kernel
> will panic. Yes, I've filled PR. :)
> FreeBSD v8.0/HVM is more usable, but network drivers are buggy.
Do you use FreeBSD 8.0/Amd64 or freeBSD 8.0/i386 ?
/Xavier
_______________________________________________
xen-discuss mailing list
[email protected]
