Recent content by mechanicus

Thanks, that was the solution. It's clear of course, that Proxmox was not intended to run in a virtual host. But on the other hand, it runs well with the virtio net driver. :cool:

After a long time I want to test Proxmox again, but a fresh test-installation in a KVM-machine, 4 drives (every 40 GB) and choosing RAIDZ-1 fails:

Thank you very much, Marco, runs well!

I have a kvm-image creating with dd like *.img How can I use this in Proxmox? In your "Migration of servers to Proxmox VE"-wiki, you wrote: But I don't see a way to add an exitig image, when I create a new VM.

Thank you very much, Tom. It runs well!

Hello, to start a spice session from the web interface by clicking the "SPICE"-Buttom on the right upper corner runs well. Great work! But what's the command line, if I want to start a spice connection from a desktop linux machine to a VM in my Proxmox-node by virt-viewer?

The problem ist solved. It concerns not the update to 2.3! After a long time, I decided to watch the start of the server personally on its own display. But there are 3 unfortunately events at the same time: 1.) Any kernel in the past changes the frambuffer. -> no display (I always connected...

No, that's a misunderstanding from me. I mean, that the Display is black and don't work.

2.6.32-17 was removed by the update. I don't know, what's happens, but i find out, that the X-Server don't work properly after the update, so that this causes a black screen.

I've a running HPHP DL385G5 server with an up to date Proxmox 2.2. After updating to 2.3 with apt-get update && apt-get dist-upgrade the server boot, load the ram-disk, I can see the well known messege of Firmware-Bug and other normal messeges for half a second and then it stopps with black...

Because real admins are working on the console. :D

As I understand, the old backup is not deleted after a successfull new backup, but before or after a failed backup. This behavior is wrong.