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
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:
(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
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 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
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.
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
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
@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'.
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
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
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
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:
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
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
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,
** 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
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:
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:
** 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
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
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.
@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
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
** 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
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
*** 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
)
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
** 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
** 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
@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)
--
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
(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
** 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
+
@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
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
@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 ''
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
@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.
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
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?)
** 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
** 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
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
@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
** 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
@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')
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
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
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.
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
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
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.
(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
*** 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
*** 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,
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
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
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
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
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
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
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
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
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
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
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
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.init
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)
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: 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
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
(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
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
*** 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
** 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
** 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
** 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
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
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
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
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)
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
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
*** 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
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
** 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
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
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
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
*** 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
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
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
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
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
** 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
@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
** 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:
** 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
** 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
1 - 100 of 6024 matches
Mail list logo
