Xen project Mailing List

On Mon, Feb 24, 2014 at 2:34 AM, Ian Campbell <Ian.Campbell@xxxxxxxxxx> wrote:

On Thu, 2014-02-20 at 12:03 -0700, Shane Johnson wrote:
> I apparently forgot to forward this on to the list - Sorry about that.

[...]

> Sorry for the vagueness. I was trying to keep things short and sweet
> but I guess I failed. I'll do better next time.

No worries.

> The Guest domains storage was on dedicated logical volumes. These I
> would snapshot and image for a backup. When the Dom0 crashed, I lost
> the original volumes and restored them from the images to new volumes
> that are currently on a external HD for portability for trying to get
> this bugger up or worst case resort to trying to recover the files
> using some sort of forensic process. Unfortunately, I lost the
> original host OS and all the configuration files. The guests where
> originally created on either this machine that crashed or my desktop
> and migrated via sneaker net to the crashed host.
>
>
> Yes the machine I am having a problem with is a HVM guest running
> Windows 2000 that's sole purpose was a file server.
>
>
> The 100% CPU usage was for the DomU in xl top.

Are you sure you were using xl before? The default in Wheezy was xend/xm
and the version of xl in Xen 4.1 (in Wheezy) is a bit tech preview.

Yes, I read that xl is the future toolstack, so I switched my hosts to it so I wouldn't have to catch up later.

From your screenshot it looks like the BIOS trying to read from the
CDROM.

I have tried it with boot = "cd" and "dc" and whether or not I press a key to get into windows setup, it always acts the same way - freezing right when it would seem like it should be accessing the MBR of the disk.

You have disks named "xvd?" and xen_platform_pci=0, which I think it a
bit unusual, I'm not sure what the result would be. Can you try naming
your disks "hd?" instead.

From reading http://xenbits.xen.org/docs/4.2-testing/man/xl.cfg.5.html it was my understanding these where needed or at least desirable for guests using the GPLPV drivers. I use the xvd for the disks cause I found it easier for the cd-rom stuff.

> I don't know which version was on the old machine for sure, but I
> imagine it wasn't too far off from the wheezy test machine ( The host
> OS was updated every Friday.) and it is 0.10.2 (This is
> from /usr/lib/xen-4.1/bin/qemu-dm --help)

That's the qemu version not the Xen version.

Sorry I thought that is what you where asking for. If you need more on the Xen version, I can get that for you.

> xenctx says it can't trace dom0

You need to give it a domid as a parameter.

I get this message no matter what domain I enter into the command. Please let me know if you would like me to try this again with the hd in the disk parameters.

> I am including the log files xl output and screenshots in an
> attachment.

Thanks. I took a look and nothing mega weird jumped out -- just the few
queries above.

Ian.

I rereading some material since my last post, a question has come to mind, what effect would not pausing the domain have on the bootability of the image file?

Here is some other information. I have been able to add the LVM's to another windows instance but everything just come across as the dynamic volumes are corrupted and I can see the files of the Basic volume. The basic partition is just the Windows OS and the dynamic volumes are where the data I need is. I was trying to reboot the original OS volume to try and see if it would recognize the dynamic volumes, but that is what keeps freezing. I have tried some file/partition recovery software with no luck. If anyone has any ideas on how I can get this data back it would be greatly appreciated.

Thank you.

--
Shane D. Johnson

IT Administrator

Rasmussen Equipment

Re: [Xen-users] Fwd: DomU freeze