From: lee <1754542@bugs.launchpad.net>
To: qemu-devel@nongnu.org
Subject: Re: [Bug 1754542] Re: colo: vm crash with segmentation fault
Date: Wed, 27 Nov 2019 06:35:12 -0000 [thread overview]
Message-ID: <CAACkWBuALs=XdGhoi2KKSxUrkwqLmDxSeXeUhigLJp5A5m2DHA@mail.gmail.com> (raw)
In-Reply-To: CAK3tnv+Xi2s2sAmdxDA6ip3YOQUA3St909BF+_LEULCQkeVoNw@mail.gmail.com
Hi Zhang Chen
I use sysbench compare Host、Qemu Native VM(virtio-blk)、Qemu Native VM、Qemu
colo disk performance.
The result in below attachment.
Qemu Native VM(virtio-blk) use -device virtio-blk-pci
Qemu colo follow https://wiki.qemu.org/Features/COLO
Thanks
Lee
Zhang Chen <zhangckid@gmail.com> 于2019年11月27日周三 上午11:15写道:
> Hi Lee,
>
> Can you introduce to me the detail test step about disk performance?
> I want to look into it when I have time.
>
> Thanks
> Zhang Chen
>
> On Wed, Nov 27, 2019 at 10:50 AM lee <1754542@bugs.launchpad.net> wrote:
> >
> > Hi Zhang Chen ,
> >
> > I try colo follow https://wiki.qemu.org/Features/COLO.
> > It work well. But disk performance slow.
> > Only host performance 10%.
> > Can virtio blk supported by current colo?
> > Or is there any other way to improve disk performance.
> >
> > Thanks
> > Zhang Chen
> >
> > --
> > You received this bug notification because you are subscribed to the bug
> > report.
> > https://bugs.launchpad.net/bugs/1754542
> >
> > Title:
> > colo: vm crash with segmentation fault
> >
> > Status in QEMU:
> > Fix Released
> >
> > 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 /usr/local/bin/qemu-system-x86_64 -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=primary-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 /usr/local/bin/qemu-system-x86_64 -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=secondary-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=secondary-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':
> 'secondary-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=secondary-disk0,node-name=nbd_client0'}}
> > { 'execute':'x-blockdev-change', 'arguments':{'parent':
> 'primary-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
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1754542
>
> Title:
> colo: vm crash with segmentation fault
>
> Status in QEMU:
> Fix Released
>
> 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 /usr/local/bin/qemu-system-x86_64 -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=primary-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 /usr/local/bin/qemu-system-x86_64 -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=secondary-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=secondary-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': 'secondary-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=secondary-disk0,node-name=nbd_client0'}}
> { 'execute':'x-blockdev-change', 'arguments':{'parent': 'primary-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
>
** Attachment added: "Qemu Host vs Qemu Native VM vs Qemu colo.xlsx"
https://bugs.launchpad.net/bugs/1754542/+attachment/5308083/+files/Qemu%20Host%20vs%20Qemu%20Native%20VM%20vs%20Qemu%20colo.xlsx
--
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 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 /usr/local/bin/qemu-system-x86_64 -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=primary-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 /usr/local/bin/qemu-system-x86_64 -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=secondary-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=secondary-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': 'secondary-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=secondary-disk0,node-name=nbd_client0'}}
{ 'execute':'x-blockdev-change', 'arguments':{'parent': 'primary-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
next prev parent reply other threads:[~2019-11-27 6:53 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-09 2:54 [Qemu-devel] [Bug 1754542] [NEW] colo: secondary vm crash when execute x-colo-lost-heartbeat 李穗恒
2018-03-09 3:08 ` [Qemu-devel] [Bug 1754542] " 李穗恒
2018-03-11 10:31 ` 李穗恒
2018-03-11 10:38 ` [Qemu-devel] [Bug 1754542] Re: colo: vm crash with segmentation fault 李穗恒
2018-03-12 0:39 ` 李穗恒
2018-03-12 0:58 ` 李穗恒
2018-03-17 20:14 ` [Qemu-devel] [Bug 1754542] [NEW] colo: secondary vm crash when execute x-colo-lost-heartbeat Zhang Chen
2018-03-17 20:16 ` Zhang Chen
2018-03-19 2:08 ` [Qemu-devel] [Bug 1754542] Re: colo: vm crash with segmentation fault 李穗恒
2018-03-21 6:04 ` Zhang Chen
2018-03-23 3:51 ` Li Zhijian
2018-03-23 8:34 ` Li Zhijian
2018-03-23 9:03 ` Zhang Chen
2018-03-20 9:18 ` 李穗恒
2018-03-20 9:19 ` 李穗恒
2018-03-22 7:31 ` 李穗恒
2018-03-22 7:39 ` 李穗恒
2018-06-03 16:28 ` Zhang Chen
2018-07-27 4:53 ` WANG Chao
2018-07-27 6:55 ` Zhang Chen
2018-07-27 10:35 ` WANG Chao
2018-08-07 11:53 ` Zhang Chen
2019-11-27 2:24 ` 李穗恒
2019-11-27 2:38 ` lee
2019-11-27 3:06 ` Zhang Chen
2019-11-27 6:35 ` lee [this message]
2019-11-27 2:41 ` lee
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAACkWBuALs=XdGhoi2KKSxUrkwqLmDxSeXeUhigLJp5A5m2DHA@mail.gmail.com' \
--to=1754542@bugs.launchpad.net \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).