- Virt - mailweb.openeuler.org

【Meeting Notice】Virt sig meeting Time: 2020-09-18 14:30-15:30
by Chenzhendong (alex) 18 Sep '20

18 Sep '20

Virt sig会议议程： 1、openEuler 20.09 虚拟化特性进展 alexchen 2、EulerRobot质量体系构建进展 kuhnchen 3、openEuler 虚拟化 20.03 SP1/21.03特性规划讨论 all -------- 原始邮件 -------- 发件人： Meeting Book <uMeeting(a)huawei.com<mailto:uMeeting@huawei.com>> 日期： 2020年9月18日周五 10:19 收件人： zdchenhn(a)163.com<mailto:zdchenhn@163.com> 主题：【Meeting Notice】Virt sig meeting Time: 2020-09-18 14:30-15:30 Topic Virt sig meeting Time 2020-09-18 14:30-15:30((UTC+08:00)Beijing) Join Conference Join (External) >><https://welink-meeting.zoom.us/j/386639496> Meeting ID 386 639 496 Convener 陈振东 Tips: Dial the access number to join conference<http://app.huawei.com/eshare/voiceMeetings> 注：仅支持部分国家和地区。( Only some countries and regions are supported.) 如果加入会议提示“会议已结束或会议号不存在”，请在官网下载最新版本入会。立即下载<https://zoom.us/download> If a message is displayed, indicating that the meeting has ended or the meeting ID does not exist, download the latest meeting client and try again.Download<https://zoom.us/download>

1 0

Re: openEuler guest with multi-numa cannot startup
by Ying Fang 17 Sep '20

17 Sep '20

On 9/17/2020 12:34 PM, Haibin Zhang wrote: > > >> On Sep 17, 2020, at 11:41 AM, Ying Fang <fangying1(a)huawei.com >> <mailto:fangying1@huawei.com>> wrote: >> >> >> >> On 8/21/2020 11:31 AM, Ying Fang via Virt wrote: >>> On 8/21/2020 11:23 AM, Haibin Zhang wrote: >>>> >>>> >>>>> On Aug 21, 2020, at 10:49 AM, Ying Fang <fangying1(a)huawei.com >>>>> <mailto:fangying1@huawei.com> <mailto:fangying1@huawei.com>> wrote: >>>>> >>>>> >>>>> >>>>> On 8/21/2020 10:21 AM, Haibin Zhang wrote: >>>>>>> On Aug 21, 2020, at 9:09 AM, Ying Fang <fangying1(a)huawei.com >>>>>>> <mailto:fangying1@huawei.com> >>>>>>> <mailto:fangying1@huawei.com><mailto:fangying1@huawei.com>> wrote: >>>>>>> >>>>>>> >>>>>>> >>>>>>> On 8/20/2020 6:23 PM, Haibin Zhang wrote: >>>>>>>>> On Aug 20, 2020, at 5:08 PM, Ying Fang <fangying1(a)huawei.com >>>>>>>>> <mailto:fangying1@huawei.com> <mailto:fangying1@huawei.com> >>>>>>>>> <mailto:fangying1@huawei.com>> wrote: >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> On 8/20/2020 3:44 PM, Haibin Zhang wrote: >>>>>>>>>> Hi, Ying Fang, >>>>>>>>>> I use qemu(https://gitee.com/src-openeuler/qemu.git) launch a >>>>>>>>>> openEuler guest, but it hung. >>>>>>>>>> Qcow2 is downloaded from >>>>>>>>>> https://repo.openeuler.org/openEuler-20.03-LTS/virtual_machine_img/aarch64/… >>>>>>>>>> Qemu command: >>>>>>>>>> qemu-system-aarch64 -name guest=12345,debug-threads=on >>>>>>>>>> -machine >>>>>>>>>> virt,accel=kvm,usb=off,dump-guest-core=off,gic-version=3 \ >>>>>>>>>> -cpu host -m 122880 -object iothread,id=iothread1 \ >>>>>>>>>> -object >>>>>>>>>> memory-backend-ram,id=ram-node0,size=64424509440,host-nodes=0,policy=preferred >>>>>>>>>> -numa node,nodeid=0,cpus=0-29,memdev=ram-node0 \ >>>>>>>>>> -object >>>>>>>>>> memory-backend-ram,id=ram-node1,size=64424509440,host-nodes=1,policy=preferred >>>>>>>>>> -numa node,nodeid=1,cpus=30-59,memdev=ram-node1 \ >>>>>>>> It works after getting rid of these two memory-backend-ram objects >>>>>>> I am wondering whether there is enough memory on each NUMA node >>>>>>> you specified in the command line on your host. You can use >>>>>>> numactl -H to check numa info of your host. >>>>>> I have specified policy=preferred not strict. >>>>>> I get some clues below: >>>>>> https://lore.kernel.org/lkml/1577088979-8545-1-git-send-email-prime.zeng@hi… >>>>>> It says numa confguration is conflict with cpu affinity specified >>>>>> by MPIDR >>>>> Yes, this may be the clue and I'm quite intrested in this issue. >>>>> >>>>> Since currently KVM does not support userspace mpdir configuration. >>>>> I am now doing some work to enable MPIDR emulation in KVM on aarch64. >>>> >>>> The “-smp x,sockets=n,cores=m” of qemu doesn’t work in aarch64 ? >>> It is partially supported, qemu has support for CPU topology >>> configuration. The topology infomation can be reported to GuestOS >>> via ACPI or fdt. However KVM does not support MPIDR emulation now, >>> which means guest can see the topology but MPIDR is different. >>> I'm now working on it to enable MPIDR emulation in KVM so that >>> the ACPI info can be coordinate with MPIDR. >>> Please refer to: >>> https://patchwork.ozlabs.org/project/qemu-devel/cover/20180704124923.32483-… >> >> The patch series related with this issue has been posted to upstream: >> https://patchwork.kernel.org/cover/11781339/ >> >> You can pick up and test it. > > Thanks, Ying Fang > > target/arm/kvm64: make MPIDR consistent with CPU Topology > target/arm/kvm32: make MPIDR consistent with CPU Topology > Above two patches may be duplicated with "arm: kvm: set MPIDR when we > can” from > https://patchwork.ozlabs.org/project/qemu-devel/patch/20170227173706.15210-… Yes, it may be. Let me have a look since I did not see it before. > >> >>>> >>>>> >>>>>>>>>> -smp 60,sockets=2,cores=30,threads=1 -bios >>>>> A 2(scokets) * 30(cores) * 1(threads) topology may confusing the >>>>> guest kernel. I'll test this situation later this week. >>>>> Please keep in touch with me. >>>>> >>>>>>>>>> /usr/share/AAVMF/AAVMF_CODE.fd \ >>>>>>>>>> -device >>>>>>>>>> pcie-root-port,port=0x8,chassis=1,id=pci.1,bus=pcie.0,multifunction=on,addr=0x1 >>>>>>>>>> \ >>>>>>>>>> -device >>>>>>>>>> pcie-root-port,port=0x9,chassis=2,id=pci.2,bus=pcie.0,addr=0x1.0x1 >>>>>>>>>> \ >>>>>>>>>> -drive >>>>>>>>>> file=/data/euler/euler.qcow2,format=qcow2,if=none,id=drive-virtio-disk0,cache=none >>>>>>>>>> \ >>>>>>>>>> -device >>>>>>>>>> virtio-blk-pci,scsi=off,bus=pci.1,addr=0x0,drive=drive-virtio-disk0,id=virtio-disk0,bootindex=1 >>>>>>>>>> \ >>>>>>>>>> -net none -serial telnet::9001,server,nowait -monitor stdio >>>>>>>>>> Guest startup logs: >>>>>>>>>> [ 3.769390] smp: Brought up 2 nodes, 60 CPUs >>>>>>>>>> [ 4.125100] SMP: Total of 60 processors activated. >>>>>>>>>> [ 4.126246] CPU features: detected: Privileged Access Never >>>>>>>>>> [ 4.127625] CPU features: detected: LSE atomic instructions >>>>>>>>>> [ 4.128969] CPU features: detected: User Access Override >>>>>>>>>> [ 4.130261] CPU features: detected: Data cache clean to >>>>>>>>>> Point of Persistence >>>>>>>>>> [ 4.131949] CPU features: detected: RAS Extension Support >>>>>>>>>> [ 4.133253] CPU features: detected: ARM64 MPAM Extension >>>>>>>>>> Support >>>>>>>>>> [ 4.134704] CPU features: detected: CRC32 instructions >>>>>>>>>> [ 4.184286] CPU: All CPU(s) started at EL1 >>>>>>>>>> [ 4.185891] alternatives: patching kernel code >>>>>>>>>> [ 64.308834] rcu: INFO: rcu_sched detected stalls on CPUs/tasks: >>>>>>>>>> [ 64.310827] rcu: (detected by 0, t=15002 jiffies, g=-719, q=0) >>>>>>>>>> [ 64.312260] rcu: All QSes seen, last rcu_sched kthread >>>>>>>>>> activity 15002 (4294908290-4294893288), >>>>>>>>>> jiffies_till_next_fqs=1, root ->qsmask 0x0 >>>>>>>>>> [ 64.315251] swapper/0 R running task 0 1 >>>>>>>>>> 0 0x0000002a >>>>>>>>>> [ 64.316930] Call trace: >>>>>>>>>> [ 64.317533] dump_backtrace+0x0/0x198 >>>>>>>>>> [ 64.318432] show_stack+0x24/0x30 >>>>>>>>>> [ 64.319248] sched_show_task+0x12c/0x160 >>>>>>>>>> [ 64.320206] rcu_check_callbacks+0x780/0x7a8 >>>>>>>>>> [ 64.321253] update_process_times+0x34/0x60 >>>>>>>>>> [ 64.322296] tick_periodic+0x48/0x100 >>>>>>>>>> [ 64.323193] tick_handle_periodic+0x38/0xd8 >>>>>>>>>> [ 64.324224] arch_timer_handler_virt+0x38/0x58 >>>>>>>>>> [ 64.325320] handle_percpu_devid_irq+0x90/0x248 >>>>>>>>>> [ 64.326419] generic_handle_irq+0x34/0x50 >>>>>>>>>> [ 64.327383] __handle_domain_irq+0x68/0xc0 >>>>>>>>>> [ 64.328367] gic_handle_irq+0x6c/0x170 >>>>>>>>>> [ 64.329275] el1_irq+0xb8/0x140 >>>>>>>>>> [ 64.330040] __bitmap_weight+0x48/0xa0 >>>>>>>>>> [ 64.330942] build_sched_domains+0xd58/0xf50 >>>>>>>>>> [ 64.331962] sched_init_domains+0xd4/0x108 >>>>>>>>>> [ 64.332950] sched_init_smp+0x3c/0x8c >>>>>>>>>> [ 64.333842] kernel_init_freeable+0x17c/0x34c >>>>>>>>>> [ 64.334891] kernel_init+0x18/0x118 >>>>>>>>>> [ 64.335735] ret_from_fork+0x10/0x18 >>>>>>>>> >>>>>>>>> You mean there is something wrong with the NUMA feature, right ? >>>>>>>>> >>>>>>>>> please try using the xml below and see if you can luanch your VM. >>>>>>>> No numa specified in below xml file. >>>>>>>>> >>>>>>>>> <domain type='kvm' id='17'> >>>>>>>>> <name>openeuler-test</name> >>>>>>>>> <memory unit='GiB'>32</memory> >>>>>>>>> <currentMemory unit='GiB'>32</currentMemory> >>>>>>>>> <memtune> >>>>>>>>> <hard_limit unit='GiB'>32</hard_limit> >>>>>>>>> </memtune> >>>>>>>>> <vcpu placement='static' cpuset='7-10'>60</vcpu> >>>>>>>>> <iothreads>5</iothreads> >>>>>>>>> <cputune> >>>>>>>>> <emulatorpin cpuset='7-10'/> >>>>>>>>> </cputune> >>>>>>>>> <resource> >>>>>>>>> <partition>/machine</partition> >>>>>>>>> </resource> >>>>>>>>> <os> >>>>>>>>> <type arch='aarch64' machine='virt-4.1'>hvm</type> >>>>>>>>> <loader readonly='yes' >>>>>>>>> type='pflash'>/usr/share/edk2/aarch64/QEMU_EFI-pflash.raw</loader> >>>>>>>>> <nvram>/var/lib/libvirt/qemu/nvram/fangying_openeuler_VARS.fd</nvram> >>>>>>>>> <boot dev='hd'/> >>>>>>>>> <boot dev='cdrom'/> >>>>>>>>> </os> >>>>>>>>> <features> >>>>>>>>> <gic version='3'/> >>>>>>>>> <acpi/> >>>>>>>>> </features> >>>>>>>>> <cpu mode='host-passthrough' check='none'> >>>>>>>>> <topology sockets='2' cores='30' threads='1'/> >>>>>>>>> </cpu> >>>>>>>>> <clock offset='utc'> >>>>>>>>> </clock> >>>>>>>>> <on_poweroff>destroy</on_poweroff> >>>>>>>>> <on_reboot>restart</on_reboot> >>>>>>>>> <on_crash>restart</on_crash> >>>>>>>>> <devices> >>>>>>>>> <emulator>/usr/bin/qemu-kvm</emulator> >>>>>>>>> <disk type='file' device='disk'> >>>>>>>>> <driver name='qemu' type='qcow2' cache='none' io='native'/> >>>>>>>>> <source >>>>>>>>> file='/root/fangying/vm/openEuler-20.03-LTS.aarch64.qcow2'/> >>>>>>>>> <backingStore/> >>>>>>>>> <target dev='sda' bus='scsi'/> >>>>>>>>> <alias name='scsi0-0-0-0'/> >>>>>>>>> <address type='drive' controller='0' bus='0' target='0' >>>>>>>>> unit='0'/> >>>>>>>>> </disk> >>>>>>>>> <controller type='usb' index='0' model='ehci'> >>>>>>>>> <alias name='usb'/> >>>>>>>>> <address type='pci' domain='0x0000' bus='0x03' slot='0x01' >>>>>>>>> function='0x0'/> >>>>>>>>> </controller> >>>>>>>>> <controller type='scsi' index='0' model='virtio-scsi'> >>>>>>>>> <alias name='scsi0'/> >>>>>>>>> <address type='pci' domain='0x0000' bus='0x04' slot='0x00' >>>>>>>>> function='0x0'/> >>>>>>>>> </controller> >>>>>>>>> <controller type='pci' index='0' model='pcie-root'> >>>>>>>>> <alias name='pcie.0'/> >>>>>>>>> </controller> >>>>>>>>> <controller type='pci' index='1' model='pcie-root-port'> >>>>>>>>> <model name='pcie-root-port'/> >>>>>>>>> <target chassis='1' port='0x8'/> >>>>>>>>> <alias name='pci.1'/> >>>>>>>>> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' >>>>>>>>> function='0x0' multifunction='on'/> >>>>>>>>> </controller> >>>>>>>>> <controller type='pci' index='2' model='pcie-root-port'> >>>>>>>>> <model name='pcie-root-port'/> >>>>>>>>> <target chassis='2' port='0x9'/> >>>>>>>>> <alias name='pci.2'/> >>>>>>>>> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' >>>>>>>>> function='0x1'/> >>>>>>>>> </controller> >>>>>>>>> <controller type='pci' index='3' model='pcie-to-pci-bridge'> >>>>>>>>> <model name='pcie-pci-bridge'/> >>>>>>>>> <alias name='pci.3'/> >>>>>>>>> <address type='pci' domain='0x0000' bus='0x01' slot='0x00' >>>>>>>>> function='0x0'/> >>>>>>>>> </controller> >>>>>>>>> <controller type='pci' index='4' model='pcie-root-port'> >>>>>>>>> <model name='pcie-root-port'/> >>>>>>>>> <target chassis='4' port='0xa'/> >>>>>>>>> <alias name='pci.4'/> >>>>>>>>> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' >>>>>>>>> function='0x2'/> >>>>>>>>> </controller> >>>>>>>>> <controller type='pci' index='5' model='pcie-root-port'> >>>>>>>>> <model name='pcie-root-port'/> >>>>>>>>> <target chassis='5' port='0xb'/> >>>>>>>>> <alias name='pci.5'/> >>>>>>>>> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' >>>>>>>>> function='0x3'/> >>>>>>>>> </controller> >>>>>>>>> <controller type='pci' index='6' model='pcie-root-port'> >>>>>>>>> <model name='pcie-root-port'/> >>>>>>>>> <target chassis='6' port='0xc'/> >>>>>>>>> <alias name='pci.6'/> >>>>>>>>> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' >>>>>>>>> function='0x4'/> >>>>>>>>> </controller> >>>>>>>>> <controller type='pci' index='7' model='pcie-root-port'> >>>>>>>>> <model name='pcie-root-port'/> >>>>>>>>> <target chassis='7' port='0xd'/> >>>>>>>>> <alias name='pci.7'/> >>>>>>>>> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' >>>>>>>>> function='0x5'/> >>>>>>>>> </controller> >>>>>>>>> <controller type='pci' index='8' model='pcie-root-port'> >>>>>>>>> <model name='pcie-root-port'/> >>>>>>>>> <target chassis='8' port='0xe'/> >>>>>>>>> <alias name='pci.8'/> >>>>>>>>> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' >>>>>>>>> function='0x6'/> >>>>>>>>> </controller> >>>>>>>>> <controller type='pci' index='9' model='pcie-root-port'> >>>>>>>>> <model name='pcie-root-port'/> >>>>>>>>> <target chassis='9' port='0xf'/> >>>>>>>>> <alias name='pci.9'/> >>>>>>>>> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' >>>>>>>>> function='0x7'/> >>>>>>>>> </controller> >>>>>>>>> <controller type='pci' index='10' model='pcie-root-port'> >>>>>>>>> <model name='pcie-root-port'/> >>>>>>>>> <target chassis='10' port='0x10'/> >>>>>>>>> <alias name='pci.10'/> >>>>>>>>> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' >>>>>>>>> function='0x0' multifunction='on'/> >>>>>>>>> </controller> >>>>>>>>> <controller type='pci' index='11' model='pcie-root-port'> >>>>>>>>> <model name='pcie-root-port'/> >>>>>>>>> <target chassis='11' port='0x11'/> >>>>>>>>> <alias name='pci.11'/> >>>>>>>>> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' >>>>>>>>> function='0x1'/> >>>>>>>>> </controller> >>>>>>>>> <controller type='pci' index='12' model='pcie-root-port'> >>>>>>>>> <model name='pcie-root-port'/> >>>>>>>>> <target chassis='12' port='0x12'/> >>>>>>>>> <alias name='pci.12'/> >>>>>>>>> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' >>>>>>>>> function='0x2'/> >>>>>>>>> </controller> >>>>>>>>> <controller type='pci' index='13' model='pcie-root-port'> >>>>>>>>> <model name='pcie-root-port'/> >>>>>>>>> <target chassis='13' port='0x13'/> >>>>>>>>> <alias name='pci.13'/> >>>>>>>>> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' >>>>>>>>> function='0x3'/> >>>>>>>>> </controller> >>>>>>>>> <controller type='pci' index='14' model='pcie-root-port'> >>>>>>>>> <model name='pcie-root-port'/> >>>>>>>>> <target chassis='14' port='0x14'/> >>>>>>>>> <alias name='pci.14'/> >>>>>>>>> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' >>>>>>>>> function='0x4'/> >>>>>>>>> </controller> >>>>>>>>> <controller type='pci' index='15' model='pcie-root-port'> >>>>>>>>> <model name='pcie-root-port'/> >>>>>>>>> <target chassis='15' port='0x15'/> >>>>>>>>> <alias name='pci.15'/> >>>>>>>>> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' >>>>>>>>> function='0x5'/> >>>>>>>>> </controller> >>>>>>>>> <controller type='pci' index='16' model='pcie-root-port'> >>>>>>>>> <model name='pcie-root-port'/> >>>>>>>>> <target chassis='16' port='0x16'/> >>>>>>>>> <alias name='pci.16'/> >>>>>>>>> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' >>>>>>>>> function='0x6'/> >>>>>>>>> </controller> >>>>>>>>> <controller type='pci' index='17' model='pcie-root-port'> >>>>>>>>> <model name='pcie-root-port'/> >>>>>>>>> <target chassis='17' port='0x17'/> >>>>>>>>> <alias name='pci.17'/> >>>>>>>>> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' >>>>>>>>> function='0x7'/> >>>>>>>>> </controller> >>>>>>>>> <controller type='pci' index='18' model='pcie-root-port'> >>>>>>>>> <model name='pcie-root-port'/> >>>>>>>>> <target chassis='18' port='0x18'/> >>>>>>>>> <alias name='pci.18'/> >>>>>>>>> <address type='pci' domain='0x0000' bus='0x00' slot='0x03' >>>>>>>>> function='0x0' multifunction='on'/> >>>>>>>>> </controller> >>>>>>>>> <controller type='pci' index='19' model='pcie-root-port'> >>>>>>>>> <model name='pcie-root-port'/> >>>>>>>>> <target chassis='19' port='0x19'/> >>>>>>>>> <alias name='pci.19'/> >>>>>>>>> <address type='pci' domain='0x0000' bus='0x00' slot='0x03' >>>>>>>>> function='0x1'/> >>>>>>>>> </controller> >>>>>>>>> <controller type='pci' index='20' model='pcie-root-port'> >>>>>>>>> <model name='pcie-root-port'/> >>>>>>>>> <target chassis='20' port='0x1a'/> >>>>>>>>> <alias name='pci.20'/> >>>>>>>>> <address type='pci' domain='0x0000' bus='0x00' slot='0x03' >>>>>>>>> function='0x2'/> >>>>>>>>> </controller> >>>>>>>>> <controller type='pci' index='21' model='pcie-root-port'> >>>>>>>>> <model name='pcie-root-port'/> >>>>>>>>> <target chassis='21' port='0x1b'/> >>>>>>>>> <alias name='pci.21'/> >>>>>>>>> <address type='pci' domain='0x0000' bus='0x00' slot='0x03' >>>>>>>>> function='0x3'/> >>>>>>>>> </controller> >>>>>>>>> <controller type='pci' index='22' model='pcie-root-port'> >>>>>>>>> <model name='pcie-root-port'/> >>>>>>>>> <target chassis='22' port='0x1c'/> >>>>>>>>> <alias name='pci.22'/> >>>>>>>>> <address type='pci' domain='0x0000' bus='0x00' slot='0x03' >>>>>>>>> function='0x4'/> >>>>>>>>> </controller> >>>>>>>>> <controller type='pci' index='23' model='pcie-root-port'> >>>>>>>>> <model name='pcie-root-port'/> >>>>>>>>> <target chassis='23' port='0x1d'/> >>>>>>>>> <alias name='pci.23'/> >>>>>>>>> <address type='pci' domain='0x0000' bus='0x00' slot='0x03' >>>>>>>>> function='0x5'/> >>>>>>>>> </controller> >>>>>>>>> <controller type='pci' index='24' model='pcie-root-port'> >>>>>>>>> <model name='pcie-root-port'/> >>>>>>>>> <target chassis='24' port='0x1e'/> >>>>>>>>> <alias name='pci.24'/> >>>>>>>>> <address type='pci' domain='0x0000' bus='0x00' slot='0x03' >>>>>>>>> function='0x6'/> >>>>>>>>> </controller> >>>>>>>>> <controller type='pci' index='25' model='pcie-root-port'> >>>>>>>>> <model name='pcie-root-port'/> >>>>>>>>> <target chassis='25' port='0x1f'/> >>>>>>>>> <alias name='pci.25'/> >>>>>>>>> <address type='pci' domain='0x0000' bus='0x00' slot='0x03' >>>>>>>>> function='0x7'/> >>>>>>>>> </controller> >>>>>>>>> <controller type='pci' index='26' model='pcie-root-port'> >>>>>>>>> <model name='pcie-root-port'/> >>>>>>>>> <target chassis='26' port='0x20'/> >>>>>>>>> <alias name='pci.26'/> >>>>>>>>> <address type='pci' domain='0x0000' bus='0x00' slot='0x04' >>>>>>>>> function='0x0' multifunction='on'/> >>>>>>>>> </controller> >>>>>>>>> <controller type='pci' index='27' model='pcie-root-port'> >>>>>>>>> <model name='pcie-root-port'/> >>>>>>>>> <target chassis='27' port='0x21'/> >>>>>>>>> <alias name='pci.27'/> >>>>>>>>> <address type='pci' domain='0x0000' bus='0x00' slot='0x04' >>>>>>>>> function='0x1'/> >>>>>>>>> </controller> >>>>>>>>> <controller type='pci' index='28' model='pcie-root-port'> >>>>>>>>> <model name='pcie-root-port'/> >>>>>>>>> <target chassis='28' port='0x22'/> >>>>>>>>> <alias name='pci.28'/> >>>>>>>>> <address type='pci' domain='0x0000' bus='0x00' slot='0x04' >>>>>>>>> function='0x2'/> >>>>>>>>> </controller> >>>>>>>>> <controller type='pci' index='29' model='pcie-root-port'> >>>>>>>>> <model name='pcie-root-port'/> >>>>>>>>> <target chassis='29' port='0x23'/> >>>>>>>>> <alias name='pci.29'/> >>>>>>>>> <address type='pci' domain='0x0000' bus='0x00' slot='0x04' >>>>>>>>> function='0x3'/> >>>>>>>>> </controller> >>>>>>>>> <controller type='pci' index='30' model='pcie-root-port'> >>>>>>>>> <model name='pcie-root-port'/> >>>>>>>>> <target chassis='30' port='0x24'/> >>>>>>>>> <alias name='pci.30'/> >>>>>>>>> <address type='pci' domain='0x0000' bus='0x00' slot='0x04' >>>>>>>>> function='0x4'/> >>>>>>>>> </controller> >>>>>>>>> <controller type='virtio-serial' index='0'> >>>>>>>>> <alias name='virtio-serial0'/> >>>>>>>>> <address type='pci' domain='0x0000' bus='0x03' slot='0x02' >>>>>>>>> function='0x0'/> >>>>>>>>> </controller> >>>>>>>>> <serial type='pty'> >>>>>>>>> <source path='/dev/pts/2'/> >>>>>>>>> <target port='0'/> >>>>>>>>> <alias name='serial0'/> >>>>>>>>> </serial> >>>>>>>>> <console type='pty' tty='/dev/pts/2'> >>>>>>>>> <source path='/dev/pts/2'/> >>>>>>>>> <target type='serial' port='0'/> >>>>>>>>> <alias name='serial0'/> >>>>>>>>> </console> >>>>>>>>> <channel type='unix'> >>>>>>>>> <source mode='bind' >>>>>>>>> path='/var/run/libvirt/qemu/fangying-test.extend'/> >>>>>>>>> <target type='virtio' name='org.qemu.guest_agent.1' >>>>>>>>> state='connected'/> >>>>>>>>> <alias name='channel0'/> >>>>>>>>> <address type='virtio-serial' controller='0' bus='0' >>>>>>>>> port='1'/> >>>>>>>>> </channel> >>>>>>>>> <channel type='unix'> >>>>>>>>> <source mode='bind' >>>>>>>>> path='/var/run/libvirt/qemu/fangying-test.agent'/> >>>>>>>>> <target type='virtio' name='org.qemu.guest_agent.0' >>>>>>>>> state='connected'/> >>>>>>>>> <alias name='channel1'/> >>>>>>>>> <address type='virtio-serial' controller='0' bus='0' >>>>>>>>> port='2'/> >>>>>>>>> </channel> >>>>>>>>> <channel type='unix'> >>>>>>>>> <source mode='bind' >>>>>>>>> path='/var/run/libvirt/qemu/fangying-test.hostd'/> >>>>>>>>> <target type='virtio' name='org.qemu.guest_agent.2' >>>>>>>>> state='connected'/> >>>>>>>>> <alias name='channel2'/> >>>>>>>>> <address type='virtio-serial' controller='0' bus='0' >>>>>>>>> port='3'/> >>>>>>>>> </channel> >>>>>>>>> <channel type='unix'> >>>>>>>>> <source mode='bind' >>>>>>>>> path='/var/run/libvirt/qemu/fangying-test.upgraded'/> >>>>>>>>> <target type='virtio' name='org.qemu.guest_agent.3' >>>>>>>>> state='connected'/> >>>>>>>>> <alias name='channel3'/> >>>>>>>>> <address type='virtio-serial' controller='0' bus='0' >>>>>>>>> port='4'/> >>>>>>>>> </channel> >>>>>>>>> <input type='tablet' bus='usb'> >>>>>>>>> <alias name='input0'/> >>>>>>>>> <address type='usb' bus='0' port='1'/> >>>>>>>>> </input> >>>>>>>>> <input type='keyboard' bus='usb'> >>>>>>>>> <alias name='input1'/> >>>>>>>>> <address type='usb' bus='0' port='2'/> >>>>>>>>> </input> >>>>>>>>> <graphics type='vnc' port='5903' autoport='yes' >>>>>>>>> listen='0.0.0.0'> >>>>>>>>> <listen type='address' address='0.0.0.0'/> >>>>>>>>> </graphics> >>>>>>>>> <video> >>>>>>>>> <model type='virtio' heads='1' primary='yes'/> >>>>>>>>> <alias name='video0'/> >>>>>>>>> <address type='pci' domain='0x0000' bus='0x03' slot='0x04' >>>>>>>>> function='0x0'/> >>>>>>>>> </video> >>>>>>>>> <memballoon model='virtio'> >>>>>>>>> <alias name='balloon0'/> >>>>>>>>> <address type='pci' domain='0x0000' bus='0x03' slot='0x03' >>>>>>>>> function='0x0'/> >>>>>>>>> </memballoon> >>>>>>>>> </devices> >>>>>>>>> <seclabel type='dynamic' model='dac' relabel='yes'> >>>>>>>>> <label>+0:+0</label> >>>>>>>>> <imagelabel>+0:+0</imagelabel> >>>>>>>>> </seclabel> >>>>>>>>> </domain> >>>>>>>>> >>>>>>>>> I will test your cmdline way later to see if it can be reproduced. >>>>>>>>> >>>>>>>>> Thanks. >>>>>>>>> Ying. >>>>>>>>> >>>>>>>> . >>>> >>> _______________________________________________ >>> Virt mailing list --virt(a)openeuler.org <mailto:virt@openeuler.org> >>> To unsubscribe send an email tovirt-leave(a)openeuler.org >>> <mailto:virt-leave@openeuler.org> >

1 0

Re: Kunpeng920 virtualization performance
by Ying Fang 17 Sep '20

17 Sep '20

On 7/2/2020 3:18 PM, Haibin Zhang wrote: > Hi, Ying Fang. > Hi Haibin, Thanks for report this issue for us. We will verify and response to you later. > I use qemu create a VM (96 cores and 360g ram) on my kunpeng 920-4826 server, then do unixbench tests. > The performance of pipe-based context switching decreases severely, which shows below: > > Guest# ./context1 60 > COUNT|4779535|1|lps > COUNT|4779536|1|lps > > Host# ./context1 60 > COUNT|13990745|1|lps > COUNT|13990746|1|lps > Could you provide more details about your OS and virtualization software version information for us? > As you know, pipe-based context switching measures the number of times two processes can exchange an > increasing integer through a pipe in a duration (like 60 seconds). Times of guest is only 34% as that > of host. Attachment is the context1.c from unixbench. It looks simple, just spawn a child process with > which it carries on a bi-directional pipe conversation. Yes, we had knowledge about this context test now. Thanks. > > Guest# taskset -c 20 ./context1 60 > COUNT|18059443|1|lps > COUNT|18059443|1|lps > > Host# taskset -c 20 ./context1 60 > COUNT|17881974|1|lps > COUNT|17881975|1|lps > > Use taskset to set cpu affinity, which makes results better. > > Can you help me fix this issue? Maybe WFE/WFI traps lead the performance cost? Is there PLE(Pause Loop Exit) feature on Kunpeng? > We had some performance tuning techniques in the openEuler OS. And Xie XiangYou is the expert on this area, maybe he could help you with it. Moreover, you can drop us an issue on gitee via: https://gitee.com/src-openeuler/qemu >

2 20

vmtop文档推送openeuler
by chenjiajun 14 Sep '20

14 Sep '20

1 0

openeuler开源代码回合
by Peng Liang 09 Sep '20

09 Sep '20

Patch： block-qcow2-do-free-crypto_opts-in-qcow2_close.patch qemu-img-free-memory-before-re-assign.patch block-qcow2-threads-fix-qcow2_decompress.patch block-Avoid-memleak-on-qcow2-image-info-failure.patch block-bdrv_set_backing_bs-fix-use-after-free.patch hmp-vnc-Fix-info-vnc-list-leak.patch migration-colo-fix-use-after-free-of-local_err.patch migration-ram-fix-use-after-free-of-local_err.patch block-mirror-fix-use-after-free-of-local_err.patch block-fix-bdrv_root_attach_child-forget-to-unref-chi.patch virtio-serial-bus-Plug-memory-leak-on-realize-error-.patch virtio-blk-delete-vqs-on-the-error-path-in-realize.patch fix-vhost_user_blk_watch-crash.patch vhost-user-blk-delay-vhost_user_blk_disconnect.patch Changelog： - block/qcow2: do free crypto_opts in qcow2_close() - qemu-img: free memory before re-assign - block/qcow2-threads: fix qcow2_decompress - block: Avoid memleak on qcow2 image info failure - block: bdrv_set_backing_bs: fix use-after-free - hmp/vnc: Fix info vnc list leak - migration/colo: fix use after free of local_err - migration/ram: fix use after free of local_err - block/mirror: fix use after free of local_err - block: fix bdrv_root_attach_child forget to unref child_bs - virtio-serial-bus: Plug memory leak on realize() error paths - virtio-blk: delete vqs on the error path in realize() - fix vhost_user_blk_watch crash - vhost-user-blk: delay vhost_user_blk_disconnect

1 0

openeuler开源bugfix回合
by chenjiajun 09 Sep '20

09 Sep '20

1 0

CPU feature忽略evtstrm和cpuid
by Peng Liang 08 Sep '20

08 Sep '20

1 0

Virt sig会议议程纪要0904//RE: 【Meeting Notice】Virt sig meeting Time: 2020-09-04 14:30-15:30
by Chenzhendong (alex) 07 Sep '20

07 Sep '20

Virt sig会议议程纪要： 1、openEuler 20.09虚拟化特性代码已经合入，正在进行稳定性和可靠性等测试。 a) vcpu hotplug/mem hotplug/HPRE加速三个特性已经测试完成。 b) 虚拟机可信启动/安全启动/PMU NMI-Watchdog/双层调度等特性正在开展测试中; c) VMtop、ARM虚拟机支持超线程、ARM虚拟机cpu feature支持Custom三个特性尚未开展测试，正在分析及测试设计； 2、EulerRobot质量体系构建进展： a) EulerRobot已经开源，已有部分开发者参与，希望后续有更多开发者参与，共同完善和优化openEuler虚拟化质量体系。 b) crystal-ci当前存在物理机部署后卡死无法使用情况，crystal-ci团队解决中，等解决完后再进行对接。 c) openEuler下虚拟化qemu/libvirt等仓库，代码门禁已经OK，正在实现让qemu/libvirt仓库代码合入后自动化生成Patch同步到src-openEuler中便于版本rpm制作，后续代码提交将切换至openeuelr仓库。 3、openEuler 支持riscv虚拟化的进展如下，后续主要进行bugfix。 a) Qemu支持RISC-V架构的KVM； b) 支持RISC-V架构虚拟机热迁移； c) 支持vhost的ioeventfd方案； From: Chenzhendong (alex) via Virt [mailto:virt@openeuler.org] Sent: Friday, September 4, 2020 10:19 AM To: virt(a)openeuler.org; dev(a)openeuler.org Cc: Zhangxiaofeng (F) <victor.zhangxiaofeng(a)huawei.com> Subject: [Virt] 【Meeting Notice】Virt sig meeting Time: 2020-09-04 14:30-15:30 Virt sig会议议程： 1、openEuler 20.09 虚拟化特性进展 alexchen 2、EulerRobot质量体系构建进展 kuhnchen 3、openEuler RISC-V虚拟化支持进展 Jiangyifei ------- 原始邮件 -------- 发件人： Meeting Book <uMeeting(a)huawei.com<mailto:uMeeting@huawei.com>> 日期： 2020年9月4日周五 10:03 收件人： zdchenhn(a)163.com<mailto:zdchenhn@163.com> 主题：【Meeting Notice】Virt sig meeting Time: 2020-09-04 14:30-15:30 Topic Virt sig meeting Time 2020-09-04 14:30-15:30((UTC+08:00)Beijing) Join Conference Join (External) >><https://welink-meeting.zoom.us/j/258690350> Meeting ID 258 690 350 Convener 陈振东 Tips: Dial the access number to join conference<http://app.huawei.com/eshare/voiceMeetings> 注：仅支持部分国家和地区。( Only some countries and regions are supported.) 如果加入会议提示“会议已结束或会议号不存在”，请在官网下载最新版本入会。立即下载<https://zoom.us/download> If a message is displayed, indicating that the meeting has ended or the meeting ID does not exist, download the latest meeting client and try again.Download<https://zoom.us/download>

1 0

【Meeting Notice】Virt sig meeting Time: 2020-09-04 14:30-15:30
by Chenzhendong (alex) 04 Sep '20

04 Sep '20

Virt sig会议议程： 1、openEuler 20.09 虚拟化特性进展 alexchen 2、EulerRobot质量体系构建进展 kuhnchen 3、openEuler RISC-V虚拟化支持进展 Jiangyifei ------- 原始邮件 -------- 发件人： Meeting Book <uMeeting(a)huawei.com<mailto:uMeeting@huawei.com>> 日期： 2020年9月4日周五 10:03 收件人： zdchenhn(a)163.com<mailto:zdchenhn@163.com> 主题：【Meeting Notice】Virt sig meeting Time: 2020-09-04 14:30-15:30 Topic Virt sig meeting Time 2020-09-04 14:30-15:30((UTC+08:00)Beijing) Join Conference Join (External) >><https://welink-meeting.zoom.us/j/258690350> Meeting ID 258 690 350 Convener 陈振东 Tips: Dial the access number to join conference<http://app.huawei.com/eshare/voiceMeetings> 注：仅支持部分国家和地区。( Only some countries and regions are supported.) 如果加入会议提示“会议已结束或会议号不存在”，请在官网下载最新版本入会。立即下载<https://zoom.us/download> If a message is displayed, indicating that the meeting has ended or the meeting ID does not exist, download the latest meeting client and try again.Download<https://zoom.us/download>

1 0

Re: hugepages leads VM startup secondary cpu failure
by Ying Fang 04 Sep '20

04 Sep '20

On 9/3/2020 9:33 PM, Haibin Zhang wrote: > Hi, YingFang. > > I configure 4K PAGE_SIZE in order to use 1G hugepage in host. But VM cannot bring up secondary CPU > > Start VM using follow command: > qemu-system-aarch64 -name guest=12345,debug-threads=on \ > -machine virt,accel=kvm,usb=off,dump-guest-core=off,gic-version=3 \ > -cpu host \ > -m 122880 \ > -object iothread,id=iothread1 \ > -object memory-backend-file,id=ram-node0,prealloc=yes,mem-path=/dev/hugepages,share=yes,size=64424509440,host-nodes=0,policy=preferred \ > -numa node,nodeid=0,cpus=0-29,memdev=ram-node0 \ > -object memory-backend-file,id=ram-node1,prealloc=yes,mem-path=/dev/hugepages,share=yes,size=64424509440,host-nodes=1,policy=preferred \ > -numa node,nodeid=1,cpus=30-59,memdev=ram-node1 \ > -smp sockets=2,cores=30,threads=1 \ > -bios /usr/share/AAVMF/AAVMF_CODE.fd \ > -drive file=/data/haibin/centos8.qcow2,format=qcow2,if=none,id=drive-virtio-disk0,cache=none \ > -device virtio-blk-pci,scsi=off,drive=drive-virtio-disk0,id=virtio-disk0,bootindex=1 \ > -net none -serial telnet::9001,server,nowait -monitor stdio > Thanks for your reporting, I will CC Zeyu Jin to lookup into it. > VM kernel logs: > [ 0.010708] Mountpoint-cache hash table entries: 65536 (order: 3, 524288 bytes) > [ 0.012517] ASID allocator initialised with 32768 entries > [ 0.013105] rcu: Hierarchical SRCU implementation. > [ 0.013843] Platform MSI: ITS@0x8080000 domain created > [ 0.014375] PCI/MSI: ITS@0x8080000 domain created > [ 0.014850] Remapping and enabling EFI services. > [ 0.015946] smp: Bringing up secondary CPUs ... > [ 1.039238] CPU1: failed to come online > [ 1.039698] CPU1: failed in unknown state : 0x0 > [ 1.051285] Detected VIPT I-cache on CPU2 > [ 1.051303] GICv3: CPU2: found redistributor 2 region 0:0x00000000080e0000 > [ 1.051520] GICv3: CPU2: using allocated LPI pending table @0x00000003c06a0000 > [ 1.051545] CPU2: Booted secondary processor 0x0000000001 [0x481fd010] > [ 2.079879] CPU3: failed to come online > [ 2.082736] CPU3: failed in unknown state : 0x0 > [ 2.085620] Detected VIPT I-cache on CPU4 > [ 2.085638] GICv3: CPU4: found redistributor 4 region 0:0x0000000008120000 > [ 2.085785] GICv3: CPU4: using allocated LPI pending table @0x00000003c06c0000 > [ 2.085808] CPU4: Booted secondary processor 0x0000000002 [0x481fd010] > [ 3.120358] Detected VIPT I-cache on CPU5 > [ 3.120379] GICv3: CPU5: found redistributor 5 region 0:0x0000000008140000 > [ 3.120607] GICv3: CPU5: using allocated LPI pending table @0x00000003c06d0000 > [ 3.120619] CPU5: failed to come online > [ 3.120632] CPU5: Booted secondary processor 0x0000000003 [0x481fd010] > [ 3.121069] ------------[ cut here ]------------ > [ 3.126345] kernel BUG at kernel/irq_work.c:147! > [ 3.126797] Internal error: Oops - BUG: 0 [#1] SMP > [ 3.127268] Modules linked in: > [ 3.127568] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 4.18.0-193.14.2.el8_2.aarch64 #1 > [ 3.128345] pstate: a0000005 (NzCv daif -PAN -UAO) > [ 3.128818] pc : irq_work_run_list+0xa8/0xb8 > [ 3.129239] lr : irq_work_run+0x24/0x48 > [ 3.129615] sp : ffff000012aefc40 > [ 3.129940] x29: ffff000012aefc40 x28: 0000000000000000 > [ 3.130458] x27: 0000000000000000 x26: 0000000000000000 > [ 3.131040] x25: 00008003ac000000 x24: ffff8003bd202130 > [ 3.131592] x23: 0000000000000000 x22: 0000000000000000 > [ 3.132119] x21: 0000000000000000 x20: ffff00001128e4c0 > [ 3.132677] x19: ffff00001128a400 x18: 0000000000000010 > [ 3.133247] x17: 0000000000000000 x16: ffff80038237ba00 > [ 3.133816] x15: ffffffffffffffff x14: ffff0000115d3708 > [ 3.134391] x13: ffff000092aef9a7 x12: ffff000012aef9b0 > [ 3.134991] x11: ffff00001160f000 x10: ffff000012aef930 > [ 3.135567] x9 : 00000000ffffffd0 x8 : ffff0000105dab10 > [ 3.136128] x7 : 000000000000000d x6 : ffff000011fc696c > [ 3.136685] x5 : 0000000000000015 x4 : 0000000000000000 > [ 3.137258] x3 : ffff8003bcf6e4c0 x2 : 0000000000000000 > [ 3.137825] x1 : 0000000000000000 x0 : ffff8003bcf6a400 > [ 3.138405] Process swapper/0 (pid: 1, stack limit = 0x(____ptrval____)) > [ 3.139096] Call trace: > [ 3.139364] irq_work_run_list+0xa8/0xb8 > [ 3.139773] irq_work_run+0x24/0x48 > [ 3.140180] flush_smp_call_function_queue+0xa4/0x150 > [ 3.140714] smpcfd_dying_cpu+0x18/0x28 > [ 3.141134] cpuhp_invoke_callback+0xa8/0x618 > [ 3.141621] _cpu_up+0x1c0/0x1d0 > [ 3.142013] do_cpu_up+0x7c/0xb8 > [ 3.142377] cpu_up+0x24/0x30 > [ 3.142717] smp_init+0xac/0x120 > [ 3.143089] kernel_init_freeable+0x168/0x314 > [ 3.143559] kernel_init+0x18/0x10c > [ 3.143942] ret_from_fork+0x10/0x18 > [ 3.144336] Code: a8c37bfd d65f03c0 a90153f3 a9025bf5 (d4210000) > [ 3.145028] ---[ end trace 392329bbeab599c5 ]--- > [ 3.145548] Kernel panic - not syncing: Fatal exception > [ 3.146149] SMP: stopping secondary CPUs > [ 4.183106] SMP: failed to stop secondary CPUs 0,2,5 > [ 4.183677] ---[ end Kernel panic - not syncing: Fatal exception ]---. >

1 0

2024

2023

2022

2021

2020

Virt