From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([208.118.235.92]:50102) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1SyPfb-0004Q9-6c for qemu-devel@nongnu.org; Mon, 06 Aug 2012 11:56:44 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1SyPfW-0000Bl-Vz for qemu-devel@nongnu.org; Mon, 06 Aug 2012 11:56:39 -0400 Received: from mx1.redhat.com ([209.132.183.28]:22657) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1SyPfW-0000A5-OB for qemu-devel@nongnu.org; Mon, 06 Aug 2012 11:56:34 -0400 Message-ID: <1344268591.3441.45.camel@ul30vt.home> From: Alex Williamson Date: Mon, 06 Aug 2012 09:56:31 -0600 In-Reply-To: <6A3DF150A5B70D4F9B66A25E3F7C888D03DF0AC5@039-SN2MPN1-022.039d.mgd.msft.net> References: <6A3DF150A5B70D4F9B66A25E3F7C888D03DF0AC5@039-SN2MPN1-022.039d.mgd.msft.net> Content-Type: text/plain; charset="UTF-8" Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] Running KVM guest on X86 List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Bhushan Bharat-R65777 Cc: "qemu-devel@nongnu.org" , Avi Kivity On Mon, 2012-08-06 at 15:40 +0000, Bhushan Bharat-R65777 wrote: > Hi Avi/All, > > I am facing issue to boot KVM guest on x86 (I used to work on PowerPC platform and do not have enough knowledge of x86). I am working on making VFIO working on PowerPC Booke, So I have cloned Alex Williamsons git repository, compiled kernel for x86 on fedora with virtualization configuration (selected all kernel config options for same). Run below command to boot Guest (I have not provided vfio device yet): > > "qemu-system-x86_64 -enable-kvm -m 1024 -nographic -kernel arch/x86_64/boot/bzImage -initrd /boot/initramfs-3.5.0-rc4+.img -serial tcp::4444,server,telnet" > > After the I can see qemu command line (able to run various commands like "info registers" etc), while guest does not boot (not even the first print comes). > > Can anyone help in what I am missing or doing wrong? x86 doesn't use the serial port for console by default, so you're making things quite a bit more difficult that way. Typically you'll want to provide a disk image (the -hda option is the easiest way to do this), a display (-vga std -vnc :0 is again easiest), and probably something to install from (-cdrom ). You can also add a -boot d to get it to choose the cdrom the first time for install. Thanks, Alex