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 [end] 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 Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Ferreira, N. L. (Nuno)
2009-Feb-09 11:19 UTC
Re: [Xen-users] Blocking problem with booting the domU
Hi Florian Just checking ... you are asking 8 vcpu''s for your domU. How many CPU''s you have then? Because if I''m not mistaken, dom0 needs to a have also (at least) a dedicated CPU to manage correctly any domU''s that may be running. Cheers, N. Rustedt, Florian wrote:> 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" > ------------------------------------------- =============================================Nuno Ricardo Santos Loureiro da Silva Ferreira NMR Spectroscopy Research Group Bijvoet Center for Biomolecular Research Utrecht University Bloembergen gebouw Padualaan 8, 3584 CH Utrecht The Netherlands P: +31.(0)30.253 9932 F: +31.(0)30.253 2652 E: n.l.ferreira@uu.nl W: http://nmr.chem.uu.nl ============================================= _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Rustedt, Florian
2009-Feb-09 11:26 UTC
AW: [Xen-users] Blocking problem with booting the domU
It's got 8 CPUs ;) No, this could not be the fault, because i had it running with that config before, but deleted unforutnately the working kernel. In between i fetched a running domu-kernel from SuSE, but i want to make it smaller, so i am wondering about the options despite the drivers -> Xen -> frontend* features that i'll need to add to keep it running as small as possible? Seems to me, that i am forced to do it on the long way, disabling one tree after the other in the kernel config and recompile until the kernel is not working any more. That will give me the blocker then... So at that point of view, the blocker is no blocker any more but a kernel-config question ;) Greets, Florian> -----Ursprüngliche Nachricht----- > Von: xen-users-bounces@lists.xensource.com > [mailto:xen-users-bounces@lists.xensource.com] Im Auftrag von > Ferreira, N. L. (Nuno) > Gesendet: Montag, 9. Februar 2009 12:19 > Cc: xen-users@lists.xensource.com > Betreff: Re: [Xen-users] Blocking problem with booting the domU > > Hi Florian > > Just checking ... you are asking 8 vcpu's for your domU. > How many CPU's you have then? Because if I'm not mistaken, > dom0 needs to a have also (at least) a dedicated CPU to > manage correctly any domU's that may be running. > > Cheers, > N. > > Rustedt, Florian wrote: > > 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" > > ----------------------------------------- > -- > =============================================> Nuno Ricardo Santos Loureiro da Silva Ferreira > > NMR Spectroscopy Research Group > Bijvoet Center for Biomolecular Research Utrecht University > Bloembergen gebouw Padualaan 8, 3584 CH Utrecht The Netherlands > > P: +31.(0)30.253 9932 > F: +31.(0)30.253 2652 > E: n.l.ferreira@uu.nl > W: http://nmr.chem.uu.nl > =============================================> > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-users >********************************************************************************************** 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 Xen-users@lists.xensource.com http://lists.xensource.com/xen-users