thr3ads.net - Xen users - [Xen-users] Xen Installation without virtualization enabled in Bios [Jul 2008]

If this information is useful, please help other people find it:
Share via:

s@l

2008-Jul-21 20:34 UTC

[Xen-users] Xen Installation without virtualization enabled in Bios

Hi there,

Having a problem with Xen using RHEL 5.  Using a dell poweredge 1950 with
BCM5708 integrated NIC''s. 

07:00.0 Ethernet controller: Broadcom Corporation NetXtreme II BCM5708
Gigabit Ethernet (rev 12)
        Subsystem: Dell Unknown device 01b3
        Control: I/O- Mem+ BusMaster+ SpecCycle+ MemWINV+ VGASnoop- ParErr+
Stepping- SERR+ FastB2B-
        Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort-
<TAbort- <MAbort- >SERR- <PERR-
        Latency: 64 (16000ns min), Cache Line Size: 64 bytes
        Interrupt: pin A routed to IRQ 16
        Region 0: Memory at f4000000 (64-bit, non-prefetchable) [size=32M]
        Capabilities: [40] PCI-X non-bridge device
                Command: DPERE- ERO- RBC=512 OST=8
                Status: Dev=07:00.0 64bit+ 133MHz+ SCD- USC- DC=simple
DMMRBC=512 DMOST=8 DMCRS=32 RSCEM- 266MHz- 533MHz-
        Capabilities: [48] Power Management version 2
                Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA
PME(D0-,D1-,D2-,D3hot+,D3cold+)
                Status: D0 PME-Enable- DSel=0 DScale=1 PME-
        Capabilities: [50] Vital Product Data
        Capabilities: [58] Message Signalled Interrupts: 64bit+ Queue=0/0
Enable-
                Address: 214082b132d03000  Data: 0b40



Basically, I have this strange issue where everything is good, I can create
my virtual guests, but there is some issue with network connectivity.  I can
get to the outside world no problem from the virtual host, but on the
guests, I can only ping the local machine, I cant ping or access anything on
the outside world. 

At first I was taking a look at drivers and other network related problems,
when I noticed that the virtualization option in the bios cpu settings was
NOT enabled.  I enabled it, but im still having the same problem.

My question is: Would installing RHEL 5 and Xen while this option was NOT
enabled in the bios cause problems and perhaps cause this networking
connectivity issue im experiencing? Do I need to reinstall xen? 

Info: 

version: xen-3.0.3-64.el5_2.1
-- 
View this message in context:
http://www.nabble.com/Xen-Installation-without-virtualization-enabled-in-Bios-tp18532312p18532312.html
Sent from the Xen - User mailing list archive at Nabble.com.


_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

Dustin Henning

2008-Jul-21 20:40 UTC

head link

RE: [Xen-users] Xen Installation without virtualization enabled in Bios

The virtualization option in the BIOS is for HVM (Full
Virtualization).  Seeing as how you had guests before this option was
enabled, you are clearly using PV.  As such, the option would have no effect
that I know of.  That said, your problem probably lies in Xen configuration.
Is this your first Xen box?  Hopefully someone skilled at troubleshooting
network connectivity issues in Xen can assist you with this.
	Dustin

-----Original Message-----
From: xen-users-bounces@lists.xensource.com
[mailto:xen-users-bounces@lists.xensource.com] On Behalf Of s@l
Sent: Monday, July 21, 2008 16:35
To: xen-users@lists.xensource.com
Subject: [Xen-users] Xen Installation without virtualization enabled in Bios


Hi there,

Having a problem with Xen using RHEL 5.  Using a dell poweredge 1950 with
BCM5708 integrated NIC''s. 

07:00.0 Ethernet controller: Broadcom Corporation NetXtreme II BCM5708
Gigabit Ethernet (rev 12)
        Subsystem: Dell Unknown device 01b3
        Control: I/O- Mem+ BusMaster+ SpecCycle+ MemWINV+ VGASnoop- ParErr+
Stepping- SERR+ FastB2B-
        Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort-
<TAbort- <MAbort- >SERR- <PERR-
        Latency: 64 (16000ns min), Cache Line Size: 64 bytes
        Interrupt: pin A routed to IRQ 16
        Region 0: Memory at f4000000 (64-bit, non-prefetchable) [size=32M]
        Capabilities: [40] PCI-X non-bridge device
                Command: DPERE- ERO- RBC=512 OST=8
                Status: Dev=07:00.0 64bit+ 133MHz+ SCD- USC- DC=simple
DMMRBC=512 DMOST=8 DMCRS=32 RSCEM- 266MHz- 533MHz-
        Capabilities: [48] Power Management version 2
                Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA
PME(D0-,D1-,D2-,D3hot+,D3cold+)
                Status: D0 PME-Enable- DSel=0 DScale=1 PME-
        Capabilities: [50] Vital Product Data
        Capabilities: [58] Message Signalled Interrupts: 64bit+ Queue=0/0
Enable-
                Address: 214082b132d03000  Data: 0b40



Basically, I have this strange issue where everything is good, I can create
my virtual guests, but there is some issue with network connectivity.  I can
get to the outside world no problem from the virtual host, but on the
guests, I can only ping the local machine, I cant ping or access anything on
the outside world. 

At first I was taking a look at drivers and other network related problems,
when I noticed that the virtualization option in the bios cpu settings was
NOT enabled.  I enabled it, but im still having the same problem.

My question is: Would installing RHEL 5 and Xen while this option was NOT
enabled in the bios cause problems and perhaps cause this networking
connectivity issue im experiencing? Do I need to reinstall xen? 

Info: 

version: xen-3.0.3-64.el5_2.1
-- 
View this message in context:
http://www.nabble.com/Xen-Installation-without-virtualization-enabled-in-Bio
s-tp18532312p18532312.html
Sent from the Xen - User mailing list archive at Nabble.com.


_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users



_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

Daniel Kao

2008-Jul-21 20:50 UTC

head link

Re: [Xen-users] Xen Installation without virtualization enabled in Bios

Dustin pretty much described where you need to look next.  Since PV is
working, it''s definitely a configuration issue in your dom0.

Have a quick look at:

http://wiki.xensource.com/xenwiki/XenNetworking

Then check your:

/etc/xen/xend-config.sxp (in your dom0)

And then check your domU''s network configuration.

We need to know if you''ve set Xen in either, bridging mode, routed mode
or NAT mode in your dom0.  If you''re able to ping dom0 from your domU,
are you setting static IP''s or using DHCP, etc.

Cheers,

Daniel

Dustin Henning wrote:

	The virtualization option in the BIOS is for HVM (Full
Virtualization).  Seeing as how you had guests before this option was
enabled, you are clearly using PV.  As such, the option would have no effect
that I know of.  That said, your problem probably lies in Xen configuration.
Is this your first Xen box?  Hopefully someone skilled at troubleshooting
network connectivity issues in Xen can assist you with this.
	Dustin

-----Original Message-----
From: xen-users-bounces@lists.xensource.com
[mailto:xen-users-bounces@lists.xensource.com] On Behalf Of s@l
Sent: Monday, July 21, 2008 16:35
To: xen-users@lists.xensource.com
Subject: [Xen-users] Xen Installation without virtualization enabled in Bios

Hi there,

Having a problem with Xen using RHEL 5.  Using a dell poweredge 1950 with
BCM5708 integrated NIC''s. 

07:00.0 Ethernet controller: Broadcom Corporation NetXtreme II BCM5708
Gigabit Ethernet (rev 12)
        Subsystem: Dell Unknown device 01b3
        Control: I/O- Mem+ BusMaster+ SpecCycle+ MemWINV+ VGASnoop- ParErr+
Stepping- SERR+ FastB2B-
        Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium &gt;TAbort-
SERR- 

-- 
Daniel Kao
Übermind, Inc.
Seattle, WA, U.S.A.


_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

Mark Williamson

2008-Jul-21 21:03 UTC

head link

Re: [Xen-users] Xen Installation without virtualization enabled in Bios

On Monday 21 July 2008, Dustin Henning wrote:> 	The virtualization option in the BIOS is for HVM (Full
> Virtualization).  Seeing as how you had guests before this option was
> enabled, you are clearly using PV.  As such, the option would have no
> effect that I know of.  That said, your problem probably lies in Xen
> configuration. Is this your first Xen box?  Hopefully someone skilled at
> troubleshooting network connectivity issues in Xen can assist you with
Incidentally if you wanted to use HVM in future that should work fine also: 
Xen comes with HVM support built in, regardless of whether it was enabled 
when Xen was installed.  To get the best HVM results you should probably use 
the latest update of RHEL.  This shouldn''t effect PV behaviour though,
so
don''t worry about it until you''ve solved the existing
networking problem.

Cheers,
Mark
> 	Dustin
>
> -----Original Message-----
> From: xen-users-bounces@lists.xensource.com
> [mailto:xen-users-bounces@lists.xensource.com] On Behalf Of s@l
> Sent: Monday, July 21, 2008 16:35
> To: xen-users@lists.xensource.com
> Subject: [Xen-users] Xen Installation without virtualization enabled in
> Bios
>
>
> Hi there,
>
> Having a problem with Xen using RHEL 5.  Using a dell poweredge 1950 with
> BCM5708 integrated NIC''s.
>
> 07:00.0 Ethernet controller: Broadcom Corporation NetXtreme II BCM5708
> Gigabit Ethernet (rev 12)
>         Subsystem: Dell Unknown device 01b3
>         Control: I/O- Mem+ BusMaster+ SpecCycle+ MemWINV+ VGASnoop- ParErr+
> Stepping- SERR+ FastB2B-
>         Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort-
> <TAbort- <MAbort- >SERR- <PERR-
>         Latency: 64 (16000ns min), Cache Line Size: 64 bytes
>         Interrupt: pin A routed to IRQ 16
>         Region 0: Memory at f4000000 (64-bit, non-prefetchable) [size=32M]
>         Capabilities: [40] PCI-X non-bridge device
>                 Command: DPERE- ERO- RBC=512 OST=8
>                 Status: Dev=07:00.0 64bit+ 133MHz+ SCD- USC- DC=simple
> DMMRBC=512 DMOST=8 DMCRS=32 RSCEM- 266MHz- 533MHz-
>         Capabilities: [48] Power Management version 2
>                 Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA
> PME(D0-,D1-,D2-,D3hot+,D3cold+)
>                 Status: D0 PME-Enable- DSel=0 DScale=1 PME-
>         Capabilities: [50] Vital Product Data
>         Capabilities: [58] Message Signalled Interrupts: 64bit+ Queue=0/0
> Enable-
>                 Address: 214082b132d03000  Data: 0b40
>
>
>
> Basically, I have this strange issue where everything is good, I can create
> my virtual guests, but there is some issue with network connectivity.  I
> can get to the outside world no problem from the virtual host, but on the
> guests, I can only ping the local machine, I cant ping or access anything
> on the outside world.
>
> At first I was taking a look at drivers and other network related problems,
> when I noticed that the virtualization option in the bios cpu settings was
> NOT enabled.  I enabled it, but im still having the same problem.
>
> My question is: Would installing RHEL 5 and Xen while this option was NOT
> enabled in the bios cause problems and perhaps cause this networking
> connectivity issue im experiencing? Do I need to reinstall xen?
>
> Info:
>
> version: xen-3.0.3-64.el5_2.1


-- 
Push Me Pull You - Distributed SCM tool (http://www.cl.cam.ac.uk/~maw48/pmpu/)

_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

s@l

2008-Jul-22 20:40 UTC

head link

Re: [Xen-users] Xen Installation without virtualization enabled in Bios

Ok so more details regarding the setup and our problem.

in the xend-config.sxp file we are using: (network-script
multi-network-bridge)

The multi-network-bridge script is as follows:

#!/bin/sh
dir=$(dirname "$0")
"$dir/network-bridge" "$@" vifnum=0 netdev=eth0
"$dir/network-bridge" "$@" vifnum=1 netdev=eth1

So Dom0 is in bridging mode.  I can ping my DomU from my Dom0 but I can not
ping my Dom0 from my DomU.  We are using static IPs.  The Dom0 is using Eth1
for connectivity.  On the DomU eth1 is also the interface we are using for
connectivity.  Eth1 on Dom0 and Eth1 on DomU are set to different subnets. 

Other possible useful information:

I can VNC into the Dom0 and then subsequently, from the dom0 VNC into the
DomU.  However, when I Do a /usr/sbin/xm list on the Dom0, the DomU is
listed as in blocked state, not the running state... I understood that the
blocked state was when it was waiting for some kind of input from a keyboard
or a mouse, like during the install of the DomU.  Is this an important
detail?



s@l wrote:> 
> Hi there,
> 
> Having a problem with Xen using RHEL 5.  Using a dell poweredge 1950 with
> BCM5708 integrated NIC''s. 
> 
> 07:00.0 Ethernet controller: Broadcom Corporation NetXtreme II BCM5708
> Gigabit Ethernet (rev 12)
>         Subsystem: Dell Unknown device 01b3
>         Control: I/O- Mem+ BusMaster+ SpecCycle+ MemWINV+ VGASnoop-
> ParErr+ Stepping- SERR+ FastB2B-
>         Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort-
> <TAbort- <MAbort- >SERR- <PERR-
>         Latency: 64 (16000ns min), Cache Line Size: 64 bytes
>         Interrupt: pin A routed to IRQ 16
>         Region 0: Memory at f4000000 (64-bit, non-prefetchable) [size=32M]
>         Capabilities: [40] PCI-X non-bridge device
>                 Command: DPERE- ERO- RBC=512 OST=8
>                 Status: Dev=07:00.0 64bit+ 133MHz+ SCD- USC- DC=simple
> DMMRBC=512 DMOST=8 DMCRS=32 RSCEM- 266MHz- 533MHz-
>         Capabilities: [48] Power Management version 2
>                 Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA
> PME(D0-,D1-,D2-,D3hot+,D3cold+)
>                 Status: D0 PME-Enable- DSel=0 DScale=1 PME-
>         Capabilities: [50] Vital Product Data
>         Capabilities: [58] Message Signalled Interrupts: 64bit+ Queue=0/0
> Enable-
>                 Address: 214082b132d03000  Data: 0b40
> 
> 
> 
> Basically, I have this strange issue where everything is good, I can
> create my virtual guests, but there is some issue with network
> connectivity.  I can get to the outside world no problem from the virtual
> host, but on the guests, I can only ping the local machine, I cant ping or
> access anything on the outside world. 
> 
> At first I was taking a look at drivers and other network related
> problems, when I noticed that the virtualization option in the bios cpu
> settings was NOT enabled.  I enabled it, but im still having the same
> problem.
> 
> My question is: Would installing RHEL 5 and Xen while this option was NOT
> enabled in the bios cause problems and perhaps cause this networking
> connectivity issue im experiencing? Do I need to reinstall xen? 
> 
> Info: 
> 
> version: xen-3.0.3-64.el5_2.1
> 
-- 
View this message in context:
http://www.nabble.com/Xen-Installation-without-virtualization-enabled-in-Bios-tp18532312p18598258.html
Sent from the Xen - User mailing list archive at Nabble.com.


_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

Daniel Kao

2008-Jul-22 20:48 UTC

head link

Re: [Xen-users] Xen Installation without virtualization enabled in Bios

I wouldn''t be worried about the state listed by xm list.  It''s
probably
fine.

"Eth1 on Dom0 and Eth1 on DomU are set to different subnets."

This is the part I''m confused about.  If eth1 is used for dom0 for 
connectivity, and eth1 is bridged between dom0 and domU and domU is 
using eth1, why are they in different subnets?  If they are in different 
subnets (unless both are running down the same physical wire), you 
should be using a routed setup versus a bridged setup.

Cheers,
Daniel

s@l wrote:> Ok so more details regarding the setup and our problem.
>
> in the xend-config.sxp file we are using: (network-script
> multi-network-bridge)
>
> The multi-network-bridge script is as follows:
>
> #!/bin/sh
> dir=$(dirname "$0")
> "$dir/network-bridge" "$@" vifnum=0 netdev=eth0
> "$dir/network-bridge" "$@" vifnum=1 netdev=eth1
>
> So Dom0 is in bridging mode.  I can ping my DomU from my Dom0 but I can not
> ping my Dom0 from my DomU.  We are using static IPs.  The Dom0 is using
Eth1
> for connectivity.  On the DomU eth1 is also the interface we are using for
> connectivity.  Eth1 on Dom0 and Eth1 on DomU are set to different subnets. 
>
> Other possible useful information:
>
> I can VNC into the Dom0 and then subsequently, from the dom0 VNC into the
> DomU.  However, when I Do a /usr/sbin/xm list on the Dom0, the DomU is
> listed as in blocked state, not the running state... I understood that the
> blocked state was when it was waiting for some kind of input from a
keyboard
> or a mouse, like during the install of the DomU.  Is this an important
> detail?
>   
-- 
Daniel Kao
Übermind, Inc.
Seattle, WA, U.S.A.


_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

s@l

2008-Jul-22 21:11 UTC

head link

Re: [Xen-users] Xen Installation without virtualization enabled in Bios

My apologies, 

Dom0 and DomU are both, in fact, on the same subnet.  I forgot Im only using
a 16 bit subnet mask, I noticed the 3rd subnets of the IP for Dom0 and DomU
were different and made this mistake... 


Daniel Kao-2 wrote:> 
> I wouldn''t be worried about the state listed by xm list. 
It''s probably
> fine.
> 
> "Eth1 on Dom0 and Eth1 on DomU are set to different subnets."
> 
> This is the part I''m confused about.  If eth1 is used for dom0 for
> connectivity, and eth1 is bridged between dom0 and domU and domU is 
> using eth1, why are they in different subnets?  If they are in different 
> subnets (unless both are running down the same physical wire), you 
> should be using a routed setup versus a bridged setup.
> 
> Cheers,
> Daniel
> 
> s@l wrote:
>> Ok so more details regarding the setup and our problem.
>>
>> in the xend-config.sxp file we are using: (network-script
>> multi-network-bridge)
>>
>> The multi-network-bridge script is as follows:
>>
>> #!/bin/sh
>> dir=$(dirname "$0")
>> "$dir/network-bridge" "$@" vifnum=0 netdev=eth0
>> "$dir/network-bridge" "$@" vifnum=1 netdev=eth1
>>
>> So Dom0 is in bridging mode.  I can ping my DomU from my Dom0 but I can
>> not
>> ping my Dom0 from my DomU.  We are using static IPs.  The Dom0 is using
>> Eth1
>> for connectivity.  On the DomU eth1 is also the interface we are using
>> for
>> connectivity.  Eth1 on Dom0 and Eth1 on DomU are set to different
>> subnets. 
>>
>> Other possible useful information:
>>
>> I can VNC into the Dom0 and then subsequently, from the dom0 VNC into
the
>> DomU.  However, when I Do a /usr/sbin/xm list on the Dom0, the DomU is
>> listed as in blocked state, not the running state... I understood that
>> the
>> blocked state was when it was waiting for some kind of input from a
>> keyboard
>> or a mouse, like during the install of the DomU.  Is this an important
>> detail?
>>   
> 
> -- 
> Daniel Kao
> Übermind, Inc.
> Seattle, WA, U.S.A.
> 
> 
> _______________________________________________
> Xen-users mailing list
> Xen-users@lists.xensource.com
> http://lists.xensource.com/xen-users
> 
> 
-- 
View this message in context:
http://www.nabble.com/Xen-Installation-without-virtualization-enabled-in-Bios-tp18532312p18598880.html
Sent from the Xen - User mailing list archive at Nabble.com.


_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

Daniel Kao

2008-Jul-22 21:35 UTC

head link

Re: [Xen-users] Xen Installation without virtualization enabled in Bios

Did this resolve your domU''s connectivity?  So the 3rd octect in the 
domU was incorrect?  That would explain pings working from one end and a 
gateway that''s outside of your subnet range which prevents outside 
connectivity... or something similar...

Cheers,
Daniel

s@l wrote:> My apologies, 
>
> Dom0 and DomU are both, in fact, on the same subnet.  I forgot Im only
using
> a 16 bit subnet mask, I noticed the 3rd subnets of the IP for Dom0 and DomU
> were different and made this mistake... 
>
>
> Daniel Kao-2 wrote:
>   
>> I wouldn''t be worried about the state listed by xm list. 
It''s probably
>> fine.
>>
>> "Eth1 on Dom0 and Eth1 on DomU are set to different subnets."
>>
>> This is the part I''m confused about.  If eth1 is used for dom0
for
>> connectivity, and eth1 is bridged between dom0 and domU and domU is 
>> using eth1, why are they in different subnets?  If they are in
different
>> subnets (unless both are running down the same physical wire), you 
>> should be using a routed setup versus a bridged setup.
>>
>> Cheers,
>> Daniel
>>     
-- 
Daniel Kao
Übermind, Inc.
Seattle, WA, U.S.A.


_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

s@l

2008-Jul-23 18:12 UTC

head link

Re: [Xen-users] Xen Installation without virtualization enabled in Bios

No there was no mistake in the IP addresses... My earlier reports of the DomU
and Dom0 being on different subnets was incorrect, they are on the same
subnet.  I still have the same problem.  I am unable to ping the Dom0 from
the DomU.  I get "Destination Host Unreachable"... 

Daniel Kao-2 wrote:> 
> Did this resolve your domU''s connectivity?  So the 3rd octect in
the
> domU was incorrect?  That would explain pings working from one end and a 
> gateway that''s outside of your subnet range which prevents outside
> connectivity... or something similar...
> 
> Cheers,
> Daniel
> 
> s@l wrote:
>> My apologies, 
>>
>> Dom0 and DomU are both, in fact, on the same subnet.  I forgot Im only
>> using
>> a 16 bit subnet mask, I noticed the 3rd subnets of the IP for Dom0 and
>> DomU
>> were different and made this mistake... 
>>
>>
>> Daniel Kao-2 wrote:
>>   
>>> I wouldn''t be worried about the state listed by xm list. 
It''s probably
>>> fine.
>>>
>>> "Eth1 on Dom0 and Eth1 on DomU are set to different
subnets."
>>>
>>> This is the part I''m confused about.  If eth1 is used for
dom0 for
>>> connectivity, and eth1 is bridged between dom0 and domU and domU is
>>> using eth1, why are they in different subnets?  If they are in
different
>>> subnets (unless both are running down the same physical wire), you 
>>> should be using a routed setup versus a bridged setup.
>>>
>>> Cheers,
>>> Daniel
>>>     
> 
> -- 
> Daniel Kao
> Übermind, Inc.
> Seattle, WA, U.S.A.
> 
> 
> _______________________________________________
> Xen-users mailing list
> Xen-users@lists.xensource.com
> http://lists.xensource.com/xen-users
> 
> 
-- 
View this message in context:
http://www.nabble.com/Xen-Installation-without-virtualization-enabled-in-Bios-tp18532312p18617087.html
Sent from the Xen - User mailing list archive at Nabble.com.


_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

Steve Hayward

2008-Jul-30 15:10 UTC

head link

RE: [Xen-users] Xen Installation without virtualization enabled in Bios

I had a similar issue with one of my Centos 5.1 servers, which was fixed by
running the command:

ethtool -K eth0 tx off

I added this to my rc.local file of each DomU.

Hope it works for you.

Steve



________________________________________
From: xen-users-bounces@lists.xensource.com
[xen-users-bounces@lists.xensource.com] On Behalf Of s@l
[sal.bayat@impactmobile.com]
Sent: Friday, July 18, 2008 3:50 PM
To: xen-users@lists.xensource.com
Subject: [Xen-users] Xen Installation without virtualization enabled in Bios

Hi there,

Having a problem with Xen using RHEL 5.  Using a dell poweredge 1950 with
BCM5708 integrated NIC''s.

07:00.0 Ethernet controller: Broadcom Corporation NetXtreme II BCM5708
Gigabit Ethernet (rev 12)
        Subsystem: Dell Unknown device 01b3
        Control: I/O- Mem+ BusMaster+ SpecCycle+ MemWINV+ VGASnoop- ParErr+
Stepping- SERR+ FastB2B-
        Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort-
<TAbort- <MAbort- >SERR- <PERR-
        Latency: 64 (16000ns min), Cache Line Size: 64 bytes
        Interrupt: pin A routed to IRQ 16
        Region 0: Memory at f4000000 (64-bit, non-prefetchable) [size=32M]
        Capabilities: [40] PCI-X non-bridge device
                Command: DPERE- ERO- RBC=512 OST=8
                Status: Dev=07:00.0 64bit+ 133MHz+ SCD- USC- DC=simple
DMMRBC=512 DMOST=8 DMCRS=32 RSCEM- 266MHz- 533MHz-
        Capabilities: [48] Power Management version 2
                Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA
PME(D0-,D1-,D2-,D3hot+,D3cold+)
                Status: D0 PME-Enable- DSel=0 DScale=1 PME-
        Capabilities: [50] Vital Product Data
        Capabilities: [58] Message Signalled Interrupts: 64bit+ Queue=0/0
Enable-
                Address: 214082b132d03000  Data: 0b40



Basically, I have this strange issue where everything is good, I can create
my virtual guests, but there is some issue with network connectivity.  I can
get to the outside world no problem from the virtual host, but on the
guests, I can only ping the local machine, I cant ping or access anything on
the outside world.

At first I was taking a look at drivers and other network related problems,
when I noticed that the virtualization option in the bios cpu settings was
NOT enabled.  I enabled it, but im still having the same problem.

My question is: Would installing RHEL 5 and Xen while this option was NOT
enabled in the bios cause problems and perhaps cause this networking
connectivity issue im experiencing? Do I need to reinstall xen?

Info:

version: xen-3.0.3-64.el5_2.1
--
View this message in context:
http://www.nabble.com/Xen-Installation-without-virtualization-enabled-in-Bios-tp18532312p18532312.html
Sent from the Xen - User mailing list archive at Nabble.com.


_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

s@l

2008-Jul-30 15:51 UTC

head link

RE: [Xen-users] Xen Installation without virtualization enabled in Bios

Thanks, I ran the command, now I can ping the Dom0 but I still cant ping
anything beyond that from the DomU, can''t ping anything else beyond the
machine itself, get destination host unreachable... still..

Steve Hayward-2 wrote:> 
> I had a similar issue with one of my Centos 5.1 servers, which was fixed
> by running the command:
> 
> ethtool -K eth0 tx off
> 
> I added this to my rc.local file of each DomU.
> 
> Hope it works for you.
> 
> Steve
> 
> 
> 
> ________________________________________
> From: xen-users-bounces@lists.xensource.com
> [xen-users-bounces@lists.xensource.com] On Behalf Of s@l
> [sal.bayat@impactmobile.com]
> Sent: Friday, July 18, 2008 3:50 PM
> To: xen-users@lists.xensource.com
> Subject: [Xen-users] Xen Installation without virtualization enabled in
> Bios
> 
> Hi there,
> 
> Having a problem with Xen using RHEL 5.  Using a dell poweredge 1950 with
> BCM5708 integrated NIC''s.
> 
> 07:00.0 Ethernet controller: Broadcom Corporation NetXtreme II BCM5708
> Gigabit Ethernet (rev 12)
>         Subsystem: Dell Unknown device 01b3
>         Control: I/O- Mem+ BusMaster+ SpecCycle+ MemWINV+ VGASnoop-
> ParErr+
> Stepping- SERR+ FastB2B-
>         Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort-
> <TAbort- <MAbort- >SERR- <PERR-
>         Latency: 64 (16000ns min), Cache Line Size: 64 bytes
>         Interrupt: pin A routed to IRQ 16
>         Region 0: Memory at f4000000 (64-bit, non-prefetchable) [size=32M]
>         Capabilities: [40] PCI-X non-bridge device
>                 Command: DPERE- ERO- RBC=512 OST=8
>                 Status: Dev=07:00.0 64bit+ 133MHz+ SCD- USC- DC=simple
> DMMRBC=512 DMOST=8 DMCRS=32 RSCEM- 266MHz- 533MHz-
>         Capabilities: [48] Power Management version 2
>                 Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA
> PME(D0-,D1-,D2-,D3hot+,D3cold+)
>                 Status: D0 PME-Enable- DSel=0 DScale=1 PME-
>         Capabilities: [50] Vital Product Data
>         Capabilities: [58] Message Signalled Interrupts: 64bit+ Queue=0/0
> Enable-
>                 Address: 214082b132d03000  Data: 0b40
> 
> 
> 
> Basically, I have this strange issue where everything is good, I can
> create
> my virtual guests, but there is some issue with network connectivity.  I
> can
> get to the outside world no problem from the virtual host, but on the
> guests, I can only ping the local machine, I cant ping or access anything
> on
> the outside world.
> 
> At first I was taking a look at drivers and other network related
> problems,
> when I noticed that the virtualization option in the bios cpu settings was
> NOT enabled.  I enabled it, but im still having the same problem.
> 
> My question is: Would installing RHEL 5 and Xen while this option was NOT
> enabled in the bios cause problems and perhaps cause this networking
> connectivity issue im experiencing? Do I need to reinstall xen?
> 
> Info:
> 
> version: xen-3.0.3-64.el5_2.1
> --
> View this message in context:
>
http://www.nabble.com/Xen-Installation-without-virtualization-enabled-in-Bios-tp18532312p18532312.html
> Sent from the Xen - User mailing list archive at Nabble.com.
> 
> 
> _______________________________________________
> Xen-users mailing list
> Xen-users@lists.xensource.com
> http://lists.xensource.com/xen-users
> 
> _______________________________________________
> Xen-users mailing list
> Xen-users@lists.xensource.com
> http://lists.xensource.com/xen-users
> 
> 
-- 
View this message in context:
http://www.nabble.com/Xen-Installation-without-virtualization-enabled-in-Bios-tp18532312p18736491.html
Sent from the Xen - User mailing list archive at Nabble.com.


_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

Brian Stempin

2008-Jul-30 16:17 UTC

head link

Re: [Xen-users] Xen Installation without virtualization enabled in Bios

Would you be kind enough to post the network section of one of your DomU
config files?  This might help with the diagnosis.

_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

s@l

2008-Jul-30 17:34 UTC

head link

Re: [Xen-users] Xen Installation without virtualization enabled in Bios

Absolutely:

name = "rogers1"
uuid = "cba597ed-b11d-7023-5394-99c528f144aa"
maxmem = 2048
memory = 2048
vcpus = 2
bootloader = "/usr/bin/pygrub"
on_poweroff = "destroy"
on_reboot = "restart"
on_crash = "restart"
vfb = [ "type=vnc,vncunused=1" ]
disk = [ "tap:aio:/var/lib/xen/images/rogers1.img,xvda,w" ]
vif = [ "mac=00:16:3e:6d:b4:b9,bridge=xenbr1",
"mac=00:16:3e:65:2c:92,bridge=xenbr0" ]


Brian Stempin wrote:> 
> Would you be kind enough to post the network section of one of your DomU
> config files?  This might help with the diagnosis.
> 
> _______________________________________________
> Xen-users mailing list
> Xen-users@lists.xensource.com
> http://lists.xensource.com/xen-users
> 
> 
-- 
View this message in context:
http://www.nabble.com/Xen-Installation-without-virtualization-enabled-in-Bios-tp18532312p18738593.html
Sent from the Xen - User mailing list archive at Nabble.com.


_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

Brian Stempin

2008-Jul-30 17:50 UTC

head link

Re: [Xen-users] Xen Installation without virtualization enabled in Bios

I just re-read your email.

To answer your most important question:
> Would installing RHEL 5 and Xen while this option was NOT
> enabled in the bios cause problems and perhaps cause this networking
> connectivity issue im experiencing? Do I need to reinstall xen? 
The answer to this is "no".  Enabling/disabling virtualization in the
BIOS, to the best of my knowledge, merely toggles the processor''s VT
flag, which only affects the ability to run fully virtualized VMs (such
as Windows).  According to your config file, you''re using pygrub, which
indicates that the DomU in question is a paravirtualized VM, and thus
not effected by the enabling/disabling of this feature.

You most likely have a legit networking issue.  A few questions to
further diagnose:
1.  Are you using any bonding?  If so, could you post details?
2.  Have you modified the stock bridge in any way?  If so, how?
3.  Have you edited any of the Xen networking scripts?  If so, could you
post your mods?

_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

s@l

2008-Jul-30 17:58 UTC

head link

Re: [Xen-users] Xen Installation without virtualization enabled in Bios

I changed the xen-config.sxp..

"
# -*- sh -*-

#
# Xend configuration file.
#

# This example configuration is appropriate for an installation that
# utilizes a bridged network configuration. Access to xend via http
# is disabled.

# Commented out entries show the default for that entry, unless otherwise
# specified.

#(logfile /var/log/xen/xend.log)
#(loglevel DEBUG)

#(xend-http-server no)
(xend-unix-server yes)
#(xend-tcp-xmlrpc-server no)
#(xend-unix-xmlrpc-server yes)
#(xend-relocation-server no)
# The relocation server should be kept desactivated unless using a trusted
# network, the domain virtual memory will be exchanged in raw form without
# encryption of the communication. See also xend-relocation-hosts-allow
option

(xend-unix-path /var/lib/xend/xend-socket)

# Port xend should use for the HTTP interface, if xend-http-server is set.
#(xend-port            8000)

# Port xend should use for the relocation interface, if
xend-relocation-server
# is set.
#(xend-relocation-port 8002)

# Address xend should listen on for HTTP connections, if xend-http-server is
# set.
# Specifying ''localhost'' prevents remote connections.
# Specifying the empty string '''' (the default) allows all
connections.
#(xend-address '''')
#(xend-address localhost)

# Address xend should listen on for relocation-socket connections, if
# xend-relocation-server is set.
# Meaning and default as for xend-address above.
#(xend-relocation-address '''')

# The hosts allowed to talk to the relocation port.  If this is empty (the
# default), then all connections are allowed (assuming that the connection
# arrives on a port and interface on which we are listening; see
# xend-relocation-port and xend-relocation-address above).  Otherwise, this
# should be a space-separated sequence of regular expressions.  Any host
with
# a fully-qualified domain name or an IP address that matches one of these
# regular expressions will be accepted.
#
# For example:
#  (xend-relocation-hosts-allow ''^localhost$
^.*\.example\.org$'')
#
#(xend-relocation-hosts-allow '''')
(xend-relocation-hosts-allow ''^localhost$
^localhost\\.localdomain$'')

# The limit (in kilobytes) on the size of the console buffer
#(console-limit 1024)

##
# To bridge network traffic, like this:
#
# dom0: fake eth0 -> vif0.0 -+
#                            |
#                          bridge -> real eth0 -> the network
#                            |
# domU: fake eth0 -> vifN.0 -+
#
# use
#
# (network-script network-bridge)
#
# Your default ethernet device is used as the outgoing interface, by
default.
# To use a different one (e.g. eth1) use
#
# (network-script ''network-bridge netdev=eth1'')
#
# The bridge is named xenbr0, by default.  To rename the bridge, use
#
# (network-script ''network-bridge bridge=<name>'')
#
# It is possible to use the network-bridge script in more complicated
# scenarios, such as having two outgoing interfaces, with two bridges, and
# two fake interfaces per guest domain.  To do things like this, write
# yourself a wrapper script, and call network-bridge from it, as
appropriate.
#
(network-script multi-network-bridge)

# The script used to control virtual interfaces.  This can be overridden on
a
# per-vif basis when creating a domain or a configuring a new vif.  The
# vif-bridge script is designed for use with the network-bridge script, or
# similar configurations.
#
# If you have overridden the bridge name using
# (network-script ''network-bridge bridge=<name>'') then
you may wish to do
the
# same here.  The bridge name can also be set when creating a domain or
# configuring a new vif, but a value specified here would act as a default.
#
# If you are using only one bridge, the vif-bridge script will discover
that,
# so there is no need to specify it explicitly.
#
(vif-script vif-bridge)

## Use the following if network traffic is routed, as an alternative to the
# settings for bridged networking given above.
#(network-script network-route)
#(vif-script     vif-route)

## Use the following if network traffic is routed with NAT, as an
alternative
# to the settings for bridged networking given above.
#(network-script network-nat)
#(vif-script     vif-nat)

# Dom0 will balloon out when needed to free memory for domU.
# dom0-min-mem is the lowest memory level (in MB) dom0 will get down to.
# If dom0-min-mem=0, dom0 will never balloon out.
(dom0-min-mem 256)

# In SMP system, dom0 will use dom0-cpus # of CPUS
# If dom0-cpus = 0, dom0 will take all cpus available
(dom0-cpus 0)

# Whether to enable core-dumps when domains crash.
#(enable-dump no)

# The tool used for initiating virtual TPM migration
#(external-migration-tool '''')

# The interface for VNC servers to listen on. Defaults
# to 127.0.0.1  To restore old ''listen everywhere'' behaviour
# set this to 0.0.0.0
#(vnc-listen ''127.0.0.1'')

# The default password for VNC console on HVM domain.
# Empty string is no authentication.
(vncpasswd '''')
"

Note the (network-script multi-network-bridge)

the script multi-network-bridge is as follows:

"
#!/bin/sh
dir=$(dirname "$0")
"$dir/network-bridge" "$@" vifnum=0 netdev=eth0
"$dir/network-bridge" "$@" vifnum=1 netdev=eth1
"

Brian Stempin wrote:> 
> I just re-read your email.
> 
> To answer your most important question:
> 
>> Would installing RHEL 5 and Xen while this option was NOT
>> enabled in the bios cause problems and perhaps cause this networking
>> connectivity issue im experiencing? Do I need to reinstall xen? 
> 
> The answer to this is "no".  Enabling/disabling virtualization in
the
> BIOS, to the best of my knowledge, merely toggles the processor''s
VT
> flag, which only affects the ability to run fully virtualized VMs (such
> as Windows).  According to your config file, you''re using pygrub,
which
> indicates that the DomU in question is a paravirtualized VM, and thus
> not effected by the enabling/disabling of this feature.
> 
> You most likely have a legit networking issue.  A few questions to
> further diagnose:
> 1.  Are you using any bonding?  If so, could you post details?
> 2.  Have you modified the stock bridge in any way?  If so, how?
> 3.  Have you edited any of the Xen networking scripts?  If so, could you
> post your mods?
> 
> _______________________________________________
> Xen-users mailing list
> Xen-users@lists.xensource.com
> http://lists.xensource.com/xen-users
> 
> 
-- 
View this message in context:
http://www.nabble.com/Xen-Installation-without-virtualization-enabled-in-Bios-tp18532312p18739100.html
Sent from the Xen - User mailing list archive at Nabble.com.

_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

Brian Stempin

2008-Jul-30 18:32 UTC

head link

Re: [Xen-users] Xen Installation without virtualization enabled in Bios

Two things come to mind:

1.  I''m not sure that the script you wrote will work correctly as-is. 
Perhaps someone else would like to chime in on this, since my bash
skills aren''t great, but here''s the usage info from the
default
network-bridge script:

|# Usage:
#
# network-bridge (start|stop|status) {VAR=VAL}*
#
# Vars:
#
# bridge     The bridge to use (default ${netdev}).
# netdev     The interface to add to the bridge (default gateway device).
# antispoof  Whether to use iptables to prevent spoofing (default no).
#
# Internal Vars:
# pdev="p${netdev}"
# tdev=tmpbridge
#
# start:
# Creates the bridge as tdev
# Copies the IP and MAC addresses from pdev to bridge
# Renames netdev to be pdev
# Renames tdev to bridge
# Enslaves pdev to bridge
#
# stop:

# Removes pdev from the bridge
# Transfers addresses, routes from bridge to pdev
# Renames bridge to tdev
# Renames pdev to netdev
# Deletes tdev
#
# status:
# Print addresses, interfaces, routes|

Based on the description above, I don''t think that you''re
passing the
correct variables to the script.

2.  You mentioned that the DomU was able to ping the Dom0, but not the
outside world.  You might want to check a few basic network things, such as:

    * running |brctl show |to make sure that the bridges are being
      created correctly.
    * running |route| from within the DomU to make sure that it''s
      gateway and subnet are set up correctly.

HTH


_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

Age_M

2008-Jul-30 18:58 UTC

head link

Re: [Xen-users] Xen Installation without virtualization enabled in Bios

Hi s@l,

another way to turn off tx-checksumming is to add a line in 
/etc/xen/scripts/xen-network-common.sh
Just add a line to the add_to_bridge function (you find it at the end of 
the file):

original script:
[...]
add_to_bridge () {
    local bridge=$1
    local dev=$2

    # Don''t add $dev to $bridge if it''s already on a bridge.
    if [ -e "/sys/class/net/${bridge}/brif/${dev}" ]; then
        ip link set ${dev} up || true
        return
    fi
    brctl addif ${bridge} ${dev}
    ip link set ${dev} up
}

modified script (check the last line):
[...]
add_to_bridge () {
    local bridge=$1
    local dev=$2

    # Don''t add $dev to $bridge if it''s already on a bridge.
    if [ -e "/sys/class/net/${bridge}/brif/${dev}" ]; then
        ip link set ${dev} up || true
        return
    fi
    brctl addif ${bridge} ${dev}
    ip link set ${dev} up
    ethtool -K ${dev} tx off
}

This works for me and all domUs that are created :-D
Greetz Age_M

_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

Birger Brunswiek

2008-Jul-30 22:25 UTC

head link

Re: [Xen-users] Xen Installation without virtualization enabled in Bios

s@l wrote:
[...]
> Note the (network-script multi-network-bridge)
> 
> the script multi-network-bridge is as follows:
> 
> "
> #!/bin/sh
> dir=$(dirname "$0")
> "$dir/network-bridge" "$@" vifnum=0 netdev=eth0
> "$dir/network-bridge" "$@" vifnum=1 netdev=eth1
> "
I think I made pretty much the same customization as you did to the bridge 
script. Mine looks like this and works for me:

#!/bin/bash
DEVICES="eth0 eth1"
for DEV in $DEVICES; do
   /etc/xen/scripts/network-bridge $@ netdev=$DEV
   if [ "$1" = "start" ]; then
     ip link set $DEV up
   fi
done




_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

Xen users - Jul 2008 - Xen Installation without virtualization enabled in Bios

[Xen-users] Xen Installation without virtualization enabled in Bios

RE: [Xen-users] Xen Installation without virtualization enabled in Bios

Re: [Xen-users] Xen Installation without virtualization enabled in Bios

Re: [Xen-users] Xen Installation without virtualization enabled in Bios

Re: [Xen-users] Xen Installation without virtualization enabled in Bios

Re: [Xen-users] Xen Installation without virtualization enabled in Bios

Re: [Xen-users] Xen Installation without virtualization enabled in Bios

Re: [Xen-users] Xen Installation without virtualization enabled in Bios

Re: [Xen-users] Xen Installation without virtualization enabled in Bios

RE: [Xen-users] Xen Installation without virtualization enabled in Bios

RE: [Xen-users] Xen Installation without virtualization enabled in Bios

Re: [Xen-users] Xen Installation without virtualization enabled in Bios

Re: [Xen-users] Xen Installation without virtualization enabled in Bios

Re: [Xen-users] Xen Installation without virtualization enabled in Bios

Re: [Xen-users] Xen Installation without virtualization enabled in Bios

Re: [Xen-users] Xen Installation without virtualization enabled in Bios

Re: [Xen-users] Xen Installation without virtualization enabled in Bios

Re: [Xen-users] Xen Installation without virtualization enabled in Bios