Re: KVM-74: HELP PLEASE - cannot boot from cdrom for recovery

Gerry Reno
2009-03-31T22:52:49Z

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