Re: [Fedora-xen] Fedora 12 x86_64, Xen 4.0.1-6 and Fedora 16 domU
On Tue, 24 Jan 2012, Roberto Fichera wrote: My thought is that since Fedora 16 comes with grub2, my current xen setup doesn't support it. It doesn't. The most recent F16 xen (4.1.1-8 or later) should though (the patches for Fedora style grub2 support are upstream in the 4.1 and unstable development trees but not in any released version yet). You could try 1) turning selinux off (setenforce 0) if it is on. 2) Running pygrub directly to see if it works or gives useful debugging ie. pygrub Note if you are using pvgrub as your boot loader then it is unlikely to cope with F16 guests. Another possibility is that your upgrade didn't generate a valid grub2 configuration, so there is nothing for the boot loader to find. Michael Young -- xen mailing list xen@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/xen
Re: [Fedora-xen] Fedora 12 x86_64, Xen 4.0.1-6 and Fedora 16 domU
Il 24/01/2012 20.31, Konrad Rzeszutek Wilk ha scritto:
> On Tue, Jan 24, 2012 at 08:24:28PM +0100, Roberto Fichera wrote:
>> Hi All,
>>
>> I just update one of my Fedora 14 domU to Fedora 16 and everything when ok
>> in the update process. But once I did the first domU reboot than I got the
>>
>> Error: Boot loader didn't return any data!
>>
>> while virt-manager reports:
>>
>> Error starting domain: POST operation failed: xend_post: error from xen
>> daemon: (xend.err "Boot loader didn't return any
>> data!")
>>
>> details reports:
>>
>> raceback (most recent call last):
>> File "/usr/share/virt-manager/virtManager/engine.py", line 589, in
>> run_domain
>> vm.startup()
>> File "/usr/share/virt-manager/virtManager/domain.py", line 150, in startup
>> self._backend.create()
>> File "/usr/lib64/python2.6/site-packages/libvirt.py", line 333, in create
>> if ret == -1: raise libvirtError ('virDomainCreate() failed', dom=self)
>> libvirtError: POST operation failed: xend_post: error from xen daemon:
>> (xend.err "Boot loader didn't return any data!")
>>
>> My thought is that since Fedora 16 comes with grub2, my current xen setup
>> doesn't support it.
> And what is "current xen setup"? What version of Xen toolstack do you have?
Distribution is a plain F12 and the Xen stack is:
Kernel 2.6.32.39-175.xendom0.fc13.x86_64
xen-4.0.1-6.fc12.src.rpm
virt-manager-0.8.2-3.fc12.src.rpm
>> I also did a backport of xen4.2.1 from F16, recompiling it from src.rpm but
>> anything was really working.
> Huh? So did it work or not? What version of src.rpm? xen-4.1.2-2 or later?
No! It wasn't working! I rebuilded under F12 the
xen-4.1.2-2.fc16.src.rpm from the last F16 updates.
>> Does anyone can suggest something to solve this problem.
> I am pretty sure this is solved - if you look in the Fedora bugzilla there is
> a BZ
> for this and it has been fixed.
Yes! I read it! But I don't know if the xen-4.1.2-2 from F16 can work
against the kernel I have. Otherwise
feel free to suggest me any other combination that might work with my
current situation.
>
>> Thanks in advance.
>> Roberto Fichera.
>> --
>> xen mailing list
>> xen@lists.fedoraproject.org
>> https://admin.fedoraproject.org/mailman/listinfo/xen
--
xen mailing list
xen@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/xen
Re: [Fedora-xen] Fedora 12 x86_64, Xen 4.0.1-6 and Fedora 16 domU
On Tue, Jan 24, 2012 at 08:24:28PM +0100, Roberto Fichera wrote:
> Hi All,
>
> I just update one of my Fedora 14 domU to Fedora 16 and everything when ok
> in the update process. But once I did the first domU reboot than I got the
>
> Error: Boot loader didn't return any data!
>
> while virt-manager reports:
>
> Error starting domain: POST operation failed: xend_post: error from xen
> daemon: (xend.err "Boot loader didn't return any
> data!")
>
> details reports:
>
> raceback (most recent call last):
> File "/usr/share/virt-manager/virtManager/engine.py", line 589, in
> run_domain
> vm.startup()
> File "/usr/share/virt-manager/virtManager/domain.py", line 150, in startup
> self._backend.create()
> File "/usr/lib64/python2.6/site-packages/libvirt.py", line 333, in create
> if ret == -1: raise libvirtError ('virDomainCreate() failed', dom=self)
> libvirtError: POST operation failed: xend_post: error from xen daemon:
> (xend.err "Boot loader didn't return any data!")
>
> My thought is that since Fedora 16 comes with grub2, my current xen setup
> doesn't support it.
And what is "current xen setup"? What version of Xen toolstack do you have?
>
> I also did a backport of xen4.2.1 from F16, recompiling it from src.rpm but
> anything was really working.
Huh? So did it work or not? What version of src.rpm? xen-4.1.2-2 or later?
>
> Does anyone can suggest something to solve this problem.
I am pretty sure this is solved - if you look in the Fedora bugzilla there is a
BZ
for this and it has been fixed.
>
> Thanks in advance.
> Roberto Fichera.
> --
> xen mailing list
> xen@lists.fedoraproject.org
> https://admin.fedoraproject.org/mailman/listinfo/xen
--
xen mailing list
xen@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/xen
[Fedora-xen] Fedora 12 x86_64, Xen 4.0.1-6 and Fedora 16 domU
Hi All,
I just update one of my Fedora 14 domU to Fedora 16 and everything when ok
in the update process. But once I did the first domU reboot than I got the
Error: Boot loader didn't return any data!
while virt-manager reports:
Error starting domain: POST operation failed: xend_post: error from xen daemon:
(xend.err "Boot loader didn't return any
data!")
details reports:
raceback (most recent call last):
File "/usr/share/virt-manager/virtManager/engine.py", line 589, in run_domain
vm.startup()
File "/usr/share/virt-manager/virtManager/domain.py", line 150, in startup
self._backend.create()
File "/usr/lib64/python2.6/site-packages/libvirt.py", line 333, in create
if ret == -1: raise libvirtError ('virDomainCreate() failed', dom=self)
libvirtError: POST operation failed: xend_post: error from xen daemon:
(xend.err "Boot loader didn't return any data!")
My thought is that since Fedora 16 comes with grub2, my current xen setup
doesn't support it.
I also did a backport of xen4.2.1 from F16, recompiling it from src.rpm but
anything was really working.
Does anyone can suggest something to solve this problem.
Thanks in advance.
Roberto Fichera.
--
xen mailing list
xen@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/xen
