A
anton
Guest
Hi,
I've deployed Debian 5.0.6 (AMD64) on ProLiant server and after that I've done a package upgrade to Proxmox - I needed a custom disk configuration, but Proxmox 1.6 doesn't allow yet to do that at installation stage. At this point I'm feeling lucky - everything works like a charm.
However, I need to have an ability to start QEMU images for other architectures, like ARMEL and PPC. Can I do that, and if so - what should be kept in mind?
Below is the snippet from a running machine.
Thanks
I've deployed Debian 5.0.6 (AMD64) on ProLiant server and after that I've done a package upgrade to Proxmox - I needed a custom disk configuration, but Proxmox 1.6 doesn't allow yet to do that at installation stage. At this point I'm feeling lucky - everything works like a charm.
However, I need to have an ability to start QEMU images for other architectures, like ARMEL and PPC. Can I do that, and if so - what should be kept in mind?
Below is the snippet from a running machine.
Thanks
Code:
# aptitude install qemu
Reading package lists... Done
Building dependency tree
Reading state information... Done
Reading extended state information
Initializing package states... Done
Reading task descriptions... Done
The following packages are BROKEN:
pve-qemu-kvm
The following NEW packages will be installed:
bochsbios{a} debootstrap{a} libbrlapi0.5{a} libicu38{a}
libpcap0.8{a} libvdemgmt0{a} libvdeplug2{a} openbios-sparc{a}
openhackware{a} proll{a} qemu sharutils{a} vde2{a} vgabios{a}
0 packages upgraded, 14 newly installed, 0 to remove and 0 not upgraded.
Need to get 18.4MB of archives. After unpacking 51.3MB will be used.
The following packages have unmet dependencies:
pve-qemu-kvm: Conflicts: qemu but 0.9.1-10lenny1 is to be installed.
The following actions will resolve these dependencies:
Remove the following packages:
proxmox-ve-2.6.32
pve-manager
pve-qemu-kvm
qemu-server