Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.debian.bugs.dist > #1249513

Bug#1107536: [Pkg-libvirt-maintainers] Bug#1107536: PPC64LE: Device hotplug/unplug requires guest reboot

From Andrea Bolognani <eof@kiyuko.org>
Newsgroups linux.debian.bugs.dist
Subject Bug#1107536: [Pkg-libvirt-maintainers] Bug#1107536: PPC64LE: Device hotplug/unplug requires guest reboot
Date 2025-06-09 20:20 +0200
Message-ID <KVPge-9pcb-5@gated-at.bofh.it> (permalink)
References <KVPge-9pcb-7@gated-at.bofh.it> <KVPge-9pcb-7@gated-at.bofh.it>
Organization linux.* mail to news gateway

Show all headers | View raw


[Multipart message — attachments visible in raw view] - view raw

On Mon, Jun 09, 2025 at 09:50:24AM +0530, Trupti wrote:
> Package: libvirt-daemon
> Severity: important
> Tags: trixie ppc64el
> 
> Version Info:
> 
> Host/Guest OS: Debian Trixie/sid (powerpc64le)
> Kernel: 6.12.27-powerpc64le-64k
> QEMU: 10.0.0
> Libvirt: 11.3.0
> 
> Issue:
> 
> Live-attaching or detaching a device with virsh on a Debian Trixie (ppc64le)
> guest does not take effect immediately. While the host command succeeds, the
> guest OS only recognizes the change after a full reboot. This defeats the
> purpose of the hotplug feature.
> 
> Steps to reproduce:
> 1) Start a guest with Debian-Trixie OS same as Host
> 2) Attach an interface to guest using below virsh attach-device command
>    'virsh attach-interface --live vm bridge --source virbr0'
> 3) The command executes successfully and give output as "Interface attached
> successfully"
> 4) But the interface is not immediately attached to guest. When the guest is
> rebooted , then the
>    interface is seen on the guest.
> 5) Same is happening with virsh detach-interface command. A guest reboot is
> required to remove
>    the interface from guest

What's the output of attach-interface if you pass the --print-xml
flag to it? What does the full live XML look like before and after
the operation?

Honestly this sounds like a guest OS issue rather than a bug in
libvirt. Is any message produced in dmesg/journal as a consequence of
the hotplug operation?

-- 
Andrea Bolognani <eof@kiyuko.org>
Resistance is futile, you will be garbage collected.

Back to linux.debian.bugs.dist | Previous | Next — Next in thread | Find similar | Unroll thread


Thread

Bug#1107536: [Pkg-libvirt-maintainers] Bug#1107536: PPC64LE: Device hotplug/unplug requires guest reboot Andrea Bolognani <eof@kiyuko.org> - 2025-06-09 20:20 +0200
  Bug#1107536: [Pkg-libvirt-maintainers] Bug#1107536: PPC64LE: Device hotplug/unplug requires guest reboot Andrea Bolognani <eof@kiyuko.org> - 2025-06-10 20:50 +0200
  Bug#1107536: [Pkg-libvirt-maintainers] Bug#1107536: PPC64LE: Device hotplug/unplug requires guest reboot Andrea Bolognani <eof@kiyuko.org> - 2025-06-20 20:40 +0200
    Re: [Pkg-libvirt-maintainers] Bug#1107536: PPC64LE: Device  hotplug/unplug requires guest reboot Trupti <trupti@linux.ibm.com> - 2025-07-15 11:00 +0200
      Re: [Pkg-libvirt-maintainers] Bug#1107536: PPC64LE: Device  hotplug/unplug requires guest reboot Bastian Blank <waldi@debian.org> - 2025-07-15 11:20 +0200

csiph-web