Host network conflicting with guests network
by bd730c5053df9efb
Hi all!
I have a question about networking and haven't been able to find it online. I need to replicate a server installation in a host to be able to test a procedure but the host is on the same network as the servers so I am not being able to create an isolated network on the host because there is an interface in the same range of ip adresses. Is there any way to create this isolated virtual network without it conflicting with the hosts network?
Thanks in advance!
Best regards,
Dave.
Sent with Proton Mail secure email.
7 hours, 32 minutes
libvirtError with pipewire audio backend
by Karl Frederick Roldan
Hi everyone,
I'm having trouble regarding using the pipewire backend for libvirt. My
OS is GNU Guix with Wayland and pipewire running with wireplumber on a
user session. I have the following versions:
libvirt-9.10.0 (with pipewire enabled)
qemu-8.2.2 (with pipewire enabled)
libpipewire-1.0.3
I only modified the =<audio>= configuration in the xml file using =sudo
virsh edit win10= as follows:
<audio id='1' type='pipewire' runtimeDir='/run/user/1000'/>
I can confirm that pipewire is running and that I have pipewire sockets
in the directory specified. But when running the VM using virt-manager,
I get the following error:
Error starting domain: internal error: process exited while
connecting to monitor: 2024-09-17T05:54:03.785811Z qemu-system-x86_64:
Failed to initialize PW context
Traceback (most recent call last):
File
"/gnu/store/nxpr6npj618pqmlanqqh7ks9a92jgm98-virt-manager-4.1.0/share/virt-manager/virtManager/asyncjob.py",
line 72, in cb_wrapper
callback(asyncjob, *args, **kwargs)
File
"/gnu/store/nxpr6npj618pqmlanqqh7ks9a92jgm98-virt-manager-4.1.0/share/virt-manager/virtManager/asyncjob.py",
line 108, in tmpcb
callback(*args, **kwargs)
File
"/gnu/store/nxpr6npj618pqmlanqqh7ks9a92jgm98-virt-manager-4.1.0/share/virt-manager/virtManager/object/libvirtobject.py",
line 57, in newfn
ret = fn(self, *args, **kwargs)
File
"/gnu/store/nxpr6npj618pqmlanqqh7ks9a92jgm98-virt-manager-4.1.0/share/virt-manager/virtManager/object/domain.py",
line 1402, in startup
self._backend.create()
File
"/gnu/store/yaqxaja0ckyf6fm7gnd9iqlrijz6qcqy-python-libvirt-10.6.0/lib/python3.10/site-packages/libvirt.py",
line 1362, in create
raise libvirtError('virDomainCreate() failed')
libvirt.libvirtError: internal error: process exited while
connecting to monitor: 2024-09-17T05:54:03.785811Z qemu-system-x86_64:
Failed to initialize PW context
If I switch the audio backend back to =spice=, the VM will run but
there's no sound. I am not sure if this is a virt-manager problem or I
somehow misconfigured libvirt. How should I proceed about this problem?
1 day, 10 hours
About virsh(1) and Postcopy migration
by Prasad Pandit
Hello,
* virsh(1) offers multiple options to initiate Postcopy migration:
1) virsh migrate --postcopy --postcopy-after-precopy
2) virsh migrate --postcopy + virsh migrate-postcopy
3) virsh migrate --postcopy --timeout <N> --timeout-postcopy
When Postcopy migration is invoked via options (2) or (3) above, the migrated guest on the destination host hangs sometimes. But such a hang is not reproducible with option (1) above.
* When using option (1) above, libvirtd(8) waits for the first pass of pre-copy to finish before enabling postcopy migration.
* Does the same waiting happen when using options (2) and (3) above?
===
2024-07-24 14:16:27.448+0000: msg={"execute":"migrate"
2024-07-24 14:16:29.318+0000: msg={"execute":"migrate-start-postcopy"
2024-07-24 14:28:39.737+0000: msg={"execute":"migrate"
2024-07-24 14:28:41.119+0000: msg={"execute":"migrate-start-postcopy"
2024-07-24 14:44:11.684+0000: msg={"execute":"migrate"
2024-07-24 14:44:12.835+0000: msg={"execute":"migrate-start-postcopy"
2024-07-24 14:48:00.675+0000: msg={"execute":"migrate"
2024-07-24 14:48:02.319+0000: msg={"execute":"migrate-start-postcopy"
2024-07-24 15:03:36.110+0000: msg={"execute":"migrate"
2024-07-24 15:03:37.341+0000: msg={"execute":"migrate-start-postcopy"
2024-07-24 16:05:25.602+0000: msg={"execute":"migrate"
2024-07-24 16:05:26.756+0000: msg={"execute":"migrate-start-postcopy"
===
* While running migration tests with options (2) and (3) above, switch to postcopy appears to happen within 2 seconds of starting migration.
- Is that reasonable time to switch from pre-copy to postcopy?
- Is there an ideal time to wait before switching to postcopy?
* The feature page below suggests to wait until one cycle of RAM migration has completed
-> https://wiki.qemu.org/Features/PostCopyLiveMigration
* I'd much appreciate any clarification/confirmation about this.
Thank you.
---
-Prasad
2 weeks
Possible issue with shared folder from host to virtual machine
by Mulloch94＠protonmail.com
I ran into an issue when trying to connect a shared folder from my host to my virtual OS in KVM. The folder actually does appear in the virtual OS, but it's empty, unlike the folder in the host which has files in it. I'm not ruling out the possibility that I configured something wrong, but the instructions on setting it up seemed to be pretty straightforward. Basically I did the following procedures:
mkdir ~/shared
chmod 777 ~/shared
Went to VirtManager enabled shared memory, added FileSystem with driver virtiofs. My source path to find the folder was /home/username/shared and the target path was /mnt/shared.
Upon booting the virtual machine everything seemed to work. I found the folder where it should be, only there was nothing in it. And on the host there was files I had already placed in the folder. So this is where I'm at now.
2 weeks, 1 day
