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 18:52:27 -0400 [thread overview]
Message-ID: <49D29EAB.90801@verizon.net> (raw)
In-Reply-To: <90eb1dc70903311227q308af046j7d9512d42c93eee1@mail.gmail.com>
Javier Guerra wrote:
> On Tue, Mar 31, 2009 at 2:13 PM, Gerry Reno <greno@verizon.net> wrote:
>
>> Javier Guerra wrote:
>>
>>> your underlying problem is that you can't get libvirt to generate the
>>> appropriate command line. you really should take it to the libvirt
>>> list
>>>
>>>
>>>
>> Ok, can you give me a command line that will work and then I'll take that
>> over to libvirt.
>>
>
> try this:
>
> /usr/bin/qemu-kvm -S -M pc -m 512 -smp 2 -name MX_3 -monitor pty -boot
> d -drive file=/var/vm/vm1/qemu/images/MX_3/MX_3.img,if=ide,index=0,boot=on
> -cdrom /dev/sr0 -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
>
Ok, I've been working with this for a couple hours but this command line
errors on F10 like this:
# /usr/bin/qemu-kvm -S -M pc -m 512 -smp 2 -name MX_3 -monitor pty -boot
d -drive
file=/var/vm/vm1/qemu/images/MX_3/MX_3.img,if=ide,index=0,boot=on -cdrom
/dev/sr0 -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
TUNGETIFF ioctl() failed: Bad file descriptor
char device redirected to /dev/pts/2
What does this error mean?
Regards,
Gerry
next prev parent reply other threads:[~2009-03-31 22:52 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
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 [this message]
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=49D29EAB.90801@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox