[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-users] no Disk drive detected when provisioning new vms or after restarting a vm

  • To: xen-users@xxxxxxxxxxxxxxxxxxx
  • From: "Fajar A. Nugraha" <list@xxxxxxxxx>
  • Date: Thu, 30 Jun 2011 00:04:24 +0700
  • Delivery-date: Wed, 29 Jun 2011 10:07:00 -0700
  • List-id: Xen user discussion <xen-users.lists.xensource.com>

On Wed, Jun 29, 2011 at 11:44 PM, mftahy <mofta7y@xxxxxxxxx> wrote:
> Hi All
> I have xen 4.0 in centos dom0
> the machine was working fine for months and yesterday out of sudden I can no
> longer provision new vms and to make things worst If any vm shutdown I
> cannot re run it again .

DId you try restarting dom0?

I know people usually reluctant to do so. as currently SOME domUs are
still running, and restarting it will mean ALL domU will have a
downtime. AFAIK though it's better to restart it NOW (or at a planned
downtime of your choice) instead of having EVERYTHING stopped working
LATER when you don't have any preparation and it cought you by

If it seems my suggestion is a bit unscientific, well, it is. I don't
know the exact cause.
However from experience, I have a Xen 3.4.2 installation that after
some time simply refuse to forward any packets for domU. Restarting
dom0 fix the problem. Probably due to some bug in that particular Xen
version, but I haven't got the time to pinpoint which one.

So for now, if you want "rock stable", stick with RHEL/Centos version
of Xen. If you upgrade it to anything else (e.g. 4.0), well, pray and
hope that it works great. Or you try Xen 4.0.2 which has some fixes,
and hope your problem is among the ones fixed by that release.


Xen-users mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.