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 _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
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@obrien-pifer.com> 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 -------- 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. _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On Thu, Jun 4, 2009 at 7:28 PM, Nick Couchman <Nick.Couchman@seakr.com> wrote:> 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.Just wondering, if you "periodically run into issues", why do you keep using SLES? Other distros can run Xen with minimum problem. -- Fajar _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On Thu, Jun 04, 2009 at 08:09:21PM +0700, Fajar A. Nugraha wrote:> On Thu, Jun 4, 2009 at 7:28 PM, Nick Couchman <Nick.Couchman@seakr.com> wrote: > > 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. > > Just wondering, if you "periodically run into issues", why do you keep > using SLES? Other distros can run Xen with minimum problem. >Or at least upgrade to SLES11. It has a lot newer Xen (+dom0 kernel) code. -- Pasi _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
My problems with SLES/XEN are minimal. By periodically, I don''t mean that it happens regularly and I just accept it and move on - I mean that once in a while something happens that causes me to have to reboot a bunch of domUs or something like that. More often than not, the reason behind the issues is really just that I made a stupid mistake - perhaps when I set up the domU - and I just end up paying for that mistake. My SLES10 XEN boxes are fairly solid. The biggest issue I have is with live migration - sometimes it just hangs up or doesn''t finish correctly. I haven''t bothered to look into why that happens, yet, so I don''t know if it''s a network issue, a XEN problem, or a SLES issue. -Nick>>> On 2009/06/04 at 07:09, "Fajar A. Nugraha" <fajar@fajar.net> wrote:On Thu, Jun 4, 2009 at 7:28 PM, Nick Couchman <Nick.Couchman@seakr.com> wrote:> 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.Just wondering, if you "periodically run into issues", why do you keep using SLES? Other distros can run Xen with minimum problem. -- Fajar -------- 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. _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On Thu, 2009-06-04 at 20:09 +0700, Fajar A. Nugraha wrote:> On Thu, Jun 4, 2009 at 7:28 PM, Nick Couchman <Nick.Couchman@seakr.com> wrote: > > 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. > > Just wondering, if you "periodically run into issues", why do you keep > using SLES? Other distros can run Xen with minimum problem. >SLES is our company standard. I''m not absolutely locked, and I could look at SLES11. James _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On Thu, 2009-06-04 at 06:28 -0600, Nick Couchman wrote:> 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 >I''ve played with migrate a little, but I''m don''t think I have enough resources (RAM) on the other servers to be able to migrate all of them, or even the few most important ones. I have one server with 8GB of RAM (that''s been up for 116 days) I have two servers with 16GB and another with 32GB of RAM. The latter three share an ocfs2 file system so migrating is possible, at least for the linux pv domUs. Thanks, James _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
I'm considering that...my main issue doing that is the fact that I use OCFS2 for my shared filesystem. One of the downsides of OCFS2 is that it is very particular about the version of OCFS2 running on each of the nodes, which means that I can't have 3 SLES10 nodes + 1 SLES11 node - I have to do most or all of the upgrades at the same time in order for OCFS2 to operate properly on all the nodes. Kind of a pain... -Nick>>> On 2009/06/04 at 08:04, Pasi Kärkkäinen<pasik@iki.fi> wrote:On Thu, Jun 04, 2009 at 08:09:21PM +0700, Fajar A. Nugraha wrote:> On Thu, Jun 4, 2009 at 7:28 PM, Nick Couchman<Nick.Couchman@seakr.com> wrote:> > I run SLES10 SP2, as well, and, although I periodically run intoissues,> > they don't seem to be consistent or regular issues - I've had mysystems up> > for longer than 60 days at a time and haven't had any issues. > > Just wondering, if you "periodically run into issues", why do youkeep> using SLES? Other distros can run Xen with minimum problem. >Or at least upgrade to SLES11. It has a lot newer Xen (+dom0 kernel) code. -- Pasi -------- 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. _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
> > I''m running xen on SLES10SP2. It''s been much more stable than SP1, butI> 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 foralmost> 60 days. Yesterday afternoon one of the sles domU''s stoppedresponding.> 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 isobviously> 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. >I haven''t found the need to reboot my xen servers for any reason other than security updates. One had an uptime over 6 months (until a datacenter operator hit the power button on my server by mistake) and another one has been up for similar times. The only problem I have had was on a test machine - once the domain id got up to 2000 or so (very frequent stopping and starting of domains to test migrations etc) it seemed to run out of resources. I haven''t seen that with 3.3.x though. James _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On Fri, Jun 05, 2009 at 11:28:09AM +1000, James Harper 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. > > > > I haven''t found the need to reboot my xen servers for any reason other > than security updates. > > One had an uptime over 6 months (until a datacenter operator hit the > power button on my server by mistake) and another one has been up for > similar times. > > The only problem I have had was on a test machine - once the domain id > got up to 2000 or so (very frequent stopping and starting of domains to > test migrations etc) it seemed to run out of resources. I haven''t seen > that with 3.3.x though. >I have Xen 3.x servers that have been running for years, no problems. I still even have a server running Xen 2.0, I think it has uptime of around 3 years now.. running a couple of domUs. It was rebooted around 3 years ago because of a fan failure :) -- Pasi _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On Fri, Jun 5, 2009 at 2:50 PM, Pasi Kärkkäinen <pasik@iki.fi> wrote:> I have Xen 3.x servers that have been running for years, no problems. > > I still even have a server running Xen 2.0, I think it has uptime of around > 3 years now.. running a couple of domUs. It was rebooted around 3 years ago > because of a fan failure :)What distro did you use? James was having problem with SLES10SP2. -- Fajar _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On Fri, Jun 05, 2009 at 03:04:34PM +0700, Fajar A. Nugraha wrote:> On Fri, Jun 5, 2009 at 2:50 PM, Pasi Kärkkäinen <pasik@iki.fi> wrote: > > I have Xen 3.x servers that have been running for years, no problems. > > > > I still even have a server running Xen 2.0, I think it has uptime of around > > 3 years now.. running a couple of domUs. It was rebooted around 3 years ago > > because of a fan failure :) > > What distro did you use? James was having problem with SLES10SP2. >Yeah, that was not SLES. Just wanted to give a general idea how it should work :) -- Pasi _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On Fri, 2009-06-05 at 11:34 +0300, Pasi Kärkkäinen wrote:> On Fri, Jun 05, 2009 at 03:04:34PM +0700, Fajar A. Nugraha wrote: > > On Fri, Jun 5, 2009 at 2:50 PM, Pasi Kärkkäinen <pasik@iki.fi> wrote: > > > I have Xen 3.x servers that have been running for years, no problems. > > > > > > I still even have a server running Xen 2.0, I think it has uptime of around > > > 3 years now.. running a couple of domUs. It was rebooted around 3 years ago > > > because of a fan failure :) > > > > What distro did you use? James was having problem with SLES10SP2. > > > > Yeah, that was not SLES. Just wanted to give a general idea how it should > work :)Thanks for all the replies. Seems possible that SLES is my issue. Thankfully it doesn''t happen that often. It was worse on SP1 (don''t remember the xen version). Maybe it will get even better when SLES catches up some more. Thanks, again, James _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Yes, SP1 was a pretty bad release of SLES - SP2 is much better. Hopefully I'll get to try out SLES11 here, soon...>>> On 2009/06/05 at 05:56, James Pifer <jep@obrien-pifer.com> wrote:On Fri, 2009-06-05 at 11:34 +0300, Pasi Kärkkäinen wrote:> On Fri, Jun 05, 2009 at 03:04:34PM +0700, Fajar A. Nugraha wrote: > > On Fri, Jun 5, 2009 at 2:50 PM, Pasi Kärkkäinen <pasik@iki.fi>wrote:> > > I have Xen 3.x servers that have been running for years, noproblems.> > > > > > I still even have a server running Xen 2.0, I think it has uptimeof around> > > 3 years now.. running a couple of domUs. It was rebooted around 3years ago> > > because of a fan failure :) > > > > What distro did you use? James was having problem with SLES10SP2. > > > > Yeah, that was not SLES. Just wanted to give a general idea how itshould> work :)Thanks for all the replies. Seems possible that SLES is my issue. Thankfully it doesn't happen that often. It was worse on SP1 (don't remember the xen version). Maybe it will get even better when SLES catches up some more. Thanks, again, James -------- 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. _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Hello, Am 04.06.2009 um 14:20 Uhr schrieb James Pifer <jep@obrien-pifer.com>:> 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.have you tried to restart xend?> 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 > > > > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-users-- greetings eMHa _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On Tue, 2009-06-09 at 21:34 +0200, Markus Hochholdinger wrote:> Hello, > > Am 04.06.2009 um 14:20 Uhr schrieb James Pifer <jep@obrien-pifer.com>: > > 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. > > have you tried to restart xend?Yes, I tried that. It didn''t change anything. xm was still hung and the same systems were running as before the restart, and the others would not start. I was pretty much stuck. Although xend acted like it restarted, I''m not confident that it actually restarted. James _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users