[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Qemu-devel] [Bug 1754542] Re: colo: vm crash with segmentation fault
From: |
李穗恒 |
Subject: |
[Qemu-devel] [Bug 1754542] Re: colo: vm crash with segmentation fault |
Date: |
Mon, 12 Mar 2018 00:39:27 -0000 |
** 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 this command
Primary:
sudo qemu-system-x86_64 -boot c -enable-kvm -m 2048 -smp 2 -qmp stdio
-name primary \
-device piix3-usb-uhci \
-device usb-tablet -netdev tap,id=hn0,vhost=off \
-device virtio-net-pci,id=net-pci0,netdev=hn0 \
-drive
if=virtio,id=colo-disk0,driver=quorum,read-pattern=fifo,vote-threshold=1,children.0.file.filename=/var/lib/libvirt/images/1.raw,children.0.driver=raw
-S
Secondary:
sudo qemu-system-x86_64 -boot c -enable-kvm -m 2048 -smp 2 -qmp stdio -name
secondary \
-device piix3-usb-uhci \
-device usb-tablet -netdev tap,id=hn0,vhost=off \
-device virtio-net-pci,id=net-pci0,netdev=hn0 \
-drive
if=none,id=colo-disk0,file.filename=/var/lib/libvirt/images/2.raw,driver=raw,node-name=node0
\
-drive if=virtio,id=active-disk0,driver=replication,mode=secondary,\
file.driver=qcow2,top-id=active-disk0,\
file.file.filename=/mnt/ramfs/active_disk.img,\
file.backing.driver=qcow2,\
file.backing.file.filename=/mnt/ramfs/hidden_disk.img,\
file.backing.backing=colo-disk0 \
-incoming tcp:0:8888
Secondary:
{'execute':'qmp_capabilities'}
{ 'execute': 'nbd-server-start',
- 'arguments': {'addr': {'type': 'inet', 'data': {'host': '192.168.0.33',
'port': '8889'} } }
+ 'arguments': {'addr': {'type': 'inet', 'data': {'host': '192.168.0.34',
'port': '8889'} } }
}
{'execute': 'nbd-server-add', 'arguments': {'device': 'colo-disk0',
'writable': true } }
Primary:
{'execute':'qmp_capabilities'}
{ 'execute': 'human-monitor-command',
'arguments': {'command-line': 'drive_add -n buddy
driver=replication,mode=primary,file.driver=nbd,file.host=192.168.0.34,file.port=8889,file.export=colo-disk0,node-name=nbd_client0'}}
{ 'execute':'x-blockdev-change', 'arguments':{'parent': 'colo-disk0', 'node':
'nbd_client0' } }
{ 'execute': 'migrate-set-capabilities',
'arguments': {'capabilities': [ {'capability': 'x-colo', 'state': true
} ] } }
{ 'execute': 'migrate', 'arguments': {'uri': 'tcp:192.168.0.34:8888' } }
- { 'execute': 'migrate-set-parameters' , 'arguments':{ 'x-checkpoint-delay':
2000 } }
+
And two VM with cash
Primary:
{"timestamp": {"seconds": 1520763655, "microseconds": 511415}, "event":
"RESUME"}
[1] 329 segmentation fault sudo /usr/local/bin/qemu-system-x86_64 -boot c
-enable-kvm -m 2048 -smp 2 -qm
Secondary:
{"timestamp": {"seconds": 1520763655, "microseconds": 510907}, "event":
"RESUME"}
[1] 367 segmentation fault sudo /usr/local/bin/qemu-system-x86_64 -boot c
-enable-kvm -m 2048 -smp 2 -qm
-
-
-
- ---------------------------------------------------------------------
- if use qemu 2.11.1
- The sync will success,but when Secondary VM execute
x-colo-lost-heartbeat,Secondary VM will crash
- Secondary:
- { 'execute': 'nbd-server-stop' }
- { 'execute': 'x-colo-lost-heartbeat' }{"return": {}}
- qemu-system-x86_64: Disconnect client, due to: Unexpected end-of-file before
all bytes were read
-
- {"return": {}}
- qemu-system-x86_64: Can't receive COLO message: Input/output error
- **
- ERROR:/build/qemu/src/qemu-2.11.1/qom/object.c:907:object_unref: assertion
failed (obj->ref > 0): (0 > 0)
- [1] 1276 abort sudo /usr/bin/qemu-system-x86_64 -boot c -enable-kvm
-m 2048 -smp 2 -qmp stdi
--
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:
New
Bug description:
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 stdio
-name primary \
-device piix3-usb-uhci \
-device usb-tablet -netdev tap,id=hn0,vhost=off \
-device virtio-net-pci,id=net-pci0,netdev=hn0 \
-drive
if=virtio,id=colo-disk0,driver=quorum,read-pattern=fifo,vote-threshold=1,children.0.file.filename=/var/lib/libvirt/images/1.raw,children.0.driver=raw
-S
Secondary:
sudo qemu-system-x86_64 -boot c -enable-kvm -m 2048 -smp 2 -qmp stdio -name
secondary \
-device piix3-usb-uhci \
-device usb-tablet -netdev tap,id=hn0,vhost=off \
-device virtio-net-pci,id=net-pci0,netdev=hn0 \
-drive
if=none,id=colo-disk0,file.filename=/var/lib/libvirt/images/2.raw,driver=raw,node-name=node0
\
-drive if=virtio,id=active-disk0,driver=replication,mode=secondary,\
file.driver=qcow2,top-id=active-disk0,\
file.file.filename=/mnt/ramfs/active_disk.img,\
file.backing.driver=qcow2,\
file.backing.file.filename=/mnt/ramfs/hidden_disk.img,\
file.backing.backing=colo-disk0 \
-incoming tcp:0:8888
Secondary:
{'execute':'qmp_capabilities'}
{ 'execute': 'nbd-server-start',
'arguments': {'addr': {'type': 'inet', 'data': {'host': '192.168.0.34',
'port': '8889'} } }
}
{'execute': 'nbd-server-add', 'arguments': {'device': 'colo-disk0',
'writable': true } }
Primary:
{'execute':'qmp_capabilities'}
{ 'execute': 'human-monitor-command',
'arguments': {'command-line': 'drive_add -n buddy
driver=replication,mode=primary,file.driver=nbd,file.host=192.168.0.34,file.port=8889,file.export=colo-disk0,node-name=nbd_client0'}}
{ 'execute':'x-blockdev-change', 'arguments':{'parent': 'colo-disk0', 'node':
'nbd_client0' } }
{ 'execute': 'migrate-set-capabilities',
'arguments': {'capabilities': [ {'capability': 'x-colo', 'state': true
} ] } }
{ 'execute': 'migrate', 'arguments': {'uri': 'tcp:192.168.0.34:8888' } }
And two VM with cash
Primary:
{"timestamp": {"seconds": 1520763655, "microseconds": 511415}, "event":
"RESUME"}
[1] 329 segmentation fault sudo /usr/local/bin/qemu-system-x86_64 -boot c
-enable-kvm -m 2048 -smp 2 -qm
Secondary:
{"timestamp": {"seconds": 1520763655, "microseconds": 510907}, "event":
"RESUME"}
[1] 367 segmentation fault sudo /usr/local/bin/qemu-system-x86_64 -boot c
-enable-kvm -m 2048 -smp 2 -qm
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1754542/+subscriptions
- [Qemu-devel] [Bug 1754542] [NEW] colo: secondary vm crash when execute x-colo-lost-heartbeat, 李穗恒, 2018/03/08
- [Qemu-devel] [Bug 1754542] Re: colo: secondary vm crash when execute x-colo-lost-heartbeat, 李穗恒, 2018/03/08
- [Qemu-devel] [Bug 1754542] Re: colo: secondary vm crash when execute x-colo-lost-heartbeat, 李穗恒, 2018/03/11
- [Qemu-devel] [Bug 1754542] Re: colo: vm crash with segmentation fault, 李穗恒, 2018/03/11
- [Qemu-devel] [Bug 1754542] Re: colo: vm crash with segmentation fault,
李穗恒 <=
- [Qemu-devel] [Bug 1754542] Re: colo: vm crash with segmentation fault, 李穗恒, 2018/03/11
- Re: [Qemu-devel] [Bug 1754542] [NEW] colo: secondary vm crash when execute x-colo-lost-heartbeat, Zhang Chen, 2018/03/17
- Re: [Qemu-devel] [Bug 1754542] [NEW] colo: secondary vm crash when execute x-colo-lost-heartbeat, Zhang Chen, 2018/03/17
- [Qemu-devel] [Bug 1754542] Re: colo: vm crash with segmentation fault, 李穗恒, 2018/03/18
[Qemu-devel] [Bug 1754542] Re: colo: vm crash with segmentation fault, 李穗恒, 2018/03/20
[Qemu-devel] [Bug 1754542] Re: colo: vm crash with segmentation fault, 李穗恒, 2018/03/20