86_64 host is not supported by hypervisor - 2024

86_64 host is not supported by hypervisor - 2024

[Adam]

TWIMC:

Had an issue with VM networking that turned out to be the host. In the 
process of troubleshooting, I

     sudo apt reinstall libvirt   (and other QEMU/KVM virtualization 
dependencies)

Now I am getting this particular error when trying to use the 
host-passthrough for the CPU.

"error: unsupported configuration: CPU mode 'host-passthrough' for 
x86_64 qemu domain on x86_64 host is not supported by hypervisor"

This was working previously.  I found that two other domains are 
responding the same.

The configuration in xml file is:

     <metadata>
     <libosinfo:libosinfo 
xmlns:libosinfo="http://libosinfo.org/xmlns/libvirt/domain/1.0">
       <libosinfo:os id="http://libosinfo.org/linux/2022"/>
     </libosinfo:libosinfo>
   </metadata>
   <memory unit='KiB'>4194304</memory>
   <currentMemory unit='KiB'>4194304</currentMemory>
   <vcpu placement='static'>2</vcpu>
   <os>
     <type arch='x86_64' machine='pc-q35-7.2'>hvm</type>
     <boot dev='hd'/>
   </os>
   <features>
     <acpi/>
     <apic/>
     <vmport state='off'/>
   </features>
   <cpu mode='host-passthrough' check='none' migratable='on'/>
   <clock offset='utc'>

But i now have to use this for it to work but the system is quite slow now.

  <metadata>
     <libosinfo:libosinfo 
xmlns:libosinfo="http://libosinfo.org/xmlns/libvirt/domain/1.0">
       <libosinfo:os id="http://libosinfo.org/linux/2022"/>
     </libosinfo:libosinfo>
   </metadata>
   <memory unit='KiB'>4194304</memory>
   <currentMemory unit='KiB'>4194304</currentMemory>
   <vcpu placement='static'>2</vcpu>
   <os>
     <type arch='x86_64' machine='pc-q35-5.2'>hvm</type>
     <boot dev='hd'/>
   </os>
   <features>
     <acpi/>
     <apic/>
     <vmport state='off'/>
   </features>
   <cpu mode='custom' match='exact' check='none'>
     <model fallback='forbid'>qemu64</model>
   </cpu>


Any recommendations, given that this used to work.


Traceback error details are below this line:

Error starting domain: unsupported configuration: CPU mode 
'host-passthrough' for x86_64 qemu domain on x86_64 host is not 
supported by hypervisor

Traceback (most recent call last):
   File "/usr/share/virt-manager/virtManager/asyncjob.py", line 72, in 
cb_wrapper
     callback(asyncjob, *args, **kwargs)
   File "/usr/share/virt-manager/virtManager/asyncjob.py", line 108, in 
tmpcb
     callback(*args, **kwargs)
   File "/usr/share/virt-manager/virtManager/object/libvirtobject.py", 
line 57, in newfn
     ret = fn(self, *args, **kwargs)
           ^^^^^^^^^^^^^^^^^^^^^^^^^
   File "/usr/share/virt-manager/virtManager/object/domain.py", line 
1402, in startup
     self._backend.create()
   File "/usr/lib/python3/dist-packages/libvirt.py", line 1373, in create
     raise libvirtError('virDomainCreate() failed')
libvirt.libvirtError: unsupported configuration: CPU mode 
'host-passthrough' for x86_64 qemu domain on x86_64 host is not 
supported by hypervisor


Thank you,

A>AM

Re: 86_64 host is not supported by hypervisor - 2024

[Daniel P. Berrangé]

On Wed, Jan 08, 2025 at 08:51:52AM -0600, Adam wrote:
> TWIMC:
> 
> Had an issue with VM networking that turned out to be the host. In the
> process of troubleshooting, I
> 
>     sudo apt reinstall libvirt   (and other QEMU/KVM virtualization
> dependencies)
> 
> Now I am getting this particular error when trying to use the
> host-passthrough for the CPU.
> 
> "error: unsupported configuration: CPU mode 'host-passthrough' for x86_64
> qemu domain on x86_64 host is not supported by hypervisor"
> 
> This was working previously.  I found that two other domains are responding
> the same.
> 
> The configuration in xml file is:
> 
>     <metadata>

You've omitted the part of the config that shows whether the
guest is configured for 'tcg' or 'kvm'. Given your error
message my guess is that you've got a 'tcg' based guest,
for which '-cpu host' is not available.

With regards,
Daniel
-- 
|: https://berrange.com      -o-    https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org         -o-            https://fstop138.berrange.com :|
|: https://entangle-photo.org    -o-    https://www.instagram.com/dberrange :|

Re: 86_64 host is not supported by hypervisor - 2024

[Adam]

I have backups of the xml and image, and they too report the same issue.

<domain type='kvm'>
   <name>vFRANK</name>
   <uuid>88c29f0e-0d18-42f9-a198-bc9c679fdf8d</uuid>
   <metadata>

On 1/8/25 08:58, Daniel P. Berrangé wrote:
> On Wed, Jan 08, 2025 at 08:51:52AM -0600, Adam wrote:
>> TWIMC:
>>
>> Had an issue with VM networking that turned out to be the host. In the
>> process of troubleshooting, I
>>
>>      sudo apt reinstall libvirt   (and other QEMU/KVM virtualization
>> dependencies)
>>
>> Now I am getting this particular error when trying to use the
>> host-passthrough for the CPU.
>>
>> "error: unsupported configuration: CPU mode 'host-passthrough' for x86_64
>> qemu domain on x86_64 host is not supported by hypervisor"
>>
>> This was working previously.  I found that two other domains are responding
>> the same.
>>
>> The configuration in xml file is:
>>
>>      <metadata>
> You've omitted the part of the config that shows whether the
> guest is configured for 'tcg' or 'kvm'. Given your error
> message my guess is that you've got a 'tcg' based guest,
> for which '-cpu host' is not available.
>
> With regards,
> Daniel

Re: 86_64 host is not supported by hypervisor - 2024

[Daniel P. Berrangé]

On Wed, Jan 08, 2025 at 09:13:47AM -0600, Adam wrote:
> I have backups of the xml and image, and they too report the same issue.
> 
> <domain type='kvm'>
>   <name>vFRANK</name>
>   <uuid>88c29f0e-0d18-42f9-a198-bc9c679fdf8d</uuid>
>   <metadata>

What is reported for

  virt-host-validate qemu
  virsh capabilities --xpath //guest
  virsh domcapabilities --virttype kvm --arch x86_64 --xpath //cpu/mode


With regards,
Daniel
-- 
|: https://berrange.com      -o-    https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org         -o-            https://fstop138.berrange.com :|
|: https://entangle-photo.org    -o-    https://www.instagram.com/dberrange :|

Re: 86_64 host is not supported by hypervisor - 2024

[Adam]

Will respond shortly.  Doing additional troubleshooting at the moment.

I copied in a backup from 02JAN24.  And, I tried to create a new XML for 
same with a different name vFRANK2 vs vFRANK.  Prior to creating it, I 
specified in the virt-manager to use host-passthrough for the cpu.  
However, upon creating the new XML based on the original .qcow2 file, it 
still changed the CPU back to qemu default instead of host-passthrough.

Regards,

A>AM


On 1/8/25 09:22, Daniel P. Berrangé wrote:
> On Wed, Jan 08, 2025 at 09:13:47AM -0600, Adam wrote:
>> I have backups of the xml and image, and they too report the same issue.
>>
>> <domain type='kvm'>
>>    <name>vFRANK</name>
>>    <uuid>88c29f0e-0d18-42f9-a198-bc9c679fdf8d</uuid>
>>    <metadata>
> What is reported for
>
>    virt-host-validate qemu
>    virsh capabilities --xpath //guest
>    virsh domcapabilities --virttype kvm --arch x86_64 --xpath //cpu/mode
>
>
> With regards,
> Daniel