Your message dated Sat, 31 Aug 2013 16:31:16 +0200
with message-id <[email protected]>
and subject line Re: Bug#721412: libvirt-bin: wrong path to xen pygrub in xml
config file, paravirtualized guest failed to start
has caused the Debian Bug report #721412,
regarding libvirt-bin: wrong path to xen pygrub in xml config file,
paravirtualized guest failed to start
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
721412: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=721412
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: libvirt-bin
Version: 0.9.12-11+deb7u1
Severity: normal
Dear Maintainer,
*** Please consider answering these questions, where appropriate ***
* What led up to the situation?
When i create a xen paravirtualized guest it failed to start with this error
:
Erreur lors du démarrage du domaine: POST operation failed: xend_post: error
from xen daemon: (xend.err "Bootloader isn't executable")
Traceback (most recent call last):
File "/usr/share/virt-manager/virtManager/asyncjob.py", line 45, in cb_wrapper
callback(asyncjob, *args, **kwargs)
File "/usr/share/virt-manager/virtManager/asyncjob.py", line 66, in tmpcb
callback(*args, **kwargs)
File "/usr/share/virt-manager/virtManager/domain.py", line 1114, in startup
self._backend.create()
File "/usr/lib/python2.7/dist-packages/libvirt.py", line 620, in create
if ret == -1: raise libvirtError ('virDomainCreate() failed', dom=self)
libvirtError: POST operation failed: xend_post: error from xen daemon:
(xend.err "Bootloader isn't executable")
I search on google and find this bug on opensuse mailing list :
http://lists.opensuse.org/opensuse-bugs/2013-01/msg00761.html
so i dump my xml config file :
virsh # dumpxml internet
<domain type='xen' id='17'>
<name>internet</name>
<uuid>3fff84b4-4a5c-bebc-7184-b12f00762e56</uuid>
<memory unit='KiB'>786432</memory>
<currentMemory unit='KiB'>786432</currentMemory>
<vcpu placement='static'>1</vcpu>
<bootloader>/usr/lib/xen-default/bin/pygrub</bootloader>
<os>
<type>linux</type>
</os>
<clock offset='utc' adjustment='reset'/>
<on_poweroff>destroy</on_poweroff>
<on_reboot>restart</on_reboot>
<on_crash>restart</on_crash>
<devices>
<emulator>/usr/lib/xen-4.1/bin/qemu-dm</emulator>
<disk type='block' device='disk'>
<driver name='phy'/>
<source dev='/dev/vg/Xen_internet'/>
<target dev='xvda' bus='xen'/>
</disk>
<interface type='bridge'>
<mac address='00:16:3e:56:4f:76'/>
<source bridge='xenbr0'/>
<script path='/etc/xen/scripts/vif-bridge'/>
<target dev='vif17.0'/>
</interface>
<console type='pty' tty='/dev/pts/2'>
<source path='/dev/pts/2'/>
<target type='xen' port='0'/>
</console>
<input type='mouse' bus='xen'/>
<graphics type='vnc' port='5900' autoport='yes' keymap='fr'/>
</devices>
</domain>
virsh #
i saw that the path to pygrub is wrong : /usr/lib/xen-default/bin/pygrub
instead of /usr/lib/xen-4.1/bin/pygrub
that causes the vm to not start.
As a more generic workaround i create a symlink like this :
ln -s /usr/lib/xen-4.1/ /usr/lib/xen-default
Now i can start paravirtualized guest successfuly :)
It would be great if it can be corrected. Thanks in advance ;)
* What exactly did you do (or not do) that was effective (or
ineffective)?
* What was the outcome of this action?
* What outcome did you expect instead?
*** End of the template - remove these lines ***
-- System Information:
Debian Release: 7.1
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 3.10.9-8-atom (SMP w/1 CPU core)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages libvirt-bin depends on:
ii adduser 3.113+nmu3
ii gettext-base 0.18.1.1-9
ii libavahi-client3 0.6.31-2
ii libavahi-common3 0.6.31-2
ii libblkid1 2.20.1-5.3
ii libc6 2.13-38
ii libcap-ng0 0.6.6-2
ii libdbus-1-3 1.6.8-1+deb7u1
ii libdevmapper1.02.1 2:1.02.74-7
ii libgcrypt11 1.5.0-5+deb7u1
ii libgnutls26 2.12.20-7
ii libnetcf1 0.1.9-2
ii libnl1 1.1-7
ii libnuma1 2.0.8~rc4-1
ii libparted0debian1 2.3-12
ii libpcap0.8 1.3.0-1
ii libpciaccess0 0.13.1-2
ii libreadline6 6.2+dfsg-0.1
ii libsasl2-2 2.1.25.dfsg1-6+deb7u1
ii libudev0 175-7.2
ii libvirt0 0.9.12-11+deb7u1
ii libxenstore3.0 4.1.4-3+deb7u1
ii libxml2 2.8.0+dfsg1-7+nmu1
ii libyajl2 2.0.4-2
ii logrotate 3.8.1-4
Versions of packages libvirt-bin recommends:
ii bridge-utils 1.5-6
ii dmidecode 2.11-9
ii dnsmasq-base 2.62-3+deb7u1
ii ebtables 2.0.10.4-1
ii gawk 1:4.0.1+dfsg-2.1
ii iproute 20120521-3+b3
ii iptables 1.4.14-3.1
ii libxml2-utils 2.8.0+dfsg1-7+nmu1
ii netcat-openbsd 1.105-7
ii parted 2.3-12
ii qemu-kvm 1.1.2+dfsg-6
Versions of packages libvirt-bin suggests:
pn policykit-1 <none>
ii radvd 1:1.8.5-1
-- no debconf information
--- End Message ---
--- Begin Message ---
Version: 0.600.1-3+deb7u1
On Sat, Aug 31, 2013 at 12:28:24PM +0200, Desgranges Arnaud wrote:
> Package: libvirt-bin
> Version: 0.9.12-11+deb7u1
> Severity: normal
>
> Dear Maintainer,
> *** Please consider answering these questions, where appropriate ***
>
> * What led up to the situation?
>
> When i create a xen paravirtualized guest it failed to start with this
> error :
> Erreur lors du démarrage du domaine: POST operation failed: xend_post: error
> from xen daemon: (xend.err "Bootloader isn't executable")
>
> Traceback (most recent call last):
> File "/usr/share/virt-manager/virtManager/asyncjob.py", line 45, in
> cb_wrapper
> callback(asyncjob, *args, **kwargs)
> File "/usr/share/virt-manager/virtManager/asyncjob.py", line 66, in tmpcb
> callback(*args, **kwargs)
> File "/usr/share/virt-manager/virtManager/domain.py", line 1114, in startup
> self._backend.create()
> File "/usr/lib/python2.7/dist-packages/libvirt.py", line 620, in create
> if ret == -1: raise libvirtError ('virDomainCreate() failed', dom=self)
> libvirtError: POST operation failed: xend_post: error from xen daemon:
> (xend.err "Bootloader isn't executable")
You didn't tell us _how_ you created the vm since that's where the
problem comes from. I assume it's done via virtinst and the bug
is fixed in the above version (currently in p-u) already.
Cheers,
-- Guido
>
> I search on google and find this bug on opensuse mailing list :
> http://lists.opensuse.org/opensuse-bugs/2013-01/msg00761.html
>
> so i dump my xml config file :
>
> virsh # dumpxml internet
> <domain type='xen' id='17'>
> <name>internet</name>
> <uuid>3fff84b4-4a5c-bebc-7184-b12f00762e56</uuid>
> <memory unit='KiB'>786432</memory>
> <currentMemory unit='KiB'>786432</currentMemory>
> <vcpu placement='static'>1</vcpu>
> <bootloader>/usr/lib/xen-default/bin/pygrub</bootloader>
> <os>
> <type>linux</type>
> </os>
> <clock offset='utc' adjustment='reset'/>
> <on_poweroff>destroy</on_poweroff>
> <on_reboot>restart</on_reboot>
> <on_crash>restart</on_crash>
> <devices>
> <emulator>/usr/lib/xen-4.1/bin/qemu-dm</emulator>
> <disk type='block' device='disk'>
> <driver name='phy'/>
> <source dev='/dev/vg/Xen_internet'/>
> <target dev='xvda' bus='xen'/>
> </disk>
> <interface type='bridge'>
> <mac address='00:16:3e:56:4f:76'/>
> <source bridge='xenbr0'/>
> <script path='/etc/xen/scripts/vif-bridge'/>
> <target dev='vif17.0'/>
> </interface>
> <console type='pty' tty='/dev/pts/2'>
> <source path='/dev/pts/2'/>
> <target type='xen' port='0'/>
> </console>
> <input type='mouse' bus='xen'/>
> <graphics type='vnc' port='5900' autoport='yes' keymap='fr'/>
> </devices>
> </domain>
>
> virsh #
>
> i saw that the path to pygrub is wrong : /usr/lib/xen-default/bin/pygrub
> instead of /usr/lib/xen-4.1/bin/pygrub
> that causes the vm to not start.
>
> As a more generic workaround i create a symlink like this :
>
> ln -s /usr/lib/xen-4.1/ /usr/lib/xen-default
>
> Now i can start paravirtualized guest successfuly :)
>
> It would be great if it can be corrected. Thanks in advance ;)
>
> * What exactly did you do (or not do) that was effective (or
> ineffective)?
> * What was the outcome of this action?
> * What outcome did you expect instead?
>
> *** End of the template - remove these lines ***
>
>
> -- System Information:
> Debian Release: 7.1
> APT prefers stable-updates
> APT policy: (500, 'stable-updates'), (500, 'stable')
> Architecture: amd64 (x86_64)
>
> Kernel: Linux 3.10.9-8-atom (SMP w/1 CPU core)
> Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)
> Shell: /bin/sh linked to /bin/dash
>
> Versions of packages libvirt-bin depends on:
> ii adduser 3.113+nmu3
> ii gettext-base 0.18.1.1-9
> ii libavahi-client3 0.6.31-2
> ii libavahi-common3 0.6.31-2
> ii libblkid1 2.20.1-5.3
> ii libc6 2.13-38
> ii libcap-ng0 0.6.6-2
> ii libdbus-1-3 1.6.8-1+deb7u1
> ii libdevmapper1.02.1 2:1.02.74-7
> ii libgcrypt11 1.5.0-5+deb7u1
> ii libgnutls26 2.12.20-7
> ii libnetcf1 0.1.9-2
> ii libnl1 1.1-7
> ii libnuma1 2.0.8~rc4-1
> ii libparted0debian1 2.3-12
> ii libpcap0.8 1.3.0-1
> ii libpciaccess0 0.13.1-2
> ii libreadline6 6.2+dfsg-0.1
> ii libsasl2-2 2.1.25.dfsg1-6+deb7u1
> ii libudev0 175-7.2
> ii libvirt0 0.9.12-11+deb7u1
> ii libxenstore3.0 4.1.4-3+deb7u1
> ii libxml2 2.8.0+dfsg1-7+nmu1
> ii libyajl2 2.0.4-2
> ii logrotate 3.8.1-4
>
> Versions of packages libvirt-bin recommends:
> ii bridge-utils 1.5-6
> ii dmidecode 2.11-9
> ii dnsmasq-base 2.62-3+deb7u1
> ii ebtables 2.0.10.4-1
> ii gawk 1:4.0.1+dfsg-2.1
> ii iproute 20120521-3+b3
> ii iptables 1.4.14-3.1
> ii libxml2-utils 2.8.0+dfsg1-7+nmu1
> ii netcat-openbsd 1.105-7
> ii parted 2.3-12
> ii qemu-kvm 1.1.2+dfsg-6
>
> Versions of packages libvirt-bin suggests:
> pn policykit-1 <none>
> ii radvd 1:1.8.5-1
>
> -- no debconf information
--- End Message ---
