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] domU hangs during boot

To: David Cemin <davidcemin@xxxxxxxxx>
Subject: Re: [Xen-users] domU hangs during boot
From: Olivier Hanesse <olivier.hanesse@xxxxxxxxx>
Date: Fri, 5 Nov 2010 13:17:55 +0100
Cc: Richie <listmail@xxxxxxxxxxxx>, xen-users@xxxxxxxxxxxxxxxxxxx
Delivery-date: Fri, 05 Nov 2010 05:19:13 -0700
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type; bh=MSVQU7FVJ8w2PEg9LDJpFOGUa0dDCTEPA9yy44Lb5KQ=; b=OAgKurJTgpJv+U/mXlJAp9vBsFialg+7m4DiR4JYtP74eHH4wZ7iCjNAEnsqNt9wFp fjGVCNsFwgsrRIMsS6lK+86RlqFZ7tBG56Z4KFYl5YPZG/MO7ghAE7ssBo1dqxJYJfnn jMbJOIAajP1V7eR9lBflBxz3ADBvFCnrZD+DM=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=TeT4YO9IBGWGJyXT1kNNJraU6IfoqTRpy+XJreEr6OHcJVZnwbfkt98v8/3uxcx8fz Jb+T2YnfT3B4yRSCJR/DITJh3wKOnpTv2M0edUDw+Ar9zfFD2cyBCOsFEO/Bb7M4pP6U idSyrneDeOq5koJRV3gadMWwY8JRCFfswGeuw=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <AANLkTikCTeSkMRHyMOMeYAcQ-g4QZ6jcZoWw3zCgxTQZ@xxxxxxxxxxxxxx>
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/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
References: <AANLkTimYdruj9CLszRQ4WxafLz2rhtsnT5-9c4A_YeJG@xxxxxxxxxxxxxx> <4CD33A5F.8000701@xxxxxxxxxxxx> <AANLkTikCTeSkMRHyMOMeYAcQ-g4QZ6jcZoWw3zCgxTQZ@xxxxxxxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
Richie is right. PV Kernel uses xvda.

Try with :

disk = ['file:/xen/domains/dom1/diskimage.img,xvda1,w','file:/xen/domains/dom1/swapimage.img,xvda5,w']

And you have to modify the "root" entry :

root = "/dev/xvde1 ro" -->  root = "/dev/xvda1 ro"

Did you modify the /etc/inittab file inside your domU to get a getty on hvc0 ?


2010/11/5 David Cemin <davidcemin@xxxxxxxxx>


2010/11/4 Richie <listmail@xxxxxxxxxxxx>

On 11/04/2010 03:56 PM, David Cemin wrote:

disk = ['file:/xen/domains/dom1/diskimage.img,sda1,w','file:/xen/domains/dom1/swapimage.img,sda5,w']

PV uses xvda.

It doesnt make sense. This is the path of the "disk" that is mapped to sda on dom0 FS. I have created this "diskimage.img" and formatted int ext3 to be the disk of my VM. Besides, there is no xvda in my /dev inside domU

(initramfs) ls /dev
console             full                tty17               tty51
null                kmsg                tty18               tty52
pts                 mem                 tty19               tty50
loop1               oldmem              tty2                tty54
block               port                tty20               tty53
ram7                random              tty21               tty56
ram13               urandom             tty22               tty57
ram3                zero                tty23               tty55
ram4                blktap-control      tty25               tty59
ram5                cpu_dma_latency     tty26               tty58
ram9                mapper              tty24               tty60
ram6                network_latency     tty28               tty6
ram15               network_throughput  tty29               tty62
ram8                nvram               tty27               tty63
ram2                snapshot            tty30               tty61
ram11               vga_arbiter         tty3                tty8
ram14               xen                 tty32               tty9
loop3               raw                 tty33               tty7
ram12               hvc0                tty31               vcs
ram10               hvc1                tty35               usbmon0
loop4               hvc2                tty36               vcsa
loop6               hvc3                tty34               vcsa1
loop2               hvc4                tty38               vcs1
loop7               hvc5                tty37               xvde5
ram0                hvc6                tty4                vcs2
loop0               hvc7                tty40               vcsa2
loop5               ptmx                tty39               vcs3
xvde1               tty                 tty42               vcsa3
disk                tty0                tty43               vcs4
ram1                tty1                tty41               vcsa4
ttyS0               tty10               tty45               vcs5
char                tty11               tty44               vcsa5
ttyS1               tty12               tty47               vcs6
ttyS2               tty13               tty48               vcsa6
ttyS3               tty14               tty46
cpu                 tty15               tty5
input               tty16               tty49


Any other Ideas? 

Thank you !!

cheers! 

--
David

 


INIT: Entering runlevel: 4
Starting enhanced syslogd: rsyslogd.
Starting periodic command scheduler: crond.


My guess is that it is starting gdm at this point.  I would either try booting single user mode or mount the domU fs in dom0 and remove the /etc/init/gdm.conf (or rcX.d links) file.



--
David Cemin
mobile: +55 51 93523097
home:   +55 51 32763785
email: davidcemin@xxxxxxxxx

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

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
<Prev in Thread] Current Thread [Next in Thread>