January 2019 - Starlingx-discuss

[Starlingx-discuss] CFP Open Until January 23, Open Infrastructure Summit in Denver
by Claire Massey 22 Jan '19

22 Jan '19

Hi everyone, FYI - the CFP is now open for the first Open Infrastructure Summit <https://www.openstack.org/summit/denver-2019/> (formerly the OpenStack Summit) which will be held in Denver, Colorado April 29 - May 1, 2019. Wednesday, *January 23* is the deadline to Submit presentations <https://www.openstack.org/summit/denver-2019/call-for-presentations>. The Open Infrastructure Summit is organized by OSF and designed to be a place where open source infrastructure communities can come together and collaborate in the open. StarlingX will have a large and prominent presence at the event so please submit talks to the CFP and plan to attend! SUBMIT YOUR PRESENTATION <https://www.openstack.org/summit/denver-2019/call-for-presentations> Important info: Based on previous Program Committee and attendee feedback, we have added / updated three Tracks: Security, Getting Started, and Open Development (previously Open Source Community). You can find the Track descriptions here <https://www.openstack.org/summit/denver-2019/summit-categories>. All of the OSF pilot projects —including Airship, Kata Containers, StarlingX and Zuul — will be front and center alongside other open source communities like Ansible, Cloud Foundry, Docker, Kubernetes, and many more. The Open Infrastructure Summit (formerly the OpenStack Summit), has evolved to recognize our diverse audience, and to signal to the market that the event is relevant for all IT infrastructure decision makers. If you’re interested in influencing the Summit content, apply to be a Programming Committee member <https://openstackfoundation.formstack.com/forms/openstackdenver2019_program…>*, where you can also find a full list of time requirements and expectations. Nominations will close on January 4, 2019. The content submission process for the Forum and Project Teams Gathering will be managed separately in the upcoming months. *OSF Staff will serve as the Programming Committee for the Getting Started Track. Denver Summit registration and sponsor sales are currently open. Learn more <https://www.openstack.org/summit/denver-2019> and email summit(a)openstack.org <mailto:summit@openstack.org> with any questions. Please email speakersupport(a)openstack.org <mailto:speakersupport@openstack.org> with any questions or feedback. Thanks, Claire

1 1

[Starlingx-discuss] After deploy VM on SRIOV NIC, VM could not get IP from dnsmasq automatically.
by Liu, ZhipengS 22 Jan '19

22 Jan '19

Hi huifeng, We just want to deploy two VM(VM1, VM2) to 2 sriov VFs and PT_VM to sriov PF as pass through in the same worker node (2 different physical ports of one sriov NIC ) As we talked, the issue is VM1, VM2 and PT_VM could not get IP from Dnsmasq. Still not sure if it is an expected case. I can configure IP for them manually, then ping between VM1 and VM2 is OK! If I use network cable to connect this 2 physical ports after configured IP, ping between VM1 and PT_VM doesn't work! openstack server create --flavor flavor-pcipt --image centos-root-img --port sriov-port vm1 openstack server create --flavor flavor-pcipt --image centos-root-img --port sriov-port2 vm2 Then I tried to deploy VM3 as below openstack server create --flavor flavor-pcipt --image centos-root-img -nic net-id = net-testpci vm3 I can see VM3 can get IP automatically from Dnsmasq, but ping from VM3 to VM1/VM2 doesn't work! vm3 | ACTIVE | net-testpci=28.10.10.20 | centos-root-img | flavor-pcipt vm2 | ACTIVE | net-testpci=28.10.10.19 | centos-root-img | flavor-pcipt vm1 | ACTIVE | net-testpci=28.10.10.16 | centos-root-img | flavor-pcipt >From below doc, it seems that PING between VM1 and VM3 should work after some configuration for FDB L2 Agent Extension I tried to add this extensions to below file and restart service. However, it will cause VM could not be created successfully. compute-5:/etc/neutron/plugins/ml2/ openvswitch_agent.ini https://wiki.openstack.org/wiki/SR-IOV-Passthrough-For-Networking FDB L2 Agent Extension The FDB population is an L2 agent extension to OVS agent or Linux bridge. Its objective is to update the FDB table for existing instance using normal port, thus enabling communication between SR-IOV instances and normal instances. The use cases of the FDB population extension are: 1. Direct port and normal port instances reside on the same compute node. 2. Direct port instance using floating IP and network node are located on the same host. Thanks! zhipeng

1 0

Re: [Starlingx-discuss] Starlingx-discuss Digest, Vol 8, Issue 73
by Chen, Haochuan Z 21 Jan '19

21 Jan '19

Hi Himanshu You seems make "Dynamic IP address allocation" to N, in config_controller for management network. I have not tried static IP deployment. You can make such triage. $ system host-add -n compute-0 -p compute -m 00:1e:67:fd:3d:fe -i 192.168.204.3 BR! Martin, Chen SSG OTC, Software Engineer 021-61164330 -----Original Message----- From: starlingx-discuss-request(a)lists.starlingx.io [mailto:starlingx-discuss-request@lists.starlingx.io] Sent: Tuesday, January 22, 2019 3:13 PM To: starlingx-discuss(a)lists.starlingx.io Subject: Starlingx-discuss Digest, Vol 8, Issue 73 Send Starlingx-discuss mailing list submissions to starlingx-discuss(a)lists.starlingx.io To subscribe or unsubscribe via the World Wide Web, visit http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss or, via email, send a message with subject or body 'help' to starlingx-discuss-request(a)lists.starlingx.io You can reach the person managing the list at starlingx-discuss-owner(a)lists.starlingx.io When replying, please edit your Subject line so it is more specific than "Re: Contents of Starlingx-discuss digest..." Today's Topics: 1. Re: Deployment Option (Hu, Yong) ---------------------------------------------------------------------- Message: 1 Date: Tue, 22 Jan 2019 07:13:09 +0000 From: "Hu, Yong" <yong.hu(a)intel.com> To: Himanshu Goyal <himanshugoyal500(a)gmail.com>, "Alonso, Juan Carlos" <juan.carlos.alonso(a)intel.com> Cc: "starlingx-discuss(a)lists.starlingx.io" <starlingx-discuss(a)lists.starlingx.io> Subject: Re: [Starlingx-discuss] Deployment Option Message-ID: <673DA92A-9CAD-4EF5-A2FC-4EE22D897B9D(a)intel.com> Content-Type: text/plain; charset="utf-8" Himanshu, Could you have a try with a hub which 2 mgt ports (from controller and compute) are plugged into? Let’s assure the normal setup works first, and then figure out why the direct linkage of cable doesn’t work. BTW: “worker” and “compute” are just different “personality” names in different STX version. On your current setup “compute” will do, supposedly. From: Himanshu Goyal <himanshugoyal500(a)gmail.com> Date: Tuesday, 22 January 2019 at 12:32 AM To: "Alonso, Juan Carlos" <juan.carlos.alonso(a)intel.com> Cc: "Hu, Yong" <yong.hu(a)intel.com>, "starlingx-discuss(a)lists.starlingx.io" <starlingx-discuss(a)lists.starlingx.io> Subject: Re: [Starlingx-discuss] Deployment Option Thanks Juan ,Yong I tried both the commands output shows as below: 1) [wrsroot@controller-0 ~(keystone_admin)]$ system host-add -n compute-0 -p worker -m 00:1e:67:fd:3d:fe usage: system host-add [-n <hostname>] [-p <personality>] [-s <subfunctions>] [-m <mgmt_mac>] [-i <mgmt_ip>] [-I <bm_ip>] [-T <bm_type>] [-U <bm_username>] [-P <bm_password>] [-b <boot_device>] [-r <rootfs_device>] [-o <install_output>] [-c <console>] [-v <vsc_controllers>] [-l <location>] [-D <true/false>] system host-add: error: argument -p/--personality: invalid choice: 'worker' (choose from 'controller', 'compute', 'storage', 'network', 'profile') [wrsroot@controller-0 ~(keystone_admin)]$ [wrsroot@controller-0 ~(keystone_admin)]$ 2) [wrsroot@controller-0 ~(keystone_admin)]$ system host-add -n compute-0 -p compute -m 00:1e:67:fd:3d:fe Host-add Rejected: Cannot add a compute host without specifying a mgmt_ip when static address allocation is configured. [wrsroot@controller-0 ~(keystone_admin)]$ Regards, Himanshu Goyal On Mon, Jan 21, 2019 at 8:42 PM Alonso, Juan Carlos <juan.carlos.alonso(a)intel.com<mailto:juan.carlos.alonso@intel.com>> wrote: Hi, The personality of computes changed to “worker”, so the command should be: system host-add -n compute-0 -p worker -m ${mac_address} Regards. Juan Carlos Alonso From: Hu, Yong Sent: Monday, January 21, 2019 8:51 AM To: Himanshu Goyal <himanshugoyal500(a)gmail.com<mailto:himanshugoyal500@gmail.com>>; Alonso, Juan Carlos <juan.carlos.alonso(a)intel.com<mailto:juan.carlos.alonso@intel.com>> Cc: starlingx-discuss(a)lists.starlingx.io<mailto:starlingx-discuss@lists.starlingx.io> Subject: Re: [Starlingx-discuss] Deployment Option Hi Himanshu, “system host-list” doesn’t “see” your compute node and LLDP won’t work, because the mgt port on compute node directly connects to mgt port on controller-0 (rather than both connecting to a hub). Anyway, given you know the MAC of mgt port on compute node, you can have a try to run the following cmd: # system host-add -n compute-0 -p compute -m <compute_node_mgt_port_mac> Regards, yong From: Himanshu Goyal <himanshugoyal500(a)gmail.com<mailto:himanshugoyal500@gmail.com>> Date: Monday, 21 January 2019 at 8:14 PM To: "Alonso, Juan Carlos" <juan.carlos.alonso(a)intel.com<mailto:juan.carlos.alonso@intel.com>> Cc: "starlingx-discuss(a)lists.starlingx.io<mailto:starlingx-discuss@lists.starlingx.io>" <starlingx-discuss(a)lists.starlingx.io<mailto:starlingx-discuss@lists.starlingx.io>> Subject: Re: [Starlingx-discuss] Deployment Option Thanks Juan, Able to unlock my controller node. But facing Issue in PXE boot of compute node. After unlocking of controller machine not able to see compute host in "system host-list" command. my controller machine is directly connected to compute machine. I'm following the below steps Steps: 1) system host-unlock controller-0 2) system host-list Output:: [wrsroot@controller-0 ~(keystone_admin)]$ system host-list +----+--------------+-------------+----------------+-------------+--------------+ | id | hostname | personality | administrative | operational | availability | +----+--------------+-------------+----------------+-------------+--------------+ | 1 | controller-0 | controller | unlocked | enabled | available | +----+--------------+-------------+----------------+-------------+--------------+ 3) power on my compute machine. And give option to boot from PXE my compute machine is directly connected with controller with mgmt port. But not able to see host in "system host-list". 4) i tried with system host-add command also, but it is giving below error: Error: [wrsroot@controller-0 ~(keystone_admin)]$ system host-add Host-add Rejected: Cannot add a compute host without specifying a mgmt_ip when static address allocation is configured. Please suggest me the needful change. Regards, Himanshu Goyal -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.starlingx.io/pipermail/starlingx-discuss/attachments/20190122/…> ------------------------------ Subject: Digest Footer _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss(a)lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss ------------------------------ End of Starlingx-discuss Digest, Vol 8, Issue 73 ************************************************

1 0

[Starlingx-discuss] Sanity Test - ISO 20190121
by Alonso, Juan Carlos 21 Jan '19

21 Jan '19

Status of the Sanity Test for last CENGN ISO: bootimage.iso from 2019-Jan-21 (link<http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20190121T06…>) Sanity Test is executed in a Virtual Environment Status: GREEN Simplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity 25 TCs [PASS] TOTAL: [ 30 TCs PASS ] Duplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity 26 TCs [PASS] TOTAL: [ 31 TCs PASS ] Multinode Controller Storage Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity 26 TCs [PASS] TOTAL: [ 31 TCs PASS ] Multinode Dedicated Storage Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity 26 TCs [PASS] TOTAL: [ 31 TCs PASS ] ------------------------------------------------------------------ Regards. Juan Carlos Alonso

1 0

[Starlingx-discuss] [ Test ] Meeting agenda - 01/22/2019
by Cabrales, Ada 21 Jan '19

21 Jan '19

Agenda for 01/22/2019 testing meeting * Review of tasks for 2019.05.0 release * Update on test repository - Cristopher * Update on Test Dashboard - Cristopher * Opens Regards, Ada

1 0

[Starlingx-discuss] [Test] STX Sanity Test Cases after Containerization
by Waheed, Numan 21 Jan '19

21 Jan '19

Hi Ada, As discussed last week, please find below test case titles for STX Sanity after containerization. Test Steps for these sanities are posted at the following shared folder: https://drive.google.com/drive/folders/1YlAlWT7FtSFNyYDdJ2hbFFW4aNGQXCHY Name of the files are "platform_sanity.txt" and "stx_openstack_sanity.txt". Please note that there will be two sanities after containerization. First will be for Platform services i.e. without installing OpenStack and the second will be with OpenStack. Sanity (Platform Only) Platform sanity test cases. Following list of test cases can be executed before stx-openstack is deployed. test_launch_app_via_kubectl(copy_test_apps, delete_test_pod, controller) test_launch_app_via_sysinv(copy_test_apps, cleanup_app) test_push_docker_image_to_local_registry(controller) test_upload_helm_charts(copy_test_apps, controller) test_kube_system_services(controller) test_horizon_host_inventory_display(host_inventory_pg) test_lock_active_controller_reject(no_simplex) test_lock_unlock_host(host_type, collect_kpi) test_swact_controller_platform(wait_for_con_drbd_sync_complete) To be added: - Test case to validate container messaging (eg: ssh into pod, messaging between pods) Sanity (With OpenStack) Sanity with stx-openstack. Following list of test cases are executed after stx-openstack is deployed. Tests should be executed with various configurations: - system with remote storage, single node system, multi-node system, etc. - https - IPv4, IPv6 test_openstack_services_healthy() test_reapply_stx_openstack(skip_for_no_openstack) test_stx_openstack_helm_override_update_and_reset(skip_for_no_openstack, reset_if_modified) test_horizon_create_delete_instance(instances_pg) test_heat_template() test_system_persist_over_host_reboot(host_type) test_add_host_simplex_negative(simplex_only) test_evacuate_vms(self, vms_) test_swact_controllers(wait_for_con_drbd_sync_complete) test_measurements_for_metric(meter) test_ceilometer_meters_exist(meters) test_system_alarms_and_events_on_lock_unlock_compute(no_simplex) test_lock_unlock_host(host_type, collect_kpi) test_vm_meta_data_retrieval() test_reboot_only_host(self, get_zone) test_migrate_vm(check_system, guest_os, mig_type, cpu_pol) test_nova_actions(guest_os, cpu_pol, actions) test_vm_with_a_large_volume_live_migrate(vms_, pre_alarm_) test_ping_between_two_vms(guest_os, vm1_vifs, vm2_vifs, skip_for_ovs) To be added: - Deploy stx-openstack from controller-1 (currently initial deployment of stx-openstack is always done from controller-0) - Recovery scenarios: validate pods recovered if process killed or pod deleted (eg: nova-compute, libvirtd) Thanks, Numan.

2 1

[Starlingx-discuss] ARs from Chandler Mini-PTG
by Zvonar, Bill 21 Jan '19

21 Jan '19

I've placed the list of ARs I captured in the mini-PTG last week up on the shared folder on Google Drive. - the shared folder is here: https://drive.google.com/drive/folders/1YlAlWT7FtSFNyYDdJ2hbFFW4aNGQXCHY?us… - the AR list is here: https://docs.google.com/spreadsheets/d/1F-JKh8_gLlUzbrUJRbsf4u65yBGVBl8HGe-… I'll add an item on the Community call agenda to go through these. Bill...

1 0

[Starlingx-discuss] Agenda: Weekly StarlingX non-OpenStack Distro meeting, 1/23
by Xie, Cindy 21 Jan '19

21 Jan '19

Agenda: 1. CentOS 7.6 upgrade status (Shuicheng/Martin) 2. Ceph upgrade (Vivian/Changcheng) 3. Python2to3 status (Austin) 4. Bug triage (Cindy) 5. Opens (all) Thx. -----Original Appointment----- From: Xie, Cindy Sent: Sunday, November 4, 2018 10:27 PM To: Xie, Cindy; 'Khalil, Ghada'; Sun, Austin; Somerville, Jim; 'Rowsell, Brent'; Liu, ZhipengS; Wold, Saul; starlingx-discuss(a)lists.starlingx.io; Shang, Dehao; Waheed, Numan; Troyer, Dean; Jones, Bruce E; Lin, Shuicheng; Zhu, Vivian; Hu, Yong Cc: Hu, Wei W; 'Seiler, Glenn'; Gomez, Juan P; 'Chen, Jacky'; Perez Rodriguez, Humberto I; 'Young, Ken'; Cobbley, David A; 'Waines, Greg'; Arce Moreno, Abraham; 'Eslimi, Dariush'; Lara, Cesar; Perez Carranza, Jose; 'Hellmann, Gil'; Armstrong, Robert H; Martinez Landa, Hayde; Martinez Monroy, Elio Subject: Weekly StarlingX non-OpenStack Distro meeting When: Wednesday, January 23, 2019 6:00 AM-7:00 AM (UTC-08:00) Pacific Time (US & Canada). Where: https://zoom.us/j/342730236 * Cadence and time slot: o Wednesday 9AM Winter EDT (10PM China time, US PDT Winter time 6AM) * Call Details: o Zoom link: https://zoom.us/j/342730236 o Dialing in from phone: o Dial(for higher quality, dial a number based on your current location): US: +1 669 900 6833 or +1 646 876 9923 o Meeting ID: 342 730 236 o International numbers available: https://zoom.us/u/ed95sU7aQ * Meeting Agenda and Minutes: o https://etherpad.openstack.org/p/stx-distro-other

1 0

[Starlingx-discuss] WG: cpu mode
by von Hoesslin, Volker 21 Jan '19

21 Jan '19

i have set "host-passthrough" in "/etc/nova/nova.conf" ================================= [DEFAULT] libvirt_cpu_mode = host-passthrough [libvirt] cpu_mode = host-passthrough ================================= and restart nove service: # service nova-compute restart for now it works! "lscpu" on guest os shows me the AMD EPIC with all features, very nice. but after reboot the compute-node, the auto-config script change this setting back to "none": [libvirt] cpu_mode = none and passthrough did not work anymore :( so how can i prevent this auto-config or define my new config as persistent? volker... ________________________________________ Von: Michel Thebeau [michel.thebeau(a)windriver.com] Gesendet: Freitag, 18. Januar 2019 17:07 An: von Hoesslin, Volker; starlingx-discuss(a)lists.starlingx.io Betreff: Re: [Starlingx-discuss] cpu mode Hi Volker, The output you listed here lists the values accepted by openstack flavor set command. Did you try "Passthrough"? I'm asking internally about cpu model support and I'll respond if I hear anything interesting. M On Thu, 2019-01-17 at 16:23 +0000, von Hoesslin, Volker wrote: > it is impossible to set a EPIC (or any other AMD) as guest CPU? > > $ openstack flavor set --property hw:cpu_model=EPYC-IBPB 76609f7b- > f0c7-48ca-8c8a-f78481e62cd4 > Failed to set flavor property: Invalid hw:cpu_model 'EPYC-IBPB', must > be one of: Passthrough, Conroe, Penryn, Nehalem, Westmere, > SandyBridge, IvyBridge, Haswell, Broadwell-noTSX, Broadwell, Skylake- > Client, Skylake-Server. (HTTP 400) (Request-ID: req-2fda19cc-8e0e- > 4be8-a8ea-b58fc00358ce) > Command Failed: One or more of the operations failed > > but my compute node seems to support EPIC CPUs? > > cat /usr/share/libvirt/cpu_map/x86_EPYC-IBRS.xml > > <cpus> > <model name='EPYC-IBPB'> > <signature family='23' model='1'/> > <vendor name='AMD'/> > <feature name='3dnowprefetch'/> > .... > <feature name='xsavec'/> > <feature name='xsaveopt'/> > </model> > </cpus> > > some tips for me how to handle this? > > volker... > > Von: von Hoesslin, Volker [Volker.Hoesslin(a)swsn.de] > Gesendet: Donnerstag, 17. Januar 2019 15:50 > An: starlingx-discuss(a)lists.starlingx.io > Betreff: [Starlingx-discuss] cpu mode > > hi, > my setup has two computes nodes, every node has a dual AMD EPYC 7601 > CPU config. how can i bring all the CPU features (AES, SSSE3, ...) to > the guest VMs. i have tryed with some flavor-metadata but nothing > realy helps, the VMs getting just a little subset of cpu-features. > some investigations to the kvm-settings hit me to the facts that my > nova config has "cpu_model=none" !? how can i fix that and bring my > AMD EPIC CPU to my nova-config?! > > here is the host /proc/cpuinfo > > processor : 127 > vendor_id : AuthenticAMD > cpu family : 23 > model : 1 > model name : AMD EPYC 7601 32-Core Processor > stepping : 2 > microcode : 0x8001227 > cpu MHz : 1200.000 > cache size : 512 KB > physical id : 1 > siblings : 64 > core id : 31 > cpu cores : 32 > apicid : 127 > initial apicid : 127 > fpu : yes > fpu_exception : yes > cpuid level : 13 > wp : yes > flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr > pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext > fxsr_opt pdpe1gb rdtscp lm constant_tsc art rep_good nopl nonstop_tsc > extd_apicid amd_dcm aperfmperf eagerfpu pni pclmulqdq monitor ssse3 > fma cx16 sse4_1 sse4_2 movbe popcnt aes xsave avx f16c rdrand lahf_lm > cmp_legacy svm extapic cr8_legacy abm sse4a misalignsse 3dnowprefetch > osvw skinit wdt tce topoext perfctr_core perfctr_nb bpext perfctr_l2 > cpb hw_pstate retpoline_amd ssbd ibpb vmmcall fsgsbase bmi1 avx2 smep > bmi2 rdseed adx smap clflushopt sha_ni xsaveopt xsavec xgetbv1 clzero > irperf xsaveerptr arat npt lbrv svm_lock nrip_save tsc_scale > vmcb_clean flushbyasid decodeassists pausefilter pfthreshold avic > v_vmsave_vmload vgif overflow_recov succor smca > bogomips : 4400.08 > TLB size : 2560 4K pages > clflush size : 64 > cache_alignment : 64 > address sizes : 48 bits physical, 48 bits virtual > power management: ts ttp tm hwpstate cpb eff_freq_ro [13] [14] > > greez & thx, > volker... > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss(a)lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss

2 4

Re: [Starlingx-discuss] cpu mode
by von Hoesslin, Volker 21 Jan '19

21 Jan '19

i know, i know, i shouldnt spam this list ;) but after some tests i have tried to change the nova-conf (/etc/nova/nova.conf) and edit some values: [default] libvirt_cpu_mode = "custom" // none -> costom libvirt_cpu_model = "EPYC-IBRS" // insert this line [libvirt] cpu_mode = "custom" // none -> custom cpu_model = "EPYC-IBRS" // insert this line but after reboot my compute-node, some auto-config logic is reconfigure this config-file and "[libvirt]" part the option "cpu_mode" is back to "none" and "cpu_model" is deleted completly :( is there any way to prevent or configure this auto-config? volker... ________________________________________ Von: von Hoesslin, Volker [Volker.Hoesslin(a)swsn.de] Gesendet: Freitag, 18. Januar 2019 13:57 An: Arevalo, Mario Alfredo C; starlingx-discuss(a)lists.starlingx.io Betreff: Re: [Starlingx-discuss] cpu mode i do not know if this helps, but here is a little more input: # virsh capabilities <capabilities> <host> <uuid>00000000-0000-0000-0000-ac1f6b647302</uuid> <cpu> <arch>x86_64</arch> <model>EPYC-IBPB</model> <vendor>AMD</vendor> <microcode version='134222375'/> <topology sockets='1' cores='32' threads='2'/> <feature name='ht'/> <feature name='osxsave'/> <feature name='xsaves'/> <feature name='cmp_legacy'/> <feature name='extapic'/> <feature name='skinit'/> <feature name='wdt'/> <feature name='tce'/> <feature name='topoext'/> <feature name='perfctr_core'/> <feature name='perfctr_nb'/> <feature name='invtsc'/> <pages unit='KiB' size='4'/> <pages unit='KiB' size='2048'/> <pages unit='KiB' size='1048576'/> </cpu> <power_management> <suspend_mem/> </power_management> <iommu support='yes'/> <migration_features> <live/> <uri_transports> <uri_transport>tcp</uri_transport> <uri_transport>rdma</uri_transport> </uri_transports> </migration_features> <topology> <cells num='2'> <cell id='0'> <memory unit='KiB'>134119260</memory> <pages unit='KiB' size='4'>2891223</pages> <pages unit='KiB' size='2048'>59329</pages> <pages unit='KiB' size='1048576'>1</pages> <distances> <sibling id='0' value='10'/> <sibling id='1' value='32'/> </distances> <cpus num='64'> <cpu id='0' socket_id='0' core_id='0' siblings='0,64'/> <cpu id='1' socket_id='0' core_id='1' siblings='1,65'/> <cpu id='2' socket_id='0' core_id='2' siblings='2,66'/> <cpu id='3' socket_id='0' core_id='3' siblings='3,67'/> <cpu id='4' socket_id='0' core_id='4' siblings='4,68'/> <cpu id='5' socket_id='0' core_id='5' siblings='5,69'/> <cpu id='6' socket_id='0' core_id='6' siblings='6,70'/> <cpu id='7' socket_id='0' core_id='7' siblings='7,71'/> <cpu id='8' socket_id='0' core_id='8' siblings='8,72'/> <cpu id='9' socket_id='0' core_id='9' siblings='9,73'/> <cpu id='10' socket_id='0' core_id='10' siblings='10,74'/> <cpu id='11' socket_id='0' core_id='11' siblings='11,75'/> <cpu id='12' socket_id='0' core_id='12' siblings='12,76'/> <cpu id='13' socket_id='0' core_id='13' siblings='13,77'/> <cpu id='14' socket_id='0' core_id='14' siblings='14,78'/> <cpu id='15' socket_id='0' core_id='15' siblings='15,79'/> <cpu id='16' socket_id='0' core_id='16' siblings='16,80'/> <cpu id='17' socket_id='0' core_id='17' siblings='17,81'/> <cpu id='18' socket_id='0' core_id='18' siblings='18,82'/> <cpu id='19' socket_id='0' core_id='19' siblings='19,83'/> <cpu id='20' socket_id='0' core_id='20' siblings='20,84'/> <cpu id='21' socket_id='0' core_id='21' siblings='21,85'/> <cpu id='22' socket_id='0' core_id='22' siblings='22,86'/> <cpu id='23' socket_id='0' core_id='23' siblings='23,87'/> <cpu id='24' socket_id='0' core_id='24' siblings='24,88'/> <cpu id='25' socket_id='0' core_id='25' siblings='25,89'/> <cpu id='26' socket_id='0' core_id='26' siblings='26,90'/> <cpu id='27' socket_id='0' core_id='27' siblings='27,91'/> <cpu id='28' socket_id='0' core_id='28' siblings='28,92'/> <cpu id='29' socket_id='0' core_id='29' siblings='29,93'/> <cpu id='30' socket_id='0' core_id='30' siblings='30,94'/> <cpu id='31' socket_id='0' core_id='31' siblings='31,95'/> <cpu id='64' socket_id='0' core_id='0' siblings='0,64'/> <cpu id='65' socket_id='0' core_id='1' siblings='1,65'/> <cpu id='66' socket_id='0' core_id='2' siblings='2,66'/> <cpu id='67' socket_id='0' core_id='3' siblings='3,67'/> <cpu id='68' socket_id='0' core_id='4' siblings='4,68'/> <cpu id='69' socket_id='0' core_id='5' siblings='5,69'/> <cpu id='70' socket_id='0' core_id='6' siblings='6,70'/> <cpu id='71' socket_id='0' core_id='7' siblings='7,71'/> <cpu id='72' socket_id='0' core_id='8' siblings='8,72'/> <cpu id='73' socket_id='0' core_id='9' siblings='9,73'/> <cpu id='74' socket_id='0' core_id='10' siblings='10,74'/> <cpu id='75' socket_id='0' core_id='11' siblings='11,75'/> <cpu id='76' socket_id='0' core_id='12' siblings='12,76'/> <cpu id='77' socket_id='0' core_id='13' siblings='13,77'/> <cpu id='78' socket_id='0' core_id='14' siblings='14,78'/> <cpu id='79' socket_id='0' core_id='15' siblings='15,79'/> <cpu id='80' socket_id='0' core_id='16' siblings='16,80'/> <cpu id='81' socket_id='0' core_id='17' siblings='17,81'/> <cpu id='82' socket_id='0' core_id='18' siblings='18,82'/> <cpu id='83' socket_id='0' core_id='19' siblings='19,83'/> <cpu id='84' socket_id='0' core_id='20' siblings='20,84'/> <cpu id='85' socket_id='0' core_id='21' siblings='21,85'/> <cpu id='86' socket_id='0' core_id='22' siblings='22,86'/> <cpu id='87' socket_id='0' core_id='23' siblings='23,87'/> <cpu id='88' socket_id='0' core_id='24' siblings='24,88'/> <cpu id='89' socket_id='0' core_id='25' siblings='25,89'/> <cpu id='90' socket_id='0' core_id='26' siblings='26,90'/> <cpu id='91' socket_id='0' core_id='27' siblings='27,91'/> <cpu id='92' socket_id='0' core_id='28' siblings='28,92'/> <cpu id='93' socket_id='0' core_id='29' siblings='29,93'/> <cpu id='94' socket_id='0' core_id='30' siblings='30,94'/> <cpu id='95' socket_id='0' core_id='31' siblings='31,95'/> </cpus> </cell> <cell id='1'> <memory unit='KiB'>134213632</memory> <pages unit='KiB' size='4'>1239040</pages> <pages unit='KiB' size='2048'>62602</pages> <pages unit='KiB' size='1048576'>1</pages> <distances> <sibling id='0' value='32'/> <sibling id='1' value='10'/> </distances> <cpus num='64'> <cpu id='32' socket_id='1' core_id='0' siblings='32,96'/> <cpu id='33' socket_id='1' core_id='1' siblings='33,97'/> <cpu id='34' socket_id='1' core_id='2' siblings='34,98'/> <cpu id='35' socket_id='1' core_id='3' siblings='35,99'/> <cpu id='36' socket_id='1' core_id='4' siblings='36,100'/> <cpu id='37' socket_id='1' core_id='5' siblings='37,101'/> <cpu id='38' socket_id='1' core_id='6' siblings='38,102'/> <cpu id='39' socket_id='1' core_id='7' siblings='39,103'/> <cpu id='40' socket_id='1' core_id='8' siblings='40,104'/> <cpu id='41' socket_id='1' core_id='9' siblings='41,105'/> <cpu id='42' socket_id='1' core_id='10' siblings='42,106'/> <cpu id='43' socket_id='1' core_id='11' siblings='43,107'/> <cpu id='44' socket_id='1' core_id='12' siblings='44,108'/> <cpu id='45' socket_id='1' core_id='13' siblings='45,109'/> <cpu id='46' socket_id='1' core_id='14' siblings='46,110'/> <cpu id='47' socket_id='1' core_id='15' siblings='47,111'/> <cpu id='48' socket_id='1' core_id='16' siblings='48,112'/> <cpu id='49' socket_id='1' core_id='17' siblings='49,113'/> <cpu id='50' socket_id='1' core_id='18' siblings='50,114'/> <cpu id='51' socket_id='1' core_id='19' siblings='51,115'/> <cpu id='52' socket_id='1' core_id='20' siblings='52,116'/> <cpu id='53' socket_id='1' core_id='21' siblings='53,117'/> <cpu id='54' socket_id='1' core_id='22' siblings='54,118'/> <cpu id='55' socket_id='1' core_id='23' siblings='55,119'/> <cpu id='56' socket_id='1' core_id='24' siblings='56,120'/> <cpu id='57' socket_id='1' core_id='25' siblings='57,121'/> <cpu id='58' socket_id='1' core_id='26' siblings='58,122'/> <cpu id='59' socket_id='1' core_id='27' siblings='59,123'/> <cpu id='60' socket_id='1' core_id='28' siblings='60,124'/> <cpu id='61' socket_id='1' core_id='29' siblings='61,125'/> <cpu id='62' socket_id='1' core_id='30' siblings='62,126'/> <cpu id='63' socket_id='1' core_id='31' siblings='63,127'/> <cpu id='96' socket_id='1' core_id='0' siblings='32,96'/> <cpu id='97' socket_id='1' core_id='1' siblings='33,97'/> <cpu id='98' socket_id='1' core_id='2' siblings='34,98'/> <cpu id='99' socket_id='1' core_id='3' siblings='35,99'/> <cpu id='100' socket_id='1' core_id='4' siblings='36,100'/> <cpu id='101' socket_id='1' core_id='5' siblings='37,101'/> <cpu id='102' socket_id='1' core_id='6' siblings='38,102'/> <cpu id='103' socket_id='1' core_id='7' siblings='39,103'/> <cpu id='104' socket_id='1' core_id='8' siblings='40,104'/> <cpu id='105' socket_id='1' core_id='9' siblings='41,105'/> <cpu id='106' socket_id='1' core_id='10' siblings='42,106'/> <cpu id='107' socket_id='1' core_id='11' siblings='43,107'/> <cpu id='108' socket_id='1' core_id='12' siblings='44,108'/> <cpu id='109' socket_id='1' core_id='13' siblings='45,109'/> <cpu id='110' socket_id='1' core_id='14' siblings='46,110'/> <cpu id='111' socket_id='1' core_id='15' siblings='47,111'/> <cpu id='112' socket_id='1' core_id='16' siblings='48,112'/> <cpu id='113' socket_id='1' core_id='17' siblings='49,113'/> <cpu id='114' socket_id='1' core_id='18' siblings='50,114'/> <cpu id='115' socket_id='1' core_id='19' siblings='51,115'/> <cpu id='116' socket_id='1' core_id='20' siblings='52,116'/> <cpu id='117' socket_id='1' core_id='21' siblings='53,117'/> <cpu id='118' socket_id='1' core_id='22' siblings='54,118'/> <cpu id='119' socket_id='1' core_id='23' siblings='55,119'/> <cpu id='120' socket_id='1' core_id='24' siblings='56,120'/> <cpu id='121' socket_id='1' core_id='25' siblings='57,121'/> <cpu id='122' socket_id='1' core_id='26' siblings='58,122'/> <cpu id='123' socket_id='1' core_id='27' siblings='59,123'/> <cpu id='124' socket_id='1' core_id='28' siblings='60,124'/> <cpu id='125' socket_id='1' core_id='29' siblings='61,125'/> <cpu id='126' socket_id='1' core_id='30' siblings='62,126'/> <cpu id='127' socket_id='1' core_id='31' siblings='63,127'/> </cpus> </cell> </cells> </topology> <cache> <bank id='0' level='3' type='both' size='8' unit='MiB' cpus='0-3,64-67'/> <bank id='1' level='3' type='both' size='8' unit='MiB' cpus='4-7,68-71'/> <bank id='2' level='3' type='both' size='8' unit='MiB' cpus='8-11,72-75'/> <bank id='3' level='3' type='both' size='8' unit='MiB' cpus='12-15,76-79'/> <bank id='4' level='3' type='both' size='8' unit='MiB' cpus='16-19,80-83'/> <bank id='5' level='3' type='both' size='8' unit='MiB' cpus='20-23,84-87'/> <bank id='6' level='3' type='both' size='8' unit='MiB' cpus='24-27,88-91'/> <bank id='7' level='3' type='both' size='8' unit='MiB' cpus='28-31,92-95'/> <bank id='8' level='3' type='both' size='8' unit='MiB' cpus='32-35,96-99'/> <bank id='9' level='3' type='both' size='8' unit='MiB' cpus='36-39,100-103'/> <bank id='10' level='3' type='both' size='8' unit='MiB' cpus='40-43,104-107'/> <bank id='11' level='3' type='both' size='8' unit='MiB' cpus='44-47,108-111'/> <bank id='12' level='3' type='both' size='8' unit='MiB' cpus='48-51,112-115'/> <bank id='13' level='3' type='both' size='8' unit='MiB' cpus='52-55,116-119'/> <bank id='14' level='3' type='both' size='8' unit='MiB' cpus='56-59,120-123'/> <bank id='15' level='3' type='both' size='8' unit='MiB' cpus='60-63,124-127'/> </cache> <secmodel> <model>none</model> <doi>0</doi> </secmodel> <secmodel> <model>dac</model> <doi>0</doi> <baselabel type='kvm'>+0:+0</baselabel> <baselabel type='qemu'>+0:+0</baselabel> </secmodel> </host> <guest> <os_type>hvm</os_type> <arch name='i686'> <wordsize>32</wordsize> <emulator>/usr/bin/qemu-system-x86_64</emulator> <machine maxCpus='240'>pc-i440fx-rhel7.4.0</machine> <machine canonical='pc-i440fx-rhel7.4.0' maxCpus='240'>pc</machine> <machine maxCpus='240'>pc-i440fx-rhel7.0.0</machine> <machine maxCpus='240'>pc-i440fx-2.4</machine> <machine maxCpus='240'>rhel6.3.0</machine> <machine maxCpus='240'>rhel6.4.0</machine> <machine maxCpus='240'>rhel6.0.0</machine> <machine maxCpus='240'>pc-i440fx-2.8</machine> <machine maxCpus='240'>pc-i440fx-2.7</machine> <machine maxCpus='240'>pc-i440fx-2.10</machine> <machine canonical='pc-i440fx-2.10' maxCpus='240'>pc</machine> <machine maxCpus='240'>pc-i440fx-rhel7.1.0</machine> <machine maxCpus='240'>pc-i440fx-2.3</machine> <machine maxCpus='240'>pc-i440fx-rhel7.2.0</machine> <machine maxCpus='240'>pc-i440fx-2.2</machine> <machine maxCpus='240'>pc-q35-rhel7.3.0</machine> <machine canonical='pc-q35-rhel7.3.0' maxCpus='240'>q35</machine> <machine maxCpus='240'>rhel6.5.0</machine> <machine maxCpus='240'>rhel6.6.0</machine> <machine maxCpus='240'>rhel6.1.0</machine> <machine maxCpus='240'>pc-i440fx-2.6</machine> <machine maxCpus='240'>rhel6.2.0</machine> <machine maxCpus='240'>pc-i440fx-2.5</machine> <machine maxCpus='240'>pc-i440fx-rhel7.3.0</machine> <machine maxCpus='240'>pc-i440fx-2.9</machine> <domain type='qemu'/> <domain type='kvm'> <emulator>/usr/libexec/qemu-kvm</emulator> <machine maxCpus='240'>pc-i440fx-rhel7.4.0</machine> <machine canonical='pc-i440fx-rhel7.4.0' maxCpus='240'>pc</machine> <machine maxCpus='240'>pc-i440fx-rhel7.0.0</machine> <machine maxCpus='240'>pc-i440fx-2.4</machine> <machine maxCpus='240'>rhel6.3.0</machine> <machine maxCpus='240'>rhel6.4.0</machine> <machine maxCpus='240'>rhel6.0.0</machine> <machine maxCpus='240'>pc-i440fx-2.8</machine> <machine maxCpus='240'>pc-i440fx-2.7</machine> <machine maxCpus='240'>pc-i440fx-2.10</machine> <machine canonical='pc-i440fx-2.10' maxCpus='240'>pc</machine> <machine maxCpus='240'>pc-i440fx-rhel7.1.0</machine> <machine maxCpus='240'>pc-i440fx-2.3</machine> <machine maxCpus='240'>pc-i440fx-rhel7.2.0</machine> <machine maxCpus='240'>pc-i440fx-2.2</machine> <machine maxCpus='240'>pc-q35-rhel7.3.0</machine> <machine canonical='pc-q35-rhel7.3.0' maxCpus='240'>q35</machine> <machine maxCpus='240'>rhel6.5.0</machine> <machine maxCpus='240'>rhel6.6.0</machine> <machine maxCpus='240'>rhel6.1.0</machine> <machine maxCpus='240'>pc-i440fx-2.6</machine> <machine maxCpus='240'>rhel6.2.0</machine> <machine maxCpus='240'>pc-i440fx-2.5</machine> <machine maxCpus='240'>pc-i440fx-rhel7.3.0</machine> <machine maxCpus='240'>pc-i440fx-2.9</machine> </domain> </arch> <features> <cpuselection/> <deviceboot/> <disksnapshot default='on' toggle='no'/> <acpi default='on' toggle='yes'/> <apic default='on' toggle='no'/> <pae/> <nonpae/> </features> </guest> <guest> <os_type>hvm</os_type> <arch name='x86_64'> <wordsize>64</wordsize> <emulator>/usr/bin/qemu-system-x86_64</emulator> <machine maxCpus='240'>pc-i440fx-rhel7.4.0</machine> <machine canonical='pc-i440fx-rhel7.4.0' maxCpus='240'>pc</machine> <machine maxCpus='240'>pc-i440fx-rhel7.0.0</machine> <machine maxCpus='240'>pc-i440fx-2.4</machine> <machine maxCpus='240'>rhel6.3.0</machine> <machine maxCpus='240'>rhel6.4.0</machine> <machine maxCpus='240'>rhel6.0.0</machine> <machine maxCpus='240'>pc-i440fx-2.8</machine> <machine maxCpus='240'>pc-i440fx-2.7</machine> <machine maxCpus='240'>pc-i440fx-2.10</machine> <machine canonical='pc-i440fx-2.10' maxCpus='240'>pc</machine> <machine maxCpus='240'>pc-i440fx-rhel7.1.0</machine> <machine maxCpus='240'>pc-i440fx-2.3</machine> <machine maxCpus='240'>pc-i440fx-rhel7.2.0</machine> <machine maxCpus='240'>pc-i440fx-2.2</machine> <machine maxCpus='240'>pc-q35-rhel7.3.0</machine> <machine canonical='pc-q35-rhel7.3.0' maxCpus='240'>q35</machine> <machine maxCpus='240'>rhel6.5.0</machine> <machine maxCpus='240'>rhel6.6.0</machine> <machine maxCpus='240'>rhel6.1.0</machine> <machine maxCpus='240'>pc-i440fx-2.6</machine> <machine maxCpus='240'>rhel6.2.0</machine> <machine maxCpus='240'>pc-i440fx-2.5</machine> <machine maxCpus='240'>pc-i440fx-rhel7.3.0</machine> <machine maxCpus='240'>pc-i440fx-2.9</machine> <domain type='qemu'/> <domain type='kvm'> <emulator>/usr/libexec/qemu-kvm</emulator> <machine maxCpus='240'>pc-i440fx-rhel7.4.0</machine> <machine canonical='pc-i440fx-rhel7.4.0' maxCpus='240'>pc</machine> <machine maxCpus='240'>pc-i440fx-rhel7.0.0</machine> <machine maxCpus='240'>pc-i440fx-2.4</machine> <machine maxCpus='240'>rhel6.3.0</machine> <machine maxCpus='240'>rhel6.4.0</machine> <machine maxCpus='240'>rhel6.0.0</machine> <machine maxCpus='240'>pc-i440fx-2.8</machine> <machine maxCpus='240'>pc-i440fx-2.7</machine> <machine maxCpus='240'>pc-i440fx-2.10</machine> <machine canonical='pc-i440fx-2.10' maxCpus='240'>pc</machine> <machine maxCpus='240'>pc-i440fx-rhel7.1.0</machine> <machine maxCpus='240'>pc-i440fx-2.3</machine> <machine maxCpus='240'>pc-i440fx-rhel7.2.0</machine> <machine maxCpus='240'>pc-i440fx-2.2</machine> <machine maxCpus='240'>pc-q35-rhel7.3.0</machine> <machine canonical='pc-q35-rhel7.3.0' maxCpus='240'>q35</machine> <machine maxCpus='240'>rhel6.5.0</machine> <machine maxCpus='240'>rhel6.6.0</machine> <machine maxCpus='240'>rhel6.1.0</machine> <machine maxCpus='240'>pc-i440fx-2.6</machine> <machine maxCpus='240'>rhel6.2.0</machine> <machine maxCpus='240'>pc-i440fx-2.5</machine> <machine maxCpus='240'>pc-i440fx-rhel7.3.0</machine> <machine maxCpus='240'>pc-i440fx-2.9</machine> </domain> </arch> <features> <cpuselection/> <deviceboot/> <disksnapshot default='on' toggle='no'/> <acpi default='on' toggle='yes'/> <apic default='on' toggle='no'/> </features> </guest> </capabilities> ________________________________________ Von: von Hoesslin, Volker [Volker.Hoesslin(a)swsn.de] Gesendet: Freitag, 18. Januar 2019 10:30 An: Arevalo, Mario Alfredo C; starlingx-discuss(a)lists.starlingx.io Betreff: Re: [Starlingx-discuss] cpu mode hi, this is an "ps aux | grep qemu" output (for better reading, a little bit formated by me): /usr/libexec/qemu-kvm -name guest=instance-0000000a,debug-threads=on -S -object secret,id=masterKey0,format=raw,file=/var/lib/libvirt/qemu/domain-13-instance-0000000a/master-key.aes -machine pc-i440fx-rhel7.4.0,accel=kvm,usb=off,dump-guest-core=off -m 8192 -realtime mlock=off -smp 4,sockets=4,cores=1,threads=1 -object memory-backend-file,id=ram-node0,prealloc=yes,mem-path=/mnt/huge-2048kB/libvirt/qemu/13-instance-0000000a,share=yes,size=8589934592,host-nodes=0,policy=bind -numa node,nodeid=0,cpus=0-3,memdev=ram-node0 -uuid 3bce281c-db91-4b6f-aa48-832c27c2338f -smbios type=1,manufacturer=Fedora Project,product=OpenStack Nova,version=16.0.2-1.tis.11,serial=f88367ca-9cf6-4678-bc69-69ed97297bb5,uuid=3bce281c-db91-4b6f-aa48-832c27c2338f,family=Virtual Machine -no-user-config -nodefaults -chardev socket,id=charmonitor,path=/var/lib/libvirt/qemu/domain-13-instance-0000000a/monitor.sock,server,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=utc,driftfix=slew -global kvm-pit.lost_tick_policy=delay -no-hpet -no-shutdown -boot reboot-timeout=5000,strict=on -global i440FX-pcihost.pci-hole64-size=67108864K -device piix3-usb-uhci,id=usb,bus=pci.0,addr=0x1.0x2 -drive file=rbd:cinder-volumes/volume-ef431cc7-2964-4335-8138-2d2c6642be6c:auth_supported=none:mon_host=192.168.204.3\:6789\;192.168.204.4\:6789\;192.168.204.112\:6789,format=raw,if=none,id=drive-virtio-disk0,cache=none,discard=unmap -device virtio-blk-pci,scsi=off,bus=pci.0,addr=0x4,drive=drive-virtio-disk0,id=virtio-disk0,bootindex=1,write-cache=on,serial=ef431cc7-2964-4335-8138-2d2c6642be6c -chardev socket,id=charnet0,path=/var/run/openvswitch/vhu74250cb0-40,server -netdev vhost-user,chardev=charnet0,id=hostnet0 -device virtio-net-pci,netdev=hostnet0,id=net0,mac=fa:16:3e:ff:cc:ac,bus=pci.0,addr=0x3 -add-fd set=0,fd=81 -chardev pty,id=charserial0,logfile=/dev/fdset/0,logappend=on -device isa-serial,chardev=charserial0,id=serial0 -device usb-tablet,id=input0,bus=usb.0,port=1 -vnc 0.0.0.0:1 -k en-us -device cirrus-vga,id=video0,bus=pci.0,addr=0x2 -incoming defer -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x5 -msg timestamp=on => btw, how can this cmd-line handle the spaces in argument "-smbios" or just "ps aux" remove the ' " ' ? this is an running VM without any changes, created and started on top starlingx (2x controller, 2x compute, 3x storage). and yes, there is no "-cpu host" argument !? this ends in something like this in guest view: $ lscpu Architecture: x86_64 CPU op-mode(s): 32-bit, 64-bit Byte Order: Little Endian CPU(s): 4 On-line CPU(s) list: 0-3 Thread(s) per core: 1 Core(s) per socket: 1 Socket(s): 4 NUMA node(s): 1 Vendor ID: AuthenticAMD CPU family: 6 Model: 13 Model name: QEMU Virtual CPU version 2.5+ Stepping: 3 CPU MHz: 2199.996 BogoMIPS: 4399.99 Hypervisor vendor: KVM Virtualization type: full L1d cache: 64K L1i cache: 64K L2 cache: 512K L3 cache: 16384K NUMA node0 CPU(s): 0-3 Flags: fpu de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 syscall nx fxsr_opt pdpe1gb lm nopl cpuid pni cx16 x2apic popcnt hypervisor lahf_lm 3dnowprefetch vmmcall here are some outputs from my flavor metadata trys: hw:cpu_model = SandyBridge => No valid host was found. There are not enough hosts available. compute-0: (VCpuModelFilter) Host VCPU model EPYC-IBPB required SandyBridge, compute-1: (VCpuModelFilter) Host VCPU model EPYC-IBPB required SandyBridge of course, SandyBridge is an intel CPU, but all of allowed CPU architectures for meta extra specs "hw:cpu_model" are Intel devices, so i need AMD! do you remember: $ openstack flavor set --property hw:cpu_model=EPYC-IBPB 76609f7b-f0c7-48ca-8c8a-f78481e62cd4 Failed to set flavor property: Invalid hw:cpu_model 'EPYC-IBPB', must be one of: Passthrough, Conroe, Penryn, Nehalem, Westmere, SandyBridge, IvyBridge, Haswell, Broadwell-noTSX, Broadwell, Skylake-Client, Skylake-Server. how can i edit this allowed CPU-Model-List?! the nova.conf settings define no CPU config, so the hyperviser has to handle this: # cat /etc/nova/nova.conf | grep cpu_mode libvirt_cpu_mode = none cpu_mode=none so this is an deadlock for me, i do not know how to fix this :( plz help, volker... ________________________________________ Von: Arevalo, Mario Alfredo C [mario.alfredo.c.arevalo(a)intel.com] Gesendet: Donnerstag, 17. Januar 2019 17:40 An: von Hoesslin, Volker; starlingx-discuss(a)lists.starlingx.io Betreff: RE: cpu mode Hi Volker, Could you please send me the QEMU command line used to launch your VM, this is in order to check the QEMU arguments/flags, possibly it requires "-cpu host" argument. Thanks. Best regards. Mario. From: von Hoesslin, Volker [Volker.Hoesslin(a)swsn.de] Sent: Thursday, January 17, 2019 8:23 AM To: starlingx-discuss(a)lists.starlingx.io Subject: Re: [Starlingx-discuss] cpu mode it is impossible to set a EPIC (or any other AMD) as guest CPU? $ openstack flavor set --property hw:cpu_model=EPYC-IBPB 76609f7b-f0c7-48ca-8c8a-f78481e62cd4 Failed to set flavor property: Invalid hw:cpu_model 'EPYC-IBPB', must be one of: Passthrough, Conroe, Penryn, Nehalem, Westmere, SandyBridge, IvyBridge, Haswell, Broadwell-noTSX, Broadwell, Skylake-Client, Skylake-Server. (HTTP 400) (Request-ID: req-2fda19cc-8e0e-4be8-a8ea-b58fc00358ce) Command Failed: One or more of the operations failed but my compute node seems to support EPIC CPUs? cat /usr/share/libvirt/cpu_map/x86_EPYC-IBRS.xml <cpus> <model name='EPYC-IBPB'> <signature family='23' model='1'/> <vendor name='AMD'/> <feature name='3dnowprefetch'/> .... <feature name='xsavec'/> <feature name='xsaveopt'/> </model> </cpus> some tips for me how to handle this? volker... Von: von Hoesslin, Volker [Volker.Hoesslin(a)swsn.de] Gesendet: Donnerstag, 17. Januar 2019 15:50 An: starlingx-discuss(a)lists.starlingx.io Betreff: [Starlingx-discuss] cpu mode hi, my setup has two computes nodes, every node has a dual AMD EPYC 7601 CPU config. how can i bring all the CPU features (AES, SSSE3, ...) to the guest VMs. i have tryed with some flavor-metadata but nothing realy helps, the VMs getting just a little subset of cpu-features. some investigations to the kvm-settings hit me to the facts that my nova config has "cpu_model=none" !? how can i fix that and bring my AMD EPIC CPU to my nova-config?! here is the host /proc/cpuinfo processor : 127 vendor_id : AuthenticAMD cpu family : 23 model : 1 model name : AMD EPYC 7601 32-Core Processor stepping : 2 microcode : 0x8001227 cpu MHz : 1200.000 cache size : 512 KB physical id : 1 siblings : 64 core id : 31 cpu cores : 32 apicid : 127 initial apicid : 127 fpu : yes fpu_exception : yes cpuid level : 13 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb rdtscp lm constant_tsc art rep_good nopl nonstop_tsc extd_apicid amd_dcm aperfmperf eagerfpu pni pclmulqdq monitor ssse3 fma cx16 sse4_1 sse4_2 movbe popcnt aes xsave avx f16c rdrand lahf_lm cmp_legacy svm extapic cr8_legacy abm sse4a misalignsse 3dnowprefetch osvw skinit wdt tce topoext perfctr_core perfctr_nb bpext perfctr_l2 cpb hw_pstate retpoline_amd ssbd ibpb vmmcall fsgsbase bmi1 avx2 smep bmi2 rdseed adx smap clflushopt sha_ni xsaveopt xsavec xgetbv1 clzero irperf xsaveerptr arat npt lbrv svm_lock nrip_save tsc_scale vmcb_clean flushbyasid decodeassists pausefilter pfthreshold avic v_vmsave_vmload vgif overflow_recov succor smca bogomips : 4400.08 TLB size : 2560 4K pages clflush size : 64 cache_alignment : 64 address sizes : 48 bits physical, 48 bits virtual power management: ts ttp tm hwpstate cpb eff_freq_ro [13] [14] greez & thx, volker... _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss(a)lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss(a)lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss

2 2