domain builder rewrite, guest kexec
PATCH 1/1 domain builder rewrite, guest kexec
Hi folks,
I've just uploaded my current state of the guest kexec and domain builder rewrite work.
Booting a new kernel via kexec starts working now, I can boot to the login prompt with a ttylinux rootfs on a ramdisk, so you can start playing with it. It's far from being bug-free though, xenstore is broken for example.
The new libxc domain builder code is in use here all day and runs stable too, although I'm using it with 32bit only at the moment.
More verbose description is here:
http://www.suse.de/~kraxel/xen/kexec.html
Patch against unstable is here:
http://www.suse.de/~kraxel/patches/domain-builder-kexec-master-xen-10647.diff
have fun & cheers,
Gerd
Signature · 2 lines
Gerd Hoffmann <[email protected]> http://www.suse.de/~kraxel/julika-dora.jpeg
Quoted 10 lines · Gerd Hoffmann
Hi folks,
I've just uploaded my current state of the guest kexec and domain builder rewrite work.
Booting a new kernel via kexec starts working now, I can boot to the login prompt with a ttylinux rootfs on a ramdisk, so you can start playing with it. It's far from being bug-free though, xenstore is broken for example.
Quoted 8 lines
The new libxc domain builder code is in use here all day and runs stable too, although I'm using it with 32bit only at the moment.
More verbose description is here:
http://www.suse.de/~kraxel/xen/kexec.htmlPatch against unstable is here:
http://www.suse.de/~kraxel/patches/domain-builder-kexec-master-xen-10647.diff
Wow, that looks pretty impressive indeed.
I wonder how much room there is for consolidating code in your domU kexec patch and the work that Magnus and I have done on dom0/hypervsisor kexec/kdump.
Signature · 3 lines
Horms H: http://www.vergenet.net/~horms/ W: http://www.valinux.co.jp/en/
Quoted 6 lines · Horms
Wow, that looks pretty impressive indeed.
I wonder how much room there is for consolidating code in your domU kexec patch and the work that Magnus and I have done on dom0/hypervsisor kexec/kdump.
I think there isn't much code which an be shared, if any. kexec'ing a domU and the physical machine are two very different problems. When merging both I think the easiest is to simply have two source files (machine-kexec-xen[0U].c) and some small stub functions which all either the dom0/hypervisor or domU kexec code.
cheers,
Gerd
Signature · 2 lines
Gerd Hoffmann <[email protected]> http://www.suse.de/~kraxel/julika-dora.jpeg
Quoted 8 lines · Gerd Hoffmann
Quoted 6 lines · Horms
Wow, that looks pretty impressive indeed.
I wonder how much room there is for consolidating code in your domU kexec patch and the work that Magnus and I have done on dom0/hypervsisor kexec/kdump.
Quoted 5 lines
I think there isn't much code which an be shared, if any. kexec'ing a domU and the physical machine are two very different problems. When merging both I think the easiest is to simply have two source files (machine-kexec-xen[0U].c) and some small stub functions which all either the dom0/hypervisor or domU kexec code.
Understood. I guess that in a lot of ways that makes the merge easier.
Signature · 3 lines
Horms H: http://www.vergenet.net/~horms/ W: http://www.valinux.co.jp/en/