Bug: Domain configuration does not support video model 'qxl'
ahogen opened this issue · comments
$ VAGRANT_DEFAULT_PROVIDER=libvirt vagrant up
Bringing machine 'default' up with 'libvirt' provider...
==> default: Checking if box 'peru/windows-10-enterprise-x64-eval' version '20240201.01' is up to date...
==> default: Creating image (snapshot of base box volume).
==> default: Creating domain with the following settings...
==> default: -- Name: test_win10_default
==> default: -- Description: Source: /path/to/Vagrantfile
==> default: -- Domain type: kvm
==> default: -- Cpus: 2
==> default: -- Feature: acpi
==> default: -- Feature: apic
==> default: -- Feature: pae
==> default: -- Feature (HyperV): name=relaxed, state=on
==> default: -- Feature (HyperV): name=synic, state=on
==> default: -- Feature (HyperV): name=vapic, state=on
==> default: -- Feature (HyperV): name=vpindex, state=on
==> default: -- Clock offset: utc
==> default: -- Memory: 2048M
==> default: -- Base box: peru/windows-10-enterprise-x64-eval
==> default: -- Storage pool: default
==> default: -- Image(vda): /path/to/libvirt-pool/test_win10_default.img, virtio, 50G
==> default: -- Disk driver opts: cache='default'
==> default: -- Graphics Type: spice
==> default: -- Graphics Websocket:
==> default: -- Graphics Port:
==> default: -- Graphics IP:
==> default: -- Graphics Password: Not defined
==> default: -- Video Type: qxl
==> default: -- Video VRAM: 16384
==> default: -- Video 3D accel: false
==> default: -- Sound Type: ich6
==> default: -- Keymap: en-us
==> default: -- TPM Backend: passthrough
==> default: -- INPUT: type=mouse, bus=ps2
==> default: -- CHANNEL: type=spicevmc, mode=
==> default: -- CHANNEL: target_type=virtio, target_name=com.redhat.spice.0
==> default: -- CHANNEL: type=unix, mode=
==> default: -- CHANNEL: target_type=virtio, target_name=org.qemu.guest_agent.0
==> default: -- RNG device model: random
Error while creating domain: Error saving the server: Call to virDomainDefineXML failed: unsupported configuration: domain configuration does not support video model 'qxl'
$ vagrant --version
Vagrant 2.4.1
$ vagrant plugin list
vagrant-libvirt (0.12.1, global)
- Version Constraint: 0.12.1
$ virsh
virsh # version
Compiled against library: libvirt 9.5.0
Using library: libvirt 9.5.0
Using API: QEMU 9.5.0
Running hypervisor: QEMU 8.0.0
$ cat /etc/os-release
NAME="AlmaLinux"
VERSION="9.3 (Shamrock Pampas Cat)"
$ uname -r
5.14.0-362.18.1.el9_3.x86_64
To Reproduce
Expected behavior
Screenshots
Additional context
QXL/SPICE may have been removed from RHEL 9?
Quick workaround...
- disable graphics output
- change video type to libvirt-vagrant plugin default of
cirrus
- disable the libvirt channel named "com.redhat.spice.0"
Vagrant.require_version ">= 2.1.0"
Vagrant.configure("2") do |config|
config.vm.box = "peru/windows-10-enterprise-x64-eval"
config.vm.provider :libvirt do |libvirt|
libvirt.graphics_type = "none";
libvirt.video_type = "cirrus";
libvirt.channel :type => 'spicevmc', :target_name => 'com.redhat.spice.0', :disabled => true
end
end
Thank you Alex.
The code is really old and not tested :-(
I'm no longer able to use GitHub Action to build (and test) the building process, because the GitHub did some major changes in their MacOS GitHub Action Runners.
Anyway - thank you for the feedback.
I'll keep this open and I'm going to update the README.md with the details.
I do not plan to do any major changes to the current templates / code - because it will need new round of changes / testing / troubleshooting / ...
This project may inspire some "packer template" builders, but most of it is outdated + old :-(
Thank you Alex for your suggestion and please please accept my apologies for slow response.
I do not plan to do any other changes to the repository, because it will require testing / fixing old bugs / updating components / etc...
I updated the README.md
with the outdated message: #524
Thank you for understanding...
This issue is stale because it has been open 60 days with no activity.
Remove stale label or comment or this will be closed in 7 days
This issue has not seen any activity since it was marked stale.
Closing.