From mboxrd@z Thu Jan 1 00:00:00 1970 From: Gerry Reno Subject: Re: KVM-74: HELP PLEASE - cannot boot from cdrom for recovery Date: Tue, 31 Mar 2009 19:41:34 -0400 Message-ID: <49D2AA2E.3070200@verizon.net> References: <49D22FAF.5060808@verizon.net> <49D25B51.1010005@wpkg.org> <49D25F4E.9030700@verizon.net> <49D26001.90909@wpkg.org> <49D261E4.4010607@verizon.net> <49D266AA.1000104@verizon.net> <90eb1dc70903311212p10e4ccdes49ee4741d920b123@mail.gmail.com> <49D26B6F.8070109@verizon.net> <90eb1dc70903311227q308af046j7d9512d42c93eee1@mail.gmail.com> <49D29EAB.90801@verizon.net> <90eb1dc70903311559w53a37969n72dfd4adf8631501@mail.gmail.com> <49D2A43C.30302@verizon.net> <49D2A855.4010300@verizon.net> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit To: kvm@vger.kernel.org Return-path: Received: from vms173007pub.verizon.net ([206.46.173.7]:15777 "EHLO vms173007pub.verizon.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1765559AbZCaXlg (ORCPT ); Tue, 31 Mar 2009 19:41:36 -0400 Received: from [192.168.2.100] ([72.91.189.24]) by vms173007.mailsrvcs.net (Sun Java(tm) System Messaging Server 6.3-7.04 (built Sep 26 2008; 32bit)) with ESMTPA id <0KHE001AK9TA86XE@vms173007.mailsrvcs.net> for kvm@vger.kernel.org; Tue, 31 Mar 2009 18:41:34 -0500 (CDT) In-reply-to: <49D2A855.4010300@verizon.net> Sender: kvm-owner@vger.kernel.org List-ID: Gerry Reno wrote: > Gerry Reno wrote: >> Javier Guerra wrote: >>> On Tue, Mar 31, 2009 at 5:52 PM, Gerry Reno 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? >> > Ok, the third try the window came up. And it is showing the same 0003 > error as before on the cdrom boot. > I have no clue what is causing this error. I've turned off selinux, > I've made sure the disk is in drive and mounted. There just seems to > be some access problem to the cdrom device from a root owned process. > Nope, it's not just root. I tried as the desktop user and same result: $ 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 open /dev/kvm: Permission denied Could not initialize KVM, will disable KVM support Console show: Boot Failure Code: 0003 Boot from CDROM failed: cannot read the boot disk. FATAL: No bootable device. Regards, Gerry