Search results

I use Proxmox 2.0 with 2 vm: A Debian 5 server and an IPcop. On the Debian server there are running several databases (mySQL, postgres, OpenLDAP). The running vm are backuped with the Proxmox backup function every night, using "snapshot". Now I heard that ist's very likely that snapshots of vm...

That's too inconvenient. But: Is using a virtual ide hd really slower than scsi? Using a real hd ok, the scsi drive / bus has a higher data rate, but in a vm?

can the developers confirm this?

Well, I have no experiences with virtio. By experience with real hds I thought scsi would be the best choice. When creating a new vm, the default recommendation ist ide. So after my experience with scsi I'm thinking that this is the kind of hd the developers would prefer / suggest to use...

The installation is not a production system. It's a testing system which should switch to a production system during 2012. According to your roadmap version 2.0 will be stable until Q1/2012.

At least the debian server boots from the virtual ide hd. That reduces the expenditure of reconfiguration very much. Can I assume that such a problem will not appear again using ide hds in the vms? Otherwise it would imply not to update the proxmox system any more. But that would come into...

The try to migrate the IPCop from scsi to ide failed. in the fstab there are entries like A change to doesn't take any effect. I will now try this with the debian server. If you have any more ideas to reactivate my vms please tell me.

I tried this with the IPCop-vm. But it ends in a kernel panic. If I am lucky, it's only because of wrong entries in te fstab (sda instead of hda) I'll try it again with chancged fstab.

ok, but is there a possibility to downgrade the system, that scsi will work again? Downgrading of pve-qemu-kvm alone didn't take effekt. The attempt to downgrade some of the other packages which were updated when the problem occured, fails.

Fist: I'm not a member, so I can't read it. Further, I feel overextended with a developer mailinglist. I'm just a user who made the mistake to 1. chose the beta 2. make an update too early Will there be an update that solves the Problem soon?

now I tried dpkg -i pve-qemu-kvm_0.15.0-1_amd64.deb and the VMs start again. But the Problem with scsi-HDs is the same. What can I do?

I tried to downgradw with the following command: The output was No errors. But now no VM starts anymore - no matter which kind of hd. Please help me to get a working Installation again.

I never had to do a downgrade before. Can you tell me how to do this?

Hallo, I have created 2 VMs (one with an IPCop and one with an Debian Server) with each one scsi Disk. That went fine until today. When I try to start them, I get an error message in the console: Booting from local disk... Boot failed... Press a key to retry When I create an new VM with an...