Re: Re: [Xen-users] Ubuntu DomU does not finish booting up.

[Matej Zary <matej.zary@xxxxxxxxx>]

On Sun, 2010-07-04 at 13:29 -0300, Pablo Morales wrote:
> Hi there guys.
> I'm trying to setup an Ubuntu 9.04 DomU, it boot fine, but does finishes
> to load completelly, this is what I get.
> 
> I'm using xen 4
> Linux netwarrior 2.6.31.13 #7 SMP Wed Jun 30 18:09:49 ART 2010 x86_64
> AMD Athlon(tm) II X4 630 Processor AuthenticAMD GNU/Linu
> 
> 
> 
> 
> * Skip starting firewall: ufw (not enabled)...                         
> [ OK ]
>  * Configuring network interfaces...                                    
> [ OK ]
>  * Setting up console font and keymap...                                
> [ OK ]
>  * Starting system log daemon...                                        
> [ OK ]
>  * Starting kernel log daemon...                                        
> [ OK ]
>  * Starting system message bus dbus                                     
> [ OK ]
>  * Starting OpenBSD Secure Shell server sshd                            
> [ OK ]
>  * Starting deferred execution scheduler
> atd                                     * Starting periodic command
> scheduler
> crond                                                                         
>  
> [ OK ]
>  * Restarting OpenBSD Secure Shell server sshd
> 
> ----
> 
> xend.log
> [2010-07-04 13:14:30 9855] DEBUG (XendDomainInfo:1891)
> XendDomainInfo.handleShutdownWatch
> [2010-07-04 13:14:30 9855] DEBUG (DevController:139) Waiting for devices
> tap2.
> [2010-07-04 13:14:30 9855] DEBUG (DevController:139) Waiting for devices
> vif.
> [2010-07-04 13:14:30 9855] DEBUG (DevController:144) Waiting for 0.
> [2010-07-04 13:14:30 9855] DEBUG (DevController:628)
> hotplugStatusCallback /local/domain/0/backend/vif/32/0/hotplug-status.
> [2010-07-04 13:14:30 9855] DEBUG (DevController:628)
> hotplugStatusCallback /local/domain/0/backend/vif/32/0/hotplug-status.
> [2010-07-04 13:14:30 9855] DEBUG (DevController:642)
> hotplugStatusCallback 1.
> [2010-07-04 13:14:30 9855] DEBUG (DevController:139) Waiting for devices
> vkbd.
> [2010-07-04 13:14:30 9855] DEBUG (DevController:139) Waiting for devices
> ioports.
> [2010-07-04 13:14:30 9855] DEBUG (DevController:139) Waiting for devices
> tap.
> [2010-07-04 13:14:30 9855] DEBUG (DevController:139) Waiting for devices
> vif2.
> [2010-07-04 13:14:30 9855] DEBUG (DevController:139) Waiting for devices
> console.
> [2010-07-04 13:14:30 9855] DEBUG (DevController:144) Waiting for 0.
> [2010-07-04 13:14:30 9855] DEBUG (DevController:139) Waiting for devices
> vscsi.
> [2010-07-04 13:14:30 9855] DEBUG (DevController:139) Waiting for devices
> vbd.
> [2010-07-04 13:14:30 9855] DEBUG (DevController:144) Waiting for 51713.
> [2010-07-04 13:14:30 9855] DEBUG (DevController:628)
> hotplugStatusCallback /local/domain/0/backend/vbd/32/51713/hotplug-status.
> [2010-07-04 13:14:31 9855] DEBUG (DevController:628)
> hotplugStatusCallback /local/domain/0/backend/vbd/32/51713/hotplug-status.
> [2010-07-04 13:14:31 9855] DEBUG (DevController:642)
> hotplugStatusCallback 1.
> [2010-07-04 13:14:31 9855] DEBUG (DevController:144) Waiting for 51714.
> [2010-07-04 13:14:31 9855] DEBUG (DevController:628)
> hotplugStatusCallback /local/domain/0/backend/vbd/32/51714/hotplug-status.
> [2010-07-04 13:14:31 9855] DEBUG (DevController:642)
> hotplugStatusCallback 1.
> [2010-07-04 13:14:31 9855] DEBUG (DevController:139) Waiting for devices
> irq.
> [2010-07-04 13:14:31 9855] DEBUG (DevController:139) Waiting for devices
> vfb.
> [2010-07-04 13:14:31 9855] DEBUG (DevController:139) Waiting for devices
> pci.
> [2010-07-04 13:14:31 9855] DEBUG (DevController:139) Waiting for devices
> vusb.
> [2010-07-04 13:14:31 9855] DEBUG (DevController:139) Waiting for devices
> vtpm.
> [2010-07-04 13:14:31 9855] INFO (XendDomain:1206) Domain LinuxVirtual-1
> (32) unpaused.
> 
> --
> Config file - No initramfs used.
> 
> kernel = "/boot/vmlinuz-2.6.31.13"
> vif = [ '' ]
> disk = [
> 'phy:NETWARRIOR/LXVIRTUAL1,xvda1,w','phy:NETWARRIOR/SWAP1,xvda2,w' ]
> root = "/dev/xvda1 ro"
> 
> 
> 
> 
> 
> Any help appreciated.
> Best Regards

I guess your DomU is running (check with xm list) and you can connect
with ssh to it, but your xm console domu access doesn't work.

If this is your case, this might help:

DomU /etc/inittab:

Replace  1:2345:respawn:/sbin/getty 38400 tty1 with 1:2345:respawn:/sbin/getty 
38400 hvc0


Regards 

Matej

<<attachment: winmail.dat>>

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