On Wed, Jul 8, 2009 at 8:58 AM, David Edmondson<dme at sun.com> wrote:
> * estseg at gmail.com [2009-07-07 21:51:49]
>> It could be completely not related but I installed dom0 2009.06 111b,
>> and 2x domU 2009.06 111b on one machine.
>> I know it's a different setup but I have very weird issue with it..
>> dom0#
>> clintr1 ? ? etherstub 9000 ?unknown ?--
>> n1intr1 ? ? vnic ? ? 9000 ? up ? ? ? clintr1
>> n2intr1 ? ? vnic ? ? 9000 ? up ? ? ? clintr1
>>
>> node1 and node2 are pvm domU 2009.06 111b with Colorado (installed
>> from my own repository) but cluster is not yet configured.
>> I added one vnic to each node for interconnect:
>> dom0# virsh attach-interface node1 bridge n1intr1 --script vif-dedicated
>>
>> The issue is I can't ping those nodes using interconnect interfaces,
>> even snoop doesn't see anything.
>
> You must set the MTU of the etherstub to 1500 before creating the VNICs
> for the guest domains.
Thanks.

Ok, the setup is different, but I am pretty sure it's the same BUG:

# xm start -c node2
v3.1.4-xvm chgset 'Wed Apr 08 14:27:49 2009 -0700 15914:cd2d74aa8832'
SunOS Release 5.11 Version snv_111b 64-bit
Copyright 1983-2009 Sun Microsystems, Inc.  All rights reserved.
Use is subject to license terms.
NOTICE: softmac: received DL_ERROR_ACK to DL_BIND_ACK; DLPI errno
0xfb83adae, UNIX errno -1
Hostname: node2
Configuring devices.
Booting in cluster mode
name is non-existent for this module
for a list of valid names, use name '?'
NOTICE: CMM: Node node1 (nodeid = 1) with votecount = 1 added.
NOTICE: CMM: Node node2 (nodeid = 2) with votecount = 0 added.
NOTICE: clcomm: Adapter vnic0 constructed
NOTICE: CMM: Node node2: attempting to join cluster.
NOTICE: CMM: Cluster doesn't have operational quorum yet; waiting for quorum.
NOTICE: clcomm: Path node2:vnic0 - node1:vnic0 errors during initiation
WARNING: Path node2:vnic0 - node1:vnic0 initiation encountered errors,
errno = 62. Remote node may be down or unreachable through this path.



-- 
Piotr Jasiukajtis | estibi | SCA OS0072
http://estseg.blogspot.com

Reply via email to