On Fri, Apr 9, 2010 at 4:37 AM, Caleb Call <caleb@macjunk.net>
wrote:> We recently had some issues with our VMs where we had a runaway script that
> sucked all the memory and then killed the VMs. The only way to recover was
> to do a xm destroy. We now have one machine that will boot but will not
> spawn a shell in runlevel 3. If you put it in to single user mode you can
> log in but if you try and do an ''ls'' in any directory
under / it just hangs.
> I ran an fsck and it came back saying there is no corruption. There are
no
> mounted file systems on this VM. I''m thinking it''s got a
corrupt disk
> image. Is there any way to verify this before I rebuild this VM? Or any
> suggestions on things to check? It''s using tap:aio for the
driver.
> Thoughts???
start with using "fsck -f".
Then mount that file image somewhere else with a working OS. Can be on
dom0, or (prefereably) another domU.
--
Fajar
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users