I have installed xen on a node and while starting up a guest while in the kernel boot I am experiencing a hold/pause. The kernel stops in the boot sequence still loading the kernel at: stdout ... [ 3240.186441] xencons_init: Initializing xen vfb; pass xencons=tty to prevent this [ 3240.186538] Xen virtual console successfully installed as xvc0 [ 3240.186598] Event-channel device installed. [ 3240.201406] netfront: Initialising virtual ethernet driver. [ 3240.201627] PNP: No PS/2 controller found. Probing ports directly. [ 3240.202648] i8042.c: No controller found. [ 3240.202746] mice: PS/2 mouse device common for all mice [ 3240.202868] TCP cubic registered [ 3240.202926] NET: Registered protocol family 1 [ 3240.203128] xen-vbd: registered block device major 3 [ 3240.203142] blkfront: hda1: barriers enabled [ 3240.203930] blkfront: hda2: barriers enabled [ 3240.300872] /build/buildd/linux-source-2.6.22-2.6.22/debian/build/custom-source-xen/drivers/rtc/hctosys.c: unable to open rtc device (rtc0) [ 3240.300885] Freeing unused kernel memory: 208k freed [ 3240.547615] Capability LSM initialized [ 3240.554750] device-mapper: ioctl: 4.11.0-ioctl (2006-10-12) initialised: dm-devel@redhat.com [ 3240.625305] thermal: Unknown symbol acpi_processor_set_thermal_limit (kernel stop) xen log: ... [2007-10-13 21:06:47 xend 4818] DEBUG (DevController:478) hotplugStatusCallback 1. [2007-10-13 21:06:47 xend 4818] DEBUG (DevController:149) Waiting for 770. [2007-10-13 21:06:47 xend 4818] DEBUG (DevController:464) hotplugStatusCallback /local/domain/0/backend/vbd/7/770/hotplug-status. [2007-10-13 21:06:47 xend 4818] DEBUG (DevController:478) hotplugStatusCallback 1. [2007-10-13 21:06:47 xend 4818] DEBUG (DevController:143) Waiting for devices irq. [2007-10-13 21:06:47 xend 4818] DEBUG (DevController:143) Waiting for devices pci. [2007-10-13 21:06:47 xend 4818] DEBUG (DevController:143) Waiting for devices ioports. [2007-10-13 21:06:47 xend 4818] DEBUG (DevController:143) Waiting for devices tap. [2007-10-13 21:06:47 xend 4818] DEBUG (DevController:143) Waiting for devices vtpm. [2007-10-13 21:06:47 xend 4818] INFO (XendDomain:370) Domain node.domain.tld (7) unpaused syslog: ... Oct 13 21:20:45 server logger: /etc/xen/scripts/block: add XENBUS_PATH=backend/vbd/8/769 Oct 13 21:20:45 server logger: /etc/xen/scripts/block: add XENBUS_PATH=backend/vbd/8/770 Oct 13 21:20:45 server logger: /etc/xen/scripts/block: Writing backend/vbd/8/769/physical-device fe:0 to xenstore. Oct 13 21:20:45 server kernel: [ 4078.342105] (cdrom_add_media_watch() file=/build/buildd/linux-source-2.6.22-2.6.22/debian/build/custom-source-xen/drivers/xen/blkback/cdrom.c, line=112) nodename:backend/vbd/8/769 Oct 13 21:20:45 server kernel: [ 4078.342117] (cdrom_is_type() file=/build/buildd/linux-source-2.6.22-2.6.22/debian/build/custom-source-xen/drivers/xen/blkback/cdrom.c, line=97) type:0 Oct 13 21:20:45 server logger: /etc/xen/scripts/block: Writing backend/vbd/8/769/hotplug-status connected to xenstore. Oct 13 21:20:45 server logger: /etc/xen/scripts/block: Writing backend/vbd/8/770/physical-device fe:1 to xenstore. Oct 13 21:20:45 server kernel: [ 4078.413169] (cdrom_add_media_watch() file=/build/buildd/linux-source-2.6.22-2.6.22/debian/build/custom-source-xen/drivers/xen/blkback/cdrom.c, line=112) nodename:backend/vbd/8/770 Oct 13 21:20:45 server kernel: [ 4078.413179] (cdrom_is_type() file=/build/buildd/linux-source-2.6.22-2.6.22/debian/build/custom-source-xen/drivers/xen/blkback/cdrom.c, line=97) type:0 Oct 13 21:20:45 server logger: /etc/xen/scripts/block: Writing backend/vbd/8/770/hotplug-status connected to xenstore. Oct 13 21:20:45 server kernel: [ 4078.699586] blkback: ring-ref 8, event-channel 6, protocol 1 (x86_64-abi) Oct 13 21:20:45 server kernel: [ 4078.703606] blkback: ring-ref 9, event-channel 7, protocol 1 (x86_64-abi) The only thing I can do in another terminal is to halt the process but I am so out of ideas. Any Ideas? -Adam _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
I have done some more testing towards starting up a guest domain. Processor: AMD Opetron Host: Ubuntu - Feisty guest: Ubuntu - Feisty (created on another box tar copied onto lvm) host and guest kernel: stock ubuntu kernel version 2.6.22-14-xen guest1 file system: xfs results: ... [11479.069603] Xen virtual console successfully installed as xvc0 [11479.069668] Event-channel device installed. [11479.082110] netfront: Initialising virtual ethernet driver. [11479.082310] PNP: No PS/2 controller found. Probing ports directly. [11479.083330] i8042.c: No controller found. [11479.083414] mice: PS/2 mouse device common for all mice [11479.083520] TCP cubic registered [11479.083573] NET: Registered protocol family 1 [11479.085829] xen-vbd: registered block device major 3 [11479.085844] blkfront: hda1: barriers enabled [11479.086551] blkfront: hda2: barriers enabled [11479.180017] /build/buildd/linux-source-2.6.22-2.6.22/debian/build/custom-source-xen/drivers/rtc/hctosys.c: unable to open rtc device (rtc0) [11479.180031] Freeing unused kernel memory: 208k freed [11479.423629] Capability LSM initialized [11479.430752] device-mapper: ioctl: 4.11.0-ioctl (2006-10-12) initialised: dm-devel@redhat.com [11479.508448] thermal: Unknown symbol acpi_processor_set_thermal_limit [11479.768737] SGI XFS with ACLs, security attributes, realtime, large block/inode numbers, no debug enabled [11479.769042] SGI XFS Quota Management subsystem [11479.779278] blkfront: hda1: write barrier op failed [11479.779291] blkfront: hda1: barriers disabled [11479.787799] Filesystem "hda1": Disabling barriers, trial barrier write failed [11479.796499] XFS mounting filesystem hda1 [11481.622424] fuse init (API version 7.8) guest2 file system: ext3 results: ... [12170.146675] xencons_init: Initializing xen vfb; pass xencons=tty to prevent this [12170.146755] Xen virtual console successfully installed as xvc0 [12170.146799] Event-channel device installed. [12170.159082] netfront: Initialising virtual ethernet driver. [12170.159286] PNP: No PS/2 controller found. Probing ports directly. [12170.160306] i8042.c: No controller found. [12170.160391] mice: PS/2 mouse device common for all mice [12170.160497] TCP cubic registered [12170.160549] NET: Registered protocol family 1 [12170.162722] xen-vbd: registered block device major 3 [12170.162737] blkfront: hda1: barriers enabled [12170.163592] blkfront: hda2: barriers enabled [12170.257064] /build/buildd/linux-source-2.6.22-2.6.22/debian/build/custom-source-xen/drivers/rtc/hctosys.c: unable to open rtc device (rtc0) [12170.257081] Freeing unused kernel memory: 208k freed [12170.502083] Capability LSM initialized [12170.509249] device-mapper: ioctl: 4.11.0-ioctl (2006-10-12) initialised: dm-devel@redhat.com [12170.577503] thermal: Unknown symbol acpi_processor_set_thermal_limit [12170.893524] kjournald starting. Commit interval 5 seconds [12170.893550] EXT3-fs: mounted filesystem with ordered data mode. Each guest can be shutdown properly. It seams like they both stop at mounting the system. -Adam _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Mark Williamson
2007-Oct-16 15:43 UTC
Re: [Xen-users] DomU stops on boot inside Dom0 while booting
It looks like perhaps they''re not outputting boot information to the serial console? Perhaps this is what you''re seeing. I see you have the message "Initializing xen vfb; pass xencons=tty to prevent this" appearing. Could you try adding that to the kernel arguments and see if that gets you any further? Cheers, Mark On Sunday 14 October 2007, Adam D wrote:> I have done some more testing towards starting up a guest domain. > > Processor: AMD Opetron > Host: Ubuntu - Feisty > guest: Ubuntu - Feisty (created on another box tar copied onto lvm) > > host and guest kernel: stock ubuntu kernel version 2.6.22-14-xen > > guest1 > file system: xfs > results: > ... > [11479.069603] Xen virtual console successfully installed as xvc0 > [11479.069668] Event-channel device installed. > [11479.082110] netfront: Initialising virtual ethernet driver. > [11479.082310] PNP: No PS/2 controller found. Probing ports directly. > [11479.083330] i8042.c: No controller found. > [11479.083414] mice: PS/2 mouse device common for all mice > [11479.083520] TCP cubic registered > [11479.083573] NET: Registered protocol family 1 > [11479.085829] xen-vbd: registered block device major 3 > [11479.085844] blkfront: hda1: barriers enabled > [11479.086551] blkfront: hda2: barriers enabled > [11479.180017] > /build/buildd/linux-source-2.6.22-2.6.22/debian/build/custom-source-xen/dri >vers/rtc/hctosys.c: unable to open rtc device (rtc0) > [11479.180031] Freeing unused kernel memory: 208k freed > [11479.423629] Capability LSM initialized > [11479.430752] device-mapper: ioctl: 4.11.0-ioctl (2006-10-12) > initialised: dm-devel@redhat.com > [11479.508448] thermal: Unknown symbol acpi_processor_set_thermal_limit > [11479.768737] SGI XFS with ACLs, security attributes, realtime, large > block/inode numbers, no debug enabled > [11479.769042] SGI XFS Quota Management subsystem > [11479.779278] blkfront: hda1: write barrier op failed > [11479.779291] blkfront: hda1: barriers disabled > [11479.787799] Filesystem "hda1": Disabling barriers, trial barrier > write failed > [11479.796499] XFS mounting filesystem hda1 > [11481.622424] fuse init (API version 7.8) > > > guest2 > file system: ext3 > results: > ... > [12170.146675] xencons_init: Initializing xen vfb; pass xencons=tty to > prevent this > [12170.146755] Xen virtual console successfully installed as xvc0 > [12170.146799] Event-channel device installed. > [12170.159082] netfront: Initialising virtual ethernet driver. > [12170.159286] PNP: No PS/2 controller found. Probing ports directly. > [12170.160306] i8042.c: No controller found. > [12170.160391] mice: PS/2 mouse device common for all mice > [12170.160497] TCP cubic registered > [12170.160549] NET: Registered protocol family 1 > [12170.162722] xen-vbd: registered block device major 3 > [12170.162737] blkfront: hda1: barriers enabled > [12170.163592] blkfront: hda2: barriers enabled > [12170.257064] > /build/buildd/linux-source-2.6.22-2.6.22/debian/build/custom-source-xen/dri >vers/rtc/hctosys.c: unable to open rtc device (rtc0) > [12170.257081] Freeing unused kernel memory: 208k freed > [12170.502083] Capability LSM initialized > [12170.509249] device-mapper: ioctl: 4.11.0-ioctl (2006-10-12) > initialised: dm-devel@redhat.com > [12170.577503] thermal: Unknown symbol acpi_processor_set_thermal_limit > [12170.893524] kjournald starting. Commit interval 5 seconds > [12170.893550] EXT3-fs: mounted filesystem with ordered data mode. > > > Each guest can be shutdown properly. It seams like they both stop at > mounting the system. > > -Adam > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-users-- Dave: Just a question. What use is a unicyle with no seat? And no pedals! Mark: To answer a question with a question: What use is a skateboard? Dave: Skateboards have wheels. Mark: My wheel has a wheel! _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Maybe Matching Threads
- DomU booting just stops
- How to boot Ubuntu 9.04(Jaunty) or Debian Lenny (vmlinuz-2.6.26-2-686-bigmem) as domU under Lenny''s vmlinuz-2.6.26-2-xen-686 as dom0. PVM''s initrd issue
- Problem with tap:aio
- Bug#479197: xen-hypervisor-3.2-1-amd64: hypervisor fails to load dom0 ("not an ELF binary")
- issues after rebooting