unable to create fairsched node

[dlsvkd]

Hello,
We're unable to restart a windows VM and we keep getting 'unable to create fairsched node'.

The complete error message is here: http://pastebin.com/r18vFNf3 . Any help appreciated.

server3:~# pveversion  --verbose
proxmox-ve-2.6.32: 3.2-121 (running kernel: 2.6.32-27-pve)
pve-manager: 3.2-1 (running version: 3.2-1/1933730b)
pve-kernel-2.6.32-27-pve: 2.6.32-121
lvm2: 2.02.98-pve4
clvm: 2.02.98-pve4
corosync-pve: 1.4.5-1
openais-pve: 1.1.4-3
libqb0: 0.11.1-2
redhat-cluster-pve: 3.2.0-2
resource-agents-pve: 3.9.2-4
fence-agents-pve: 4.0.5-1
pve-cluster: 3.0-12
qemu-server: 3.1-15
pve-firmware: 1.1-2
libpve-common-perl: 3.0-14
libpve-access-control: 3.0-11
libpve-storage-perl: 3.0-19
pve-libspice-server1: 0.12.4-3
vncterm: 1.1-6
vzctl: 4.0-1pve4
vzprocps: 2.0.11-2
vzquota: 3.1-2
pve-qemu-kvm: 1.7-4
ksm-control-daemon: 1.1-1
glusterfs-client: 3.4.2-1

 

[dietmar]

Please update your system. Then test again.

 

[dlsvkd]

This system is in production with running VMs.
Are you suggesting an 'apt-get update && apt-get upgrade' ?

 

[dlsvkd]

This system is in production with running VMs.
Are you suggesting an 'apt-get update && apt-get upgrade' ?

I tried an 'apt-get update' and got the below. How to proceed?

server3:~# apt-get update
Get:1 http://security.debian.org wheezy/updates Release.gpg [836 B]
Get:2 http://security.debian.org wheezy/updates Release [102 kB]
Get:3 http://ftp.us.debian.org wheezy Release.gpg [1,655 B]
Get:4 http://ftp.us.debian.org wheezy Release [168 kB]
Get:5 http://security.debian.org wheezy/updates/main amd64 Packages [239 kB]
Get:6 http://security.debian.org wheezy/updates/contrib amd64 Packages [14 B]
Get:7 http://security.debian.org wheezy/updates/contrib Translation-en [14 B]
Get:8 http://security.debian.org wheezy/updates/main Translation-en [136 kB]
Get:9 http://ftp.us.debian.org wheezy/main amd64 Packages [5,841 kB]
Ign https://enterprise.proxmox.com wheezy Release.gpg
Ign https://enterprise.proxmox.com wheezy Release
Get:10 http://ftp.us.debian.org wheezy/contrib amd64 Packages [42.0 kB]
Get:11 http://ftp.us.debian.org wheezy/contrib Translation-en [34.8 kB]
Get:12 http://ftp.us.debian.org wheezy/main Translation-en [3,848 kB]
Err https://enterprise.proxmox.com wheezy/pve-enterprise amd64 Packages
  The requested URL returned error: 401
Ign https://enterprise.proxmox.com wheezy/pve-enterprise Translation-en_US
Ign https://enterprise.proxmox.com wheezy/pve-enterprise Translation-en
Fetched 10.4 MB in 6s (1,570 kB/s)
W: Failed to fetch https://enterprise.proxmox.com/debian/dists/wheezy/pve-enterprise/binary-amd64/Packages  The requested URL returned error: 401

E: Some index files failed to download. They have been ignored, or old ones used instead.

 

[dlsvkd]

bump. What are the correct update/upgrade procedures ?

 

[udo]

bump. What are the correct update/upgrade procedures ?

Hi,
use the right repository - see here http://pve.proxmox.com/wiki/Package_repositories

You need an reboot to activate the new kernel! If you only stop/start the VMs, they use the actual software.

Udo (don't forget the backups!)

 

[dlsvkd]

Thanks for the info .. but my apologies for being a bit dense here ... This was a fresh install (about a year ago) and there have been no system changes since.

What could have happened to make VMs unbootable all of a sudden ?

In other words, if I haven't make any system changes ( no apt-get updates, or upgrades or reboots ) why would VMs stop being bootable ? What am I missing here?

 

[udo]

Hi,
your issue has perhaps nothing to do with the version, but the developer don't want to look for issues, which are fixed long time ago.
This is the reason, why you should upgrade.

Can you try to use virtio-net instead of e1000 in a VM?

Udo