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...@yahoo.com>
To: b...@campercaver.net, Bill Gee <b...@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<b...@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<b...@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<b...@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<b...@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<b...@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@centos.org
>
> >
>
> > > > https://lists.centos.org/mailman/listinfo/centos
>
> >
>
> > > >
>
> >
>
> > > >
>
> >
>
> > >
>
> >
>
> > > _______________________________________________
>
> >
>
> > > CentOS mailing list
>
> >
>
> > > CentOS@centos.org
>
> >
>
> > > https://lists.centos.org/mailman/listinfo/centos
>
> >
>
> > >
>
> >
>
> > >
>
> >
>
> >
>
> >
>
> >
>
>
>
>
-----------------------------------------
_______________________________________________
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos
