That makes sense Alexandre, thank you. I'm glad I wasn't going crazy :-) -----Original Message----- From: Alexandre DERUMIER [mailto:[email protected]] Sent: 26 February 2015 08:22 To: Chris Murray Cc: proxmoxve Subject: Re: [PVE-User] VM boot options after 3.4 upgrade
Hi, yes the change is here: https://git.proxmox.com/?p=qemu-server.git;a=commit;h=cf71f776cb9ab246e9718c5a95a0518223f9f51b Now, you really need to specify the boot device. ----- Mail original ----- De: "Chris Murray" <[email protected]> À: "proxmoxve" <[email protected]> Envoyé: Mercredi 25 Février 2015 20:39:33 Objet: [PVE-User] VM boot options after 3.4 upgrade Hi there, I think something may be altering the boot order during the upgrade process to 3.4, but I haven't quite put my finger on it. Some VMs don't start properly afterward, as they use VIRTIO disks, yet the boot process is set to use IDE0 first. It's easy enough to change to VIRTIO0, of course, I'm just thinking surely they'd never have booted if they'd been incorrect all along. I've only noticed this after upgrading to 3.4. I haven't noticed a pattern yet, and of course now I'm upgraded, there's no going back to test again. Chris _______________________________________________ pve-user mailing list [email protected] http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-user ----- No virus found in this message. Checked by AVG - www.avg.com Version: 2015.0.5736 / Virus Database: 4293/9154 - Release Date: 02/21/15 _______________________________________________ pve-user mailing list [email protected] http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-user
