WinServer2016 guest no mouse in VirtManager
by John McInnes
Hi! I recently converted several Windows Server VMs from HyperV to libvirt/KVM. The host is running openSUSE Leap 15.3. I used virt-v2v and I installed virtio drivers on all of them and it all went well - except for one VM. The mouse does not work for this VM in VirtualMachineManager. There is no cursor and no response. There are no issues showing in Windows Device Manager. The mouse shows up as a PS/2 mouse. Interestingly if I RDP into this VM using Microsoft Remote Desktop the mouse works fine. Any ideas?
----
John McInnes
jmcinnes /\T svt.org
1 year, 5 months
[libvirt-users] [virtual interface] detach interface during boot succeed with no changes
by Yalan Zhang
Hi guys,
when I detach an interface from vm during boot (vm boot not finished), it
always fail. I'm not sure if there is an existing bug. I have
confirmed with someone that for disk, there is similar behavior, if
this is also acceptable?
# virsh destroy rhel7.2; virsh start rhel7.2 ;sleep 2; virsh
detach-interface rhel7.2 network 52:54:00:98:c4:a0; sleep 2; virsh
dumpxml rhel7.2 |grep /interface -B9
Domain rhel7.2 destroyed
Domain rhel7.2 started
Interface detached successfully
<address type='pci' domain='0x0000' bus='0x00' slot='0x06'
function='0x0'/>
</controller>
<interface type='network'>
<mac address='52:54:00:98:c4:a0'/>
<source network='default' bridge='virbr0'/>
<target dev='vnet0'/>
<model type='rtl8139'/>
<alias name='net0'/>
<address type='pci' domain='0x0000' bus='0x00' slot='0x03'
function='0x0'/>
</interface>
When I detach after the vm boot, expand the sleep time to 10, it will succeed.
# virsh destroy rhel7.2; virsh start rhel7.2 ;sleep 10; virsh
detach-interface rhel7.2 network 52:54:00:98:c4:a0; sleep 2; virsh
dumpxml rhel7.2 |grep /interface -B9
Domain rhel7.2 destroyed
Domain rhel7.2 started
Interface detached successfully
-------
Best Regards,
Yalan Zhang
IRC: yalzhang
Internal phone: 8389413
1 year, 10 months
Storage Pool - NFS v4.1
by Charles Koprowski
Hello,
In order to use pNFS which is only available in NFS version 4.1, I'm trying
to create a netfs storage pool specifying the protocol version to be used :
<pool type="netfs">
<name>vms</name>
<source>
...
<format type="nfs"/>
<protocol ver='4.1'/>
</source>
<target>
...
</pool>
But the storage pool XML documentation [1] states that :
protocol
For a netfs Storage Pool provide a mechanism to define which NFS protocol
version number will be used to contact the server's NFS service. The
attribute ver accepts an unsigned *integer* as the version number to use.
And indeed, when I try to virsh pool-define I get :
error: Failed to define pool from pool.xml
error: XML error: storage pool protocol ver '4.1' is malformed
How can I specify the desired NFS minor version to libvirt ?
I could mount the NFS share myself and build a dir storage pool on top of
it but that's not very pretty.
Thank you,
[1] https://libvirt.org/formatstorage.html
--
Charles
2 years
Domain XML and VLAN tagging
by Gionatan Danti
Hi all,
from here [1]:
"Network connections that support guest-transparent VLAN tagging include
1) type='bridge' interfaces connected to an Open vSwitch bridge Since
0.10.0 , 2) SRIOV Virtual Functions (VF) used via type='hostdev' (direct
device assignment) Since 0.10.0 , and 3) SRIOV VFs used via
type='direct' with mode='passthrough' (macvtap "passthru" mode) Since
1.3.5 . All other connection types, including standard linux bridges and
libvirt's own virtual networks, do not support it."
I read it correctly that when used on a classical linux bridge these
vlan tags does nothing? If so, it is due to something related to the
underlying bridge device (ie: incomplete support for vlan filtering) or
it is because libvirt lacks the necessary "plumbing" to use advanced
bridge features?
Thanks.
[1]
https://libvirt.org/formatdomain.html#setting-vlan-tag-on-supported-netwo...
--
Danti Gionatan
Supporto Tecnico
Assyoma S.r.l. - www.assyoma.it
email: g.danti(a)assyoma.it - info(a)assyoma.it
GPG public key ID: FF5F32A8
2 years, 1 month
managed save returns "migration with virtiofs device is not supported"
by Francesc Guasch
Hello. I have a virtual machine with a virtiofs entry configured.
When I try to do a managed save it fails with this message:
libvirt error code: 55, message: Requested operation is not valid:
migration with virtiofs device is not supported
This is libvirt 8.0.0 that comes with Ubuntu 22.04. I have seen
the current release in git is libvirt 8.5 . I will try to build
from source and try again if you think this was not the expected
behaviour.
This is the filesystem entry:
<filesystem type='mount' accessmode='passthrough'>
<driver type='virtiofs'/>
<source dir='/home/shared'/>
<target dir='home_shared'/>
<address type='pci' domain='0x0000' bus='0x01' slot='0x00'
function='0x0'/>
</filesystem>
Sorry if this is not the right place to ask. I can write an
issue in gitlab or whatever is more appropriate.
Thanks !
2 years, 1 month
managed save returns "migration with virtiofs device is not supported"
by Francesc Guasch
Hello. I have a virtual machine with a virtiofs entry configured.
When I try to do a managed save it fails with this message:
libvirt error code: 55, message: Requested operation is not valid:
migration with virtiofs device is not supported
This is libvirt 8.0.0 that comes with Ubuntu 22.04. I have seen
the current release in git is libvirt 8.5 . I will try to build
from source and try again if you think this was not the expected
behaviour.
This is the filesystem entry:
<filesystem type='mount' accessmode='passthrough'>
<driver type='virtiofs'/>
<source dir='/home/shared'/>
<target dir='home_shared'/>
<address type='pci' domain='0x0000' bus='0x01' slot='0x00'
function='0x0'/>
</filesystem>
Sorry if this is not the right place to ask. I can write an
issue in gitlab or whatever is more appropriate.
Thanks !
2 years, 1 month
After restarted libvirtd service, live migration VM hit an issue 'Target CPU check default does not match source none'
by 梁朝军
Hi All,
After restarted the libvirtd service on the source host, we start live migration VM to destination host and often hit an issue 'unsupported configuration: Target CPU check default does not match source none’
We don’t configure any special setting for CPU model when start VM and I think it should be ‘custom’ mode by default . Furthermore , those two hosts for doing live migration have almost the same capabilities as below.
It’s confused me why failed to check the cpu configuration after restart libvitd service on source host?
The libvirt version is 7.9.0, package: 1.el8 (Unknown, 2021-11-28-22:35:11) private build
Host OS version : rhat8.4
QEMU version: QEMU 5.1 private build
Any comments are appreciated.
Thanks
2 years, 1 month
Domain XML of a restored VM
by Tomáš Golembiovský
Hi,
I am looking for clarification on what exactly is happening to the
domain XML when resuming a suspended VM. We would like to make sure we
don't lose any configuration and we also see some unexpected behavior.
The VM with the name/UUID same as resumed VM may or may not already
exist. If it does, what role does the original domain XML of a VM play
when resuming? Is there any merging taking place between the existing
domain XML and the domain XML stored in save image? Is the original XML
simply thrown away and replaced?
Is there any difference how the stored XML is treated compared to the
XML passed in `virDomainRestoreFlags()`? I see some unexpected changes
here. When I use `virDomainSaveImageGetXMLDesc()` to retrieve the stored
XML and pass it unchanged to the `virDomainRestoreFlags()` the final
domain XML is different then when `virDomainRestore()` is used or when
`virDomainRestoreFlags()` with no `dxml` argument is used. We have:
<graphics ... passwdValidTo='1970-01-01T00:00:01'>
in the domain XML and the `passwdValidTo` argument disappears when
domain XML is passed in `dxml` argument but it is preserved in other
cases. Is this behavior expected? If yes, can we do anything to preserve
the configuration? What other changes in domain XML can be expected?
Thanks,
Tomas
--
Tomáš Golembiovský <tgolembi(a)redhat.com>
2 years, 1 month
