From: "Blue Swirl" <blauwirbel@gmail.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] 32 bit emulating 64 bit
Date: Mon, 9 Jul 2007 20:06:01 +0300 [thread overview]
Message-ID: <f43fc5580707091006r2b491dd5jf8d37701b32ee716@mail.gmail.com> (raw)
In-Reply-To: <46926434.20600@bandsman.co.uk>
On 7/9/07, Nigel Horne <njh@bandsman.co.uk> wrote:
> Is it possible to use a 32 bit host to run a 64 bit guest? I can't get the IA64 version
> of FreeBSD6.2 to boot under my 32 bit Linux, qemu just changes its status bar to QEMU [ stopped ]
> no reason or message is printed, it just silently stops.
Generally yes, I don't know about IA64 status. For example Sparc64
emulator on x86 runs as fine as on x86-64:
OpenBIOS for Sparc64
boot arg = 0x0
00000000-08000000
RAM 128 MB
forth started.
initializing memory...done
Initializing PCI devices...
0:0.0 - 108e:a000 - /pci/pci108e,a000 - host
0:1.0 - 108e:5000 - /pci/pci108e,5000 - pci
0:1.1 - 108e:5000 - /pci/pci108e,5000 - pci
0:2.0 - 1013:b8 - /pci/pci1013,b8 - display
0:3.0 - 10ec:8029 - /pci/pci10ec,8029 - ethernet
0:4.0 - 8086:7010 - /pci/pci8086,7010 - ide
ide0: [io ports 0x1f0-0x1f7,0x3f6]
drive0 [ATA disk]: QEMU HARDDISK
ide1: [io ports 0x170-0x177,0x376]
drive0 [ATAPI floppy]: QEMU CD-ROM
floppy_init
FDC is a S82078B
floppy_reset
floppy_motor_off
SENSEI 20 00
status = 80, reply_buffer= 20 0
fdc_specify
FD_SPECIFY(c1, 11)
set_drive status = 80, new_dor = 10
floppy_recalibrate
fdc_state.version = 0062
invalid nvram partition length
nvram error detected, zapping pram
falling off...
Unhandled Exception 0x0000000000000008
PC = 0x0000000000000008 NPC = 0x000000000000000c
Stopping execution
The physical address space is much larger than 4G.
prev parent reply other threads:[~2007-07-09 17:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-09 16:37 [Qemu-devel] 32 bit emulating 64 bit Nigel Horne
2007-07-09 16:57 ` Avi Kivity
2007-07-09 17:11 ` Andreas Färber
2007-07-09 17:30 ` Nigel Horne
2007-07-09 17:06 ` Blue Swirl [this message]
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=f43fc5580707091006r2b491dd5jf8d37701b32ee716@mail.gmail.com \
--to=blauwirbel@gmail.com \
--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 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).