From mboxrd@z Thu Jan  1 00:00:00 1970
From: Brian Jackson <iggy@theiggy.com>
Subject: Re: KVM-74: HELP PLEASE - cannot boot from cdrom for recovery
Date: Tue, 31 Mar 2009 19:06:45 -0500
Message-ID: <200903311906.45348.iggy@theiggy.com>
References: <49D22FAF.5060808@verizon.net> <49D2A43C.30302@verizon.net> <49D2A855.4010300@verizon.net>
Mime-Version: 1.0
Content-Type: text/plain;
  charset="utf-8"
Content-Transfer-Encoding: 7bit
Cc: kvm@vger.kernel.org
To: Gerry Reno <greno@verizon.net>
Return-path: <kvm-owner@vger.kernel.org>
Received: from theiggy.com ([66.220.1.110]:55775 "EHLO mail.theiggy.com"
	rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP
	id S1755957AbZDAADu (ORCPT <rfc822;kvm@vger.kernel.org>);
	Tue, 31 Mar 2009 20:03:50 -0400
In-Reply-To: <49D2A855.4010300@verizon.net>
Content-Disposition: inline
Sender: kvm-owner@vger.kernel.org
List-ID: <kvm.vger.kernel.org>

On Tuesday 31 March 2009 18:33:41 Gerry Reno wrote:
> Gerry Reno wrote:
> > 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?
>
> 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.


The CD shouldn't be mounted. You just use /dev/cdrom or whatever as the option 
to -cdrom. No prep needed (other than inserting the CD)


> There just seems to be
> some access problem to the cdrom device from a root owned process.
>
> Regards,
> Gerry