From: Tomasz Chmielewski <mangoo@wpkg.org>
To: Gerry Reno <greno@verizon.net>
Cc: kvm@vger.kernel.org
Subject: Re: KVM-74: HELP PLEASE - cannot boot from cdrom for recovery
Date: Tue, 31 Mar 2009 20:05:05 +0200 [thread overview]
Message-ID: <49D25B51.1010005@wpkg.org> (raw)
In-Reply-To: <49D25AD9.7020304@verizon.net>
Gerry Reno schrieb:
> Gerry Reno wrote:
>> Gerry Reno wrote:
>>> Javier Guerra wrote:
>>>> On Tue, Mar 31, 2009 at 12:01 PM, Gerry Reno <greno@verizon.net> wrote:
>>>>
>>>>> Charles Duffy wrote:
>>>>> I put the xml stanza in the file and undefine/define domain but it
>>>>> gives an
>>>>> error about cannot read image file.
>>>>> <source file=/media/Fedora 10 DVD"/>
>>>>> And I check this path and I can read all the files from the command
>>>>> line on
>>>>> the DVD just fine.
>>>>> What could be the problem?
>>>>>
>>>>
>>>> don't put a mount dir, either use a ISO image, or the cdrom device file
>>>>
>>>>
>>>>
>>> Ok, a little closer now. I put this in xml file and redefine domain
>>> and it now defines:
>>>
>>> <source file=/dev/sr0"/>
>>> This was device that mount showed as mounting the DVD.
>>>
>>> But when the domain boots and I select 3. CDROM from screen, it still
>>> shows the original boot error:
>>> Boot Failure Code: 0003
>>> Boot from CDROM failed: cannot read the boot disk.
>>> FATAL: No bootable device.
>>> What should I change?
>>>
>> Here is what command looks like now using 'ps':
>> /usr/bin/qemu-kvm -S -M pc -m 512 -smp 2 -name MX_3 -monitor pty -boot
>> c -drive
>> file=/var/vm/vm1/qemu/images/MX_3/MX_3.img,if=ide,index=0,boot=on
>> -drive file=/dev/sr0,if=ide,media=cdrom,index=3 -net
>> nic,macaddr=00:0c:29:e3:bc:ee,vlan=0 -net
>> tap,fd=17,script=,vlan=0,ifname=vnet1 -serial none -parallel none -usb
>> -vnc 127.0.0.1:1 -k en-us
>>
> And I try other disk type:
> <disk type='block' device='cdrom'>
> But that produces the same error.
>
> What else can I add in order to boot from cdrom?
What does:
md5sum /dev/sr0
output?
--
Tomasz Chmielewski
http://wpkg.org
next prev parent reply other threads:[~2009-03-31 18:05 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 [this message]
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
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=49D25B51.1010005@wpkg.org \
--to=mangoo@wpkg.org \
--cc=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox