hello, I remember reading somewhere about the ability to reboot dom0 without loosing anything (other domUs still function) when there are troubles with dom0 driver. Is that true? if so, how can we do that? regards, aq _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
> I remember reading somewhere about the ability to reboot dom0 without > loosing anything (other domUs still function) when there are troubles > with dom0 driver. Is that true? if so, how can we do that?You can''t do this with dom0 itself - it holds too much state about the running system. The idea is to partition driver functionality out into separate domains - one domain for your network interface, another for your block interface... These service domains directly, giving good performance. When they crash, dom0 can restart them and the other domains will reconnect and carry on. This is a pretty nice trick, since drivers are one of the least reliable parts of the OS. The Xend support code for this needs tracing through - somebody reported that the domains would reconnect after the restart. Cheers, Mark _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
On 7/29/05, Mark Williamson <mark.williamson@cl.cam.ac.uk> wrote:> > I remember reading somewhere about the ability to reboot dom0 without > > loosing anything (other domUs still function) when there are troubles > > with dom0 driver. Is that true? if so, how can we do that? > > You can''t do this with dom0 itself - it holds too much state about the running > system.ah, that should be "restart device driver domain without loosing ...". as dom0 is usually device driver domain, that confused me a little ;-) thanks Mark. aq _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel