[SOLVED] This is killing me I can NOT get QEMU installed.

chgo2oc

New Member
Feb 11, 2020
16
0
1
55
San Clemente California
I know it kernel issues and a repository issue. I have a community licensed installed. I have re-imaged the thing 3X, somehow the boot partition might have been changed led to this crazyness.. I have tried every solution i could find

I have removed and replaced the repositories, I have attempted

does anyone know hot to re-image thing? any help would be great


Code:
root@pve:/proc# systemd-detect-virt
none

Code:
proc/cpuinfo

model           : 158
model name      : Intel(R) Core(TM) i5-8400 CPU @ 2.80GHz


Code:
root@pve:~# apt-get install qemu
Reading package lists... Done
Building dependency tree       
Reading state information... Done
Package qemu is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source

E: Package 'qemu' has no installation candidate



Code:
root@pve:~# dpkg -l | grep pve-kernel
ii  pve-firmware                         3.1-3                        all          Binary firmware code for the pve-kernel
ii  pve-kernel-5.4                       6.3-3                        all          Latest Proxmox VE Kernel Image
ii  pve-kernel-5.4.73-1-pve              5.4.73-1                     amd64        The Proxmox PVE Kernel Image
ii  pve-kernel-5.4.78-2-pve              5.4.78-2                     amd64        The Proxmox PVE Kernel Image
ii  pve-kernel-helper                    6.3-3                        all          Function for various kernel maintenance tasks.



Code:
root@pve:~# pveversion -v
proxmox-ve: 6.3-1 (running kernel: 5.4.78-2-pve)
pve-manager: 6.3-3 (running version: 6.3-3/eee5f901)
pve-kernel-5.4: 6.3-3
pve-kernel-helper: 6.3-3
pve-kernel-5.4.78-2-pve: 5.4.78-2
pve-kernel-5.4.73-1-pve: 5.4.73-1
ceph-fuse: 15.2.6-pve1
corosync: 3.0.4-pve1
criu: 3.11-3
glusterfs-client: 5.5-3
ifupdown: 0.8.35+pve1
ksm-control-daemon: 1.3-1
libjs-extjs: 6.0.1-10
libknet1: 1.16-pve1
libproxmox-acme-perl: 1.0.5
libproxmox-backup-qemu0: 1.0.2-1
libpve-access-control: 6.1-3
libpve-apiclient-perl: 3.1-3
libpve-common-perl: 6.3-2
libpve-guest-common-perl: 3.1-3
libpve-http-server-perl: 3.0-6
libpve-storage-perl: 6.3-3
libqb0: 1.0.5-1
libspice-server1: 0.14.2-4~pve6+1
lvm2: 2.03.02-pve4
lxc-pve: 4.0.3-1
lxcfs: 4.0.3-pve3
novnc-pve: 1.1.0-1
proxmox-backup-client: 1.0.5-1
proxmox-mini-journalreader: 1.1-1
proxmox-widget-toolkit: 2.4-3
pve-cluster: 6.2-1
pve-container: 3.3-1
pve-docs: 6.3-1
pve-edk2-firmware: 2.20200531-1
pve-firewall: 4.1-3
pve-firmware: 3.1-3
pve-ha-manager: 3.1-1
pve-i18n: 2.2-2
pve-qemu-kvm: 5.1.0-7
pve-xtermjs: 4.7.0-3
qemu-server: 6.3-2
smartmontools: 7.1-pve2
spiceterm: 3.1-1
vncterm: 1.6-2
zfsutils-linux: 0.8.5-pve1


Code:
root@pve:/proc# ls -1 /dev/disk/by-id/
ata-Samsung_SSD_850_EVO_500GB_S2RANX0H723071P
ata-Samsung_SSD_850_EVO_500GB_S2RANX0H723071P-part1
ata-Samsung_SSD_850_EVO_500GB_S2RANX0H723071P-part9
ata-Samsung_SSD_860_EVO_500GB_S59UNS0N703774J
ata-Samsung_SSD_860_EVO_500GB_S59UNS0N703774J-part1
ata-Samsung_SSD_860_EVO_500GB_S59UNS0N703774J-part9
ata-SanDisk_SDSSDH31000G_1827A2802048
ata-SanDisk_SDSSDH31000G_1827A2802048-part1
ata-SanDisk_SDSSDH31000G_1827A2802048-part9
ata-WDC_WD1001FALS-00J7B0_WD-WMATV0994545
ata-WDC_WD1001FALS-00J7B0_WD-WMATV0994545-part1
ata-WDC_WD1001FALS-00J7B0_WD-WMATV0994545-part9
nvme-ADATA_SX8200NP_2I2520034897
nvme-ADATA_SX8200NP_2I2520034897-part1
nvme-ADATA_SX8200NP_2I2520034897-part2
nvme-ADATA_SX8200NP_2I2520034897-part3
nvme-nvme.126f-324932353230303334383937-4144415441205358383230304e50-00000001
nvme-nvme.126f-324932353230303334383937-4144415441205358383230304e50-00000001-part1
nvme-nvme.126f-324932353230303334383937-4144415441205358383230304e50-00000001-part2
nvme-nvme.126f-324932353230303334383937-4144415441205358383230304e50-00000001-part3
wwn-0x50014ee05674809c
wwn-0x50014ee05674809c-part1
wwn-0x50014ee05674809c-part9
wwn-0x5001b448b6f86413
wwn-0x5001b448b6f86413-part1
wwn-0x5001b448b6f86413-part9
wwn-0x5002538d410baf13
wwn-0x5002538d410baf13-part1
wwn-0x5002538d410baf13-part9
wwn-0x5002538e30731b63
wwn-0x5002538e30731b63-part1
wwn-0x5002538e30731b63-part9
 
Last edited:
t.lamprecht, I got it solved sorry I didn't document the string that gave me the solution.. essentially... it involved deleting the hook and creating a new empty hook.. the post indicated it was risky move user beware.. but it worked..

mark solved thanks
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!