Re: interface qos conflicts with ovs
by Michal Prívozník
[please keep the list CC'ed]
On 6/11/21 4:42 PM, Jiatong Shen wrote:
> ah, OK. we are hitting this one when transfering to neutron ovs firewall
> and would like to fix
> it before moving to production.. does this bug still exist? If yes, can we
> take it and try
> submitting a fix? Thank you.
Sure you can! I'm happy to review patches.
Michal
4 years
lxcContainerMountFSBind - Failed to bind mount directory
by Priyanka Gupta
Hi Everyone,
I am looking to understand this piece of code and error.
2021-06-09 06:52:55.548+0000: 1: debug : lxcContainerMountAllFS:1612 :
Mounting all non-root filesystems
2021-06-09 06:52:55.548+0000: 1: debug : lxcContainerMountAllFS:1619 :
Mounting '/bootflash/SHARED-IOX' -> '/bootflash/SHARED-IOX'
2021-06-09 06:52:55.548+0000: 1: debug : lxcContainerResolveSymlinks:630 :
Resolving '/bootflash/SHARED-IOX'
2021-06-09 06:52:55.548+0000: 1: debug : lxcContainerResolveSymlinks:646 :
Resolved '/bootflash/SHARED-IOX' to /bootflash/SHARED-IOX
2021-06-09 06:52:55.548+0000: 1: debug : lxcContainerMountFSBind:1176 :
src=/bootflash/SHARED-IOX dst=/bootflash/SHARED-IOX
2021-06-09 06:52:55.548+0000: 1: error : lxcContainerMountFSBind:1223 :
Failed to bind mount directory /.oldroot/bootflash/SHARED-IOX to
/bootflash/SHARED-IOX: No such file or directory
I am on Libvirt 5.5.0
Any pointers?
Thanks
Priyanka
4 years
why cannot connect to libvirtd using virsh ???
by tommy
[root@test2 ~]# virsh -c quem+ssh://root@192.168.10.175/system
root(a)192.168.10.175's <mailto:root@192.168.10.175's> password:
error: failed to connect to the hypervisor
error: no connection driver available for quem:///system
But, on the same terminal using virt-manager to connect to 192.168.10.175 is
successful.
Why ?
4 years
virtiofs mounted filesystems & SELinux
by Link Dupont
I am mounting a filesystem into a domain using the virtiofs driver.
<filesystem accessmode="passthrough" type="mount">
<source dir="/home"/>
<target dir="/home"/>
<driver type="virtiofs"/>
</filesystem>
Both my host (Fedora 34) and guest (CentOS 8.4) are running with SELinux
enforcing. From my host, I can see that the SELinux context type is set to
user_home_dir_t.
$ ls -ldZ /home/link
drwxr-xr-x. 61 link link system_u:object_r:user_home_dir_t:s0 8192 May 21
12:41 /home/link
>From within the guest however, the volume is unlabeled_t
$ ls -lZd /home/link
drwxr-xr-x. 61 link link system_u:object_r:unlabeled_t:s0 8192 May 21 12:53 /
home/link
Is there a way to pass the SELinux context through to the guest? Or mount the
volume with the correct options to map SELinux contexts?
4 years
Re: How to hot plugin a new vhost-user-blk-pci device to running VM?
by 梁朝军
Thanks all of you for your help.
One more question regarding vhost-user-blk-pci type device, how to identify a vhost-blk disk in QEUM VM ? for example, disk name looks like vda,vdb,..., but that some application in VM want to detect that a certain entry is really the device it is waiting for. Specific for windows , they always show as disk 0, 1, 2….etc
Is there any way to identify those disk with each other in VM?
thanks
> 在 2021年5月17日，下午3:13，Michal Prívozník <mprivozn(a)redhat.com> 写道：
>
> On 5/17/21 7:08 AM, Liang Chaojun wrote:
>>
>> Thanks Michal and Peter for your response. I‘ m running it on qemu 5.1 build by myself. BTW, follow Peter’s suggestion, where I can get the latest rpms if I want to upgrade to Libvirt 7.1? As I know it seems need more than twenty related rpms not include dependency.
>
> Well, since you're building qemu yourself you could also build libvirt.
> Just be aware that the v7.3.0 release was the last one that supports
> RHEL-7. Newer releases might still work, but upstream does not aim to
> make everything work.
>
> https://libvirt.org/platforms.html
>
> Michal
>
4 years
Re: error when building from git checkout
by Andrea Bolognani
[re-adding libvirt-users]
On Fri, Jun 04, 2021 at 04:49:49PM +0800, Jiatong Shen wrote:
> Thank you very much for the reply. after applying this ps, the error is
> gone.
Glad to hear that! I've sent the patch to the mailing list now :)
> also curious to know if there is a way to skip building docs? thank you.
Passing -Ddocs=disabled to Meson should do the trick.
--
Andrea Bolognani / Red Hat / Virtualization
4 years
error when building from git checkout
by Jiatong Shen
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 virkeyname-osx.html with a meson_exe.py custom command
FAILED: docs/manpages/virkeyname-osx.html
/home/sjt/.local/bin/meson --internal exe --capture
docs/manpages/virkeyname-osx.html -- /usr/bin/xsltproc --stringparam
pagesrc docs/manpages/virkeyname-osx.rst --stringparam builddir
/home/sjt/src/c/libvirt/build --stringparam timestamp 'Thu Jun 3 23:11:25
2021 UTC' --nonet ../docs/subsite.xsl docs/manpages/virkeyname-osx.html.in
docs/manpages/virkeyname-osx.html.in:17: parser error : Double hyphen
within comment: <!-- This file is auto-generated from keymaps.csv
Data
keymap-gen --lang=rst --title=virkeyname-osx --subtitle=Key name values
for os
^
docs/manpages/virkeyname-osx.html.in:17: parser error : Double hyphen
within comment: <!-- This file is auto-generated from keymaps.csv
Data
keymap-gen --lang=rst --title=virkeyname-osx --subtitle=Key name values
for os
^
docs/manpages/virkeyname-osx.html.in:17: parser error : Double hyphen
within comment: <!-- This file is auto-generated from keymaps.csv
Data
keymap-gen --lang=rst --title=virkeyname-osx --subtitle=Key name values
for os
^
unable to parse docs/manpages/virkeyname-osx.html.in
[2/12] Generating virkeycode-usb.html with a meson_exe.py custom command
FAILED: docs/manpages/virkeycode-usb.html
/home/sjt/.local/bin/meson --internal exe --capture
docs/manpages/virkeycode-usb.html -- /usr/bin/xsltproc --stringparam
pagesrc docs/manpages/virkeycode-usb.rst --stringparam builddir
/home/sjt/src/c/libvirt/build --stringparam timestamp 'Thu Jun 3 23:11:25
2021 UTC' --nonet ../docs/subsite.xsl docs/manpages/virkeycode-usb.html.in
docs/manpages/virkeycode-usb.html.in:17: parser error : Double hyphen
within comment: <!-- This file is auto-generated from keymaps.csv
Data
keymap-gen --lang=rst --title=virkeycode-usb --subtitle=Key code values
for us
^
docs/manpages/virkeycode-usb.html.in:17: parser error : Double hyphen
within comment: <!-- This file is auto-generated from keymaps.csv
Data
keymap-gen --lang=rst --title=virkeycode-usb --subtitle=Key code values
for us
^
docs/manpages/virkeycode-usb.html.in:17: parser error : Double hyphen
within comment: <!-- This file is auto-generated from keymaps.csv
Data
keymap-gen --lang=rst --title=virkeycode-usb --subtitle=Key code values
for us
^
unable to parse docs/manpages/virkeycode-usb.html.in
[3/12] Generating virkeycode-atset1.html with a meson_exe.py custom command
FAILED: docs/manpages/virkeycode-atset1.html
/home/sjt/.local/bin/meson --internal exe --capture
docs/manpages/virkeycode-atset1.html -- /usr/bin/xsltproc --stringparam
pagesrc docs/manpages/virkeycode-atset1.rst --stringparam builddir
/home/sjt/src/c/libvirt/build --stringparam timestamp 'Thu Jun 3 23:11:25
2021 UTC' --nonet ../docs/subsite.xsl docs/manpages/
virkeycode-atset1.html.in
docs/manpages/virkeycode-atset1.html.in:17: parser error : Double hyphen
within comment: <!-- This file is auto-generated from keymaps.csv
Data
keymap-gen --lang=rst --title=virkeycode-atset1 --subtitle=Key code
values for
^
docs/manpages/virkeycode-atset1.html.in:17: parser error : Double hyphen
within comment: <!-- This file is auto-generated from keymaps.csv
Data
keymap-gen --lang=rst --title=virkeycode-atset1 --subtitle=Key code
values for
^
docs/manpages/virkeycode-atset1.html.in:17: parser error : Double hyphen
within comment: <!-- This file is auto-generated from keymaps.csv
Data
keymap-gen --lang=rst --title=virkeycode-atset1 --subtitle=Key code
values for
^
unable to parse docs/manpages/virkeycode-atset1.html.in
[4/12] Generating virkeycode-xtkbd.html with a meson_exe.py custom command
FAILED: docs/manpages/virkeycode-xtkbd.html
any advice on how to fix it? thank you very much
--
Best Regards,
Jiatong Shen
4 years
Error: --boot uefi=RPI_EFI.fd : Did not find any UEFI binary path for arch 'aarch64' emulating raspi3 on jetson nano with virt-install
by Mario Marietto
Hello.
it's more of a challenge,to be able to emulate the raspberry pi 3 on my
Jetson nano (aarch64) using virt-install. I'm learning how to do that by
reading heavily here :
https://github.com/dhruvvyas90/qemu-rpi-kernel
I tried to do something like this :
virt-install \
--name pi \
--machine raspi3 \
--cpu arm1176 \
--memory 1024 \
--import \ --disk
/root/Desktop/zi/Work/Android/Raspy/Debian/2019-09-26-raspbian-buster-lite.img,format=raw,bus=virtio
\
--network user,model=virtio \
--video vga \
--graphics spice \
--rng device=/dev/urandom,model=virtio \
--boot 'uefi=RPI_EFI.fd,dtb=bcm2710-rpi-3-b-plus.dtb,kernel=kernel8.img,kernel_args=root=/dev/vda2
rootwait panic=1 dwc_otg.fiq_fsm_enable=0' \
--events on_reboot=destroy
But I get this error :
ERROR Error: --boot uefi=RPI_EFI.fd,dtb=bcm2710-rpi-3-b-plus.dtb,kernel=
kernel8.img,kernel_args=root=/dev/vda2 rootwait panic=1
dwc_otg.fiq_fsm_enable=0: Did not find any UEFI binary path for arch
'aarch64'
I've got the UEFI BIOS file from here :
https://github.com/andreiw/RaspberryPiPkg/blob/master/Binary/prebuilt/201...
I'm not sure if it isn't the right efi file to use in this specific
configuration or if it is,but I'm passing the parameter badly. What do you
suggest me to do ?
--
Mario.
4 years
virt viewer for Mac
by Francesc Guasch
Hi. Please excuse me if this is not the right place to ask.
We are using virt viewer happily from Linux, and though the
Windows release sometimes has issues it seems it is maintained.
There is this Mac client here:
https://people.freedesktop.org/~teuf/spice-gtk-osx/
We have been reported it is outdated and somehow buggy.
Is there another alternative ? Are there plans to port
virt-viewer for Macs ?
Thank you.
4 years
