Public bug reported:
$ sudo lxc-create -n quantal-armhf -t ubuntu -- -a armhf
:
:
W: Failure while installing base packages. This will be re-attempted up to
five times.
W: Failure while installing base packages. This will be re-attempted up to
five times.
W: Failure while installing base p
** Attachment added: "lxc.log"
https://bugs.launchpad.net/bugs/999187/+attachment/3146114/+files/lxc.log
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/999187
Title:
lxc-create for a
Hi Serge - yes, this was on a precise host.
Confirmed that lxc 0.7.5-3ubuntu56 from precise-proposed/universe now
allows me to create, start and stop an armhf container.
Thanks for the quick turn-around!
--
You received this bug notification because you are a member of Ubuntu
Server Team, which
Public bug reported:
Running a i686 32-bit quantal container on a i686 32-bit precise host
I'm seeing kernel message corruption in /var/log/syslog in the
container:
___
May 24 10:41:04 localhost ntpdate[172]: adjust time server 91.189.94.4 offset 0.
001225 sec
May 24 10:41:05 localhost ke
--
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/1003888
Title:
corrupted kernel messages being logged to syslog
To manage notifications about this bug go to:
https://bugs.launchpad.net/u
Hi Serge - two corruptions in the host as mentioned above.
--
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/1003888
Title:
corrupted kernel messages being logged to syslog
To manage noti
** Changed in: upstart
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.net/bugs/926468
Title:
Stopping ssh with a logged in user causes init to sp
Not an upstart issue fwics.
** Package changed: upstart (Ubuntu) => postfix (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to postfix in Ubuntu.
https://bugs.launchpad.net/bugs/1066144
Title:
arguments to dbus_server_disconne
@Paul: Please can you specify which packages are newly installed for
your to see this issue? Is it reproducable on other systems for you? As
mentioned, I do not see this problem on vanilla quantal system + the
postfix package installed.
--
You received this bug notification because you are a memb
Please can you boot such a system with '--debug' and capture syslog /
dmesg / console so we can try and work out what is happening here.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.
https://bugs.launchpad.net/bu
Public bug reported:
If LANG is not 'en_GB.UTF-8', lxc-create fails:
$ echo $LANG
fr_CA.UTF8
$ sudo lxc-create -n foo -t ubuntu -- raring
lxc-create: No config file specified, using the default config
/etc/lxc/default.conf
Checking cache download in /var/cache/lxc/raring/rootfs-i386 ...
Copy
Adding '-x' to the ubuntu template the problem is with locale-gen:
+ configure_ubuntu /var/lib/lxc/raring/rootfs raring raring
+ rootfs=/var/lib/lxc/raring/rootfs
+ hostname=raring
+ release=raring
+ cat
+ cat
+ cat
+ '[' '!' -f /var/lib/lxc/raring/rootfs/etc/init/container-detect.conf ']'
+ '[' -
Public bug reported:
$ sudo lxc-clone -o old -n new
$ echo $?
1
$ sudo bash /usr/bin/lxc-clone -o old -n new
Tweaking configuration
Copying rootfs...
Updating rootfs...
'raring-cloned' created
$
Problem appears to be missing "|| true" in LXC_PATH= assignment in
/usr/share/lxc/lxc.functions:
LXC_
What about the C locale? This fails as well.
Maybe the ubuntu template could check LANG. If not set, or not in
$(locale -a) or /usr/share/i18n/SUPPORTED, revert to en_US.UTF-8?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubu
Public bug reported:
$ sudo lxc-info -n raring
state: STOPPED
pid:-1
$ sudo lxc-execute -n raring -- true
lxc-execute: Failed to find an lxc-init
lxc-execute: invalid sequence number 1. expected 4
lxc-execute: failed to spawn 'raring'
$ dpkg -l lxc|grep lxc-init || echo not found
not fou
I believe the problem here is that -- in the case where a JobClass has
no running instances -- a reload is causing the original JobClass to be
destroyed. That eventually leads to Event->blockers to reach zero (as a
result of the JobClasses EventOperators being freed) causing the event
to be destroy
Public bug reported:
$ sudo lxc-ls -1
oneiric
precise
raring
raring-cloned
sid
$ sudo lxc-stop -n foo
$ echo $?
0
lxc-stop should return 1 in the example above and display an error
rather than silently failing and returning 0 to denote success.
ProblemType: Bug
DistroRelease: Ubuntu 13.04
Packag
ed at the sprint next week.
** Patch added: "upstart-bug-1124384-minimal-fix.diff"
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1124384/+attachment/3654975/+files/upstart-bug-1124384-minimal-fix.diff
** Changed in: upstart (Ubuntu)
Assignee: (unassigned) => James
Public bug reported:
Attempting to run apt-get in a nested vm hosted in OpenStack results in
a general protection fault in the kernel in the nested VM.
** Affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Affects: qemu-kvm (Ubuntu)
Importance: Undecided
St
Attempting to repeat the dep8 test run in the same environment has so
far resulted in the qemu-kvm binary consuming 200% CPU (recreated on
multiple nodes).
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu-kvm in Ubuntu.
https://bugs
I'm suspecting an issue with nested=1... the nested VM does eventually
boot but it takes many minutes to do so. At this point, the cpu usage of
qemu-kvm drops to reasonable values. But if you ssh into the vm, the
usage jumps up to ~200% again.
To recreate:
$ sudo apt-get install -y genisoimage li
** Attachment added: "Another general protection fault panic"
https://bugs.launchpad.net/ubuntu/+source/qemu-kvm/+bug/1208455/+attachment/3761555/+files/kvm.log
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu-kvm in Ubuntu.
htt
Kernel logs can be found on bug 1208509.
--
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 nested kvm VM on
OpenStack
Note that #4 was taken from a local nested kvm environment (not
OpenStack).
** Summary changed:
- general protection fault running apt-get inside nested kvm VM on OpenStack
+ general protection fault running apt-get inside nested kvm VM
--
You received this bug notification because you are a me
** 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 qemu-kvm in Ubuntu.
https://bugs.launchpad.net/bugs/1208455
Title:
general protection fault running apt-get inside n
High CPU may be cloud-init. Using todays server image, running 'prepare-
testbed' spins the CPU at 200%. The end of the log shows:
Aug 6 10:13:15 autopkgtest [CLOUDINIT] helpers.py[DEBUG]: Running
config-package-update-upgrade-install using lock ()
Aug 6 10:13:15 autopkgtest [CLOUDINIT] util.py
What we know so far:
- the issue is not related to cloud-init.
- the very high CPU load was atleast partly caused by byobu bug 1208853. To
disable byobu...
=== modified file 'bin/prepare-testbed'
--- bin/prepare-testbed 2013-08-06 08:05:16 +
+++ bin/prepare-testbed 2013-08-06 14:01:42 +
Fresh kernel panic from 2nd-level nested VM running with host, 1st level
and 2nd level all running with nested=1.
** Attachment added: "kvm.log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1208455/+attachment/3763650/+files/kvm.log
--
You received this bug notification because you a
Testing with linux-image-3.11.0-0-generic from -proposed with nested=Y
in all 3 environments does appear to solve this issue.
--
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
T
I got the panic again last night. This was running a 3.11 kernel for the
host, but of course the 1st and 2nd level guests were still running 3.10
as 3.11 is still in -proposed. So, although it's possible to get a test
run with (3.11, 3.10, 3.10) I really need to try running with (3.11,
3.11, 3.11)
Now that 3.11 is out of proposed, we're seeing a different kernel
failure, starting with
run-parts: executing /etc/kernel/postinst.d/zz-update-grub 3.11.0-2-generic
/boot/vmlinuz-3.11.0-2-generic
Generating grub.cfg ...
Found linux image: /boot/vmlinuz-3.11.0-2-generic
Found initrd image: /boot/i
The kernel BUG: above happens when running "bin/prepare-testbed -r saucy -d
i386" from lp:auto-package-testing in canonistack:
the kvm instance spins at ~200% CPU again.
I modified bin/prepare-testbed slightly to log the output of the vm and
disable byoubu. See attached.
** Patch added: "auto-p
To recreate:
1) Follow instructions on internal wiki (page
"InformationInfrastructure/IS/CanonicalOpenstack") to create a keypair.
2) Create an guest instance:
$ keyname="${USER}_lcy01"
$ image=$(euca-describe-images|grep saucy|head -1|awk '{print $2}')
$ euca-run-instances -k $keyname -t m1.med
Latest kernel panic (from 2nd-level guest) using following kernel
versions:
host: 3.11.0-1-generic (-2 causes problems for my graphics hardware atm)
1st-level guest: 3.11.0-2-generic
2nd-level guest: 3.11.0-2-generic
** Attachment added: "kvm.log"
https://bugs.launchpad.net/ubuntu/+source/li
The latest advice for running on Canonistack (kvm guest instance where
nested=Y is to):
- Only run on a 64-bit Canonistack guest instance.
- Modify bin/prepare-testbed and bin/run-adt-test to start the autopkgtest VM
using 'qemu-system-x86_64 -enable-kvm'.
- Have the DEP8 test running inside the
'qemu -serial file:/tmp/kvm.log' Looks like an alternative to 'qemu
-nographic >/tmp/kvm.log 2>&1'.
--
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
Re #27, removing -nographic still causes the same lockup for me.
--
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 doubl
Public bug reported:
Binary package hint: autofs5
/etc/init/autofs.conf contains the following stop on condition:
stop on runlevel[!2345]
This will stop the autofs service when the event called
"runlevel[!2345]" is emitted! There is a missing space here. autofs.conf
should specify:
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to autofs5 in ubuntu.
https://bugs.launchpad.net/bugs/718664
Title:
upstart config fo file autofs5 requires space
--
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
** Branch linked: lp:~jamesodhunt/ubuntu/natty/autofs5/fix-upstart-
config
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to autofs5 in ubuntu.
https://bugs.launchpad.net/bugs/718664
Title:
upstart config fo file autofs5 requires space
Hi Jamie - your syslog shows that Upstart attempted to restart smbd a
number of times, but since smbd kept exiting in error, it eventually hit
the upstart respawn limit at which point Upstart stopped attempting to
start it.
The problem suggests an issue either with the smbd binary or one of the
fi
@Jason: thanks for taking the time to look at this. Yes, I can confirm
your understanding of the problem as I had come to exactly the same
conclusion! :-) I have raised a bug on openssh for the stderr fd leak:
https://bugzilla.mindrot.org/show_bug.cgi?id=1976
** Bug watch added: OpenSSH Portable
** Changed in: upstart (Ubuntu Precise)
Assignee: (unassigned) => James Hunt (jamesodhunt)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.net/bugs/926468
Title:
Stopping ssh wit
** Also affects: upstart
Importance: Undecided
Status: New
** Changed in: upstart
Assignee: (unassigned) => James Hunt (jamesodhunt)
** Changed in: upstart
Importance: Undecided => High
** Changed in: upstart
Status: New => Fix Committed
--
You received
If you would like to help with testing the fix for this bug, I've put an
updated version of Upstart (version '1.4-0ubuntu7~jh') in my upstart-
job-logging PPA:
https://launchpad.net/~jamesodhunt/+archive/upstart-job-logging/
Please install and provide feedback.
** Changed in: upstart (Ubuntu P
@Jason: thanks for the feedback.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.net/bugs/926468
Title:
Stopping ssh with a logged in user causes init to spin at 100%
To manage notifications
I agree with Steve here: Upstart is careful to set CLOEXEC on all the
fds it has control over, so I would much prefer this be fixed at source.
A temporary work-around for jobs that are affected by this issue is to
add the following code at the top of all appropriate script sections -
remember that
Public bug reported:
Seems to be due to 1.1.0~rc1-0ubuntu1 landing?
$ lxc-start -n trusty --logfile /tmp/lxc.log --logpriority debug
lxc-start: lxc_start.c: main: 345 The container failed to start.
lxc-start: lxc_start.c: main: 347 To get more details, run the container in
foreground mode.
lxc-s
Ah - seems we'd actually need to add in a couple of loops in those
original dep-8 tests: run the tests as root, then run as a non-priv user
too! :)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.ne
Hi Serge,
Yep, updating to lxcfs 0.4, killing lxcfs, then a 'sudo chown -R james:
/sys/fs/cgroup/systemd/user.slice/user-1000.slice/session-c2.scope'
allowed me to start the non-priv container.
** Changed in: lxc (Ubuntu)
Status: Incomplete => New
--
You received this bug notification be
Still a problem on 3.13.0-17-generic.
--
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/1268906
Title:
cpu soft lockup running kvm
To manage notifications about this bug go to:
https
Hi Serge,
Looking at nih's configure.ac, you actually want to use '--enable-
threading' I think. I've never used this option and tbh wasn't even
aware it was there.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https:/
HI Serge - yes, problem is still there with the ppa versions:
$ dpkg -l|egrep "kvm|qemu"
ii ipxe-qemu
1.0.0+git-2013.c3d1e78-2ubuntu1 all PXE boot
firmware - ROM images for qemu
ii kvm-ipxe
Right. So to be completely clear, by calling nih_dbus_setup(), nih was
registering a libdbus handler that runs on the client side such that
whenever libdbus deemed necessary, it would attempt to wake up the
clients main loop by calling nih_main_loop_interrupt(). However, since
the client didn't hav
Sorry - ignore that. However, problem persists on a separate fully-
updated amd64 trusty system running kvm version 2.0.0~rc1+dfsg-0ubuntu3.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu in Ubuntu.
https://bugs.launchpad.net/bugs
Hi Serge,
I'm running on pure amd64 too so the problem is not arch-specific.
The simplest way to recreate:
$ kvm -cdrom /usr/lib/memtest86+/memtest86+.iso -m 512
Just hold down control+alt and frantically toggle the monitor using the
'2' and '1'. Within a couple of seconds it hangs.
--
You re
*** This bug is a duplicate of bug 901038 ***
https://bugs.launchpad.net/bugs/901038
Hi Serge,
The problem I believe is that Upstart is in the process of restarting so
initctl cannot (yet) reconnect to Upstart until it has finished the re-
exec. See comment #7 on bug 901038.
** This bug has
Public bug reported:
dnsmasq is spinning at 100% CPU. This also causes networking to fail.
Problem seems to be that it is calling recvmsg(STDIN_FILENO, ...) which
is totally invalid. See attached strace log.
ProblemType: Bug
DistroRelease: Ubuntu 14.10
Package: dnsmasq-base 2.70-1
ProcVersionSign
Attached is a full strace from dnsmasq startup showing the problem.
** Attachment added: "dnsmasq-strace.log"
https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1314697/+attachment/4107998/+files/dnsmasq-strace.log
** Summary changed:
- Upon upgrade, DNS resolution no longer works; dnsma
Updated description since problem is unrelated to upgrade - it just
occurs with the version of dnsmasq currently in utopic.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to dnsmasq in Ubuntu.
https://bugs.launchpad.net/bugs/1314697
Titl
A bit of debugging shows that the culprit is blockdata_expand() which is
being called via blockdata_init(). The issue seems to be that
blockdata_expand() is passed a parameter of zero. That function then
mallocs zero bytes (successfully seemingly), the proceeds to overwrite
data before the returned
BTW - the problem is recreatable for me every time simply by spinning up
a utopic kvm instance.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to dnsmasq in Ubuntu.
https://bugs.launchpad.net/bugs/1314697
Title:
DNS resolution no longe
After discussion with Scott, the best short-term solution would seem to
be:
1) Modify /etc/init.d/umountfs to call the following in do_stop before
calling umount/swapoff:
"initctl emit unmount-filesystem"
2) Modify /etc/init.d/umountroot to call the following in do_stop before
calling umoun
@Michael: yes, this should be "stop on unmount-filesystem or single-
user" (we can create a new event for single-user to make the logic
clearer).
@Clint: I agree that full migration sounds like the best approach. I
have had a few discussions previously with Scott on the idea of abstract
jobs. Ther
** Changed in: sysvinit (Ubuntu Maverick)
Assignee: (unassigned) => James Hunt (jamesodhunt)
** Changed in: sysvinit (Ubuntu Maverick)
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is a direct subscriber.
ntu17_to_sysvinit_2.87dsf-4ubuntu18.diff"
https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/672177/+attachment/1824633/+files/lucid-sysvinit_2.87dsf-4ubuntu17_to_sysvinit_2.87dsf-4ubuntu18.diff
** Changed in: sysvinit (Ubuntu Lucid)
Assignee: (unassigned) => James Hunt (jame
Equivalent sysvinit patch for Maverick.
** Patch added:
"maverick-sysvinit_2.87dsf-4ubuntu18_to_sysvinit_2.87dsf-4ubuntu19.diff"
https://bugs.launchpad.net/ubuntu/natty/+source/sysvinit/+bug/672177/+attachment/1824655/+files/maverick-sysvinit_2.87dsf-4ubuntu18_to_sysvinit_2.87dsf-4ubuntu19.di
Equivalent sysvinit patch for Natty.
** Patch added:
"natty_sysvinit_2.87dsf-4ubuntu19_to_sysvinit_2.87dsf-4ubuntu20.diff"
https://bugs.launchpad.net/ubuntu/natty/+source/sysvinit/+bug/672177/+attachment/1824656/+files/natty_sysvinit_2.87dsf-4ubuntu19_to_sysvinit_2.87dsf-4ubuntu20.diff
--
Y
** Also affects: kvm (Ubuntu)
Importance: Undecided
Status: New
--
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/862392
Title:
unity/compiz dies horribly if kvm interrupted when
Upstart certainly changed, but none of the changes affect console
handling. Could the kernel change be the culprit maybe?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.
https://bugs.launchpad.net/bugs/1235231
Tit
Public bug reported:
ssh -vvv is failing for me where is a VPN system.
VPN is configured and connected via network-manager. Last messages from
ssh (hangs forever):
debug2: kex_parse_kexinit: none,z...@openssh.com
debug2: kex_parse_kexinit: none,z...@openssh.com
debug2: kex_parse_kexinit:
debu
scp suffers the same issue, but interestingly, so seemingly does pscp
which hangs indefinitely after successfully connecting and starting to
send the data.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openssh in Ubuntu.
https://bugs.
Public bug reported:
To recreate (although this does *NOT* fail most of the time alas):
1) press "ctrl-alt-2" to switch to the qemu console.
2) type say "sendkey ctrl-alt-f1"
3) press "ctrl-alt-1".
Expected outcome: Switch to tty1 in the VM.
Actual outcome: No switch to tty1 in the VM. and qemu
... as if by magic it hung again :) I managed to trigger it by toggling
the following two key combos rapidly starting from within the qemu
console:
ctrl-alt-1 # switch to console (actually, we're already there, but ...)
ctrl-alt-2 # switch out of console
** Attachment added: "kvm-strace.log.gz"
I never saw the issue with saucy. Downgrading to 1.5.0+dfsg-3ubuntu5.1
certainly appears to have resolved the issue for me, so it's looking
like a regression introduced by 1.6.0+dfsg-2ubuntu4.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribe
Hi Serge,
1.7.0+dfsg-2ubuntu2 still exhibits the problem I'm afraid.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu in Ubuntu.
https://bugs.launchpad.net/bugs/1257352
Title:
kvm hangs occasionally when switching out of the qem
Hi Serge,
Yes, I get the hang on upstream too (HEAD
e157b8fdd412d48eacfbb8c67d3d58780154faa3).
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu in Ubuntu.
https://bugs.launchpad.net/bugs/1257352
Title:
kvm hangs occasionally wh
See CurrentDmesg.txt for lots of errors such as:
[ 1688.474887] Call Trace:
[ 1688.474914] [] kvm_vcpu_ioctl+0x433/0x4d0 [kvm]
[ 1688.474924] [] ? wake_up_state+0xf/0x20
[ 1688.474931] [] ? wake_futex+0x65/0x90
[ 1688.474937] [] ? futex_wake+0x13d/0x160
[ 1688.474942] [] ? do_futex+0xeb/0x660
Alas, same issue using kernel 3.13.0-031300rc8-generic.
** Changed in: linux (Ubuntu)
Status: Incomplete => New
--
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/1268906
Title:
Same problem with 3.13.0-4-generic.
--
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/1268906
Title:
cpu soft lockup running kvm
To manage notifications about this bug go to:
https:/
Same problem with 3.13.0-4-generic. Any progress on this? kvm is
unusable due to this issue.
** Attachment added: "dmesg-3.13.0-4-generic.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1268906/+attachment/3952909/+files/dmesg-3.13.0-4-generic.txt
--
You received this bug notificat
> I haven't been able to find where in upstart this is happening, but on the
> kernel side I can tell that it's due to an open() without
> O_NOCTTY.
Upstart does not open /dev/console without O_NOCTTY afaics. Are you sure
your kernel debug is showing pid 1 is doing this?
--
You received this b
Still a problem on 3.13.0-5-generic.
--
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/1268906
Title:
cpu soft lockup running kvm
To manage notifications about this bug go to:
https:
dmesg from 3.13.0-5-generic kernel.
** Attachment added: "dmesg.3.13.0-5-generic"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1268906/+attachment/3954151/+files/dmesg.3.13.0-5-generic
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subs
@Serge - perfectly happy to change that, in fact...
@Stéphane - could you review and test lp:~jamesodhunt/upstart/kmsg-
noctty? Thanks!
--
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/1263
** Changed in: upstart
Assignee: (unassigned) => James Hunt (jamesodhunt)
** Changed in: upstart
Status: New => Fix Committed
** Also affects: upstart (Ubuntu)
Importance: Undecided
Status: New
** Changed in: upstart (Ubuntu Trusty)
Status: New => Confirmed
Serge has just identified that the trigger for this bug is running kvm
with '-net user': without this option, no issues.
** Changed in: qemu-kvm (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to q
Latest series of oopses running on a fully updated trusty system.
** Attachment added: "dmesg.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1268906/+attachment/3958887/+files/dmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is
Same problem running with -vnc :7
** Attachment added: "dmesg.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1268906/+attachment/395/+files/dmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu-kvm in Ubuntu
To be clear, my host system is a 64-bit capable first-gen i7, but is
actually running fully 32-bit.
--
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/1268906
Title:
cpu soft lockup ru
Latest trusty desktop image (dated 24 Jan) results in the oops when
running with kvm as:
$ kvm --enable-kvm -cdrom ubuntu_trusty-desktop-i386.iso -boot d -m 1024
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu-kvm in Ubuntu.
https
I think the switch to 3.13 may have borked kvm for me. I'll try to
confirm that tomorrow...
--
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/1268906
Title:
cpu soft lockup running kv
Public bug reported:
$ lxc-start -n trusty
lxc_container: Permission denied - failed to get real path for
'/home/james/.local/share/lxc/trusty/rootfs'
lxc_container: failed to mount rootfs
lxc_container: failed to setup rootfs for 'trusty'
lxc_container: failed to setup the container
lxc_containe
The problem does seem to be an LXC bug. However, I can work around it by
changing the perms on my home directory from 0750 to 0755.
--
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/1277466
** Also affects: cgmanager (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cgmanager in Ubuntu.
https://bugs.launchpad.net/bugs/1357252
Title:
"Application failed to start." during
** Changed in: upstart
Status: New => In Progress
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cgmanager in Ubuntu.
https://bugs.launchpad.net/bugs/1
** No longer affects: linux (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cgmanager in Ubuntu.
https://bugs.launchpad.net/bugs/1357252
Title:
Upstart jobs specifying cgroup fail to start occasionally
To manage notificatio
** Also affects: systemd-shim (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cgmanager in Ubuntu.
https://bugs.launchpad.net/bugs/1357252
Title:
Upstart jobs specifying cgroup fai
** Changed in: upstart
Status: In Progress => Invalid
** Changed in: upstart
Importance: Critical => Undecided
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cgmanager in Ubuntu.
https://bugs.launchpad.net/bugs/1357252
Titl
** Summary changed:
- systemd-shim fails to handle cgmanager being unavailable
+ upstart can race with cgmanager when using remove-on-empty
** Changed in: upstart
Status: Invalid => In Progress
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is
1 - 100 of 104 matches
Mail list logo
