** Changed in: linux (Ubuntu)
Status: Confirmed = Triaged
--
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/1109029
Title:
Depend on linux-initramfs-tools
To manage
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v3.9 kernel[0] (Not a kernel in the daily directory) and install both
the linux-image and linux-image-extra .deb packages.
If this bug is fixed in the
Can you also test the latest v3.8.4 stable kernel?
http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.8.4-raring/
If the bug still exits in 3.8.4, we will need to perform a reverse
bisect to identify the commit that fixes in this bug in v3.9-rc4.
--
You received this bug notification because you
** Changed in: linux
Importance: Undecided = High
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu)
Importance: Undecided = High
** Tags added: kernel-da-key raring
--
You received this bug notification because you are a member of
** Changed in: linux (Ubuntu)
Status: New = Confirmed
--
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/1196295
Title:
lxc-start enters uninterruptible sleep
To manage
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v3.10 kernel[0].
If this bug is fixed in the mainline kernel, please add the following
tag 'kernel-fixed-upstream'.
If the mainline kernel does not fix
Thanks for testing the upstream kernel. One additional question. Was
there a previous kernel version that did not exhibit this issue? It
would be good to know if this is a regression. If it is, we can perform
a bisect to identify the commit that introduced it.
--
You received this bug
** Tags removed: kernel-key needs-upstream-testing
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to vsftpd in Ubuntu.
https://bugs.launchpad.net/bugs/790863
Title:
Unable to start lxc container after update to 2.6.32-32
To manage
Hi Serge,
Can you attach the patch by Daniel Lezcano, or post a link to the patch?
** Tags added: precise
** Tags added: kernel-da-key
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
Hi Serge,
Thanks for posting the link. Do you know if this patch will make it
into the 3.2 mainline kernel?
--
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/914676
Title:
Support clean
I ask because we would rather have the patch come through a stable
update from upstream vs cherry picking it.
--
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/914676
Title:
Support clean
Are you requesting that this patch be cherry picked for Precise?
--
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/914676
Title:
Support clean container reboot vs shutdown disambiguation
** Changed in: linux (Ubuntu)
Status: Incomplete = Triaged
--
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/914676
Title:
Support clean container reboot vs shutdown disambiguation
** Tags added: kernel-key
--
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/914676
Title:
Support clean container reboot vs shutdown disambiguation
To manage notifications about this bug
** Also affects: lxc (Ubuntu)
Importance: Undecided
Status: New
--
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/917660
Title:
Installing qemu-user-static in an i386 lxc
** Changed in: linux (Ubuntu)
Status: Incomplete = Confirmed
--
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/925024
Title:
apparmor makes it impossible to install
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v3.3 kernel[1] (Not a kernel in the daily directory). Once you've
tested the upstream kernel, please remove the 'needs-upstream-testing'
tag(Only that
** Changed in: linux (Ubuntu)
Importance: Undecided = Medium
** Tags added: lucid regression-update
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to drbd8 in Ubuntu.
https://bugs.launchpad.net/bugs/1000355
Title:
drbd fence-peer
*** This bug is a duplicate of bug 1002388 ***
https://bugs.launchpad.net/bugs/1002388
** This bug is no longer a duplicate of bug 1007965
package linux-image-3.2.0-24-generic 3.2.0-24.39 failed to install/upgrade:
subprocess installed post-installation script returned error exit status
** Changed in: linux (Ubuntu)
Importance: Undecided = High
** Tags added: kernel-key
--
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/1034125
Title:
containers can load a kernel to
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v3.6 kernel[0] (Not a kernel in the daily directory) and install both
the linux-image and linux-image-extra .deb packages.
Once you've tested the
Does this issue go away if you boot into the kernel prior to the
upgrade?
--
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
Thanks, Serge. It would be good to know if the bug goes away if you
boot the precise kernel in the quantal vm. That will tell us if this is
a regression. If it is, we can perform a kernel bisect to identify the
commit in Quantal that introduced the regression.
--
You received this bug
@Paul, were you able to test the kernel mentioned in comment #22 ? The
3.5.0-17 kernel is now available as well.
** Changed in: linux (Ubuntu Quantal)
Status: Confirmed = Incomplete
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is
@Paul,
Can you also confirm this bug no longer exists in the latest quantal
images? If so, please mark this bug as Fix Released.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu-kvm in Ubuntu.
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v3.7 kernel[0] (Not a kernel in the daily directory) and install both
the linux-image and linux-image-extra .deb packages.
If this bug is fixed in the
This bug was filed against a series that is no longer supported and so
is being marked as Won't Fix. If this issue still exists in a supported
series, please file a new bug.
This change has been made by an automated script, maintained by the
Ubuntu Kernel Team.
** Changed in: linux (Ubuntu)
** Changed in: linux (Ubuntu)
Importance: Undecided = Medium
--
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/1079212
Title:
network slow when 2 VMs using virtio net bridged to
** Changed in: linux (Ubuntu)
Importance: Undecided = Medium
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to open-vm-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1088053
Title:
Kernel needs to provide FIFREEZE/FITHAW ioctl so
Hi Nate,
It appears FIFREEZE AND FITHAW are already built into the kernel.
Here is the defines in ~/linux/include/linux/fs.h(Also in
~linux/include/uapi/linux/fs.h):
#define FIFREEZE_IOWR('X', 119, int)/* Freeze */
#define FITHAW _IOWR('X', 120, int)/* Thaw */
In
This could be an issue:
/var/lib/dkms/open-vm-tools/2012.10.14/build/vmsync/sync.c: In function
‘VmSyncThawDevices’:
/var/lib/dkms/open-vm-tools/2012.10.14/build/vmsync/sync.c:165:37: error:
‘struct super_block’ has no member named ‘s_frozen’
** Changed in: linux (Ubuntu)
Status: Triaged = Incomplete
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to open-vm-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1088053
Title:
Kernel needs to provide FIFREEZE/FITHAW ioctl
@Peter
The decision was made to install Ubuntu on an internal disk and not the
SAN. The issue was still happening at that time with 10.04 and 10.10.
However, the system is not in productions, so it cannot be reconfigured.
--
You received this bug notification because you are a member of
Public bug reported:
System configuration is an IBM HS21 blade connected to an IBM DS3400 SAN.
The system is running Ubuntu 10.10 with multipath-tools version:
0.4.8-14ubuntu4.10.10.2
The Ubuntu OS is installed on an internal disk and not the SAN.
multipathd show paths
hcil dev dev_t pri dm_st
syslog
** Attachment added: syslog_log
https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/824790/+attachment/2269613/+files/syslog_log
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to multipath-tools in Ubuntu.
multipath.conf
** Attachment added: multipath.conf.081011
https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/824790/+attachment/2269612/+files/multipath.conf.081011
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to
The lvm.conf file has not been modified from what ships with Ubuntu.
--
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/824790
Title:
IBM DS3400 Will Not Bring Up Second Path
** Changed in: multipath-tools (Ubuntu)
Status: Confirmed = Invalid
--
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/824790
Title:
IBM DS3400 Will Not Bring Up Second
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v3.11 kernel[0].
If this bug is fixed in the mainline kernel, please add the following
tag 'kernel-fixed-upstream'.
If the mainline kernel does not fix
Per comment #13, it sounds like this issue is resolved in the 3.11
kernel, which is what Saucy will be rebased to. Does this issue only
exist in Saucy, or should the bug be targeted to other releases as well?
** Also affects: linux (Ubuntu Saucy)
Importance: High
Status: Incomplete
**
** Also affects: kvm (Ubuntu)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu)
Status: Triaged = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to kvm in Ubuntu.
** Tags removed: performing-bisect
--
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/1201092
Title:
Cannot load kvm_amd module - (says disabled by bios)
To manage notifications about
** Tags removed: kernel-key
** Tags added: kernel-da-key
--
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/1208455
Title:
general protection fault running apt-get inside double
@James Page, Did this bug just start happening after a new kernel
update? Was there a prior kernel that did not get this fault? If so,
we can perform a bisect to identify the commit that introduced the
regression.
Also, the 3.11.0-3.7 kernel is now available, which is rebased to
upstream
Thanks for the info, James. So in 3.10 and earlier the kernel did not
register a protocol hander for GRE and now it does?
--
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/1213879
** Changed in: linux (Ubuntu)
Status: Confirmed = 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/1196295
Title:
lxc-start enters uninterruptible sleep
To manage
** Changed in: linux (Ubuntu)
Importance: Undecided = High
** Tags added: kernel-key trusty
** Changed in: linux (Ubuntu)
Status: Incomplete = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
Do you happen to know if this is also an issue in the latest mainline
kernel[0]?
[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.13-rc6-trusty/
** Changed in: linux (Ubuntu)
Status: Confirmed = Incomplete
** Also affects: linux (Ubuntu Trusty)
Importance: High
Status:
One additional question, do you happen to know if this is a regression?
Did this not happen with previous releases/kernels?
** Tags removed: kernel-da-key
** Tags added: kernel-key
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc
This bug appears to be related to the mysql test suite versus the
kernel, so adding mysql bug task.
** Changed in: linux (Ubuntu)
Importance: Undecided = Medium
** Tags added: kernel-da-key ppc64el
** Also affects: mysql-5.5 (Ubuntu)
Importance: Undecided
Status: New
--
You
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v3.13 kernel[0].
If this bug is fixed in the mainline kernel, please add the following
tag 'kernel-fixed-upstream'.
If the mainline kernel does not fix
** Tags removed: kernel-key
--
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/1263738
Title:
login console 0 in user namespace container is not configured right
To manage notifications
Did this issue start happening after an update/upgrade? Was there a
kernel version where you were not having this particular problem? This
will help determine if the problem you are seeing is the result of the
introduction of a regression, and when this regression was introduced.
If this is a
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v3.13 kernel[0].
If this bug is fixed in the mainline kernel, please add the following
tag 'kernel-fixed-upstream'.
If the mainline kernel does not fix
This has happened again. Since this is Hardy, there is no apport-
collect. The following information has been added to the bug:
1) uname -a uname-a.log
2) dmesg dmesg.log
3) sudo lspci -vvnn lspci-vvnn.log
4) cat /proc/version_signature version.log
Please let us know if any additional data
** Attachment added: dmesg.log
https://bugs.launchpad.net/ubuntu/+source/samba/+bug/526464/+attachment/1791464/+files/dmesg.log
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba in ubuntu.
** Attachment added: lspci-vvnn.log
https://bugs.launchpad.net/ubuntu/+source/samba/+bug/526464/+attachment/1791465/+files/lspci-vvnn.log
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba in ubuntu.
** Attachment added: uname-a.log
https://bugs.launchpad.net/ubuntu/+source/samba/+bug/526464/+attachment/1791466/+files/uname-a.log
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba in ubuntu.
** Attachment added: version.log
https://bugs.launchpad.net/ubuntu/+source/samba/+bug/526464/+attachment/1791467/+files/version.log
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba in ubuntu.
One additional detail. The following error was reported on the
application side:
destination file error: CrystalEnterprise.DiskUnmanaged: Access is
denied.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba in ubuntu.
We disabled the AppArmor profile, but there was no effect on this error.
We reviewed the domain controller logs when one of these authentication
failures happened. There was not entry in the domain controller logs
stating that the authentication was attempted. For all successful
Public bug reported:
Binary package hint: multipath-tools
Installing either multipath-tools-boot or multipath-tools causes the
root partition to go 'Read onlyl'. System is then unable to reboot.
The only way to recover system is to boot in rescue mode and un-install
multipath-tools.
The
** Attachment added: multipath.conf
https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/716659/+attachment/1842127/+files/multipath.conf
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to multipath-tools in ubuntu.
Logs from system that had this failure.
** Attachment added: Ubuntu-Multipating.Sys-Message-Syslog-log.rar
https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/716659/+attachment/1842153/+files/Ubuntu-Multipating.Sys-Message-Syslog-log.rar
--
You received this bug notification
We performed a full Wireshark trace when the authentication failure
happens.
It looks like all successful authentications send packets to the domain
controller and perform an LDAP searchRequest. However, when the failures
happen, we don't see any data being sent to the Windows domain
controllers.
@Peter
Thanks for the suggestion. I will report back.
--
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/716659
Title:
Root filesystem goes Read only after installing
@ Surbhi, thanks for the feedback. I don't see debuglevel in the
smb.conf file. Is the parameter log level = N the same option? In
the previous logs we had this set to 5. I can see if we can increase
it to 10. If debuglevel and log level are different, I can see if
we can add that
@Surbhi, We have logs with the log level set to 5. Will setting the
log level to 10 provide additional valuable data? We would like to
prevent any changes, since this is a production environment, and
changing the log level requires a maintenance window.
--
You received this bug notification
** Description changed:
Binary package hint: multipath-tools
Installing either multipath-tools-boot or multipath-tools causes the
- root partition to go 'Read onlyl'. System is then unable to reboot.
- The only way to recover system is to boot in rescue mode and un-install
+ root
@Peter, we made all the suggested changes to the multipath.conf file,
but still have the same issue. The root filesystem goes read-only as
soon as multipathd starts. For the sake if time, the OS will now be
installed on an internal drive instead of boot from SAN. I'll post the
results from this
Output from multipath -v4
** Attachment added: multipath_v4_output.txt
https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/716659/+attachment/1877247/+files/multipath_v4_output.txt
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is
@Surbhi, unfortunately increasing the log level to 10 caused a
production outage. The high amount of logging overloaded the system and
made it unresponsive.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba in ubuntu.
** Attachment added: crystal3_2011-02-08_1000.pcap
https://bugs.launchpad.net/ubuntu/+source/samba/+bug/526464/+attachment/1901891/+files/crystal3_2011-02-08_1000.pcap
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba in
** Attachment added: fs1_2011-02-08_1000.pcap
https://bugs.launchpad.net/ubuntu/+source/samba/+bug/526464/+attachment/1901896/+files/fs1_2011-02-08_1000.pcap
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba in ubuntu.
Two wireshark traces were uploaded. The system crystal3 is the Windows
server. The system fs1 is the Ubuntu server.
--
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/526464
Title:
** Attachment added: crystal3_2011-01-25_1345.pcap
https://bugs.launchpad.net/ubuntu/+source/samba/+bug/526464/+attachment/1912733/+files/crystal3_2011-01-25_1345.pcap
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba in
** Attachment added: fs1_2011-01-25_1345.pcap
https://bugs.launchpad.net/ubuntu/+source/samba/+bug/526464/+attachment/1912734/+files/fs1_2011-01-25_1345.pcap
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba in ubuntu.
Failure vs Success screenshot. Failure is left screen and success is
right screen.
** Attachment added: wireshark_auth_screenshot.png
https://bugs.launchpad.net/ubuntu/+source/samba/+bug/526464/+attachment/1912735/+files/wireshark_auth_screenshot.png
--
You received this bug notification
Samba log showing failure and success that match up with the wireshark
dumps.
** Attachment added: crystal3.log
https://bugs.launchpad.net/ubuntu/+source/samba/+bug/526464/+attachment/1912741/+files/crystal3.log
--
You received this bug notification because you are a member of Ubuntu
Server
@Surbhi,
I uploaded two additional wireshark traces. These traces are for the
same two machines, but from an earlier date. The two wireshark traces
show sucessful auths and failures for both users(service_bhavnacrysta
and crystaluser).
I also uploaded the samba log for this time period. The
/var/log/auth.log file.
** Attachment added: auth_log
https://bugs.launchpad.net/ubuntu/+source/samba/+bug/526464/+attachment/1915502/+files/auth_log
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba in ubuntu.
smb.conf file.
** Attachment added: smb.conf
https://bugs.launchpad.net/ubuntu/+source/samba/+bug/526464/+attachment/1915503/+files/smb.conf
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba in ubuntu.
** Attachment added: crystal3.log.old
https://bugs.launchpad.net/ubuntu/+source/samba/+bug/526464/+attachment/1917956/+files/crystal3.log.old
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba in ubuntu.
Attaching a modified /etc/network/interfaces that allowed the network to
start.
** Attachment added: interfaces.working.txt
http://launchpadlibrarian.net/33521281/interfaces.working.txt
--
uec node cd install doesn't handle static network configuration
https://bugs.launchpad.net/bugs/446023
Attaching the broken /etc/network/interfaces from my configuration.
** Attachment added: interfaces.bad
http://launchpadlibrarian.net/33521225/interfaces.bad
--
uec node cd install doesn't handle static network configuration
https://bugs.launchpad.net/bugs/446023
You received this bug
I opened a duplicate bug: 451291
--
euca-describe-images reports all UEC images as x86_64
https://bugs.launchpad.net/bugs/451358
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to eucalyptus in ubuntu.
--
Ubuntu-server-bugs mailing list
** Also affects: eucalyptus (Ubuntu)
Importance: Undecided
Status: New
--
UEC Installer Only Configures One Network Interface
https://bugs.launchpad.net/bugs/448036
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to eucalyptus in
Public bug reported:
I'm having an issue starting an instance. I see errors stating disk
not found and no domain with matching name found. I'm also seeing an
error saying no supported architecture for os type 'hvm':
Snippet from nc.log:
[Wed Oct 14 14:57:00 2009][001691][EUCAINFO ] currently
Restarting libvirt and eucalyptus-nc did not seem to work around the
issue. Just to make sure I restarted things properly here is what I did
on the Node Controller:
eqlu...@granada:~$ sudo /etc/init.d/libvirt-bin restart
* Restarting libvirt management daemon /usr/sbin/libvirtd [
Contents of /var/log/eucalyptus/euca_test_nc.log:
This is perl, v5.10.0 built for i486-linux-gnu-thread-multi
Copyright 1987-2007, Larry Wall
Perl may be copied only under the terms of either the Artistic License or the
GNU General Public License, which may be found in the Perl 5 source kit.
Hmm. I wonder if this could be related to the bios. I'll check it to
ensure the correct settings are enabled for KVM. Could an error like
this occur if the bios was not setup correctly?
--
Unable to start EUC instances - no supported architecture for os type 'hvm'
I think I found the issue:
kern.log:Oct 13 15:53:45 granada kernel: [7.832803] kvm: disabled by
bios
I will correct the bios and re-test.
--
Unable to start EUC instances - no supported architecture for os type 'hvm'
https://bugs.launchpad.net/bugs/452323
You received this bug notification
I like your option. If a test case was automated, a check could be
performed first :-) As long as that error is always reported by dmesg
when the bios is not enabled :-)
--
kvm disable in bios (was: Unable to start EUC instances - no supported
architecture for os type 'hvm')
I checked the bios and found that VT extensions were not enabled. I
enabled them and was able to start my instance :-)
However, I ran into an issuing the ssh command listed in the test case:
$ ssh -i mykey.priv ubu...@$ipaddr
Permission denied (publickey).
I'll investigate this further.
I
Public bug reported:
I started an instance, which was assigned an IP Address from the cluster
DHCP. However, after a couple of days, the instance was no longer using
the IP address from DHCP, and would only respond to the private IP
Address.
This is what euca-describe-instance reported
I'm reviewing the logs now to see if there are additional details.
I think the max-lease-time is running out which is defined in
/etc/dhcp3/dhcpd.conf. The two configurable settings are:
default-lease-time 600;
max-lease-time 7200;
7200 is three days, which is the right about when my public IP
I restarted my instance on Monday after the public IP address changed.
The initial issue happened after three days. However, it's now been
four days, and I have not been able to reproduce it again. It now seems
there is not a pre-determined amount of time before the IP address
expires.
I'll
One other thing to note. The following is the output of euca-describe-
instances from this morning. Before the issue was reproduced:
$ euca-describe-instances
RESERVATION r-39C7074C admin default
INSTANCEi-46910829 emi-230B11AE172.23.46.78172.19.1.2
running
Looks like I just reproduced it after seven days:
$ euca-describe-instances
RESERVATION r-39C7074C admin default
INSTANCEi-46910829 emi-230B11AE172.19.1.2 172.19.1.2
running mykey 0 c1.medium 1970-01-01T00:00:00.813Z
ubuntucluster1
I can give this a test today. I will post feedback shortly.
--
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
1 - 100 of 30239 matches
Mail list logo
