> I guess my next question is, how do I find out the correct TTY (or
> whatever) to use to talk to the host, since /dev/tty00 doesn't work
> for me. I'm using virtual hosting at a provider, so I don't know the
> configuration from the outside.
I'm at the same point:
# sh /etc/rc.d/qemu-guest-agent start
Starting qemu_guest_agent.
1756483306.437000: critical: error opening channel '/dev/tty00': Device not
configured
1756483306.437075: critical: failed to create guest agent channel
1756483306.437102: critical: failed to initialize guest agent channel
1756483306.437118: critical: error initializing guest agent
#
and I don't have /dev/tty00:
# ls -l /dev/tty00
crw------- 1 uucp wheel 8, 0 May 25 2021 /dev/tty00
# echo a > /dev/tty00
sh: cannot create /dev/tty00: no such device or address
#
> I'll attach the dmesg in case it gives some clues.
Could it be this one?
virtio1 at pci0 dev 28 function 0
virtio1: console device (id 3, rev. 0x00)
virtio1: autoconfiguration error: no matching child driver; not configured
I.e. you don't appear to have a suitable matching device driver
at the moment. Looks like you could get this via the "viocon"
driver, and then get e.g. /dev/ttyVI00, ref. viocon(4), but
evidently it's not in GENERIC:
$ cd /usr/src/sys/arch/amd64/conf
$ grep viocon GENERIC
$ uname -r
10.99.12
$
$ grep __NetBSD_Version__ /usr/src/sys/sys/param.h
* #define __NetBSD_Version__ MMmmrrpp00
#define __NetBSD_Version__ 1099001200 /* NetBSD 10.99.12 */
(m) * 1000000) + (p) * 100) <= __NetBSD_Version__)
* New code must use __NetBSD_Version__ instead, and should not even
$
You'd also need to run MAKEDEV for it, as per normal conventions:
$ grep ttyVI /dev/MAKEDEV
makedev ttyVI
ttyVI[0-9][0-9])
port=${i#ttyVI?}
unit=${devunit#ttyVI}
mkdev ttyVI$unit$port c 364 $((16*$unit + $port))
ttyVI)
makedev ttyVI00 ttyVI10 ttyVI20 ttyVI30
$
The virtual devices I see are (from dmesg):
[ 1.013261] virtio0 at pci0 dev 3 function 0
[ 1.013261] virtio0: Virtio Memory Balloon Device (rev. 0x00)
[ 1.013261] viomb0 at virtio0virtio0: allocated 8192 byte for virtqueue 0
for inflate, size 128
[ 1.013261] virtio0: allocated 8192 byte for virtqueue 1 for deflate, size
128
[ 1.013261] : Features: 0x10000000<INDIRECT_DESC>
[ 1.013261] virtio0: interrupting at ioapic0 pin 11
[ 1.013261] virtio1 at pci0 dev 5 function 0
[ 1.013261] virtio1: Virtio SCSI Device (rev. 0x00)
[ 1.013261] vioscsi0 at virtio1: Features: 0x10000000<INDIRECT_DESC>
[ 1.013261] virtio1: allocated 86016 byte for virtqueue 0 for control, size
256
[ 1.013261] virtio1: using 73728 byte (4608 entries) indirect descriptors
[ 1.013261] virtio1: allocated 86016 byte for virtqueue 1 for event, size
256
[ 1.013261] virtio1: using 73728 byte (4608 entries) indirect descriptors
[ 1.013261] virtio1: allocated 86016 byte for virtqueue 2 for request, size
256
[ 1.013261] virtio1: using 73728 byte (4608 entries) indirect descriptors
[ 1.013261] vioscsi0: cmd_per_lun 128 qsize 256 seg_max 254 max_target 255
max_lun 16383
[ 1.013261] virtio1: config interrupting at msix0 vec 0
[ 1.013261] virtio1: queues interrupting at msix0 vec 1
[ 1.013261] scsibus0 at vioscsi0: 16 targets, 1024 luns per target
[ 1.013261] virtio2 at pci0 dev 18 function 0
[ 1.013261] virtio2: Virtio Network Device (rev. 0x00)
[ 1.013261] vioif0 at virtio2: Features:
0x11070020<INDIRECT_DESC,NOTIFY_ON_EMPTY,CTRL_RX,CTRL_VQ,STATUS,MAC>
[ 1.013261] vioif0: Ethernet address 7e:4f:c4:c1:60:5b
[ 1.013261] virtio2: allocated 32768 byte for virtqueue 0 for rx0, size 1024
[ 1.013261] virtio2: allocated 81920 byte for virtqueue 1 for tx0, size 256
[ 1.013261] virtio2: using 69632 byte (4352 entries) indirect descriptors
[ 1.013261] virtio2: allocated 8192 byte for virtqueue 2 for control, size
64
[ 1.013261] virtio2: config interrupting at msix1 vec 0
[ 1.013261] virtio2: queues interrupting at msix1 vec 1
[ 1.013261] ppb0 at pci0 dev 30 function 0: vendor 1b36 product 0001 (rev.
0x00)
[ 1.013261] pci1 at ppb0 bus 1
[ 1.013261] pci1: i/o space, memory space enabled
[ 1.013261] virtio3 at pci1 dev 29 function 0
[ 1.013261] virtio3: Virtio Entropy Device (rev. 0x00)
[ 1.013261] viornd0 at virtio3: Features: 0x10000000<INDIRECT_DESC>
[ 1.013261] virtio3: allocated 8192 byte for virtqueue 0 for Entropy
request, size 8
[ 1.013261] virtio3: interrupting at ioapic0 pin 11
Hmm, this is with 9.3, "I should upgrade". I should probably
also speak to my local proxmox manager to see if some option has
been left unchecked on that side of the equation.
Regards,
- Håvard
