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

["s@l" <sal.bayat@xxxxxxxxxxxxxxxx>]

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@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users