Thanks for coming back Vincent, I'll mark as invalid then.
** Changed in: qemu (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1883009
Title:
Thanks Vincent for following up and glad to hear the problem is gone.
I'm setting this report to Invalid then. Should you face new issues do
not hesitate to open a new one.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Hi Christian,
sorry for the delay, I had a HW issue before getting the new server up
with proxmox. Starting from a fresh setup, you are right, it works
without any issues.
So let's ignore this request, there is no need of any systemd
modification.
thanks again,
--
You received this bug
** Changed in: qemu (Ubuntu)
Status: Invalid => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1883009
Title:
qemu-guest-agent / systemctl enable failure
To manage notifications
right.
I'll download the "current" proxmox iso 6.2 and re-do a fresh
installation too... just in case. I did twice this installation ~1 month
a go.
I'll capture and put more inside for debugging. I'll keep you posted. I
hope I am not hunting a ghost...
--
You received this bug notification
I installed a proxmox 6.2 for testing purposes.
On that I installed a Ubuntu 20.04 Guest.
The setup has a checkbox for "qemu-agent" which I ticked.
(also worth as a test of the new installer in that env)
Installed qmeu-guest-agent in there and rebooted.
E voila - up and running.
It does not run
The setup is quite straightforward, but it requires a standalone server:
https://www.proxmox.com/en/downloads/item/proxmox-ve-6-2-iso-installer
If you can't find any environment for such setup, ping me thru a private
email (vjardin AT freeDOTfr), I'll look for a mean we could share.
Since udev
hmm thanks vincent, nothing that would obviously be too suspicious.
I wonder if I need to setup a proxmox VM somewhere ...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1883009
Title:
You welcome, here it is:
$ sudo lshw -C input
*-usb
description: Human interface device
product: QEMU USB Tablet
vendor: QEMU
physical id: 1
bus info: usb@1:1
version: 0.00
serial: 28754-:00:01.2-1
capabilities:
Hmm, not too many differences to mine:
-device virtio-serial-pci,id=virtio-serial0,bus=pci.3,addr=0x0 \
-device
virtserialport,bus=virtio-serial0.0,nr=1,chardev=charchannel0,id=channel0,name=org.qemu.guest_agent.0
\
The -pci being a difference is an alias to change per underlying
architecture
There is a single virtio port:
# ls -la /dev/virtio-ports/
lrwxrwxrwx 1 root root 11 May 25 19:07 org.qemu.guest_agent.0 -> ../vport2p1
# ls -la /dev/vport*
crw--- 1 root root 243, 1 May 25 19:07 /dev/vport2p1
As you can notice, there is 1 single deivce, but it starts from
vport2p1.
It
In your case it finds the device and tries to follow:
Following Set Member:
sys-devices-pci:00-:00:08.0-virtio2-virtio\x2dports-vport2p1.device
Following Set Member: dev-vport2p1.device
It knows it is udev related
Found: found-udev
But your path is different:
For reference, the same grep that you did:
ubuntu@focal:~$ sudo systemd-analyze dump | grep qemu
RequiredBy: qemu-guest-agent.service (destination-default)
Before: qemu-guest-agent.service (destination-default)
ReferencedBy: qemu-guest-agent.service (destination-default)
I installed twice a Ubuntu 20.04 / Server on two different proxmox
systems and for both I get this same issue. So, on my side, it seems to
happen for 100% of the cases.
Regarding:
# sudo systemd-analyze dump
I do not have any "Unit qemu-guest-agent.service":
# sudo systemd-analyze dump |
Odd, it worked on all systems I've seen so far - it is not generally
failing.
Can you check your `systemd-analyze dump` output if it contains
something like the following:
-> Unit qemu-guest-agent.service:
Description: QEMU Guest Agent
Instance: n/a
Unit Load State:
Hi Christian,
the guest is properly set:
# ls -la /dev/virtio-ports/org.qemu.guest_agent.0
lrwxrwxrwx 1 root root 11 May 25 19:07 /dev/virtio-ports/org.qemu.guest_agent.0
-> ../vport2p1
# lsof /dev/virtio-ports/org.qemu.guest_agent.0
In order to get the "qm agent 100 ping && echo ok" working,
The trigger it needs is the virtio port being set up.
Do you have:
/dev/virtio-ports/org.qemu.guest_agent.0
in your guest?
If not your guest definition will need it, for config examples see
https://wiki.qemu.org/Features/GuestAgent
https://wiki.libvirt.org/page/Qemu_guest_agent
If you have
Hi,
I set it to Invalid then. I didn't see Dan had already done so when I
replied to the bug and changed its status.
The problem you describe may depend on how the guest is started, as the
udev rule has a trigger on virtio-ports. If you believe this is a bug
and not a configuration problem
** Changed in: qemu (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1883009
Title:
qemu-guest-agent / systemctl enable failure
To manage notifications
Thanks Dan and Paride for your followup. I'd like this issue to be
invalid, but it seems qemu agent is not run by udev:
qm agent 100 ping && echo ok
QEMU guest agent is not running
vm$ sudo systemctl start qemu-guest-agent
qm agent 100 ping && echo ok
ok
it seems that:
===
cat
Hi Vincent,
I think the systemd service is working as intended. Other than the
output you pasted, running `systemctl enable qemu-guest-agent` prints
the following:
[...]
Possible reasons for having this kind of units are:
• A unit may be statically enabled by being symlinked from another unit's
> sudo systemctl enable qemu-guest-agent
that's not how you use it; it's a static service. You don't manually
enable/disable it, nor do you start/stop it.
the package provides a udev rule to setup SYSTEMD_WANTS for the agent
for any 'org.qemu.guest_agent.0' device, in /lib/udev/rules.d/60-qemu-
22 matches
Mail list logo
