[Bug 1084514] Re: Unable to connect to EC2 instance after bootstrap
I can't reproduce this. Yolanda, since you marked this confirmed, were you able to reproduce it? -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to juju in Ubuntu. https://bugs.launchpad.net/bugs/1084514 Title: Unable to connect to EC2 instance after bootstrap To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/juju/+bug/1084514/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1080912] Re: qemu-kvm must depend on udev
Verified in precise. -- 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/1080912 Title: qemu-kvm must depend on udev To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu-kvm/+bug/1080912/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1057024] Re: kvm kernel module always loaded, without setting /dev/kvm permissions
(Re-verified in precise) -- 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/1057024 Title: kvm kernel module always loaded, without setting /dev/kvm permissions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu-kvm/+bug/1057024/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1077838] Re: qemu-nbd -r -c taints device for subsequent usage, even after -d
Verified on precise. -- 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/1077838 Title: qemu-nbd -r -c taints device for subsequent usage, even after -d To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1077838/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1078530] Re: upstart job fails to start under lxc
This bug is not fully solved by this version, because the init job still tries to load and unload kvm modules. The qemu-kvm job should detect that it is running in a container and gracefully exit. -- 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/1078530 Title: upstart job fails to start under lxc To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu-kvm/+bug/1078530/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1078530] Re: upstart job fails to start under lxc
Verified in quantal, where the upstart job also does ||true when modprobe and rmmod fail. However, not running in a container at all would be safer. -- 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/1078530 Title: upstart job fails to start under lxc To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu-kvm/+bug/1078530/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1077838] Re: qemu-nbd -r -c taints device for subsequent usage, even after -d
Verified on quantal. ** Tags removed: verification-needed ** Tags added: verification-done -- 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/1077838 Title: qemu-nbd -r -c taints device for subsequent usage, even after -d To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1077838/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1080912] Re: qemu-kvm must depend on udev
Verified in quantal. ** Tags removed: verification-needed ** Tags added: verification-done -- 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/1080912 Title: qemu-kvm must depend on udev To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu-kvm/+bug/1080912/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1078530] Re: upstart job fails to start under lxc
@lifeless, the upstart job is only responsible for setting up the kvm kernel module and related kernel settings. With my new proposed change, the upstart job would detect it's in a container and consider itself done. In reality, for quantal the modprobes and rmmods were already doing '|| true'. So the only thing my new upload changes is that rather than try to do all these things and be denied, it won't try. (Or, rather than try to do them and succeed due to a bad policy, and potentially break the host.) The host will have to set up kvm; but it would have to anyway, since containers are never allowed to modprobe by default. And quantal and later always modprobe kvm on the host. Finally, libvirt and python-libvirt do not depend on qemu-kvm. But again, qemu-kvm will install just fine and even be usable in the container. It just can't be set up there. -- 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/1078530 Title: upstart job fails to start under lxc To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu-kvm/+bug/1078530/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
Re: [Bug 589063] Re: Windows Server 2008 won't boot with more than 4 vCPUs
Quoting Simon Déziel (589...@bugs.launchpad.net): I confirmed the package from Nigel's PPA works well and fixed the issue. I'd still really appreaciate if the package could re-enter -proposed and later -updates. Thanks I've re-pushed to -proposed, but need an admin to accept it. -- 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/589063 Title: Windows Server 2008 won't boot with more than 4 vCPUs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu-kvm/+bug/589063/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1068365] Re: openvswitch gre tunnels not working in quantal
Thiago, I *think* you misunderstood. There is no claim that this is fixed in the upstream driver. Rather the openvswitch-dkms package, which has the non-upstream kernel driver, was re-added to the archive. You can install and use it to use this feature until the feature is added to the upstream kernel driver. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openvswitch in Ubuntu. https://bugs.launchpad.net/bugs/1068365 Title: openvswitch gre tunnels not working in quantal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1068365/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1094019] Re: Linux's getdents gets /.. inode number from host system under LXC
I can't reproduce this on my raring laptop. ubuntu@r2:~$ ls -lid / /.. 2783189 drwxr-xr-x 22 root root 4096 Jan 2 15:58 / 2783189 drwxr-xr-x 22 root root 4096 Jan 2 15:58 /.. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1094019 Title: Linux's getdents gets /.. inode number from host system under LXC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1094019/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1094019] Re: Linux's getdents gets /.. inode number from host system under LXC
Nor can I reproduce it on a precise instance running 3.2.0-35-virtual #55-Ubuntu: ubuntu@p1:~$ ls -lid / /.. 139754 drwxr-xr-x 22 root root 4096 Jan 2 16:09 / 139754 drwxr-xr-x 22 root root 4096 Jan 2 16:09 /.. ** Changed in: lxc (Ubuntu) Importance: Undecided = Critical ** Changed in: lxc (Ubuntu) Importance: Critical = Medium -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1094019 Title: Linux's getdents gets /.. inode number from host system under LXC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1094019/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1094019] Re: Linux's getdents gets /.. inode number from host system under LXC
Ok, sorry, I see now. Yes i can reproduce this with getdents of course. This has nothing to do with lxc lying, and yes if you need to work around this you'll need to use blockdev-backed rootfs for the containers. The container is set up with the tasks pivot_root'd into the container's /, which in your case is a bind mount. Resolution of '..' respects the fact that the /var/lib/lxc/container/rootfs should be root, and returns itself. However, there is only one actual directory entry for /var/lib/lxc/container/rootfs in all the kernel, and it's '..' (d_parent) points to /var/lib/lxc/container. Lxc can't do anything about that. The kernel's flexible mounts, bind mounts, and mounts namespaces provide different *views* of the filesystems, don't change what is in the actual filesystems. ** Changed in: lxc (Ubuntu) Status: New = Won't Fix -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1094019 Title: Linux's getdents gets /.. inode number from host system under LXC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1094019/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1077838] Re: qemu-nbd -r -c taints device for subsequent usage, even after -d
Re-verified in precise. ** Tags removed: verification-needed ** Tags added: verification-done -- 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/1077838 Title: qemu-nbd -r -c taints device for subsequent usage, even after -d To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1077838/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1057024] Re: kvm kernel module always loaded, without setting /dev/kvm permissions
Re-verified. ** Tags removed: verification-needed ** Tags added: verification-done -- 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/1057024 Title: kvm kernel module always loaded, without setting /dev/kvm permissions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu-kvm/+bug/1057024/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1080912] Re: qemu-kvm must depend on udev
** Tags removed: verification-needed ** Tags added: verification-done ** Tags removed: verification-done ** Tags added: verification-needed ** Tags removed: verification-needed ** Tags added: verification-done -- 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/1080912 Title: qemu-kvm must depend on udev To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu-kvm/+bug/1080912/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1078530] Re: upstart job fails to start under lxc
Verified in precise - I installed qemu-kvm in a precise container on a precise host (which had qemu-kvm installed, so the kernel module was loaded). Package installation succeeded, as does 'sudo stop qemu-kvm; sudo start qemu-kvm' ** Tags removed: verification-needed ** Tags added: verification-done -- 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/1078530 Title: upstart job fails to start under lxc To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu-kvm/+bug/1078530/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1095181] Re: terrible breakage on git rebase
Thanks for taking the time to report this bug. The README in etckeeper points out that etckeeper tracks file metadata that git otherwise ignores. Could you tell us exactly how what steps you are taking, i.e. how you are rebasing? Could you tell us which release you are on? ** Changed in: etckeeper (Ubuntu) Importance: Undecided = High ** Changed in: etckeeper (Ubuntu) Status: New = Incomplete -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to etckeeper in Ubuntu. https://bugs.launchpad.net/bugs/1095181 Title: terrible breakage on git rebase To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/etckeeper/+bug/1095181/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 941968] Re: lockfile-create hangs inside lxc containers (potential buffer overflow?)
** Changed in: lxc (Ubuntu) Status: Expired = Confirmed -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to ntp in Ubuntu. https://bugs.launchpad.net/bugs/941968 Title: lockfile-create hangs inside lxc containers (potential buffer overflow?) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/941968/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 941968] Re: lockfile-create hangs inside lxc containers (potential buffer overflow?)
Sebastian, I'm sorry, could you please give us more specifically the steps you took? What was that username for - is that the logged-in username on the host? is the environment the environment name in .juju/environments.yaml, and service the name of the charm you invoked? -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to ntp in Ubuntu. https://bugs.launchpad.net/bugs/941968 Title: lockfile-create hangs inside lxc containers (potential buffer overflow?) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/941968/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 589063] Re: Windows Server 2008 won't boot with more than 4 vCPUs
The problem may have been that ubuntu-sru was unsubscribed. I've resubscribed it to the bug, hopefully the upload will be accepted soon. -- 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/589063 Title: Windows Server 2008 won't boot with more than 4 vCPUs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu-kvm/+bug/589063/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 997978] Re: KVM images lose connectivity with bridged network
@BenKochie, could you please file a new bug with details? -- 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/997978 Title: KVM images lose connectivity with bridged network To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/997978/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1096771] Re: error 'No cgroup mounted on the system' but cgroup mounted
I can't reproduce this on 12.10. could you do sudo lxc-start -n containername -l info -o outout then attach outout here? ** Changed in: lxc (Ubuntu) Status: New = Incomplete ** Changed in: lxc (Ubuntu) Importance: Undecided = High -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1096771 Title: error 'No cgroup mounted on the system' but cgroup mounted To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1096771/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1096125] Re: virsh create-snapshot fails
** Changed in: kvm (Ubuntu) Importance: Undecided = Medium -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to kvm in Ubuntu. https://bugs.launchpad.net/bugs/1096125 Title: virsh create-snapshot fails To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kvm/+bug/1096125/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1096125] Re: virsh create-snapshot fails
I don't believe this is due to apparmor. However there certainly is an apparmor bug, as running virsh snapshot-create-as causes the /etc/apparmor.d/libvirt/test1-uuid.files entry for /var/lib/libvirt/images/test1.img to be replaced by one for /var/lib/libvirt/images/test1.snapshot1 -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to kvm in Ubuntu. https://bugs.launchpad.net/bugs/1096125 Title: virsh create-snapshot fails To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kvm/+bug/1096125/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1096984] Re: Wrong device for the / mount point
*** This bug is a duplicate of bug 1060404 *** https://bugs.launchpad.net/bugs/1060404 Thanks for filing this bug. I believe the grub part of this bug is covered in bug 1060404 (which is not fixed in Precise). I don't believe the first part should be deemed a bug. lxc is not actually involved, and even without containers there is absolutely no guarantee that any results in 'mount' will be paths which are currently accessible to you. Moreover, note that if mount were returning a valid path (and grub succeeded in installing itself there) you would be destroying the grub install for the host :) Therefore grub-install simply needs to not run in the container. ** This bug has been marked a duplicate of bug 1060404 update-grub runs and fails in containers -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1096984 Title: Wrong device for the / mount point To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1096984/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1096771] Re: error 'No cgroup mounted on the system' but cgroup mounted
** Also affects: libcgroup (Ubuntu) Importance: Undecided Status: New ** Changed in: libcgroup (Ubuntu) Status: New = In Progress ** No longer affects: lxc (Ubuntu) ** Changed in: libcgroup (Ubuntu) Importance: Undecided = High ** Changed in: libcgroup (Ubuntu) Assignee: (unassigned) = Serge Hallyn (serge-hallyn) ** Summary changed: - error 'No cgroup mounted on the system' but cgroup mounted + cgroup-bin (deleted) init scripts stick around -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1096771 Title: cgroup-bin (deleted) init scripts stick around To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libcgroup/+bug/1096771/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1060404] Re: update-grub runs and fails in containers
** Description changed: - == - SRU justification for lxc part: - 1. Impact: update-grub fails, causing apt-get updates to fail if there is a new kernel. - 2. Development fix: modify ubuntu templates to mount devtmpfs before starting container - 3. Stable fix: same as development fix. - 4. Test case: - sudo lxc-create -t ubuntu-cloud -n q1 - sudo lxc-start q1 - # inside the container, run sudo update-grub - 5. Regression potential: This adds one more mount per container (by default, removable), taking up more memory. - == - If grub is installed in a container (as happens, for instance, with the ubuntu-cloud template) then an update of grub or linux-image will cause update-grub to be run. It tries, finds it can't access the root device, fails, and causes the update to fail. + [XXX edit - removed the SRU justification for lxc part. The proposed solution + was not safe, and was undone in a later commit. devtmpfs cannot be mounted + in a container, because changes under the container's /dev are then + reflected in the host's /dev. + + If grub is installed in a container (as happens, for instance, with the + ubuntu-cloud template) then an update of grub or linux-image will cause + update-grub to be run. It tries, finds it can't access the root device, + fails, and causes the update to fail. It would be better for update-grub to detect that it is in a container and simply exit 0, so that the apt-get can succeed. I'm attaching a debdiff which does that. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1060404 Title: update-grub runs and fails in containers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1060404/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1096771] Re: cgroup-bin (deleted) init scripts stick around
** Description changed: - $ sudo lxc-start -n lucid-test-lp -lDEBUG + === + SRU Justification + 1. Impact: cgroups can be wrongly set up, preventing lxc (and juju-lxc, etc) from working + 2. Development fix: properly remove the upstart jobs from older cgroup-bin. + 3. Stable fix: same as development fix + 4. Test case: install precise's libcgroup1 and cgroup-bin (quick to build from the precise source). check that /etc/cgred.conf exists. Install the new versions, and do 'apt-get install -f' to have cgroup-lite (a new dependency) be installed. Check for /etc/cgred.conf - with the fix, it should have been removed. + 5. Regression potential: there should be none. + === + $ sudo lxc-start -n lucid-test-lp -lDEBUG lxc-start: No cgroup mounted on the system lxc-start: failed to spawn 'lucid-test-lp' robertc@lifelessdesktop:~$ mount /dev/mapper/isw_bichcdfhcg_ARRAY0p6 on / type ext4 (rw,errors=remount-ro) proc on /proc type proc (rw,noexec,nosuid,nodev) sysfs on /sys type sysfs (rw,noexec,nosuid,nodev) none on /sys/fs/fuse/connections type fusectl (rw) none on /sys/kernel/debug type debugfs (rw) none on /sys/kernel/security type securityfs (rw) udev on /dev type devtmpfs (rw,mode=0755) devpts on /dev/pts type devpts (rw,noexec,nosuid,gid=5,mode=0620) tmpfs on /run type tmpfs (rw,noexec,nosuid,size=10%,mode=0755) none on /run/lock type tmpfs (rw,noexec,nosuid,nodev,size=5242880) none on /run/shm type tmpfs (rw,nosuid,nodev) none on /run/user type tmpfs (rw,noexec,nosuid,nodev,size=104857600,mode=0755) cgroup on /sys/fs/cgroup/cpuset type cgroup (rw,relatime,cpuset) cgroup on /sys/fs/cgroup/cpu type cgroup (rw,relatime,cpu) cgroup on /sys/fs/cgroup/cpuacct type cgroup (rw,relatime,cpuacct) cgroup on /sys/fs/cgroup/memory type cgroup (rw,relatime,memory) cgroup on /sys/fs/cgroup/devices type cgroup (rw,relatime,devices) cgroup on /sys/fs/cgroup/freezer type cgroup (rw,relatime,freezer) cgroup on /sys/fs/cgroup/blkio type cgroup (rw,relatime,blkio) cgroup on /sys/fs/cgroup/perf_event type cgroup (rw,relatime,perf_event) binfmt_misc on /proc/sys/fs/binfmt_misc type binfmt_misc (rw,noexec,nosuid,nodev) gvfsd-fuse on /run/user/robertc/gvfs type fuse.gvfsd-fuse (rw,nosuid,nodev,user=robertc) ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: lxc 0.8.0~rc1-4ubuntu39 ProcVersionSignature: Ubuntu 3.5.0-21.32-generic 3.5.7.1 Uname: Linux 3.5.0-21-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.6.1-0ubuntu9 Architecture: amd64 Date: Mon Jan 7 19:14:58 2013 MarkForUpload: True ProcEnviron: - LANGUAGE=en_NZ:en - TERM=screen - PATH=(custom, no user) - LANG=en_NZ.UTF-8 - SHELL=/bin/bash + LANGUAGE=en_NZ:en + TERM=screen + PATH=(custom, no user) + LANG=en_NZ.UTF-8 + SHELL=/bin/bash SourcePackage: lxc UpgradeStatus: Upgraded to quantal on 2012-10-30 (69 days ago) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to libcgroup in Ubuntu. https://bugs.launchpad.net/bugs/1096771 Title: cgroup-bin (deleted) init scripts stick around To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libcgroup/+bug/1096771/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1060404] Re: update-grub runs and fails in containers
@Andreas, it needs to be fixed in grub. However the fix in raring should be SRUable. ** Changed in: grub2 (Ubuntu Precise) Importance: Undecided = High ** No longer affects: upstart (Ubuntu) ** No longer affects: upstart (Ubuntu Precise) ** No longer affects: upstart (Ubuntu Quantal) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1060404 Title: update-grub runs and fails in containers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1060404/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1097312] [NEW] container startup must not fail if setup_kmsg fails
Public bug reported: setup_kmsg is a convenience to have container syslog messages (generated by userspace) directed at the console. However it fails the container must not fail to start. ** Affects: lxc (Ubuntu) Importance: Undecided Status: Fix Released ** Affects: lxc (Ubuntu Quantal) Importance: Medium Status: Triaged ** Also affects: lxc (Ubuntu Quantal) Importance: Undecided Status: New ** Changed in: lxc (Ubuntu) Status: New = Fix Released ** Changed in: lxc (Ubuntu Quantal) Status: New = Triaged ** Changed in: lxc (Ubuntu Quantal) Importance: Undecided = Medium -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1097312 Title: container startup must not fail if setup_kmsg fails To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1097312/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1097312] Re: container startup must not fail if setup_kmsg fails
(medium priority because this does not affect most regular lxc usage) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1097312 Title: container startup must not fail if setup_kmsg fails To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1097312/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1097312] Re: container startup must not fail if setup_kmsg fails
** Description changed: setup_kmsg is a convenience to have container syslog messages (generated by userspace) directed at the console. However it fails the container must not fail to start. + + + SRU Justification + Impact: certain containers will fail to start + Development fix: if /dev/kmsg could not be set up, don't fail container startup + Stable fix: same as development fix + Test case: + sudo lxc-create -t sshd -n ssh1 + sudo lxc-start -n ssh1 + Regression potential: containers can run fine without setup_kmsg() having run, so allowing container startup to proceed when setup_kmsg() fails should introduce no regression. + ** Changed in: lxc (Ubuntu Quantal) Status: Triaged = In Progress -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1097312 Title: container startup must not fail if setup_kmsg fails To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1097312/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1033727] Re: USB passthrough doesn't work anymore with qemu-kvm 1.1.1
@Peter Schaefer, (replying to comment #12) could you please follow up on comments #6 and #7? It also would be worthwhile, at this point, checking whether latest upstream (1.3) is still broken. -- 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/1033727 Title: USB passthrough doesn't work anymore with qemu-kvm 1.1.1 To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1033727/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1091579] Re: Networking when starting kvm in commandline
A fix for this is applied in the new qemu source tree (which has not yet been accepted from NEW into raring). ** Changed in: kvm (Ubuntu) Importance: High = Medium ** Changed in: kvm (Ubuntu) Status: Confirmed = Fix Committed -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to kvm in Ubuntu. https://bugs.launchpad.net/bugs/1091579 Title: Networking when starting kvm in commandline To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kvm/+bug/1091579/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 941968] Re: lockfile-create hangs inside lxc containers (potential buffer overflow?)
@Sebastian, what you are seeing is likely unrelated to this particular bug. However if I simply do something like: juju deploy --repository=~/myrepo local:precise/ovs-lxc lxc-5678901234567890123456789012345678901 and very quickly juju debug-log then I see: LXCError: lxc-start: node name '' is too long lxc-start: failed to read configuration file Traceback (most recent call last): Could you confirm whether that is what you also see? And if so, file it as a bug against lxc and juju? -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to ntp in Ubuntu. https://bugs.launchpad.net/bugs/941968 Title: lockfile-create hangs inside lxc containers (potential buffer overflow?) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lockfile-progs/+bug/941968/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 941968] Re: lockfile-create hangs inside lxc containers (potential buffer overflow?)
Never mind - simply doing sudo hostname host567890123456789012345678901234567890 sudo apt-get install lxc in precise reproduced this, giving me * Starting NTP server ntpd *** glibc detected *** lockfile-create: free(): invalid next size (fast): 0x00d750a0 *** -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to ntp in Ubuntu. https://bugs.launchpad.net/bugs/941968 Title: lockfile-create hangs inside lxc containers (potential buffer overflow?) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lockfile-progs/+bug/941968/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 941968] Re: lockfile-create hangs inside lxc containers (potential buffer overflow?)
@jamespage, do you still see this bug? ** Changed in: ntp (Ubuntu) Status: Expired = Confirmed ** Changed in: ntp (Ubuntu) Importance: Undecided = High -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to ntp in Ubuntu. https://bugs.launchpad.net/bugs/941968 Title: lockfile-create hangs inside lxc containers (potential buffer overflow?) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lockfile-progs/+bug/941968/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 941968] Re: lockfile-create hangs inside lxc containers (potential buffer overflow?)
Note I get the same thing in a kvm-based cloud instance. Marking this bug as not affecting lxc. ** No longer affects: lxc (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to ntp in Ubuntu. https://bugs.launchpad.net/bugs/941968 Title: lockfile-create hangs inside lxc containers (potential buffer overflow?) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lockfile-progs/+bug/941968/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 941968] Re: lockfile-create hangs inside lxc containers (potential buffer overflow?)
I have reproduced this on precise and raring. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to ntp in Ubuntu. https://bugs.launchpad.net/bugs/941968 Title: lockfile-create hangs inside lxc containers (potential buffer overflow?) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lockfile-progs/+bug/941968/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 941968] Re: lockfile-create hangs inside lxc containers (potential buffer overflow?)
** Also affects: lockfile-progs (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to ntp in Ubuntu. https://bugs.launchpad.net/bugs/941968 Title: lockfile-create hangs inside lxc containers (potential buffer overflow?) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lockfile-progs/+bug/941968/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 941968] Re: lockfile-create hangs inside lxc containers (potential buffer overflow?)
** No longer affects: lockfile-progs (Ubuntu) ** No longer affects: ntp (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to ntp in Ubuntu. https://bugs.launchpad.net/bugs/941968 Title: lockfile-create hangs inside lxc containers (potential buffer overflow?) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/liblockfile/+bug/941968/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1093661] Re: cgrulesengd fails to start
Actually libcgroup no longer ships the init scripts at all. The bug (recently reported and fixed, not yet SRUd to quantal) was that the init scripts were not being properly removed. From the NEWS file: libcgroup (0.38-1) unstable; urgency=low This version sees the removal of both initscripts cgconfig and cgred from the cgroup-bin package. This means that cgroups will not be mounted by default and no classification will occur during boot. There are numerous issues surrounding the boot-time classification including race conditions and collisions with lxc and libvirt. I may replace support for mounting available cgroups at boot time as time allows. This version provides a stable point from which to move forward. -- Jon Bernard jbern...@debian.org Mon, 18 Jun 2012 21:29:29 -0400 -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to libcgroup in Ubuntu. https://bugs.launchpad.net/bugs/1093661 Title: cgrulesengd fails to start To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libcgroup/+bug/1093661/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1093661] Re: cgrulesengd fails to start
@Jon, I'm not sure how you want to address this - if you consider this a valid bug (given that the rules engine is flawed and not starting it was by design) or not. I will mark it invalid, but please feel free to re-mark it valid if you prefer. If you'd like to get together for a catchup+design discussion, please ping me. ** Changed in: libcgroup (Ubuntu) Status: New = Invalid -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to libcgroup in Ubuntu. https://bugs.launchpad.net/bugs/1093661 Title: cgrulesengd fails to start To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libcgroup/+bug/1093661/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1094438] Re: Samba crashes invalid pointer: 0x00007f0bc3de7590
** Changed in: samba (Ubuntu) Importance: Undecided = High -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba in Ubuntu. https://bugs.launchpad.net/bugs/1094438 Title: Samba crashes invalid pointer: 0x7f0bc3de7590 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1094438/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1060404] Re: update-grub runs and fails in containers
@Henning, At one point we thought a workaround was to have devtmpfs mounted in the container. However that is a bad thing to do as changes in the container's /dev will be reflected in the host's /dev. So the only workaround right now (until grub is fixed in precise) is to check (with 'mount') which device / is mounted from in the container, and then create that device in the container. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1060404 Title: update-grub runs and fails in containers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1060404/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1097340] Re: package libapache2-mod-php5 5.3.10-1ubuntu3.4 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Thanks for reporting this bug. The missing file belongs to php5-common package, which is properly depended upon by libapache2-mod-php5. It would appear to have been manually deleted. You can cause it to be reinstalled by doing: sudo apt-get install --reinstall php5-common After this, you can do sudo apt-get install -f to complete the failed installation of libapache2-mod-php5. Please let us know if this does not solve your problem. ** Changed in: php5 (Ubuntu) Status: New = Invalid -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to php5 in Ubuntu. https://bugs.launchpad.net/bugs/1097340 Title: package libapache2-mod-php5 5.3.10-1ubuntu3.4 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/php5/+bug/1097340/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1094944] Re: squid3 remove doesn't delete logrotate conf file
Thanks for reporting this issue. The logrotate file is a conffile, and per debian policy is only removed when you purge the package. sudo apt-get purge squid3 ** Changed in: squid3 (Ubuntu) Status: New = Invalid -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to squid3 in Ubuntu. https://bugs.launchpad.net/bugs/1094944 Title: squid3 remove doesn't delete logrotate conf file To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/1094944/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1097652] Re: dhclient cause error message when calling samba hook
Thanks for submitting this bug. ** Changed in: samba (Ubuntu) Status: New = Confirmed ** Changed in: samba (Ubuntu) Importance: Undecided = Low -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba in Ubuntu. https://bugs.launchpad.net/bugs/1097652 Title: dhclient cause error message when calling samba hook To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1097652/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1085595] Re: glance could not be installed (dependency problem)
Thanks for reporting this bug. I couldn't reproduce this in either precise or raring. Since you say the solution was to remove /usr/local/bin/glance-*, the problem appears to have been caused by previous manual installations of glance - that is, not through the package. ** Changed in: glance (Ubuntu) Status: New = Invalid -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to glance in Ubuntu. https://bugs.launchpad.net/bugs/1085595 Title: glance could not be installed (dependency problem) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glance/+bug/1085595/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1092715] Re: udevadm trigger --action=change not working in quantal and raring
The cause of the problem is simply the udev-acl call in 70-udev- acl.rules. Since this is a higher # rule than 40-qemu-kvm.rules, it gets run after. The problem can be solved by: 1. moving 40-qemu-kvm.rules to 72-qemu-kvm.rules 2. making qemu-kvm depend on acl 3. appending RUN+=/usr/bin/setfacl -m g::rw /dev/kvm to 72-qemu-kvm.rules. ** No longer affects: linux (Ubuntu) ** Package changed: udev (Ubuntu) = qemu-kvm (Ubuntu) ** Also affects: qemu-kvm (Ubuntu Quantal) Importance: Undecided Status: New ** Also affects: qemu-kvm (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: qemu-kvm (Ubuntu Raring) Importance: High Status: Confirmed ** Changed in: qemu-kvm (Ubuntu Quantal) Status: New = Confirmed ** Changed in: qemu-kvm (Ubuntu Precise) Status: New = Confirmed ** Changed in: qemu-kvm (Ubuntu Quantal) Importance: Undecided = High ** Changed in: qemu-kvm (Ubuntu Precise) Importance: Undecided = High -- 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/1092715 Title: udevadm trigger --action=change not working in quantal and raring To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu-kvm/+bug/1092715/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1092715] Re: udevadm trigger --action=change not working in quantal and raring
Actually qemu-kvm.rules can stay at 40 by using :=, so the rules file becomes KERNEL==kvm, GROUP:=kvm, MODE:=0660, TAG:=, RUN:=/usr/bin/setfacl -m g::rw /dev/kvm -- 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/1092715 Title: udevadm trigger --action=change not working in quantal and raring To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu-kvm/+bug/1092715/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1092715] Re: udevadm trigger --action=change not working in quantal and raring
(replacing /dev/kvm with $env{DEVNAME} of course)
--
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/1092715
Title:
udevadm trigger --action=change not working in quantal and raring
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qemu-kvm/+bug/1092715/+subscriptions
--
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 764278] Re: interface name eth1 does not come back after lxc-stop
*** This bug is a duplicate of bug 1086244 *** https://bugs.launchpad.net/bugs/1086244 @Evan, please see bug 1086244. I suspect it's the one you want. The fix can be SRUd to precise as soon as it lands in raring with the 0.9 merge. ** This bug has been marked a duplicate of bug 1086244 'phys' interface does not come back after lxc-stop -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/764278 Title: interface name eth1 does not come back after lxc-stop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/764278/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 764278] Re: interface name eth1 does not come back after lxc-stop
*** This bug is a duplicate of bug 1086244 *** https://bugs.launchpad.net/bugs/1086244 (Obviously I was either misreading or just thinking wrongly when I said this was a kernel bug and fixed in comment #1) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/764278 Title: interface name eth1 does not come back after lxc-stop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/764278/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1099155] Re: [raring] No ip assigned to bridge and no routes added for routed network
Thanks, Roman. network-manager in precise would not have been a problem, but as of raring it tries to take control of virtual interfaces. This has also been confirmed by stgraber and myself in lxc. ** Changed in: network-manager (Ubuntu) Status: New = Confirmed ** Also affects: lxc (Ubuntu) Importance: Undecided Status: New ** Changed in: lxc (Ubuntu) Status: New = Confirmed ** Changed in: libvirt (Ubuntu) Status: New = Confirmed ** Changed in: libvirt (Ubuntu) Importance: Undecided = High ** Changed in: lxc (Ubuntu) Importance: Undecided = Critical ** Changed in: network-manager (Ubuntu) Importance: Undecided = Critical ** Changed in: libvirt (Ubuntu) Importance: High = Critical -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1099155 Title: [raring] No ip assigned to bridge and no routes added for routed network To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1099155/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Blueprint servercloud-r-lxc] LXC work for R
Blueprint changed by Serge Hallyn:
Work items changed:
Work items:
[serge-hallyn] Send user namespace delta to kernel-team ASAP: DONE
[serge-hallyn] Post syslog namespace design wiki page: DONE
[serge-hallyn] Send syslog namespace prototype to lkml: DONE
[serge-hallyn] Send syslog namespace description to kernel-team ASAP: DONE
[serge-hallyn] Add set_cgroup_item() and get_cgroup_item() to C API: DONE
[daniel-lezcano] Improved monitor notification support: TODO
[stgraber] Fix lxc-ls (re-write using api): DONE
[serge-hallyn] lxc-create or template option to specify userns mapping: TODO
[serge-hallyn] push user namespace lxc delta upstream: INPROGRESS
[serge-hallyn] add config options for loglevel and output file: DONE
[serge-hallyn] drop lxccontainer.log default logging in api: DONE
- [serge-hallyn] lxc-create - set a default log file in
/var/log/lxc/$container: TODO
+ [serge-hallyn] lxc-create - set a default log file in
/var/log/lxc/$container: DONE
[serge-hallyn] lxc.autodev: push lxc patch upstream: DONE
[serge-hallyn] lxc.autodev: push lxc patch into package: DONE
[serge-hallyn] lxc.autodev: push mountall patch into package: DONE
[serge-hallyn] list broken functionality in ubuntu container in user
namespace: TODO
[serge-hallyn] improve ubuntu container experience in user namespace: TODO
[serge-hallyn] add config option for RLIMIT_NPROC in userns container: TODO
[stgraber] add (not container) to upstart jobs which just fail: INPROGRESS
[stgraber] write tool to pass devices into container: DONE
[stgraber] create a separate package for templates: DONE
[stgraber] have lxc-create record the name of template used in container
config file for debugging: DONE
[stgraber] support templates outside of $templatedir (pushed to git): DONE
[stgraber] investigate what's needed to support containers outside of
/var/lib/lxc: INPROGRESS
[serge-hallyn] test apparmor profile stacking; implement any lxc changes
needed to support it: BLOCKED
[stgraber] rebase staging branch on upstream master: DONE
[serge-hallyn] test attach support in userns kernel; shout if anything
missing: DONE
[daniel-lezcano] investigate/use http://lxc.sourceforge.net/download/procfs
to filter /proc/{cpuinfo,meminfo,etc}: TODO
[stgraber] investigate: does dnsmasq save mac-ip across host reboots? (it
does): DONE
[stgraber] Port arkose to python3 (and make it pep8 clean): DONE
[stgraber] Port arkose to python3-lxc: BLOCKED
[stgraber] Port auto-dist-upgrader to python3-lxc: DONE
[stgraber] Tweak the tests to ensure auto-dist-upgrader on LXC gives the same
results as on kvm: INPROGRESS
[stgraber] Check what it'd take to make lxc work fine when
creating/starting/stopping containers in parallel: TODO
[stgraber] Add code to detect and install langpacks in containers (at least
-base-en): DONE
[stgraber] Get LXC into main: INPROGRESS
[ebiederm] Push current userns patchset upstream: INPROGRESS
[ebiederm] Add support for tmpfs mounts in userns: TODO
--
LXC work for R
https://blueprints.launchpad.net/ubuntu/+spec/servercloud-r-lxc
--
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Blueprint servercloud-r-lxc] LXC work for R
Blueprint changed by Serge Hallyn:
Work items changed:
Work items:
[serge-hallyn] Send user namespace delta to kernel-team ASAP: DONE
[serge-hallyn] Post syslog namespace design wiki page: DONE
[serge-hallyn] Send syslog namespace prototype to lkml: DONE
[serge-hallyn] Send syslog namespace description to kernel-team ASAP: DONE
[serge-hallyn] Add set_cgroup_item() and get_cgroup_item() to C API: DONE
[daniel-lezcano] Improved monitor notification support: TODO
[stgraber] Fix lxc-ls (re-write using api): DONE
[serge-hallyn] lxc-create or template option to specify userns mapping: TODO
[serge-hallyn] push user namespace lxc delta upstream: INPROGRESS
[serge-hallyn] add config options for loglevel and output file: DONE
[serge-hallyn] drop lxccontainer.log default logging in api: DONE
[serge-hallyn] lxc-create - set a default log file in
/var/log/lxc/$container: DONE
[serge-hallyn] lxc.autodev: push lxc patch upstream: DONE
[serge-hallyn] lxc.autodev: push lxc patch into package: DONE
[serge-hallyn] lxc.autodev: push mountall patch into package: DONE
[serge-hallyn] list broken functionality in ubuntu container in user
namespace: TODO
[serge-hallyn] improve ubuntu container experience in user namespace: TODO
[serge-hallyn] add config option for RLIMIT_NPROC in userns container: TODO
[stgraber] add (not container) to upstart jobs which just fail: INPROGRESS
[stgraber] write tool to pass devices into container: DONE
[stgraber] create a separate package for templates: DONE
[stgraber] have lxc-create record the name of template used in container
config file for debugging: DONE
[stgraber] support templates outside of $templatedir (pushed to git): DONE
[stgraber] investigate what's needed to support containers outside of
/var/lib/lxc: INPROGRESS
[serge-hallyn] test apparmor profile stacking; implement any lxc changes
needed to support it: BLOCKED
[stgraber] rebase staging branch on upstream master: DONE
[serge-hallyn] test attach support in userns kernel; shout if anything
missing: DONE
[daniel-lezcano] investigate/use http://lxc.sourceforge.net/download/procfs
to filter /proc/{cpuinfo,meminfo,etc}: TODO
[stgraber] investigate: does dnsmasq save mac-ip across host reboots? (it
does): DONE
[stgraber] Port arkose to python3 (and make it pep8 clean): DONE
[stgraber] Port arkose to python3-lxc: BLOCKED
[stgraber] Port auto-dist-upgrader to python3-lxc: DONE
[stgraber] Tweak the tests to ensure auto-dist-upgrader on LXC gives the same
results as on kvm: INPROGRESS
[stgraber] Check what it'd take to make lxc work fine when
creating/starting/stopping containers in parallel: TODO
[stgraber] Add code to detect and install langpacks in containers (at least
-base-en): DONE
[stgraber] Get LXC into main: INPROGRESS
- [ebiederm] Push current userns patchset upstream: INPROGRESS
+ [ebiederm] Push current userns patchset upstream: DONE
[ebiederm] Add support for tmpfs mounts in userns: TODO
--
LXC work for R
https://blueprints.launchpad.net/ubuntu/+spec/servercloud-r-lxc
--
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Blueprint servercloud-r-lxc] LXC work for R
Blueprint changed by Serge Hallyn:
Work items changed:
Work items:
[serge-hallyn] Send user namespace delta to kernel-team ASAP: DONE
[serge-hallyn] Post syslog namespace design wiki page: DONE
[serge-hallyn] Send syslog namespace prototype to lkml: DONE
[serge-hallyn] Send syslog namespace description to kernel-team ASAP: DONE
[serge-hallyn] Add set_cgroup_item() and get_cgroup_item() to C API: DONE
[daniel-lezcano] Improved monitor notification support: TODO
[stgraber] Fix lxc-ls (re-write using api): DONE
[serge-hallyn] lxc-create or template option to specify userns mapping: TODO
- [serge-hallyn] push user namespace lxc delta upstream: INPROGRESS
+ [serge-hallyn] push user namespace lxc delta upstream: DONE
[serge-hallyn] add config options for loglevel and output file: DONE
[serge-hallyn] drop lxccontainer.log default logging in api: DONE
[serge-hallyn] lxc-create - set a default log file in
/var/log/lxc/$container: DONE
[serge-hallyn] lxc.autodev: push lxc patch upstream: DONE
[serge-hallyn] lxc.autodev: push lxc patch into package: DONE
[serge-hallyn] lxc.autodev: push mountall patch into package: DONE
[serge-hallyn] list broken functionality in ubuntu container in user
namespace: TODO
[serge-hallyn] improve ubuntu container experience in user namespace: TODO
[serge-hallyn] add config option for RLIMIT_NPROC in userns container: TODO
[stgraber] add (not container) to upstart jobs which just fail: INPROGRESS
[stgraber] write tool to pass devices into container: DONE
[stgraber] create a separate package for templates: DONE
[stgraber] have lxc-create record the name of template used in container
config file for debugging: DONE
[stgraber] support templates outside of $templatedir (pushed to git): DONE
[stgraber] investigate what's needed to support containers outside of
/var/lib/lxc: INPROGRESS
[serge-hallyn] test apparmor profile stacking; implement any lxc changes
needed to support it: BLOCKED
[stgraber] rebase staging branch on upstream master: DONE
[serge-hallyn] test attach support in userns kernel; shout if anything
missing: DONE
[daniel-lezcano] investigate/use http://lxc.sourceforge.net/download/procfs
to filter /proc/{cpuinfo,meminfo,etc}: TODO
[stgraber] investigate: does dnsmasq save mac-ip across host reboots? (it
does): DONE
[stgraber] Port arkose to python3 (and make it pep8 clean): DONE
[stgraber] Port arkose to python3-lxc: BLOCKED
[stgraber] Port auto-dist-upgrader to python3-lxc: DONE
[stgraber] Tweak the tests to ensure auto-dist-upgrader on LXC gives the same
results as on kvm: INPROGRESS
[stgraber] Check what it'd take to make lxc work fine when
creating/starting/stopping containers in parallel: TODO
[stgraber] Add code to detect and install langpacks in containers (at least
-base-en): DONE
[stgraber] Get LXC into main: INPROGRESS
[ebiederm] Push current userns patchset upstream: DONE
[ebiederm] Add support for tmpfs mounts in userns: TODO
--
LXC work for R
https://blueprints.launchpad.net/ubuntu/+spec/servercloud-r-lxc
--
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Blueprint servercloud-r-libvirt] Libvirt work for R
Blueprint changed by Serge Hallyn: Work items changed: Work items: [serge-hallyn] Have virbr0 not be set to autostart if it's network is in use: DONE [stefan-bader-canonical] watch for libxl patches for xen 4.2: TODO [mdeslaur] make sure OVMF support in virt-manager is sufficient to easily test secureboot and non-secureboot UEFI boots: TODO [serge-hallyn] Simplify hugepages exploitation in libirt-qemu (LP: #1001584): DONE - [serge-hallyn] Blog on using hugepages with kvm and libvirt: TODO -- Libvirt work for R https://blueprints.launchpad.net/ubuntu/+spec/servercloud-r-libvirt -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Blueprint servercloud-r-libvirt] Libvirt work for R
Blueprint changed by Serge Hallyn: Whiteboard changed: User Stories: Risks: Test Plans: The qrt libvirt testsuite is to be run before every package upload. Release Note: - * Libvirt can now be used to launch and test UEFI based VMS. - * Libvirt-qemu can now be set up in one step to use hugepages for improved performance. + * Libvirt can now be used to launch and test UEFI based VMS. + * Libvirt-qemu can now be set up in one step to use hugepages for improved performance. + + Notes: + * transparent hugepages are available in 1.3, so no setup is needed for use of hugepages. Therefore blog is canceled. -- Libvirt work for R https://blueprints.launchpad.net/ubuntu/+spec/servercloud-r-libvirt -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Blueprint servercloud-r-qemu] QEMU plans for R
Blueprint changed by Serge Hallyn: Whiteboard changed: User Stories: N/A Risks: None Test Plans: The qrt qemu tests are to be run before every upload. Release Note: + 1. The qemu and qemu-kvm sources have been merged. Some of the kvm command line usage therefore has changed. For instance, '-enable-kvm' must be specified rather than being implied. (List of changes to come here) + 2. Transparent hugepages are now supported. The performance gains of hugepages in kvm will be automatically realized when available. -- QEMU plans for R https://blueprints.launchpad.net/ubuntu/+spec/servercloud-r-qemu -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Blueprint servercloud-r-qemu] QEMU plans for R
Blueprint changed by Serge Hallyn: Work items changed: Work items: [serge-hallyn] push for fix for LP: #217427: TODO [serge-hallyn] merge qemu-linaro patches into qemu source: DONE [serge-hallyn] drop vde2 and spice from build-deps: DONE - [serge-hallyn] build candidate qemu to replace qemu-linaro and qemu-kvm: INPROGRESS + [serge-hallyn] build candidate qemu to replace qemu-linaro and qemu-kvm: DONE [pmaydell] test candidate qemu with arm: BLOCKED [serge-hallyn] build separate qemu-kvm-spice source pkg in universe: TODO [serge-hallyn] MIR qemu-user-static etc: TODO - [serge-hallyn] merge upstream 1.3: BLOCKED + [serge-hallyn] merge upstream 1.3: INPROGRESS [stefan-bader-canonical] review gridcentric patches: DONE [sarnold] do a security review of gridcentric patches: TODO - [serge-hallyn] merge gridcentric patches into qemu source: BLOCKED + [serge-hallyn] merge gridcentric patches into qemu source: DONE [ivoks] (or was it louis-bouchard?) test vhost-net for reliability and performance: TODO [serge-hallyn] switch vhost-net to enabled-by-default if deemed safe: BLOCKED -- QEMU plans for R https://blueprints.launchpad.net/ubuntu/+spec/servercloud-r-qemu -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1060404] Re: update-grub runs and fails in containers
Confirmed in precise, thanks. ** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1060404 Title: update-grub runs and fails in containers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1060404/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1100843] Re: Live Migration Causes Performance Issues
Thanks, that is very interesting. I'll be pushing qemu 1.3.0 to ubuntu raring hopefully tomorrow - it would be interesting to know if this still happens there. ** Changed in: qemu-kvm (Ubuntu) Importance: Undecided = Medium ** Changed in: qemu-kvm (Ubuntu) Status: Confirmed = Triaged -- 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/1100843 Title: Live Migration Causes Performance Issues To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu-kvm/+bug/1100843/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1100877] Re: lxc-start fails after upgrade to raring
Thanks for reporting this bug. At first I thought it was a dup of 1099155, but if that were the case then lxcbr0 would exist, it simply would not have an address. Could you please show the results of ifconfig -a brctl show ls -l /var/log/upstart/lxc* cat /etc/default/lxc cat /etc/init/lxc-net.conf ** Changed in: lxc (Ubuntu) Importance: Undecided = High ** Changed in: lxc (Ubuntu) Status: New = Incomplete -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1100877 Title: lxc-start fails after upgrade to raring To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1100877/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1100857] Re: Init script does not support status command
Thanks for reporting this bug and proposing a patch. I notice that in
raring, a shorter patch was used to implement status. Does the
following patch work for you in precise?
--- debian/backuppc.init2013-01-17 20:20:25.0 +
+++ /home/ubuntu/backuppc-3.2.1/debian/backuppc.init2013-01-17
20:19:36.0 +
@@ -81,11 +81,8 @@ case $1 in
--signal 1
log_end_msg $?
;;
- status)
-status_of_proc $BINDIR/$DAEMON $NAME exit 0 || exit $?
-;;
*)
-log_success_msg Usage: /etc/init.d/$NAME
{start|stop|restart|reload|status}
+log_success_msg Usage: /etc/init.d/$NAME {start|stop|restart|reload}
exit 1
;;
esac
** Changed in: backuppc (Ubuntu)
Importance: Undecided = Low
** Changed in: backuppc (Ubuntu)
Status: New = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to backuppc in Ubuntu.
https://bugs.launchpad.net/bugs/1100857
Title:
Init script does not support status command
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/backuppc/+bug/1100857/+subscriptions
--
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1099947] Re: driver unable to connect to CyberPower UPS using usbhid-ups driver
Marking confirmed based on the fedora report. THe Makefile.am in raring still shows: ./scripts/udev/Makefile.am: udevrules_DATA += 52-nut-usbups.rules ./scripts/udev/Makefile.am: udevrules_DATA += 52-nut-ipmipsu.rules so I doubt it has been fixed there. ** Changed in: nut (Ubuntu) Importance: Undecided = High ** Changed in: nut (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nut in Ubuntu. https://bugs.launchpad.net/bugs/1099947 Title: driver unable to connect to CyberPower UPS using usbhid-ups driver To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nut/+bug/1099947/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1100936] Re: init script cannot find java7 from oracle
Marking confirmed since the init scripts don't look for anything but openjdks. Though since they do so quite explicitly, it seems not impossible that there might be known problems with running tomcat with java-x-oracle. ** Changed in: tomcat6 (Ubuntu) Importance: Undecided = Medium ** Changed in: tomcat7 (Ubuntu) Importance: Undecided = Medium -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to tomcat6 in Ubuntu. https://bugs.launchpad.net/bugs/1100936 Title: init script cannot find java7 from oracle To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tomcat6/+bug/1100936/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1100936] Re: init script cannot find java7 from oracle
** Changed in: tomcat6 (Ubuntu) Status: New = Confirmed ** Changed in: tomcat7 (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to tomcat6 in Ubuntu. https://bugs.launchpad.net/bugs/1100936 Title: init script cannot find java7 from oracle To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tomcat6/+bug/1100936/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1099875] Re: multipathd ignores dev_loss_tmo and fast_io_fail_tmo settings
Thanks for reporting this bug. You say that multipathd -kshow config shows the changes you want, could you please show the full output of it? In addition to the output of 'multipath -v4' ? -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to multipath-tools in Ubuntu. https://bugs.launchpad.net/bugs/1099875 Title: multipathd ignores dev_loss_tmo and fast_io_fail_tmo settings To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1099875/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1099875] Re: multipathd ignores dev_loss_tmo and fast_io_fail_tmo settings
(marking incomplete pending response from bug submitter - please feel free to re-set to New when attaching the information) ** Changed in: multipath-tools (Ubuntu) Importance: Undecided = High ** Changed in: multipath-tools (Ubuntu) Status: New = Incomplete -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to multipath-tools in Ubuntu. https://bugs.launchpad.net/bugs/1099875 Title: multipathd ignores dev_loss_tmo and fast_io_fail_tmo settings To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1099875/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1097312] Re: container startup must not fail if setup_kmsg fails
verified on quantal. ** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1097312 Title: container startup must not fail if setup_kmsg fails To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1097312/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1100877] Re: lxc-start fails after upgrade to raring
*** This bug is a duplicate of bug 1099155 *** https://bugs.launchpad.net/bugs/1099155 Thanks for the info - could you show the contents of /var/log/upstart /lxc-net.log? -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1100877 Title: lxc-start fails after upgrade to raring To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1100877/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1100877] Re: lxc-start fails after upgrade to raring
** This bug has been marked a duplicate of bug 1099155 [raring] No ip assigned to bridge and no routes added for virtual networks -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1100877 Title: lxc-start fails after upgrade to raring To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1100877/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1100877] Re: lxc-start fails after upgrade to raring
** This bug is no longer a duplicate of bug 1099155 [raring] No ip assigned to bridge and no routes added for virtual networks -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1100877 Title: lxc-start fails after upgrade to raring To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1100877/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1084000] Re: libcap2: List of capabilities not in sync with the linux kernel
** No longer affects: lxc (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1084000 Title: libcap2: List of capabilities not in sync with the linux kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libcap2/+bug/1084000/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1084178] Re: auto.net does not handle mutliple mount points from a remote
Managed to reproduce this on raring. ** Changed in: autofs (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to autofs in Ubuntu. https://bugs.launchpad.net/bugs/1084178 Title: auto.net does not handle mutliple mount points from a remote To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/autofs/+bug/1084178/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1084178] Re: auto.net does not handle mutliple mount points from a remote
This turns out to not be a bug, but a misconfiguration. Your /etc/exports specifies 'fsid=0' for both exports. You don't have to specify an fsid, but if you do, it takes the place of the default uuid which nfsd would use to identify the filesystems. In other words, you told the server that both are the same. ** Changed in: autofs (Ubuntu) Status: Confirmed = Invalid -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to autofs in Ubuntu. https://bugs.launchpad.net/bugs/1084178 Title: auto.net does not handle mutliple mount points from a remote To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/autofs/+bug/1084178/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1096771] Re: cgroup-bin (deleted) init scripts stick around
Verified on quantal-proposed. ** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to libcgroup in Ubuntu. https://bugs.launchpad.net/bugs/1096771 Title: cgroup-bin (deleted) init scripts stick around To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libcgroup/+bug/1096771/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1103385] Re: Raring crashes on 12.04 LTS host with cirrus @800x600
Thanks for reporting this bug. Marking medium priority - not high because there is a workaround and it's a non-default condition, and not low because you can crash before doing the workaround. ** Changed in: qemu-kvm (Ubuntu) Importance: Undecided = Medium ** Changed in: qemu-kvm (Ubuntu) Status: New = Confirmed -- 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/1103385 Title: Raring crashes on 12.04 LTS host with cirrus @800x600 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu-kvm/+bug/1103385/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1103089] Re: package mysql-server-5.5 5.5.29-0ubuntu0.12.04.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Thanks for reporting this error. The syslog shows that mysql is trying to read /etc/my.cnf. This is a nonstandard location, and one which the apparmor profile by default denies. You'll need to update /etc/apaprmor.d/local/usr.sbin.mysqld to grant this permission, or move the configuration file into /etc/mysql/ ** Changed in: mysql-5.5 (Ubuntu) Status: New = Invalid -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to mysql-5.5 in Ubuntu. https://bugs.launchpad.net/bugs/1103089 Title: package mysql-server-5.5 5.5.29-0ubuntu0.12.04.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-5.5/+bug/1103089/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1102971] Re: package mysql-server-5.5 5.5.28-0ubuntu0.12.04.3 failed to install/upgrade: 설치한 post-installation 스크립트 하위 프로세스가 오류 1번을 리턴했습니다
Thanks for reporting this error. The DpkgTerminalLog.txt shows that the upgrade failed because the file /etc/apparmor.d/abstractions/mysql has been removed. That file is required. Please grab a new copy by doing sudo apt-get install --reinstall apparmor dpkg -x /var/cache/apt/archives/apparmor_*.deb x sudo cp x/etc/apparmor.d/abstractions/mysql /etc/apparmor.d/abstractions/ Then re-try your upgrade. If that does not work or you need more help, please rrespond to this mail. ** Changed in: mysql-5.5 (Ubuntu) Status: New = Invalid -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to mysql-5.5 in Ubuntu. https://bugs.launchpad.net/bugs/1102971 Title: package mysql-server-5.5 5.5.28-0ubuntu0.12.04.3 failed to install/upgrade: 설치한 post-installation 스크립트 하위 프로세스가 오류 1번을 리턴했습니다 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-5.5/+bug/1102971/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1102196] Re: Segfault on startup
*** This bug is a duplicate of bug 941968 *** https://bugs.launchpad.net/bugs/941968 Thanks for reporting this bug. It is a result of a lock in liblockfile. I will mark this bug a dup of bug 941968. I've also bumped the priority of that bug to high to hopefully get the proposed patch to fix it reviewed faster. ** This bug has been marked a duplicate of bug 941968 lockfile-create hangs inside lxc containers (potential buffer overflow?) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to ntp in Ubuntu. https://bugs.launchpad.net/bugs/1102196 Title: Segfault on startup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1102196/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
Re: [Bug 1103683] [NEW] Merge libvirt 1.0.1 from Debian experimental
Quoting Xiao-Long Chen (chillermillerl...@hotmail.com): Public bug reported: Would it be possible to merge libvirt 1.0.1 from Debian experimental? no, but 1.0.1 merged from upstream was just pushed to raring. The 1.0.1 release fixes a few issues, such as setting up a NAT network on a remote libvirt system. A few of the apparmor patches are accepted upstream as well as a few other patches. Also, the Debian package enables the vbox backend. Note that libvirt *no longer* requires VirtualBox to be installed to build the vbox backend (this was something that was mentioned in an old bug report). If this is something you'd specifically want to see, then absolutely please open a new box asking for vbox to be enabled, pointing out that vbox won't need to be in build-deps. That sounds like we can do it. Thanks! ** Changed in: libvirt (Ubuntu) Status: New = Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to libvirt in Ubuntu. https://bugs.launchpad.net/bugs/1103683 Title: Merge libvirt 1.0.1 from Debian experimental To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1103683/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1100787] Re: Samba 3.6.3 segfault or panic.
** Changed in: samba (Ubuntu) Importance: Undecided = High -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba in Ubuntu. https://bugs.launchpad.net/bugs/1100787 Title: Samba 3.6.3 segfault or panic. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1100787/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1092715] Re: udevadm trigger --action=change not working in quantal and raring
I prefer to fix this bit through bug 1103022. May mark this one invalid. It has been further obfuscated by the presence of an apparent inotify bug stopping udev from seeing updates on some systems. -- 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/1092715 Title: udevadm trigger --action=change not working in quantal and raring To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu-kvm/+bug/1092715/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Blueprint servercloud-r-qemu] QEMU plans for R
Blueprint changed by Serge Hallyn: Work items changed: Work items: [serge-hallyn] push for fix for LP: #217427: TODO [serge-hallyn] merge qemu-linaro patches into qemu source: DONE [serge-hallyn] drop vde2 and spice from build-deps: DONE [serge-hallyn] build candidate qemu to replace qemu-linaro and qemu-kvm: DONE [pmaydell] test candidate qemu with arm: BLOCKED [serge-hallyn] build separate qemu-kvm-spice source pkg in universe: TODO - [serge-hallyn] MIR qemu-user-static etc: TODO [serge-hallyn] merge upstream 1.3: INPROGRESS [stefan-bader-canonical] review gridcentric patches: DONE [sarnold] do a security review of gridcentric patches: TODO [serge-hallyn] merge gridcentric patches into qemu source: DONE [ivoks] (or was it louis-bouchard?) test vhost-net for reliability and performance: TODO [serge-hallyn] switch vhost-net to enabled-by-default if deemed safe: BLOCKED -- QEMU plans for R https://blueprints.launchpad.net/ubuntu/+spec/servercloud-r-qemu -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Blueprint servercloud-r-qemu] QEMU plans for R
Blueprint changed by Serge Hallyn:
Whiteboard changed:
User Stories:
N/A
Risks:
None
Test Plans:
The qrt qemu tests are to be run before every upload.
Release Note:
1. The qemu and qemu-kvm sources have been merged. Some of the kvm command
line usage therefore has changed. For instance, '-enable-kvm' must be
specified rather than being implied. (List of changes to come here)
2. Transparent hugepages are now supported. The performance gains of
hugepages in kvm will be automatically realized when available.
+
+ Notes:
+
+ The {qemu-kvm,qemu-linaro}-qemu switch does not require MIR'ing the
+ binary packages which migrated from qemu-linaro. We can look at that,
+ but it's low priority unless someone (independently) requires qemu-user
+ etc in main. The work item was in case somehow it was required for this
+ switch. As it is not, I dropped the WI.
--
QEMU plans for R
https://blueprints.launchpad.net/ubuntu/+spec/servercloud-r-qemu
--
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1103385] Re: Raring crashes on 12.04 LTS host with cirrus @800x600
*** This bug is a duplicate of bug 1039647 *** https://bugs.launchpad.net/bugs/1039647 ** This bug has been marked a duplicate of bug 1039647 KVM/cirrus desktop fails to start -- 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/1103385 Title: Raring crashes on 12.04 LTS host with cirrus @800x600 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu-kvm/+bug/1103385/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1054129] Re: reboot with -vga cirrus can result in broken output
There are other open bugs for qemu+cirrus, so I will close this one for qemu to mirror the linux status. ** No longer affects: qemu-kvm (Ubuntu Quantal) ** No longer affects: qemu-kvm (Ubuntu) -- 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/1054129 Title: reboot with -vga cirrus can result in broken output To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1054129/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Blueprint servercloud-r-binfmtns] Namespace for binfmt?
Blueprint changed by Serge Hallyn: Whiteboard changed: User Stories: Aboo installs qemu-user-static:i386 on his amd64 host. He is now unable to execute any amd64 elf binaries including sync and poweroff. Risks: Upstream (kernel) rejects the idea. Test Plans: * Install - * qemu-user-static:i386 on amd64 host - * qemu-user-static:amd64 in i386 userspace on amd64 kernel + * qemu-user-static:i386 on amd64 host + * qemu-user-static:amd64 in i386 userspace on amd64 kernel * Run full ltp, qemu, libvirt, and lxc testsuites on any proposed kernel change. Release Note: + + Notes: related bug: http://pad.lv/427863 -- Namespace for binfmt? https://blueprints.launchpad.net/ubuntu/+spec/servercloud-r-binfmtns -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Blueprint servercloud-r-binfmtns] Namespace for binfmt?
Blueprint changed by Serge Hallyn: Work items changed: Work items: [cjwatson] write a formal userspace rationale for binfmt namespace: TODO [stefan-bader-canonical] (or serge-hallyn) consider querying about a -o newinstance mount option to binfmt_misc filesystem (problem is how toI tie that to task doing exec): TODO [serge-hallyn] talk to stefan-bader-canonical about possible ns implementation: TODO [stefan-bader-canonical] consider implementing binfmt namespace: TODO - [serge-hallyn] add check to qemu-user-static postinst to not install 32/64 cross handlers: TODO -- Namespace for binfmt? https://blueprints.launchpad.net/ubuntu/+spec/servercloud-r-binfmtns -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Blueprint servercloud-r-binfmtns] Namespace for binfmt?
Blueprint changed by Serge Hallyn: Whiteboard changed: User Stories: Aboo installs qemu-user-static:i386 on his amd64 host. He is now unable to execute any amd64 elf binaries including sync and poweroff. Risks: Upstream (kernel) rejects the idea. Test Plans: * Install * qemu-user-static:i386 on amd64 host * qemu-user-static:amd64 in i386 userspace on amd64 kernel * Run full ltp, qemu, libvirt, and lxc testsuites on any proposed kernel change. Release Note: - Notes: related bug: http://pad.lv/427863 + Notes: + * related bug: http://pad.lv/427863 + * I don't seem able to make qemu-user-static in a i386 chroot on amd64 + hot break the host in raring. (in precise i can). Therefore I removed the + work item for adding a check for that condition to qemu-user-static.postinst. -- Namespace for binfmt? https://blueprints.launchpad.net/ubuntu/+spec/servercloud-r-binfmtns -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 787091] Re: Unable to use USB device in KVM quest
** Package changed: qemu-kvm (Ubuntu) = libvirt (Ubuntu) -- 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/787091 Title: Unable to use USB device in KVM quest To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/787091/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 787091] Re: Unable to use USB device in KVM quest
@Daniele, I'm not sure what you are wanting to do. I suspect your best bet will be to go to askubuntu.com with details. I'm quite certain that this bug has been fixed for some time in libvirt, perhaps with http://www.redhat.com/archives/libvir- list/2010-November/msg6.html. I'm marking this Fix released. If anyone can reproduce this in raring please do re-open with detailed reproduction steps. ** Changed in: libvirt (Ubuntu) Status: Triaged = Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to libvirt in Ubuntu. https://bugs.launchpad.net/bugs/787091 Title: Unable to use USB device in KVM quest To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/787091/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1091579] Re: Networking when starting kvm in commandline
** Package changed: kvm (Ubuntu) = qemu (Ubuntu) ** Changed in: qemu (Ubuntu) Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to kvm in Ubuntu. https://bugs.launchpad.net/bugs/1091579 Title: Networking when starting kvm in commandline To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1091579/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1033727] Re: USB passthrough doesn't work anymore with qemu-kvm 1.1.1
** No longer affects: qemu-kvm (Ubuntu Raring) ** Changed in: qemu-kvm (Ubuntu Quantal) Assignee: (unassigned) = Serge Hallyn (serge-hallyn) ** No longer affects: qemu (Ubuntu 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/bugs/1033727 Title: USB passthrough doesn't work anymore with qemu-kvm 1.1.1 To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1033727/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1089402] Re: qemu-utils installs dangling symlink in precise
** Changed in: qemu-kvm (Ubuntu Precise) Assignee: (unassigned) = Serge Hallyn (serge-hallyn) -- 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/1089402 Title: qemu-utils installs dangling symlink in precise To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu-kvm/+bug/1089402/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
