From: Brian Jackson <iggy@theiggy.com>
To: Gerry Reno <greno@verizon.net>
Cc: kvm@vger.kernel.org
Subject: Re: KVM-74: HELP PLEASE - cannot boot from cdrom for recovery
Date: Tue, 31 Mar 2009 19:06:45 -0500 [thread overview]
Message-ID: <200903311906.45348.iggy@theiggy.com> (raw)
In-Reply-To: <49D2A855.4010300@verizon.net>
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
next prev parent reply other threads:[~2009-04-01 0:03 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
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 [this message]
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=200903311906.45348.iggy@theiggy.com \
--to=iggy@theiggy.com \
--cc=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