All of lore.kernel.org
 help / color / mirror / Atom feed
From: Logan Bateman <1860742@bugs.launchpad.net>
To: qemu-devel@nongnu.org
Subject: [Bug 1860742] [NEW] xv6 Bootloop
Date: Fri, 24 Jan 2020 04:03:00 -0000	[thread overview]
Message-ID: <157983858012.5517.4456579868320256063.malonedeb@chaenomeles.canonical.com> (raw)

Public bug reported:

Qemu Version: 4.2.0

Launch command: 
qemu-system-x86_64 -nographic -drive file=fs.img,index=1,media=disk,format=raw -drive file=xv6.img,index=0,media=disk,format=raw -smp 2 -m 512

How to reproduce? 
1.)  Use/install latest release of qemu (4.2.0 at time of writing)

2.)  Download, build, and run xv6 (a simple os designed for learning
operating systems fundamentals)

cd /tmp
git clone https://github.com/mit-pdos/xv6-public.git
cd xv6-public
make qemu-nox

3.)  Qemu should now bootloop (seem to try to boot but then just
repeat). This is what it looks like below before it repeats:

SeaBIOS (version ?-20191223_100556-anatol)

iPXE (http://ipxe.org) 00:03.0 CA00 PCI2.10 PnP PMM+1FF92A50+1FEF2A50 CA00
                                                                               
Booting from Hard Disk..


Host: Arch Linux - Kernel version: 5.4.13
Guest: xv6 (https://github.com/mit-pdos/xv6-public)

Suspicion:

When I was using qemu 2.11.1 inside docker, the xv6 os booted with no
problem. I am thinking that something changed between Qemu 2.11.1 and
Qemu 4.2.0 which is now causing boot problems.

** Affects: qemu
     Importance: Undecided
         Status: New


** Tags: bootloop xv6

-- 
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1860742

Title:
  xv6 Bootloop

Status in QEMU:
  New

Bug description:
  Qemu Version: 4.2.0

  Launch command: 
  qemu-system-x86_64 -nographic -drive file=fs.img,index=1,media=disk,format=raw -drive file=xv6.img,index=0,media=disk,format=raw -smp 2 -m 512

  How to reproduce? 
  1.)  Use/install latest release of qemu (4.2.0 at time of writing)

  2.)  Download, build, and run xv6 (a simple os designed for learning
  operating systems fundamentals)

  cd /tmp
  git clone https://github.com/mit-pdos/xv6-public.git
  cd xv6-public
  make qemu-nox

  3.)  Qemu should now bootloop (seem to try to boot but then just
  repeat). This is what it looks like below before it repeats:

  SeaBIOS (version ?-20191223_100556-anatol)

  iPXE (http://ipxe.org) 00:03.0 CA00 PCI2.10 PnP PMM+1FF92A50+1FEF2A50 CA00
                                                                                 
  Booting from Hard Disk..


  Host: Arch Linux - Kernel version: 5.4.13
  Guest: xv6 (https://github.com/mit-pdos/xv6-public)

  Suspicion:

  When I was using qemu 2.11.1 inside docker, the xv6 os booted with no
  problem. I am thinking that something changed between Qemu 2.11.1 and
  Qemu 4.2.0 which is now causing boot problems.

To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1860742/+subscriptions


             reply	other threads:[~2020-01-24  4:11 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-24  4:03 Logan Bateman [this message]
2020-01-24  4:12 ` [Bug 1860742] Re: xv6 Bootloop Logan Bateman
2020-02-18 17:40 ` Mohammadreza Ghofrani
2020-05-11  8:37 ` Manavjeet Singh
2021-05-02 18:25 ` Thomas Huth
2021-05-03 20:50 ` Logan Bateman
2021-05-06  8:59 ` Thomas Huth

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=157983858012.5517.4456579868320256063.malonedeb@chaenomeles.canonical.com \
    --to=1860742@bugs.launchpad.net \
    --cc=qemu-devel@nongnu.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.