Rejecting I/O to offline device

[Proximate]

I have an old Centos 6.6 that I cannot mess with. It's an old phone system that can't be updated else it will break right away.
Today, the phones went dead and looking at the vm, I saw 'proxmox 7 rejecting I/O to offline device' over and over.
The vm would only respond to a reset and then came back online.

In searching, I found some posts talking about the kernel version perhaps being a problem.
The kernel is: 2.6.32-504.16.2.el6.x86_64 #1 SMP Wed Apr 22 06:48:29 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux

Proxmox OS Type seems to allow 2.6 so is the problem related to kernel or something else since the other vms are all working fine.

 

[t.lamprecht]

Hi,

can you post the VMs config to have a better picture of the interactions from the VM kernel with the PVE host kernel (e.g., if virtio is used)? qm config VMID

Also, what storage are the disks from that VM one? Were there any hiccups in connection to that storage?

What software versions is the PVE node running? pveversion -v

 

[Proximate]

Hi,

Hope I have all the info you are asking for.
The vm config, the proxmox version I have but I'm not clear on 'what storage are the disks from'. I think you want to know if it was imported for example and it was, from ESX 6.7.

# pveversion -v
proxmox-ve: 7.1-1 (running kernel: 5.13.19-2-pve)
pve-manager: 7.1-7 (running version: 7.1-7/df5740ad)
pve-kernel-helper: 7.1-14
pve-kernel-5.13: 7.1-5
pve-kernel-5.13.19-2-pve: 5.13.19-4
ceph-fuse: 15.2.15-pve1
corosync: 3.1.5-pve2
criu: 3.15-1+pve-1
glusterfs-client: 9.2-1
ifupdown2: 3.1.0-1+pmx3
ksm-control-daemon: 1.4-1
libjs-extjs: 7.0.0-1
libknet1: 1.22-pve2
libproxmox-acme-perl: 1.4.1
libproxmox-backup-qemu0: 1.2.0-1
libpve-access-control: 7.1-7
libpve-apiclient-perl: 3.2-1
libpve-common-perl: 7.0-14
libpve-guest-common-perl: 4.0-3
libpve-http-server-perl: 4.1-1
libpve-storage-perl: 7.1-1
libspice-server1: 0.14.3-2.1
lvm2: 2.03.11-2.1
lxc-pve: 4.0.11-1
lxcfs: 4.0.11-pve1
novnc-pve: 1.3.0-2
proxmox-backup-client: 2.1.5-1
proxmox-backup-file-restore: 2.1.5-1
proxmox-mini-journalreader: 1.3-1
proxmox-widget-toolkit: 3.4-7
pve-cluster: 7.1-3
pve-container: 4.1-2
pve-docs: 7.1-2
pve-edk2-firmware: 3.20210831-2
pve-firewall: 4.2-5
pve-firmware: 3.3-6
pve-ha-manager: 3.3-3
pve-i18n: 2.6-2
pve-qemu-kvm: 6.1.1-2
pve-xtermjs: 4.16.0-1
qemu-server: 7.1-4
smartmontools: 7.2-1
spiceterm: 3.2-2
swtpm: 0.7.1~bpo11+1
vncterm: 1.7-1
zfsutils-linux: 2.1.4-pve1

# qm config 199
boot: order=scsi0
cores: 4
memory: 4096
name: c6-voip-srv
net0: virtio=82:E9:02:E4:D4:7E,bridge=vmbr0,firewall=1
onboot: 1
ostype: l26
scsi0: local-zfs:vm-199-disk-0,format=raw,size=5122M
scsi1: local-zfs:vm-199-disk-1,format=raw,size=64742M
scsihw: pvscsi
smbios1: uuid=e1d598dc-ecb7-4793-b509-d62c54c12cc4
vmgenid: e2cef548-3bb3-4d8e-b9bf-e58b9196493c

It has been fine since restarting it so far.

 

[Proximate]

I should mention that after this happened, I noticed I had the os type to 2.4. I have since changed it to the 2.6 option.