All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gerry Reno <greno@verizon.net>
To: kvm@vger.kernel.org
Subject: Re: KVM-74: HELP PLEASE - cannot boot from cdrom for recovery
Date: Tue, 31 Mar 2009 15:11:32 -0400	[thread overview]
Message-ID: <49D26AE4.9020101@verizon.net> (raw)
In-Reply-To: <49D266AA.1000104@verizon.net>

Gerry Reno wrote:
> Gerry Reno wrote:
>> 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.
>>
>>
> Ok, using an F10 ISO file when get access denied error when trying to 
> define the domain.  So I did this:  chcon -t virt_image_t F10-ISO-FILE 
> and now the domain defines ok.  BUT, even then using the ISO file we 
> still get the same error message as always:
> Boot Failure Code:  0003
> Boot from CDROM failed:  cannot read the boot disk.
> FATAL: No bootable device.
>
>
> The host runs with SELinux targeted enforce.  So thinking this might 
> be an selinux issue I set 'setenforce 0' to put it into permissive 
> mode but it made no difference.  Still the same boot error.
> Boot Failure Code:  0003
> Boot from CDROM failed:  cannot read the boot disk.
> FATAL: No bootable device.
>
We even tried setting the 'hvm' boot device to be 'cdrom' and it 
automatically tries to boot from the cdrom but it still gets the same 
0003 error as before.

Is there no way to recovery this VM?  Seems like we fell into a trap 
with no escape.

Regards,
Gerry


  reply	other threads:[~2009-03-31 19:11 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-31 14:58 KVM-74: HELP PLEASE - cannot boot from cdrom for recovery Gerry Reno
2009-03-31 15:00 ` Tomasz Chmielewski
2009-03-31 15:08   ` Gerry Reno
2009-03-31 15:10     ` Tomasz Chmielewski
2009-03-31 15:18       ` Gerry Reno
2009-03-31 15:50         ` Charles Duffy
2009-03-31 15:55           ` Gerry Reno
2009-03-31 16:13             ` Charles Duffy
2009-03-31 17:01               ` Gerry Reno
2009-03-31 17:05                 ` Javier Guerra
2009-03-31 17:22                   ` Gerry Reno
2009-03-31 17:31                     ` Gerry Reno
2009-03-31 18:03                       ` Gerry Reno
2009-03-31 18:05                         ` Tomasz Chmielewski
2009-03-31 18:22                           ` Gerry Reno
2009-03-31 18:25                             ` Tomasz Chmielewski
2009-03-31 18:33                               ` Gerry Reno
2009-03-31 18:53                                 ` Gerry Reno
2009-03-31 19:11                                   ` Gerry Reno [this message]
2009-03-31 19:12                                   ` Javier Guerra
2009-03-31 19:13                                     ` Gerry Reno
2009-03-31 19:27                                       ` Javier Guerra
2009-03-31 22:52                                         ` Gerry Reno
2009-03-31 22:59                                           ` Javier Guerra
2009-03-31 23:16                                             ` Gerry Reno
2009-03-31 23:33                                               ` Gerry Reno
2009-03-31 23:41                                                 ` Gerry Reno
2009-04-01  0:06                                                 ` Brian Jackson
2009-04-01  0:08                                                 ` Brian Jackson
2009-03-31 17:07                 ` Charles Duffy
2009-03-31 17:10                 ` Tomasz Chmielewski

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=49D26AE4.9020101@verizon.net \
    --to=greno@verizon.net \
    --cc=kvm@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.