Yes, when I originally opened a bug on this we were using headless
rackmount servers. I would imagine that is the dominant use case.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to open-vm-tools in Ubuntu.
Dianne: If I remember correctly, this warning didn't actually cause the
package install to fail. Maybe you have another problem? What exactly is
the error message you get?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to bacula in
* Starting Bacula Director...
21-Apr 10:23 bacula-dir: ERROR TERMINATION at lex.c:784
Config error: expected a string, got T_EOL: =
: line 236, col 12 of file /etc/bacula/bacula-dir.conf
dbname = ; DB Address = ; dbuser = ; dbpassword =
That is your problem. It is already reported
Did this ever get fixed? The upstream patch with the helper was posted
to the mailing list in November 2009 and in the same thread it is
mentioned that the Ubuntu packaging would enable this by the time
Lucid/qemu-0.12-rc1 was released.
Do you have a link for the qemu-devel thread? I had a look at
http://lists.gnu.org/archive/html/qemu-devel/ but couldn't see anything.
--
virsh save is very slow
https://bugs.launchpad.net/bugs/524447
You received this bug notification because you are a member of Ubuntu
Server Team, which is
Public bug reported:
Binary package hint: nagios3
# apt-get install nagios3
...
Setting up nagios3-common (3.2.0-4ubuntu2) ...
Adding system-user for nagios
Creating config file /etc/nagios3/conf.d/host-gateway_nagios3.cfg with new
version
* Starting nagios3 monitoring daemon nagios3
Public bug reported:
Binary package hint: nagios3-cgi
Install nagios3
Goto http://localhost/nagios3/
Click View Config-Hosts
Icons in columns Statusmap image and VRML image are broken:
* Statusmap image uses
http://localhost/nagios3/images/logos/base/debian.gd2 which is a non-
standard
Public bug reported:
Binary package hint: nagios3
As detailed at http://forums.meulie.net/viewtopic.php?f=61t=4502 and
https://help.ubuntu.com/community/Nagios3
/etc/nagios-plugins/config/disk.cfg needs the arguments [-A -i '.gvfs']
Nagios by default should ignore gvfs - user shouldn't be
3.2.0-4ubuntu2
** Changed in: nagios3 (Ubuntu)
Status: Incomplete = New
--
nagios3-cgi bad icons after install
https://bugs.launchpad.net/bugs/615837
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nagios3 in ubuntu.
--
Sorry, we no longer have that server.. too many problems, kvm+libvirt
ended up getting replaced with ESXi...
--
libvirtd can't start qemu:///session domain - failed to set CPU affinity:
Operation not permitted
https://bugs.launchpad.net/bugs/535147
You received this bug notification because you
gdahlman has it right. This issue and the lack of snapshots were the two
main reasons that the company I work for left Ubuntu KVM and settled on
VMware ESXi.
--
libvirt-bin hypervisor does not support virConnectNumOfInterfaces / unable to
create domain with virt-manager using network bridge
Public bug reported:
Binary package hint: bacula-director-mysql
Fresh install warns about unknown template:
Setting up bacula-director-mysql (5.0.1-1ubuntu1) ...
debconf: Unknown template field '_description', in stanza #9 of
/var/lib/dpkg/info/bacula-director-mysql.templates
dbconfig-common:
Install fresh system using ubuntu-10.04-amd64-server.iso
# apt-get install bacula-director-mysql
Setting up bacula-director-mysql (5.0.1-1ubuntu1) ...
Installing new version of config file /etc/bacula/scripts/make_catalog_backup
...
Installing new version of config file
I did the following and it works:
apt-get install autofs smbfs smbclient
echo /smb /etc/auto.smb /etc/auto.master
mkdir /smb
/etc/init.d/autofs restart
ls /smb/buffalo/share (buffalo is a samba host, share is the share name -
replace with local details)
Initially this was not working for me,
Vadmin: You can still use KVM through the command line, or through virt-
manager if you ssh in to your VM host, run virt-manager, and connect to
localhost. This requires virt-manager and a bunch of X11 type libraries
to be installed on your VM host.
--
libvirt-bin hypervisor does not support
Same error as bug #423653 ?
--
package bind9 1:9.6.1.dfsg.P1-3 [modified:
usr/share/bind9/bind9-default.md5sum] failed to install/upgrade: subprocess
installed post-installation script killed by signal (Interrupt)
https://bugs.launchpad.net/bugs/437783
You received this bug notification
This bug looks like it could be the same as bug #437783
After install postfix says: Postfix was not set up. Start with cp
/usr/share/postfix/main.cf.debian /etc/postfix/main.cf
Doing this cp fixed the errors for me. Before that I would always get
the following on ifup/ifdown:
*** This bug is a duplicate of bug 426497 ***
https://bugs.launchpad.net/bugs/426497
** This bug has been marked a duplicate of bug 426497
kqemu mode not compiled for karmic
--
kqemu not available in karmic
https://bugs.launchpad.net/bugs/424765
You received this bug notification because
This bug still exists in karmic. You can use --mask 255.255.255.0 in
the vm-builder command line as a workaround.
--
VMBuilder/vm.py crash on an alpha char in numeric constant
https://bugs.launchpad.net/bugs/313575
You received this bug notification because you are a member of Ubuntu
Server
Public bug reported:
Binary package hint: libvirt-bin
$ virsh iface-list
error: Failed to list active interfaces
error: this function is not supported by the hypervisor:
virConnectNumOfInterfaces
This occurs on both karmic and lucid. This means that a user will be
unable to create a new domain
I think this bug also causes the virt-manager configuration of a virtual
network with forwarding to fail:
Host config - Virtual networks - Create a new virtual network -
Connecting to physical network - Forwarding to physical network -
Destination:Any physical device
Destination is a drop down
also note that virt-manager under karmic will just fail on these
operations. virt-manager under lucid warns that Libvirt version does
not support physical interface listing if you browse to: Add new
virtual hardware - Network - Host device
--
libvirt-bin hypervisor does not support
Public bug reported:
Upstream recommends to use default user:group = qemu:qemu
From http://libvirt.org/drvqemu.html
In the system instance, libvirt releases from 0.7.0 onwards allow
control over the user/group that the QEMU virtual machines are run as. A
build of libvirt with no configuration
Public bug reported:
Start a domain with virsh start dom
Do virsh save dom /tmp/x
virsh hangs forever and /tmp/x is a 1.7k file
** Affects: libvirt (Ubuntu)
Importance: Undecided
Status: New
--
virsh save hangs forever
https://bugs.launchpad.net/bugs/522686
You received this bug
Public bug reported:
The script does: start-stop-daemon --stop --pidfile /var/run/libvirtd.pid
--exec '/usr/sbin/libvirtd'
It should do something like: start-stop-daemon --stop --pidfile
/var/run/libvirtd.pid --exec '/usr/sbin/libvirtd' --retry 5
--retry means libvirtd will be sent SIGKILL if
Public bug reported:
# which libvirtd
/usr/sbin/libvirtd
# man libvirtd
No manual entry for libvirtd
See 'man 7 undocumented' for help when manual pages are not available.
** Affects: libvirt (Ubuntu)
Importance: Undecided
Status: New
--
libvirtd does not have a man page
*** This bug is a duplicate of bug 457716 ***
https://bugs.launchpad.net/bugs/457716
** This bug has been marked a duplicate of bug 457716
apparmor denies save and restore
--
virsh save hangs forever
https://bugs.launchpad.net/bugs/522686
You received this bug notification because you
Yes.
Do virsh save dom /tmp/x to hang libvirtd (bug #457716)
Then service libvirt-bin restart to restart libvirtd. It reports that the
service is running but this is not true - in fact the process has died without
reporting an error.
If I then run libvirtd manually I get:
# libvirtd
Public bug reported:
Binary package hint: libvirt-bin
$ virsh console host1
Connecting to uri: qemu:///system
Connected to domain host1
Escape character is ^]
11:17:06.610: error : vshRunConsole:77 : unable to open tty /dev/pts/1:
Permission denied
** Affects: libvirt (Ubuntu)
Importance:
Confirmed under Karmic.
--
virsh console does not work (/dev/pts/1: Permission denied)
https://bugs.launchpad.net/bugs/523148
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libvirt in ubuntu.
--
Ubuntu-server-bugs mailing list
Public bug reported:
As reported here: http://www.redhat.com/archives/libvir-
list/2009-December/msg00203.html
virsh save is very slow - it writes the image at around 1MB/sec on my
test system.
(I think I saw a bug report for this issue on Fedora's bugzilla, but I
can't find it now...)
** Bug watch added: Debian Bug tracker #567818
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=567818
** Also affects: libvirt (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=567818
Importance: Unknown
Status: Unknown
--
virsh console does not work (/dev/pts/1:
I'm sorry, this is not something that we can solve in the qemu-kvm
package that is in Ubuntu Main.
Why not? The standard Ubuntu kernel supports capabilities
(CONFIG_SECURITY_FILE_CAPABILITIES). It is obviously not desirable to
have qemu networking broken by default, or to tell users that they
Jules: I think your issue is different - my bug is about permissions but
the device path is ok. Your bug appears to have some weird device path
- causing the device to not be found. Check your XML definition in
/etc/libvirt/qemu/guest1.xml
--
virsh console does not work (/dev/pts/1: Permission
Kees: I know about the wiki page - I'm the one who edited it to note
this issue. It is not true that file capabilities only work in Lucid - I
am using Karmic and it works fine. libcap2-bin is also not a PAM
package. It is also not true that you need to manually add users to
Public bug reported:
Create a domain xml file. There is nothing special required in the VM
description, the following will suffice:
domain type='kvm'
nametest1/name
uuidcd224bdf-9b8a-e2f7-ef3b-ae7acfd30c1d/uuid
memory524288/memory
currentMemory524288/currentMemory
vcpu1/vcpu
os
This looks like a dupe of bug #103010 - tun/tap networking (necessary
for bridging) does not work in qemu for non-root users.
--
virt-manager Network bridge Operation not permitted
https://bugs.launchpad.net/bugs/519572
You received this bug notification because you are a member of Ubuntu
Server
Architecture: amd64
DistroRelease: Ubuntu 9.10
Package: libvirt-bin 0.7.0-1ubuntu13.1
PackageArchitecture: amd64
ProcEnviron:
SHELL=/bin/bash
PATH=(custom, user)
LANG=en_GB.UTF-8
ProcVersionSignature: Ubuntu 2.6.31-19.56-server
Uname: Linux 2.6.31-19-server x86_64
UserGroups: adm admin cdrom
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/40685654/Dependencies.txt
** Changed in: libvirt (Ubuntu)
Status: Incomplete = New
** Tags added: apport-collected
--
libvirtd can't start qemu:///session domain - failed to set CPU affinity:
Operation not
from strace:
futex(0x80cde0, FUTEX_WAIT_PRIVATE, 2, NULL11:38:23.962: error :
qemudInitCpus:1243 : failed to set CPU affinity: Operation not permitted
libvir: QEMU error : failed to set CPU affinity: Operation not permitted
qemudInitCpus:1243 does:
if (sched_setaffinity(vm-vcpupids[i],
That qemudInitCpus function is from src/qemu_driver.c : 1243
--
libvirtd can't start qemu:///session domain - failed to set CPU affinity:
Operation not permitted
https://bugs.launchpad.net/bugs/535147
You received this bug notification because you are a member of Ubuntu
Server Team, which is
This bug still exists on karmic
--
[Lucid] Error starting domain: could not remove profile
https://bugs.launchpad.net/bugs/517714
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libvirt in ubuntu.
--
Ubuntu-server-bugs mailing list
** Bug watch added: Debian Bug tracker #412941
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=412941
** Also affects: qemu-kvm (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=412941
Importance: Unknown
Status: Unknown
--
qemu no tun/tap networking
Is bug #523148 related to apparmor?
--
apparmor denies save and restore
https://bugs.launchpad.net/bugs/457716
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libvirt in ubuntu.
--
Ubuntu-server-bugs mailing list
*** This bug is a duplicate of bug 463684 ***
https://bugs.launchpad.net/bugs/463684
This bug was only fixed for Lucid?
The docs for Karmic here https://help.ubuntu.com/9.10/serverguide/C
/openldap-server.html are still wrong
--
OpenLDAP server instructions out of date: slapd no longer
The documentation for Karmic is still wrong:
https://help.ubuntu.com/9.10/serverguide/C/openldap-server.html
--
openldap sections in ubuntu server guide not updated for packages in karmic
https://bugs.launchpad.net/bugs/463684
You received this bug notification because you are a member of Ubuntu
Also see bug #355400 - OpenLDAP doc page is horrible.
I found this forum post
http://ubuntuforums.org/showpost.php?p=8161118postcount=6 and this
thread http://ubuntuforums.org/showthread.php?t=1313472 to be useful in
getting a server up and running. It's a shame the Ubuntu documentation
is still
The only KVM hardware I have access to at the moment is a production
server. Upgrading it to lucid - which is still in beta - is not really
feasible at the moment.
--
libvirtd can't start qemu:///session domain - failed to set CPU affinity:
Operation not permitted
Public bug reported:
Binary package hint: qemu-kvm
Booting Centos 4 with the default 2.6.9 kernel I get a sporadic error
maybe ~5% of the time:
ENABLING IO-APIC IRQs
..TIMER: vector=0x31 pin1=2 pin2=-1
..MP-BIOS bug: 8254 timer not connected to IO-APIC
...trying to set up timer (IRQ0) through
If the diagnosis I posted above is correct, then the frequency with
which this error appears will depend on both the virtualisation platform
(in this case the KVM host) and the guest kernel. We virtualise CentOS
4.4 systems (2.6.9 kernel) and my colleague reports that, in two years
of using
Public bug reported:
Binary package hint: qemu-kvm
Trying to boot this iso:
7d88cd87df509a740d9f47b9bbf1375e *ubuntu-7.10-server-i386.iso
( from http://mirror.linux.org.au/ubuntu-releases/7.10/ )
Domain XML definition is:
domain type='kvm' id='13'
nameubuntu710/name
Confirmed under Karmic.
--
qemu-kvm: ubuntu-7.10-server-i386.iso fails to boot
https://bugs.launchpad.net/bugs/564727
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu-kvm in ubuntu.
--
Ubuntu-server-bugs mailing list
Apparently this is listed already on the upstream page http://www.linux-
kvm.org/page/Guest_Support_Status#Linux_Family:_Ubuntu.2FDebian_Derivatives
--
qemu-kvm: ubuntu-7.10-server-i386.iso fails to boot
https://bugs.launchpad.net/bugs/564727
You received this bug notification because you are a
The Debian bug appears to have been marked Fix Released because the
actual qemu package was removed from Debian and replaced with qemu-kvm.
Maybe another bug needs to be opened for that package.
--
qemu no tun/tap networking
https://bugs.launchpad.net/bugs/103010
You received this bug
** Also affects: dhcp3 (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=717217
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to dhcp3 in Ubuntu.
55 matches
Mail list logo
