Sponsored Content
Full Discussion: XEN and SLES11
Operating Systems Linux SuSE XEN and SLES11 Post 302487883 by hiddenshadow on Friday 14th of January 2011 02:52:45 AM
Old 01-14-2011
XEN and SLES11

Good morning,

Server:HP ProLiant DL165 G7 diskless with Disc on Storage
OS:SLES11 SP1 and xen-3.3.1_18546_12-3.1
iSCSI:INTEL Gigabit ET Dual Port Server Adapter 825768

When I start SLES11 with Xen in boot-loader menu, then the boot will stop because linux could'nt find the iscsi interface :
Code:
Starting iSCSI daemon
iscsiadm: No records found!
Trying manual resume from /dev/disk/by-id/scsi-360060...

It's really strange because when I start SLES11 in normal mode (default) then all are ok and here're the result of commands:
Code:
# iscsiadm -m session -P 1
Target: iqn.1994-04.jp.com
    Current Portal: 192.168.192.160:3260,1
    Persistent Portal: 192.168.192.160:3260,1
        **********
        Interface:
        **********
        Iface Name: default
        Iface Transport: tcp
        Iface Initiatorname: iqn.2011.xen1
        Iface IPaddress: 192.168.192.166
        Iface HWaddress: default
        Iface Netdev: default
        SID: 1
        iSCSI Connection State: LOGGED IN
        iSCSI Session State: LOGGED_IN
        Internal iscsid Session State: NO CHANGE

lsscsi
[6:0:0:0]    cd/dvd  TEAC     DV-18S-A         B.0C  /dev/sr0
[8:0:0:0]    disk    HITACHI  DF600F           0000  /dev/sda
[8:0:0:1]    disk    HITACHI  DF600F           0000  /dev/sdb
[8:0:0:2]    disk    HITACHI  DF600F           0000  /dev/sdc
[8:0:0:3]    disk    HITACHI  DF600F           0000  /dev/sdd
[8:0:0:4]    disk    HITACHI  DF600F           0000  /dev/sde

...and the boot loader :
Code:
# cat /boot/grub/menu.lst
###Don't change this comment - YaST2 identifier: Original name: linux###
title SUSE Linux Enterprise Server 11 - 2.6.27.19-5 (default)
    root (hd0,0)
    kernel /vmlinuz-2.6.27.19-5-default root=/dev/disk/by-id/scsi-360060e80104d32a004f3423200
000001-part3 apic=bigsmp resume=/dev/disk/by-id/scsi-360060e80104d32a004f3423200000001-part2 
splash=silent crashkernel=256M-:128M@16M showopts vga=0x31d
    initrd /initrd-2.6.27.19-5-default

###Don't change this comment - YaST2 identifier: Original name: xen###
title Xen -- SUSE Linux Enterprise Server 11 - 2.6.27.19-5
    root (hd0,0)
    kernel /xen.gz 
    module /vmlinuz-2.6.27.19-5-xen root=/dev/disk/by-id/scsi-360060e80104d32a004f34232000000
01-part3 apic=bigsmp resume=/dev/disk/by-id/scsi-360060e80104d32a004f3423200000001-part2 spla
sh=silent showopts vga=0x31d
    module /initrd-2.6.27.19-5-xen

Are a specials config's files for XEN or where could I find my problem?

Have someone an Idea?

Thanks
nm

Last edited by hiddenshadow; 01-14-2011 at 04:58 AM..
 

9 More Discussions You Might Find Interesting

1. Virtualization and Cloud Computing

Opensolaris and Xen

Quick question- When installing a VM with xen on Opensolaris to get paravirtualizion you need an install tree and I can't seem to use an .iso. What what is exactly an intsall tree in this contex? (0 Replies)
Discussion started by: Lespaul20
0 Replies

2. UNIX for Advanced & Expert Users

xen

was looking for some help /tutorials on xen ..im a beginner on virtualisation ..so any help would be greatly appreciated ...p.s. whats the basic difference between para and full virtualisation (2 Replies)
Discussion started by: tarunicon
2 Replies

3. SuSE

SLES11 - RAID6 all disks marked as Spare

Hello, After a replacement of the motherboard of my server, all disks belonging to a raid6 are now marked as spare. Is there any way to mark those disks as active and restore the raid6? $ cat /proc/mdstat Personalities : md1 : inactive sda1(S) sdk1(S) sdj1(S) sdi1(S) sdh1(S)... (0 Replies)
Discussion started by: xavix
0 Replies

4. UNIX and Linux Applications

OpenQRM-4.6 with XEN

has anyone deployed openQRM-4.6 with XEN... On the site they don't have good documention for XEN.. I am testing it for last 2 month but still no luck with XEN. Please help me with this. :mad: Thanks Prashant (0 Replies)
Discussion started by: prashant_ohol
0 Replies

5. Red Hat

XEN on RHEL 6

Hi guys. I read that RHEL will not support XEN in version 6 and it will support KVM. Does this mean we can't install XEN from RHEL repositories? Should we install it from source code? (8 Replies)
Discussion started by: majid.merkava
8 Replies

6. Red Hat

xen lvm

how can i mount lvm on another disk (like xvdc)to dom0? (0 Replies)
Discussion started by: daxian
0 Replies

7. Linux

Apache2-mpm-itk installation SLES11

Hi, do anyone know how to apply the corresponding apache2-mpm-itk patches to an already installed apache2 on a SLES11 machine? This is the link to the module: apache2-mpm-itk And this is the link to the patches: Index of /apache2.2-mpm-itk-2.2.17-01 Thanks (0 Replies)
Discussion started by: asanchez
0 Replies

8. Red Hat

Help using XEN in CentOS 5.9

Hey guys, I've been straddling with this issue for quite some time now and I'm getting absolutely nowhere with it. It took me a long time to get XEN up and running on my server. We only use SSH to manipulate our servers, but we finally got it up and running. Now I'm at the point of actually... (1 Reply)
Discussion started by: mccabec123
1 Replies

9. SuSE

Network issue in SLES11.2

I had installed suse linux 11.2 . I had some strange problem with my network , after configuring it showing some error like tulip_stop_rxtx() failed . The server is not reachable from outside. Could some one help me with it. (1 Reply)
Discussion started by: nanduri
1 Replies
EM(4)							   BSD Kernel Interfaces Manual 						     EM(4)

NAME
em -- Intel(R) PRO/1000 Gigabit Ethernet adapter driver SYNOPSIS
To compile this driver into the kernel, place the following line in your kernel configuration file: device em Alternatively, to load the driver as a module at boot time, place the following line in loader.conf(5): if_em_load="YES" DESCRIPTION
The em driver provides support for PCI Gigabit Ethernet adapters based on the Intel 82540, 82541ER, 82541PI, 82542, 82543, 82544, 82545, 82546, 82546EB, 82546GB, 82547, 82571, 81572, 82573, and 82574 Ethernet controller chips. The driver supports Transmit/Receive checksum off- load and Jumbo Frames on all but 82542-based adapters. Furthermore it supports TCP segmentation offload (TSO) on all adapters but those based on the 82543, 82544 and 82547 controller chips. The identification LEDs of the adapters supported by the em driver can be controlled via the led(4) API for localization purposes. For further hardware information, see the README included with the driver. For questions related to hardware requirements, refer to the documentation supplied with your Intel PRO/1000 adapter. All hardware require- ments listed apply to use with FreeBSD. Support for Jumbo Frames is provided via the interface MTU setting. Selecting an MTU larger than 1500 bytes with the ifconfig(8) utility configures the adapter to receive and transmit Jumbo Frames. The maximum MTU size for Jumbo Frames is 16114. This driver version supports VLANs. The em driver supports the following media types: autoselect Enables auto-negotiation for speed and duplex. 10baseT/UTP Sets 10Mbps operation. Use the mediaopt option to select full-duplex mode. 100baseTX Sets 100Mbps operation. Use the mediaopt option to select full-duplex mode. 1000baseSX Sets 1000Mbps operation. Only full-duplex mode is supported at this speed. 1000baseTX Sets 1000Mbps operation. Only full-duplex mode is supported at this speed. The em driver supports the following media options: full-duplex Forces full-duplex operation half-duplex Forces half-duplex operation. Only use mediaopt to set the driver to full-duplex. If mediaopt is not specified, the driver defaults to half-duplex. For more information on configuring this device, see ifconfig(8). HARDWARE
The em driver supports Gigabit Ethernet adapters based on the Intel 82540, 82541ER, 82541PI, 82542, 82543, 82544, 82545, 82546, 82546EB, 82546GB, 82547, 82571, 82572, 82573, and 82574 controller chips: o Intel PRO/1000 CT Network Connection (82547) o Intel PRO/1000 F Server Adapter (82543) o Intel PRO/1000 Gigabit Server Adapter (82542) o Intel PRO/1000 GT Desktop Adapter (82541PI) o Intel PRO/1000 MF Dual Port Server Adapter (82546) o Intel PRO/1000 MF Server Adapter (82545) o Intel PRO/1000 MF Server Adapter (LX) (82545) o Intel PRO/1000 MT Desktop Adapter (82540) o Intel PRO/1000 MT Desktop Adapter (82541) o Intel PRO/1000 MT Dual Port Server Adapter (82546) o Intel PRO/1000 MT Quad Port Server Adapter (82546EB) o Intel PRO/1000 MT Server Adapter (82545) o Intel PRO/1000 PF Dual Port Server Adapter (82571) o Intel PRO/1000 PF Quad Port Server Adapter (82571) o Intel PRO/1000 PF Server Adapter (82572) o Intel PRO/1000 PT Desktop Adapter (82572) o Intel PRO/1000 PT Dual Port Server Adapter (82571) o Intel PRO/1000 PT Quad Port Server Adapter (82571) o Intel PRO/1000 PT Server Adapter (82572) o Intel PRO/1000 T Desktop Adapter (82544) o Intel PRO/1000 T Server Adapter (82543) o Intel PRO/1000 XF Server Adapter (82544) o Intel PRO/1000 XT Server Adapter (82544) LOADER TUNABLES
Tunables can be set at the loader(8) prompt before booting the kernel or stored in loader.conf(5). hw.em.rxd Number of receive descriptors allocated by the driver. The default value is 256. The 82542 and 82543-based adapters can handle up to 256 descriptors, while others can have up to 4096. hw.em.txd Number of transmit descriptors allocated by the driver. The default value is 256. The 82542 and 82543-based adapters can handle up to 256 descriptors, while others can have up to 4096. hw.em.rx_int_delay This value delays the generation of receive interrupts in units of 1.024 microseconds. The default value is 0, since adapters may hang with this feature being enabled. hw.em.rx_abs_int_delay If hw.em.rx_int_delay is non-zero, this tunable limits the maximum delay in which a receive interrupt is generated. hw.em.tx_int_delay This value delays the generation of transmit interrupts in units of 1.024 microseconds. The default value is 64. hw.em.tx_abs_int_delay If hw.em.tx_int_delay is non-zero, this tunable limits the maximum delay in which a transmit interrupt is generated. DIAGNOSTICS
em%d: Unable to allocate bus resource: memory A fatal initialization error has occurred. em%d: Unable to allocate bus resource: interrupt A fatal initialization error has occurred. em%d: watchdog timeout -- resetting The device has stopped responding to the network, or there is a problem with the network connection (cable). SUPPORT
For general information and support, go to the Intel support website at: http://support.intel.com. If an issue is identified with the released source code on the supported kernel with a supported adapter, email the specific information related to the issue to <freebsdnic@mailbox.intel.com>. FILES
/dev/led/em* identification LED device nodes EXAMPLES
Make the identification LED of em0 blink: echo f2 > /dev/led/em0 Turn the identification LED of em0 off again: echo 0 > /dev/led/em0 SEE ALSO
altq(4), arp(4), igb(4), led(4), netintro(4), ng_ether(4), polling(4), vlan(4), ifconfig(8) HISTORY
The em device driver first appeared in FreeBSD 4.4. AUTHORS
The em driver was written by Intel Corporation <freebsdnic@mailbox.intel.com>. BUGS
Hardware-assisted VLAN processing is disabled by default. You can enable it on an em interface using ifconfig(8). BSD
May 14, 2010 BSD
All times are GMT -4. The time now is 06:25 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy