Bug 613626 - network fails on KVM domU and iSCSI root is not mounted
network fails on KVM domU and iSCSI root is not mounted
Status: CLOSED WONTFIX
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: mkinitrd (Show other bugs)
5.5
All Linux
low Severity medium
: rc
: ---
Assigned To: Brian Lane
Release Test Team
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2010-07-12 09:06 EDT by Alexander Todorov
Modified: 2011-08-23 14:25 EDT (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2011-08-23 14:25:29 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Alexander Todorov 2010-07-12 09:06:59 EDT
Description of problem:
A KVM domU fails to bring up networking and the result is that the rootfs which is on iSCSI can't be mounted.

Version-Release number of selected component (if applicable):
mkinitrd-5.1.19.6-61

How reproducible:
Always 

Steps to Reproduce:
1. On a RHEL6 KVM host start installation of RHEL 5.5 GA guest
2. Leave default settings: guest is using virtio for disk and network, network is using the bridge br0.
3. Use a local disk (for /boot) and an iSCSI disk for the guest system. The iSCSI disk is hosted on the host as well. 
4. Complete the install (use default partitioning - LVM) and reboot.
  
Actual results:
Anaconda finds the iSCSI disk and is able to perform partitioning. Installation completes. On boot the system fails to find the root filesystem.
Relevant console messages:

... skip ...
SCSI subsystem initialized
Loading sd_mod.ko module
Loading scsi_transport_iscsi.ko module
Loading scsi_transport_iscsi2.ko module
Loading iSCSI transport class v2.0-871.
Loading libiscsi2.ko module
Loading libiscsi_tcp.ko module
Loading iscsi_tcp.ko module
iscsi: registered transport (tcp)
Loading virtio.ko module
Loading virtio_net.ko module
Bringing up eth0
waiting for link... 0 seconds.
Sending request for IP information through eth0
ERROR: Interface setup failed: pumpSetupInterface failed: get link - 19: No such device.
rename: error linking /var/lib/dhclient/dhclient.leases to new file /var/lib/dhclient/dhclient-eth0.leases: No such file or directory
Attaching to iSCSI storage
iscsistart: transport class version 2.0-871. iscsid version 2.0-871
iscsistart: version 2.0-871
iscsistart: Logging into iqn.2008-09.com.example:server.target1 10.16.65.142:3260,1
iscsistart: cannot make a connection to 10.16.65.142:3260 (-1,101)
iscsistart: initiator reported error (4 - encountered connection failure)
Loading virtio_ring.ko module
Loading virtio_pci.ko module
... skip ...

Expected results:
The system boots. 

Additional info:
Comment 1 Alexander Todorov 2010-07-12 09:09:04 EDT
Last lines in /var/log/messages on the host are:

Jul 12 09:08:14 hp-dl585g5-01 ntpd[2246]: Listening on interface #16 vnet0, fe80::70c6:31ff:fe5f:5044#123 Enabled
Jul 12 09:08:21 hp-dl585g5-01 kernel: kvm: 14525: cpu0 unimplemented perfctr wrmsr: 0xc0010004 data 0x0
Jul 12 09:08:21 hp-dl585g5-01 kernel: kvm: 14525: cpu0 unimplemented perfctr wrmsr: 0xc0010000 data 0x130076
Jul 12 09:08:21 hp-dl585g5-01 kernel: kvm: 14525: cpu0 unimplemented perfctr wrmsr: 0xc0010004 data 0xffffffffffde4630
Jul 12 09:08:21 hp-dl585g5-01 kernel: kvm: 14525: cpu0 unimplemented perfctr wrmsr: 0xc0010000 data 0x530076
Comment 6 RHEL Product and Program Management 2011-08-23 14:25:29 EDT
Development Management has reviewed and declined this request.  You may appeal
this decision by reopening this request.

Note You need to log in before you can comment on or make changes to this bug.