On Wed, Sep 8, 2010 at 7:25 PM, Sauro Saltini <saltini@xxxxxx> wrote:
> vif=[ 'type=paravirtual, bridge=br0, mac=00:16:3e:00:00:02',
> 'type=paravirtual, bridge=br1, mac=00:16:3e:00:00:20' ]
you don't need "type=paravirtual", just remove it. Where did you find
"type=paravirtual" anyway? I've never seen it on any of the examples.
> boot='c'
you don't need this as well. It's not used on PV domU.
> sdl=0
> vnc=0
I'm pretty sure you don't need those two lines, since PV domUs use "vfb=..."
> Pinging 192.168.99.202 from testing domU (10.0.0.102) doesn't work, and
> tcpdump -nvvi on dom0 (both listening on vifx.y or bridge) gives (every 5 to
> 10 seconds):
> ....
> 14:17:29.922210 ARP, Ethernet (len 6), IPv4 (len 4), Request who-has
> 192.168.99.202 tell 192.168.99.88, length 28
> 14:17:29.922304 ARP, Ethernet (len 6), IPv4 (len 4), Reply 192.168.99.202
> is-at 00:09:6b:89:d0:8a, length 46
> ....
>
> but no icmp traffic at all !
At this point I'd start with using known-good setup first, since it
can save a lot of time. Try using 2.6.34 + the patch I mentioned
earlier for both dom0 and PV domU.
--
Fajar
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
|