[libvirt-users] [virtual interface] detach interface during boot succeed with no changes
by Yalan Zhang
Hi guys,
when I detach an interface from vm during boot (vm boot not finished), it
always fail. I'm not sure if there is an existing bug. I have
confirmed with someone that for disk, there is similar behavior, if
this is also acceptable?
# virsh destroy rhel7.2; virsh start rhel7.2 ;sleep 2; virsh
detach-interface rhel7.2 network 52:54:00:98:c4:a0; sleep 2; virsh
dumpxml rhel7.2 |grep /interface -B9
Domain rhel7.2 destroyed
Domain rhel7.2 started
Interface detached successfully
<address type='pci' domain='0x0000' bus='0x00' slot='0x06'
function='0x0'/>
</controller>
<interface type='network'>
<mac address='52:54:00:98:c4:a0'/>
<source network='default' bridge='virbr0'/>
<target dev='vnet0'/>
<model type='rtl8139'/>
<alias name='net0'/>
<address type='pci' domain='0x0000' bus='0x00' slot='0x03'
function='0x0'/>
</interface>
When I detach after the vm boot, expand the sleep time to 10, it will succeed.
# virsh destroy rhel7.2; virsh start rhel7.2 ;sleep 10; virsh
detach-interface rhel7.2 network 52:54:00:98:c4:a0; sleep 2; virsh
dumpxml rhel7.2 |grep /interface -B9
Domain rhel7.2 destroyed
Domain rhel7.2 started
Interface detached successfully
-------
Best Regards,
Yalan Zhang
IRC: yalzhang
Internal phone: 8389413
2 years, 4 months
[FOSDEM][CFP] Virtualization & IaaS Devroom
by Piotr Kliczewski
We are excited to announce that the call for proposals is now open for the
Virtualization & IaaS devroom at the upcoming FOSDEM 2022, to be hosted
virtually on February 5th 2022.
This year will mark FOSDEM’s 22nd anniversary as one of the longest-running
free and open source software developer events, attracting thousands of
developers and users from all over the world. Due to Covid-19, FOSDEM will
be held virtually this year on February 5th & 6th, 2022.
About the Devroom
The Virtualization & IaaS devroom will feature session topics such as open
source hypervisors and virtual machine managers such as Xen Project, KVM,
bhyve, and VirtualBox, and Infrastructure-as-a-Service projects such as
KubeVirt, Apache CloudStack, Foreman, OpenStack, oVirt, QEMU and OpenNebula.
This devroom will host presentations that focus on topics of shared
interest, such as KVM; libvirt; shared storage; virtualized networking;
cloud security; clustering and high availability; interfacing with multiple
hypervisors; hyperconverged deployments; and scaling across hundreds or
thousands of servers.
Presentations in this devroom will be aimed at users or developers working
on these platforms who are looking to collaborate and improve shared
infrastructure or solve common problems. We seek topics that encourage
dialog between projects and continued work post-FOSDEM.
Important Dates
Submission deadline: 20th of December
Acceptance notifications: 25th of December
Final schedule announcement: 31st of December
Recorded presentations upload deadline: 15th of January
Devroom: 6th February 2022
Submit Your Proposal
All submissions must be made via the Pentabarf event planning site[1]. If
you have not used Pentabarf before, you will need to create an account. If
you submitted proposals for FOSDEM in previous years, you can use your
existing account.
After creating the account, select Create Event to start the submission
process. Make sure to select Virtualization and IaaS devroom from the Track
list. Please fill out all the required fields, and provide a meaningful
abstract and description of your proposed session.
Submission Guidelines
We expect more proposals than we can possibly accept, so it is vitally
important that you submit your proposal on or before the deadline. Late
submissions are unlikely to be considered.
All presentation slots are 30 minutes, with 20 minutes planned for
presentations, and 10 minutes for Q&A.
All presentations will need to be pre-recorded and put into our system at
least a couple of weeks before the event.
The presentations should be uploaded by 15th of January and made available
under Creative
Commons licenses. In the Submission notes field, please indicate that you
agree that your presentation will be licensed under the CC-By-SA-4.0 or
CC-By-4.0 license and that you agree to have your presentation recorded.
For example:
"If my presentation is accepted for FOSDEM, I hereby agree to license all
recordings, slides, and other associated materials under the Creative
Commons Attribution Share-Alike 4.0 International License. Sincerely,
<NAME>."
In the Submission notes field, please also confirm that if your talk is
accepted, you will be able to attend the virtual FOSDEM event for the Q&A.
We will not consider proposals from prospective speakers who are unsure
whether they will be able to attend the FOSDEM virtual event.
If you are experiencing problems with Pentabarf, the proposal submission
interface, or have other questions, you can email our devroom mailing
list[2] and we will try to help you.
Code of Conduct
Following the release of the updated code of conduct for FOSDEM, we'd like
to remind all speakers and attendees that all of the presentations and
discussions in our devroom are held under the guidelines set in the CoC and
we expect attendees, speakers, and volunteers to follow the CoC at all
times.
If you submit a proposal and it is accepted, you will be required to
confirm that you accept the FOSDEM CoC. If you have any questions about the
CoC or wish to have one of the devroom organizers review your presentation
slides or any other content for CoC compliance, please email us and we will
do our best to assist you.
Call for Volunteers
We are also looking for volunteers to help run the devroom. We need
assistance with helping speakers to record the presentation as well as
helping with streaming and chat moderation for the devroom. Please contact
devroom mailing list [2] for more information.
Questions?
If you have any questions about this devroom, please send your questions to
our devroom mailing list. You can also subscribe to the list to receive
updates about important dates, session announcements, and to connect with
other attendees.
See you all at FOSDEM!
[1] https://penta.fosdem.org/submission/FOSDEM22
[2] iaas-virt-devroom at lists.fosdem.org
3 years, 1 month
a test email (& dmarc) @admins
by lejeczek
hi guys.
I sent email a while ago and I wonder, also having not
received a single reply, because I did not get that own
email - is there are problem I'm having here or DMARC(yahoo
& others?) are not fixed in by this mailing list - would an
admin(anybody) know?
many thanks, L.
3 years, 1 month
Libvirt Snapshot Question
by Elias Mobery
Hi everybody!
I'm using a snapshot purely for writes and was wondering if it's possible
to clear/empty the snapshot after it reaches a certain size?
Created with:
virsh snapshot-create-as --disk-only
I tried deleting and recreating it but get an error at deletion:
virsh snapshot-delete
Error: source for disk 'vda' is not a regular file
I also tried virsh snapshot-create-as --no-metadata --disk-only
But the same error as above pops up when trying to delete.
Any ideas?
3 years, 1 month
qemu-img create with preallocation=full and compression_type=zlib
by Richard Taubo
Hi!
When running this command on Fedora 35 I get:
[#] qemu-img create -o preallocation=full -f qcow2 /var/vm_mail/mytest.qcow2 10GB
=> Formatting '/var/vm_mail//mytest.qcow2', fmt=qcow2 . . . preallocation=full compression_type=zlib . . . ."
Question:
When using 'preallocation=full’ I was surprised that the resulting qcow2 image includes the 'compression_type=zlib’ part.
Why/when is this compression used when the qcow2 image is fully preallocated?
Thanks for input on this! :-)
Best regards
Richard Taubo
3 years, 1 month
virsh create fails with "Unable to find any firmware to satisfy 'efi'" for aarch64 guest on macOS
by Nathan Vander Wilt
I am having trouble when I `virsh create test.xml` with an aarch64
guest on a macOS (Apple Silicon) host. I've wrestled with a variety of
issues but the one I simply haven't been able to get past is this
regarding the UEFI firmware:
error: Failed to create domain from test.xml
error: operation failed: Unable to find any firmware to satisfy 'efi'
This is with `virsh --version` of 7.9.0 and `qemu-system-aarch64
--version` of 6.1.0, both installed via the common `brew` tool from
its main 'homebrew/core' tap. I have confirmed that the loader/nvram
files referenced do exist.
Running `qemu-system-aarch64 -L help` outputs two lines:
/opt/homebrew/Cellar/qemu/6.1.0_1/bin/../share/qemu-firmware
/opt/homebrew/Cellar/qemu/6.1.0_1/bin/../share/qemu
The …/share/qemu-firmware folder does NOT exist, but symlinking it to
a …/share/qemu/firmware folder which does exist does not improve the
situation.
I have also tried renaming the …/share/qemu/firmware folder (e.g. `mv
firmware zzz-firmware`) as some notes I found led me to believe that
libvirst might ignore my loader/nvram settings entirely if QEMU had
the "new" firmware JSON configuration stuff there? But again no
improvement….
How can I debug this further? What should I try next?
thanks,
-natevw
--- the test.xml domain configuration I am trying ---
<domain type="qemu" xmlns:qemu="http://libvirt.org/schemas/domain/qemu/1.0">
<name>test1</name>
<uuid>D45FCA3E-B873-4608-A0B8-3D8529E7CFB7</uuid>
<memory unit="MiB">2048</memory>
<cpu mode="host-model" check="partial" />
<vcpu>2</vcpu>
<clock offset="utc"/>
<qemu:commandline>
<qemu:arg value='-accel'/>
<qemu:arg value='hvf'/>
</qemu:commandline>
<os firmware="efi">
<type arch="aarch64" machine="virt">hvm</type>
<loader readonly="yes" secure="no"
type="pflash">/opt/homebrew/share/qemu/edk2-aarch64-code.fd</loader>
<nvram template="/opt/homebrew/share/qemu/edk2-arm-vars.fd">/Users/me/vm_testing/vm-test1.efi.fd</nvram>
<bootmenu enable="no"/>
<boot dev="hd"/>
</os>
<features>
<acpi/>
<gic version="3"/>
<pae/>
</features>
<devices>
<emulator>/opt/homebrew/bin/qemu-system-aarch64</emulator>
<disk type="file" device="disk">
<driver name="qemu" type="qcow2"/>
<source file="/Users/me/vm_testing/vm-test1.qcow2"/>
<target dev="vda" bus="virtio"/>
</disk>
<interface type="network">
<source network="default"/>
<model type="virtio"/>
</interface>
<console type="pty">
<target type="serial" port="0"/>
</console>
<rng model="virtio">
<backend model="random">/dev/urandom</backend>
</rng>
</devices>
</domain>
3 years, 1 month
Fwd: Installing virtiofs drivers on Windows 11....
by Mario Marietto
Hello to everyone.
I'm testing Windows 11 with bhyve and I've found an annoying problem that
prevents me from completing some tasks that I'm working on.
It seems that the virtio-9p driver does not work inside the Windows 11 os
emulated with bhyve and maybe also with qemu-kvm. When Windows 11 is
launched,I don't see the folder "mnt" mounted on the root folder of Windows
11. Below you can see which bhyve parameters I've used :
bhyve -S -c 4 -m 8G -w -H \
-s 0,hostbridge \
-s 1,ahci-cd,/home/marietto/Downloads/virtio/virtio-win-0.1.208.iso \
-s 2,ahci-hd,/mnt/da0p1/Backups/OS/bhyve/Windows/win11.img \
-s 3,fbuf,tcp=0.0.0.0:5900,w=1440,h=900,wait \
-s 8,virtio-net,tap0 \
----> -s 9,virtio-9p,sharename=/mnt \
-s 30,xhci,tablet \
-s 31,lpc \
-l bootrom,/usr/local/share/uefi-firmware/BHYVE_UEFI.fd \
vm0
Investigating a little bit more and reading from this tutorial :
https://virtio-fs.gitlab.io/howto-windows.html
I've realized that there should be some problem with the WinFsp
<http://www.secfs.net/winfsp> - Windows File System Proxy and or with the
virtiofs PCI device driver because I'm not able to enable the virtiofs
service with the command used on the tutorial :
C:\> sc start VirtioFsSvc
it gives the error : "the dependency service does not exist or it has
been marked for the elimination.
I've attached some screenshots to help you to understand what's happening.
Please help me,thanks.
Attached screenshots :
https://ibb.co/m5vm1hd
https://ibb.co/Qd6TS5d
https://ibb.co/3018SGd
--
Mario.
3 years, 1 month
virsh blockjob $domain --abort
by Jeff Brown
Please advise:
After a scheduled crontab snapshot backup of a VM it failed to do a
blockcommit, and is currently writing to both the snapshot and the
original QCOW2 images.
(I don't think it's a bug, and suspect that I caused it by running the
backup script manually while the snapshot was already running.)
$ virsh blockcommit VM sda --active --pivot --shallow --verbose
error: block copy still active: disk 'sda' already in active block job
$ virsh blockjob VM sda --info
Active Block Commit: [100 %]
$ virsh domblkerror VM
No errors found
Running on Debian 9 (Stretch).
$ virsh version
Compiled against library: libvirt 3.0.0
Using library: libvirt 3.0.0
Using API: QEMU 3.0.0
Running hypervisor: QEMU 2.8.1
Now, I've read up on the probable solution, somewhat, but running $
virsh blockjob $domain --abort on this production server scares me; and
I'm just asking whether it would be advisable to stop services and make
a full data backup prior to doing so? It would entail taking the
services offline for at least an hour. The snapshot is currently at
12GB, and according to blockjob --info the VM image is 100% in synch.
Will appreciate any advice. Thank you.
Best regards,
Jeff
3 years, 1 month
Libvirt + Debian Live = Heart Attack
by Elias Mobery
Hi everyone!
I've built a Debian Live ISO with packages qemu and libvirt to run a VM in
the live environment.
The guest images are placed in /var/lib/libvirt/images and 2GB each.
Everything works great, except for one issue.
When starting a VM, libvirt automatically issues a chown command to the
images, changing ownership.
This results in a copy of the images being created in
/run/live/overlay/rw/var/lib/libvirt/images
I don't want these copies to be made but can't stop it.
I've tried editing qemu.conf user/group, dynamic ownership etc. without any
luck.
Is there a way to STOP libvirt from changing the ownership of these images?
3 years, 1 month
