** Changed in: qemu
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/893208
Title:
qemu on ARM hosts can't boot i386 image
Status in QEMU:
Fix Released
Indeed, I had no problem booting the images this time around:
https://asciinema.org/a/d2m42g5c0n3z2pnbskhirdv5j
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/893208
Title:
qemu on ARM hosts can't
Looks like a patch for this issue has now been included here:
http://git.qemu.org/?p=qemu.git;a=commitdiff;h=d1bb099f6308d594061
** Changed in: qemu
Status: Confirmed => Fix Committed
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to
FWIW:
Program received signal SIGINT, Interrupt.
0xb644f73c in seqlock_read_retry (sl=0xb6b2acc8 , start=0)
at /tmp/qemu/include/qemu/seqlock.h:69
69 return unlikely(atomic_read(&sl->sequence) != start);
(gdb) bt
#0 0xb644f73c in seqlock_read_retry (sl=0xb6b2acc8 , start=0)
at /t
Unfortunately that doesn't seem to work. Qemu immediately goes into
infinite loop and has to be killed -9.
Building anything besides qemu-system-i386 leads to link errors:
LINK x86_64-linux-user/qemu-x86_64
/usr/bin/ld.gold.real: error: ../libqemustub.a(cpu-get-icount.o): multiple
definition
Another OS that works:
https://static.redox-os.org/redox-installer.iso
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/893208
Title:
qemu on ARM hosts can't boot i386 image
Status in QEMU:
Confir
No, this doesn't have anything to do with the RTC. It's just about our
fallback implementation of cpu_get_host_ticks() being very poor.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/893208
Title:
q
Would the presence of RTC make any difference?
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/893208
Title:
qemu on ARM hosts can't boot i386 image
Status in QEMU:
Confirmed
Status in Linaro QEMU
It doesn't work on my XU4 either. The supported virtualization would
probably work for ARM images but it's not something many people need.
What's the holdup, dear devs?
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.lau
The "holdup" is simply that nobody who is interested in this issue has
written a patch like that Paolo proposed in comment #13. (Mostly people
either want to run ARM or other guest images in emulation on x86, or
they're running ARM images with hardware virtualization on ARM hardware.
Trying to run
** Changed in: qemu
Status: New => Confirmed
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/893208
Title:
qemu on ARM hosts can't boot i386 image
Status in QEMU:
Confirmed
Status in Linaro
Still present in 2.5.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/893208
Title:
qemu on ARM hosts can't boot i386 image
Status in QEMU:
New
Status in Linaro QEMU:
New
Bug description:
If
Thanks for all the tips guys, I finally got it to work on my Rpi2.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/893208
Title:
qemu on ARM hosts can't boot i386 image
Status in QEMU:
New
Status
I tried installing openbsd yesterday from an official image to another
raw image disk - no problem and the installed system works flawlessly.
Hurd also boots fine (via grub) along with a few toy x86 kernels.
It almost begins to look as if the raw images are ok whereas the qcow2
format is the probl
BTW, it seems the more expensive (but vastly less popular) odroids like
the xu4 are built around kvm enabled processors which is why this bug
doesn't affect them.
The most popular C1/C1+'s processor doesn't support kvm though so any
update would be appreciated.
--
You received this bug notificat
get_clock() sounds like a good idea. Anybody post the patch? :)
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/893208
Title:
qemu on ARM hosts can't boot i386 image
Status in QEMU:
New
Status in
Thanks for looking into it, Laszlo. I've already tried dosbox and had
no idea qemu was impractical.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/893208
Title:
qemu on ARM hosts can't boot i386 ima
PeteVine: That sounds like a separate bug ; probably best to get a
separate report for it with a backtrace.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/893208
Title:
qemu on ARM hosts can't boot
What a funny coincidence, just before getting all of that bug email
(telepathy?), I decided to also try a debian hurd image, but it
immediately aborts:
qemu-system-i386: qemu-coroutine-lock.c:91: qemu_co_queue_restart_all:
Assertion `qemu_in_coroutine()' failed.
Aborted
Is this known and/or des
On 09/21/15 17:50, Dr. David Alan Gilbert wrote:
> * Peter Maydell (peter.mayd...@linaro.org) wrote:
>> On 21 September 2015 at 08:12, Laszlo Ersek wrote:
>>> Where does the division by zero come from then? Well grub fetches and
>>> stashes the TSC, then programs the PIT to sleep for some time, th
* Peter Maydell (peter.mayd...@linaro.org) wrote:
> On 21 September 2015 at 08:12, Laszlo Ersek wrote:
> > Where does the division by zero come from then? Well grub fetches and
> > stashes the TSC, then programs the PIT to sleep for some time, then
> > re-fetches the TSC, and uses the TSC differen
On 21 September 2015 at 08:12, Laszlo Ersek wrote:
> Where does the division by zero come from then? Well grub fetches and
> stashes the TSC, then programs the PIT to sleep for some time, then
> re-fetches the TSC, and uses the TSC difference as denominator when
> calculating the "TSC rate". (It h
On 09/19/15 12:54, Marina Kovalevna wrote:
> Hello boyos,
>
> I got myself an Rpi2 recently and have been reading up on qemu.
>
> Does this mean there's a problem booting x86 images on Arm or just the
> ones from that particular source?
>
The outlandishness of this use case (-> buy an underpowe
Hello boyos,
I got myself an Rpi2 recently and have been reading up on qemu.
Does this mean there's a problem booting x86 images on Arm or just the
ones from that particular source?
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
ht
Just for laughs I 've tested my qemu build with this guy's x86 kernel
and it's working as expected:
https://github.com/mopp/Axel
the difference being it was using -cdrom switch to boot from an .iso
image
--
You received this bug notification because you are a member of qemu-
devel-ml, which is
I was about to file a bug with the exact symptoms.
I can't boot a (possibly the very one) debian wheezy standard qcow2
image on my Odroid C1 (works fine on x86-32 with the same command line)
using qemu-system-i386 that I built yesterday from git source.
Is there a workaround or has nobody needed
On the basis of this analysis by David and since we don't seem to have
problems with ARM guests on ARM hosts, I think we can deprioritise this
bug as not being a requirement for KVM work.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU
** Changed in: qemu-linaro
Assignee: Dr. David Alan Gilbert (davidgil-uk) => (unassigned)
** Changed in: qemu-linaro
Importance: Undecided => Medium
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/b
** Also affects: qemu
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/893208
Title:
qemu on ARM hosts can't boot i386 image
Status in QEMU:
New
Status i
29 matches
Mail list logo
