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

Gerry Reno
2009-03-31T23:16:33Z

Javier Guerra wrote:
> On Tue, Mar 31, 2009 at 5:52 PM, Gerry Reno <greno@verizon.net> wrote:
>
>> 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?
>>
>
> ah, i didn't notice the "fd=17" in the "-net" parameter.
>
> to make it simple, first try with userspace network:
>
> qemu-kvm -m 512 -hda /var/vm/vm1/qemu/images/MX_3/MX_3 -cdrom /dev/sr0
> -boot d -vnc 127.0.0.1
>
>
>
Ok, I ran this line:

qemu-kvm -m 512 -hda /var/vm/vm1/qemu/images/MX_3/MX_3.img -cdrom
/dev/sr0 -boot d -vnc 127.0.0.1:1

And it started the VM but I cannot connect to it for some reason.

The error:
$ vncviewer
Rect too big: 5x3584 at 10,0 exceeds 720x400

Have you ever seen this?
I don't know what's causing this but it seems like a really weird size.
I'm still working on this error...
Is there a way to tell vncviewer to connect anyway?

Regards,
Gerry