On Fri, Aug 10, 2012 at 08:19:49AM +0000, Bhushan Bharat-R65777 wrote:
> > > > >> 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
> > > > >> <image.iso>). You can also add a -boot d to get it to choose the
> > > > >> cdrom
> > the first time for install.
> > > > >> Thanks,
> > > > >
> > > > > Thanks Avi and Alex, I can see the KVM guest boot prints by adding
> > > > > -append
> > > > "console=ttyS0"
> > > >
> > > > Note, once you get to user space you will need a getty specified in
> > > > inittab in order to get a login on your serial port. Something like:
> > > >
> > > > T0:23:respawn:/sbin/getty -L ttyS0
> > >
> > > 1)
> > > I tried booting with prebuilt qcow2 then it works for me:
> > > qemu-system-x86_64 -enable-kvm -nographic -device sga -m 1024 -hda
> > > debian_squeeze_amd64_standard.qcow2
> > >
> > > Does anyone help on how I can add my kernel to qcow2? Or create a proper
> > qcow2?
> > >
> > > 2)
> > > Also I tried as mentioned in section "3.9 Direct Linux Boot":
> > http://qemu.weilnetz.de/qemu-doc.html#disk_005fimages :
> > >
> > > qemu-kvm -enable-kvm -nographic -kernel /boot/vmlinuz-3.5.0+ -hda
> > > /boot/initramfs-3.5.0+.img -append "console=ttyS0 root=/dev/sda" -m
> > > 1024
> > >
> > -hda /boot/initramfs-3.5.0+.img is incorrect. Should be -hda
> > debian_squeeze_amd64_standard.qcow2 -initrd /boot/initramfs-3.5.0+.img and
> > root=/dev/sda1 probably.
>
> I tried :
> qemu-system-x86_64 -enable-kvm -nographic -kernel /boot/vmlinuz-3.5.0+
> -initrd /boot/initramfs-3.5.0+.img -append "root=/dev/sda1 rw console=ttyS0"
> -m 1024 -hda debian_squeeze_amd64_standard.qcow2
>
> With this I get the login prompt, but it is not taking input character from
> keyboard properly (not able to give login credentials even). Seeing some
> weird behavior, like sometimes it treat normal character as like ENTER
> pressed.
>
See other email in this thread about getty config. It would be simple
for you to not use -nographic.
--
Gleb.
