ISO and Templates Resident on the local Proxmox system

[gcmartin]

I am using Proxmox Beta 2. This is machine is used for beta testing and feedback to Proxmox. It is a 64bit X2 with 4GB of RAM. It intends to test KVM features ONLY, currently booting several Linux distros and an WinXP. This system is pristine. Except for a mount to copy ISO files manually to this system. It is pristine. Edit: I did edit the Interfaces file to change eth0 to eth1 (where the LAN cable to connected) on the bridge definition I am having issues with

1. Drive definitions
2. CD boot issues (This were problems with Beta 1 for booting a newly created VM guest)
3. Understanding the requirements for manually adding ISO images so that the Proxmox web manager could find them.
4. Understanding that Proxmox web manager will ONLY see an ISO iff it is "re-uploaded" via the web manager's upload. < @Tom showed a way to get the web manager to make ISOs visable.>
5. Getting a KVM virtual guest setup to boot the ISO of a Linux distro

Edit: The Proxmox has been redownloaded. Using Proxmox V2Beta2. It has cleared the error I was getting with the wrong QEMU version. System is Pristine and testing is begun again.
Several ISOs are uploaded via Proxmox GUI. A 64bit KVM VM has been created with the ISO as the target for Installation.

Here's the current status.
The KVM VM was started but, I cannot see anything it the Console GUI. The Proxmox GUI indicates that the VM is running, but the Console GUI is showing a "Stopped" status without any boot-time messages???
Running ===> Stopped ===>
There is the small 64bit ISO here. It is uploaded and "running". Advice would be appreciated

Direction

My plan is to address booting from an ISO uploaded, and finally, to boot from DVD drive attached to the system. (Nothing fancy). PVE Version

pve-manager: 2.0-10 (pve-manager/2.0/7a10f3e6)
running kernel: 2.6.32-6-pve
proxmox-ve-2.6.32: 2.0-52
pve-kernel-2.6.32-6-pve: 2.6.32-52
lvm2: 2.02.86-1pve1
clvm: 2.02.86-1pve1
corosync-pve: 1.4.1-1
openais-pve: 1.1.4-1
libqb: 0.6.0-1
redhat-cluster-pve: 3.1.7-1
pve-cluster: 1.0-11
qemu-server: 2.0-3
pve-firmware: 1.0-13
libpve-common-perl: 1.0-7
libpve-access-control: 1.0-2
libpve-storage-perl: 2.0-6
vncterm: 1.0-2
vzctl: 3.0.29-3pve3
vzprocps: 2.0.11-2
vzquota: 3.0.12-3
pve-qemu-kvm: 0.15.0-1
ksm-control-daemon: 1.1-1

Files MANUALLY added to /mnt/pve/template/iso. Is this correct layout you expect?

# ls -la /mnt/pve/template/iso  total 1050932  
drwxr-xr-x 2 root root      4096 Nov 23 10:48 .  
drwxr-xr-x 3 root root      4096 Nov 22 22:07 ..  
-rwxr-xr-x 1 root root 108679168 Nov 23 10:48 guydog-5.0.1.iso  
-rwxr-xr-x 1 root root 376559616 Nov 23 10:48 LH64-512_Remaster4Servers.iso  
-rw-r--r-- 1 root root 373293056 Nov 22 22:12 proxmox-ve_2.0-7a10f3e6-17.iso  
-rwxr-xr-x 1 root root 216543232 Nov 23 10:49 Puppy528-002M.iso

I will try to post, here, all info so that it can easily be followed by support team(s).

 

[tom]

you got old version of qemu-server, update will help!

 

[gcmartin]

Thanks @Tom.

Would it be prudent for me to apply the same "aptitude ..." command to this beta 2 as was advised for Beta1 users?
They were advised to upgrade as follows: aptitude update && aptitude dist-upgrade.

Or what would you advise for competency.

Thanks in advance.

 

[tom]

yes, run

 [I][B]aptitude update && aptitude dist-upgrade[/B][/I]

in any case, read the logs and output and check if you need a reboot (in the case of a kernel upgrade) and check also your package list with:

pveversion -v