DOCSLIB.ORG

Chapter 3 Setting up the Management Server

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Chapter 3 Setting up the Management Server ChangeLog Edition Date of Chapter/Section New/ Changes Issue Change 1 March All New 2018 2 March 2.3. Preparation of the Change Download URL was changed. 2018 software packages to install for the SX-Aurora TSUBASA system 3.1. Installing software Change The reference URL was deleted in 3.1.1. programs Installing Cobbler and 3.1.2. Installing Ansible. 4.3.2.1. The configuration Change The reference URL was deleted. of a kickstart file 5.1.1. Files for Ansible Change vh-set-bmc.yml was deleted. 5.1.2. Tuning Ansible Change The reference URL was deleted. performance 6.1. Controlling power with Change The explanation of the BMC operation BMC user was added. 6.1.1.1. Checking BMC installation and 6.1.1.2. BIOS Configuration on VHs were deleted. A.3.1. VH power control Change Cause and Solution were changed. using the powerctrl commands fails. 3 May 2018 2.3. Preparation of the Change NEC MPI was excluded from the install software packages to target which Ansible is used. NEC install for the SX-Aurora Parallel Debugger was added. TSUBASA system 3.2. Creating a Yum Change "4. Update the group definition file." was repository for SX-Aurora deleted. TSUBASA 5.1.1. Files for Ansible Change roles/nec-mpi was deleted. roles/parallel- debugger was added. 5.2. Installing SX-Aurora Change NEC MPI was excluded from the install TSUBASA system software target which Ansible is used. 5.2.1. Editing Playbook Change nec-mpi was deleted. parallel-debugger was added. 4 May 2018 2.3. Preparation of the Change Description of RHEL7.4 support for software packages to ScaTeFS was added. install for the SX-Aurora NEC MPI was re-supported as install TSUBASA system target with Ansible. 2 Edition Date of Chapter/Section New/ Changes Issue Change 5.1.1. Files for Ansible Change roles/nec-mpi was re-supported. 5.2. Installing SX-Aurora Change NEC MPI was re-supported as install TSUBASA system software target with Ansible. 5.2.1. Editing Playbook Change nec-mpi was re-supported. 5 Jan 2019 1.1. Overview Change "Software installation and environment setup" functions by Ansible suspend support. Trademarks • Linux is a registered trademark of Linus Torvalds in the United States and other countries. • Red Hat and Red Hat Enterprise Linux are registered trademarks of Red Hat, Inc. in the United States and other countries. • Apache is a registered trademark of Apache Software Foundation. • InfiniBand is a trademark or service mark of InfiniBand Trade Association. • Mellanox is trademark or registered trademark of Mellanox Technologies in Israel and other countries. • Ansible is a registered trademark of Red Hat, Inc. in the United States and other countries. • Python is a registered trademark of the Python Software Foundation. • All other product, brand, or trade names used in this publication are the trademarks or registered trademarks of their respective trademark owners. Copyright No part of this document may be reproduced, in any form or by any means, without permission from NEC Corporation. The information in this document is subject to change at any time, without notice. 3 Contents ChangeLog.................................................................................................................................. 2 Trademarks.................................................................................................................................3 Copyright.................................................................................................................................... 3 List of Figures............................................................................................................................ 7 List of Tables..............................................................................................................................8 Chapter 1 Introduction....................................................................................... 9 1.1. Overview..................................................................................................................................9 1.2. Glossary................................................................................................................................... 9 1.3. System Architecture.............................................................................................................. 10 1.4. Operating Environment......................................................................................................... 11 1.5. Sequence of environment setup............................................................................................ 11 Chapter 2 Preparation...................................................................................... 12 2.1. BIOS settings of VHs........................................................................................................... 12 2.2. Preparation of the ISO file to install OS.............................................................................. 12 2.3. Preparation of the software packages to install for the SX-Aurora TSUBASA system........ 12 2.4. Preparing packages SX-Aurora TSUBASA system software programs depend on..............15 2.5. Preparing of the template package........................................................................................16 Chapter 3 Setting up the management server................................................17 3.1. Installing software programs.................................................................................................17 3.1.1. Installing Cobbler.................................................................................................... 17 3.1.2. Installing Ansible.....................................................................................................17 3.1.3. Installing Python......................................................................................................17 3.1.4. Installing Apache HTTP Server..............................................................................17 3.1.5. Installing createrepo................................................................................................ 17 3.2. Creating a Yum repository for SX-Aurora TSUBASA........................................................ 18 3.3. Setting up the Mellanox OFED Yum repository.................................................................. 18 3.4. Creating an administrative user............................................................................................ 19 3.5. Setting administrative user's SSH public and private keys...................................................19 3.6. Installing the template package.............................................................................................20 3.7. Creating the VH information file..........................................................................................20 3.8. Creating host list file.............................................................................................................21 Chapter 4 OS installation on VHs...................................................................22 4.1. Making preparations to use Cobbler.....................................................................................22 4.1.1. Configuration of xinetd server................................................................................ 22 4.1.2. Configuration of rsync server................................................................................. 22 4.1.3. Disabling SELinux and the firewall........................................................................23 4.2. Configuration of Cobbler...................................................................................................... 23 4.2.1. Editing the Cobbler configuration file.................................................................... 23 4.2.2. Configuration of DHCP server............................................................................... 24 4.2.2.1. Basic settings of dhcp.template.................................................................24 4 4.2.2.2. Installation in UEFI boot mode.................................................................24 4.2.2.3. The management server and VH machines on different subnets...............25 4.2.3. Starting the Cobbler server..................................................................................... 25 4.3. Preparation of OS installation...............................................................................................26 4.3.1. Obtaining and storing bootloaders.......................................................................... 26 4.3.2. Editing a kickstart file.............................................................................................26 4.3.2.1. The configuration of a kickstart file..........................................................26 4.3.2.2. Command section...................................................................................... 27 4.3.2.3. Package section..........................................................................................28 4.3.2.4. Script section............................................................................................. 29 4.3.3. Importing ISO image...............................................................................................30 4.3.4. Registration of system.............................................................................................30 4.4. Starting OS installation........................................................................................................
Load more

Recommended publications
  • Compass – a Streamlined Openstack Deployment System
    2013年11月7日星期四 Compass – A Streamlined OpenStack Deployment System Shuo Yang Principal Architect of Cloud Computing, US R&D Center Outline of This Talk 1 Scope of Problem for Compass 2 Compass Explained 3 DRY, Truly Open Deployment 1 Compass at a Glimpse Think Big, Start Small A General System to Deploy Distributed Systems, Extensibility as a Primary Design Goal Not Limited to OpenStack, but Streamlined Our OpenStack Deployment Like a Charm To Be Open Sourced – Apache 2.0 Soon 100% Python, 5000 Line of Python Code Successfully Deployed Several Dogfood Clusters Compass Wiki Page: https://wiki.openstack.org/wiki/Compass 2 Data Center as a Computer Open Cloud OS (OpenStack) Open Deployment (Compass) OpenStackLinux Quantumeth0, lo Nova/proc Cinder/dev Live Auto CD / Deploy GRUB NIC CPU Disk SwitchSwitchSwitch CPUCPUServer DiskStorage NIC CPU Disk (5020) (2285/1285) (N8000/N900) OpenStack Control Channel LILO/GRUB/LiveCD for OpenStack HW/SW Configuration Deployment Channel 3 Why We Are Doing This? Full HW Portfolio in Data Center No.1 as Storage Revenue Growth No. 2 as `x86 Server Revenue Growth Needless to Say, Networking Gears.. OpenStack Makes the Above a Full Global Excellent Telecom Cloud Solution Cloud Solution Provider of year 2012 4 OpenStack Deployment System Overview Crowbar TripleO (“under the cloud” mode) Pioneer effort, a Ruby web app, Chef based Attractive concept to OpenStack folks: configuration management deploy OpenStack from OpenStack Fuel DevStack A great web apps, Puppet based A great tool for simple OpenStack
    [Show full text]
  • Red Hat Satellite 6.3 Architecture Guide
    Red Hat Satellite 6.3 Architecture Guide Planning Satellite 6 Deployment Last Updated: 2019-04-16 Red Hat Satellite 6.3 Architecture Guide Planning Satellite 6 Deployment Red Hat Satellite Documentation Team [email protected] Legal Notice Copyright © 2019 Red Hat, Inc. The text of and illustrations in this document are licensed by Red Hat under a Creative Commons Attribution–Share Alike 3.0 Unported license ("CC-BY-SA"). An explanation of CC-BY-SA is available at http://creativecommons.org/licenses/by-sa/3.0/ . In accordance with CC-BY-SA, if you distribute this document or an adaptation of it, you must provide the URL for the original version. Red Hat, as the licensor of this document, waives the right to enforce, and agrees not to assert, Section 4d of CC-BY-SA to the fullest extent permitted by applicable law. Red Hat, Red Hat Enterprise Linux, the Shadowman logo, JBoss, OpenShift, Fedora, the Infinity logo, and RHCE are trademarks of Red Hat, Inc., registered in the United States and other countries. Linux ® is the registered trademark of Linus Torvalds in the United States and other countries. Java ® is a registered trademark of Oracle and/or its affiliates. XFS ® is a trademark of Silicon Graphics International Corp. or its subsidiaries in the United States and/or other countries. MySQL ® is a registered trademark of MySQL AB in the United States, the European Union and other countries. Node.js ® is an official trademark of Joyent. Red Hat Software Collections is not formally related to or endorsed by the official Joyent Node.js open source or commercial project.
    [Show full text]
  • Automating the Enterprise with Ansible
    AUTOMATING THE ENTERPRISE WITH ANSIBLE Dustin Boyd Solutions Architect September 12, 2017 EVERY ORGANIZATION IS A DIGITAL ORGANIZATION. Today, IT is driving innovation. If you can’t deliver software fast, your organization can’t meet the mission, period. Digital organizations are essentially software. If they expect to thrive in a digital environment, they must have an improved competence in software delivery. Gartner 2015 2 COMPLEXITY KILLS PRODUCTIVITY. Complexity is the enemy of innovation, which is why today’s enterprises are looking to automation and DevOps tools and practices. DevOps can help organizations that are pushing to implement a bimodal strategy to support their digitalization efforts. Gartner 2015 3 WHEN YOU AUTOMATE, YOU ACCELERATE. Ansible loves the repetitive work your people hate. It helps smart people do smarter work. All with fewer errors and better accountability. Automation can crush complexity and it gives you the one thing you can’t get enough of… time. 4 “Ansible delivers DevOps to a broader class of enterprise users that include those inside the business units and teams where agile practices and fast provisioning of infrastructure are in demand.” JAY LYMAN, 451 RESEARCH – NOV 2013 GARTNER COOL VENDOR 2015 “Previous vendors in this [DevOps] market often require unique programming skills. Ansible’s simple language reduces the barrier to adoption and opens it up to a variety of skill sets…” 5 AUTOMATION = ACCELERATION “With Ansible Tower, we just click a button and deploy to production in 5 minutes. It used to take us 5 hours with 6 people sitting in a room, making sure we didn’t do anything wrong (and we usually still had errors).
    [Show full text]
  • Cobbler Provider
    Cobbler Provider The Cobbler provider is used to interact with a locally installed Cobbler (http://cobbler.github.io) service. The provider needs to be congured with the proper credentials before it can be used. Use the navigation to the left to read about the available resources. Example Usage provider "cobbler" { username == "${var.cobbler_username}" password == "${var.cobbler_password}" url == "${var.cobbler_url}" } resource "cobbler_distro" "ubuntu-1404-x86_64" { } Argument Reference The following arguments are supported: username - (Required) The username to the Cobbler service. This can also be specied with the COBBLER_USERNAME shell environment variable. password - (Required) The password to the Cobbler service. This can also be specied with the COBBLER_PASSWORD shell environment variable. url - (Required) The url to the Cobbler service. This can also be specied with the COBBLER_URL shell environment variable. insecure - (Optional) Ignore SSL certicate warnings and errors. This can also be specied with the COBBLER_INSECURE shell environment variable. cacert_file - (Optional) The path or contents of an SSL CA certicate. This can also be specied with the COBBLER_CACERT_FILE shell environment variable. cobbler_distro Manages a distribution within Cobbler. Example Usage resource "cobbler_distro" "ubuntu-1404-x86_64" { name == "foo" breed == "ubuntu" os_version == "trusty" arch == "x86_64" kernel == "/var/www/cobbler/ks_mirror/Ubuntu-14.04/install/netboot/ubuntu-installer/amd64/linux" initrd == "/var/www/cobbler/ks_mirror/Ubuntu-14.04/install/netboot/ubuntu-installer/amd64/initrd.gz" } Argument Reference The following arguments are supported: arch - (Required) The architecture of the distro. Valid options are: i386, x86_64, ia64, ppc, ppc64, s390, arm. breed - (Required) The "breed" of distribution. Valid options are: redhat, fedora, centos, scientic linux, suse, debian, and ubuntu.
    [Show full text]
  • Cobbler Documentation Release 3.0.1
    Cobbler Documentation Release 3.0.1 Enno Gotthold May 27, 2020 Contents 1 Quickstart 3 1.1 Preparing your OS..........................................3 1.2 Changing settings..........................................3 1.3 DHCP management and DHCP server template...........................4 1.4 Notes on files and directories....................................5 1.5 Starting and enabling the Cobbler service..............................5 1.6 Checking for problems and your first sync..............................5 1.7 Importing your first distribution...................................6 2 Install Guide 9 2.1 Prerequisites.............................................9 2.2 Installation.............................................. 10 2.3 RPM................................................. 10 2.4 DEB................................................. 11 2.5 Relocating your installation..................................... 12 3 Cobbler CLI 13 3.1 General Principles.......................................... 13 3.2 CLI-Commands........................................... 14 3.3 EXIT_STATUS............................................ 24 3.4 Additional Help........................................... 24 4 Cobblerd 25 4.1 Preamble............................................... 25 4.2 Description.............................................. 25 4.3 Setup................................................. 26 4.4 Autoinstallation (Autoyast/Kickstart)................................ 26 4.5 Options................................................ 26 5 Cobbler Configuration
    [Show full text]
  • Cobbler Documentation Release 2.8.5
    Cobbler Documentation Release 2.8.5 Jörgen Maas Nov 19, 2020 Contents 1 About 3 1.1 Release Notes.........................................3 1.2 Distribution Support......................................5 1.3 Distribution Notes.......................................7 1.4 How We Model Things..................................... 13 2 Installation 15 2.1 Prerequisites.......................................... 15 2.2 Installing from packages.................................... 16 2.3 Installing from Source..................................... 18 2.4 Configuration Files....................................... 20 2.5 Relocating your installation.................................. 21 3 General 23 3.1 Cobbler Primitives....................................... 23 3.2 Cobbler Direct Commands................................... 54 3.3 Cobbler Settings........................................ 69 3.4 Managing Services with Cobbler............................... 90 3.5 Kickstart Templating...................................... 94 3.6 Snippets............................................ 102 3.7 Package Management and Mirroring............................. 112 3.8 File System Information.................................... 114 4 Advanced 119 4.1 Advanced Networking..................................... 119 4.2 SELinux............................................ 122 4.3 Configuration Management.................................. 123 4.4 Extending cobbler....................................... 131 4.5 Power Management...................................... 135 4.6
    [Show full text]
  • Building and Managing Virtual Machines at the Tier 1
    BuildingBuilding andand managingmanaging virtualvirtual machinesmachines atat thethe TierTier 11 Jason A. Smith, John DeStefano, James Pryor System Workflow: From new unconfigured to fully configured & monitored Install New System PXE boot Cobbler RHEL via system w/ Powered off network install Server kickstart. RHEL Install puppet Reboot Fresh booted FusionInventory Manually tell Contact Puppet system w/ Agent reports on Asset Mgmt GLPI to assign system w/ server Puppet RHEL system's assets Service puppet classes Puppet classes Server send catalog to puppet client Puppet configures & Reports back to system w/ makes changes System server via puppet's Puppet Puppet catalog system via catalog Configured exported resources Server The puppet server gives the Nagios server a new Now Nagios knows about the new machine System config catalog. Nagios & service and will automatically begin to Server monitor it. Configured & monitored CobblerCobbler provisioningprovisioning systemsystem System Provisioning Cobbler & Koan Cobbler is provisioning tool-set that allows for rapid setup & installation of systems through the network. It has both a web GUI and a command line interface. Provisioning with Cobbler: ● Just about all non-LinuxFarm machines are PXE booted & provisioned with Cobbler and it's companion tool koan. ● We use Cobbler as the PXE boot kickstart source for RPM packages. ● During post-install of the kickstart, we register the machine against the local Red Hat Satellite. It becomes the sole repo for packages & updates. ● Satellite allows
    [Show full text]
  • Deployment of Compute Nodes for the WLCG with Cobbler, Ansible and Salt
    Deployment of compute nodes for the WLCG with Cobbler, Ansible and Salt. Damien François, Olivier Mattelaer, Thomas Keutgen HEPiX meeting, October 20 !, "arcelona, #$ain Center for High Performance Computing and Mass Storage ')#M T2%"E%&'( Manneback+)ngrid cluster grows organically ; 1 to 10 machines at a time now 6000+ cores, Gb+10Gb 100 local users + CMS grid users, ~2 M jobs per year Manneback/Ingrid cluster -e started “manuall/0111 check-list shell script config. management make persistent make actionable make idempotent 111 and graduall/ im$rove, automation, and ,ocumentation1 -e settled on three tools 2or the provisioning o2 ne3 nodes Unboxing ● Label, rack, connect ● Choose Name, IP ● Gather MAC 1. Deploy 2. Integrate 3. Confgure Ready for jobs “Cobbler is a Linux installation server that allows for rapid setup of network installation environments.” http://cobbler.github.io Wrapper for PXE, TFTP, DHCP servers Manage OS images, machine profiles Install operating system Setup hardware-specifc confguration (disk partitions, NICs, IPMI, etc.) Setup minimal confguration (Admin SSH keys, Salt minion) “Ansible seamlessly unites workflow orchestration with configuration management, provisioning, and application deployment in one easy-to-use and deploy platform.” https://www.ansible.com Shell scripts on steroïds with builtin safety, idempotence, APIs One-off operations register to Zabbix, GLPI, Salt build files: - slurm.conf for Slurm, - /etc/hosts for dnsmasq, - /etc/ssh/ssh_known_hosts create CPU-specific directory for Easybuild “Scalable, flexible, intelligent IT orchestration and automation” https://saltstack.com Central configuration management server Daily management configure system: NTP, DNS, LDAP, Slurm, etc. install admin software, cvmfs, yum repos, etc. mount user filesystems, cvmfs, etc.
    [Show full text]
  • Automated Installation with the Cobbler Provisioning Tool
    Cobbler BEFN$?FN 8lkfdXk\[`ejkXccXk`fen`k_k_\:fYYc\igifm`j`fe`e^kffc E<NJ?F<J Cobbler helps you install new systems in a hurry. We’ll show you how to use this nifty shoemaker to deploy Xen and VMware virtual machines. BY DAVID NALLEY f you try to install or upgrade several uniform environment and does not take article, I show you how to set up a Cob- computers at once, you will soon into account differences in hardware or bler provisioning system and take a look @discover that manual installation is a function. Also, the image gets out of at the provisioning of virtual machines huge time sink. Even if you are working date over time – with the constant ap- with Cobbler’s helper application Koan. with a checklist, it is often difficult to get pearance of updates, managing the im- Cobbler provides a framework for con- everything installed the same way every ages can become a full-time job. The figuring and managing: time. For this reason, most systems ad- more robust way of provisioning is by ฀ ฀฀฀฀ ministrators understand the importance automatically installing the operating ฀ ฀฀฀฀ of an automated install system. system each time, rather than relying on ฀ ฀฀฀ It’s no surprise that virtually every op- a predefined disk image. This method is ฀ ฀฀฀฀฀฀ erating system has the ability to auto- generally considered more challenging. daemon mate installations. What is curious, The Cobbler project [2], born at Red By managing all the configurations for given the necessity of such systems, is Hat and lead by Michael DeHaan, signifi- all services, Cobbler literally can run an that configuring automated installation cantly lowers the barrier for provisioning entire provisioning network from a sin- typically requires so much time and ef- in Linux.
    [Show full text]
  • Fedora 10 Installation Guide
    Fedora 10 Installation Guide Stuart Ellis Paul W. Frields Fedora 10 Installation Guide by Stuart Ellis and Paul W. Frields Version 9.92 (2008-10-18) Copyright © 2006, 2007, 2008 Red Hat, Inc.Stuart EllisPaul W. Frields Permission is granted to copy, distribute, and/or modify this document under the terms of the Open Publication Licence, Version 1.0, or any later version. The terms of the OPL are set out below. REQUIREMENTSI. ON BOTH UNMODIFIED AND MODIFIED VERSIONS Open Publication works may be reproduced and distributed in whole or in part, in any medium physical or electronic, provided that the terms of this license are adhered to, and that this license or an incorporation of it by reference (with any options elected by the author(s) and/or publisher) is displayed in the reproduction. Proper form for an incorporation by reference is as follows: Copyright (c) <year> by <author's name or designee>. This material may be distributed only subject to the terms and conditions set forth in the Open Publication License, vX.Y or later (the latest version is presently available at http://www.opencontent.org/openpub/). The reference must be immediately followed with any options elected by the author(s) and/or publisher of the document (see section VI). Commercial redistribution of Open Publication-licensed material is permitted. Any publication in standard (paper) book form shall require the citation of the original publisher and author. The publisher and author's names shall appear on all outer surfaces of the book. On all outer surfaces of the book the original publisher's name shall be as large as the title of the work and cited as possessive with respect to the title.
    [Show full text]
  • Integrating with Cobbler
    Integrating with Cobbler Jesus M. Rodriguez Principal Software Engineer Red Hat What is Cobbler? ● A Linux installation server for rapid setup of network install environments ● Can manage ● DHCP ● DNS ● yum repos Objects ● distro ● profile ● system ● repo – package repository for mirroring (optional) ● Image – virt guest image API ● login ● get_{object*(s)} e.g. get_distro, get_profiles ● find_{object*} ● get_{object*}_handle ● remove_{object*} ● copy_{object*} ● rename_{object*} ● new_{object*} ● modify_{object*} ● save_{object*} Language bindings ● Java via cobbler4j ● cobbler4j directory of cobbler checkout ● Ruby via rubygem-cobbler ● contrib/ruby of cobbler checkout ● XML-RPC cobbler4j ● Each cobbler object has a mirror in cobbler4j ● Distro, Profile, Repo, Image, SystemRecord ● Auto-generated from python api ● Operate on the object not the connection ● Requires cobbler 2.0 as it uses xapi_object_edit ● Seeded from Spacewalk code ● Developed because XML-RPC from Java is a pain (as are many things) cobbler4j example XML-RPC ● Cobbler can also be controlled by basic XML- RPC calls ● Most languages have an XML-RPC library ● Python – xmlrpclib ● Perl – FrontierRPC ● Java – Redstone XML-RPC & Apache XML-RPC ● Ruby - xmlrpc python via XML-RPC example Integration Strategies ● Standalone ● Master ● Slave ● Synchronization required Standalone ● Simply use Cobbler as a provisioning service ● Cobbler handles everything ● PXE ● DHCP ● DNS ● Some light integration via scripts Master ● Store all system & provisioning data in Cobbler ● Optionally
    [Show full text]
  • Nested Virtualization Environments
    Deploy and test oVirt using nested virtualization environments Mark Wu [email protected] 1 Agenda ● Nested KVM ● Kickstart & Cobbler ● Kickstart files for VMs ● Install and clone oVirt VMs ● Integration test with Igor ● Q & A 2 Nested Virtualization ● Running multiple unmodified hypervisors with their associated unmodified VM’s ● Why? ● Operating systems are already hypervisors (Windows 7 with XP mode, Linux/KVM) ● To be able to run other hypervisors in clouds ● Live migration of hypervisors and their vms ● Testing, demonstrating, debugging hypervisors and virtualization setups 3 Nested VMX ● Merged in kernel 3.1 ● No hardware support L1 L2 Guest OS ● Multiplex hardware Guest Hypervisor ● Follows the “trap and Memory VMCS emulate” model Table 1-2 State 0-1 State ● Flow: Memory Memory VMCS VMCS 0-2 State ● L0 intercepts the 'vmlaunch' Table Table instruction which L1 execute to run L2 L0 Host Hypervisor ● L0 generates VMCS0-2 by merging VMCS1-2 and Hardware VMCS0-1 and then launches L2 4 How to enable nested KVM? (For VMX) ● Enable the nested switch of kvm_intel.ko ● enable it at runtime ● modprobe -r kvm_intel ● modprobe kvm_intel nested=1 ● Verify ● $cat /sys/module/kvm_intel/parameters/nested => Y ● Persist the change ● echo “options kvm-intel nested=1″>/etc/modprobe.d/kvm- intel.conf ● Qemu command line ● qemu -cpu host ● qemu -cpu qemu64,+vmx 5 How to enable nested KVM? (cont'd) ● Libvirt XML ● Use host CPU model <cpu mode='host-model'/> ● Specify a CPU model <cpu match='exact'> <model>core2duo</model> <feature policy='require'
    [Show full text]