Dom0 is Wheezy 64 bit with kernel 3.2.0-1-amd64 version 3.2.4-1, xen from
xen-unstable.hg changeset 24823:b75664e53905 plus these patch for not fail
build:
http://xen.1045712.n5.nabble.com/PATCH-0-of-2-rename-libxl-yajl-gen-alloc-td5469362.html
On boot start to load but after start ramdisk load server reboot without
message on screen.
The grub2 entry is:
-----------------------------------------
menuentry ''Wheezy con Linux 3.2.0-1-amd64 e XEN 4.2 - RAID''
--class debian
--class gnu-linux --class gnu --class os {
set root=''(RAID-ROOT)''
echo ''Caricamento Hypervisor Xen 4.2...''
multiboot /boot/xen.gz placeholder dom0_mem=1024M
echo ''Caricamento Linux 3.2.0-1-amd64...''
linux /boot/vmlinuz-3.2.0-1-amd64 placeholder root=/dev/mapper/RAID-ROOT ro
quiet
echo ''Caricamento ramdisk iniziale...''
initrd /boot/initrd.img-3.2.0-1-amd64
}
-----------------------------------------
I try also with debug options and see with SOL (serial on lan) if see some
more but also with it see only the three echo line.
The grub2 entry is:
-----------------------------------------
menuentry ''Wheezy con Linux 3.2.0-1-amd64 e XEN 4.2 - RAID - Debug su
Seriale'' --class debian --class gnu-linux --class gnu --class os {
set root=''(RAID-ROOT)''
echo ''Caricamento Hypervisor Xen 4.2...''
multiboot /boot/xen.gz placeholder dom0_mem=1024M loglvl=all
guest_loglvl=all sync_console console_to_ring com2=19200,8n1 console=com2
echo ''Caricamento Linux 3.2.0-1-amd64...''
linux /boot/vmlinuz-3.2.0-1-amd64 placeholder root=/dev/mapper/RAID-ROOT ro
console=hvc0 earlyprintk=xen nomodeset
echo ''Caricamento ramdisk iniziale...''
initrd /boot/initrd.img-3.2.0-1-amd64
}
-----------------------------------------
Without xen boot correctly.
I have missed or wrong something on grub debug entry?
Thanks for any reply and sorry for bad english.
--
View this message in context:
http://xen.1045712.n5.nabble.com/xen-unstable-unable-to-boot-on-Wheezy-tp5493035p5493035.html
Sent from the Xen - Dev mailing list archive at Nabble.com.
On Fri, Feb 17, 2012 at 08:06:39AM -0800, Fantu wrote:> Dom0 is Wheezy 64 bit with kernel 3.2.0-1-amd64 version 3.2.4-1, xen from > xen-unstable.hg changeset 24823:b75664e53905 plus these patch for not fail > build: > http://xen.1045712.n5.nabble.com/PATCH-0-of-2-rename-libxl-yajl-gen-alloc-td5469362.html > > On boot start to load but after start ramdisk load server reboot without > message on screen. > > The grub2 entry is: > ----------------------------------------- > menuentry ''Wheezy con Linux 3.2.0-1-amd64 e XEN 4.2 - RAID'' --class debian > --class gnu-linux --class gnu --class os { > set root=''(RAID-ROOT)'' > echo ''Caricamento Hypervisor Xen 4.2...'' > multiboot /boot/xen.gz placeholder dom0_mem=1024M > echo ''Caricamento Linux 3.2.0-1-amd64...'' > linux /boot/vmlinuz-3.2.0-1-amd64 placeholder root=/dev/mapper/RAID-ROOT roIT should be ''module''> quiet > echo ''Caricamento ramdisk iniziale...'' > initrd /boot/initrd.img-3.2.0-1-amd64and ''module'' here too.> } > ----------------------------------------- > > I try also with debug options and see with SOL (serial on lan) if see some > more but also with it see only the three echo line. > > The grub2 entry is: > ----------------------------------------- > menuentry ''Wheezy con Linux 3.2.0-1-amd64 e XEN 4.2 - RAID - Debug su > Seriale'' --class debian --class gnu-linux --class gnu --class os { > set root=''(RAID-ROOT)'' > echo ''Caricamento Hypervisor Xen 4.2...'' > multiboot /boot/xen.gz placeholder dom0_mem=1024M loglvl=all > guest_loglvl=all sync_console console_to_ring com2=19200,8n1 console=com2 > echo ''Caricamento Linux 3.2.0-1-amd64...'' > linux /boot/vmlinuz-3.2.0-1-amd64 placeholder root=/dev/mapper/RAID-ROOT ro > console=hvc0 earlyprintk=xen nomodeset > echo ''Caricamento ramdisk iniziale...'' > initrd /boot/initrd.img-3.2.0-1-amd64 > } > ----------------------------------------- > > Without xen boot correctly. > > I have missed or wrong something on grub debug entry?Yup. You should have used ''module''> > Thanks for any reply and sorry for bad english. > > -- > View this message in context: http://xen.1045712.n5.nabble.com/xen-unstable-unable-to-boot-on-Wheezy-tp5493035p5493035.html > Sent from the Xen - Dev mailing list archive at Nabble.com. > > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.xensource.com > http://lists.xensource.com/xen-devel
Thanks for reply and sorry for my stupid error. Now boot but there is xl error on init startup and xl command for libxl* missing files. If can help I will post full build log(apparently without error after add 2 patches for solve xl problem with yajl2). -- View this message in context: http://xen.1045712.n5.nabble.com/xen-unstable-unable-to-boot-on-Wheezy-tp5493035p5496780.html Sent from the Xen - Dev mailing list archive at Nabble.com.
This is build log file: http://xen.1045712.n5.nabble.com/file/n5498606/xenbuild3.log xenbuild3.log About various libxl are build and installed: ls /usr/lib64/ fs libvhd.so.1.0.0 libxenstat.so.0 libblktap.a libxenctrl.a libxenstat.so.0.0 libblktapctl.a libxenctrl.so libxenstore.a libblktapctl.so libxenctrl.so.4.2 libxenstore.so libblktapctl.so.1.0 libxenctrl.so.4.2.0 libxenstore.so.3.0 libblktapctl.so.1.0.0 libxenguest.a libxenstore.so.3.0.1 libblktap.so libxenguest.so libxenvchan.a libblktap.so.3.0 libxenguest.so.4.2 libxenvchan.so libblktap.so.3.0.0 libxenguest.so.4.2.0 libxenvchan.so.1.0 libfsimage.so libxenlight.a libxenvchan.so.1.0.0 libfsimage.so.1.0 libxenlight.so libxlutil.a libfsimage.so.1.0.0 libxenlight.so.2.0 libxlutil.so libvhd.a libxenlight.so.2.0.0 libxlutil.so.1.0 libvhd.so libxenstat.a libxlutil.so.1.0.0 libvhd.so.1.0 libxenstat.so xen But they are not considered... xl list xl: error while loading shared libraries: libxlutil.so.1.0: cannot open shared object file: No such file or directory -- View this message in context: http://xen.1045712.n5.nabble.com/xen-unstable-unable-to-boot-on-Wheezy-tp5493035p5498606.html Sent from the Xen - Dev mailing list archive at Nabble.com.
On Mon, 2012-02-20 at 10:06 +0000, Fantu wrote:> This is build log file: > http://xen.1045712.n5.nabble.com/file/n5498606/xenbuild3.log xenbuild3.log > About various libxl are build and installed: > ls /usr/lib64/This is not in the library path for a Debian Wheezy (or later) systems due to changes surrounding the implementation of multiarch. This has been discussed on the list a couple of times this year -- please check the archives (might have been in the context of Ubuntu which has the same issue). You need to override config/StdGNU.mk:LIBDIR* to build on a Debian system. I use the following. Hopefully this will be fixed properly by the autoconf patches. Ian. diff -r 6ba9b19e1d79 config/StdGNU.mk --- a/config/StdGNU.mk Mon Feb 20 10:33:54 2012 +0000 +++ b/config/StdGNU.mk Mon Feb 20 10:34:05 2012 +0000 @@ -34,7 +34,7 @@ BINDIR = $(PREFIX)/bin INCLUDEDIR = $(PREFIX)/include LIBLEAFDIR = lib LIBLEAFDIR_x86_32 = lib -LIBLEAFDIR_x86_64 ?= lib64 +LIBLEAFDIR_x86_64 ?= lib LIBDIR = $(PREFIX)/$(LIBLEAFDIR) LIBDIR_x86_32 = $(PREFIX)/$(LIBLEAFDIR_x86_32) LIBDIR_x86_64 = $(PREFIX)/$(LIBLEAFDIR_x86_64)
Maybe Matching Threads
- make install not creating lib entries in /usr/lib under Ubunu 11.10
- Time for 4.2.0 rc0?
- [PATCH 0 of 1 v2] tools: honour --libdir when it is passed to ./configure
- xen-unstable: Qemu upstream domUs not start on Wheezy
- [PATCH 0 of 2 RESEND] tools: add two new compile flags and perform checks on user defined folders.