r, which links to all the
relevant information. It seems to do its job, seeing as you managed
to find your way to the mailing list after all :)
[1]
https://lists.libvirt.org/archives/list/de...@lists.libvirt.org/thread/FZT5AKOI5VT6PTYTDKUF32RFILKRACEX/
--
Andrea Bolognani / Red Hat / Virtualizati
uspicious. There are a few things that differ
between x86_64 and aarch64, but this shouldn't be one of them.
Are you 100% sure that the two environments are identical, modulo the
architecture? Honestly, what seems a lot more likely is that either
the Ansible playbooks execute some task
On Tue, Feb 20, 2024 at 02:04:11PM -0500, Chuck Lever wrote:
> On Tue, Feb 20, 2024 at 10:58:46AM -0800, Andrea Bolognani wrote:
> > On Tue, Feb 20, 2024 at 10:17:43AM -0500, Chuck Lever wrote:
> > > On Mon, Feb 19, 2024 at 07:18:06PM -0500, Laine Stump wrote:
> > > &
; networks and
> > > > > > > guests.
> > > > > >
> > > > > > These are wrapped up in scripts and ansible playbooks, so I'll have
> > > > > > to dig through that to figure out which connection is being used.
> > > >
On Tue, Feb 27, 2024 at 09:49:23AM -0500, Chuck Lever wrote:
> On Tue, Feb 27, 2024 at 01:20:46AM -0800, Andrea Bolognani wrote:
> > Note that you shouldn't enable both the monolithic daemon (libvirtd)
> > and the modular daemons (virtnetworkd, virtqemud) at the same time.
&g
these files are.
Based on the names, I believe those have been created by libguestfs.
Rich, is it possible that libguestfs doesn't use
VIR_DOMAIN_UNDEFINE_NVRAM when cleaning up after itself?
--
Andrea Bolognani / Red Hat / Virtualization
___
Users mailing list -- users@lists.libvirt.org
To unsubscribe send an email to users-le...@lists.libvirt.org
l libvirt-daemon-system
instead. That should produce a working local installation by bringing
in the clients, the daemon, the QEMU driver as well as QEMU itself.
--
Andrea Bolognani / Red Hat / Virtualization
___
Users mailing list -- users@lists.libvirt.org
To unsubscribe send an email to users-le...@lists.libvirt.org
olves spawning and
subsequently migrating a single VM) yesterday and I could see
warnings about hitting max_client_requests in the logs.
--
Andrea Bolognani / Red Hat / Virtualization
___
Users mailing list -- users@lists.libvirt.org
To unsubscribe send an email to users-le...@lists.libvirt.org
On Thu, Mar 07, 2024 at 05:15:46PM +, Daniel P. Berrangé wrote:
> On Thu, Mar 07, 2024 at 08:45:37AM -0800, Andrea Bolognani wrote:
> > On Thu, Mar 07, 2024 at 03:30:30PM +, Daniel P. Berrangé wrote:
> > > I wonder if something is hitting the 'max_client_requests&#
e, my opinion is that the solution isn't changing libvirt
so that exposing multiple isa-serial devices becomes possible, but
rather enhancing the OpenBSD driver so that it supports virtio-serial
channels, the same way that other operating systems can. The FreeBSD
driver can likely be used as inspiration.
--
Andrea Bolognani / Red Hat / Virtualization
___
Users mailing list -- users@lists.libvirt.org
To unsubscribe send an email to users-le...@lists.libvirt.org
On Mon, May 13, 2024 at 06:38:12AM GMT, Andrea Bolognani wrote:
> What I find weird is that a driver seems to exist already:
>
> https://man.openbsd.org/viocon.4
>
> A few limitations are listed, and I'm not sure whether any of those
> are relevant for this scenario. But
ically define libvirt networks without
> needing to run 'virsh net-define'?
You need to install the file in /etc/libvirt/qemu/networks instead.
If you want the network to be autostarted, you also need to create a
symlink in /etc/libvirt/qemu/networks/autostart that points to the
network
On Thu, Jun 13, 2024 at 09:28:08AM GMT, Laine Stump wrote:
> On 6/12/24 6:42 AM, Andrea Bolognani wrote:
> > On Tue, Jun 11, 2024 at 04:23:33PM GMT, richard.schmitt--- via Users wrote:
> > > Is there a way to statically define libvirt networks without
> > > needi
w fixed. Andrea, can you backport it please?
Apologies for the embarrassing delay. This has now been backported
and will be part of the upcoming Debian 12.8 stable update, due in a
week or so.
https://tracker.debian.org/news/1581461/accepted-libvirt-900-4deb12u2-source-into-proposed-updates
after shim populates the NVRAM. Depends if we can come up with
> a relativel foolproof way to identify this situation.
The need for a full reset (as opposed to shim just creating the
missing entries and moving on) is apparently triggered by the
presence of a TPM, which these days we add by defau
On Sat, Nov 16, 2024 at 02:28:24AM +0800, d tbsky wrote:
> Andrea Bolognani
> > I'd also be surprised if this only affected Windows. Wouldn't Linux
> > guests likely see a similar change in how the device is presented?
>
> I don't understand all the imp
this would have to be an option passed to the
QEMU virtio-blk device or some tunable in the driver.
I'd also be surprised if this only affected Windows. Wouldn't Linux
guests likely see a similar change in how the device is presented?
--
Andrea Bolognani / Red Hat / Virtualization
On Thu, Jan 30, 2025 at 01:20:40PM -0500, Laine Stump wrote:
> On 1/30/25 10:48 AM, Andrea Bolognani wrote:
> > Debian 12 doesn't come with a new enough libvirt version anyway, but
> > FYI a few months back I switched the default backend in Debian to
> > nftables (mat
On Fri, Feb 07, 2025 at 11:09:35AM +, Daniel P. Berrangé wrote:
> On Thu, Jan 30, 2025 at 12:47:41PM -0800, Andrea Bolognani wrote:
> > If things really work the way you describe them, it sounds like an
> > unsolvable problem indeed. Any scenario in which all possible
> >
On Fri, Feb 07, 2025 at 02:59:05PM +, Daniel P. Berrangé wrote:
> On Fri, Feb 07, 2025 at 06:39:50AM -0800, Andrea Bolognani wrote:
> > I'm wondering though, are we sure that e.g. Docker is doing the same
> > thing? My understanding is that if we go through firewalld bu
On Fri, Feb 07, 2025 at 03:48:00PM +, Daniel P. Berrangé wrote:
> On Fri, Feb 07, 2025 at 07:44:02AM -0800, Andrea Bolognani wrote:
> > I'm not sure what Docker does either, but I can tell you for sure
> > that, at least on Debian, switching libvirt to the nftables backen
caveats.
[1] https://bugs.debian.org/1090355
--
Andrea Bolognani / Red Hat / Virtualization
kaging?
>
> Yes, it seems debian is intentionally not shipping them :-(
It's not a matter of intention as much as it is one of resources. I
maintain the Debian package in my spare time and I just haven't
gotten around to implement this specific transition yet. It'll come
eventually.
--
Andrea Bolognani / Red Hat / Virtualization
happening at all on a different host
with an Intel CPU...
Long story short, I configured the guest to use the qemu64 CPU model
and it has been running with zero issues on my AMD host ever since.
That's probably a bit heavy handed and I could have gotten away with
a more recent Intel CPU model, but I didn't have much reason to go
back and revisit the choice.
--
Andrea Bolognani / Red Hat / Virtualization
On Fri, Dec 13, 2024 at 07:12:04AM -0800, Connor Kuehl wrote:
> On 12/13/24 2:18 AM, Andrea Bolognani wrote:
> >> I think something like this is a reasonable fallback:
> >>
> >> $ virsh capabilities | xmllint --xpath '//arch/@name' -
> >
> &g
25 matches
Mail list logo
