[Bug 989452] Re: oneiric's virt-viewer can't connect to console of precise's virtual machines

There are currently multiple bugs that deal with virt-manager/virt- viewer not being able to connect to a VNC console of a Libvirt/KVM domain, such as #837275, #995320 and this one. The problem remains, however. On a Precise server (12.04.1) where /etc/libvirt/qemu.conf has set vnc_listen = "0.0.

[Bug 989452] Re: oneiric's virt-viewer can't connect to console of precise's virtual machines

Addendum: All this with Precise machines (client and server), no Oneiric or earlier involved. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu-kvm in Ubuntu. https://bugs.launchpad.net/bugs/989452 Title: oneiric's virt-viewer can

[Bug 989452] Re: oneiric's virt-viewer can't connect to console of precise's virtual machines

Serge, at the moment it is a bit difficult but in a few weeks I could have some spare machines available on which I could install Quantal. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu-kvm in Ubuntu. https://bugs.launchpad.net/bu

[Bug 445619] Re: slapd should start before kerberos kdc and admin servers, possibly others

This is still a problem, both in Lucid and Precise. ** Summary changed: - [karmic] slapd should start before kerberos kdc and admin servers, possibly others + slapd should start before kerberos kdc and admin servers, possibly others -- You received this bug notification because you are a membe

[Bug 545795] Re: apparmor driver blocks access to hostdev and pcidev devices

I'm sorry to post to this bug that has a status of "Fix released" but I am not sure it is really fixed. I have a situation similar too the original poster's concerning a USB card reader that won't make it past AppArmor it seems. Using libvirt-bin 0.7.5-5ubuntu27. Situation: one of our servers was

[Bug 545795] Re: apparmor driver blocks access to hostdev and pcidev devices

Interestingly, or perhaps not, merely running /etc/init.d/apparmor stop isn't enough. I stop AppArmor, restart Libvirt and then start my VMs. However upon starting a VM an AppArmor profile still gets loaded and thus AppArmor denies access to the USB device I want to pass through. I have to run /etc

[Bug 545795] Re: apparmor driver blocks access to hostdev and pcidev devices

Looks like I found it. The VM in my case is trying to access /sys/devices/pci:00/:00:1e.0/:01:04.4/usb6/devnum but the abstractions/libvirt-qemu profile only allows /sys/bus/usb/devices/ r, /sys/devices/*/*/usb[0-9]*/** r, when it should (also) allow /sys/devices/*/*/*/usb[0-

[Bug 545795] Re: apparmor driver blocks access to hostdev and pcidev devices

Jamie, yes this fixes it. thank you! I notice however some redundancies between abstractions/libvirt-qemu and usr.lib.libvirt.virt-aa-helper? At least the line "/sys/bus/usb/devices/ r," appears in both, don't know if that matters any, though. So that's good :) But now I have discovered something

[Bug 545795] Re: apparmor driver blocks access to hostdev and pcidev devices

Oh and it seems that disconnecting/detaching an USB device from the running VM doesn't work at all? virt-manager complains: Device could not be removed from the running machine. This change will take effect after the next VM reboot But this has probably nothing to do with AppArmor and may just be

[Bug 578332] [NEW] AppArmor blocks hot-attaching of USB devices

Public bug reported: On Ubuntu 10.04 server, after applying the fixes to Libvirt's AppArmor profiles as discussed in bug 545795 the hot-attachment of USB devices is blocked/denied by AppArmor. Hot-attachment means: a KVM-based VM is running and a USB devices connected to the underlying host is to

[Bug 578332] Re: AppArmor blocks hotplugging of USB devices

** Summary changed: - AppArmor blocks hot-attaching of USB devices + AppArmor blocks hotplugging of USB devices ** Description changed: On Ubuntu 10.04 server, after applying the fixes to Libvirt's AppArmor - profiles as discussed in bug 545795 the hot-attachment of USB devices is - blocked/de

[Bug 423252] Re: NSS using LDAP+SSL breaks setuid applications like su, sudo, apache2 suexec, and atd

Just to add something that has nothing to do directly with this bug, but is related: we have been using SSSD for quite a while now, using Timo Aaltonen's PPA and could not be happier. In my opinion SSSD is the superior solution for all things authn/aut

[Bug 1393923] Re: postfix (2.11.0-1) does not LDAP table lookup since libp11-kit0 (0.20.2-2ubuntu2)

Over a year later this problem still exists. It is impossible to run a Postfix server that does (SSL/TLS secured) LDAP lookups on Ubuntu 14.04.3. I wonder how is this not affecting more people? -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscri

[Bug 1414684] [NEW] bsd-mailx no longer supports sendmail options, thus breaking existing scripts (like Bootmail)

Public bug reported: The security update of bsd-mailx (8.1.2-0.2006cvs-1ubuntu0.1 on Ubuntu 12.04) removes bsd-mailx's support for specifying sendmail options after "--" on the commandline. This breaks any script that supplies classic sendmail options like -F or -f on the mail commandline. A

[Bug 1414684] Re: bsd-mailx no longer supports sendmail options, thus breaking existing scripts (like Bootmail)

Bug against Bootmail is here: https://bugs.launchpad.net/ubuntu/+source/bootmail/+bug/1414696 > What do you suggest instead? I don't really have a suggestion and I am not disputing that this change was necessary. But the USN description doesn't even mention that specifying sendmail options after

[Bug 1414684] Re: bsd-mailx no longer supports sendmail options, thus breaking existing scripts (like Bootmail)

FWIW, I am content with the updated USN and agree with Won't Fix. Just wanted to raise the issue here in case I am not the only one bitten by this change. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to bsd-mailx in Ubuntu. https://bugs

[Bug 495394] Re: autostart almost always fails on boot time host

Mika, thank you for the patch and new upstart job. We are trying it out here and find that the bridged-network job seems to be waiting forever for a "net-device-up" signal to be emitted, thus keeping libvirtd-bin from starting. I only now have begun reading up on upstart but so far I can't find an

[Bug 495394] Re: autostart almost always fails on boot time host

Thanks for the new patch! I tested it just now and it seems to work, but it's always hard to tell when dealing with race conditions. I'll keep testing. Out of interest, the only change (apart from the more verbose way of testing the $interface variable) is the added "break" statement, right? I am

[Bug 81242] Re: postfix-ldap is linked against gnuTLS

For what it's worth this is still a problem in 10.04.1 and Postfix 2.7.0-1. Manually copying /dev/random and /dev/urandom to /var/spool/postfix/dev works around the problem. I also find it quite strange that this doesn't affect more people. In fact this bug seems to have been completely forgotten.

[Bug 579723] Re: kvm memory ballooning is unusable in Lucid

This does not seem fixed in 10.04.1. The fix would apparently belong in Libvirt but the changelogs for the Libvirt package in 10.04.1 don't indicate anything and no KVM guest processes on my hosts running 10.04.1 show the "-balloon virtio" flag. I had to use a wrapper script around qemu-system-x86_

[Bug 350936] Re: Should shut down domains on system shutdown

Orticio, this is an English-speaking forum. Please stop asking people to speak Spanish. Translated by Google: Este es un foro de habla Inglés. Por favor, deje de pedir a la gente a hablar español. -- You received this bug notification because you are a member of Ubuntu Server Team, which is sub

[Bug 350936] Re: Should shut down domains on system shutdown

So is there any way the proper fix will make it into Lucid? Or has that ship sailed? In the meantime I have applied Sebastian Marsching's method which works quite well. Thanks for that, Sebastian. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subs

[Bug 350936] Re: Should shut down domains on system shutdown

Clint, great to hear, thanks. We have many Lucid servers in production, but no Maverick or Natty, so the fix getting into Lucid is most important for us. But if time and resources allow it, backporting the fix to Maverick and Natty would certainly be nice. -- You received this bug notification be

[Bug 368962] Re: [Jaunty] Can't reboot kvm virtual machines using virsh

This bug doesn't seem to have gotten much attention since July last year but I can report that the issue still exists on Karmic using libvirt-bin 0.7.0-1ubuntu13.1: $ virsh reboot foo1 Connecting to uri: qemu:///system error: Failed to reboot domain foo1 error: this function is not supported by th

[Bug 517067] [NEW] Using virtio for block devices makes disks and partitions disappear in KVM/QEMU (using vmbuilder and libvirt)

Public bug reported: Binary package hint: libvirt-bin I can reproduce that trying to use bus='virtio' for virtual disks in the definition of a libvirt domain makes virtual disks thus defined disappear in the eyes of KVM/QEMU. This leads to error messages like the following when booting, as well a

[Bug 517067] Re: Using virtio for block devices makes disks and partitions disappear in KVM/QEMU (using vmbuilder and libvirt)

** Attachment added: "Domain definition for guest "foo", using virtio for block devices" http://launchpadlibrarian.net/38748978/foo.xml -- Using virtio for block devices makes disks and partitions disappear in KVM/QEMU (using vmbuilder and libvirt) https://bugs.launchpad.net/bugs/517067 You

[Bug 517067] Re: Using virtio for block devices makes disks and partitions disappear in KVM/QEMU (using vmbuilder and libvirt)

Thanks for the comment, but how do you figure? I did not change anything after the fact, I modified the template used for installation and setup of the guest domain. First, it seems to depend on the bus type whether the virtual disks are at all visible to QEMU, as can be seen from the screenshots.

[Bug 303882] Re: python-vm-builder --raw doesn't set size correctly

Would also like to see this fixed for karmic. Using python-vmbuilder 0.11.3-0ubuntu1 and the same error occurs when trying to use a 10G LVM volume as a --raw device. I assume this is the same bug. sudo vmbuilder kvm ubuntu --debug --verbose -m 2048 --raw=/dev/mapper/vg --storage-lv--chat_root --ro

[Bug 517067] Re: Using virtio for block devices makes disks and partitions disappear in KVM/QEMU (using vmbuilder and libvirt)

You are right of course, /etc/fstab on the guest contains "/dev/sdXY" entries. These get generated by /usr/share/pyshared/VMBuilder/plugins/ubuntu/feisty.py as you mentioned. After changing all "/dev/sdXY" to "/dev/vdXY" I can indeed boot happily :) What threw me off was that QEMU did not (and doe

[Bug 1325560] Re: kvm virtio netdevs lose network connectivity under "enough" load

Installing 3.14.1 as per comment #17 fixed these connectivity issues for us as well, but it doesn't look like the 3.14.1 kernel made it anywhere near the 14.04.1 release. There is also no mention of this or any related bugs in https://wiki.ubuntu.com/TrustyTahr/ReleaseNotes/ChangeSummary/14.04.1.