I worked around this by renaming 20_linux_xen to 09_linux_xen, then running
update-grub, to make sure that the xen entry was top of the list. An ugly
quick-n-dirty thing, but it worked :-)
Jon
On 19 Jul 2011, at 05:02, Todd Deshane wrote:
> 2011/7/18 Jonathan Ludlam <Jonathan.Ludlam@xxxxxxxxxxxxx>:
>> OK, there's a new blktap deb there (which you can tell by the date - at some
>> point I'll sort things so that the version numbers aren't all 0.1 and the
>> release numbers aren't all 1 :-)
>>
>
> The install works. I've cleaned up the wiki page a bit too.
>
> http://wiki.xensource.com/xenwiki/XAPI_on_debian
>
> I think I am running into a grub2 problem at the moment though. It
> won't seem to boot to the Xen hypervisor (I'm grub blind since I am
> doing this over a serial connection that doesn't show grub).
>
> I'll try to work through the grub2 issue tomorrow, but any suggestions
> are welcome.
>
> here is the /etc/grub.d/20_linux_xen file that comes with debian unstable:
>
> http://pastebin.com/KivyRSsM
>
> Any ideas as to why it won't boot into the Xen hypervisor?
>
> I've done this type of troubleshooting already:
>
> http://wiki.xensource.com/xenwiki/XenCommonProblems#head-26434581604cc8357d9762aaaf040e8d87b37752
>
> It can't even insert the modules for xen-evtchn (no such device),
> which makes sense if (like I suspect) the Xen hypervisor is not
> actually there.
>
> Xen booting messages don't show up in dmesg or /var/log/messages, so
> grub2 seems like the problem for sure.
>
> Thanks,
> Todd
>
>> Jon
>>
>> On 18 Jul 2011, at 11:10, Jonathan Ludlam wrote:
>>
>>> Hi Sébastien,
>>>
>>> Thanks for testing this out - as I wrote on the wiki page, I didn't really
>>> expect any of it to work yet, so if anything actually did work, that's a
>>> bonus! :-)
>>>
>>> On 17 Jul 2011, at 20:33, Sébastien RICCIO wrote:
>>>
>>>> Hi,
>>>>
>>>> I'm currently trying to install xapi on debian (unstable), following the
>>>> following wiki page:
>>>> http://wiki.xensource.com/xenwiki/XAPI_on_debian
>>>>
>>>> 1. Install squeeze 32-bits (it's not specified on the wiki, but I guess
>>>> it wont work with 64-bit as the xapi *.deb files are for 32).
>>>>
>>>
>>> Yes, 32 bit only at the moment. We've not tried any of this stuff in 64
>>> bit, so we're concentrating on that at the moment. I'd be very interested
>>> in knowing what happens on 64 bit though, and it is something that we'll be
>>> wanting to look into longer term.
>>>
>>>> note: you must leave an unused 1mb partition somewhere when
>>>> creating your partitions or grub2 used in sid will complain
>>>> during the dist-upgrade. This will result into an unbootable
>>>> system. (at least it happened to me)
>>>>
>>>
>>> Interesting, I didn't have this problem - when I upgraded I chose to throw
>>> out my original grub.conf and use the new one, and it does seem to boot.
>>>
>>>> 2. Edit sources.list to use unstable instead of squeeze
>>>>
>>>
>>> ..snip..
>>>
>>>> box# dpkg -i *deb
>>>>
>>>> ----8<----------
>>>> Selecting previously deselected package blktap.
>>>> (Reading database ... 37780 files and directories currently installed.)
>>>> Unpacking blktap (from blktap_0.1-1_i386.deb) ...
>>>> Selecting previously deselected package blktap-dkms.
>>>> Unpacking blktap-dkms (from blktap-dkms_0.1_all.deb) ...
>>>> Selecting previously deselected package fe.
>>>> Unpacking fe (from fe_0.1-1_i386.deb) ...
>>>> Selecting previously deselected package squeezed.
>>>> Unpacking squeezed (from squeezed_0.1-1_i386.deb) ...
>>>> Selecting previously deselected package v6d.
>>>> Unpacking v6d (from v6d_0.1-1_i386.deb) ...
>>>> Selecting previously deselected package xapi.
>>>> Unpacking xapi (from xapi_0.1-1_i386.deb) ...
>>>> Selecting previously deselected package xen-sm.
>>>> Unpacking xen-sm (from xen-sm_0.1-1_i386.deb) ...
>>>> Setting up blktap (0.1-1) ...
>>>> Setting up blktap-dkms (0.1) ...
>>>> dkms.conf: Error! No 'BUILT_MODULE_NAME' directive specified for record #0.
>>>> Error! Bad conf file.
>>>> File: /tmp/dkms.rTkg1a/dkms_binaries_only/dkms.conf
>>>> does not represent a valid dkms.conf file.
>>>>
>>>>
>>>> Unable to load DKMS tarball /usr/share/blktap-dkms/blktap-0.1.dkms.tar.gz.
>>>> Common causes include:
>>>> - You must be using DKMS 2.1.0.0 or later to support binaries only
>>>> distribution specific archives.
>>>> - Corrupt distribution specific archive
>>>>
>>>>
>>>> dpkg: error processing blktap-dkms (--install):
>>>> subprocess installed post-installation script returned error exit status 2
>>>>
>>>
>>> Right, a broken package. We've not got a nice way of making these things
>>> yet - I've got some suggestions from Daniel Stodden on how to proceed, so
>>> between us maybe we'll be able to make something that works. When I've got
>>> something new to test I'll let you know.
>>>
>>> Thanks again for helping out!
>>>
>>> Jon
>>>
>>>
>>>
>>> _______________________________________________
>>> Xen-users mailing list
>>> Xen-users@xxxxxxxxxxxxxxxxxxx
>>> http://lists.xensource.com/xen-users
>>
>>
>
>
>
> --
> Todd Deshane
> http://www.linkedin.com/in/deshantm
> http://www.xen.org/products/cloudxen.html
> http://runningxen.com/
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
|
Home