Thanks for the report.
We're working hard on autoregistration for Lucid. We'll take a look at
this problem as soon as the Lucid autoregistration code is ready for
some exercise.
** Changed in: eucalyptus (Ubuntu)
Importance: Undecided = High
--
Lucid: walrus not automatically discovered
** Changed in: eucalyptus (Ubuntu)
Importance: Undecided = Medium
--
arch parameter is not passed by the image proxy during image install from store
https://bugs.launchpad.net/bugs/494084
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to
Excellent, thanks, Roland.
We can carry that patch in Ubuntu.
To get it upstream, you're going to need to submit it to the qemu-devel
mailing list. Anthony isn't able to take patches submitted through
Launchpad, unfortunately...
--
KVM crashes when -vga is set to vmware.
** Changed in: qemu-kvm (Ubuntu)
Status: Confirmed = Triaged
** Changed in: qemu
Status: Confirmed = Triaged
** Changed in: qemu-kvm (Ubuntu)
Assignee: (unassigned) = Dustin Kirkland (kirkland)
--
KVM crashes when -vga is set to vmware.
https://bugs.launchpad.net/bugs/414885
** Summary changed:
- /usr/sbin/ietadm needs to be added to wrappers.conf
+ eucalyptus 1.6.2 should not depend on ietadm, iscsitarget
--
eucalyptus 1.6.2 should not depend on ietadm, iscsitarget
https://bugs.launchpad.net/bugs/497196
You received this bug notification because you are a member
** Changed in: eucalyptus (Ubuntu)
Importance: Medium = High
--
eucalyptus 1.6.2 should not depend on ietadm, iscsitarget
https://bugs.launchpad.net/bugs/497196
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to eucalyptus in ubuntu.
--
Off-topic, but yes, I'm trying to package qemu-kvm-0.12 right now.
There are a number of blocking issues with the release, though.
--
KVM crashes when -vga is set to vmware.
https://bugs.launchpad.net/bugs/414885
You received this bug notification because you are a member of Ubuntu
Server Team,
Strike this request, per:
On Wed, 2009-12-16 at 12:45 +, Matt Zimmerman wrote:
On Wed, Dec 16, 2009 at 06:39:41AM -0600, Dustin Kirkland wrote:
This brings up a related point. I have written the MIR for aoetools
(per the work-item Matt assigned me). I have confirmed that aoetools
** Changed in: eucalyptus (Ubuntu)
Status: Triaged = Fix Committed
--
eucalyptus-nc needs an upstart job
https://bugs.launchpad.net/bugs/438631
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to eucalyptus in ubuntu.
--
** Changed in: eucalyptus
Status: New = Fix Committed
--
euca-describe-images does not show kernel and ramdisk for an image
https://bugs.launchpad.net/bugs/439366
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to euca2ools in ubuntu.
Public bug reported:
ietadm is in /usr/sbin/ietadm, which is not in the eucalyptus user's
default PATH.
This is causing the following errors in /var/log/eucalyptus/cloud-error.log:
com.eucalyptus.util.EucalyptusCloudException: ietadm not found: Is iscsitarget
installed?
at
Hmm, actually, it doesn't look like there's any ~eucalyptus/.bashrc at
all. This seems like a bad thing, no?
--
ietadm not in the eucalyptus user's path
https://bugs.launchpad.net/bugs/497196
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed
Rather, since it's euca_rootwrapped, it need an entry in
/etc/eucalyptus/euca_rootwrap.
** Summary changed:
- ietadm not in the eucalyptus user's path
+ /usr/sbin/ietadm needs to be added to wrappers.conf
--
/usr/sbin/ietadm needs to be added to wrappers.conf
** Changed in: eucalyptus (Ubuntu)
Status: New = Confirmed
** Also affects: eucalyptus
Importance: Undecided
Status: New
** Changed in: eucalyptus
Status: New = Confirmed
** Changed in: eucalyptus
Importance: Undecided = Wishlist
--
Redundancy for cloud and cluster
Thanks for following up.
I can confirm that the qemu-kvm build that produces this binary most
certainly does enable kvm by default. (The same binary, if built from
qemu alone will not, however that's not what we're using in ubuntu).
** Changed in: libvirt (Ubuntu)
Status: New = Invalid
** Changed in: eucalyptus (Ubuntu)
Assignee: (unassigned) = Dustin Kirkland (kirkland)
** Changed in: eucalyptus (Ubuntu)
Status: Triaged = In Progress
--
eucalyptus-common maintainer script should not add dpkg statoverrides
https://bugs.launchpad.net/bugs/437012
You received
** Changed in: eucalyptus (Ubuntu)
Status: In Progress = Fix Committed
--
eucalyptus-common maintainer script should not add dpkg statoverrides
https://bugs.launchpad.net/bugs/437012
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to
(Ubuntu)
Importance: Medium
Status: Triaged
** Affects: eucalyptus (Ubuntu)
Importance: Medium
Assignee: Dustin Kirkland (kirkland)
Status: Triaged
** Also affects: aoetools (Ubuntu)
Importance: Undecided
Status: New
** Changed in: eucalyptus (Ubuntu
** Summary changed:
- eucalyptus-nc should depend on aoetools to support EBS
+ MIR: aoetools
--
MIR: aoetools
https://bugs.launchpad.net/bugs/496780
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to eucalyptus in ubuntu.
--
** Changed in: testdrive
Status: New = Invalid
** Also affects: mysql-dfsg-5.1 (Ubuntu)
Importance: Undecided
Status: New
--
Server install with LAMP asks three times for MySQL password
https://bugs.launchpad.net/bugs/495213
You received this bug notification because you are a
Thierry-
Can you verify this package?
We need other fixes associated with this update here onsite at a
partner.
--
User data is not parsed correctly by Eucalyptus in some cases
https://bugs.launchpad.net/bugs/461156
You received this bug notification because you are a member of Ubuntu
Server
Thierry-
Can you verify this package?
We need other fixes associated with this update here onsite at a
partner.
--
memory leak; rampart_context not freed (memory leaked per connection)
https://bugs.launchpad.net/bugs/460085
You received this bug notification because you are a member of Ubuntu
Thanks, Colin. I do think this is fixed too.
** Changed in: kvm (Ubuntu)
Status: Incomplete = Fix Released
--
requires -cpu qemu32 on i386 host to boot karmic PAE kernels
https://bugs.launchpad.net/bugs/393671
You received this bug notification because you are a member of Ubuntu
Server
Martin-
I have tested the packages in -proposed according to the instructions
above.
They solve the problem as described in the bug, and do not cause
regressions in my experience. I think you can mark this one
verification-done.
Thanks.
--
eucalyptus CLEAN=1 should also be supported in start
** Changed in: eucalyptus (Ubuntu)
Assignee: (unassigned) = Dustin Kirkland (kirkland)
--
eucalyptus CLEAN=1 should also be supported in start
https://bugs.launchpad.net/bugs/491254
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed
Thierry-
I'm somewhat happy you could confirm the non-determinism, though it
means that we really need to get this fixed.
I also agree with your analysis of the supported CLEAN=1 states. I
saw your other bug filed and assigned it to myself.
--
eucalyptus-cc init script doesn't always clear
** Also affects: eucalyptus (Ubuntu Karmic)
Importance: Undecided
Status: New
** Also affects: eucalyptus (Ubuntu Lucid)
Importance: Wishlist
Assignee: Dustin Kirkland (kirkland)
Status: Triaged
** Changed in: eucalyptus (Ubuntu Karmic)
Status: New = In Progress
** Changed in: eucalyptus (Ubuntu Karmic)
Status: Triaged = In Progress
** Changed in: eucalyptus (Ubuntu Lucid)
Status: Triaged = In Progress
** Changed in: eucalyptus (Ubuntu Karmic)
Importance: Medium = High
** Changed in: eucalyptus (Ubuntu Lucid)
Importance: Medium =
*** This bug is a duplicate of bug 491254 ***
https://bugs.launchpad.net/bugs/491254
** This bug has been marked a duplicate of bug 491254
eucalyptus CLEAN=1 should also be supported in start
--
eucalyptus-cc init script doesn't always clear /var/lib/eucalyptus/CC
** Changed in: eucalyptus (Ubuntu Karmic)
Status: In Progress = Fix Committed
--
User data is not parsed correctly by Eucalyptus in some cases
https://bugs.launchpad.net/bugs/461156
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to
Dan/Thierry-
I just uploaded a package to karmic-proposed containing the eucalyptus
r946 fix.
Could one of you guys help draft the SRU testing notes and put that into
the bug description? Thanks.
** Changed in: eucalyptus (Ubuntu Karmic)
Status: Triaged = Fix Committed
--
memory leak;
** Description changed:
CLEAN=1 support has been implemented as part of bug 460089, to avoid
cleaning up the CC network state at each restart. A CLEAN=1 option was
added to the post-stop in eucalyptus-cc.conf. A similar option should be
added to the pre-start so that CLEAN=1 is also
Dan Nurmi indicated that the carried patch could be eliminated, and
instead generated at build time if some axis2 (??) package were in main
instead of universe, and eucalyptus could build-depend on it, rather
than the eucalyptus package maintainer installing this universe package
on his local
** Changed in: eucalyptus (Ubuntu)
Status: Triaged = In Progress
** Changed in: eucalyptus (Ubuntu)
Assignee: (unassigned) = Dustin Kirkland (kirkland)
--
Query string authentication does not work in some cases
https://bugs.launchpad.net/bugs/46
You received this bug
** Changed in: eucalyptus (Ubuntu)
Status: Triaged = In Progress
--
Describe Regions returns an invalid response
https://bugs.launchpad.net/bugs/482249
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to eucalyptus in ubuntu.
--
** Changed in: eucalyptus (Ubuntu)
Status: Incomplete = In Progress
** Changed in: eucalyptus (Ubuntu)
Assignee: (unassigned) = Dustin Kirkland (kirkland)
--
Eucalyptus does not allow api connection over https
https://bugs.launchpad.net/bugs/480783
You received this bug notification
** Also affects: eucalyptus (Ubuntu)
Importance: Undecided
Status: New
** Changed in: eucalyptus (Ubuntu)
Status: New = In Progress
** Changed in: eucalyptus (Ubuntu)
Importance: Undecided = Low
** Changed in: eucalyptus (Ubuntu)
Assignee: (unassigned) = Dustin Kirkland
** Also affects: eucalyptus (Ubuntu)
Importance: Undecided
Status: New
** Changed in: eucalyptus (Ubuntu)
Status: New = In Progress
** Changed in: eucalyptus (Ubuntu)
Importance: Undecided = Low
** Changed in: eucalyptus (Ubuntu)
Assignee: (unassigned) = Dustin Kirkland
** Changed in: eucalyptus (Ubuntu)
Assignee: (unassigned) = Dustin Kirkland (kirkland)
--
Describe Regions returns an invalid response
https://bugs.launchpad.net/bugs/482249
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to eucalyptus
** Also affects: eucalyptus (Ubuntu)
Importance: Undecided
Status: New
** Changed in: eucalyptus (Ubuntu)
Status: New = In Progress
** Changed in: eucalyptus (Ubuntu)
Importance: Undecided = High
** Changed in: eucalyptus (Ubuntu)
Assignee: (unassigned) = Dustin
** Changed in: eucalyptus (Ubuntu)
Status: Confirmed = In Progress
** Changed in: eucalyptus (Ubuntu)
Assignee: (unassigned) = Dustin Kirkland (kirkland)
--
Multiple concurrent snapshots on the same volume do not work reliably
https://bugs.launchpad.net/bugs/461394
You received
** Changed in: eucalyptus (Ubuntu)
Assignee: Thierry Carrez (ttx) = Dustin Kirkland (kirkland)
--
User data is not parsed correctly by Eucalyptus in some cases
https://bugs.launchpad.net/bugs/461156
You received this bug notification because you are a member of Ubuntu
Server Team, which
** Changed in: rampart (Ubuntu)
Status: Triaged = In Progress
** Changed in: rampart (Ubuntu)
Status: In Progress = Triaged
** Changed in: rampart (Ubuntu)
Assignee: Thierry Carrez (ttx) = Dustin Kirkland (kirkland)
** Changed in: rampart (Ubuntu)
Assignee: Dustin
** Also affects: eucalyptus (Ubuntu)
Importance: Undecided
Status: New
** Changed in: eucalyptus (Ubuntu)
Status: New = In Progress
** Changed in: eucalyptus (Ubuntu)
Importance: Undecided = Low
** Changed in: eucalyptus (Ubuntu)
Assignee: (unassigned) = Dustin Kirkland
** Also affects: eucalyptus (Ubuntu)
Importance: Undecided
Status: New
** Changed in: eucalyptus (Ubuntu)
Status: New = In Progress
** Changed in: eucalyptus (Ubuntu)
Importance: Undecided = Low
** Changed in: eucalyptus (Ubuntu)
Assignee: (unassigned) = Dustin Kirkland
** Also affects: eucalyptus (Ubuntu)
Importance: Undecided
Status: New
** Changed in: eucalyptus (Ubuntu)
Status: New = In Progress
** Changed in: eucalyptus (Ubuntu)
Assignee: (unassigned) = Dustin Kirkland (kirkland)
** Changed in: eucalyptus (Ubuntu)
Importance
** Also affects: eucalyptus (Ubuntu)
Importance: Undecided
Status: New
** Changed in: eucalyptus (Ubuntu)
Status: New = In Progress
** Changed in: eucalyptus (Ubuntu)
Assignee: (unassigned) = Dustin Kirkland (kirkland)
** Changed in: eucalyptus (Ubuntu)
Importance
There seems to be some non-determinism, here.
I can confirm that sometimes when I pass CLEAN=1, it is cleared, and
sometimes it's not.
This needs to be fixed.
--
eucalyptus-cc init script doesn't always clear /var/lib/eucalyptus/CC
https://bugs.launchpad.net/bugs/490382
You received this bug
Okay, I can now confirm that this works well in the karmic-proposed
package.
My testing was affected by a different bug that I will file now and fix
in another SRU.
Martin, you can mark this verification-done and push to -updates.
:-Dustin
--
[regression] euca_rootwrap fixes affected
don't take affect because the CC
state isn't cleared.
** Affects: eucalyptus (Ubuntu)
Importance: Medium
Assignee: Dustin Kirkland (kirkland)
Status: Triaged
** Affects: eucalyptus (Ubuntu Lucid)
Importance: Medium
Assignee: Dustin Kirkland (kirkland)
Status
Public bug reported:
Filing this bug on Kees' behalf, for tracking purposes...
On Fri, 2009-11-13 at 22:22 -0800, Kees Cook wrote:
Hi,
My --no-reverse option is upstream[1] now, so you should be able to use
avahi-publish in newer avahi versions to publish an A record without
the potentially
(nurmi)
Status: Confirmed
** Affects: eucalyptus (Ubuntu)
Importance: High
Assignee: Dustin Kirkland (kirkland)
Status: Triaged
** Changed in: eucalyptus (Ubuntu)
Status: New = Triaged
** Changed in: eucalyptus (Ubuntu)
Importance: Undecided = High
** Summary changed:
- eucalyptus.conf is confusing and underdocumented
+ eucalyptus.conf, euca_conf is confusing and underdocumented
** Changed in: eucalyptus (Ubuntu)
Assignee: (unassigned) = Dustin Kirkland (kirkland)
** Changed in: eucalyptus
Status: New = Confirmed
Public bug reported:
Scripts change it.
The sysadmin can customize it.
Package upgrades are messy.
We need a cleaner method of configuration inheritance/override.
** Affects: eucalyptus (Ubuntu)
Importance: High
Assignee: Dustin Kirkland (kirkland)
Status: Triaged
** Changed in: eucalyptus (Ubuntu)
Importance: Wishlist = High
** Changed in: eucalyptus (Ubuntu)
Assignee: (unassigned) = Dustin Kirkland (kirkland)
** Changed in: eucalyptus (Ubuntu)
Milestone: None = lucid-alpha-2
** Changed in: eucalyptus (Ubuntu)
Assignee: Dustin Kirkland
Public bug reported:
It would be very nice if Eucalyptus could optionally use a database
other than the self-contained hsql.
Perhaps postgres, or mysql.
This is a wishlist bug, just listed here for the sake of completeness,
and/or discussion.
Per UDS-Dallas, the gobby notes stated:
* Move
Thanks Chris.
This is 'wishlist' priority, fwiw. Just a would be nice to have...
--
support databases other than hsqldb by default
https://bugs.launchpad.net/bugs/487280
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to eucalyptus in
I have both virtualbox-ose and qemu-kvm installed on my Karmic system.
When I want to run virtualbox, I first run:
$ sudo service qemu-kvm stop
which unloads the kvm module, and then I can run virtualbox.
--
module blacklisting not respected
https://bugs.launchpad.net/bugs/484807
You received
Cool, thanks for the followup, Nick!
** Changed in: eucalyptus
Status: New = Invalid
** Changed in: eucalyptus (Ubuntu)
Status: Confirmed = Invalid
--
karmic netboot UEC install fails at registering nodes
https://bugs.launchpad.net/bugs/480125
You received this bug notification
It is a security issue, but does not need to be private. Changing that
now...
** Visibility changed to: Public
--
Eucalyptus does not allow api connection over https
https://bugs.launchpad.net/bugs/480783
You received this bug notification because you are a member of Ubuntu
Server Team, which
I'll convert it into a Question, since this stems from a
misunderstanding of the behavior of qemu and its -boot option, now
explained clearly by Anthony.
** Changed in: qemu-kvm (Ubuntu)
Status: Incomplete = New
--
Fails to boot from CD after reboot: CDROM boot failure code: 0003
** Changed in: qemu-kvm (Ubuntu)
Status: New = Invalid
--
Fails to boot from CD after reboot: CDROM boot failure code: 0003
https://bugs.launchpad.net/bugs/348633
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu-kvm in ubuntu.
Thierry/Scott-
Are there proposed fixes for this issue, at this point?
--
User data is not parsed correctly by Eucalyptus in some cases
https://bugs.launchpad.net/bugs/461156
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to eucalyptus in
Okay, I fixed this in a .2 upload.
Debdiff against the .1 version in karmic-proposed attached for SRU
team's review.
I verified that avahi-daemon.conf actually lands in the eucalyptus-cc deb, and
gets installed to:
-rw-r--r-- root/root 620 2009-11-10 14:00
that?
** Changed in: kvm (Ubuntu)
Status: Triaged = Incomplete
** Changed in: kvm (Ubuntu)
Assignee: Dustin Kirkland (kirkland) = (unassigned)
--
kvm: use PulseAudio instead of ALSA
https://bugs.launchpad.net/bugs/393430
You received this bug notification because you are a member
** Changed in: eucalyptus (Ubuntu)
Assignee: Dustin Kirkland (kirkland) = Mathias Gug (mathiaz)
--
the CC is returning incorrect networkIndex values on describeInstances
https://bugs.launchpad.net/bugs/454405
You received this bug notification because you are a member of Ubuntu
Server Team
Matt, Evan-
From the kvm(1) manpage, I think the option you want is:
# boot from CD-ROM first, switch back to default order after reboot
-boot once=d
Can you give that a try and see if that gives you the behavior you
expect?
I tested here with a real, working disk image, and a live ISO.
nentis-
Thanks for retesting.
I'm employed by Canonical to do this sort of work, and therefore won't
accept your bounty ;-)
Though I appreciate the gesture.
:-Dustin
--
kvm-84: virtio on qcow2 broken (regression)
https://bugs.launchpad.net/bugs/404394
You received this bug notification
I, too, tested raw images as well, and saw no problems.
--
kvm-84: virtio on qcow2 broken (regression)
https://bugs.launchpad.net/bugs/404394
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to kvm in ubuntu.
--
Ubuntu-server-bugs mailing
Yes, Mathias.
We're interested in changes in behavior between 12.3 and 12.4.
--
kvm-84: virtio on qcow2 broken (regression)
https://bugs.launchpad.net/bugs/404394
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to kvm in ubuntu.
--
Hmm, okay. It just makes my testing take a little longer than I would
like.
I suppose 300 is a realistic minimum. I'll convert this bug to a
question.
** Changed in: eucalyptus
Status: Confirmed = Invalid
** Changed in: eucalyptus (Ubuntu)
Status: Confirmed = Invalid
**
** Changed in: linux (Ubuntu)
Status: Confirmed = Invalid
--
Certain VMs do not run under KVM using karmic's kernel
https://bugs.launchpad.net/bugs/379991
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu-kvm in ubuntu.
--
** Changed in: kvm (Ubuntu Jaunty)
Status: Triaged = In Progress
--
qcow2 corruption regression
https://bugs.launchpad.net/bugs/404394
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to kvm in ubuntu.
--
Ubuntu-server-bugs mailing
I have confirmed the issue as described by Nathan on kvm in Jaunty.
I have also confirmed that this problem does *not* exist in Karmic.
:-Dustin
--
qcow2 corruption regression
https://bugs.launchpad.net/bugs/404394
You received this bug notification because you are a member of Ubuntu
Server
The problem I see in the guest with the ubuntu12.3 version looks like
the attached screenshot.
--
qcow2 corruption regression
https://bugs.launchpad.net/bugs/404394
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to kvm in ubuntu.
--
** Attachment added: Screenshot-QEMU.png
http://launchpadlibrarian.net/35106346/Screenshot-QEMU.png
--
qcow2 corruption regression
https://bugs.launchpad.net/bugs/404394
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to kvm in ubuntu.
Okay, this problem is caused by the upstream git commit that we cherry picked:
qcow2-corruption-Fix-alloc_cluster_link_l2-Kevin-W.patch
641636d19e3d8eeb8fac31e20641eaf33befd6e7
It was fixed upstream by
Fix-cluster-freeing-in-qcow2.patch
d4d698f020e50333d6eae48ce323752613b5c3ea
We need to
Attaching a patch against the hardy-backports version of kvm-84, which
is also affected.
** Also affects: kvm (Ubuntu Karmic)
Importance: Undecided
Status: New
** Changed in: kvm (Ubuntu Karmic)
Status: New = Fix Released
** Also affects: kvm (Ubuntu Hardy)
Importance:
Attaching a patch against the intrepid-backports version of kvm-84,
which is also affected.
** Attachment added: intrepid-backport-404394.debdiff
http://launchpadlibrarian.net/35112054/intrepid-backport-404394.debdiff
--
qcow2 corruption regression
https://bugs.launchpad.net/bugs/404394
You
: Undecided = High
** Changed in: kvm (Ubuntu Karmic)
Assignee: (unassigned) = Dustin Kirkland (kirkland)
** Changed in: kvm (Ubuntu Intrepid)
Assignee: (unassigned) = Dustin Kirkland (kirkland)
** Changed in: kvm (Ubuntu Jaunty)
Assignee: (unassigned) = Dustin Kirkland (kirkland
Uploaded to:
* jaunty-proposed
* intrepid-backports
* hardy-backports
Awaiting archive approval. Please test this ASAP.
** Changed in: kvm (Ubuntu Hardy)
Assignee: (unassigned) = Dustin Kirkland (kirkland)
--
qcow2 corruption regression
https://bugs.launchpad.net/bugs/404394
You
** Summary changed:
- qcow2 corruption regression
+ kvm-84: virtio on qcow2 broken (regression)
--
kvm-84: virtio on qcow2 broken (regression)
https://bugs.launchpad.net/bugs/404394
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to kvm in
** Changed in: kvm (Ubuntu Jaunty)
Status: In Progress = Fix Committed
** Changed in: kvm (Ubuntu Hardy)
Status: In Progress = Fix Committed
** Changed in: kvm (Ubuntu Intrepid)
Status: In Progress = Fix Committed
--
kvm-84: virtio on qcow2 broken (regression)
** Description changed:
cluster/handlers.c: euca_rootwrap rework did not whitelist powerwake;
however, powerwake does *not* need root privs, drop euca_rootwrap
wrapper.
===
SRU Verification
This fix is bundled with a set of unrelated SRU fixes for Eucalyptus.
To
** Description changed:
cluster/handlers.c: euca_rootwrap rework did not whitelist powerwake;
however, powerwake does *not* need root privs, drop euca_rootwrap
wrapper.
+
+ ===
+ SRU Verification
+
+ This fix is bundled with a set of unrelated SRU fixes for Eucalyptus.
+
+ To
I tested the package in Mathias's PPA.
It seems to work well.
However, I had to reboot the system to get the loglevel changes to take
effect. I need to research a little more closely exactly which upstart
jobs need to be restarted
** Description changed:
eucalyptus 1.6~bzr931-0ubuntu7, UEC
I've tested the package in Mathias' ppa. The functionality related to
this bug seems to work well.
--
[regression] euca_rootwrap fixes affected eucalyptus power management
(powerwake)
https://bugs.launchpad.net/bugs/458163
You received this bug notification because you are a member of Ubuntu
Public bug reported:
/etc/eucalyptus/eucalyptus.conf says:
...
# Powersave options. POWER_IDLETHRESH is the number of seconds that a
# node can remain idle (i.e. no running VMs) before a powerdown is
# attempted. POWER_WAKETHRESH is the number of seconds that
# Eucalyptus should wait after
** Description changed:
When accessing https://cloud ip:8443/ the title of the redesigned
page is still Eucalyptus where is should say Ubuntu Enterprise
Cloud.
- =
- SRU verification
+ ==
+ SRU Verification
+ 1) Point your browser at your UEC frontend:
+ *
No, there is no kqemu in Karmic.
Upstream qemu has abandoned support for kqemu, as it's unmaintained and
breaks kvm support.
** Changed in: qemu-kvm (Ubuntu)
Status: New = Won't Fix
--
Some options are not avaible in qemu
https://bugs.launchpad.net/bugs/424765
You received this bug
** Changed in: qemu-kvm (Ubuntu)
Status: Incomplete = Fix Released
** Changed in: qemu
Status: Incomplete = Fix Released
--
qemu-kvm 0.11.0-0ubuntu5, virtualized proxy, useless
https://bugs.launchpad.net/bugs/452712
You received this bug notification because you are a member of
So the attached patch would allow the package to upgrade/install. I'm
attaching it here in case this is what we need.
However, I think that we would just be hiding a problem under the rug.
As part of libvirt's package installation procedure, it needs to create
the libvirtd group, and add any
Thanks, Martin.
--
kvm disabled in bios (was: Unable to start EUC instances - no supported
architecture for os type 'hvm')
https://bugs.launchpad.net/bugs/452323
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu-kvm in ubuntu.
--
You can install qemu-kvm on a system without KVM. You will be running
with qemu emulation.
** Summary changed:
- Some options are not avaible in qemu
+ kqemu not available in karmic
** Changed in: qemu-kvm (Ubuntu)
Status: New = Won't Fix
--
kqemu not available in karmic
I just added a new task, triaged/high against hardy's linux kernel.
The Hardy linux kernel uses a backport of 2.6.25's virtio-net
implementation that causes this bug.
This virtio-net driver needs to be fixed such that hardy vm guests using
virtio-net doesn't truncate packets and crash
Okay, well, I'm going to add a task against the adduser package.
Perhaps the adduser package should handle this more gracefully.
Colin, any opinion?
** Also affects: adduser (Ubuntu)
Importance: Undecided
Status: New
** Changed in: adduser (Ubuntu)
Importance: Undecided = Low
**
I'm seeing this quite a bit now in my UEC. I'm suggesting that we
should probably identify a fix and roll it out in an SRU.
Thierry, if you disagree, feel free to close it won't-fix again.
:-Dustin
** Changed in: eucalyptus (Ubuntu Karmic)
Milestone: None = karmic-updates
** Changed in:
Joe,
Can you test 0.11.0-0ubuntu6.3 now in karmic-proposed?
:-Dustin
--
kvm disabled in bios (was: Unable to start EUC instances - no supported
architecture for os type 'hvm')
https://bugs.launchpad.net/bugs/452323
You received this bug notification because you are a member of Ubuntu
Server
Martin, I've tested the package in karmic-proposed. Verifying this one
is *very* easy. I would appreciate it if someone else would try the
instructions in the description.
:-Dustin
** Description changed:
Binary package hint: qemu-kvm
qemu-kvm has the ability to boot off of a remote,
FWIW, I tested the new /usr/bin/kvm-ok and it seems to work well.
Hopefully Joe can run his little barrage of tests and confirm the new
behavior as provided in the updated package.
:-Dustin
--
kvm disabled in bios (was: Unable to start EUC instances - no supported
architecture for os type
1201 - 1300 of 2030 matches
Mail list logo
