Paul Fisher wrote: > Basically, I'm stuck even being able to generate a vnic over my > (inactive) e1000g0 interface: > > [EMAIL PROTECTED]:~$ pfexec dladm show-link > LINK CLASS MTU STATE OVER > e1000g0 phys 1500 down -- > iwk0 phys 1500 up -- > > [EMAIL PROTECTED]:~$ /usr/lib/vna e1000g0 08:00:27:22:5E:3A > Invalid link name: e1000g0 >
I went back and tried this again, hoping to make some more progress, and apparently I can get the vnic defined over the inactive e1000g0 interface. Please disregard, I believe it was as simple as being too tired (and forgetting to use pfexec). Local networking works just by manually doing: $ pfexec /usr/lib/vna e1000g0 08:00:27:22:5E:3A vnic0 $ pfexec ifconfig vnic0 plumb $ pfexec ifconfig vnic0 192.168.254.1/24 up $ pfexec svccfg -s xvm/xend setprop config/default-nic = \"vnic0\" $ pfexec xm start etch-01 The in the domU do: # ifconfig eth0 192.168.254.10/24 up Ping works both ways now! Now to get NAT configured... -- paul _______________________________________________ xen-discuss mailing list [email protected]
