OK, since there hasn't been a reply within 6 months, I assume this is
now fixed. So closing this ticket now.
** Changed in: qemu
Status: Incomplete => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Do you still have this problem with the latest released version of QEMU
(see http://wiki.qemu-project.org/Download)?
** Changed in: qemu
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Anyone works on the crash now? The above back trace shows it crashed at
assert(s-current) ?
--
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/1303926
Title:
qemu-system-x86_64 crashed
Anyone works on the crash now? The above back trace shows it crashed at
assert(s-current) ?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1303926
Title:
qemu-system-x86_64 crashed with SIGABRT
To
I have the similar issue, the KVM 2.0 keeps crashing, here is the stack
I captured with GDB
(gdb) c
Continuing.
Program received signal SIGABRT, Aborted.
[Switching to Thread 0x7ffede1f9700 (LWP )]
0x7ffeee4d4f79 in __GI_raise (sig=sig@entry=6) at
I have the similar issue, the KVM 2.0 keeps crashing, here is the stack
I captured with GDB
(gdb) c
Continuing.
Program received signal SIGABRT, Aborted.
[Switching to Thread 0x7ffede1f9700 (LWP )]
0x7ffeee4d4f79 in __GI_raise (sig=sig@entry=6) at
Hi Serge,
I have opened this new bug:
https://bugs.launchpad.net/ubuntu/+source/qemu-kvm/+bug/1320144
--
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/1303926
Title:
Hi Serge,
I have opened this new bug:
https://bugs.launchpad.net/ubuntu/+source/qemu-kvm/+bug/1320144
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1303926
Title:
qemu-system-x86_64 crashed with
Hi Serge,
I think I have already reported the required information a number of times with
the Ubuntu built-in bug reporting facility (apport?), which asked me to report
the crash information to developers.
Are you able to find it out or do I need to manually open a new bug?
Thanks you.
--
Unfortunately the only bug launchpad shows me when I search for bugs reported
by you is https://bugs.launchpad.net/ubuntu/+source/qemu-kvm/+bug/1180777
If you can give me a bug# that would be great, otherwise please do file a
new bug.
--
You received this bug notification because you are a
Hi Serge,
I think I have already reported the required information a number of times with
the Ubuntu built-in bug reporting facility (apport?), which asked me to report
the crash information to developers.
Are you able to find it out or do I need to manually open a new bug?
Thanks you.
--
Unfortunately the only bug launchpad shows me when I search for bugs reported
by you is https://bugs.launchpad.net/ubuntu/+source/qemu-kvm/+bug/1180777
If you can give me a bug# that would be great, otherwise please do file a
new bug.
--
You received this bug notification because you are a
Hi Serge,
I keep getting the crash notification due to kvm crashes with the same
bug title as this one. I see that the status is Fix Released, I'm on
precise and fully up-to-date.
My package is:
ii qemu-kvm 1.0+noroms-0ubuntu14.14
Full virtualization on i386 and
Hi,
the cause of this particular bug was introduced during 2014, so could
not have been present in precise. We definately will want to figure out
the cause of your bug, so please open a new bug report using 'ubuntu-bug
qemu-kvm' immediately after a crash has happened.
Thanks!
** Also affects:
Hi,
the cause of this particular bug was introduced during 2014, so could
not have been present in precise. We definately will want to figure out
the cause of your bug, so please open a new bug report using 'ubuntu-bug
qemu-kvm' immediately after a crash has happened.
Thanks!
** Also affects:
Hi Serge,
I keep getting the crash notification due to kvm crashes with the same
bug title as this one. I see that the status is Fix Released, I'm on
precise and fully up-to-date.
My package is:
ii qemu-kvm 1.0+noroms-0ubuntu14.14
Full virtualization on i386 and
This bug was fixed in the package qemu - 2.0.0~rc1+dfsg-0ubuntu3
---
qemu (2.0.0~rc1+dfsg-0ubuntu3) trusty; urgency=medium
* d/p/ubuntu/kvm_physical_sync_dirty_bitmap-ignore-ENOENT-from-kv.patch
don't abort() just because the kernel has no dirty bitmap.
(LP: #1303926)
--
This bug was fixed in the package qemu - 2.0.0~rc1+dfsg-0ubuntu3
---
qemu (2.0.0~rc1+dfsg-0ubuntu3) trusty; urgency=medium
* d/p/ubuntu/kvm_physical_sync_dirty_bitmap-ignore-ENOENT-from-kv.patch
don't abort() just because the kernel has no dirty bitmap.
(LP: #1303926)
--
** Attachment removed: CoreDump.gz
https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1303926/+attachment/4072413/+files/CoreDump.gz
** Information type changed from Private to Public
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed
** Changed in: qemu (Ubuntu)
Importance: Undecided = High
** Changed in: qemu (Ubuntu)
Assignee: (unassigned) = Serge Hallyn (serge-hallyn)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu in Ubuntu.
And it is not just with vnc either.
** Changed in: qemu (Ubuntu)
Status: New = Triaged
--
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/1303926
Title:
qemu-system-x86_64 crashed
** Also affects: qemu
Importance: Undecided
Status: New
--
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/1303926
Title:
qemu-system-x86_64 crashed with SIGABRT
To manage
2f487a3d40faff1772e14da6b921900915501f9a was ok, so bisecting right now.
--
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/1303926
Title:
qemu-system-x86_64 crashed with SIGABRT
To
Hm, bisect is pointing at 6ff45f01c734e1ad051f19913449e2577c9f4b7d
which is very unlikely. I'll have to keep playing.
--
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/1303926
Title:
Pretty sure that commit b533f658a98325d0e47b36113bd9f5bcc046fdae is the
first bad commit.
This is interesting. The commit is correct in that kvm_vm_ioctl()
returns -errno, not -1, on error. However, the caller,
kvm_physical_sync_dirty_bitmap, on seeing the error, shortcuts some
extra errors to
At the point when the ioctl fails, this is the backtrace:
(gdb) where
#0 kvm_physical_sync_dirty_bitmap (section=0x7fffd820) at
/home/serge/src/qemu/kvm-all.c:446
#1 0x5580e30c in kvm_log_sync (listener=optimized out,
section=optimized out) at /home/serge/src/qemu/kvm-all.c:803
#2
(which means my comment #8 is off track - the caller in this case is
checking the return value, then aborting - and this is the exact same
backtrace as we get anyway)
** Changed in: qemu (Ubuntu)
Assignee: Serge Hallyn (serge-hallyn) = (unassigned)
--
You received this bug notification
It seems reasonable that if we are requesting writing a dirty bitmap,
and kernel says it's not dirty, we ignore that failure? I.e. ignore
ENOENT?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu in Ubuntu.
Looking at arch/x86/kvm/x86.c, ENOENT (only) happens when
memslot-dirty_bitmap is NULL in kvm_vm_ioctl_get_dirty_log().
--
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/1303926
Title:
** Attachment removed: CoreDump.gz
https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1303926/+attachment/4072413/+files/CoreDump.gz
** Information type changed from Private to Public
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Changed in: qemu (Ubuntu)
Importance: Undecided = High
** Changed in: qemu (Ubuntu)
Assignee: (unassigned) = Serge Hallyn (serge-hallyn)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
And it is not just with vnc either.
** Changed in: qemu (Ubuntu)
Status: New = Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1303926
Title:
qemu-system-x86_64 crashed with SIGABRT
** Also affects: qemu
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1303926
Title:
qemu-system-x86_64 crashed with SIGABRT
To manage notifications about
2f487a3d40faff1772e14da6b921900915501f9a was ok, so bisecting right now.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1303926
Title:
qemu-system-x86_64 crashed with SIGABRT
To manage
Hm, bisect is pointing at 6ff45f01c734e1ad051f19913449e2577c9f4b7d
which is very unlikely. I'll have to keep playing.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1303926
Title:
Pretty sure that commit b533f658a98325d0e47b36113bd9f5bcc046fdae is the
first bad commit.
This is interesting. The commit is correct in that kvm_vm_ioctl()
returns -errno, not -1, on error. However, the caller,
kvm_physical_sync_dirty_bitmap, on seeing the error, shortcuts some
extra errors to
(which means my comment #8 is off track - the caller in this case is
checking the return value, then aborting - and this is the exact same
backtrace as we get anyway)
** Changed in: qemu (Ubuntu)
Assignee: Serge Hallyn (serge-hallyn) = (unassigned)
--
You received this bug notification
At the point when the ioctl fails, this is the backtrace:
(gdb) where
#0 kvm_physical_sync_dirty_bitmap (section=0x7fffd820) at
/home/serge/src/qemu/kvm-all.c:446
#1 0x5580e30c in kvm_log_sync (listener=optimized out,
section=optimized out) at /home/serge/src/qemu/kvm-all.c:803
#2
It seems reasonable that if we are requesting writing a dirty bitmap,
and kernel says it's not dirty, we ignore that failure? I.e. ignore
ENOENT?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1303926
Looking at arch/x86/kvm/x86.c, ENOENT (only) happens when
memslot-dirty_bitmap is NULL in kvm_vm_ioctl_get_dirty_log().
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1303926
Title:
40 matches
Mail list logo
