crossbow discuss - Apr 2007 - Testing IP Instances in 62 on vmware

The network fails for the zone when i try to setup it with ip-type exclusive.

Its on a vmware server 1.0.2 using a emulated e1000g, this is the only current
way i have got to test it with :(

Any ideas on how to find out what the problem is?  
Is it that the emulation done by vmware can''t do this?

I think it would be useful for this to work in vmware, as you can add many
virtual nics to an install to play with this stuff.
 
 
This message posted from opensolaris.org

(I presume you are running nv62 as a guest OS of vmware)
John-Paul Drawneek Wrote:
> The network fails for the zone when i try to setup it with ip-type
exclusive.
When did it fail?
Is it
when you do "set ip-type=exclusive" in zonecfg?
or
when you do zoneadm -z <your zone> boot?
Is there any error message?
> 
> Its on a vmware server 1.0.2 using a emulated e1000g, this is the only
current way i have got to test it with :(
If you can plumb that e1000g in the global zone, it should work in
exclusive-IP zones too.
> 
> Any ideas on how to find out what the problem is?  
> Is it that the emulation done by vmware can''t do this?
> 
> I think it would be useful for this to work in vmware, as you can add many
virtual nics to an install to play with this stuff.
Sure, thanks for trying it on vmware.

Best,

Donghai.

> (I presume you are running nv62 as a guest OS of
> vmware)
> John-Paul Drawneek Wrote:
> > The network fails for the zone when i try to setup
> it with ip-type exclusive.
> When did it fail?
> Is it
> when you do "set ip-type=exclusive" in zonecfg?
> or
> when you do zoneadm -z <your zone> boot?
> Is there any error message?
svcs physical fails - and you can''t ping the ip address from inside the
zone.
Also when you set the ip address when you are configuring the zone (this is in
side the zone) there is an error message about ip address can''t be set.
Its really quickly displayed as it appears between two screens of the configure
thingy when solaris boots for the first time.
> 
> > 
> > Its on a vmware server 1.0.2 using a emulated
> > e1000g, this is the only current way i have got to
> > test it with :(
> If you can plumb that e1000g in the global zone, it
> should work in
> exclusive-IP zones too.
Thats what i though, but theres no joy.
> 
> > 
> > Any ideas on how to find out what the problem is?  
> > Is it that the emulation done by vmware can''t do
> > this?
> > 
> > I think it would be useful for this to work in
> > vmware, as you can add many virtual nics to an
> > install to play with this stuff.
> Sure, thanks for trying it on vmware.
> 
> Best,
> 
> Donghai.
> _______________________________________________
> crossbow-discuss mailing list
> crossbow-discuss at opensolaris.org
> http://opensolaris.org/mailman/listinfo/crossbow-discu
> ss
>
 
 
This message posted from opensolaris.org

If zoneadm boot didn''t give any warning, the zone should already
have the interface, could you please take a look under /dev in
the zone, and see if /dev/e1000g0 is there?

Also you could do a "ifconfig -a plumb", and see if e1000g0 get
plumbed, if that''s the case, then it should be other things went
wrong.

What does the log of physical 
(/etc/svc/volatile/network-physical:default.log) say BTW.

Best,

Donghai.

John-Paul Drawneek Wrote:
>>(I presume you are running nv62 as a guest OS of
>>vmware)
>>John-Paul Drawneek Wrote:
>>
>>>The network fails for the zone when i try to setup
>>
>>it with ip-type exclusive.
>>When did it fail?
>>Is it
>>when you do "set ip-type=exclusive" in zonecfg?
>>or
>>when you do zoneadm -z <your zone> boot?
>>Is there any error message?
> 
> 
> svcs physical fails - and you can''t ping the ip address from
inside the zone.
> Also when you set the ip address when you are configuring the zone (this is
in side the zone) there is an error message about ip address can''t be
set.  Its really quickly displayed as it appears between two screens of the
configure thingy when solaris boots for the first time.
> 
> 
>>>Its on a vmware server 1.0.2 using a emulated
>>>e1000g, this is the only current way i have got to
>>>test it with :(
>>
>>If you can plumb that e1000g in the global zone, it
>>should work in
>>exclusive-IP zones too.
> 
> 
> Thats what i though, but theres no joy.
> 
> 
>>>Any ideas on how to find out what the problem is?  
>>>Is it that the emulation done by vmware can''t do
>>>this?
>>>
>>>I think it would be useful for this to work in
>>>vmware, as you can add many virtual nics to an
>>>install to play with this stuff.
>>
>>Sure, thanks for trying it on vmware.
>>
>>Best,
>>
>>Donghai.
>>_______________________________________________
>>crossbow-discuss mailing list
>>crossbow-discuss at opensolaris.org
>>http://opensolaris.org/mailman/listinfo/crossbow-discu
>>ss
>>
> 
>  
>  
> This message posted from opensolaris.org
> _______________________________________________
> crossbow-discuss mailing list
> crossbow-discuss at opensolaris.org
> http://opensolaris.org/mailman/listinfo/crossbow-discuss

ok found out that it was because of an ip conflict.

this was not obvious, than it normal is - could be a bug, or could be made
clear.

Got to many vm on the go.

> If zoneadm boot didn''t give any warning, the zone
> should already
> have the interface, could you please take a look
> 
> What does the log of physical 
> (/etc/svc/volatile/network-physical:default.log) say
> BTW.
> 
> Best,
> 
> Donghai.
>
 
 
This message posted from opensolaris.org

John-Paul Drawneek wrote:
> ok found out that it was because of an ip conflict.
> 
> this was not obvious, than it normal is - could be a bug, or could be made
clear.
We''ve had IPv4 duplicate address support in Solaris Nevada for a while,
thus from inside the zone ifconfig -a should show that it failed due to 
a duplicate IP address. But this doesn''t get logged outside of the
zone.
> Got to many vm on the go.
Might make sense to configure them using DHCP assuming you have a DHCP 
server.

    Erik