From mboxrd@z Thu Jan 1 00:00:00 1970 From: Gerry Reno Subject: Re: KVM-74: HELP PLEASE - cannot boot from cdrom for recovery Date: Tue, 31 Mar 2009 14:33:08 -0400 Message-ID: <49D261E4.4010607@verizon.net> References: <49D22FAF.5060808@verizon.net> <49D23022.5060101@wpkg.org> <49D231D0.3040805@verizon.net> <49D23255.8090202@wpkg.org> <49D2345D.1060101@verizon.net> <49D23BBF.5020804@messageone.com> <49D23D03.8090607@verizon.net> <49D24C56.6040502@verizon.net> <90eb1dc70903311005l32c5d631j21dfdbd1f8339c4f@mail.gmail.com> <49D25151.90207@verizon.net> <49D25358.2030805@verizon.net> <49D25AD9.7020304@verizon.net> <49D25B51.1010005@wpkg.org> <49D25F4E.9030700@verizon.net> <49D26001.90909@wpkg.org> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit To: kvm@vger.kernel.org Return-path: Received: from vms173005pub.verizon.net ([206.46.173.5]:46879 "EHLO vms173005pub.verizon.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752725AbZCaSdU (ORCPT ); Tue, 31 Mar 2009 14:33:20 -0400 Received: from [192.168.2.100] ([72.91.189.24]) by vms173005.mailsrvcs.net (Sun Java(tm) System Messaging Server 6.3-7.04 (built Sep 26 2008; 32bit)) with ESMTPA id <0KHD00L3VVJ9Z09I@vms173005.mailsrvcs.net> for kvm@vger.kernel.org; Tue, 31 Mar 2009 13:33:10 -0500 (CDT) In-reply-to: <49D26001.90909@wpkg.org> Sender: kvm-owner@vger.kernel.org List-ID: Tomasz Chmielewski wrote: > Gerry Reno schrieb: > >>> What does: >>> >>> md5sum /dev/sr0 >>> >>> output? >>> >>> >> DVD is Fedora 10 DVD (i386) >> >> Four cases: >> >> # desktop user; DVD unmounted >> $ md5sum /dev/sr0 >> md5sum: /dev/sr0: Input/output error >> >> # desktop user; DVD mounted >> $ md5sum /dev/sr0 >> ff311b322c894aabc4361c4e270f5a3f /dev/sr0 > > Download the iso file to your disk and point kvm there. > > It's the easiest to do; your problem is not really kvm-specific. > > I'll try that but it seems as though the process being owned by root is preventing the access to the cdrom. So isn't that kvm? Does libvirt know this? I mean never once have we been able to use the cdrom from the VM. Not just for this problem. This seems to be some kind of access problem. Regards, Gerry