[Expired for qemu-kvm (Ubuntu) because there has been no activity for 60
days.]
** Changed in: qemu-kvm (Ubuntu)
Status: Incomplete = Expired
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu-kvm in Ubuntu.
Please reply if you can still reproduce this bug.
** Changed in: qemu-kvm (Ubuntu)
Status: Confirmed = Incomplete
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu-kvm in Ubuntu.
https://bugs.launchpad.net/bugs/1047040
@serge-hallyn
Sorry for the late respond. The image file is provided by internal colleague in
my company. I am not sure if it is suitable to provide it to others other than
the one in our company. However, it seems behaves differently on different
hardware configuration. The VM was crashed
@serge-hallyn
this image is provided by others. It is a qcow2 image file.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu-kvm in Ubuntu.
https://bugs.launchpad.net/bugs/1047040
Title:
kvm crashed on precise - memory corruption
Can you give us the URL?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu-kvm in Ubuntu.
https://bugs.launchpad.net/bugs/1047040
Title:
kvm crashed on precise - memory corruption
To manage notifications about this bug go to:
@arnose
was this image a simple installation of quantal? Can you reproduce this
by creating images int he same way?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu-kvm in Ubuntu.
https://bugs.launchpad.net/bugs/1047040
Title:
It seems that I have a VM image which could cause this issue definitely
in a small round of reboot stress. The same VM would totally shutdown if
failed in free() and lock libvirtd if failed in malloc().
--
You received this bug notification because you are a member of Ubuntu
Server Team, which
** Changed in: qemu-kvm (Ubuntu)
Status: Incomplete = New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu-kvm in Ubuntu.
https://bugs.launchpad.net/bugs/1047040
Title:
kvm crashed on precise - memory corruption
To
** Changed in: qemu-kvm (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu-kvm in Ubuntu.
https://bugs.launchpad.net/bugs/1047040
Title:
kvm crashed on precise - memory corruption
To manage
Recently I also encounter this issue. I am running reboot stress test
with ubuntu desktop. After 2xxx times, the VM shutdown then reboot to
have the same memory corruption information in qemu.log. It also causes
my libvirt responds wierd. After kill the VM, libvirtd works well.
--
You received
Quoting Chun-Hung Chen (1047...@bugs.launchpad.net):
Recently I also encounter this issue. I am running reboot stress test
Thanks for the information.
with ubuntu desktop. After 2xxx times, the VM shutdown then reboot to
Does this mean more than 2000 times?
have the same memory corruption
Actually, I have encounter twice with the same VM at two different hardware
configuration.
One is running for more than two thousand times and another is about twenty
times.
** Attachment added: qemu log
** Attachment added: libvirtd.log
https://bugs.launchpad.net/ubuntu/+source/qemu-kvm/+bug/1047040/+attachment/3613354/+files/libvirtd.log.1
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu-kvm in Ubuntu.
** Attachment added: Another similar but not identical scenario with the same
VM
https://bugs.launchpad.net/ubuntu/+source/qemu-kvm/+bug/1047040/+attachment/3613355/+files/instance-000a.log
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is
** Attachment added: Another similar but not identical scenario with the same
VM
https://bugs.launchpad.net/ubuntu/+source/qemu-kvm/+bug/1047040/+attachment/3613356/+files/libvirtd.log.1
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is
[Expired for qemu-kvm (Ubuntu) because there has been no activity for 60
days.]
** Changed in: qemu-kvm (Ubuntu)
Status: Incomplete = Expired
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu-kvm in Ubuntu.
** Summary changed:
- kvm crashed - memory corruption
+ kvm crashed on precise - memory corruption
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu-kvm in Ubuntu.
https://bugs.launchpad.net/bugs/1047040
Title:
kvm crashed on
** Changed in: qemu-kvm (Ubuntu)
Importance: Undecided = High
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu-kvm in Ubuntu.
https://bugs.launchpad.net/bugs/1047040
Title:
kvm crashed on precise - memory corruption
To
Reboots have been running for a few hours now. Can't reproduce. Will
mark invalid, but reopen if i see it again.
** Changed in: qemu-kvm (Ubuntu)
Status: New = Incomplete
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to
Actually, marked incomplete since I can't get more information. (THe
laptop now has qemu-kvm-dbgsym installed so hopefully i'll run into it
again and be able to attach gdb to it)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to
20 matches
Mail list logo
