@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
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
@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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1047040
Title:
kvm crashed on precise - memory corruption
To manage
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
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
Bugs, which is
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
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
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
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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1047040
** 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
Bugs, which is subscribed to
** 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
Bugs, which is
There was not a problem with the current kernel but with the different
chips. We change the hardware so there is no prior kernel version which
is working on the Intel C600 without hotplug issues.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
apport-collect 1060760 can't be run on this machine. I will collect some
log files if needed. Besides, I have tried installed the kernel v3.6.1
and the Intel C600 driver is v1.1.0. Retry the scenario with a disk
unplugged then plugged again. Boom, shows different error messages and
kernel panic in
** Tags added: kernel-bug-exists-upstream
** Tags removed: needs-upstream-testing
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1060760
Title:
Hot plug and unplug causes system hangs
To manage
Gonna needs some time to do it. I will attach the results ASAP. Thanks.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1060760
Title:
Hot plug and unplug causes system hangs
To manage notifications
Public bug reported:
We are testing our hardware stability with hot plug and unplug several
times and it causes our system hangs.
The SAS Controller is Intel C600 with driver version 1.0.0. The syslog
related to the issue listed below.
Oct 2 16:10:41 MyTestBox kernel: : [354243.488743] sas:
21 matches
Mail list logo
