[PVE-User] no VMs listed in the webadmin pages

[Daniel Llewellyn]

I've tried to post to the forums with this query, but the forum
software reported that I don't have the correct privileges to post to
the "Proxmox VE: Installation and configuration" forum. (I've signed
up a user and confirmed the email address, but it seems that I'm still
not allowed:-/)

Anyhow, to the important problem:

I've just installed pve on bare metal hardware. initially I tried
creating a KVM/QEMU VM to house smoothwall to control my internet
connection. Once the qm command had completed successfully and
reported that the vm was created, I then moved to the virtual machines
list to start the vm to install smoothwall. However, the vm wasn't
listed in that screen. This meant that I couldn't delete the vm with
the admin interface (something which I should have done from the
commandline at this point).

I then tried creating a debian vz container, however, I forgot to
change the vm id to something other than 101. Once the command had
completed successfully, I again moved to the list of installed
machines only to find it empty again. at this point I tried rebooting
the server to see if any VMs appeared, but still no-go.. I then used
qm to "destroy" vm 101, and vzctl to destroy the 101 that it had
control of also.. then I tried recreating a vz machine which still
refused to be listed in the virtual machines list.

the relevant sections of the syslog are :

initial qemu vm:
Sep 25 00:32:00 localhost pvedaemon[2645]: creating new VM 101 on node
0 (localhost)
Sep 25 00:32:00 localhost pvedaemon[2645]: VM 101 created

initial vz vm (with qemu vm still installed):
Sep 25 00:40:04 localhost pvedaemon[2768]: creating new VM 101 on node
0 (localhost)
Sep 25 00:40:11 localhost kernel: CT: 101: started
Sep 25 00:40:15 localhost kernel: CT: 101: stopped
Sep 25 00:40:15 localhost pvedaemon[2768]: VM 101 created

and final vz vm (after having deleted the other vms using vzctl and qm
- no messages regarding these actions in the syslog):
Sep 25 00:08:55 localhost pvedaemon[3983]: creating new VM 101 on node
0 (localhost)
Sep 25 00:09:03 localhost kernel: CT: 101: started
Sep 25 00:09:06 localhost kernel: CT: 101: stopped
Sep 25 00:09:06 localhost pvedaemon[3983]: VM 101 created

it would appear that I also created a vz vm on id 102 (previously
unused) to test whether it was the conflicting qemu and vz virtual
machine IDs that was preventing them from displaying, but 102 also
refused to display.

Relevant entries from syslog regarding vm 102:
Sep 24 23:55:42 localhost pvedaemon[2980]: creating new VM 102 on node
0 (localhost)
Sep 24 23:55:49 localhost kernel: CT: 102: started
Sep 24 23:55:53 localhost kernel: CT: 102: stopped
Sep 24 23:55:53 localhost pvedaemon[2980]: VM 102 created

/tmp/vmops-102.out:
UPID:2980:1222296942:vmops:create:0:102:root
/usr/bin/pvectl vzcreate 102 --disk 8 --ostemplate
debian-4.0-standard_4.0-2_i386.tar.gz --hostname test --nameserver
192.168.1.1 --searchdomain xyz-network.com --onboot yes --userpasswd
root:test --swap 512 --mem 512 --cpus 1 --netif ifname=eth0
vzctl set 102 --vmguarpages 262144:9223372036854775807 --oomguarpages
262144:9223372036854775807 --privvmpages 262144:274644 --lockedpages
131072:131072 --disks
pace 8388608:9227468 --diskinodes 1600000:1760000 --hostname test --searchdomain
 xyz-network.com --netif_add eth0,,, --onboot yes --nameserver
192.168.1.1 --userpasswd root:test --save
Starting container ...
Container is mounted
Container start in progress...
Stopping container ...
Container was stopped
Container is unmounted
Saved parameters for CT 102
VM 102 created

/tmp/vmops-101.out for the vz version of 101:
UPID:3983:1222297735:vmops:create:0:101:root
/usr/bin/pvectl vzcreate 101 --disk 8 --ostemplate
debian-4.0-standard_4.0-2_i386.tar.gz --hostname test --nameserver
192.168.1.1 --searchdomain xyz-network.com --onboot yes --userpasswd
root:testing --ipset 192.168.1.199 --swap 512 --mem 512 --cpus 1
vzctl set 101 --vmguarpages 262144:9223372036854775807 --oomguarpages
262144:9223372036854775807 --privvmpages 262144:274644 --lockedpages
131072:131072 --diskspace 8388608:9227468 --diskinodes 1600000:1760000
--hostname test --searchdomain xyz-network.com --ipadd 192.168.1.199
--onboot yes --nameserver 192.168.1.1 --userpasswd root:testing --save
Starting container ...
Container is mounted
Container start in progress...
Stopping container ...
Container was stopped
Container is unmounted
Saved parameters for CT 101
VM 101 created


if I can provide any more information to help diagnose this problem,
let me know..

-- 
Regards,
 The Honeymonster aka Daniel Llewellyn