** Changed in: qemu
Status: New => 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/1754542
Title:
colo: vm crash with segmentation fault
Status in QEMU:
Fix Released
Bug desc
Public bug reported:
I use Arch Linux x86_64
both qemu 2.11.1 and Zhang
Chen's(https://github.com/zhangckid/qemu/commits/colo-with-virtio-net-internal-jul10)
Following document 'COLO-FT.txt',
I test colo feature on my hosts
I run this command
Primary:
sudo qemu-system-x86_64 -boot c -enable-kv
** Description changed:
I use Arch Linux x86_64
both qemu 2.11.1 and Zhang
Chen's(https://github.com/zhangckid/qemu/commits/colo-with-virtio-net-internal-jul10)
Following document 'COLO-FT.txt',
I test colo feature on my hosts
I run this command
Primary:
sudo qemu-system-x86_64 -
** Description changed:
I use Arch Linux x86_64
- both qemu 2.11.1 and Zhang
Chen's(https://github.com/zhangckid/qemu/commits/colo-with-virtio-net-internal-jul10)
+ Zhang
Chen's(https://github.com/zhangckid/qemu/commits/colo-with-virtio-net-internal-jul10)
Following document 'COLO-FT.txt',
** Summary changed:
- colo: secondary vm crash when execute x-colo-lost-heartbeat
+ colo: vm crash with segmentation fault
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1754542
Title:
colo: vm c
** Description changed:
I use Arch Linux x86_64
- Zhang
Chen's(https://github.com/zhangckid/qemu/commits/colo-with-virtio-net-internal-jul10)
+ Zhang Chen's(https://github.com/zhangckid/qemu/tree/qemu-colo-18mar10)
Following document 'COLO-FT.txt',
I test colo feature on my hosts
I run
** Description changed:
I use Arch Linux x86_64
Zhang Chen's(https://github.com/zhangckid/qemu/tree/qemu-colo-18mar10)
Following document 'COLO-FT.txt',
I test colo feature on my hosts
I run this command
Primary:
- sudo qemu-system-x86_64 -boot c -enable-kvm -m 2048 -smp 2 -qmp s
Hi Zhang Chen,
I follow the https://wiki.qemu.org/Features/COLO, And Vm no crash.
But SVM rebooting constantly after print RESET, PVM normal startup.
Secondary:
{"timestamp": {"seconds": 1521421788, "microseconds": 541058}, "event":
"RESUME"}
{"timestamp": {"seconds": 1521421808, "microseconds":
It is my trace event file.
I read it many times, but still can't find the cause of the error.
I just found after colo_vm_state_change ide_reset and ps2_kbd_reset ...
** Attachment added: "trace-pvm.log"
https://bugs.launchpad.net/qemu/+bug/1754542/+attachment/5084770/+files/trace-pvm.log
--
It is svn trace even
** Attachment added: "trace-svm.log"
https://bugs.launchpad.net/qemu/+bug/1754542/+attachment/5084771/+files/trace-svm.log
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/17545
I took a photo when SVM print reset.
It seems like kernel panic.
I hope this will help.
** Attachment added: "SVM_error.HEIC"
https://bugs.launchpad.net/qemu/+bug/1754542/+attachment/5086650/+files/SVM_error.HEIC
--
You received this bug notification because you are a member of qemu-
devel-
SVM error photo
** Attachment removed: "SVM_error.HEIC"
https://bugs.launchpad.net/qemu/+bug/1754542/+attachment/5086650/+files/SVM_error.HEIC
** Attachment added: "SVM.err.jpg"
https://bugs.launchpad.net/qemu/+bug/1754542/+attachment/5086654/+files/SVM.err.jpg
--
You received this bug
12 matches
Mail list logo