** Description changed:
+ [Impact]
+
+ libvirtd to start within guests of some Xen environments. This has been
+ reported by multiple users of the Rackspace public cloud. libvirt has
+ many use-cases in this environment, most notably driving upstream
+ OpenStack CI efforts. This bug makes libv
** Patch added: "Revised debdiff for Saucy"
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1248025/+attachment/4028449/+files/saucy-fixes.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bu
For the Saucy upload, please hold back. There is some follow up to avoid
an unnecessary error logged by libvirt when there is no Xen capabilities
file (functionality not impacted). I will push out some revised debdiff.
--
You received this bug notification because you are a member of Ubuntu
Bugs,
** Changed in: cloud-archive
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1248025
Title:
libvirt-bin fails to start inside Xen
To manage notifications about this b
This bug was fixed in the package libvirt - 1.2.2-0ubuntu3
---
libvirt (1.2.2-0ubuntu3) trusty; urgency=low
* d/p/libxl-Check-for-control_d-string-to-decide-about-dom.patch: Prevent
using the libxl driver when not running in dom0 but having xenfs mounted.
(LP: #1248025)
--
** Also affects: libvirt (Ubuntu Saucy)
Importance: Undecided
Status: New
** Also affects: libvirt (Ubuntu Trusty)
Importance: Undecided
Assignee: Stefan Bader (smb)
Status: In Progress
** Changed in: libvirt (Ubuntu Saucy)
Status: New => In Progress
** Changed in
The change was accepted upstream. So here is the debdiff for Trusty,
too. Note that things will need a bit of fiddling as we need to modify
xend detection around the same place as Debian packaging is different.
** Patch added: "trusty-fixes.debdiff"
https://bugs.launchpad.net/ubuntu/+source/li
** Tags added: patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1248025
Title:
libvirt-bin fails to start inside Xen
To manage notifications about this bug go to:
https://bugs.launchpad.net/clou
Waiting for the outcome of the upstream discussion, but this would be
the proposed change for the Saucy libvirt package (fixing the toolstack
path and dom0 detection).
** Patch added: "proposed-fixes.debdiff"
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1248025/+attachment/4019926/+f
To clarify, I think someone said Precise guests would suffer the same.
But that should only be with a libvirt version from Saucy (to be more
precise a libvirt compiled against libxen-dev from Saucy as that was the
first release that had the packaging fixed so libvirt would build the
libxl driver).
So Adam was giving me access to some Rackspace guests. I found that in those a
xenfs was mounted to /proc/xen. This was done by the init script of
xe-guest-utilities. I suspect this is something that works together with a
XenServer host. There was also a nova-agent running which I could not find
Downgrading the libxen and libxenstore libraries (sorry, I was referring
to those before but wrote libvirt). to previous versions did not help to
cause the issue. Also used a precise (Xen-4.1) host for the same Saucy
guest. Still libvirtd starts and keeps running.
--
You received this bug notific
This is dirty but at the same time we could be quite sure this does work
as it is clearly the startup going wrong. :)
Maybe I can go the other way round and downgrade my libvirt version to
the ubuntu1.1 level to see whether things fail then. Some of the CVE
fixes just read to me as fix leaking hyp
I know this is dirty, but...
removing /usr/lib/libvirt/connection-driver/libvirt_driver_libxl.so and
/usr/lib/libvirt/connection-driver/libvirt_driver_xen.so makes libvirt-
bin launch on the Rackspace public cloud.
A strace of the libvirt-bin process shows it opening /proc/xen/xenbus
and then try
Adam (or others), in the Saucy instance, which version of libxen does get
installed there? The current version should be 4.3.0-1ubuntu1.3. This is the
version I have been testing with. Though in the dpkg list from rackerjoe that
was back at ubuntu1.1.
Somehow it seems in my case libxl_ctx_alloc
Hitting this on rackspace using on both a saucy instance /w 1.1.1-0ubuntu8.5
and on a precise instance /w cloud archive's 1.1.1-0ubuntu8.5~cloud0. Attached
is a debug log of saucy's failure.
** Attachment added: "debug"
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1248025/+attac
** Package changed: ubuntu => libvirt (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1248025
Title:
libvirt-bin fails to start inside Xen
To manage notifications about this bug go to:
https
Hm, ok. Looks like the patch mentioned above was in v0.9.0 already, so
at least that would be in 1.1.1 already in the Saucy version.
Unfortunately trying to reproduce locally is not working. The effect is
just as I would expect it. In the libxl specific log I get:
xc: error: Could not obtain hand
Thanks rackerjoe. That change sounds quite plausible. And the explanation
helped greatly to understand how things are meant to be. I initially tried to
reproduce with a PV guest (because that is at least in EC2 the more common
type). Though that did not work (or rather it failed not to work). Wi
This commit in libvirt-bin upstream may be useful for tracking this
down:
commit 03ede2f69d294af49642805384d54ac8ac7a4adc
Author: Daniel Veillard
Date: Fri Apr 1 19:30:53 2011 +0800
Fix libxl driver startup
When you happen to have a libvirtd binary compiled with the
libxenlight
tried the libvirt-bin in icehouse cloud-archive and different bug so I
tried the grizzly one.
I just tested and verified that this issue does not exist in libvirt-
bin_1.0.2-0ubuntu11.13.04.5~cloud1_amd64.deb which is available in the
grizzly ubuntu cloud-archive.
So, some change between 1.0.2 an
** Attachment added: "dmidecode.txt"
https://bugs.launchpad.net/ubuntu/+bug/1248025/+attachment/4006657/+files/dmidecode.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1248025
Title:
libvirt-
** Attachment added: "cpuinfo.txt"
https://bugs.launchpad.net/ubuntu/+bug/1248025/+attachment/4006655/+files/cpuinfo.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1248025
Title:
libvirt-bin
** Attachment added: "dmesg.txt"
https://bugs.launchpad.net/ubuntu/+bug/1248025/+attachment/4006656/+files/dmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1248025
Title:
libvirt-bin fail
This is a PVHVM kernel. I will attach dmesg, dmidecode, libvirtd log,
and list of packages installed.
To answer your question about why libvirt is installed on the guest - we
use the public cloud to test certain openstack features with qemu. We
understand that you don't get hardware virt with th
** Attachment added: "libvirtd.log"
https://bugs.launchpad.net/ubuntu/+bug/1248025/+attachment/4006659/+files/libvirtd.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1248025
Title:
libvirt-bi
** Attachment added: "dpkg.txt"
https://bugs.launchpad.net/ubuntu/+bug/1248025/+attachment/4006658/+files/dpkg.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1248025
Title:
libvirt-bin fails
First question is what kind of Xen guests are the default for Rackspace (PV or
HVM). I suspect PV because of the dmi/id errors. Then I wonder whether there is
anything more related to Xen installed in the guests than libxen and
libxenstore.
The message about xen-toolstack actually shows a glitch
I'm seeing this issue on Precise too.
libvirtd.log:
2014-03-03 04:11:05.819+: 3454: info : libvirt version: 1.2.1
2014-03-03 04:11:05.819+: 3454: error : udevGetDMIData:1558 : Failed to get
udev device for syspath '/sys/devices/virtual/dmi/id' or '/sys/class/dmi/id'
2014-03-03 04:11:05.8
I'm getting the same error as @breu. Is there some way to workaround it?
Is the xen-toolstack bin path hardcoded or can it be configured?
$ uname -a
Linux jupiter 3.11.0-17-generic #31~precise1-Ubuntu SMP Tue Feb 4 21:25:43 UTC
2014 x86_64 x86_64 x86_64 GNU/Linux
$ cat /var/log/libvirt/libvirtd.
** Package changed: libvirt-bin (Ubuntu) => cloud-archive
** Project changed: cloud-archive => ubuntu
** Also affects: cloud-archive
Importance: Undecided
Status: New
** Changed in: cloud-archive
Status: New => Confirmed
--
You received this bug notification because you are a
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: libvirt-bin (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1248025
Title:
Getting a somewhat similar error:
root@breu-ubuntu-grizzly-neutron-node4:/etc/libvirt# /usr/sbin/libvirtd -l -v
2014-02-18 00:29:42.945+: 6009: info : libvirt version: 1.1.1
2014-02-18 00:29:42.945+: 6009: error : virExec:418 : Cannot find
'usr/lib/xen-common/bin/xen-toolstack' in path: N
33 matches
Mail list logo
