April 2023 - Users - libvirt List Archives

[libvirt-users] bridge / ubuntu / no arp reply
by François Chenais 15 Oct '26

15 Oct '26

Hello I'm trying to setup a bridged guest on an ubuntu 13.10 but it doesn't work. (Everything is ok with NAT) Network sniffing shows that arp replies don't come back to the guest. Test 1 ------ Guest : ping host_bridge_ip (ok) Test 2 ------ Guest: ping other_lan_host (KO) other_lan_host - receives arp who-is request - sends arp reply - arp -a shows the guest macaddr => Guest doesn't receive reply Test 3 ------ other_lan_host ping the Guest (KO) - arp -a shows "incomplete" addr - Guest receives nothing On Host ------- network tcpdump on bridge or vnet interfaces shows request but no reply ... Thanks in advance for help or ideas François

3 4

Libvirt
by Gk Gk 26 Oct '23

26 Oct '23

Hi All, I am trying to collect memory, disk and network stats for a VM on kvm host. It seems that the statistics are not matching what the OS inside the VM is reporting. Why is this discrepancy ? Is this a known bug of libvirt ? Also I heard that libvirt shows cumulative figures for these measures ever since the VM was created. Also I tested by creating a new vm and comparing the stats without a reboot . Even in this case, the stats dont agree. Can someone help me here please ? Thanks Kumar

2 5

PHP API
by Simon Fairweather 03 May '23

03 May '23

Hi Michal Are there plans to implement snapshot create_as version of the following function where XML could be passed? https://github.com/libvirt/libvirt-php/blob/afe404b2cf4bb46cdd39c6ea4df1c7c… Regards Simon.

2 1

UEFI and External Snapshots
by Simon Fairweather 27 Apr '23

27 Apr '23

Is there a plan to support UEFI and Ext Snaps? Or is there a location for documentation as the info I can find is quite old.

2 2

seclabel & fuse
by lejeczek 24 Apr '23

24 Apr '23

Hi guys. Wtih images stored on fuse-mounded storage - does it make sense to try 'seclabel', does it even work? Are there any other techniques which would help to add that/similar layer of security when fuse is used? many thanks, L.

1 0

ecrypting image file breaks efi/boot of the guest/Ubuntu - ?
by lejeczek 20 Apr '23

20 Apr '23

Hi guys. I've have a guest and that guest differs from all other guest by: <os> <type arch='x86_64' machine='pc-q35-rhel9.0.0'>hvm</type> <loader readonly='yes' secure='yes' type='pflash'>/usr/share/edk2/ovmf/OVMF_CODE.secboot.fd</loader> <nvram>/var/lib/libvirt/qemu/nvram/ubusrv1_VARS.fd</nvram> <boot dev='hd'/> <bootmenu enable='yes'/> </os> whereas everything else has: <os> <type arch='x86_64' machine='pc-q35-rhel9.0.0'>hvm</type> <boot dev='hd'/> <boot dev='cdrom'/> <bootmenu enable='yes'/> </os> Now, that different guest fails - as the only one - to start, to boot after its qcow2 image was luks-encrypted. Guest starts but says that: BdsDxe: failed to load Boot0001 "Uefi Misc Device" from PciRoot (0x0)/Pci(0x2,0x3)/Pci(0x0,0x0): Not found revert back to original, non-encrypted qcow2 image and all works a ok. All and any thoughts shared are much appreciated. many thanks, L.

2 7

which daemon/service for live migration - ?
by lejeczek 19 Apr '23

19 Apr '23

Hi guys. With this relatively new modular approach in libvirt - which service is needed in order to migrate guests via tcp? many thanks, L.

3 11

storage backup with encryption on-the-fly ?
by lejeczek 11 Apr '23

11 Apr '23

Hi guys. Is there a solution, perhaps a function of libvirt, to backup guest's storage and encrypt the resulting image file? On-the-fly ideally. If not ready/built-in solution then perhaps a best technique you recommend/use? I currently use 'backup-begin' on qcow2s, which are LUKS encrypted. many thanks, L.

2 4

Virtiofsd
by Simon Fairweather 06 Apr '23

06 Apr '23

Hi In QEMU 8 virtiofsd has been removed in favor of the rust version. Which includes options that are not longer supported, Do you have a view on what should be used going forwards to support virtiofsd in libvirt with qemu 8? The options are showing as depreciated, -o <compat-options>... Options in a format compatible with the legacy implementation [deprecated] Rust version options virtiofsd backend 1.5.1 Launch a virtiofsd backend. USAGE: virtiofsd [FLAGS] [OPTIONS] --fd <fd> --socket <socket> --socket-path <socket-path> FLAGS: --allow-direct-io Honor the O_DIRECT flag passed down by guest applications --announce-submounts Tell the guest which directories are mount points -d Set log level to "debug" [deprecated] -f Compatibility option that has no effect [deprecated] -h, --help Prints help information --killpriv-v2 Enable KILLPRIV V2 support --no-killpriv-v2 Disable KILLPRIV V2 support [default] --no-readdirplus Disable support for READDIRPLUS operations --posix-acl Enable support for posix ACLs (implies --xattr) --print-capabilities Print vhost-user.json backend program capabilities and exit --security-label Enable security label support. Expects SELinux xattr on file creation from client and stores it in the newly created file --syslog Log to syslog [default: stderr] -V, --version Prints version information --writeback Enable writeback cache --xattr Enable support for extended attributes OPTIONS: --cache <cache> The caching policy the file system should use (auto, always, never) [default: auto] -o <compat-options>... Options in a format compatible with the legacy implementation [deprecated] --fd <fd> File descriptor for the listening socket --inode-file-handles=<inode-file-handles> When to use file handles to reference inodes instead of O_PATH file descriptors (never, prefer, mandatory) - never: Never use file handles, always use O_PATH file descriptors. - prefer: Attempt to generate file handles, but fall back to O_PATH file descriptors where the underlying filesystem does not support file handles. Useful when there are various different filesystems under the shared directory and some of them do not support file handles. ("fallback" is a deprecated alias for "prefer".) - mandatory: Always use file handles, never fall back to O_PATH file descriptors. Using file handles reduces the number of file descriptors virtiofsd keeps open, which is not only helpful with resources, but may also be important in cases where virtiofsd should only have file descriptors open for files that are open in the guest, e.g. to get around bad interactions with NFS's silly renaming. [default: never] --log-level <log-level> Log level (error, warn, info, debug, trace, off) [default: info] --modcaps <modcaps> Modify the list of capabilities, e.g., --modcaps=+sys_admin:-chown --rlimit-nofile <rlimit-nofile> Set maximum number of file descriptors (0 leaves rlimit unchanged) [default: min(1000000, '/proc/sys/fs/nr_open')] --sandbox <sandbox> Sandbox mechanism to isolate the daemon process (namespace, chroot, none) [default: namespace] --seccomp <seccomp> Action to take when seccomp finds a not allowed syscall (none, kill, log, trap) [default: kill] --shared-dir <shared-dir> Shared directory path --socket <socket> vhost-user socket path [deprecated] --socket-group <socket-group> Name of group for the vhost-user socket --socket-path <socket-path> vhost-user socket path --thread-pool-size <thread-pool-size> Maximum thread pool size. A value of "0" disables the pool [default: 0] --xattrmap <xattrmap> Add custom rules for translating extended attributes between host and guest (e.g. :map::user.virtiofs.:) Regards Simon.

2 4

backup-begin
by André Malm 06 Apr '23

06 Apr '23

Hello, For some vms the virsh backup-begin sometimes shuts off the vm and returns "error: operation failed: domain is not running" although it was clearly in state running (or paused). Is the idea that you should guest-fsfreeze-freeze / virsh suspend before virsh backup-begin? I have tried with both with the same results. What could be causing the machine to shut off? Thanks, André

2 6