[Slackbuilds-users] xen again

[Paul McCormack]

Hey Chris,

I haven't been clear.. I did build the custom kernel with the scripts 
from the slackbuild after installing xen.

I checked I was running domain0 by

xl list

Name ID Mem VCPUs State Time(s)

Domain-0 0 512 4 r----- 9.2


Its the domU I'm having trouble with. slackware installed on the image 
but then I can't create domU.


When you mention a custom kernel I assume that you mean vmlinuz-3.10.17-xen?


is that correct?

I just got this to work using debian wheezy, learneda lot,  but still 
haven't ruled out going back to slack... I just need a wee lie down 
first.. :)

pretty freaky having 2 servers on one box.... ;)

On 8/17/2014 2:26 AM, Chris Abela wrote:
>
> I suppose that you are referring to the INFO file. The required field 
> is for dependencies.
>
> Chris Abela
>
> On 17 Aug 2014 01:07, "Paul McCormack" <islandmarmot at gmail.com 
> <mailto:islandmarmot at gmail.com>> wrote:
>
>     I thought that was optional and if it it is required then
>     shouldn't the slackbuild reflect that?
>
>     On 16 Aug 2014 18:16, "Chris Abela" <kristofru at gmail.com
>     <mailto:kristofru at gmail.com>> wrote:
>
>         Reading
>         http://slackbuilds.org/slackbuilds/14.1/system/xen/dom0/README.dom0
>         I understand that you need a custom kernel for dom0.
>
>         Chris
>
>         On 16 Aug 2014 16:51, "Paul McCormack" <islandmarmot at gmail.com
>         <mailto:islandmarmot at gmail.com>> wrote:
>
>             I'm not sure that my first post made it through so the
>             humour may be lost but here goes.
>
>
>             I have a dom0 running on Slackware64 14.1, 3.10.17 with
>             multilib and updated using slackpkg "Slackware64 14.1"
>
>
>             xl list gives me
>
>
>             Name ID Mem VCPUs State Time(s)
>
>             Domain-0 0 512 4 r----- 9.2
>
>
>             I built the domU image as per the slackbuild and I can
>             mount it. I modified the script to install from a USB
>             drive. This works but lilo did not run.
>
>
>             when I try to create the domain xl panics..
>
>
>             In the mydom config file the first two lines are
>
>
>             kernel = "/boot/vmlinuz-xen"
>
>             ramdisk = "/boot/initrd-xen.gz"
>
>
>             So I'm a little confused as I expected to see
>
>
>             kernel = "/boot/vmlinuz"
>
>             ramdisk = "/boot/initrd.gz"
>
>
>             Checking the slackware.img /boot/vmlinuz ->
>             /boot/vmlinuz-huge-3.10.17
>
>
>             I guess that the way forward is to either copy the "*-xen"
>             files to mnt/boot and or run mkinitrd.
>
>
>             I think the former due to fact that we symlink
>             lib/modules/3.10.17-xen to lib/modules/3.10.17
>
>
>             ok tried that - copied vmlinuz-xen and initrd-xem.gz over
>             to boot no change
>
>
>             xl create -c mydom results in.........
>
>
>             -------------------------------------------------------------------
>
>             Parsing config from mydom
>
>             xc: error: panic: xc_dom_bzimageloader.c:655:
>             xc_dom_probe_bzimage_kernel: boot protocol too old (0203):
>             Invalid kernel
>
>             xc: error: panic: xc_dom_core.c:621: xc_dom_find_loader:
>             no loader found: Invalid kernel
>
>             libxl: error: libxl_dom.c:384:libxl__build_pv:
>             xc_dom_parse_image failed: No such file or directory
>
>             libxl: error: libxl_create.c:900:domcreate_rebuild_done:
>             cannot (re-)build domain: -3
>
>             -------------------------------------------------------------------
>
>
>             am I heading in the right direction here? I've tried
>             searching and can't figure it out.
>
>
>             _______________________________________________
>             SlackBuilds-users mailing list
>             SlackBuilds-users at slackbuilds.org
>             <mailto:SlackBuilds-users at slackbuilds.org>
>             http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
>             Archives -
>             http://lists.slackbuilds.org/pipermail/slackbuilds-users/
>             FAQ - http://slackbuilds.org/faq/
>
>
>
>         _______________________________________________
>         SlackBuilds-users mailing list
>         SlackBuilds-users at slackbuilds.org
>         <mailto:SlackBuilds-users at slackbuilds.org>
>         http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
>         Archives -
>         http://lists.slackbuilds.org/pipermail/slackbuilds-users/
>         FAQ - http://slackbuilds.org/faq/
>
>
>
>     _______________________________________________
>     SlackBuilds-users mailing list
>     SlackBuilds-users at slackbuilds.org
>     <mailto:SlackBuilds-users at slackbuilds.org>
>     http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
>     Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/
>     FAQ - http://slackbuilds.org/faq/
>
>
>
>
> _______________________________________________
> SlackBuilds-users mailing list
> SlackBuilds-users at slackbuilds.org
> http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - http://slackbuilds.org/faq/
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20140817/9a6968eb/attachment.html>