Discuss

discuss@lists.centos.org

8 participants
34745 discussions

Update - Resizing a QEMU guest display
by Bill Gee 11 Feb '21

11 Feb '21

Strahil Nikolov and I took this conversation off-line for a few days. The thread of our discussion is below. Net result: No solution is yet found. Strahil had some very good ideas, but they did not pan out in this case. For archiving - and in hope that someone may have some other ideas! - I post this back to the list. -- Bill Gee ---------- Forwarded Message ---------- Subject: Re: [CentOS] Resizing a QEMU guest display Date: Tuesday, February 9, 2021, 10:38:08 PM CST From: Strahil Nikolov <hunter86_bg(a)yahoo.com> To: bgee(a)campercaver.net, Bill Gee <bgee(a)campercaver.net> Erm... mine was spice-vdagent.service , and not '.socket'.Never mind, it could be something else. Best Regards,Strahil Nikolov On Tue, Feb 9, 2021 at 21:52, Bill Gee<bgee(a)campercaver.net> wrote: I restarted spice-vdagentd.socket on the guest that will not resize. It still will not resize. [root@practice21a ~]# systemctl restart spice-vdagentd.socket [root@practice21a ~]# systemctl status spice-vdagentd.socket ● spice-vdagentd.socket - Activation socket for spice guest agent daemon Loaded: loaded (/usr/lib/systemd/system/spice-vdagentd.socket; static) Active: active (listening) since Tue 2021-02-09 13:43:10 CST; 8s ago Triggers: ● spice-vdagentd.service Listen: /run/spice-vdagentd/spice-vdagent-sock (Stream) CGroup: /system.slice/spice-vdagentd.socket Feb 09 13:43:10 practice21a.billgee.local systemd[1]: Listening on Activation socket for spice guest a> [root@practice21a ~]# ps ax | grep spice 3018 ? Ssl 0:00 /usr/bin/spice-vdagent 3032 ? Ssl 0:00 /usr/sbin/spice-vdagentd 3554 pts/0 S+ 0:00 grep --color=auto spice [root@practice21a ~]# But! Just to be sure, I checked the guest that WILL resize. There is no service on it called spice-vdagentd.socket! There is also no process with spice in the name. The guest that should work does not, and the guest that should not work does! -- Bill Gee On Tuesday, February 9, 2021 12:56:38 PM CST you wrote: > The serviceis indirect, which means that another unit has to 'call' it. Try restarting the service in the VM. > # systemctl status spice-vdagentd.service ● spice-vdagentd.service - Agent daemon for Spice guests Loaded: loaded (/usr/lib/systemd/system/spice-vdagentd.service; indirect; vendor preset: enabled) Active: active (running) since Mon 2021-02-08 22:31:06 EET; 22h ago Main PID: 27963 (spice-vdagentd) Tasks: 1 CGroup: /system.slice/spice-vdagentd.service └─27963 /usr/sbin/spice-vdagentd Feb 08 22:31:06 openshift1 systemd[1]: Starting Agent dae...Feb 08 22:31:06 openshift1 systemd[1]: Started Agent daem...Feb 08 22:31:07 openshift1 spice-vdagentd[27963]: opening...Hint: Some lines were ellipsized, use -l to show in full. > Best Regards,Strahil Nikolov > > On Tue, Feb 9, 2021 at 20:50, Bill Gee<bgee(a)campercaver.net> wrote: > Hmmmm.... I am missing something. Why would rebooting the entire computer NOT restart the service? > > > And for that matter - Exactly what service are you talking about? Can you be more specific? > > > > The service is of type indirect. Try to restart only the service (not the guest). > > > Best Regards,Strahil Nikolov > > > > > > > > > On Tue, Feb 9, 2021 at 20:31, Bill Gee<bgee(a)campercaver.net> wrote: > > > The host and all of its guests have been rebooted multiple times in the last two days. > > > > > > > > > > > > > Have you restarted the service ?Yesterday I built a CentOS 7 system and spice didn't resize untill I restarted the service. > > > > > > > Best Regards,Strahil Nikolov > > > > > > > > > > > > > > > > > > > > > On Mon, Feb 8, 2021 at 14:40, Bill Gee<bgee(a)campercaver.net> wrote: Hi Strahil - > > > > > > > > > > > > > > Thanks for the link. Unfortunately it is not helpful. The spice agent is already installed on the guest, and the spice channel is already configured. > > > > > > > > > > > > > > [bgee@practice21a ~]$ rpm -qa | grep spice > > > > > > > spice-vdagent-0.20.0-3.fc33.x86_64 > > > > > > > > > > > > > > A question occurs to me ... The working guest also has both the spice-vdagent package and the spice channel. Why does it work and the other guest does not? > > > > > > > > > > > > > > > I think the following is a good start: > > > > > > > > 11.3. SPICE Agent Red Hat Enterprise Linux 7 | Red Hat Customer Portal > > > > > > > > | > > > > > > > > | > > > > > > > > | > > > > > > > > | | | > > > > > > > > > > > > > > > > | > > > > > > > > > > > > > > > > | > > > > > > > > | > > > > > > > > | | > > > > > > > > 11.3. SPICE Agent Red Hat Enterprise Linux 7 | Red Hat Customer Portal > > > > > > > > > > > > > > > > The Red Hat Customer Portal delivers the knowledge, expertise, and guidance available through your Red Hat subscription. > > > > > > > > | | > > > > > > > > > > > > > > > > | > > > > > > > > > > > > > > > > | > > > > > > > > > > > > > > > > > > > > > > > > Best Regards,Strahil Nikolov > > > > > > > > > > > > > > > > > > > > > > > > On Sun, Feb 7, 2021 at 20:29, Bill Gee<bgee(a)campercaver.net> wrote: Hi Strahil - > > > > > > > > > > > > > > > > How does one reach a guest via spice? I am not familiar with any remote access application called "spice". I have tried two methods of accessing the host. First is to open it from the Virtual Machine Manager on the host. Second is to use TigerVNC to access it across the local network. > > > > > > > > > > > > > > > > I see a package installed on the guest which looks like the guest agent. Is there more that needs to be added? This is the only qemu package installed on both the Fedora machine that does not resize and the CentOS7 machine that will resize. The versions are way different between the two guests. > > > > > > > > > > > > > > > > [root@practice21a ~]# rpm -qa | grep qemu > > > > > > > > qemu-guest-agent-5.1.0-9.fc33.x86_64 > > > > > > > > > > > > > > > > The Fedora guest has, as you see, version 5.1.0-9. The CentOS7 guest has version 2.12.0-3. Perhaps the Fedora guest version is too new to run on a CentOS7 host?? > > > > > > > > > > > > > > > > I see other QEMU packages available. One of them is called "qemu-device-display-qxl" which is very suggestive. However, that package is NOT installed on the CentOS7 guest and yet that guest works. > > > > > > > > > > > > > > > > Another package I see is "libvirt-daemon-driver-qemu". This package is installed on the host but is not present on either guest. Is it needed on guests? > > > > > > > > > > > > > > > > > Have you tried to reach the VM via spice ?Also check if qemu's guest agent is runningin the VM. > > > > > > > > > > > > > > > > > > Best Regards,Strahil Nikolov > > > > > > > > > > > > > > > > _______________________________________________ > > > > > > > > CentOS mailing list > > > > > > > > CentOS(a)centos.org > > > > > > > > https://lists.centos.org/mailman/listinfo/centos > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > _______________________________________________ > > > > > > > CentOS mailing list > > > > > > > CentOS(a)centos.org > > > > > > > https://lists.centos.org/mailman/listinfo/centos > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > -----------------------------------------

1 0

Re: [CentOS] udev rules & USB devices - ignored at boot
by lejeczek 11 Feb '21

11 Feb '21

On 09/02/2021 18:25, Strahil Nikolov wrote: > CentOS 7 doesn't use the old naming convention but ,if you > set a device name and mac address for your connection, the > network stack will rename the device during activation. > > Try with: > > SUBSYSTEM=="net", ACTION=="add|change", DRIVERS=="?*", > ATTR{address}=="00:1e:10:1f:00:00", ATTR{type}=="1", > pop NAME="lteusb" dnf pulled in quite a few updates in the meanwhile but most likely "change" does the trick. I thought it had something to do with USB/kernel/subsystems parts as the very same rules worked for PCIe devices, those worked at re/boot. many! thanks Strahil. > > Best Regards, > Strahil Nikolov > > On Mon, Feb 8, 2021 at 17:04, lejeczek via CentOS > <centos(a)centos.org> wrote: > > > On 08/02/2021 08:10, Strahil Nikolov wrote: > > Can you share your udev rules ? > > > > Best Regards, > > Strahil Nikolov > > > > On Sun, Feb 7, 2021 at 15:33, lejeczek via CentOS > > <centos(a)centos.org <mailto:centos@centos.org>> wrote: > > Hi guys, > > > > I have an Ethernet USB adapter for which udev > executes my > > custom rules but!... udev does it only at plug-in > > event and > > not! when the USB stays plugged in during a > reboot, then > > same rules are ignored (or some other problem > results in > > udev failure to do the same when device is > plugged to a > > running system). > > My system is just an average box with a Ryzen on > a B550 > > platform. > > Anybody sees this reproduce? > > many thanks, L. > > _______________________________________________ > > CentOS mailing list > > CentOS(a)centos.org <mailto:CentOS@centos.org> > <mailto:CentOS@centos.org <mailto:CentOS@centos.org>> > > https://lists.centos.org/mailman/listinfo/centos > <https://lists.centos.org/mailman/listinfo/centos> > > <https://lists.centos.org/mailman/listinfo/centos > <https://lists.centos.org/mailman/listinfo/centos>> > > > simple rules: > > SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", > ATTR{address}=="00:1e:10:1f:00:00", ATTR{type}=="1", > KERNEL=="eth*", NAME="lteusb" > > like I said - I get iface "lteusb" when I plug the USB > so it > works. If I leave that USB plugged in and reboot then no > "lteusb". > > regards, L. > > _______________________________________________ > CentOS mailing list > CentOS(a)centos.org <mailto:CentOS@centos.org> > https://lists.centos.org/mailman/listinfo/centos > <https://lists.centos.org/mailman/listinfo/centos> >

1 0

smba shares are unreachable once or twice per month
by Prengel, Ralf 10 Feb '21

10 Feb '21

Hallo, I ve a problem with my samba-server. We are using a centos 7.7 with an samba exporting samba-shares. Logins are managed by our Windows-AD. The samba server has only the function to exports hares. Windows clients are Win10 patched every month. Our problem: Once or twice a month shares aren't akctive any longer and reachable for the Window-Clients. Network can nor be a reason because the same directory exported via NFS is reachable for all Linux-NFS-Client. Normally we disconect and connect the Samba server in the AD and after a reboot the shares are working again but that cant be the solution ;-) Can anyone give me hints hwo to anaylse and solving the problem. Thanks Ralf

3 2

CentOS-announce Digest, Vol 191, Issue 3
by centos-announce-request＠centos.org 10 Feb '21

10 Feb '21

Send CentOS-announce mailing list submissions to centos-announce(a)centos.org To subscribe or unsubscribe via the World Wide Web, visit https://lists.centos.org/mailman/listinfo/centos-announce or, via email, send a message with subject or body 'help' to centos-announce-request(a)centos.org You can reach the person managing the list at centos-announce-owner(a)centos.org When replying, please edit your Subject line so it is more specific than "Re: Contents of CentOS-announce digest..." Today's Topics: 1. CESA-2021:0411 Important CentOS 7 flatpak Security Update (Johnny Hughes) 2. CEBA-2021:0439 CentOS 7 glibc BugFix Update (Johnny Hughes) ---------------------------------------------------------------------- Message: 1 Date: Tue, 9 Feb 2021 14:32:53 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CESA-2021:0411 Important CentOS 7 flatpak Security Update Message-ID: <20210209143253.GA26338(a)bstore1.rdu2.centos.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Security Advisory 2021:0411 Important Upstream details at : https://access.redhat.com/errata/RHSA-2021:0411 The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) x86_64: 0e230546571aa26c06f1097967584ab4b9e777e7ca6c94d45f8706a36bdccc22 flatpak-1.0.9-10.el7_9.x86_64.rpm 724795eec6065da1df593d22a6a359fc5b241aec5a3916cbec646ff78f2196ba flatpak-builder-1.0.0-10.el7_9.x86_64.rpm 85ac0468355fd6847c79849e947fd3b5d88f606ad3aa6fd06cb4aca3fe3c9fc8 flatpak-devel-1.0.9-10.el7_9.x86_64.rpm 6a5560cf575ee9bfa9cac85044e94e3bce3ea85e26431c99e41877289cf82b64 flatpak-libs-1.0.9-10.el7_9.x86_64.rpm Source: 170d39f61f08b19f0c202440b9ac801e8d5e80ec0240b8cd0f3a9d85a3c109d4 flatpak-1.0.9-10.el7_9.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net Twitter: @JohnnyCentOS ------------------------------ Message: 2 Date: Tue, 9 Feb 2021 14:33:56 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CEBA-2021:0439 CentOS 7 glibc BugFix Update Message-ID: <20210209143356.GA26542(a)bstore1.rdu2.centos.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Bugfix Advisory 2021:0439 Upstream details at : https://access.redhat.com/errata/RHBA-2021:0439 The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) x86_64: ee561a3f0dd8945edec3478e8426cc324bdf6fc5fe6a31d762cfae60d3e14830 glibc-2.17-323.el7_9.i686.rpm b2b420ac2c03b3a2e4cadd073857498446180ec51a863fe30335c9da3a963fde glibc-2.17-323.el7_9.x86_64.rpm f48d75115ac638576d608849a173ace6a70c2430a2e0226487652befdf004b27 glibc-common-2.17-323.el7_9.x86_64.rpm acbb0c34227bd9c7bba35cfa08b4942dd141ee4ccadd128d8acedaef5e31522c glibc-devel-2.17-323.el7_9.i686.rpm aab72ef4b89bc4481b87f7aaf225cbdefb62073dddddc7fc7c2b94ab11a0a936 glibc-devel-2.17-323.el7_9.x86_64.rpm 9ba71fe357dd09d1913b30b0bd83507588d8cb06eda6f2c15326f3f1384c6180 glibc-headers-2.17-323.el7_9.x86_64.rpm eae7a2d2bc9f6058c113c27e6bdea6677a865df0f7924ed51165a2653c2d2175 glibc-static-2.17-323.el7_9.i686.rpm 49e01e923bc5d1026751341c9a01ab8ef4d50d8b17e94f179de33afcbfb0b234 glibc-static-2.17-323.el7_9.x86_64.rpm cafdbebcda7664e47d81f647d715249983cbe0bb4b063c1d56ab327a8766e2d0 glibc-utils-2.17-323.el7_9.x86_64.rpm 27d1ba676d3d4007102e714f71f0f4e97d46890c6eed54e5f10720ff65e7cea8 nscd-2.17-323.el7_9.x86_64.rpm Source: cb68b648ffec5a38b0cef7e6a88fb2dfb6357c8f0a17cf0331376a3cdfd41d97 glibc-2.17-323.el7_9.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net Twitter: @JohnnyCentOS ------------------------------ Subject: Digest Footer _______________________________________________ CentOS-announce mailing list CentOS-announce(a)centos.org https://lists.centos.org/mailman/listinfo/centos-announce ------------------------------ End of CentOS-announce Digest, Vol 191, Issue 3 ***********************************************

1 0

SCLO php70 imap missing
by H 10 Feb '21

10 Feb '21

I am installing php70 on a machine running CentOS 7 for a particular reason and needed sclo-php70-php-imap which I believe is the imap module for php70 from SCL. It, however, does not seem to be available even though https://cbs.centos.org/koji/buildinfo?buildID=24734 suggests it should be. Am I missing something?

1 0

Resizing a QEMU guest display
by Bill Gee 09 Feb '21

09 Feb '21

Hello everyone - I think I know the answer, but just in case ... I want to run it by the experts. I have a machines running CentOS 7. "uname -a" returns this: Linux practice7.billgee.local 3.10.0-1160.15.2.el7.x86_64 #1 SMP Wed Feb 3 15:06:38 UTC 2021 x86_64 x86 _64 x86_64 GNU/Linux This machine has an nVidia GS8400 and uses the nouveau driver. Its main job is to be a host for QEMU/KVM virtual machines. The QEMU packages on the host are: [bgee@practice7 ~]$ rpm -qa | grep qemu qemu-kvm-1.5.3-175.el7_9.3.x86_64 qemu-guest-agent-2.12.0-3.el7.x86_64 qemu-kvm-common-1.5.3-175.el7_9.3.x86_64 qemu-img-1.5.3-175.el7_9.3.x86_64 libvirt-daemon-driver-qemu-4.5.0-36.el7_9.3.x86_64 ipxe-roms-qemu-20180825-3.git133f4c.el7.noarch One of the guest VMs is Fedora 33. The guest comes up with a display resolution of 1024x768. I have not found a way to change it to something higher. If I go to the Settings - Display item in Fedora, there is a long list of resolutions. No matter what I choose, the system will switch to that resolution for about 1/2 second and then go back to 1024x768. This happens when using VNC to connect remotely and also when running on the host computer. Resizing the guest display window does nothing except make big black borders around the guest display. The guest video configuration in the virtual machine manager is set for "QXL". In my searching I found several suggestions to use "virtio" instead. When I make that change and start the guest, it immediately throws an error: "This QEMU does not support 'virtio' video device" I also tried "vmvga" and "cirrus". The cirrus setting does not resize and also loses coordination of the mouse pointer. The vmvga setting gives the same message about not being supported in this QEMU. I verified that the spice-vdagent package is installed on the guest VM. The virtual machine manager has "Resize guest with window" set to ON. Just to make life really interesting... Another guest VM on the same host is running CentOS7. That machine happily resizes! It is set for QXL in the virtual machine manager. I think I am just out of luck. I found some references which say that CentOS 7 does not have support for virtio displays. Is that right? Is there some way to resize the Fedora guest? I don't care about dynamic sizing by dragging a window border. If I can choose something and have it stick, I would be happy. Thanks! -- Bill Gee

2 5

Recommendation for 10 gigabit NICs on CentOS8
by Strahil Nikolov 09 Feb '21

09 Feb '21

Hi All, can you share what kind of old NICs do you use on CentOS 8 (Stream or not , it doesn't matter) without any issues? I was looking at ebay and I found some pretty old Mellanox "ConnectX" or "ConnectX-2" but I seriously doubt they will work on CentOS 8. Any proposals are also welcome. I don't care of the brand as long as it is PCIe and is supported by the vanilla kernel. Best Regards, Strahil Nikolov

4 3

firewalld - same source in different zones
by Łukasz Posadowski 08 Feb '21

08 Feb '21

Hi. I have a little trouble with firewalld. I'm trying to open some ports for monitoring server, but it's in the same network as "home" zone: Monitored host (192.168.111.60): lukasz @ strategie 17:52:19 ~ $ -> sudo firewall-cmd --get-active home sources: 192.168.111.0/24 (open ports 22, 80, 443) monitoring sources: 192.168.111.19 (open ports: 5666) public interfaces: ens18 (no open ports) --------------------------------------------------- Monitoring host (192.168.111.19): lukasz @ potemkin 17:57:25 ~ $ -> telnet strategie.ping.local 5666 Trying 192.168.111.60... telnet: connect to address 192.168.111.60: No route to host lukasz @ potemkin 17:57:26 ~ $ -> telnet strategie.ping.local 80 Trying 192.168.111.60... Connected to strategie.ping.local. Escape character is '^]'. ^] telnet> Connection closed. --------------------------------------------------- I think there are conflicting rules on a monitored host, that: - prevent access to 5666 from 192.168.111.0/24, - give access to 5666 from 192.168.111.19 and packets from potemkin are routed trough a home zone. I really would like to have dedicated "monitor" zone. Is there a way to give "monitor" zone more priority, than "home"? I may end with OpenVPN on potemkin and use 172.30.25.0/24 for monitoring, but, apart from encryption aspect, it seems a little excessive. Thank You. -- Łukasz Posadowski

2 2

Re: [CentOS] udev rules & USB devices - ignored at boot
by lejeczek 08 Feb '21

08 Feb '21

On 08/02/2021 08:10, Strahil Nikolov wrote: > Can you share your udev rules ? > > Best Regards, > Strahil Nikolov > > On Sun, Feb 7, 2021 at 15:33, lejeczek via CentOS > <centos(a)centos.org> wrote: > Hi guys, > > I have an Ethernet USB adapter for which udev executes my > custom rules but!... udev does it only at plug-in > event and > not! when the USB stays plugged in during a reboot, then > same rules are ignored (or some other problem results in > udev failure to do the same when device is plugged to a > running system). > My system is just an average box with a Ryzen on a B550 > platform. > Anybody sees this reproduce? > many thanks, L. > _______________________________________________ > CentOS mailing list > CentOS(a)centos.org <mailto:CentOS@centos.org> > https://lists.centos.org/mailman/listinfo/centos > <https://lists.centos.org/mailman/listinfo/centos> > simple rules: SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:1e:10:1f:00:00", ATTR{type}=="1", KERNEL=="eth*", NAME="lteusb" like I said - I get iface "lteusb" when I plug the USB so it works. If I leave that USB plugged in and reboot then no "lteusb". regards, L.

2 1

Challenging times in trying to access oracle Linux documentation
by Shamim Shahriar 07 Feb '21

07 Feb '21

Good afternoon everyone, hope you all are well. Apologies if this is considered unwelcome -- asking oracle question in centos group -- but a lot of centos Vs oracle is going on here so hoping this will not be shot down. I am unable to access any of the oracle documentation I need, as it keeps on asking for support identifier number, which, as far as I can tell, is only available if I purchase an expensive support subscription. Even obtaining a free oracle cloud account does not give you any access. I was trying to access oracle FreeIPA setup how to documentation, and even after many emails work oracle support over several weeks -- no resolution! They are not even clear as to what I need to do to obtain access -- all they are saying is I need a SI number!!! Has anyone experienced that or is it me having the issue? If I have to pay subscription, why not continue with RHEL subscription anyway? Would appreciate if someone could please confirm. Best regards Shamim

9 15

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Discuss