On Fri, Sep 22, 2023 at 10:48:55AM +, Michael Kjörling wrote:
> On 22 Sep 2023 01:34 -0700, from abolo...@redhat.com (Andrea Bolognani):
> >> If I switch the suspend-to-disk enabled="yes"
> >> I strangely get an error
> >> error: operation failed: Una
irmware/*.json
$
Yeah, the error message is not very helpful. Unfortunately, due to
the way firmware autoselection works, emitting a better one would be
pretty much impossible :(
--
Andrea Bolognani / Red Hat / Virtualization
pite the same input XML.
We generally try fairly hard to avoid this kind of situation, but we
can only really guarantee stable PCI addresses for the lifetime of a
VM that has been defined and can't promise that the same input XML
will result in the same guest ABI when using different versions of
libvirt.
--
Andrea Bolognani / Red Hat / Virtualization
would be worth it.
Please consider moving to Ubuntu 22.04, the current LTS release. The
steps I provided will work there.
--
Andrea Bolognani / Red Hat / Virtualization
hat you mean ...
> gpg: Signature made Sun 17 Jul 2022 09:01:01 AM PDT
> gpg:using RSA key 3B8F2DF67895CA9C771232DFF79E1FC5428583AC
> gpg:issuer "e...@kiyuko.org"
> gpg: Can't check signature: No public key
> Validation FAILED!!
Installi
ackage --no-sign
to actually build the package. Assuming there are no errors, you
should end up with a bunch of .deb files that you can install on the
system using apt-get.
--
Andrea Bolognani / Red Hat / Virtualization
I build a .rpm (rpmbuild -ta) and then install it.
You could grab the source package for the latest version of libvirt
available in Debian, which would be
https://deb.debian.org/debian/pool/main/libv/libvirt/libvirt_8.5.0-1.dsc
right now, and then follow the instructions in
https://wiki.debian.org/BuildingTutorial#Get_the_source_package
to rebuild it locally targeting your release of Ubuntu. Since it's
not insanely old, I expect that would work just fine.
--
Andrea Bolognani / Red Hat / Virtualization
e with new guest's VG
> name of hostname of a already existing, different guest, each time different
> guest.
Have you made sure the disk image didn't exist before calling
virt-install? If it's a leftover from a previous (aborted?)
installation, then the installer might be picking up the VG as
defined earlier instead of creating it from scratch, which would
explain the name.
--
Andrea Bolognani / Red Hat / Virtualization
e software running in the guest that will
process the ACPI event appropriately. systemd will usually take care
of that part.
--
Andrea Bolognani / Red Hat / Virtualization
:) There is no one-size-fits-all
solution.
libvirt follows the "mechanism, not policy" principle: the mechanism
is already available, as documented in the page you were quoting, and
the policy is better implemented in your application. OpenStack is a
good example to follow in this regard.
--
Andrea Bolognani / Red Hat / Virtualization
dition to that, considering that there already entries for
Debian testing and Fedora Rawhide, adding one for Debian unstable
might make sense too.
--
Andrea Bolognani / Red Hat / Virtualization
n11 entry so
that things work as expected when creating a Debian 11 VM on a Debian
11 host? https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=980744 was
AFAICT intended to achieve just that.
--
Andrea Bolognani / Red Hat / Virtualization
the qemu-kvm-block-gluster and
libvirt-daemon-driver-storage-gluster packages have been dropped, but
it's questionable whether this is prominent enough for people to
actually notice.
--
Andrea Bolognani / Red Hat / Virtualization
On Tue, Nov 30, 2021 at 11:06:27AM +, Daniel P. Berrangé wrote:
> On Tue, Nov 30, 2021 at 02:40:07AM -0800, Andrea Bolognani wrote:
> > Michal, have you actually looked at the patch mentioned earlier? If
> > not, you can perhaps do a clean room implementation o
tch I feel
like I couldn't possibly submit it myself and still be in the clear.
--
Andrea Bolognani / Red Hat / Virtualization
rate driver,
and to the best of my knowledge one doesn't currently exist.
Yes, the fact that virtio-9p is sometimes also referred to as
"VirtFS" is extremely confusing :(
All reports of success in that thread seem to come from people who
are using virtiofs, not virtio-9p. You could certainly do the same if
you were using QEMU, but bhyve doesn't have virtiofs support yet.
--
Andrea Bolognani / Red Hat / Virtualization
distant future, but in the meantime other users might be able to
suggest alternative ways to implement host/guest file sharing.
Good luck!
--
Andrea Bolognani / Red Hat / Virtualization
ibb.co/m5vm1hd
> https://ibb.co/Qd6TS5d
> https://ibb.co/3018SGd
I highly recommend changing your OS' language to English before
grabbing screenshots. Limiting the pool of people who might be able
to help you to those who can understand Italian is unlikely to make
things any easier for you ;)
--
Andrea Bolognani / Red Hat / Virtualization
rom source, have a look at the
Dockerfiles in ci/containers: there's one for Ubuntu 20.04, and it
includes the full list of packages you need to install in order to
satisfy all build dependencies.
--
Andrea Bolognani / Red Hat / Virtualization
with attaching disks. All disks are
> attached correctly.
> But we do not know what's the problem with stein. If someone meets the
> problem, you can update your openstack.
>
> Jaze Lee 于2021年10月12日周二 上午9:20写道：
> > Andrea Bolognani 于2021年10月12日周二 上午12:07写道：
> > > O
ugh OpenStack and not
directly, you're more likely to find someone who's able to help you
out if you use the OpenStack support channels.
--
Andrea Bolognani / Red Hat / Virtualization
cess to the read-only socket is usually not very restrictive, since
a read-only connection can only be used to collect data anyway.
--
Andrea Bolognani / Red Hat / Virtualization
one the repo, branch off the v6.0.0 tag, cherry-pick the changes
you're interested in and then generate the archive using 'make
distcheck'.
[1] You could have told us this in the first place instead of asking
a more generic question for which a different answer was more
approp
ocess will break
in interesting ways very quickly. Pretend they don't exist and grab a
proper, signed source tarball from the location Martin pointed you to
instead.
--
Andrea Bolognani / Red Hat / Virtualization
libvirt, it's recommended to
explicitly pass -Dfeature=enabled/disabled for each and every feature
instead of relying on libvirt's autodetection getting things right:
this ensures that the build either exactly matches your expectations
or fails with a useful error message.
--
Andrea Bolognani / Red Hat / Virtualization
building docs? thank you.
Passing -Ddocs=disabled to Meson should do the trick.
--
Andrea Bolognani / Red Hat / Virtualization
On Fri, Jun 04, 2021 at 07:21:59AM +0800, Jiatong Shen wrote:
> Hello community,
>
> I am trying to compile libvirt from source but being trapped with following
> error message when running ninja -C build
>
> ninja -C build
> ninja: Entering directory `build'
> [1/12] Generating
t;
> Centos 8
>
> > What does the
> >
> > Miscellaneous
> > ...
> > Init script: XXX
> >
> > entry look like in the summary that's displayed when you run Meson?
>
> Miscellaneous
> Init script: systemd
These all look good, so I really have no idea what's going on.
Hopefully someone else on the list will be able to help you!
Good luck :)
--
Andrea Bolognani / Red Hat / Virtualization
systemctl daemon-reload
> But the problem persists..
> what will be the problem...
What does running
$ ls /usr/lib/systemd/system/*virt*
output?
What does the
Miscellaneous
...
Init script: XXX
entry look like in the summary that's displayed when you run Meson?
What OS are you using?
--
Andrea Bolognani / Red Hat / Virtualization
thout the parameter even before that.
--
Andrea Bolognani / Red Hat / Virtualization
$ pkg-config --cflags --libs libvirt
If you get an error about libvirt not being found, you probably need
to run
$ export PKG_CONFIG_PATH=/usr/local/lib/pkgconfig
or something along those lines beforehand.
--
Andrea Bolognani / Red Hat / Virtualization
On Mon, 2021-01-04 at 17:22 +0800, tommy wrote:
> Andrea Bolognani wrote:
> > On Thu, 2020-12-24 at 13:38 +0800, tommy wrote:
> > > But, on my system, there are no such service like libvirtd-tls.socket or
> > > libvirtd-tcp.socket.
> > >
> >
bled enabled
This is Debian, but the Ubuntu package is pretty much identical, so I
don't expect it to behave differently.
So the unit exists on you system, you just need to enable it :)
--
Andrea Bolognani / Red Hat / Virtualization
r/local/bin/rst2html5 from the rst2html5 PyPi
package installed on your system, and Meson is apparently picking up
the latter rather than the former.
Please uninstall the PyPi version with "pip uninstall rst2html5" (or
something like that) and try again. Make sure you wipe out the build
directory to force Meson to look for binaries again.
--
Andrea Bolognani / Red Hat / Virtualization
On Fri, 2020-09-25 at 10:26 +0100, Daniel P. Berrangé wrote:
> On Fri, Sep 25, 2020 at 11:23:57AM +0200, Andrea Bolognani wrote:
> > On Fri, 2020-09-25 at 10:16 +0100, Daniel P. Berrangé wrote:
> > > There is a completely different rst2html5 that people might get
> > >
be removed.
Can we do something to get that package off PyPi? It's not the first
time the overlap has caused trouble for our users, and it certainly
won't be the last...
--
Andrea Bolognani / Red Hat / Virtualization
On Fri, 2020-09-25 at 16:21 +0800, Wei Wang wrote:
> On Fri, Sep 25, 2020 at 3:56 PM Andrea Bolognani wrote:
> > On Fri, 2020-09-25 at 10:33 +0800, Wei Wang wrote:
> > > In file included from ../src/util/virfile.c:42:
> > > /usr/include/libutil.h:43:10: fatal error:
n FreeBSD, can you check
which package /usr/include/libutil.h belongs to?
--
Andrea Bolognani / Red Hat / Virtualization
ing for is
See
https://libvirt.org/formatdomain.html#consoles-serial-parallel-channel-devices
for more information about configuring serial devices.
--
Andrea Bolognani / Red Hat / Virtualization
ug working.
The ppc64-specific requirements were documented with
commit 8f474ceea05aec349be19726e394a62e300efe77
Author: Daniel Henrique Barboza
Date: Mon Jul 20 13:51:46 2020 -0300
formatdomain.html.in: mention pSeries NVDIMM 'align down' mechanic
The reason why we align down the guest a
cause of this the libvirt package can't
build-depend on it. It appears that the situation is similar for Arch
as well.
Once the ZFS driver has been built, the corresponding binary package
can have a runtime dependency on the ZFS package, and it will simply
not be installable unless the user has enabled contrib.
--
Andrea Bolognani / Red Hat / Virtualization
; of the file contents ourselves.
There's a bug filed for this:
https://bugzilla.redhat.com/show_bug.cgi?id=1229255
Both you and Dan commented on it at some point, but I thought I'd
bring it up in case you forgot - it was a while ago :)
--
Andrea Bolognani / Red Hat / Virtualization
houldn't be there. But actually, whole autobuild
> script is a bit misleading. The way I build RPMs is autogen.sh + make
> rpm. Would you mind if I remove the autobuild script?
FWIW there were autobuild.sh scripts in most repositories and I have
made an effort to get rid of them something like a year ago, so if
there are any remaining I would certainly welcome removing them.
--
Andrea Bolognani / Red Hat / Virtualization
On Mon, 2020-04-06 at 09:49 +0100, Daniel P. Berrangé wrote:
> On Mon, Apr 06, 2020 at 10:45:49AM +0200, Andrea Bolognani wrote:
> > The plan is to replace our use of nc with a custom virt-nc helper
> > that will link against libvirt on the host side and will thus be able
> &g
use of nc with a custom virt-nc helper
that will link against libvirt on the host side and will thus be able
to use the default socket path appropriate for the system; however,
as far as I'm aware nobody is currently working on it.
--
Andrea Bolognani / Red Hat / Virtualization
the correct
ones in this case are actually
/lib/x86_64-linux-gnu/libnss_libvirt.so.2
/lib/x86_64-linux-gnu/libnss_libvirt_guest.so.2
--
Andrea Bolognani / Red Hat / Virtualization
has no way of knowing, or influencing, what happens
there.
--
Andrea Bolognani / Red Hat / Virtualization
installer-amd64/
Since you're installing from a local .iso image, you need to use
the --cdrom option instead.
That won't work with --extra-args, but luckily the Alpine installer
is smart enough to figure out that there's no graphical console
connected to the guest and use ttyS0 automatically :)
--
Andrea Bolognani / Red Hat / Virtualization
cortex-a53
destroy
restart
destroy
/usr/bin/qemu-system-aarch64
qemu-system-aarch64-4.2.0-2.fc31.x86_64
libvirt-5.10.0-2.fc31.x86_64
virt-manager-2.2.1-2.fc31.noarch
I can run the above and, after some time, get a login prompt on the
serial console.
--
Andrea Bolognani / Red Hat / Virtualization
___
libvirt-u
On Mon, 2019-10-07 at 13:26 +, proc...@riseup.net wrote:
> On 10/7/19 7:31 AM, Andrea Bolognani wrote:
> > On Sat, 2019-10-05 at 14:32 +, proc...@riseup.net wrote:
> > > Hi. I am very interested in the security properties a totally open TPM
> > > ca
pdating the osinfo database through your distro's
package manager is not enough to get the CentOS 8.0 OS variant and
you don't want to replace it with the upstream one,
--os-variant centos7.0
should also work in a pinch.
--
Andrea Bolognani / Red Hat / Virtualization
___
d
for your configuration but the latter is not available :)
Unfortunately it looks like swtpm it's not packaged for Debian, so
I'm afraid the solution is not just a simple apt-get away :(
--
Andrea Bolognani / Red Hat / Virtualization
___
libvirt-us
mply impossible
for anyone to figure out the root cause of the error message you're
seeing. Please share the *exact* changes you made.
--
Andrea Bolognani / Red Hat / Virtualization
___
libvirt-users mailing list
libvirt-users@redhat.com
https://www.redhat.com/mailman/listinfo/libvirt-users
ncluding the
XML that's passed to libvirt. Please attempt the installation again,
capture that output in a plain text file and send it to the list as
an attachment.
Also run
$ /usr/local/bin/qemu-system-x86_64 -machine help
and attach the output of that command, too.
That should help us figure out what'
machine type
> Use -machine help to list supported machines!
My guess would be that your modified QEMU does not support whatever
machine type the guest is configured to use.
What's in the
hvm
element, and is that machine type listed in the output of
qemu-system-x86_64 -machine help
?
--
35.954242Z qemu-system-x86_64:
> > > > -enable-kvm: unsupported machine type
> > > > Use -machine help to list supported machines'
... from the error message it looks like you're using the
/usr/bin/qemu-system-x86_64 binary instead, which does *not* contain
that machine type.
exactly did you change? Can you show both the output of 'virsh
dumpxml ubuntu18.04 --inactive' and the contents of ubuntu18.04.xml?
--
Andrea Bolognani / Red Hat / Virtualization
___
libvirt-users mailing list
libvirt-users@redhat.com
https://www.redhat.com/mailman/listinfo/libvirt-users
On Thu, 2019-04-18 at 15:29 +0100, Daniel P. Berrangé wrote:
> On Thu, Apr 18, 2019 at 04:23:05PM +0200, Andrea Bolognani wrote:
> > qemuDomainAssignAddresses() is supposed to make sure that any address
> > configured explicitly by the user (or previously by libvirt) is
> >
function='0x1'/>
>
>
>
>function='0x2'/>
>
>
>function='0x1'/>
>
>
>
>
>
>
> function='0x0'/>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>function='0x0'/>
>
>
>
>
>
>
--
Andrea Bolognani / Red Hat / Virtualization
___
libvirt-users mailing list
libvirt-users@redhat.com
https://www.redhat.com/mailman/listinfo/libvirt-users
On Thu, 2018-11-01 at 16:40 +0100, Erik Skultety wrote:
> On Wed, Oct 31, 2018 at 05:33:09PM +0100, Martin Kletzander wrote:
> > On Wed, Oct 31, 2018 at 09:32:30AM +0100, Andrea Bolognani wrote:
> > > On Wed, 2018-10-31 at 10:56 +0900, Minjun Hong wrote:
> > > > I se
uri_default = "xen:///"
in /etc/libvirt/libvirt.conf to change the system-wide default URI
without having to mess with environment variables.
--
Andrea Bolognani / Red Hat / Virtualization
___
libvirt-users mailing list
libvirt-users@redhat.com
https://www.redhat.com/mailman/listinfo/libvirt-users
noted that QEMU in general allows users to make pretty
unwise device placement choices without so much of a warning, so I
would not take the above as proof the pcie-to-pci-bridge should be
allowed to plug into pcie-expander-bus (or pcie-root) directly :)
--
Andrea Bolognani / Red Hat / Virtualizat
On Mon, 2018-10-15 at 11:46 +0200, Kashyap Chamarthy wrote:
> On Mon, Oct 15, 2018 at 09:05:16AM +0200, Andrea Bolognani wrote:
> > Interesting. What is the output of 'virsh capabilities'?
>
> In attachment.
Looks reasonable enough.
> > More interesting still is the fact t
On Mon, 2018-10-15 at 08:21 +0200, Kashyap Chamarthy wrote:
> On Sun, Oct 14, 2018 at 02:28:07PM +0200, Andrea Bolognani wrote:
> > If I had to guess, I would say the element of your guest
> > is probably pointing to a custom-built QEMU 2.11 binary rather than
> > the defau
11'
> # echo $?
> 1
>
> * * *
>
> It's getting late, and I should stop staring at screens.
If I had to guess, I would say the element of your guest
is probably pointing to a custom-built QEMU 2.11 binary rather than
the default one installed from RPMs.
--
Andr
On Tue, 2018-10-02 at 10:11 +0200, Gionatan Danti wrote:
> On 02/10/2018 09:19, Andrea Bolognani wrote:
> > Your assessment looks correct, and the controller is indeed compiled
> > out downstream. Filing a BZ sounds like a reasonable next step, but
> > you might also want to
menting your own scripts, at least to the
best of my knowledge. Hopefully someone will prove me wrong, but
I really wouldn't count too much on it :(
--
Andrea Bolognani / Red Hat / Virtualization
___
libvirt-users mailing list
libvirt-users@redhat.com
https://www.redhat.com/mailman/listinfo/libvirt-users
tracked on Bugzilla, it's fairly
common practice to add a comment pointing to the commit(s) once
the relevant code has been merged, which means including a link
to Bugzilla as mentioned above would kind of partially address
this too :)
--
Andrea Bolognani / Red Hat / Virtualization
_
der to use libvirt from Python, you need to have *both*
libvirt itself *and* the Python bindings installed on the system:
libvirt-python doesn't replace libvirt, and in fact can't work at
all unless the C library is available as well.
--
Andrea Bolognani / Red Ha
bindings: on
https://libvirt.org/downloads.html
you can find links for both the C library and modules built on
top of it, including the Python bindings.
--
Andrea Bolognani / Red Hat / Virtualization
___
libvirt-users mailing list
libvirt-users@r
l there. There are a lot of other places
that will need adjusting after that, but it's a good start.
qemu:commandline can be a way out in some cases, but in general
it should be avoided because it's completely opaque to libvirt.
The lsi device is a SCSI controller, so it probably shows up
becau
On Thu, 2017-12-07 at 11:55 -0500, Doug Hughes wrote:
[...]
> from the guest perspective, here's an example from the .xml
>
>
>
>
As a side note, you should only use rtl8139 if your guest OS
literally can't be convinced to work with anything else.
--
A
omeone with access to macOS will have to fix
the issue and post a patch on the development mailing list.
--
Andrea Bolognani / Red Hat / Virtualization
___
libvirt-users mailing list
libvirt-users@redhat.com
https://www.redhat.com/mailman/listinfo/libvirt-users
at 16.04 it should work nicely and,
most importantly, rolling back in case it doesn't should
also be pretty straighforward.
--
Andrea Bolognani / Red Hat / Virtualization
___
libvirt-users mailing list
libvirt-users@redhat.com
https://www.redhat.co
irt) 1.3.1
As mentioned in my previous message, libvirt 1.3.1 is
about a year and a half old.
While you can install a newer libvirt version from source,
doing so is generally not recommended because your package
manager will not be aware of it and will prevent you from
installing packages that depend
d
a half ago), however the libvirt-guests script hasn't
changed very much in the meantime.
--
Andrea Bolognani / Red Hat / Virtualization
___
libvirt-users mailing list
libvirt-users@redhat.com
https://www.redhat.com/mailman/listinfo/libvirt-users
mctl disable libvirt-guests
to verify if the script is really what causes shutdown
to hang. It might very well be that it's merely the last
thing producing output before the actual issue occurs.
--
Andrea Bolognani / Red Hat / Virtualization
___
l
o for guests running on Hyper-V pretty
much what VirtIO drivers do for those running on QEMU/KVM.
--
Andrea Bolognani / Red Hat / Virtualization
___
libvirt-users mailing list
libvirt-users@redhat.com
https://www.redhat.com/mailman/listinfo/libvirt-users
too.
--
Andrea Bolognani / Red Hat / Virtualization
___
libvirt-users mailing list
libvirt-users@redhat.com
https://www.redhat.com/mailman/listinfo/libvirt-users
teps on my Fedora 24/x86_64 laptop and
I didn't run into any issues: if the experience is not quite
as seamless for you, I'd be interested in having the details.
--
Andrea Bolognani / Red Hat / Virtualization
___
libvirt-users mailing list
lib
was referring to).
By the way, edk2-ovmf is included in Fedora proper these
days, you don't need to use edk2.git-ovmf-x64 any longer ;)
--
Andrea Bolognani / Red Hat / Virtualization
___
libvirt-users mailing list
libvirt-users@redhat.com
https://www.redhat.com/mailman/listinfo/libvirt-users
On Tue, 2016-10-25 at 14:54 +0200, Michal Privoznik wrote:
> LD_PRELOAD="/usr/local/usr/lib64/" ./myApp
Surely you mean LD_LIBRARY_PATH?
--
Andrea Bolognani / Red Hat / Virtualization
___
libvirt-users mailing list
libvirt-users@red
going for 1), as that will
allow you to use all of libvirt's features down the line,
when it eventually turns out you need them ;)
--
Andrea Bolognani / Red Hat / Virtualization
___
libvirt-users mailing list
libvirt-users@redhat.com
https://www.redhat.com/mail
successfully on the Ubuntu
host and copying it over to the custom Linux host (guest
configuration + qcow2 disk image) to see whether it can
boot.
Failing that I guess upgrading QEMU is your best bet.
--
Andrea Bolognani / Red Hat / Virtualization
___
om
> built Linux I'd have to add the package manually and
> compile from source...which cakes a long time to do. So
> before attempting thatjust wonderingis there a
> better way? Anything I can try?
I think you're seriously overestimating the time it would
take to c
omething related on my issue
It looks like at least one of the guests is taking awfully
long to shut down. What if you bump up the timeout? Does it
manage to shut down before reaching it?
[1] Follow instructions at http://wiki.libvirt.org/page/DebugLogs
[2] When editing the file, add the new instruction *right
after* the first line. Of course you should make a backup
copy of the file before tweaking it
--
Andrea Bolognani / Red Hat / Virtualization
___
libvirt-users mailing list
libvirt-users@redhat.com
https://www.redhat.com/mailman/listinfo/libvirt-users
ontext
for the
/var/lib/libvirt/images
directory and files contained therein. It's likely that the
issue is caused by something messing with those information
behind libvirt's back, and not by a bug in libvirt itself
or virt-manager.
--
Andrea Bolognani / Red Hat / Virtualization
_
.service
to your libvirt-guests.service via 'systemctl edit' and
see if it helps? I don't think it should be needed for your
use case, but it's probably a good idea to have it there
anyways.
--
Andrea Bolognani / Red Hat / Virtualization
___
libvirt-users mailing list
libvirt-users@redhat.com
https://www.redhat.com/mailman/listinfo/libvirt-users
s? Does the libvirt-guests service actually
bring up the guests that were running before shutdown when
you start it a second time?
--
Andrea Bolognani / Red Hat / Virtualization
___
libvirt-users mailing list
libvirt-users@redhat.com
https://www.redhat.com/mailman/listinfo/libvirt-users
d as you'd like, but if you use QEMU you
can already achieve something similar via qemu-guest-agent.
https://www.redhat.com/archives/libvir-list/2016-August/msg00339.html
--
Andrea Bolognani / Red Hat / Virtualization
___
libvirt-users mailing list
li
lazy refcounts: true
The '--format' option is to specify the image format for the
input image. If you want the *output* image to be raw, you'll
have to use '--convert raw'.
-- Andrea Bolognani / Red Hat / Virtualization
___
libvirt-users mailing list
libvirt-users@redhat.com
https://www.redhat.com/mailman/listinfo/libvirt-users
S.fd in /var/lib/libvirt/qemu/nvram
and changing the 'template' attribute so that it points to the
*VARS.fd file you should have in your edk2 source tree, eg. the one
matching the OVMF.fd you're using to boot?
Not sure if that would help, but it's definitely worth a shot :)
Cheers.
--
Andrea Bol
created. (This assumes
> that your distro uses the same packaging setup as RHEL/Fedora/CentOS).
He's building libvirt from source though, see the first message :)
Cheers.
--
Andrea Bolognani
Software Engineer - Virtualization Team
___
libvirt-users m
fig-network: the
package contains /usr/share/libvirt/networks/default.xml
and its %post script copies it over to /etc to actually
enable the network.
Cheers.
--
Andrea Bolognani
Software Engineer - Virtualization Team
___
libvirt-users mailing li
On Wed, 2016-03-09 at 14:53 +, Andrei Perietanu wrote:
>
> On Wed, Mar 9, 2016 at 2:49 PM, Andrea Bolognani <abolo...@redhat.com> wrote:
> > On Wed, 2016-03-09 at 14:15 +, Andrei Perietanu wrote:
> > > I am building a custom Linux image which includes KVM a
nough to run
# virsh net-autostart --disable default
or delete
/etc/libvirt/qemu/networks/autostart/default.xml
after installation. You can also run
# virsh net-undefine default
or delete
/etc/libvirt/qemu/networks/default.xml
if you are sure you're never going to need the
default ne
s
it's owned by the deamon; always use 'virsh edit', 'virsh
dumpxml' etc. to inspect and modify it.
--
Andrea Bolognani
Software Engineer - Virtualization Team
___
libvirt-users mailing list
libvirt-users@redhat.com
https://www.redhat.com/mailman/listinfo/libvirt-users
in libnl3 rather than a problem in the way
libvirt is using said library. I suggest you file a bug against
libnl3 on the Debian Bug Tracking System.
Cheers.
--
Andrea Bolognani
Software Engineer - Virtualization Team
___
libvirt-users mailing list
libvirt
99 matches
Mail list logo
