[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Xen-users] domU hangs during boot
- To: Olivier Hanesse <olivier.hanesse@xxxxxxxxx>
- From: David Cemin <davidcemin@xxxxxxxxx>
- Date: Fri, 5 Nov 2010 10:51:23 -0200
- Cc: Richie <listmail@xxxxxxxxxxxx>, xen-users@xxxxxxxxxxxxxxxxxxx
- Delivery-date: Fri, 05 Nov 2010 05:55:16 -0700
- 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=F1fQBZ1x/JO3kkB8kLcyKPf4VXv2ZdKo7Yr8HCYlk1RQCwR+XMRrbHRANwGjpg04U1 Lb/24ekg7/dwXJ9vWOk7aZqMmh+xWm+sHpG5u79koWMKzl6nbvY1PMvqyf9wG/ahcjOB IUR1yKMYEENOfpN3UrlIG2vpnprWbvUv5rPOs=
- List-id: Xen user discussion <xen-users.lists.xensource.com>
Thank you guys,
It was missing the entry on /etc/inittab .. I've changed the root line as well, but my first assumption was right .. I was missing a tty ..
Now I have other problems .. I'll try to figure out the solutions before posting something here again.
Thank you !!
regards.
-- David 2010/11/5 Olivier Hanesse <olivier.hanesse@xxxxxxxxx>
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.
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
-- 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
|