|
Scheduling maintenance is always a good idea, and if you have multiple Xen boxes that share the same storage, you should be able to live-migrate your domUs over to another server temporarily, then run updates and bounce your server, then migrate them back. That's one of the really nice things about Xen - maintenance to the underlying physical system should be transparent. Obviously this doesn't always work perfectly, but most of them time it should.
I run SLES10 SP2, as well, and, although I periodically run into issues, they don't seem to be consistent or regular issues - I've had my systems up for longer than 60 days at a time and haven't had any issues. I occasionally use the above method for maintaining them, though, so they get updated and rebooted every couple of months.
-Nick
>>> On 2009/06/04 at 06:20, James Pifer <jep@xxxxxxxxxxxxxxxx> wrote:
|
I'm running xen on SLES10SP2. It's been much more stable than SP1, but I
still occasionally have issues.
For example, one of my servers (8 CPU/32GB RAM) has five sles pv domUs
and five fully virtualized windows 2k3 domUs. It had been up for almost
60 days. Yesterday afternoon one of the sles domU's stopped responding.
I went to check on it and I couldn't using virt-manager and xm list
would hang. I ended up having to restart the server, which is obviously
a pain.
Should I have scheduled maintenance to bounce dom0 once a month? This
would probably save myself the headaches of the occasional problem. Just
wondering what others are doing.
Thanks,
James
|
<br><hr>
This e-mail may contain confidential and privileged material for the sole use of the intended recipient. If this email is not intended for you, or you are not responsible for the delivery of this message to the intended recipient, please note that this message may contain SEAKR Engineering (SEAKR) Privileged/Proprietary Information. In such a case, you are strictly prohibited from downloading, photocopying, distributing or otherwise using this message, its contents or attachments in any way. If you have received this message in error, please notify us immediately by replying to this e-mail and delete the message from your mailbox. Information contained in this message that does not relate to the business of SEAKR is neither endorsed by nor attributable to SEAKR.
|
