Hide Forgot
Created attachment 500027 [details] snapshot Description of problem: anaconda crash when install with RHEL5.7-Server-20110518.0 and showing "errno 30 readonly file system" Version-Release number of selected component (if applicable): RHEL5.7-Server - tree 20110518.0 How reproducible: 1/30 Steps to Reproduce: 1.perform a installation inside VM qemu-kvm -name 'vm1' -monitor ... -serial .. \ -drive ..if=virtio,media=disk,cache=none,boot=on,format=qcow2 \ -net nic,vlan=0,model=virtio,macaddr='9a:19:f8:f4:80:33' \ -net tap,vlan=0,ifname='t0-023515-nqir',script='...switch'\ -m 4096 -smp 2,cores=1,threads=1,sockets=2 \ -drive file='5.7-x86_64-DVD.iso',media=cdrom,index=1 \ -drive file='ks.iso',media=cdrom,index=2 \ -cpu qemu64,+sse2 -soundhw ac97 \ -kernel '/usr/local/staf/test/RHEV/kvm/autotest-devel/client/tests/kvm/images/rhel57-64/vmlinuz' \ -initrd '/usr/local/staf/test/RHEV/kvm/autotest-devel/client/tests/kvm/images/rhel57-64/initrd.img' \ -spice port=8000,disable-ticketing \ -qxl 1 -rtc-td-hack -M rhel5.6.0 -boot n \ -usbdevice tablet -no-kvm-pit-reinjection \ --append 'ks=cdrom nicdelay=60 console=ttyS0,115200 console=tty0' 2. 3. Actual results: anaconda crash,pls see attached snapshot Expected results: installation finish successfully Additional info: Host_info: host_kernel x64-2.6.18-262 kvm_version kvm-83-232 full cmd: /usr/local/staf/test/RHEV/kvm/autotest-devel/client/tests/kvm/qemu -name 'vm1' -monitor unix:'/tmp/monitor-humanmonitor1-20110520-023515-nqir',server,nowait -serial unix:'/tmp/serial-20110520-023515-nqir',server,nowait -drive file='/usr/local/staf/test/RHEV/kvm/autotest-devel/client/tests/kvm/images/RHEL-Server-5.7-64-virtio.qcow2',index=0,if=virtio,media=disk,cache=none,boot=on,format=qcow2 -net nic,vlan=0,model=virtio,macaddr='9a:19:f8:f4:80:33' -net tap,vlan=0,ifname='t0-023515-nqir',script='/usr/local/staf/test/RHEV/kvm/autotest-devel/client/tests/kvm/scripts/qemu-ifup-switch',downscript='no' -m 4096 -smp 2,cores=1,threads=1,sockets=2 -drive file='/usr/local/staf/test/RHEV/kvm/autotest-devel/client/tests/kvm/isos/linux/RHEL-Server-5.7-x86_64-DVD.iso',media=cdrom,index=1 -drive file='/usr/local/staf/test/RHEV/kvm/autotest-devel/client/tests/kvm/isos/../images/rhel57-64/ks.iso',media=cdrom,index=2 -cpu qemu64,+sse2 -soundhw ac97 -kernel '/usr/local/staf/test/RHEV/kvm/autotest-devel/client/tests/kvm/images/rhel57-64/vmlinuz' -initrd '/usr/local/staf/test/RHEV/kvm/autotest-devel/client/tests/kvm/images/rhel57-64/initrd.img' -spice port=8000,disable-ticketing -qxl 1 -rtc-td-hack -M rhel5.6.0 -boot n -usbdevice tablet -no-kvm-pit-reinjection --append 'ks=cdrom nicdelay=60 console=ttyS0,115200 console=tty0'
Created attachment 500029 [details] guest serial output
Created attachment 500030 [details] kvm_stat info when running guest
Reporter, 1) are you using a kickstart for this installation? It doesn't look like from the commands in comment 0, but if you do please attach it. 2) what packages do you choose to install? 3) Can you please reproduce the crash and attach /mnt/sysimage/root/install.log to this log? Do you remember what package was being installed at the moment of the crash? The file we are flushing into is on the root filesystem so it should be writable at all times. It's however possible that either there's some weird package manipulating the writability installed or we're under changeroot and the file handler points to a wrong location for some reason.
Created attachment 500044 [details] ks iso file
(In reply to comment #3) > Reporter, Hi, > > 1) are you using a kickstart for this installation? It doesn't look like from > the commands in comment 0, but if you do please attach it. > I do install it using kickstart,uploaded ks.iso > 2) what packages do you choose to install? > pls check ks.iso > 3) Can you please reproduce the crash and attach /mnt/sysimage/root/install.log > to this log? Do you remember what package was being installed at the moment of > the crash? > I am trying reproduce it,packages are in the ks.cfg inside ks.iso Best Regards, Xiaoqing.
This has been in needinfo for three months, closing for insufficient data.