[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, 1 month
error during host deploy
by Dana Elfassy
Hi,
While running a test case of adding hosts on ovirt system tests there was a
failure while the following command was executed:
vdsm-tool configure --force
On libvirtd log I found this error:
2021-12-17 00:11:41.753+0000: 28031: error : virNetTLSContextNew:732 :
Unable to generate diffie-hellman parameters: Error in public key
generation.
How would you suggest to debug this failure?
attaching libvirtd & journalctl logs
libvirt version: 7.10.0, package: 1.module_el8.6.0+1046+bd8eec5e
Thanks,
Dana
The error from host deploy log:
"2021-12-17 01":"11":"45 CET - fatal":[
ost-basic-suite-master-host-0
]:"FAILED! =>"{
"changed":true,
"cmd":[
"vdsm-tool",
"configure",
"--force"
],
"delta":"0:00:06.908971",
"end":"2021-12-17 01:11:42.815057",
"msg":"non-zero return code",
"rc":1,
"start":"2021-12-17 01:11:35.906086",
"stderr":"Error: ServiceOperationError: _systemctlStart
failed\nb'Job for libvirtd.service failed because a fatal signal was
delivered causing the control process to dump core.\\nSee \"systemctl
status libvirtd.service\" and \"journalctl -xe\" for details.\\n' ",
"stderr_lines":[
"Error: ServiceOperationError: _systemctlStart failed",
"b'Job for libvirtd.service failed because a fatal signal was
delivered causing the control process to dump core.\\nSee \"systemctl
status libvirtd.service\" and \"journalctl -xe\" for details.\\n' "
],
"stdout":"\nChecking configuration status...\n\nlvm is configured
for vdsm\nCurrent revision of multipath.conf detected,
preserving\nlibvirt is already configured for vdsm\nSUCCESS: ssl
configured to true. No conflicts\nsanlock is configured for
vdsm\nManaged volume database is already configured\n\nRunning
configure...\nReconfiguration of libvirt is done.\nReconfiguration of
passwd is done.",
"stdout_lines":[
"",
"Checking configuration status...",
"",
"lvm is configured for vdsm",
"Current revision of multipath.conf detected, preserving",
"libvirt is already configured for vdsm",
"SUCCESS: ssl configured to true. No conflicts",
"sanlock is configured for vdsm",
"Managed volume database is already configured",
"",
"Running configure...",
"Reconfiguration of libvirt is done.",
"Reconfiguration of passwd is done."
]
}
2 years, 9 months
Best way to install guest when it is not listed in output of osinfo-query os
by john doe
Hello all,
I would like to install Debian Bullseye using virt-install, as part of
the command I usually specify the OS used with the option '--os-variant'.
This works great untill Buster ('debian10'), but now the guest is
Bullseye ('debian11') and is not listed in the output of 'osinfo-query
os' (1).
If I don't use the '--os-variant' flag I get the following warning:
"WARNING No operating system detected, VM performance may suffer.
Specify an OS with --os-variant for optimal results."
Should I ignore the warning or what is the best way forward to install a
Debian Bullseye guest?
Both the host and the guest are Debian 11.
1) https://lists.debian.org/debian-user/2021/12/msg00742.html
--
John Doe
2 years, 10 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
2 years, 10 months
Libvirt on little.BIG ARM systems unable to start guest if no cpuset is provided
by Qu Wenruo
Hi,
Recently I got my libvirt setup on both RK3399 (RockPro64) and RPI CM4,
with upstream kernels.
For RPI CM4 its mostly smooth sail, but on RK3399 due to its little.BIG
setup (core 0-3 are 4x A55 cores, and core 4-5 are 2x A72 cores), it
brings quite some troubles for VMs.
In short, without proper cpuset to bind the VM to either all A72 cores
or all A55 cores, the VM will mostly fail to boot.
Currently the working xml is:
<vcpu placement='static' cpuset='4-5'>2</vcpu>
<cpu mode='host-passthrough' check='none'/>
But even with vcpupin, pinning each vcpu to each physical core, VM will
mostly fail to start up due to vcpu initialization failed with -EINVAL.
This brings a problem, in theory RK3399 SoC should out-perform BCM2711
in multi-core performance, but if a VM can only be bind to either A72 or
A55 cores, then the performance is no longer competitive against
BCM2711, wasting the PCIE 2.0 x4 capacity.
I guess with projects like Asahi Linux making progress, there will be
more and more such problems.
Any clue on how to properly pass all physical CPU cores to VM for
little.BIG setup?
Thanks,
Qu
2 years, 10 months
Guest vm doesn't recover after the nfs connection resume
by Liang Cong
Dear developers：
I found one issue during regular test and I could not confirm whether it is
a libvirt|qemu issue or it is a nfs client issue or it is not an issue, so
could you help to check it?
Below is the issue reproduce steps:
1.there is a nfs server with exports file like:
/nfs *(async,rw,no_root_squash)
2. host machine soft mount nfs:
mount nfs_server_ip:/nfs /var/lib/libvirt/images/nfs -o v4,soft
3. start a guest vm with disk tag xml like below:
<disk type='file' device='disk'>
<driver name='qemu' type='qcow2'/>
<source
file='/var/lib/libvirt/images/nfs/RHEL-8.6.0-20211102.1-x86_64.qcow2'
index='1'/>
<backingStore/>
<target dev='vda' bus='virtio'/>
<alias name='virtio-disk0'/>
</disk>
4.Start the vm and during the guest vm boot, apply the iptables rule to
drop the nfs connection to nfs server
iptables -A OUTPUT -d nfs_server_ip -p tcp --dport 2049 -j DROP
5. Wait until the error log appear in /var/log/message
kernel: nfs: server nfs_server_ip not responding, timed out
6. delete the iptables rule to retain the connection to nfs server
iptables -D OUTPUT -d nfs_server_ip -p tcp --dport 2049 -j DROP
7. check the guest vm, found the boot process with error and can not
recover.
rror: ../../grub-core/disk/i386/pc/biosdisk.c:546:failure reading sector
0x7ab8 from `hd0'.
error: ../../grub-core/disk/i386/pc/biosdisk.c:546:failure reading sector
0x9190 from `hd0'.
error: ../../grub-core/disk/i386/pc/biosdisk.c:546:failure reading sector
8. found there is error message in /var/log/message
kernel: NFS: __nfs4_reclaim_open_state: Lock reclaim failed!
Thanks
Liang Cong
2 years, 10 months
internal error - invalid characters
by lejeczek
Hi guys.
Have you seen something like this below?
...
internal error: The string resource has invalid characters
in its value
internal error: The provided value contains invalid
characters: Solarstorm SFN5162F SFP+ Server Adapter
this if from journal logs.
This hardware model of the NICs which comprise make up a
team/bridge which libvirt net use, but what would 'libvirtd'
bother with that?
many thanks, L.
2 years, 10 months
Libgfapi gone too?
by lejeczek
Hi guys.
Is glusterFS/libgfapi support removed (permanently) too? In
CentOS 9 Stream.
thanks, L.
2 years, 10 months
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.
2 years, 10 months
