@mario - does upgrading to the backports kernel fix this for you?
--
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/1047531
Title:
Ubuntu 12.04 (Precise) guests can't boot on Ubuntu 1
I am experiencing this randomly with a host on ubuntu 12.04 and
upgrading guests from 12.04 to 14.04... randomly machines never boot
after the upgrade... others do..
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu-kvm in Ubuntu.
ht
(lowered priority since there is a workaround - using the backports
kernel. I don't believe this is a bug in qemu-kvm, since newer kernel
fixes it, but I'm not yet marking it invalid for qemu-kvm since it's
possible qemu-kvm coudl work around it somehow if it did the right
thing)
** Changed in: q
** Tags added: regression-release
--
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/1047531
Title:
Ubuntu 12.04 (Precise) guests can't boot on Ubuntu 10.04 (Lucid) QEMU-
KVM host
T
Also, when booting the Precise VM on Lucid host with oneiric kernel I
see the following message in dmesg:
kvm: : cpu0 unhandled rdmsr: 0xc0010001
There are no similar messages for other 10 Lucid VMs, running on the
same host.
--
You received this bug notification because you are a member of Ubu
Just in case, I'd like to confirm that upgrading the kernel to linux-
image-server-lts-backport-oneiric does solve this problem for me too.
--
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/b
Thanks for confirming the bug !
As for me, the workaround was to run the VM on another machine with
Intel processor, so that I can start upgrading the main server to
Precise (which, as far as I can tell, does not have this problem).
--
You received this bug notification because you are a member
Since the backports kernel, which is officially supported, works, I
suspect the kernel team may set this bug to low priority.
** Changed in: linux (Ubuntu)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu)
Status: New => Confirmed
--
You received this bug notification beca
When I installed the oneiric backports kernel, the VM booted just fine.
So a workaround here is:
sudo apt-get install linux-image-server-lts-backport-oneiric
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a mem
To my surprise, this is happening even with the very latest qemu-kvm
upstream git HEAD.
Host is an amd laptop with kernel: Linux ubuntu 2.6.32-43-generic-pae
#97-Ubuntu SMP Wed Sep 5 16:59:17 UTC 2012 i686 GNU/Linux
Guest kernel is vmlinuz-3.2.0-29-virtual
--
You received this bug notification
Peeking through gdb, it seems the kernel is hung inside setup_arch:
#0 0xc0135e81 in ?? ()
#1 0xc097a0a3 in ?? ()
#2 0xc09744ed in ?? ()
#3 0xc09740ba in ?? ()
#4 0x in ?? ()
where System.map (in the precise image) shows
c097a024 T reserve_standard_io_resources
c097a048 T setup_ar
Actually I believe I've reproduced this on an amd laptop. It does look
to be an amd-only bug. I've not reproduced it on intel.
** Changed in: qemu-kvm (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is
With 4 simultaneous instances I still could nto reproduce this. Again,
I removed 'console=ttyS0' from /boot/grub/grub.cfg (with the qcow file
mounted over qemu-nbd), and had to wait for cloud-init to time out on
its attempts to contact a provider.
--
You received this bug notification because yo
and 6 works too (hitting my memory limit)
Can you install the qemu-kvm-dbgsym package (see
https://wiki.ubuntu.com/DebuggingProgramCrash) and, when the guest is
frozen, get a stack trace to see where qemu is?
** Changed in: qemu-kvm (Ubuntu)
Status: New => Incomplete
--
You received this
Yes, in my case both host and guest are 32-bit. PAE is enabled by
default in stock 32-bit server Lucid kernel.
All my computers are running in 32-bit mode and, unfortunately, I can't
easily reinstall OS on them.
--
You received this bug notification because you are a member of Ubuntu
Server Team
Quoting Konstantin L. Metlov (met...@fti.dn.ua):
> May be it is the number of VMs then... Can you run 11 of them ?
I couldn't do 11 - not enough memory. I could do a bunch. However
I just noticed that you're running amd in 32-bit mode with PAE. I
was running 64-bit lucid! I'll re-install and t
May be it is the number of VMs then... Can you run 11 of them ?
--
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/1047531
Title:
Ubuntu 12.04 (Precise) guests can't boot on Ubuntu 10.
Failed to reproduce on amd as well.
--
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/1047531
Title:
Ubuntu 12.04 (Precise) guests can't boot on Ubuntu 10.04 (Lucid) QEMU-
KVM host
I couldn't reproduce this with lucid on intel. Trying amd.
--
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/1047531
Title:
Ubuntu 12.04 (Precise) guests can't boot on Ubuntu 10.04 (
Quoting Konstantin L. Metlov (met...@fti.dn.ua):
> Just to revive the topic...
>
> I have tried booting Precise cloudimg on one of my Lucid workstations
> with vanilla Lucid and KVM but 2.6.38-15-generic-pae (backported Natty)
> kernel. After removing 'console=ttyS0' the image boots properly. The
Just to revive the topic...
I have tried booting Precise cloudimg on one of my Lucid workstations
with vanilla Lucid and KVM but 2.6.38-15-generic-pae (backported Natty)
kernel. After removing 'console=ttyS0' the image boots properly. The
other difference is that the workstation I used has Intel C
Ah, sorry, that's another bug, but I suspect a duplicate of this.
I'll wait until I manage (or fail) to reproduce to ask for more - sorry.
--
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/b
4 ? Why ? There is only one "ubuntu-12.04-server-
cloudimg-i386-disk1.img". There is no "c.img" and no Windows involved.
--
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/1047531
Title:
Quoting Konstantin L. Metlov (met...@fti.dn.ua):
> Also the VM in hanged state uses exactly 36 Mb of memory out of
> allocated 512Mb and spins indefinitely using 100% CPU (sometimes
> sligntly more: 102% or 104%). Probably, this memory usage corresponds to
> the kernel+initrd.
Interesting.
Your k
Thanks, Konstantin.
I'll setup a new lucid host (as soon as hardware is freed from other
tests) and try to reproduce.
** Changed in: qemu-kvm (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qe
Also the VM in hanged state uses exactly 36 Mb of memory out of
allocated 512Mb and spins indefinitely using 100% CPU (sometimes
sligntly more: 102% or 104%). Probably, this memory usage corresponds to
the kernel+initrd.
I have enabled GRUB debug output, but never seen it telling anything
about la
Nope. In my case this does not help. I just get "Booting a command list"
and hang. I've tried removing "console=ttyS0" before and did it again
now just for a test. The hang happens not only with cloud images, but
with VMbuilder images and install ISOs too.
What bothers me, actually, is that I can'
(Also, after minutes I do then get a login prompt, with 'console=ttyS0'
removed from boot command)
--
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/1047531
Title:
Ubuntu 12.04 (Prec
Thanks for taking the time to report this bug.
I can actually reproduce this in quantal. However (at least in my case)
kvm is not actually hanging. The default boot prompt is sending output
to 'console=ttyS0', and cloud-init waits a long time for an ec2 server
to be available.
When I catch the
** Package changed: ubuntu => qemu-kvm (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu-kvm in Ubuntu.
https://bugs.launchpad.net/bugs/1047531
Title:
Ubuntu 12.04 (Precise) guests can't boot on Ubuntu 10.04 (Lucid) QEMU-
30 matches
Mail list logo
