Windows not seeing NIC in KVM.

[Chaser7783]

I upgraded proxmox from 1.9 to 2.1. I am able to see all my vm's and connect to them via vnc console. The core server is able to ping out etc, as well as the openvz vms.
The issues is with the Windows KVM, prior to the upgrade they all saw the nic and was able to connect, after the update the NIC is not showing in device manager.

Here is the output from pveversion -v
pve-manager: 2.1-14 (pve-manager/2.1/f32f3f46)
running kernel: 2.6.32-14-pve
proxmox-ve-2.6.32: 2.1-74
pve-kernel-2.6.32-13-pve: 2.6.32-72
pve-kernel-2.6.32-14-pve: 2.6.32-74
pve-kernel-2.6.32-6-pve: 2.6.32-55+ovzfix-1
pve-kernel-2.6.32-7-pve: 2.6.32-55+ovzfix-2
lvm2: 2.02.95-1pve2
clvm: 2.02.95-1pve2
corosync-pve: 1.4.3-1
openais-pve: 1.1.4-2
libqb: 0.10.1-2
redhat-cluster-pve: 3.1.92-3
resource-agents-pve: 3.9.2-3
fence-agents-pve: 3.1.8-1
pve-cluster: 1.0-27
qemu-server: 2.0-49
pve-firmware: 1.0-18
libpve-common-perl: 1.0-30
libpve-access-control: 1.0-24
libpve-storage-perl: 2.0-31
vncterm: 1.0-3
vzctl: 3.0.30-2pve5
vzprocps: 2.0.11-2
vzquota: 3.0.12-3
pve-qemu-kvm: 1.1-8
ksm-control-daemon: 1.1-1

 

[spirit]

proxmox 2.1 use different virtual pci address "slot" for network card (like physical pci slot on a motheboard), and windows assign ip address by slot position.

You should see new network interfaces (if not try to rescan hardware in windows), but you need to assign ip address again on these network cards.

 

[tom]

try starting in safe-mode, then reboot. I had some guest with exactly this behavior.