From: PeanuTech <peanutdude@gmail.com>
To: xen-devel@lists.xensource.com
Subject: Error booting domU
Date: Sat, 19 Jun 2010 22:49:46 +0300 [thread overview]
Message-ID: <AANLkTincg9iMUfGMdbhgdtFoj3ynanB0x3PfOFloaw7-@mail.gmail.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1059 bytes --]
I use xen-4.0.1-rc3-pre with linux 2.6.31.13 on Ubuntu Lucid and
virt-manager 0.8.4. When I try to run a Fedora 13 PV domain that I've
created I get the following error:
Error starting domain: POST operation failed: xend_post: error from xen
daemon: (xend.err "Boot loader didn't return any data!")
And the details are:
raceback (most recent call last):
File "/usr/share/virt-manager/virtManager/engine.py", line 814, in
run_domain
vm.startup()
File "/usr/share/virt-manager/virtManager/domain.py", line 1286, in
startup
self._backend.create()
File "/usr/lib/python2.6/dist-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!")
I found on google several references to this problem, and almost alll of
them wrote that you need to make symbolic links, so that libvirt could find
the Xen components.
I don't know which files I need to link. What should I do?
[-- Attachment #1.2: Type: text/html, Size: 1366 bytes --]
[-- Attachment #2: Type: text/plain, Size: 138 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
next reply other threads:[~2010-06-19 19:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-19 19:49 PeanuTech [this message]
2010-06-19 20:14 ` Error booting domU Pasi Kärkkäinen
2010-06-20 7:50 ` PeanuTech
2010-06-20 8:43 ` Pasi Kärkkäinen
2010-06-20 21:26 ` PeanuTech
2010-06-20 21:33 ` Pasi Kärkkäinen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=AANLkTincg9iMUfGMdbhgdtFoj3ynanB0x3PfOFloaw7-@mail.gmail.com \
--to=peanutdude@gmail.com \
--cc=xen-devel@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.