Hi,
I''ve prepared a Ubuntu 10.04 LTS server on a Xen 3.2-1 host running
Debian Lenny on kernel 2.6.26-2-xen-amd64. The Ubuntu 10.04 domU is
running a 2.6.32-24-server kernel from the Ubuntu repositories, which is
(must be :-) ) xen-aware. The domU uses pygrub to boot and it works like
a charm.
Now I''m trying to deploy this domU on a Xen 3.2-1 host running Debian
Etch on kernel 2.6.18-6-xen-amd64. When I xm create domU on this system,
I see the pygrub boot menu but then an error message comes up:
Error: (2, ''Invalid kernel'', ''xc_dom_find_loader:
no loader found\n'')
When I use pygrub directly (ie. rather than xm create), I get this message:
# pygrub /dev/d/xm.dt2
linux (kernel /var/run/xend/boot/boot_kernel.jZIjuL)(ramdisk
/var/run/xend/boot/boot_ramdisk.pQPLZC)(args "root=/dev/xvda1 ro")
Any suggestions for how to further diagnose this?
kind regards,
Jan
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
Hi,
A bit more info on this:
Full extract from /var/log/xen/xend.log for this domU session:
[2010-09-27 05:06:22 4409] DEBUG (__init__:1072)
XendDomainInfo.create([''vm'', [''name'',
''dt2.para''], [''memory'',
''2048''],
[''on_poweroff'', ''destroy''],
[''on_reboot'', ''restart''],
[''on_crash'',
''restart''], [''vcpus'', 2],
[''on_xend_start'', ''ignore''],
[''on_xend_stop'',
''ignore''], [''image'',
[''linux'', [''root'', ''/dev/xvda1
ro'']]], [''device'',
[''vbd'', [''uname'',
''phy:/dev/d/xm.dt2''], [''dev'',
''xvda1''], [''mode'',
''w'']]], [''device'', [''vif'',
[''ip'', ''192.168.212.12''],
[''mac'',
''00:16:3E:00:1F:00''], [''bridge'',
''eth0'']]]])
[2010-09-27 05:06:22 4409] DEBUG (__init__:1072)
XendDomainInfo.constructDomain
[2010-09-27 05:06:22 4409] DEBUG (__init__:1072) Balloon: 2097396 KiB
free; need 2048; done.
[2010-09-27 05:06:22 4409] DEBUG (__init__:1072) Adding Domain: 9
[2010-09-27 05:06:22 4409] DEBUG (__init__:1072)
XendDomainInfo.initDomain: 9 256
[2010-09-27 05:06:22 8161] DEBUG (__init__:1072) Launching bootloader as
[''/usr/bin/pygrub'', ''--args=root=/dev/xvda1 ro
'',
''--output=/var/run/xend/boot/xenbl.10154'',
''/dev/d/xm.dt2''].
[2010-09-27 05:06:29 4409] DEBUG (__init__:1072)
_initDomain:shadow_memory=0x0, memory_static_max=0x80000000,
memory_static_min=0x0.
[2010-09-27 05:06:29 4409] DEBUG (__init__:1072) Balloon: 2097388 KiB
free; need 2097152; done.
[2010-09-27 05:06:29 4409] INFO (__init__:1072) buildDomain os=linux
dom=9 vcpus=2
[2010-09-27 05:06:29 4409] DEBUG (__init__:1072) domid = 9
[2010-09-27 05:06:29 4409] DEBUG (__init__:1072) memsize = 2048
[2010-09-27 05:06:29 4409] DEBUG (__init__:1072) image
/var/run/xend/boot/boot_kernel.0BCcGq
[2010-09-27 05:06:29 4409] DEBUG (__init__:1072) store_evtchn = 1
[2010-09-27 05:06:29 4409] DEBUG (__init__:1072) console_evtchn = 2
[2010-09-27 05:06:29 4409] DEBUG (__init__:1072) cmdline root=/dev/xvda1
ro
[2010-09-27 05:06:29 4409] DEBUG (__init__:1072) ramdisk
/var/run/xend/boot/boot_ramdisk.hQst77
[2010-09-27 05:06:29 4409] DEBUG (__init__:1072) vcpus = 2
[2010-09-27 05:06:29 4409] DEBUG (__init__:1072) features [2010-09-27
05:06:29 4409] ERROR (__init__:1072)
XendDomainInfo.initDomain: exception occurred
Traceback (most recent call last):
File "/usr/lib/xen-3.2-1/lib/python/xen/xend/XendDomainInfo.py",
line
1741, in _initDomain
channel_details = self.image.createImage()
File "/usr/lib/xen-3.2-1/lib/python/xen/xend/image.py", line 122, in
createImage
return self.createDomain()
File "/usr/lib/xen-3.2-1/lib/python/xen/xend/image.py", line 141, in
createDomain
result = self.buildDomain()
File "/usr/lib/xen-3.2-1/lib/python/xen/xend/image.py", line 613, in
buildDomain
return LinuxImageHandler.buildDomain(self)
File "/usr/lib/xen-3.2-1/lib/python/xen/xend/image.py", line 372, in
buildDomain
vhpt = self.vhpt)
Error: (2, ''Invalid kernel'', ''xc_dom_find_loader: no
loader found\n'')
[2010-09-27 05:06:29 4409] ERROR (__init__:1072) VM start failed
Traceback (most recent call last):
File "/usr/lib/xen-3.2-1/lib/python/xen/xend/XendDomainInfo.py",
line
420, in start
XendTask.log_progress(31, 60, self._initDomain)
File "/usr/lib/xen-3.2-1/lib/python/xen/xend/XendTask.py", line 209,
in log_progress
retval = func(*args, **kwds)
File "/usr/lib/xen-3.2-1/lib/python/xen/xend/XendDomainInfo.py",
line
1769, in _initDomain
raise VmError(str(exn))
VmError: (2, ''Invalid kernel'', ''xc_dom_find_loader:
no loader found\n'')
[2010-09-27 05:06:29 4409] DEBUG (__init__:1072) XendDomainInfo.destroy:
domid=9
[2010-09-27 05:06:29 4409] DEBUG (__init__:1072)
XendDomainInfo.destroyDomain(9)
[2010-09-27 05:06:29 4409] DEBUG (__init__:1072) Destroying device model
[2010-09-27 05:06:29 4409] DEBUG (__init__:1072) Releasing devices
[2010-09-27 05:06:29 4409] ERROR (__init__:1072) Domain construction failed
Traceback (most recent call last):
File "/usr/lib/xen-3.2-1/lib/python/xen/xend/XendDomainInfo.py",
line
87, in create
vm.start()
File "/usr/lib/xen-3.2-1/lib/python/xen/xend/XendDomainInfo.py",
line
420, in start
XendTask.log_progress(31, 60, self._initDomain)
File "/usr/lib/xen-3.2-1/lib/python/xen/xend/XendTask.py", line 209,
in log_progress
retval = func(*args, **kwds)
File "/usr/lib/xen-3.2-1/lib/python/xen/xend/XendDomainInfo.py",
line
1769, in _initDomain
raise VmError(str(exn))
VmError: (2, ''Invalid kernel'', ''xc_dom_find_loader:
no loader found\n'')
[2010-09-27 05:06:29 4409] DEBUG (__init__:1072) XendDomainInfo.destroy:
domid=None
[2010-09-27 05:06:29 4409] DEBUG (__init__:1072)
XendDomainInfo.destroyDomain(None)
[2010-09-27 05:06:29 4409] DEBUG (__init__:1072) No device model
[2010-09-27 05:06:29 4409] DEBUG (__init__:1072) Releasing devices
The image and ramdisk files as referred to by xend (boot_kernel.0BCcGq
and boot_ramdisk.hQst77) do exist and match the corresponding files from
domU.
cheers,
Jan
On 27/09/10 17:48, Jan Bakuwel wrote:> Hi,
>
> I''ve prepared a Ubuntu 10.04 LTS server on a Xen 3.2-1 host
running
> Debian Lenny on kernel 2.6.26-2-xen-amd64. The Ubuntu 10.04 domU is
> running a 2.6.32-24-server kernel from the Ubuntu repositories, which is
> (must be :-) ) xen-aware. The domU uses pygrub to boot and it works like
> a charm.
>
> Now I''m trying to deploy this domU on a Xen 3.2-1 host running
Debian
> Etch on kernel 2.6.18-6-xen-amd64. When I xm create domU on this system,
> I see the pygrub boot menu but then an error message comes up:
>
> Error: (2, ''Invalid kernel'',
''xc_dom_find_loader: no loader found\n'')
>
> When I use pygrub directly (ie. rather than xm create), I get this message:
>
> # pygrub /dev/d/xm.dt2
> linux (kernel /var/run/xend/boot/boot_kernel.0BCcGq)(ramdisk
> /var/run/xend/boot/boot_ramdisk.hQst77)(args "root=/dev/xvda1
ro")
>
> Any suggestions for how to further diagnose this?
>
> kind regards,
> Jan
>
>
>
>
> _______________________________________________
> Xen-users mailing list
> Xen-users@lists.xensource.com
> http://lists.xensource.com/xen-users
>
>
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
On Mon, Sep 27, 2010 at 12:32 PM, Jan Bakuwel <jan.bakuwel@gmail.com> wrote:> Hi, > > A bit more info on this: > > Full extract from /var/log/xen/xend.log for this domU session: >> [2010-09-27 05:06:22 8161] DEBUG (__init__:1072) Launching bootloader as > [''/usr/bin/pygrub'', ''--args=root=/dev/xvda1 ro '', > ''--output=/var/run/xend/boot/xenbl.10154'', ''/dev/d/xm.dt2'']. >Error: (2, ''Invalid kernel'', ''xc_dom_find_loader: no loader found\n'')>> > I''ve prepared a Ubuntu 10.04 LTS server on a Xen 3.2-1 host running > > Debian Lenny on kernel 2.6.26-2-xen-amd64. The Ubuntu 10.04 domU is > > running a 2.6.32-24-server kernel from the Ubuntu repositories, which is > > (must be :-) ) xen-aware. The domU uses pygrub to boot and it works like > > a charm. > > > > Now I''m trying to deploy this domU on a Xen 3.2-1 host running Debian > > Etch on kernel 2.6.18-6-xen-amd64. When I xm create domU on this system, > > I see the pygrub boot menu but then an error message comes up: > > > > Error: (2, ''Invalid kernel'', ''xc_dom_find_loader: no loader found\n'') >Are you sure that both the hypervisor and userland are the same version (3.2) in both Etch and Lenny? Ubuntu''s default kernel is newer pv_ops kernel, which might not be identified correctly as xen-compatible by old xen userland tools. Try copying the kernel and initrd to dom0, and boot it (i.e. not using "bootloader", but "kernel", "ramdisk", and "extra"). My guess is it will show the same message. -- Fajar _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Hi Fajar,> Are you sure that both the hypervisor and userland are the same > version (3.2) in both Etch and Lenny?They are not exactly the same but hopefully sufficiently the same: Lenny: # dpkg --list | grep xen ii libxenstore3.0 3.2.1-2 Xenstore communications library for Xen ii linux-image-2.6.26-2-xen-amd64 2.6.26-19 Linux 2.6.26 image on AMD64, oldstyle Xen support ii linux-modules-2.6.26-2-xen-amd64 2.6.26-19 Linux 2.6.26 modules on AMD64 ii xen-hypervisor-3.2-1-amd64 3.2.1-2 The Xen Hypervisor on AMD64 ii xen-tools 3.9-4 Tools to manage Debian XEN virtual servers ii xen-utils-3.2-1 3.2.1-2 XEN administrative tools ii xen-utils-common 3.2.0-2 XEN administrative tools - common files ii xenstore-utils 3.2.1-2 Xenstore utilities for Xen Etch: # dpkg --list | grep xen ii libxenstore3.0 3.2.0-3~bpo4+2 Xenstore communications library for Xen ii linux-image-2.6-xen-amd64 2.6.18+6etch3 Linux kernel 2.6 image on AMD64 ii linux-image-2.6.18-6-xen-amd64 2.6.18.dfsg.1-22etch3 Linux 2.6.18 image on AMD64 ii linux-modules-2.6.18-6-xen-amd64 2.6.18.dfsg.1-22etch3 Linux 2.6.18 modules on AMD64 ii xen-docs-3.2 3.2.0-3~bpo4+2 Documentation for Xen ii xen-hypervisor-3.2-1-amd64 3.2.0-3~bpo4+2 The Xen Hypervisor on AMD64 ii xen-shell 1.8-3~bpo40+1 Console based Xen administration utility ii xen-tools 3.9-4~bpo40+1 Tools to manage Debian XEN virtual servers ii xen-utils-3.2-1 3.2.0-3~bpo4+2 XEN administrative tools ii xen-utils-common 3.2.0-1~bpo4+1 XEN administrative tools - common files ii xenman 0.6-5~bpo40+2 A graphical Xen management tool ii xenstore-utils 3.2.0-3~bpo4+2 Xenstore utilities for Xen> > Ubuntu''s default kernel is newer pv_ops kernel, which might not be > identified correctly as xen-compatible by old xen userland tools.The next question is: how can I convince the slightly old(er) xen userland tools that we''re dealing with a proper xen-compatible kernel for domU here.> Try copying the kernel and initrd to dom0, and boot it (i.e. not using > "bootloader", but "kernel", "ramdisk", and "extra"). My guess is it > will show the same message.You''re right... Jan _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On Mon, Sep 27, 2010 at 5:04 PM, Jan Bakuwel <jan.bakuwel@gmail.com> wrote:> Etch: > >ii xen-utils-3.2-1> 3.2.0-3~bpo4+2 XEN administrative tools >The next question is: how can I convince the slightly old(er) xen> userland tools that we''re dealing with a proper xen-compatible kernel > for domU here. > >I don''t know of a way other than upgrading your xen version (possibly by compiling from source) You might want to upgrade to 3.4.3 (I suggest you avoid 4.0.x for now, unless you''re testing new features/dom0 kernel) -- Fajar _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Hi Fajar, On 27/09/10 23:29, Fajar A. Nugraha wrote:> On Mon, Sep 27, 2010 at 5:04 PM, Jan Bakuwel <jan.bakuwel@gmail.com > <mailto:jan.bakuwel@gmail.com>> wrote: > > Etch: > > > ii xen-utils-3.2-1 > 3.2.0-3~bpo4+2 XEN administrative tools > > > The next question is: how can I convince the slightly old(er) xen > userland tools that we''re dealing with a proper xen-compatible kernel > for domU here. > > > I don''t know of a way other than upgrading your xen version (possibly > by compiling from source) > You might want to upgrade to 3.4.3 (I suggest you avoid 4.0.x for now, > unless you''re testing new features/dom0 kernel)Upgrading dom0 on that system is a lot of work (various reasons). Both systems seem to use Xen 3.2-1 although the Etch versions are also "3.2.0". Do you think the (very slight) difference in userland tools might be causing domU not to boot on Etch but working fine on Lenny or would the 2.6.18-6-xen kernel on Etch vs the 2.6.26-2-xen kernel on Lenny more likely be the problem? I really hope I can avoid having to upgrade dom0 (apart from patching the userland tools). thanks, Jan _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
As far as i can remember, for pv_ops guests(i.e. Ubuntu) you need to be running Xen 3.3 or above. On 27 September 2010 20:59, Jan Bakuwel <jan.bakuwel@gmail.com> wrote:> Hi Fajar, > > > On 27/09/10 23:29, Fajar A. Nugraha wrote: > > On Mon, Sep 27, 2010 at 5:04 PM, Jan Bakuwel <jan.bakuwel@gmail.com > > <mailto:jan.bakuwel@gmail.com>> wrote: > > > > Etch: > > > > > > ii xen-utils-3.2-1 > > 3.2.0-3~bpo4+2 XEN administrative tools > > > > > > The next question is: how can I convince the slightly old(er) xen > > userland tools that we''re dealing with a proper xen-compatible kernel > > for domU here. > > > > > > I don''t know of a way other than upgrading your xen version (possibly > > by compiling from source) > > You might want to upgrade to 3.4.3 (I suggest you avoid 4.0.x for now, > > unless you''re testing new features/dom0 kernel) > > Upgrading dom0 on that system is a lot of work (various reasons). > > Both systems seem to use Xen 3.2-1 although the Etch versions are also > "3.2.0". > > Do you think the (very slight) difference in userland tools might be > causing domU not to boot on Etch but working fine on Lenny or would the > 2.6.18-6-xen kernel on Etch vs the 2.6.26-2-xen kernel on Lenny more > likely be the problem? > > I really hope I can avoid having to upgrade dom0 (apart from patching > the userland tools). > > thanks, > Jan > > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-users >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Hi David, On 28/09/10 09:42, David Markey wrote:> As far as i can remember, for pv_ops guests(i.e. Ubuntu) you need to > be running Xen 3.3 or above.Ubuntu 10.04 LTS guest (64bit) runs beautifully on a Debian Lenny 2.6.26-2-xen-amd64 kernel with Xen 3.2-1, see previous posts, so I am hoping I can get it to run too on Debian Etch 2.6.18-6-xen-amd64 with Xen 3.2-1. I''m now comparing the two userlands to see how far I can get. Any further insight/help much appreciated. kind regards, Jan _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Hi Fajar, On 27/09/10 23:29, Fajar A. Nugraha wrote:> > I don''t know of a way other than upgrading your xen version (possibly > by compiling from source) > You might want to upgrade to 3.4.3 (I suggest you avoid 4.0.x for now, > unless you''re testing new features/dom0 kernel)Thought I should let you know that I''ve got Ubuntu 10.04 LTS running nicely on Debian Etch with a 2.6.18-6-xen-amd64 kernel. It was a matter of upgrading Xen from 3.2-0 to 3.2-1 (apparently there was a small update after Xen got installed initially). thanks again for your help, Jan _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users