New install, can't find templates

Unseen

New Member
Mar 28, 2015
15
0
1
Hey guys,

Just installed 1st time today. I'm in the interface but I see no templates at all? What's the difference between "Create CT" and "Create VM"?

Either one I choose, resource pool dropdown is empty, or template tab is blank too.

I see this in the task logs too:

starting apt-get update
Hit http://security.debian.org wheezy/updates Release.gpg
Hit http://security.debian.org wheezy/updates Release
Hit http://security.debian.org wheezy/updates/main amd64 Packages
Hit http://security.debian.org wheezy/updates/contrib amd64 Packages
Get:1 http://ftp.us.debian.org wheezy Release.gpg [2390 B]
Hit http://security.debian.org wheezy/updates/contrib Translation-en
Hit http://security.debian.org wheezy/updates/main Translation-en
Hit http://ftp.us.debian.org wheezy Release
Ign http://ftp.us.debian.org wheezy Release
Ign http://ftp.us.debian.org wheezy/main amd64 Packages/DiffIndex
Ign http://ftp.us.debian.org wheezy/contrib amd64 Packages/DiffIndex
Hit http://ftp.us.debian.org wheezy/contrib Translation-en
Hit http://ftp.us.debian.org wheezy/main Translation-en
Hit http://ftp.us.debian.org wheezy/main amd64 Packages
Hit http://ftp.us.debian.org wheezy/contrib amd64 Packages
Ign https://enterprise.proxmox.com wheezy Release.gpg
Ign https://enterprise.proxmox.com wheezy Release
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
Fetched 2390 B in 4s (517 B/s)
W: GPG error: http://ftp.us.debian.org wheezy Release: The following signatures were invalid: BADSIG 8B48AD6246925553 Debian Archive Automatic Signing Key (7.0/wheezy) <ftpmaster@debian.org>
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.
TASK ERROR: command 'apt-get update' failed: exit code 100
 
I figured a way to download an ISO, Centos 7. I created a VM with it and it won't start. Neither do I know what the root password is either.

Code:
Could not access KVM kernel module: No such file or directory
failed to initialize KVM: No such file or director
TASK ERROR: start failed: command '/usr/bin/kvm -id 100 -chardev 'socket,id=qmp,path=/var/run/qemu-server/100.qmp,server,nowait' -mon 'chardev=qmp,mode=control' -vnc unix:/var/run/qemu-server/100.vnc,x509,password -pidfile /var/run/qemu-server/100.pid -daemonize -smbios 'type=1,uuid=d0baa355-09b1-46ff-9939-3add6d69f160' -name Test -smp '4,sockets=1,cores=4,maxcpus=4' -nodefaults -boot 'menu=on,strict=on,reboot-timeout=1000' -vga cirrus -cpu kvm64,+lahf_lm,+x2apic,+sep -m 2048 -k en-us -cpuunits 1000 -device 'piix3-usb-uhci,id=uhci,bus=pci.0,addr=0x1.0x2' -device 'usb-tablet,id=tablet,bus=uhci.0,port=1' -device 'virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x3' -iscsi 'initiator-name=iqn.1993-08.org.debian:01:25f36db21ce' -drive 'file=/var/lib/vz/template/iso/CentOS-7-x86_64-Minimal-1503-01.iso,if=none,id=drive-ide2,media=cdrom,aio=native' -device 'ide-cd,bus=ide.1,unit=0,drive=drive-ide2,id=ide2,bootindex=200' -drive 'file=/var/lib/vz/images/100/vm-100-disk-1.qcow2,if=none,id=drive-ide0,format=qcow2,aio=native,cache=none,detect-zeroes=on' -device 'ide-hd,bus=ide.0,unit=0,drive=drive-ide0,id=ide0,bootindex=100' -netdev 'type=tap,id=net0,ifname=tap100i0,script=/var/lib/qemu-server/pve-bridge,downscript=/var/lib/qemu-server/pve-bridgedown' -device 'e1000,mac=AE:51:26:66:52:9E,netdev=net0,bus=pci.0,addr=0x12,id=net0,bootindex=300'' failed: exit code 1
 
Last edited:
When you create a VM with an ISO, you have to install the OS and you select the root password.
 
2 things.
First you load templates by selecting the local option from the list on the left. Than using contents tab. There is a template button there.
Second, even when you do setup from template you will need to run through setup and provide some info including root password.

Sent from my phone
 
How? I created a VM with Centos 7 and started up the console, it already asks for a password?
Did you try reading the centos install instructions? Do they have you log into root on the ISO to run the install? What ISO did you download? Have you ever installed a Linux distro before?

Simply booting an ISO is not installing to KVM. A KVM is just like a physical machine, you have to install an OS on it just like you would a physical machine.
 
Did you try reading the centos install instructions? Do they have you log into root on the ISO to run the install? What ISO did you download? Have you ever installed a Linux distro before?

Simply booting an ISO is not installing to KVM. A KVM is just like a physical machine, you have to install an OS on it just like you would a physical machine.

I've installed Centos for years, on VPS both OVZ and KVM using SoluSVM, remotely via KVM/IP and on site dedicated server machines. Promox is far different than any of these other ways.

Why is it more involved here than any other way? I created the VM using the Centos 7 ISO which I already mentioned twice. It's running and the VNC is asking for a password. So, how do I "install" it if it already asked for the ISO upon creating the VM and now asking for a root password?
 
Maybe a browser problem (I assume you use noVNC console?). Try to clear the browser cache and try again. Make sure the VM is started.

Yes, the VM is started. I mentioned that before, but it is asking for a password. It isn't a browser or cache issue. I tried several browsers and cleared cache/cookies, same thing. VM running, still asking for password.

I've tried noVNC, VNC (blank), Spice (page not found). Again, VM is "running"
 
I've installed Centos for years, on VPS both OVZ and KVM using SoluSVM, remotely via KVM/IP and on site dedicated server machines. Promox is far different than any of these other ways.

Why is it more involved here than any other way? I created the VM using the Centos 7 ISO which I already mentioned twice. It's running and the VNC is asking for a password. So, how do I "install" it if it already asked for the ISO upon creating the VM and now asking for a root password?
It is exactly the same in Proxmox as in any other hypervisor. You boot the ISO, run through the installer and install the OS. If you used an ISO and are using it through KVM, you have to install it just like a physical machine. This isn't difficult to understand. It's identical.

There is zero difference between hypervisors when it comes to installing an OS from an ISO. This simply isn't a Proxmox problem.

If you are using a CT (openvz container), then that is a different story and you need to get the password from wherever you got the vz template.

Again, booting an ISO in Proxmox KVM is identical in every way possible to booting a physical CD/DVD/USB of that OS.
 
It is exactly the same in Proxmox as in any other hypervisor. You boot the ISO, run through the installer and install the OS. If you used an ISO and are using it through KVM, you have to install it just like a physical machine. This isn't difficult to understand. It's identical.

There is zero difference between hypervisors when it comes to installing an OS from an ISO. This simply isn't a Proxmox problem.

If you are using a CT (openvz container), then that is a different story and you need to get the password from wherever you got the vz template.

Again, booting an ISO in Proxmox KVM is identical in every way possible to booting a physical CD/DVD/USB of that OS.

I'm aware it's not "difficult" and hypervisors are the same, but why it won't work here is beyond me.

1. I got the Centos 7 64bit ISO from Centos mirror off their site.
2. I created a new VM (not CT) using that ISO I placed into /var/lib/vz/template/iso
3. Inputted all info, selected that ISO. I clicked "start"

I get this error upon starting, which I mentioned before

Could not access KVM kernel module: No such file or directory
failed to initialize KVM: No such file or directory
TASK ERROR: start failed: command '/usr/bin/kvm -id 100 -chardev 'socket,id=qmp,path=/var/run/qemu-server/100.qmp,server,nowait' -mon 'chardev=qmp,mode=control' -vnc unix:/var/run/qemu-server/100.vnc,x509,password -pidfile /var/run/qemu-server/100.pid -daemonize -smbios 'type=1,uuid=bd6af92b-18bb-440f-97b5-553c99b29ef0' -name Test -smp '4,sockets=1,cores=4,maxcpus=4' -nodefaults -boot 'menu=on,strict=on,reboot-timeout=1000' -vga cirrus -cpu kvm64,+lahf_lm,+x2apic,+sep -m 2048 -k en-us -cpuunits 1000 -device 'piix3-usb-uhci,id=uhci,bus=pci.0,addr=0x1.0x2' -device 'usb-tablet,id=tablet,bus=uhci.0,port=1' -device 'virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x3' -iscsi 'initiator-name=iqn.1993-08.org.debian:01:25f36db21ce' -drive 'file=/var/lib/vz/template/iso/CentOS-7-x86_64-Minimal-1503-01.iso,if=none,id=drive-ide2,media=cdrom,aio=native' -device 'ide-cd,bus=ide.1,unit=0,drive=drive-ide2,id=ide2,bootindex=200' -drive 'file=/var/lib/vz/images/100/vm-100-disk-1.qcow2,if=none,id=drive-ide0,format=qcow2,aio=native,cache=none,detect-zeroes=on' -device 'ide-hd,bus=ide.0,unit=0,drive=drive-ide0,id=ide0,bootindex=100' -netdev 'type=tap,id=net0,ifname=tap100i0,script=/var/lib/qemu-server/pve-bridge,downscript=/var/lib/qemu-server/pve-bridgedown' -device 'e1000,mac=66:03:77:25:70:ED,netdev=net0,bus=pci.0,addr=0x12,id=net0,bootindex=300'' failed: exit code 1

Now, I've created a CT using the Centos 7 template from here https://openvz.org/Download/template/precreated

Created fine, booted fine but cannot ssh into the IP. I can access via the VNC. Not sure where the hiccup is.

On the NODE itself, I set the networking to the vmbr0 config. The eth0/eth1 are blank. I simply recall this is what it asked during Promox installation yesterday.
 
I'm aware it's not "difficult" and hypervisors are the same, but why it won't work here is beyond me.

1. I got the Centos 7 64bit ISO from Centos mirror off their site.
2. I created a new VM (not CT) using that ISO I placed into /var/lib/vz/template/iso
3. Inputted all info, selected that ISO. I clicked "start"

I get this error upon starting, which I mentioned before



Now, I've created a CT using the Centos 7 template from here https://openvz.org/Download/template/precreated

Created fine, booted fine but cannot ssh into the IP. I can access via the VNC. Not sure where the hiccup is.

On the NODE itself, I set the networking to the vmbr0 config. The eth0/eth1 are blank. I simply recall this is what it asked during Promox installation yesterday.


Your KVM error looks like you do not have virtualization features enabled in BIOS. So that tells me that you are unable to boot an ISO in KVM.

You kept saying that you were installing via ISO and getting the password prompt. If you boot a CT, you arent using an ISO, but a VZ template.

For the root password on a container created from openvz.org template...

https://openvz.org/User_Guide/Operations_on_Containers#Setting_root_Password_for_Container
 
Shoot, totally forgot about BIOS settings. Thanks for the heads up. Will enable it and update the thread.
 

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!