Difference between revisions of "Virt-install (Windows)"
Jump to navigation
Jump to search
| Line 3: | Line 3: | ||
Example Virtual Machine using virtio: | Example Virtual Machine using virtio: | ||
| − | <code>[[virt-install]] --autostart --check all=on --name YOUR_VM_MACHINE --memory VM_MEMORY --vcpus VM_CPUs --[[os-variant]] ubuntu18.04 --cdrom VM_INSTALLATION_MEDIA --disk /path/libvirt/VM_STORAGE_POOL_NAME/YOUR_VM_MACHINE.qcow2 --graphics vnc,listen=0.0.0.0 --noautoconsole --wait TIME_TO_WAIT --network type=direct,source=eno111,source_mode=bridge,model=[[virtio]]</code> | + | <code>[[virt-install]] [[--autostart]] --check all=on --name YOUR_VM_MACHINE --memory VM_MEMORY --vcpus VM_CPUs --[[os-variant]] ubuntu18.04 --cdrom VM_INSTALLATION_MEDIA --disk /path/libvirt/VM_STORAGE_POOL_NAME/YOUR_VM_MACHINE.qcow2 --graphics vnc,listen=0.0.0.0 --noautoconsole --wait TIME_TO_WAIT --network type=direct,source=eno111,source_mode=bridge,model=[[virtio]]</code> |
Revision as of 17:22, 5 November 2021
Contents
--network virtio
Example Virtual Machine using virtio:
virt-install --autostart --check all=on --name YOUR_VM_MACHINE --memory VM_MEMORY --vcpus VM_CPUs --os-variant ubuntu18.04 --cdrom VM_INSTALLATION_MEDIA --disk /path/libvirt/VM_STORAGE_POOL_NAME/YOUR_VM_MACHINE.qcow2 --graphics vnc,listen=0.0.0.0 --noautoconsole --wait TIME_TO_WAIT --network type=direct,source=eno111,source_mode=bridge,model=virtio
See os-variant: win2k19, win2k16, win2k3, win10
--graphics vnc
https://docs.openstack.org/image-guide/virt-install.html
1) qemu-img create -f qcow2 IMAGE_NAME.qcow2 10G 2) virt-install --virt-type=kvm --name MY_VMNAME --ram 1024 --disk /path/to/your/precreated_image/IMAGE_NAME.qcow2,format=qcow2 --network network=default --graphics vnc,listen=0.0.0.0 --noautoconsole --os-type=windows --os-variant=win10 --cdrom=/path/to/windowsimg/Win10_1909_EnglishInternational_x64.iso Starting install... Domain installation still in progress. You can reconnect to the console to complete the installation process. 3) virsh vncdisplay MY_VMNAME :3 4) Use VNC Client to connect. Ports: (1 -> 5901, 2 -> 5902, .../...)
--graphics spice
1) qemu-img create -f qcow2 IMAGE_NAME.qcow2 10G 2) virt-install --name=MY_NEW_VMNAME --os-type=windows --disk path=/path/to/your/precreated_image/IMAGE_NAME.qcow2 --cdrom=/path/to/your/iso/Win10_1909_EnglishInternational_x64.iso --graphics spice --ram=1024 Starting install... Domain installation still in progress. Waiting for installation to complete. 3) virsh vncdisplay MY_NEW_VMNAME error: Failed to get VNC port. Is this domain using VNC?
Virt-install with errors
virt-install --connect=qemu:///system --name=mywin --os-type=windows -r 1024 --cpus=1 --os-variant=win2k3 --hvm --cdrom=/path/to/en_windows_2k3.iso --disk path=/path/to/win2k3.img --accelerate --network=bridge:br0 --vnc
WARNING Graphics requested but DISPLAY is not set. Not running virt-viewer. WARNING No console to launch for the guest, defaulting to --wait -1
WARNING Graphics requested but DISPLAY is not set. Not running virt-viewer. WARNING No console to launch for the guest, defaulting to --wait -1 Starting install... ERROR Cannot get interface MTU on 'br0': No such device Domain installation does not appear to have been successful. If it was, you can restart your domain by running: virsh --connect qemu:///system start mywin otherwise, please restart your installation.
ERROR Cannot read CA certificate '/etc/pki/CA/cacert.pem': No such file or directory
WARNING Graphics requested but DISPLAY is not set. Not running virt-viewer. WARNING No console to launch for the guest, defaulting to --wait -1
Starting install... ERROR internal error: process exited while connecting to monitor: 2020-02-05T10:13:42.360993Z qemu-system-x86_64: -device ide-cd,bus=ide.0,unit=1,drive=drive-ide0-0-1,id=ide0-0-1,bootindex=1: Failed to get shared "write" lock Is another process using the image? Domain installation does not appear to have been successful. If it was, you can restart your domain by running: virsh --connect qemu:///system start MY_DOMAIN otherwise, please restart your installation.
Activities
- Install virtio-win
- Change an existing interface to
virtio: https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/7/html/virtualization_deployment_and_administration_guide/sect-kvm_para_virtualized_virtio_drivers-using_kvm_virtio_drivers_for_nic_devices
See also
- Certified Windows drivers for KVM guests in Canonical Advantage
- Microsoft Windows: Windows 10, Windows 11, Windows Server, Windows IoT, Windows Server containers, RDP, Windows Update, Windows Defender, Windows Unified Write Filter (UWF), ReFS,
Start-Service, Stop-Service, Set-Service, DISM, SFC, systeminfo, Microsoft Hyper-V, WSL, Windows Terminal, Windows Subsystem for Linux (WLS), Windows Server 2022, PowerShell,logoff,query user, WLMS, File explorer, Copy-Item, BitLocker, Cmdlet,choco, scoop, Windows VSS - Virtio, Install virtio-win
virtinst(package):virt-install,virt-clone,virt-convertandvirt-xmllibguestfs-tools:virt-sysprep,virt-clone,virt-builder,virt-customize,virt-resize,virt-rescue,virt-sparsify,guestmount,guestfish,virt-inspector,virt-cat,virt-log,virt-df,virt-ls,virt-filesystems,virt-list-filesystems,virt-edit- KVM, Installation, QEMU,
virsh,virtinst,libguestfs-tools, libvirt, qemu, Red Hat Virtualization (RHV), MacVTap, Virtio, oVirt, KVM services, KVM networking, KVM graphics, CPU, KVM on ARM
Advertising:
