Search results

Re: VM's recently restored after update presenting cryptic error message, unable to s I also wanted to mention that the virtual disks on the various win 7 guests were a mix of virtio with .qcow2 and ide with .raw

Re: VM's recently restored after update presenting cryptic error message, unable to s Not sure why I even tried this but via the GUI under the hard disk for one of the VM's I changed it from no cache (default) to write through and the vm started ok and it can be accesses/used. Does anyone know...

We just moved from 3.1 to 3.4 and in restoring our Windows 7 guest virtual machines from backup they are not starting. Please see the error below. kvm: -drive file=/var/lib/vz/images/201/vm-201-disk-1.qcow2,if=none,id=drive-virtio0,format=qcow2,aio=native,cache=none,detect-zeroes=on: file...

I created a template on our Proxmox server 3.1-21 and have been using it to clone new VM's as needed, Windows 7 32 bit. Today I went to clone a new VM from my template and the VM went up to 100%-105% and the VM just kind of froze. I wasn't even able to use spice viewer to see what was going...

I've read that when those keyboard lights are flashing that its an indication of a kernel panic. If there are problems with compatibility with my intel i-5 or asus mobo and the installer disk does anyone think it would be feasible to install debian wheezy and then install pve (proxmox) that way?

This is a new build and I can't install at all. I hit enter at the boot prompt and then on the next screen the Caps Lock and Scroll lock keys on the keyboard start flashing. The mother board is an Asus Z87-A The processor is 4 core i5-4670k 3.4 ghz 6mb cache I installed an ubuntu desktop on...