Bug 621043
|
Description
Chao Yang
2010-08-04 05:58:25 UTC
Created attachment 436440 [details]
VM define file.
Created attachment 436441 [details]
/tmp/ directory of the VM
This issue has been proposed when we are only considering blocker issues in the current Red Hat Enterprise Linux release. ** If you would still like this issue considered for the current release, ask your support representative to file as a blocker on your behalf. Otherwise ask that it be considered for the next Red Hat Enterprise Linux release. ** Hi, I also tried to load the driverdisk from harddisk, the same DUD and VM. The driver had been loaded as expected. ***************************** bash-4.1# busybox cat /sys/module/sym53c8xx/version 2.2.3rhtest60b1 bash-4.1# ***************************** Created attachment 436463 [details]
anaconda.log for load driver from harddisk.
Created attachment 436464 [details]
syslog for load driver from harddisk.
Try NFS method, also failed to load. We can see the driver is download and unpacked from the nfs location, but didn't get loaded. ----------------------------------------- bash-4.1# busybox cat /sys/module/sym53c8xx/version 2.2.3 bash-4.1# rmmod sym53c8xx bash-4.1# modprobe sym53c8xx bash-4.1# busybox cat /sys/module/sym53c8xx/version 2.2.3.rhtest60b1 Attached the /tmp/ dir for ref. Thanks. Best, Chao Created attachment 437786 [details]
/tmp/ dir for load driver image file from nfs server.
Re-assign to Anaconda. I suspect it's very similar to some of the other issues. Note that this says FTP and not TFTP so it's perhaps not the lack of re-running depmod from within the initramfs, and besides, it looks like the driver is put in place but just not loaded. Weird. Anyway, it's an Anaconda issue I think :) Created attachment 437810 [details]
/tmp/ dir for load driver from http server.
What I have observed here: 1. Failed to load driver disk from all three network locations(HTTP, FTP, NFS). 2. Manually modprobe can load the update driver. This is a basic function for DUD, give high Priority. If you need any further information please let me know. Thanks. Best, Chao If you check the /lib/modules/<kernel version>/modules.dep, can you see the module there with path in updates/DD dir? (should be) And is there any other line with that driver not being in updates dir? (shouldn't be) Also do you see the module being present in /tmp/DD? (should be) If all my assertions are valid, then it doesn't seem to be Anaconda itself and I need log files, content of /tmp/DD and /tmp/DD-0 and detailed reproduction steps to investigate. Hi Martin, I Just checked the files, and here is answers. (In reply to comment #13) > If you check the /lib/modules/<kernel version>/modules.dep, can you see the > module there with path in updates/DD dir? (should be) > bash4-1# grep updates /lib/modules/2.6.32-59.1.el6.x86_64/modules.dep updates/DD/2.6.32-59.1.el6.x86_64/extra/sym53c8xx/sym53c8xx.ko: kernel/drivers/scsi/scsi_transport_spi.ko.gz > And is there any other line with that driver not being in updates dir? > (shouldn't be) > Nothing else. > Also do you see the module being present in /tmp/DD? (should be) > bash4-1# busybox ls /tmp/DD/lib/modules/2.6.32-59.1.el6.x86_64/extra/sym53c8xx/sym53c8xx.ko /tmp/DD/lib/modules/2.6.32-59.1.el6.x86_64/extra/sym53c8xx/sym53c8xx.ko > If all my assertions are valid, then it doesn't seem to be Anaconda itself and > I need log files, content of /tmp/DD and /tmp/DD-0 and detailed reproduction > steps to investigate. You can find log files, content of /tmp/DD and /tmp/DD-0 and in the attachment tarball files. How to reproduce: 1. config HTTP/FTP/NFS server with 2.6.32-59 version DUD. 2. modify virtual machine define xml file, add following lines: <cmdline>linux dd=http://10.66.65.116/dd-59.iso</cmdline> # Using http <cmdline>linux dd=ftp://10.66.65.116/pub/dd-59.iso</cmdline> # Using ftp <cmdline>linux dd=nfs:10.66.65.116:/nfs-repo/dd-59.iso</cmdline> Using nfs 3. virsh define <vm xml file> to register vm to your virt-manager 4. start vm and the driver should be loaded automaticly. Anything missing or wrong please let me know. Thanks a lot! Best, Chao Hi Martin, Also you can get my xml define file in the attachment. Best, Chao There is another bug you should also be watching that is related, but not quite the same issue. That is that when building an initramfs, dracut does not include the "updates" directory. It does now include the "extra" and "weak-updates" directory as of today, and I am hoping the other directory for tomorrow. https://bugzilla.redhat.com/show_bug.cgi?id=622641 Jon. For clarity, comment 17 is just an FYI. It is not intended to address this. Please retest using a current nightly tree containing anaconda-13.21.77-1 or later. This will be done with the compose that completes on 20100817. Jon. Chao: can you test this please with the 2010817 when it shows up in a few hours? Jon. Thanks :) Sure, when will the 201080817 tree available? Best, Chao TEST RESULTS ------------ The updates image supplied by Martin does get through the install, HOWEVER, the kmod is not installed on the finish system and the updated driver is not used: $ rpm -qa | grep kmod <nothing> This urgently requires fixing. Please investigate why the kmod RPM is not targeted for installation, and perform any necessary testing. Thanks for initial fix - we're half way there :) Jon. Just using the latest 20100817 tree (http://download.devel.redhat.com/nightly/RHEL6.0-20100817.n.0/6/Server/x86_64/os/) to reproduce. I found that driver still can't be loaded from http. But this time, instead of the error message, the installer prompt you to choose a language. And also try to load from CDROM. loaded correctly. Best, Chao Created attachment 439094 [details]
load driver from http server screenshot.
Created attachment 439095 [details]
load driver from http server /tmp/ folder, including anaconda.log, syslog etc.
Created attachment 439096 [details]
load driver from http server VM config file.
Workaround is to load driver disks from CD-ROM as stated in comment #27. No data corruption occurs because of this bug, so given that we have that and a valid workaround, this doesn't meet remaining 6.0 blocker criteria. Moving this one to 6.1. According to my testing, adding new drivers from network based driverdisks should work. Only updates are problematic, because we cannot refresh all loaded drivers due to NM being already started (it tracebacked when I tried). Addendum to previous comment: It is ok to ship 6.0 without support for loading driver disks from FTP/HTTP, however we *must* verify that TFTP based (when contained within the initramfs) updates work at a minimum. Jon. I have just verified TFTP case, working fine. Here is my steps to verify:
1. Setup the PXE/TFTP server in the host.
2. Set a VM to boot from PXE, also change the network to a special pxe network.
3. Modify initrd image file, two things to do here:
(1) Add "busybox" tool to bin;
(2) Add dd.iso file;
Following the instruction: "Anaconda Initrd Update" (http://intranet.corp.redhat.com/ic/intranet/AnacondaInitrdUpdate.html)
4. Boot the VM from PXE.
5. Driver updated correctlly.
Attach screenshot, syslog and anaconda.log.
Best,
Chao
Created attachment 439296 [details]
screenshot of dud from TFTP.
Created attachment 439299 [details]
syslog for dud from TFTP.
Created attachment 439300 [details]
anaconda.log for dud from TFTP.
Since the TFTP is working, remove the blocker ? flag. Thanks. Best, Chao Chao: we need to test this with the 20100818 compose or a later version. That is currently being built, so in a few hours we can test it with the full nightly. Jon. Verified on i386 and x86_64 arch, driver update from PXE/TFTP works as expected. So I suppose we are done here. Best, Chao Sorry to forget the tree info: 20100818. Thanks. Best, Chao Can you include a screenshot or some data from the install? Can you run: $ rpm -qa | grep kmod After the install and show that the module was loaded? Also: $ modinfo <module name> To show the right one is being picked up? Thanks. Thanks. I am willing to consider this VERIFIED now. Red Hat Enterprise Linux 6.0 is now available and should resolve the problem described in this bug report. This report is therefore being closed with a resolution of CURRENTRELEASE. You may reopen this bug report if the solution does not work for you. |