Re: AW: Updates for Proxmox VE 2.2 - including QEMU 1.3
After a clean of the file /etc/pve/priv/authorized_keys the upgrade completes ok
After a clean of the file /etc/pve/priv/authorized_keys the upgrade completes ok
Updates for Proxmox VE 2.2 - including QEMU 1.3
- Thread starter martin
- Start date
Re: AW: Updates for Proxmox VE 2.2 - including QEMU 1.3
A bug in the previous version wrote many useless lines into /etc/pve/priv/authorized_keys. Try to remove those duplicated entries to free up some space.
A bug in the previous version wrote many useless lines into /etc/pve/priv/authorized_keys. Try to remove those duplicated entries to free up some space.
Since I used "stop" for shutting down the VM's I guess your first requirement that the VM should be disabled was fulfilled but I was strucked by the second requirement - I did not enable the resource before trying migration?
Assumption: A HA enabled resource is never able to do off-line migration?
Just a quick question: Is migrating a VM from old to new release impossible even if it has been restarted?
If the answer is yes then a new update strategy should be used:
1) Choose the two nodes in your cluster running the least critical VM's and use them as node1 and node2
2) Update node1
3) Update node2
4) restart all VM's on node1 - use "stop" to avoid migration followed by start
5) Migrate all VM's all VM's away from node1 to node2
6) Reboot node1
7) When node1 is available migrate all VM's from node2 to node1 - this time online-migration should work
8) Reboot node2
9) Upgrade Node3..n
10) On each of these nodes restart all VM's - use "stop" to avoid migration followed by start
11) Migrate all VM's from nodes3..n to either node1 or node2 - online-migration should work
If the answer is yes then a new update strategy should be used:
1) Choose the two nodes in your cluster running the least critical VM's and use them as node1 and node2
2) Update node1
3) Update node2
4) restart all VM's on node1 - use "stop" to avoid migration followed by start
5) Migrate all VM's all VM's away from node1 to node2
6) Reboot node1
7) When node1 is available migrate all VM's from node2 to node1 - this time online-migration should work
8) Reboot node2
9) Upgrade Node3..n
10) On each of these nodes restart all VM's - use "stop" to avoid migration followed by start
11) Migrate all VM's from nodes3..n to either node1 or node2 - online-migration should work
- update to latest packages so that all hosts in your HA cluster have latest qemu 1.3
- poweroff/shutdown all your HA enabled VMs, do this inside the VM (as soon as the VM is off, HA manager starts them again automatically, now using qemu 1.3)
- in order to apply the new kernel, you need to reboot. as we still not have the maintenance mode, you need to live-migrate all VM´s manually away from a node and then you can reboot. do this step by step for all nodes.
Re: AW: Updates for Proxmox VE 2.2 - including QEMU 1.3
Paolo posted an updated bios.bin file to the qemu-devel list:
http://lists.gnu.org/archive/html/qemu-devel/2012-12/msg01703.html
Download that file and copy it to /usr/share/kvm/bios.bin
That should fix the problem - please can you test?
Paolo posted an updated bios.bin file to the qemu-devel list:
http://lists.gnu.org/archive/html/qemu-devel/2012-12/msg01703.html
Download that file and copy it to /usr/share/kvm/bios.bin
That should fix the problem - please can you test?
Re: AW: Updates for Proxmox VE 2.2 - including QEMU 1.3
Hi,
I have just tried. No dice:-\
Using this bios resolves in a kernel panic. See screen dump.
Hi,
I have just tried. No dice:-\
Using this bios resolves in a kernel panic. See screen dump.
Re: AW: Updates for Proxmox VE 2.2 - including QEMU 1.3
I just installed a fresh freebsd9 with success, just following this howto:
http://pve.proxmox.com/wiki/FreeBSD_Guest_Notes
(without the fix, it just hang)
I just installed a fresh freebsd9 with success, just following this howto:
http://pve.proxmox.com/wiki/FreeBSD_Guest_Notes
(without the fix, it just hang)
Re: AW: Updates for Proxmox VE 2.2 - including QEMU 1.3
The file in that post is only half the size of the bios.bin it's replacing. Might be truncated?
The file in that post is only half the size of the bios.bin it's replacing. Might be truncated?
Re: AW: Updates for Proxmox VE 2.2 - including QEMU 1.3
My try was with FreeNas 8 aka FreeBSD 8.3
My try was with FreeNas 8 aka FreeBSD 8.3
Re: AW: Updates for Proxmox VE 2.2 - including QEMU 1.3
Hi Tom and Dietmar,
I can confirm that the pve-qemu-kvm-1.3-10 has solved my problems
Thanks for a prompt fix of this problem.
Hi Tom and Dietmar,
I can confirm that the pve-qemu-kvm-1.3-10 has solved my problems
Thanks for a prompt fix of this problem.Re: AW: Updates for Proxmox VE 2.2 - including QEMU 1.3
Just been reading the qemu 1.3 change log.
This feature jumped out at me.
"A new block job is supported: live disk mirroring (also known as "storage migration") moves data from an image to another. A new command "block-job-complete" is used to switch the VM to use the destination image exclusively."
I am guessing that in time this would technically mean that we could be getting live migration of kvm machines, using direct attached storage???
Rob
Just been reading the qemu 1.3 change log.
This feature jumped out at me.
"A new block job is supported: live disk mirroring (also known as "storage migration") moves data from an image to another. A new command "block-job-complete" is used to switch the VM to use the destination image exclusively."
I am guessing that in time this would technically mean that we could be getting live migration of kvm machines, using direct attached storage???
Rob
Re: AW: Updates for Proxmox VE 2.2 - including QEMU 1.3
yes, live storage migration, and also live storage migration during live migration. (so live migration with local storage is technically possible)
yes, live storage migration, and also live storage migration during live migration. (so live migration with local storage is technically possible)
I tested now... It is still not fixed ... going back to drbd-8.3 branch ... merry christmas to all