Marc Neitzner wrote:> Hi, > > yes, sure, but the problem is, that the configuration did not change, > the nic yukonx1 is still > the same, available and up and running. The only difference is, that the > system is now on snv_127, > while this never happend up and including snv_126. Thus it seems that > something odd did happen. > Why does dladm not recognize the adapter any longer ?I don''t believe this drivers is distributed with Solaris? Did you download it from Marvell? Is it still installed on the system? If so, do any yukon related messages show up under /var/adm/messages MRJ> Best regards, Marc > > John Levon schrieb: >> On Sun, Nov 29, 2009 at 05:36:49PM +0100, Marc Neitzner wrote: >> >> >>> => dladm: invalid link name ''yukonx1'': object not found >>> >> You must have specified this as your bridge name in the XML config for >> the guest - remove this with virsh edit. >> >> regards >> john >> > _______________________________________________ > xen-discuss mailing list > xen-discuss@opensolaris.org
Hi !
In snv_127 I suddenly face a problem I never had before. Xvm can''t
attach a vif to my primary
physical nic any longer:
$ pfexec xm start ulrac1
Error: Device 0 (vif) could not be connected. error: Failed to create
vnic over yukonx1 with MAC address 00:16:36:3c:bf:70
This worked fine in all previous snv_12x releases I tested, including
snv_126. I think there is a privilege issue somewhere.
The physical nic works fine as usual. Any hints ?
Thanks
Marc
John Levon schrieb:> On Sun, Nov 29, 2009 at 05:11:13PM +0100, Marc Neitzner wrote: > > >> $ pfexec xm start ulrac1 >> Error: Device 0 (vif) could not be connected. error: Failed to create >> vnic over yukonx1 with MAC address 00:16:36:3c:bf:70 >> > > /var/log/xen/xpvd-event.log should have the reason. > > regards > john >Hi, thanks for the reply ! => dladm: invalid link name ''yukonx1'': object not found I checked "dladm show-phys" and it does not return any nic. I also had a look using "truss-f" to check what dladm is looking for, but unfortunately I can''t find any obvious location/devices where dladm is is looking for the physical devices. Best regards Marc
On Sun, Nov 29, 2009 at 05:11:13PM +0100, Marc Neitzner wrote:> $ pfexec xm start ulrac1 > Error: Device 0 (vif) could not be connected. error: Failed to create > vnic over yukonx1 with MAC address 00:16:36:3c:bf:70/var/log/xen/xpvd-event.log should have the reason. regards john
On Sun, Nov 29, 2009 at 05:36:49PM +0100, Marc Neitzner wrote:> => dladm: invalid link name ''yukonx1'': object not foundYou must have specified this as your bridge name in the XML config for the guest - remove this with virsh edit. regards john
Hi, yes, sure, but the problem is, that the configuration did not change, the nic yukonx1 is still the same, available and up and running. The only difference is, that the system is now on snv_127, while this never happend up and including snv_126. Thus it seems that something odd did happen. Why does dladm not recognize the adapter any longer ? Best regards, Marc John Levon schrieb:> On Sun, Nov 29, 2009 at 05:36:49PM +0100, Marc Neitzner wrote: > > >> => dladm: invalid link name ''yukonx1'': object not found >> > > You must have specified this as your bridge name in the XML config for > the guest - remove this with virsh edit. > > regards > john >