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/
Home Products Support Community News


[Xen-users] Blocking problem with booting the domU

To: <xen-users@xxxxxxxxxxxxxxxxxxx>
Subject: [Xen-users] Blocking problem with booting the domU
From: "Rustedt, Florian" <Florian.Rustedt@xxxxxxxxxxx>
Date: Mon, 9 Feb 2009 10:19:30 +0100
Delivery-date: Mon, 09 Feb 2009 01:20:20 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
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>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcmKl4MMSJ0FyI0aT2uGHJX1VudtbQ==
Thread-topic: Blocking problem with booting the domU
Hello List,

My domU stops at the point, where it should start the init-process and gives no 
hint, why:
Xen virtual console successfully installed as xvc0
Event-channel device installed.
netfront: Initialising virtual ethernet driver.
i2c /dev entries driver
NET: Registered protocol family 17
xen-vbd: registered block device major 8
blkfront: sda5: barriers enabled
registered taskstats version 1
XENBUS: Device with no driver: device/vkbd/0
XENBUS: Device with no driver: device/vfb/0
XENBUS: Device with no driver: device/console/0
XFS mounting filesystem sda5
VFS: Mounted root (xfs filesystem) readonly.
Freeing unused kernel memory: 172k freed
udevd version 128 started

Now it idles and does nothing. If i connect via vnc, i get only the qemu 
console, don't know why?!
The domU-config:
xen0 ~ # cat /etc/xen/suse-default
name    = "suse-default";
memory  = 1024;
cpus = "0-7";
vcpus = 8;

kernel = "/boot/vmlinuz_domU"
extra=" root=/dev/sda5"

disk = [ 'file:/VirtualMachines/Templates/Suse_hda5,sda5,w' ]
vif = [ "mac=00:16:3e:1b:65:10" ];

vfb = [ 'type=vnc,vncunused=1' ]
vnc = 1
vncconsole = 0
keymap = "de"
As the kernel is "homemade" i am assuming that there must be something more 
that should be activated than only the xen-frontend-configs?

I want to have a smallest possible kernel, only containing the features i'ld 
need to boot into the paravirtualized image, so i deactivated most.

So what is happening between "freeing memory" and "starting init" that i could 
have broke?

Kind regards, Florian
IMPORTANT: The contents of this email and any attachments are confidential. 
They are intended for the 
named recipient(s) only.
If you have received this email in error, please notify the system manager or 
the sender immediately and do 
not disclose the contents to anyone or make copies thereof.
*** eSafe scanned this email for viruses, vandals, and malicious content. ***
Xen-users mailing list
<Prev in Thread] Current Thread [Next in Thread>