qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Chegu Vinod <chegu_vinod@hp.com>
To: qemu-devel qemu-devel <qemu-devel@nongnu.org>, seabios@seabios.org
Cc: Paolo Bonzini <pbonzini@redhat.com>,
	Marcelo Tosatti <mtosatti@redhat.com>
Subject: [Qemu-devel] OS crash while attempting to boot a 1TB guest.
Date: Mon, 03 Jun 2013 13:01:36 -0700	[thread overview]
Message-ID: <51ACF620.5080009@hp.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1090 bytes --]


Hello,

For guest sizes >= 1TB RAM  the guest OS is unable to boot up (please 
see attached GIF file for the Oops message). Wonder if this is a 
bug/regression in qemu/seabios or does one have to enable/disable 
something else in the qemu command line (pl. see below) ?

Thanks
Vinod


Host and Guest OS : 3.10-rc2 (from kvm.git) and qemu1.5.5 (from qemu.git 
as of May 28th)

The qemu command line :


/usr/local/bin/qemu-system-x86_64 \
-enable-kvm \
-cpu host \
-name vm1 \
-m 1048576 -smp 80,sockets=80,cores=1,threads=1 \
-mem-path /dev/hugepages \
-no-hpet \
-chardev 
socket,id=charmonitor,path=/var/lib/libvirt/qemu/vm1.monitor,server,nowait \
-mon chardev=charmonitor,id=monitor,mode=control -rtc base=utc 
-no-shutdown \
-drive 
file=/var/lib/libvirt/images/vm1/vm1.img,if=none,id=drive-virtio-disk0,format=raw,cache=none 
\
-device 
virtio-blk-pci,scsi=off,bus=pci.0,addr=0x5,drive=drive-virtio-disk0,id=virtio-disk0,bootindex=1 
\
-monitor stdio \
-net nic,model=virtio,macaddr=<...>,netdev=nic-0 \
-netdev tap,id=nic-0,ifname=tap0,script=no,downscript=no,vhost=on \
-vnc :4



[-- Attachment #2: guest_panic2.GIF --]
[-- Type: image/gif, Size: 19743 bytes --]

                 reply	other threads:[~2013-06-03 20:01 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=51ACF620.5080009@hp.com \
    --to=chegu_vinod@hp.com \
    --cc=mtosatti@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=seabios@seabios.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;
as well as URLs for NNTP newsgroup(s).