[Expired for QEMU because there has been no activity for 60 days.]
** Changed in: qemu
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1463172
Title:
destination
[Expired for qemu (Ubuntu) because there has been no activity for 60
days.]
** Changed in: qemu (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1463172
Looking through old bug tickets... can you still reproduce this issue
with the latest version of QEMU? Or could we close this ticket nowadays?
** Changed in: qemu
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
** Changed in: qemu (Ubuntu)
Importance: Undecided => Low
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1463172
Title:
destination arm board hangs after migration from x86 source
To manage
** Changed in: qemu (Ubuntu)
Importance: Undecided => Low
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu in Ubuntu.
https://bugs.launchpad.net/bugs/1463172
Title:
destination arm board hangs after migration from x86 source
Hi,
would it be possible to run the emulator on arm under gdb (with
debugging symbols intalled), do the incoming migration, and then when it
hangs, show a backtrace from gdb?
** Changed in: qemu (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a
Hi,
would it be possible to run the emulator on arm under gdb (with
debugging symbols intalled), do the incoming migration, and then when it
hangs, show a backtrace from gdb?
** Changed in: qemu (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a
I'm going to mark this invalid as I don't believe this is a supported
case. If someone can vouch for the fact that this is supposed to work,
please leave a comment.
** Changed in: qemu (Ubuntu)
Status: New = Invalid
--
You received this bug notification because you are a member of
I'm going to mark this invalid as I don't believe this is a supported
case. If someone can vouch for the fact that this is supposed to work,
please leave a comment.
** Changed in: qemu (Ubuntu)
Status: New = Invalid
--
You received this bug notification because you are a member of
I think it is in theory supposed to work, but possibly in practice it
doesn't...
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu in Ubuntu.
https://bugs.launchpad.net/bugs/1463172
Title:
destination arm board hangs after
I think it is in theory supposed to work, but possibly in practice it
doesn't...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1463172
Title:
destination arm board hangs after migration from x86
Hm, ok, thanks - sadly i don't have any board I can test this on with
me. Wonder whether a rpi2 (which I have but not with me) would work.
** Changed in: qemu (Ubuntu)
Status: Invalid = New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is
Hm, ok, thanks - sadly i don't have any board I can test this on with
me. Wonder whether a rpi2 (which I have but not with me) would work.
** Changed in: qemu (Ubuntu)
Status: Invalid = New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Sorry, I forgot the include in the ram size parameter. I normally set it
to 512m so qemu-system-i386 -hda arch.img -boot d -m 512m.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu in Ubuntu.
https://bugs.launchpad.net/bugs/1463172
Thanks for the information.
I'm suspect that this sort of migration is not expected to work, but
I've marked the bug as affecting upstream in case someone there can
comment.
** Changed in: qemu (Ubuntu)
Status: Incomplete = New
--
You received this bug notification because you are a
I am migrating qemu-system-i386 on a x86 to an other qemu-system-i386 on
an arm. The exact command line is qemu-system-i386 -hda arch.img -boot
d. The arm board is the APM883208 X-C1. The hard drive image is stored
in a share nsf system.
--
You received this bug notification because you are a
Sorry, I forgot the include in the ram size parameter. I normally set it
to 512m so qemu-system-i386 -hda arch.img -boot d -m 512m.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1463172
Title:
I am migrating qemu-system-i386 on a x86 to an other qemu-system-i386 on
an arm. The exact command line is qemu-system-i386 -hda arch.img -boot
d. The arm board is the APM883208 X-C1. The hard drive image is stored
in a share nsf system.
--
You received this bug notification because you are a
Thanks for the information.
I'm suspect that this sort of migration is not expected to work, but
I've marked the bug as affecting upstream in case someone there can
comment.
** Changed in: qemu (Ubuntu)
Status: Incomplete = New
--
You received this bug notification because you are a
To be sure I'm understanding right, are you migrating from qemu-system-
arm on x86 to a native arm board? What are the exact parameters you are
passing the emulator, and what exactly is the physical board?
** Changed in: qemu (Ubuntu)
Status: New = Incomplete
** Also affects: qemu
To be sure I'm understanding right, are you migrating from qemu-system-
arm on x86 to a native arm board? What are the exact parameters you are
passing the emulator, and what exactly is the physical board?
** Changed in: qemu (Ubuntu)
Status: New = Incomplete
** Also affects: qemu
21 matches
Mail list logo