WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-users

Re: [Xen-users] xen 3.1 - domU hangs just after "xm create"

To: Mats.Petersson@xxxxxxx
Subject: Re: [Xen-users] xen 3.1 - domU hangs just after "xm create"
From: Сергей Лукашевич <lukash33@xxxxxxxxx>
Date: Mon, 25 Jun 2007 19:30:24 +0400
Cc: xen-users@xxxxxxxxxxxxxxxxxxx
Delivery-date: Mon, 25 Jun 2007 08:28:33 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx



25.06.07, 18:34, Petersson, Mats <Mats.Petersson@xxxxxxx> <>:



>  

> > -----Original Message-----

> > From: xen-users-bounces@xxxxxxxxxxxxxxxxxxx 

> > [mailto:xen-users-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of 

> > ?????? ?????????

> > Sent: 25 June 2007 15:26

> > To: xen-users@xxxxxxxxxxxxxxxxxxx

> > Subject: [Xen-users] xen 3.1 - domU hangs just after "xm create"

> > 

> > What are methods to debug domU when it hangs? Using xen 3.1 

> > compiled from sources I could not manage to launch no domU. 

> > Fot instance, I run something like this:

> > 

> > 

> > 

> > =====8<=====================

> > 

> > disk = [ 'file:/oradata-act/sles.disk,hda1,w', ',hdc:cdrom,r' ]

> > 

> > kernel = "/boot/vmlinuz-2.6.18-xen"

> > 

> > ramdisk = "/boot/initrd-2.6.18-xen"

> I take it this is the same initrd you use for Dom0? Does it have the drivers 
> for DomU too?



Yes, the same kernel and the same initrd. I beleive XEN allows using same here 
from some of 2.* versions, is not it? Initrd contains reiserfs driver - that's 
quite enough to start booting. I suspect something wrong with my compiling and 
installing XEN because domUs output NO lines to their consoles to suspect its 
kernel.



> You may want to mount the sles.disk and use "mkinitrd" to create a new 
> ramdisk from inside the sles.disk instead - that has uses the fstab of the 
> sles.disk, etc. 

> > 

> > cpus = "1"

> > 

> > vcpus = 2

> > 

> > memory = 256

> > 

> > name = "sles"

> > 

> > root="/dev/hda1 ro"

> > 

> > =====8<=====================

> > 

> > 

> > 

> > Of course, sles.disk is a reiserfs image containing unTARred 

> > SLES9.3 64bit OS.

> I hope you don't use reiserfs on reiserfs here - as if you do and you ever 
> need to "fsck" the underlaying disk, then you'll get problems - reiserfs uses 
> a "magic word" to indicate where it starts it's filesystem, and finding 
> another (same) magic word in the middle of the file-system is most certainly 
> going to make things very confused when trying to figure out what's what. 



I DO use reiserfs onto reiserfs. Sounds very strange - magics can confuse fsck? 
Do you have some additional info on this behaviour? Some link or the like? It 
would be interesting to look at.



> > 

> > 

> > 

> > The domain console outputs nothing but several spaces at the 

> > very start and the domU hangs in a few (15-25) seconds.

> "Interesting". Not sure what that could be. 

> > 

> > 

> > 

> > What are log files to analyze? What are 'debug' options?

> I'd start with "xm dmesg". If that's not saying anything useful, look at 
> /var/log/xen/xend.log and .../xend-debug.log



Only following files present there:



domain-builder-ng.log

qemu-dm.25423.log

qemu-dm.3345.log

xen-hotplug.log



xm dmesg is very interesting, thank you. Seems that every attempt to launch a 
domU yelds the following:



(XEN) mm.c:636:d0 Error getting mfn 100 (pfn 5555555555555555) from L1 entry 
8000000000100125 for dom32753



Also I saw some other strange lines from "xm dmesg" like this:



(XEN) microcode: CPU6 not a capable Intel processor



Not sure whether they appear when I experiment with HVM domUs...





> These may also not contain anything useful - but it would be where I'd start 
> trying to figure out what's wrong. 

> > 

> > 

> > 

> > I managed to run dom0  which is behaving not so bad. 

> > 

> > Only several 'segfault's in dmesg confuse me.

> Where are those segfualts from?



Well, I was trying to compile dev86 there and the ncc compiler sigfaulted. Also 
irqbalance sigfaulted:



irqbalance[3258]: segfault at 0000000000528018 rip 00000000004016ba rsp 
00007fff9cf9b8f0 error 4



> > 

> > 

> > 

> > I use SUN X4600 server which is of 64bits, 32gigs and 16 virtual CPUs.

> I expect this to be capable of running Xen for sure. 

> --

> Mats




_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users