2:59 p.m.
Hi, I'm having trouble installing a fedora f20 guest on a centos5
host, I previously had a working f16 guest, so I guess I want to
know if this is possible or not.
virt-install seems to work ok as before, but then the reboot fails
with this error:
Error starting domain: POST operation failed: xend_post: error from
xen daemon: (xend.err "Error creating domain: Boot loader didn't
return any data!")
I've tried formatting /boot as ext2 and ext3 with the same result,
now I'm out of ideas. Here is my virt-install command:
virt-install --paravirt --name honk --ram 2048 --disk \
path=/dev/VolGroup02/LogVol12 --vnc --location \
http://dl.fedoraproject.org/pub/fedora/linux/releases/20/Fedora/x86_64/os/
--
Bruno
8:12 a.m.
On 01/20/2014 03:59 PM, Bruno Postle wrote:
Hi, I'm having trouble installing a fedora f20 guest on a centos5
host, I
previously had a working f16 guest, so I guess I want to know if this is
possible or not.
virt-install seems to work ok as before, but then the reboot fails with this
error:
Error starting domain: POST operation failed: xend_post: error from xen
daemon: (xend.err "Error creating domain: Boot loader didn't return any
data!")
I've tried formatting /boot as ext2 and ext3 with the same result, now I'm out
of ideas. Here is my virt-install command:
virt-install --paravirt --name honk --ram 2048 --disk \
path=/dev/VolGroup02/LogVol12 --vnc --location \
http://dl.fedoraproject.org/pub/fedora/linux/releases/20/Fedora/x86_64/os/
F20 as a paravirt guest should work, but I think nowadays most people are
using fullvirt xen, so maybe paravirt isn't tested as much with new distros.
I'm just guessing though
Regardless, you'll probably have to dig in xen logs to or do some googling to
find more info: I don't have any idea. It's very unlikely to be a
virt-install/libvirt issue though
- Cole
8:14 a.m.
On 01/21/2014 09:12 AM, Cole Robinson wrote:
On 01/20/2014 03:59 PM, Bruno Postle wrote:
> Hi, I'm having trouble installing a fedora f20 guest on a centos5 host, I
> previously had a working f16 guest, so I guess I want to know if this is
> possible or not.
>
> virt-install seems to work ok as before, but then the reboot fails with this
> error:
>
> Error starting domain: POST operation failed: xend_post: error from xen
> daemon: (xend.err "Error creating domain: Boot loader didn't return any
data!")
>
> I've tried formatting /boot as ext2 and ext3 with the same result, now I'm
out
> of ideas. Here is my virt-install command:
>
> virt-install --paravirt --name honk --ram 2048 --disk \
> path=/dev/VolGroup02/LogVol12 --vnc --location \
> http://dl.fedoraproject.org/pub/fedora/linux/releases/20/Fedora/x86_64/os/
>
F20 as a paravirt guest should work, but I think nowadays most people are
using fullvirt xen, so maybe paravirt isn't tested as much with new distros.
I'm just guessing though
Regardless, you'll probably have to dig in xen logs to or do some googling to
find more info: I don't have any idea. It's very unlikely to be a
virt-install/libvirt issue though
Sorry, I thought this email went to the upstream virt-manager list, hence I
was focusing on that :)
RHEL5 xen is an old frankenstein monster at this point as well, so could be a
xen issue that just hasn't been backported.
CCing fedora xen list as well, maybe they have ideas.
- Cole
2:46 p.m.
New subject: [Fedora-xen] f20 guest on centos5 xen host
On Tue, 21 Jan 2014, Cole Robinson wrote:
On 01/21/2014 09:12 AM, Cole Robinson wrote:
> On 01/20/2014 03:59 PM, Bruno Postle wrote:
>> Hi, I'm having trouble installing a fedora f20 guest on a centos5 host, I
>> previously had a working f16 guest, so I guess I want to know if this is
>> possible or not.
>>
>> virt-install seems to work ok as before, but then the reboot fails with this
>> error:
>>
>> Error starting domain: POST operation failed: xend_post: error from xen
>> daemon: (xend.err "Error creating domain: Boot loader didn't return
any data!")
>>
>> I've tried formatting /boot as ext2 and ext3 with the same result, now
I'm out
>> of ideas. Here is my virt-install command:
>>
>> virt-install --paravirt --name honk --ram 2048 --disk \
>> path=/dev/VolGroup02/LogVol12 --vnc --location \
>> http://dl.fedoraproject.org/pub/fedora/linux/releases/20/Fedora/x86_64/os/
>>
>
> F20 as a paravirt guest should work, but I think nowadays most people are
> using fullvirt xen, so maybe paravirt isn't tested as much with new distros.
> I'm just guessing though
>
> Regardless, you'll probably have to dig in xen logs to or do some googling to
> find more info: I don't have any idea. It's very unlikely to be a
> virt-install/libvirt issue though
>
Sorry, I thought this email went to the upstream virt-manager list, hence I
was focusing on that :)
RHEL5 xen is an old frankenstein monster at this point as well, so could be a
xen issue that just hasn't been backported.
CCing fedora xen list as well, maybe they have ideas.
I would need to see more logs to be sure, but I would guess pygrub is
missing at least one update and this one
http://xenbits.xenproject.org/gitweb/?p=xen.git;a=commit;h=d513814db6af2b...
is a possibility. You could test if it is pygrub by running directly - in
your case try
/usr/bin/pygrub /dev/VolGroup02/LogVol12
as root - it should give you a choice of kernels and return the details
for the one you pick.
Michael Young
3:57 p.m.
On Tue 21-Jan-2014 at 19:59 +0000, Bruno Postle wrote:
File
"/usr/lib64/python2.4/site-packages/grub/GrubConf.py", line 233, in
_set_default
self._default = int(val)
ValueError: invalid literal for int(): ${next_entry}
It looks like the centos5 version of pygrub doesn't like this sort of
syntax in the f20 grub.cfg file:
set default="${next_entry}"
This is it, I changed the 'int(val)' to '0' in
/usr/lib64/python2.4/site-packages/grub/GrubConf.py and the f20
guest came up after installation.
Though it now fails to come back up after yum update and reboot:
[2014-01-21 21:42:50 xend.XendDomainInfo 3625] WARNING (XendDomainInfo:1262) Domain has
crashed: name=honk id=28.
[2014-01-21 21:42:50 xend.XendDomainInfo 3625] ERROR (XendDomainInfo:2864) VM honk
restarting too fast (Elapsed time: 1.151586 seconds). Refusing to restart to avoid loops.
--
Bruno
4:35 p.m.
On Tue 21-Jan-2014 at 21:57 +0000, Bruno Postle wrote:
Though it now fails to come back up after yum update and reboot:
[2014-01-21 21:42:50 xend.XendDomainInfo 3625] WARNING (XendDomainInfo:1262) Domain has
crashed: name=honk id=28.
[2014-01-21 21:42:50 xend.XendDomainInfo 3625] ERROR (XendDomainInfo:2864) VM honk
restarting too fast (Elapsed time: 1.151586 seconds). Refusing to restart to avoid loops.
I have some more info on this second problem, the first problem is
clearly the same as described in this patch/workaround:
http://xenbits.xenproject.org/gitweb/?p=xen.git;a=commit;h=d513814db6af2b...
Now the system will come back up on reboot, but not if I upgrade the
kernel on the guest (I can upgrade everything else).
Any ideas? it is either that there is some new incompatibility
between kernel 3.11.10 and 3.12.8 on f20, or pygrub on centos5 can't
cope with two kernel entries.
--
Bruno
2:51 a.m.
On Wed 22-Jan-2014 at 22:35 +0000, Bruno Postle wrote:
On Tue 21-Jan-2014 at 21:57 +0000, Bruno Postle wrote:
>
>Though it now fails to come back up after yum update and reboot:
>
> [2014-01-21 21:42:50 xend.XendDomainInfo 3625] WARNING (XendDomainInfo:1262) Domain
has crashed: name=honk id=28.
> [2014-01-21 21:42:50 xend.XendDomainInfo 3625] ERROR (XendDomainInfo:2864) VM honk
restarting too fast (Elapsed time: 1.151586 seconds). Refusing to restart to avoid loops.
I have some more info on this second problem, the first problem is
clearly the same as described in this patch/workaround:
http://xenbits.xenproject.org/gitweb/?p=xen.git;a=commit;h=d513814db6af2b...
Now the system will come back up on reboot, but not if I upgrade the
kernel on the guest (I can upgrade everything else).
Any ideas? it is either that there is some new incompatibility
between kernel 3.11.10 and 3.12.8 on f20, or pygrub on centos5 can't
cope with two kernel entries.
Further info, I did the obvious test here: I installed this new f20
kernel and removed the old f20 kernel entry from the grub.cfg file.
The guest crashes, so I suppose the f20 3.12.8 kernel is
incompatible with centos5 xen.
--
Bruno
6:33 a.m.
On Fri, Jan 24, 2014 at 08:51:46AM +0000, Bruno Postle wrote:
On Wed 22-Jan-2014 at 22:35 +0000, Bruno Postle wrote:
>On Tue 21-Jan-2014 at 21:57 +0000, Bruno Postle wrote:
>>
>>Though it now fails to come back up after yum update and reboot:
>>
>>[2014-01-21 21:42:50 xend.XendDomainInfo 3625] WARNING (XendDomainInfo:1262)
Domain has crashed: name=honk id=28.
>>[2014-01-21 21:42:50 xend.XendDomainInfo 3625] ERROR (XendDomainInfo:2864) VM
honk restarting too fast (Elapsed time: 1.151586 seconds). Refusing to restart to avoid
loops.
>
>I have some more info on this second problem, the first problem is
>clearly the same as described in this patch/workaround:
http://xenbits.xenproject.org/gitweb/?p=xen.git;a=commit;h=d513814db6af2b...
>
>Now the system will come back up on reboot, but not if I upgrade
>the kernel on the guest (I can upgrade everything else).
>
>Any ideas? it is either that there is some new incompatibility
>between kernel 3.11.10 and 3.12.8 on f20, or pygrub on centos5
>can't cope with two kernel entries.
Further info, I did the obvious test here: I installed this new f20
kernel and removed the old f20 kernel entry from the grub.cfg file.
The guest crashes, so I suppose the f20 3.12.8 kernel is
incompatible with centos5 xen.
Can you please paste the full domU kernel verbose debug output,
so we can see what goes wrong?
-- Pasi
3:57 p.m.
On Mon 17-Feb-2014 at 14:33 +0200, Pasi Kärkkäinen wrote:
On Fri, Jan 24, 2014 at 08:51:46AM +0000, Bruno Postle wrote:
> >>Though it now fails to come back up after yum update and reboot:
> >>
> >>[2014-01-21 21:42:50 xend.XendDomainInfo 3625] WARNING (XendDomainInfo:1262)
Domain has crashed: name=honk id=28.
> >>[2014-01-21 21:42:50 xend.XendDomainInfo 3625] ERROR (XendDomainInfo:2864) VM
honk restarting too fast (Elapsed time: 1.151586 seconds). Refusing to restart to avoid
loops.
> Further info, I did the obvious test here: I installed this new
f20
> kernel and removed the old f20 kernel entry from the grub.cfg file.
> The guest crashes, so I suppose the f20 3.12.8 kernel is
> incompatible with centos5 xen.
Can you please paste the full domU kernel verbose debug output,
so we can see what goes wrong?
Thanks, but I some some help here. I'm starting the guest in
virt-manager but nothing appears in the console, how can I capture
the kernel output?
--
Bruno
4:02 p.m.
New subject: [Fedora-xen] f20 guest on centos5 xen host
On Tue 21-Jan-2014 at 20:46 +0000, M A Young wrote:
I would need to see more logs to be sure, but I would guess pygrub is
missing at least one update and this one
http://xenbits.xenproject.org/gitweb/?p=xen.git;a=commit;h=d513814db6af2b...
is a possibility. You could test if it is pygrub by running directly
- in your case try
/usr/bin/pygrub /dev/VolGroup02/LogVol12
as root - it should give you a choice of kernels and return the
details for the one you pick.
Thanks, this now works as expected (with the patch applied). This
is the resulting kernel line:
linux (kernel /var/lib/xen/boot_kernel.bfKeqy)(ramdisk
/var/lib/xen/boot_ramdisk.GwQf8f)(args
"root=UUID=75e83bc3-5536-4f49-9578-110455c6bcdb ro console=hvc0
vconsole.font=latarcyrheb-sun16 LANG=en_GB.UTF-8")
(though the guest still crashes on reboot as described in my last
email)
--
Bruno
3:35 p.m.
New subject: [Fedora-xen] f20 guest on centos5 xen host
On Tue, Jan 21, 2014 at 09:14:15AM -0500, Cole Robinson wrote:
On 01/21/2014 09:12 AM, Cole Robinson wrote:
> On 01/20/2014 03:59 PM, Bruno Postle wrote:
>> Hi, I'm having trouble installing a fedora f20 guest on a centos5 host, I
>> previously had a working f16 guest, so I guess I want to know if this is
>> possible or not.
>>
>> virt-install seems to work ok as before, but then the reboot fails with this
>> error:
>>
>> Error starting domain: POST operation failed: xend_post: error from xen
>> daemon: (xend.err "Error creating domain: Boot loader didn't return
any data!")
>>
>> I've tried formatting /boot as ext2 and ext3 with the same result, now
I'm out
>> of ideas. Here is my virt-install command:
>>
>> virt-install --paravirt --name honk --ram 2048 --disk \
>> path=/dev/VolGroup02/LogVol12 --vnc --location \
>> http://dl.fedoraproject.org/pub/fedora/linux/releases/20/Fedora/x86_64/os/
It might be this one:
https://bugzilla.redhat.com/show_bug.cgi?id=1039171
CC-ing Jim on it
It was a bit hard to find it - but basically you had to use --network
parameter and if you used a bridge - then it had to be called 'xenbr0'.
>>
>
> F20 as a paravirt guest should work, but I think nowadays most people are
> using fullvirt xen, so maybe paravirt isn't tested as much with new distros.
> I'm just guessing though
>
> Regardless, you'll probably have to dig in xen logs to or do some googling to
> find more info: I don't have any idea. It's very unlikely to be a
> virt-install/libvirt issue though
>
Sorry, I thought this email went to the upstream virt-manager list, hence I
was focusing on that :)
RHEL5 xen is an old frankenstein monster at this point as well, so could be a
xen issue that just hasn't been backported.
CCing fedora xen list as well, maybe they have ideas.
- Cole
--
xen mailing list
xen(a)lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/xen
1:59 p.m.
On Tue 21-Jan-2014 at 09:12 -0500, Cole Robinson wrote:
On 01/20/2014 03:59 PM, Bruno Postle wrote:
> Hi, I'm having trouble installing a fedora f20 guest on a centos5
> host, I previously had a working f16 guest, so I guess I want to
> know if this is possible or not.
>
> virt-install seems to work ok as before, but then the reboot
> fails with this error:
>
> Error starting domain: POST operation failed: xend_post: error
> from xen daemon: (xend.err "Error creating domain: Boot loader
> didn't return any data!")
>
> I've tried formatting /boot as ext2 and ext3 with the same
> result, now I'm out of ideas. Here is my virt-install command:
>
> virt-install --paravirt --name honk --ram 2048 --disk \
> path=/dev/VolGroup02/LogVol12 --vnc --location \
> http://dl.fedoraproject.org/pub/fedora/linux/releases/20/Fedora/x86_64/os/
F20 as a paravirt guest should work, but I think nowadays most
people are using fullvirt xen, so maybe paravirt isn't tested as
much with new distros. I'm just guessing though
Thanks, I tried with --hvm instead of --paravirt, but this fails:
ERROR Host does not support virtualization type 'hvm
Regardless, you'll probably have to dig in xen logs to or do some
googling to find more info: I don't have any idea. It's very
unlikely to be a virt-install/libvirt issue though
Ah, there is more in xend-debug.log:
Using <class 'grub.GrubConf.Grub2ConfigFile'> to parse /grub2/grub.cfg
Traceback (most recent call last):
File "/usr/bin/pygrub", line 758, in ?
chosencfg = run_grub(file, entry, fs)
File "/usr/bin/pygrub", line 581, in run_grub
g = Grub(file, fs)
File "/usr/bin/pygrub", line 223, in __init__
self.read_config(file, fs)
File "/usr/bin/pygrub", line 443, in read_config
self.cf.parse(buf)
File "/usr/lib64/python2.4/site-packages/grub/GrubConf.py", line 430, in
parse
setattr(self, self.commands[com], arg.strip())
File "/usr/lib64/python2.4/site-packages/grub/GrubConf.py", line 233, in
_set_default
self._default = int(val)
ValueError: invalid literal for int(): ${next_entry}
Traceback (most recent call last):
File "/usr/lib64/python2.4/site-packages/xen/xend/server/SrvDomainDir.py",
line 77, in op_create
dominfo = self.xd.domain_create(config)
File "/usr/lib64/python2.4/site-packages/xen/xend/XendDomain.py", line 245,
in domain_create
dominfo = XendDomainInfo.create(config)
File "/usr/lib64/python2.4/site-packages/xen/xend/XendDomainInfo.py", line
266, in create
vm.initDomain()
File "/usr/lib64/python2.4/site-packages/xen/xend/XendDomainInfo.py", line
2155, in initDomain
self.configure_bootloader()
File "/usr/lib64/python2.4/site-packages/xen/xend/XendDomainInfo.py", line
2965, in configure_bootloader
self.info['image'])
File "/usr/lib64/python2.4/site-packages/xen/xend/XendBootloader.py", line
97, in bootloader
raise VmError, msg
VmError: Boot loader didn't return any data!
It looks like the centos5 version of pygrub doesn't like this sort
of syntax in the f20 grub.cfg file:
set default="${next_entry}"
--
Bruno
3714
days inactive
3742
days old
11 comments
5 participants
participants (5)
-
Bruno Postle -
Cole Robinson -
Konrad Rzeszutek Wilk -
M A Young -
Pasi Kärkkäinen