Failure to start kvm can also be caused by VirtualBox running on the
host - watch out for dmesg like:
kvm: enabling virtualization on CPU3 failed
kvm: enabling virtualization on CPU0 failed
kvm: enabling virtualization on CPU2 failed
kvm: enabling virtualization on CPU1 failed
to fix it:
#
(yes: this is mostly the same text as I posted for Bug #241305 because
the same problems apply)
This issue has been reported over 4 years ago, and has become a serious
real-life problem for organisations. IANA (global supply) ran out of
IPv4 addresses in February 2011. Shortly after that APNIC
** Changed in: lm-sensors (Ubuntu)
Status: Incomplete = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lm-sensors in Ubuntu.
https://bugs.launchpad.net/bugs/1078922
Title:
Fan runs unnecessary
To manage
Dear Phillip Susi,
I have run Ubuntu 12.10 with kernel linux-image-3.2.0-33.52-generic without
headers.
It has not helped. The problem has remained.
I now notice that even with cold hardware the fan continues to run at full
speed at 28°C because there just was a peak to 37°C.
--
You received
Hi Dan
Thanks for the report; the reason the source package in Debian and
Ubuntu pulls from github is that we don't use the embedded libs3 or
leveldb as distributed at http://ceph.com/download/.
I would suspect that this file gets stripped out during the automatic
archive creation on github.
This is per design.
** Changed in: quagga (Ubuntu)
Status: New = Invalid
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to quagga in Ubuntu.
https://bugs.launchpad.net/bugs/1078620
Title:
package quagga
Then I'm afraid I have to stand by what I said before: this isn't a bug.
You will need to look into your motherboard manual to see if there are
settings you can tune for the fan.
** Changed in: lm-sensors (Ubuntu)
Status: Confirmed = Invalid
--
You received this bug notification because
so what is the actual syntax for OpenStack Essex?
I also did not find anything in the docs (maybe I am blind) that you can
specify a hostname as part of the availability zone's name.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to
It's not that the file gets stripped out, but that it is generated by
'make dist' when the tarballs are built.
There are --with-system-libs3 and --with-system-leveldb configure flags
that ignore the bundled library code. Would it help if those were the
defaults? Or is there a fundamental issue
There is an explanatory comment on the review for the doc update but we
have not back ported to Essex docs - see
https://review.openstack.org/#/c/15983/
Anne Gentle
Content Stacker
a...@openstack.org
On Nov 17, 2012, at 9:23 AM, Christian Parpart tra...@gmail.com wrote:
so what is the actual
You have been subscribed to a public bug:
On Ubuntu 12.10, tzdata says the date is 2005. i wanted to changed it
but it's not possible to change it. i tried to reinstall and reconfigure
tzdata but it didn't work
** Affects: ntp (Ubuntu)
Importance: Undecided
Status: Confirmed
--
i also tried to change it manually, but it doesn't work
** Package changed: tzdata (Ubuntu) = ntp (Ubuntu)
** Changed in: ntp (Ubuntu)
Status: Invalid = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to ntp in Ubuntu.
Hello! Without further information as to why asterisk failed to start,
we cannot proceed with attempts to reproduce or fix this issue. Can you
include relevant log files so that we can debug the issue? Thanks!
** Changed in: asterisk (Ubuntu)
Importance: Undecided = Medium
** Changed in:
Re debconf, thats not really a factor. Not answering the questions just
uses defaults, but debconf and the maintainer scripts that use it do not
change their behavior. Indeed, I think this issue doesn't seem to have
much helpful information. I'm going to close it as Invalid.
** Changed in: puppet
Hello! I suspect your deb package may have become corrupted in some way.
Can you try running 'sudo apt-get clean' and then installing again?
** Changed in: unixodbc (Ubuntu)
Status: New = Incomplete
** Changed in: unixodbc (Ubuntu)
Importance: Undecided = Medium
--
You received this
Hi py, its very difficult to debug an issue like this without two
important things:
1) a core dump from the segfault. If you attach that, please mark the
bug private first (so that nobody can read the contents of your RAM).
2) log files for smbd surrounding the event.
Without those, we won't be
16 matches
Mail list logo