AppArmor issue when using gluster storage pool
by Max Schettler
Hi,
I'm trying to run a VM image that's stored on a gluster storage pool
which I added to libvirt (5.0.0) on a Debian 10 installation.
Whenever I try to boot a gluster-based VM, I get an error message about
a missing AppArmor profile. In fact, the corresponding files
(/etc/apparmor.d/libvirt/libvirt-{,.files}) are missing. After some
tinkering I noticed that the profile for the VM are in fact missing iff
there is a gluster-based disk attached to the VM in question. Whenever I
remove the disk, the profile files reappear, and when I add it again,
they are not present.
I am wondering what might cause this, and how I could fix, or work
around it, other than outright disabling AppArmor altogether.
Thanks and best regards, Max Schettler
--
Max Schettler, M.Sc.
TKN, TU Berlin, Germany
http://www.ccs-labs.org/team/schettler/
3 years, 7 months
SASL(-1): generic failure: All-whitespace username - from HA/pacemaker
by lejeczek
Hi guys,
I have a HA/pacemaker cluster with VirtualDomain and it all
seems to work fine, VMs start & stop, except for live migration.
So I thought I'd start here with errors I see, from 'pacemaker':
...
All-whitespace username.
notice: vpn1_migrate_to_0[977276] error output [ error:
authentication failed: Failed to start SASL negotiation: -1
(SASL(-1): generic failure: All-whitespace username.) ]
notice: vpn1_migrate_to_0[977276] error output [
ocf-exit-reason:vpn1: live migration to dzien failed: 1 ]
notice: Result of migrate_to operation for vpn1 on swir: error
notice: swir-vpn1_migrate_to_0:189 [ error: authentication
failed: Failed to start SASL negotiation: -1 (SASL(-1):
generic failure: All-whitespace
username.)\nocf-exit-reason:vpn1: live migration to dzien
failed: 1\n ]
notice: Result of stop operation for vpn1 on swir: ok
Can you shed more light on what virsh/libvirt says there?
many thanks, L.
3 years, 7 months
live migration with authentication - how?
by lejeczek
Hi guys.
I'm trying I assumed something very crude, logic suggested I
should try it first:
$ virsh migrate reactos
qemu+ssh://dzien/system?authfile=/etc/ovirt-hosted-engine/virsh_auth.conf
Please enter your authentication name: vdsm@ovirt
Please enter your password:
As you can see I still get asked for credentials.
Is it possible to live migrate that(or some) way, without
being asked for those?
many thanks,
L.
3 years, 7 months
Libvirt-lxc: iptables not working in containers
by John Hurnett
Hi,
I can't get iptables to work in libvirt-lxc containers. "iptables -L"
command shows empty chains. However I tested the same scenario with pure
lxc and iptables works as it should.
Has anyone experienced that? It seems like a bug, but maybe there is some
libvirt xml parameter I am missing?
BR
3 years, 7 months
Installing Kali Linux as Guest OS in KVM Hypervisor
by Kaushal Shriyan
Hi,
I have run the below command to install Kali Linux using
linux-2020.4-installer-amd64.iso from https://www.kali.org/downloads/
#virt-install --name kalilinux --memory 4096 --vcpus=2
--location=/linuxkvmaddgbdisk/kali-linux-2020.4-installer-amd64.iso,kernel=install.amd/gtk/vmlinuz,initrd=install.amd/gtk/initrd.gz
--network=bridge:br0 --os-type=linux --os-variant=debian9 --graphics=none
--extra-args "console=ttyS0" -v --disk
path=/linuxkvmaddgbdisk/kalilinux.img,size=50
I am not able to get the root login prompt when I run the below command to
set IP and hostname for the guest OS. Am I missing any parameters from the
above virt-install command to install Kali Linux as Guest OS in KVM
Hypervisor?
#virsh console kalilinux
Connected to domain kalilinux
Escape character is ^]
Any help will be highly appreciated. I look forward to hearing from you.
Thanks in Advance.
Best Regards,
Kaushal
3 years, 7 months
[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 2021, to be hosted
virtually on February 6th 2021.
This year will mark FOSDEM’s 21th 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 6th & 7th, 2021.
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 2021
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/FOSDEM17>https://penta.fosdem
.org/submission/FOSDEM21
[2] iaas-virt-devroom at lists.fosdem.org
3 years, 7 months
Cannot passthrough usb with bus number and device number
by YaoHua Wu
Sometimes, qemu cannot find correct usb device number
Reproduce steps:
1、lsusb
Bus 001 Device 011: ID 090c:1000
1、prepare usb device attach xml
<hostdev managed="yes" mode="subsystem" type="usb">
<source>
<vendor id="0x090c" />
<product id="0x1000" />
<address bus='001' device='011'/>
</source><address bus="1" port="1" type="usb" />
</hostdev>
2、virsh attach-device vm usb.xml
error: internal error: Did not find USB device 090c:1000 bus:1 device 9
Question:
why the device number returned in qemu's error report is not what I wrote in xml，
what I mean is that if my dev number is really wrong, the returned error should also be the number I wrote，
commonly when using dongle
Look forward to your reply
yaohua.wu
3 years, 7 months
