Hi all,
I'm faced with reactivation software 1C.
After upgrade from version 5.1-44 to 5.2-1 guest VM windows server 2008 r2 has changed a little.
And software detected this change.
Current proxmox version:
Detected os changes, was:
Get new report of software:
So changed something not important to windows activation but significant to 1c software.
VM config is:
Previously in the past I've added machine code to keep same hardware as during installation. Now I guess I need to do in same way.
Looked at changlog qemu 2.11 but I don't notice what could influence on my problem.
Later I will try to boot older kernel. Did I missed something changed?
I'm faced with reactivation software 1C.
After upgrade from version 5.1-44 to 5.2-1 guest VM windows server 2008 r2 has changed a little.
And software detected this change.
Current proxmox version:
proxmox-ve: 5.2-2 (running kernel: 4.15.17-1-pve)
pve-manager: 5.2-1 (running version: 5.2-1/0fcd7879)
pve-kernel-4.15: 5.2-1
pve-kernel-4.13: 5.1-44
pve-kernel-4.15.17-1-pve: 4.15.17-9
pve-kernel-4.13.16-2-pve: 4.13.16-48
pve-kernel-4.10.17-2-pve: 4.10.17-20
corosync: 2.4.2-pve5
criu: 2.11.1-1~bpo90
glusterfs-client: 3.8.8-1
ksm-control-daemon: 1.2-2
libjs-extjs: 6.0.1-2
libpve-access-control: 5.0-8
libpve-apiclient-perl: 2.0-4
libpve-common-perl: 5.0-31
libpve-guest-common-perl: 2.0-16
libpve-http-server-perl: 2.0-8
libpve-storage-perl: 5.0-23
libqb0: 1.0.1-1
lvm2: 2.02.168-pve6
lxc-pve: 3.0.0-3
lxcfs: 3.0.0-1
novnc-pve: 0.6-4
proxmox-widget-toolkit: 1.0-18
pve-cluster: 5.0-27
pve-container: 2.0-23
pve-docs: 5.2-4
pve-firewall: 3.0-9
pve-firmware: 2.0-4
pve-ha-manager: 2.0-5
pve-i18n: 1.0-5
pve-libspice-server1: 0.12.8-3
pve-qemu-kvm: 2.11.1-5
pve-xtermjs: 1.0-5
qemu-server: 5.0-26
smartmontools: 6.5+svn4324-1
spiceterm: 3.0-5
vncterm: 1.5-3
zfsutils-linux: 0.7.8-pve1~bpo9
pve-manager: 5.2-1 (running version: 5.2-1/0fcd7879)
pve-kernel-4.15: 5.2-1
pve-kernel-4.13: 5.1-44
pve-kernel-4.15.17-1-pve: 4.15.17-9
pve-kernel-4.13.16-2-pve: 4.13.16-48
pve-kernel-4.10.17-2-pve: 4.10.17-20
corosync: 2.4.2-pve5
criu: 2.11.1-1~bpo90
glusterfs-client: 3.8.8-1
ksm-control-daemon: 1.2-2
libjs-extjs: 6.0.1-2
libpve-access-control: 5.0-8
libpve-apiclient-perl: 2.0-4
libpve-common-perl: 5.0-31
libpve-guest-common-perl: 2.0-16
libpve-http-server-perl: 2.0-8
libpve-storage-perl: 5.0-23
libqb0: 1.0.1-1
lvm2: 2.02.168-pve6
lxc-pve: 3.0.0-3
lxcfs: 3.0.0-1
novnc-pve: 0.6-4
proxmox-widget-toolkit: 1.0-18
pve-cluster: 5.0-27
pve-container: 2.0-23
pve-docs: 5.2-4
pve-firewall: 3.0-9
pve-firmware: 2.0-4
pve-ha-manager: 2.0-5
pve-i18n: 1.0-5
pve-libspice-server1: 0.12.8-3
pve-qemu-kvm: 2.11.1-5
pve-xtermjs: 1.0-5
qemu-server: 5.0-26
smartmontools: 6.5+svn4324-1
spiceterm: 3.0-5
vncterm: 1.5-3
zfsutils-linux: 0.7.8-pve1~bpo9
Detected os changes, was:
Get new report of software:
So changed something not important to windows activation but significant to 1c software.
VM config is:
boot: dc
bootdisk: virtio0
cores: 4
cpu: kvm64
ide2: none,media=cdrom
machine: pc-i440fx-1.7
memory: 8192
name: 1cc
net0: e1000=72:51:B4:BB:F7:06,bridge=vmbr0
ostype: win7
sockets: 1
virtio0: ss800_004:vm-1110-disk-1,size=53G
virtio1: ss800_004:vm-1110-disk-2,size=80G
bootdisk: virtio0
cores: 4
cpu: kvm64
ide2: none,media=cdrom
machine: pc-i440fx-1.7
memory: 8192
name: 1cc
net0: e1000=72:51:B4:BB:F7:06,bridge=vmbr0
ostype: win7
sockets: 1
virtio0: ss800_004:vm-1110-disk-1,size=53G
virtio1: ss800_004:vm-1110-disk-2,size=80G
Previously in the past I've added machine code to keep same hardware as during installation. Now I guess I need to do in same way.
Looked at changlog qemu 2.11 but I don't notice what could influence on my problem.
Later I will try to boot older kernel. Did I missed something changed?