On Mon, 2011-02-07 at 19:30 +0530, santwana wrote: > Hi All, > > I am facing issues while installing SLES11 SP1 GA guest using autotest > on the latest kernel(2.6.38-rc3). The installation is failing with the > error: > INFO | ERROR > kvm.raw.virtio_blk.smp2.SLES.11.1.64.virtio_net.unattended_install.cdrom > kvm.raw.virtio_blk.smp2.SLES.11.1.64.virtio_net.unattended_install.cdrom > timestamp=1296721316 localtime=Feb 03 13:51:56 Command <mount > -o > loop,rw /tmp/kvm_autotest_root/images/sles-11-1-64/autoyast.vfd > /home/vhost-net/autotest/client/tmp/tmpl56sOd_kvm.raw.virtio_blk.smp2.SLES.11.1.64.virtio_net.unattended_install.cdrom/floppy_S1bWxF> > failed, rc=32, Command returned non-zero exit status [context: > preprocessing --> Creating unattended install floppy image > /tmp/kvm_autotest_root/images/sles-11-1-64/autoyast.vfd] > * Command: > mount -o > loop,rw /tmp/kvm_autotest_root/images/sles-11-1-64/autoyast.vfd > > /home/vhost-net/autotest/client/tmp/tmpl56sOd_kvm.raw.virtio_blk.smp2.SLES > .11.1.64.virtio_net.unattended_install.cdrom/floppy_S1bWxF > Exit status: 32 > Duration: 0.0478329658508 > > stderr: > /dev/loop0: Permission denied
I was thinking about this problem, even though Santwana told me the problem was gone after she rebooted the machine. What I think it might have happened here is that all loopback devices were binded to images, probably due to prior kvm autotest executions that didn't clean properly for some reason. With all loopback taken, the mount wouldn't be possible. Santwana, if this happens again you might try: losetup -a To see which loopback devices are taken, if any. If there are like 8 devices taken, that's the reason why you hit the problem you described. Those can be cleaned up through losetup -d [loopback-name] provided the loopback mounts are not being used. Anyway, just thought it'd be a useful comment, Lucas _______________________________________________ Autotest mailing list Autotest@test.kernel.org http://test.kernel.org/cgi-bin/mailman/listinfo/autotest
