the patch required a small patch to eucalyptus that initializes axis2c
in the CC for each NC client connection (most already were handled this
way, except to StartNetwork/RunInstances).
in r946
--
memory leak; rampart_context not freed (memory leaked per connection)
** Attachment added: rampartc-1.3.0-euca.patch
http://launchpadlibrarian.net/34337608/rampartc-1.3.0-euca.patch
** Also affects: eucalyptus
Importance: Undecided
Status: New
** Also affects: eucalyptus (Ubuntu)
Importance: Undecided
Status: New
--
memory leak;
Public bug reported:
in the eucalyptus-cc upstart script, the line:
rm -f /var/lib/eucalyptus/CC/*
will always clear all CC state when the service is stopped. The
upstream init scripts use:
stop/start/restart
to control the service while maintaining CC state (stored in
Public bug reported:
It looks like the rampart_context structure is not freed after
processing (in rampart_in_handler.c), and in the rampart_context_free
function, the section for freeing the receiver_cert is commented out (in
rampart_token_processor.c). In our application (eucalyptus), this is
** Attachment added: rampartc-1.3.0-euca.patch
http://launchpadlibrarian.net/34337608/rampartc-1.3.0-euca.patch
** Also affects: eucalyptus
Importance: Undecided
Status: New
** Also affects: eucalyptus (Ubuntu)
Importance: Undecided
Status: New
--
memory leak;
Public bug reported:
in the eucalyptus-cc upstart script, the line:
rm -f /var/lib/eucalyptus/CC/*
will always clear all CC state when the service is stopped. The
upstream init scripts use:
stop/start/restart
to control the service while maintaining CC state (stored in
We (Eucalyptus team) have rolled new versions of the images that query
the meta-data service if it exists in preparation for the UEC release
(we've also added a 32 bit versions of each image :). The images are in
testing now, and will be released as soon as they are ready!
--
Non-ubuntu
We (Eucalyptus team) have rolled new versions of the images that query
the meta-data service if it exists in preparation for the UEC release
(we've also added a 32 bit versions of each image :). The images are in
testing now, and will be released as soon as they are ready!
--
Non-ubuntu
the java (cloud, walrus, sc) components' logging uses log4j. the
defaults can be found in source under:
clc/modules/core/src/main/resources/log4j.xml
where you'll find the following, which control the file size and the max
number of files of this size that can exist
param
the java (cloud, walrus, sc) components' logging uses log4j. the
defaults can be found in source under:
clc/modules/core/src/main/resources/log4j.xml
where you'll find the following, which control the file size and the max
number of files of this size that can exist
param
Public bug reported:
There are several helpful links under the new Eucalyptus UEC Theme
'Services' tab. Adding a section that contains information and links
back to Eucalyptus itself would be helpful to users looking for
Eucalyptus user forums, documentation, downloads, and other Eucalyptus
Public bug reported:
There are several helpful links under the new Eucalyptus UEC Theme
'Services' tab. Adding a section that contains information and links
back to Eucalyptus itself would be helpful to users looking for
Eucalyptus user forums, documentation, downloads, and other Eucalyptus
I looks like this bug happens when an authorize is called before the
group is used in another context (run-instances, describe-group, etc).
For example:
euca-authorize (fails)
euca-describe-groups
euca-authorize (success)
Attaching the log file showing exception, and exact commands
**
I looks like this bug happens when an authorize is called before the
group is used in another context (run-instances, describe-group, etc).
For example:
euca-authorize (fails)
euca-describe-groups
euca-authorize (success)
Attaching the log file showing exception, and exact commands
**
Public bug reported:
When trying to install a UEC node from the 20091017 .iso (amd64), the
installation fails during install of qemu-kvm due to a package conflict. Below
is a snippet of /var/log/syslog during the failure:
.
Oct 18 00:10:35 in-target: python-apt is already the newest
Public bug reported:
When trying to install a UEC node from the 20091017 .iso (amd64), the
installation fails during install of qemu-kvm due to a package conflict. Below
is a snippet of /var/log/syslog during the failure:
.
Oct 18 00:10:35 in-target: python-apt is already the newest
This branch contains a simple fix to change the admin UI version string
to '1.6', in order to help avoid confusion with users having prior
versions of eucalyptus (1.6-devel).
lp:~nurmi/eucalyptus/webuiversion
--
Eucalyptus version string is incorrect (currently 1.6-devel, should be 1.6)
This branch contains a simple fix to change the admin UI version string
to '1.6', in order to help avoid confusion with users having prior
versions of eucalyptus (1.6-devel).
lp:~nurmi/eucalyptus/webuiversion
--
Eucalyptus version string is incorrect (currently 1.6-devel, should be 1.6)
Public bug reported:
in the karmic package r931, the version string reported through the
admin UI and on the filesystem is set incorrectly (current=1.6-devel,
should be=1.6)
** Affects: eucalyptus (Ubuntu)
Importance: Undecided
Status: New
** Tags: eucalyptus
** Tags added:
Greetings,
We've analyzed the points in the source tree that are referenced, and
have found that none of them are actually exercised in a Karmic default
eucalyptus running system. More detail on each follows:
GLclient is a testing utility that doesn't get installed by the package (or a
'make
Public bug reported:
in the karmic package r931, the version string reported through the
admin UI and on the filesystem is set incorrectly (current=1.6-devel,
should be=1.6)
** Affects: eucalyptus (Ubuntu)
Importance: Undecided
Status: New
** Tags: eucalyptus
** Tags added:
Greetings,
We've analyzed the points in the source tree that are referenced, and
have found that none of them are actually exercised in a Karmic default
eucalyptus running system. More detail on each follows:
GLclient is a testing utility that doesn't get installed by the package (or a
'make
Niemeyer and I tracked down the issue, which ended up being that the
manifest set by the image store proxy for both the ERI and EMI was
identical.
--
Unable to start images installed/registered via the image store
https://bugs.launchpad.net/bugs/446841
You received this bug notification because
We will be adding the ability for the CC to accept ranges of IPs, using
only the last octet of the IPs, in a near commit of Eucalyptus. All
octets must obviously be between 0 and 255 inclusive. The following
will be accepted:
A.B.C.D-A.B.C.E
where D = E. Multiple ranges can be specified:
committed in eucalyptus revno 926
--
Eucalyptus Public IPs should be submitted in CIDR or range notation
https://bugs.launchpad.net/bugs/438565
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to eucalyptus in ubuntu.
--
Ubuntu-server-bugs
Niemeyer and I tracked down the issue, which ended up being that the
manifest set by the image store proxy for both the ERI and EMI was
identical.
--
Unable to start images installed/registered via the image store
https://bugs.launchpad.net/bugs/446841
You received this bug notification because
We will be adding the ability for the CC to accept ranges of IPs, using
only the last octet of the IPs, in a near commit of Eucalyptus. All
octets must obviously be between 0 and 255 inclusive. The following
will be accepted:
A.B.C.D-A.B.C.E
where D = E. Multiple ranges can be specified:
committed in eucalyptus revno 926
--
Eucalyptus Public IPs should be submitted in CIDR or range notation
https://bugs.launchpad.net/bugs/438565
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Fixed in revno 925
--
Assignment of IP 169.254.169.254 on CC is conflicting with UEC avahi publish
mechanism
https://bugs.launchpad.net/bugs/449143
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to eucalyptus in ubuntu.
--
** Changed in: eucalyptus/1.6
Status: In Progress = Fix Committed
** Changed in: eucalyptus
Status: In Progress = Fix Committed
--
Assignment of IP 169.254.169.254 on CC is conflicting with UEC avahi publish
mechanism
https://bugs.launchpad.net/bugs/449143
You received this bug
Fixed in revno 925
--
Assignment of IP 169.254.169.254 on CC is conflicting with UEC avahi publish
mechanism
https://bugs.launchpad.net/bugs/449143
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Fixed in r922
** Changed in: eucalyptus
Status: In Progress = Fix Committed
** Changed in: eucalyptus/1.6
Status: New = Fix Committed
--
In STATIC mode, the CC is reporting instance's public IP incorrectly (last
number is missing)
https://bugs.launchpad.net/bugs/447555
You
** Changed in: eucalyptus/1.6
Status: In Progress = Fix Committed
** Changed in: eucalyptus
Status: In Progress = Fix Committed
--
Assignment of IP 169.254.169.254 on CC is conflicting with UEC avahi publish
mechanism
https://bugs.launchpad.net/bugs/449143
You received this bug
Public bug reported:
There is a bug in client-marshal-adb.c that causes a segfault in the CC
when the number of running instances is high (sometimes). Fixed in
revno 924
** Affects: eucalyptus
Importance: High
Status: Fix Committed
** Affects: eucalyptus/1.6
Importance: High
globally scoped subnets to broadcast on?)
This fix is in testing now (Oct11/2009)
** Affects: eucalyptus
Importance: High
Assignee: Daniel Nurmi (nurmi)
Status: In Progress
** Affects: eucalyptus/1.6
Importance: High
Status: In Progress
** Affects: ubuntu
My experiments with hot-attaching virtio disks to eucalyptus VMs have
been partially successful. I've been able to attach/detach a virtio
disk to/from a VM once, but the second attach causes a kvm segfault
followed by a libvirtd segfault. Removing eucalyptus from the scenario,
this problem can
My experiments with hot-attaching virtio disks to eucalyptus VMs have
been partially successful. I've been able to attach/detach a virtio
disk to/from a VM once, but the second attach causes a kvm segfault
followed by a libvirtd segfault. Removing eucalyptus from the scenario,
this problem can
** Also affects: eucalyptus
Importance: Undecided
Status: New
** Changed in: eucalyptus
Importance: Undecided = High
--
Instances from large, fresh EMIs fail to start just after being registered
https://bugs.launchpad.net/bugs/439410
You received this bug notification because you
The problem is that the connection from the NC to Walrus is being
successfully opened, but is being timed out on the server side after two
minutes if no data is written to the wire (which is the case when the
large image is being decrypted/cached). We've increased the retry count
in the NC to 10
** Also affects: eucalyptus
Importance: Undecided
Status: New
** Changed in: eucalyptus
Importance: Undecided = High
--
Instances from large, fresh EMIs fail to start just after being registered
https://bugs.launchpad.net/bugs/439410
You received this bug notification because you
The problem is that the connection from the NC to Walrus is being
successfully opened, but is being timed out on the server side after two
minutes if no data is written to the wire (which is the case when the
large image is being decrypted/cached). We've increased the retry count
in the NC to 10
Functionally, the instance is getting the correct ip, but the reporting
is incorrect.
** Affects: eucalyptus
Importance: Medium
Assignee: Daniel Nurmi (nurmi)
Status: In Progress
** Affects: eucalyptus/1.6
Importance: Undecided
Status: New
** Affects: ubuntu
** Changed in: eucalyptus (Ubuntu Karmic)
Status: Triaged = In Progress
** Changed in: eucalyptus (Ubuntu Karmic)
Assignee: (unassigned) = Dustin Kirkland (kirkland)
--
over time, c3p0 causes deadlock condition in CLC (database borkage)
https://bugs.launchpad.net/bugs/436885
You
** Changed in: eucalyptus (Ubuntu Karmic)
Assignee: (unassigned) = Dustin Kirkland (kirkland)
** Changed in: eucalyptus (Ubuntu Karmic)
Status: Triaged = In Progress
--
if apache2 is using worker MPM, rampart causing periodic CC segfaults
https://bugs.launchpad.net/bugs/436407
You
** Changed in: eucalyptus (Ubuntu)
Assignee: (unassigned) = Dustin Kirkland (kirkland)
** Changed in: eucalyptus (Ubuntu)
Status: Triaged = In Progress
--
Part of storage controller setup that should run as the eucalyptus user runs as
root
https://bugs.launchpad.net/bugs/436276
You
** Changed in: eucalyptus (Ubuntu)
Status: Triaged = In Progress
** Changed in: eucalyptus (Ubuntu)
Assignee: (unassigned) = Dustin Kirkland (kirkland)
--
SYSTEM mode, instances do not run
https://bugs.launchpad.net/bugs/430957
You received this bug notification because you are a
** Changed in: eucalyptus (Ubuntu Karmic)
Assignee: (unassigned) = Dustin Kirkland (kirkland)
** Changed in: eucalyptus (Ubuntu Karmic)
Status: Triaged = In Progress
--
Eucalyptus restart is needed after autoregistration of components
https://bugs.launchpad.net/bugs/439251
You
** Changed in: eucalyptus (Ubuntu)
Status: Triaged = In Progress
** Changed in: eucalyptus (Ubuntu)
Assignee: (unassigned) = Dustin Kirkland (kirkland)
--
External command failure not handled correctly in some cases
https://bugs.launchpad.net/bugs/440744
You received this bug
** Changed in: eucalyptus (Ubuntu Karmic)
Status: Triaged = In Progress
** Changed in: eucalyptus (Ubuntu Karmic)
Assignee: (unassigned) = Dustin Kirkland (kirkland)
--
excessive number of CLC sockets to the backend cause the system to stop
updating state
** Changed in: eucalyptus (Ubuntu Karmic)
Assignee: (unassigned) = Dustin Kirkland (kirkland)
** Changed in: eucalyptus (Ubuntu Karmic)
Status: Triaged = In Progress
--
Eucalyptus restart is needed after autoregistration of components
https://bugs.launchpad.net/bugs/439251
You
** Changed in: eucalyptus (Ubuntu Karmic)
Status: Triaged = In Progress
** Changed in: eucalyptus (Ubuntu Karmic)
Assignee: (unassigned) = Dustin Kirkland (kirkland)
--
over time, c3p0 causes deadlock condition in CLC (database borkage)
https://bugs.launchpad.net/bugs/436885
You
** Changed in: eucalyptus (Ubuntu Karmic)
Assignee: (unassigned) = Dustin Kirkland (kirkland)
** Changed in: eucalyptus (Ubuntu Karmic)
Status: Triaged = In Progress
--
if apache2 is using worker MPM, rampart causing periodic CC segfaults
https://bugs.launchpad.net/bugs/436407
You
** Changed in: eucalyptus (Ubuntu)
Status: Triaged = In Progress
** Changed in: eucalyptus (Ubuntu)
Assignee: (unassigned) = Dustin Kirkland (kirkland)
--
SYSTEM mode, instances do not run
https://bugs.launchpad.net/bugs/430957
You received this bug notification because you are a
** Changed in: eucalyptus (Ubuntu Karmic)
Status: Triaged = In Progress
** Changed in: eucalyptus (Ubuntu Karmic)
Assignee: (unassigned) = Dustin Kirkland (kirkland)
--
excessive number of CLC sockets to the backend cause the system to stop
updating state
** Changed in: eucalyptus (Ubuntu)
Assignee: (unassigned) = Dustin Kirkland (kirkland)
** Changed in: eucalyptus (Ubuntu)
Status: Triaged = In Progress
--
Part of storage controller setup that should run as the eucalyptus user runs as
root
https://bugs.launchpad.net/bugs/436276
You
** Changed in: eucalyptus (Ubuntu)
Status: Triaged = In Progress
** Changed in: eucalyptus (Ubuntu)
Assignee: (unassigned) = Dustin Kirkland (kirkland)
--
External command failure not handled correctly in some cases
https://bugs.launchpad.net/bugs/440744
You received this bug
Is it possible that, at some point, a walrus registration was attempted
with 'localhost'? If so, you'll need to deregister walrus:
euca_conf --deregister-walrus
and try registering again with a valid public IP. This error is
implying that the system believes that a registered walrus lives on
Is it possible that, at some point, a walrus registration was attempted
with 'localhost'? If so, you'll need to deregister walrus:
euca_conf --deregister-walrus
and try registering again with a valid public IP. This error is
implying that the system believes that a registered walrus lives on
** Attachment added: libvirtd-issue.tgz
http://launchpadlibrarian.net/32683674/libvirtd-issue.tgz
** Also affects: eucalyptus (Ubuntu)
Importance: Undecided
Status: New
** Tags added: eucalyptus
--
libvirtd is leaking file descriptors to /var/log/libvirt/qemu/vmid.log
Public bug reported:
It looks like the libvirtd daemon is leaking file descriptors to the
logfile that it sets up for each VM. I've attached a typescript showing
the symptom (start vm, inspect lsof, stop vm, inspect lsof, start vm,
inspect lsof, stop vm, inspect lsof), note that the descriptors
** Attachment added: libvirtd-issue.tgz
http://launchpadlibrarian.net/32683674/libvirtd-issue.tgz
** Also affects: eucalyptus (Ubuntu)
Importance: Undecided
Status: New
** Tags added: eucalyptus
--
libvirtd is leaking file descriptors to /var/log/libvirt/qemu/vmid.log
Public bug reported:
It looks like the libvirtd daemon is leaking file descriptors to the
logfile that it sets up for each VM. I've attached a typescript showing
the symptom (start vm, inspect lsof, stop vm, inspect lsof, start vm,
inspect lsof, stop vm, inspect lsof), note that the descriptors
Public bug reported:
When installing a UEC node (from server iso 09272009.1), I'm finding
that the bridge device that is defined in /etc/network/interfaces never
comes up on machine boot. contents of /etc/network/interfaces looks
correct:
---
# This file describes the
Public bug reported:
When installing a UEC node (from server iso 09272009.1), I'm finding
that the bridge device that is defined in /etc/network/interfaces never
comes up on machine boot. contents of /etc/network/interfaces looks
correct:
---
# This file describes the
This issue was addressed in Eucalytpus revno 768, and as such should
already be in latest karmic package (854)
** Changed in: eucalyptus (Ubuntu)
Status: Confirmed = Fix Released
--
Invalid S3_URL and EC2_URL in eucarc
https://bugs.launchpad.net/bugs/429734
You received this bug
This issue was resolved in Eucalyptus revnos 754-758, which addressed
multiple register/de-register issues.
--
euca_conf --register-sc returns success even though it fails
https://bugs.launchpad.net/bugs/431832
You received this bug notification because you are a member of Ubuntu
Server Team,
I think there may be some confusion here; the original bug, as we
understood it, was that an administrator could not add a user unless
email was configured and working properly (i.e., every addition of a
user required the system to send an email to the user, for the user to
repond, and for the
all, here is as much information as I could think of in an attempt to
allow for reproducability (see attached file). Here is what each file
in the attached tarball contains:
setup - quick description of machine set up
orig.libvirt.xml - the XML vm description that is passed to libvirt
all, here is as much information as I could think of in an attempt to
allow for reproducability (see attached file). Here is what each file
in the attached tarball contains:
setup - quick description of machine set up
orig.libvirt.xml - the XML vm description that is passed to libvirt
This issue was addressed in Eucalytpus revno 768, and as such should
already be in latest karmic package (854)
** Changed in: eucalyptus (Ubuntu)
Status: Confirmed = Fix Released
--
Invalid S3_URL and EC2_URL in eucarc
https://bugs.launchpad.net/bugs/429734
You received this bug
This issue was resolved in Eucalyptus revnos 754-758, which addressed
multiple register/de-register issues.
--
euca_conf --register-sc returns success even though it fails
https://bugs.launchpad.net/bugs/431832
You received this bug notification because you are a member of Ubuntu
Bugs, which is
This issue was resolved in Eucalyptus revnos 754-758, which addressed
multiple register/de-register issues (and, reduced the verbosity level
of the output from euca_conf, which can be brought back with the
--verbose flag :)
--
SOAP error when running euca_conf --deregister-walrus
I think there may be some confusion here; the original bug, as we
understood it, was that an administrator could not add a user unless
email was configured and working properly (i.e., every addition of a
user required the system to send an email to the user, for the user to
repond, and for the
all, here is as much information as I could think of in an attempt to
allow for reproducability (see attached file). Here is what each file
in the attached tarball contains:
setup - quick description of machine set up
orig.libvirt.xml - the XML vm description that is passed to libvirt
all, here is as much information as I could think of in an attempt to
allow for reproducability (see attached file). Here is what each file
in the attached tarball contains:
setup - quick description of machine set up
orig.libvirt.xml - the XML vm description that is passed to libvirt
fully addressed in revno 593
** Also affects: eucalyptus/1.6
Importance: Undecided
Status: New
** Changed in: eucalyptus/1.6
Status: New = Fix Committed
** Changed in: eucalyptus/1.6
Importance: Undecided = High
--
SC registration through web UI fails
fixed in revno 892
--
Part of storage controller setup that should run as the eucalyptus user runs as
root
https://bugs.launchpad.net/bugs/436276
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to eucalyptus in ubuntu.
--
If anyone can reproduce this issue, we'll need the logfiles:
/var/log/eucalyptus/cloud-*
in order to diagnose the core issue.
Thank you
--
500 server error when attempting to register ramdisk image
https://bugs.launchpad.net/bugs/428188
You received this bug notification because you are a
** Changed in: eucalyptus/1.6
Status: New = Fix Committed
--
over time, c3p0 causes deadlock condition in CLC
https://bugs.launchpad.net/bugs/436885
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to eucalyptus in ubuntu.
--
** Changed in: eucalyptus/1.6
Importance: Undecided = Medium
** Changed in: eucalyptus/1.6
Status: New = Confirmed
--
'eucarc' in downloaded credentials zipfile does not contain 'EC2_USER_ID'
https://bugs.launchpad.net/bugs/426389
You received this bug notification because you are a
** Also affects: eucalyptus/1.6
Importance: Undecided
Status: New
** Changed in: eucalyptus/1.6
Status: New = Fix Committed
** Changed in: eucalyptus/1.6
Importance: Undecided = Critical
--
SYSTEM mode, instances do not run
https://bugs.launchpad.net/bugs/430957
You
This problem is fixed in eucalyptus 1.6 revnos = 760
--
In MANAGED mode, with CLC and CC on same host, on first boot of CLC, Walrus URL
is detected as 169.254.169.254
https://bugs.launchpad.net/bugs/385435
You received this bug notification because you are a member of Ubuntu
Server Team, which
fully addressed in revno 593
** Also affects: eucalyptus/1.6
Importance: Undecided
Status: New
** Changed in: eucalyptus/1.6
Status: New = Fix Committed
** Changed in: eucalyptus/1.6
Importance: Undecided = High
--
SC registration through web UI fails
fixed in revno 892
--
Part of storage controller setup that should run as the eucalyptus user runs as
root
https://bugs.launchpad.net/bugs/436276
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
If anyone can reproduce this issue, we'll need the logfiles:
/var/log/eucalyptus/cloud-*
in order to diagnose the core issue.
Thank you
--
500 server error when attempting to register ramdisk image
https://bugs.launchpad.net/bugs/428188
You received this bug notification because you are a
** Changed in: eucalyptus/1.6
Status: New = Fix Committed
--
over time, c3p0 causes deadlock condition in CLC
https://bugs.launchpad.net/bugs/436885
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
** Changed in: eucalyptus/1.6
Importance: Undecided = Medium
** Changed in: eucalyptus/1.6
Status: New = Confirmed
--
'eucarc' in downloaded credentials zipfile does not contain 'EC2_USER_ID'
https://bugs.launchpad.net/bugs/426389
You received this bug notification because you are a
** Also affects: eucalyptus/1.6
Importance: Undecided
Status: New
** Changed in: eucalyptus/1.6
Status: New = Fix Committed
** Changed in: eucalyptus/1.6
Importance: Undecided = Critical
--
SYSTEM mode, instances do not run
https://bugs.launchpad.net/bugs/430957
You
This problem is fixed in eucalyptus 1.6 revnos = 760
--
In MANAGED mode, with CLC and CC on same host, on first boot of CLC, Walrus URL
is detected as 169.254.169.254
https://bugs.launchpad.net/bugs/385435
You received this bug notification because you are a member of Ubuntu
Bugs, which is
(this process with the same
VM/kernel works on Jaunty). Apparmor is disabled.
--
Daniel Nurmi
Co-Founder, Engineer
Eucalyptus Systems, Inc.
130 Castilian Dr. | Goleta, CA | 93117
Office: 805-845-8000 | Cell: 805-259-5269
Email: nu...@eucalyptus.com
www.eucalyptus.com
(this process with the same
VM/kernel works on Jaunty). Apparmor is disabled.
--
Daniel Nurmi
Co-Founder, Engineer
Eucalyptus Systems, Inc.
130 Castilian Dr. | Goleta, CA | 93117
Office: 805-845-8000 | Cell: 805-259-5269
Email: nu...@eucalyptus.com
www.eucalyptus.com
There is another bug, in KVM i suspect, that is preventing
attach/detach of block devices from fully working, however, you can see
some progress (logs indicating activity on the scsi bus in the VM when
you do an attach/detach):
https://bugs.launchpad.net/ubuntu/+source/eucalyptus/+bug/432154
--
I agree with Etienne on this issue; another thing to consider is that
many virtual appliances that are developed for EC2/UEC will be depending
on EBS functionality, due to the persistence observation made above.
--
dynamic block device attach/detach not functional with karmic KVM
There is another bug, in KVM i suspect, that is preventing
attach/detach of block devices from fully working, however, you can see
some progress (logs indicating activity on the scsi bus in the VM when
you do an attach/detach):
https://bugs.launchpad.net/ubuntu/+source/eucalyptus/+bug/432154
--
I agree with Etienne on this issue; another thing to consider is that
many virtual appliances that are developed for EC2/UEC will be depending
on EBS functionality, due to the persistence observation made above.
--
dynamic block device attach/detach not functional with karmic KVM
Jamie, thank you for taking a look here. First, after your response,
I've been able to modify /etc/apparmor.d/abstractions/libvirt-qemu with
the following:
/var/lib/eucalyptus/instances/**/console.log w,
/var/lib/eucalyptus/instances/**/kernel r,
/var/lib/eucalyptus/instances/**/ramdisk
I've found one more runtime issue with the apparmor profile. Eucalyptus
can provide the ability to dynamically attach/detach block devices to
VMs at runtime using libvirt attach-disk/detach-disk. We currently use
AOE for dynamic block devices, and these appear on the node in:
/dev/etherd/e*
Public bug reported:
The version of KVM currently in karmic does not appear to have a fully
functional dynamic block device attach/detach:
outside VM:
---
r...@explorer:/root# virsh list
Connecting to uri: qemu:///system
Id Name
** Also affects: qemu-kvm
Importance: Undecided
Status: New
** Also affects: qemu-kvm (Ubuntu)
Importance: Undecided
Status: New
--
dynamic block device attach/detach not functional with karmic KVM
https://bugs.launchpad.net/bugs/432154
You received this bug notification
Jamie, thank you for taking a look here. First, after your response,
I've been able to modify /etc/apparmor.d/abstractions/libvirt-qemu with
the following:
/var/lib/eucalyptus/instances/**/console.log w,
/var/lib/eucalyptus/instances/**/kernel r,
/var/lib/eucalyptus/instances/**/ramdisk
101 - 200 of 276 matches
Mail list logo
