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 18:52:27 -0400 Message-ID: <49D29EAB.90801@verizon.net> References: <49D22FAF.5060808@verizon.net> <49D25358.2030805@verizon.net> <49D25AD9.7020304@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> 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]:35764 "EHLO vms173007pub.verizon.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1763921AbZCaWwt (ORCPT ); Tue, 31 Mar 2009 18:52:49 -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 <0KHE00GWP7JF9N05@vms173007.mailsrvcs.net> for kvm@vger.kernel.org; Tue, 31 Mar 2009 17:52:28 -0500 (CDT) In-reply-to: <90eb1dc70903311227q308af046j7d9512d42c93eee1@mail.gmail.com> Sender: kvm-owner@vger.kernel.org List-ID: Javier Guerra wrote: > On Tue, Mar 31, 2009 at 2:13 PM, Gerry Reno 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