tags 683096 = confirmed
retitle 683096 no grub menu before boot with in-kernel irqchip
thanks
On 09.08.2012 08:44, Jamie Heilman wrote:
> Michael Tokarev wrote:
>> tags 683096 + moreinfo unreproducible
>> thanks
>>
>> Guys, can you please provide the complete qemu-kvm
>> command line which you use
Marc Haber wrote:
> On Wed, Aug 08, 2012 at 10:46:26PM +0400, Michael Tokarev wrote:
> > Guys, can you please provide the complete qemu-kvm
> > command line which you use to start the guest?
>
> How do I get that out of libvirt/virt-manager?
try "ps ww -C kvm"
--
Jamie Heilman
Michael Tokarev wrote:
> tags 683096 + moreinfo unreproducible
> thanks
>
> Guys, can you please provide the complete qemu-kvm
> command line which you use to start the guest?
>
> So far I can't reproduce the issue and I think I'm
> missing some options which you're using.
kvm -name bunk -m
On Wed, Aug 08, 2012 at 10:46:26PM +0400, Michael Tokarev wrote:
> Guys, can you please provide the complete qemu-kvm
> command line which you use to start the guest?
How do I get that out of libvirt/virt-manager?
Greetings
Marc
--
---
tags 683096 + moreinfo unreproducible
thanks
Guys, can you please provide the complete qemu-kvm
command line which you use to start the guest?
So far I can't reproduce the issue and I think I'm
missing some options which you're using.
Meanwhile I'm tagging this bug as unreproducible.
Thanks!
/
Marc Haber wrote:
> Is there a fix on the way, or is KVM upstream still debating with the
> kernel developers about who is at fault here?
No fix on the way, this bug will need to be upstreamed. There's been
no discussion about it on the list at all yet.
--
Jamie Heilman http
On Sun, Jul 29, 2012 at 04:28:25PM +, Jamie Heilman wrote:
> Marc Haber wrote:
> > On Sun, Jul 29, 2012 at 09:12:26AM +, Jamie Heilman wrote:
> > > Marc, you'll want to review the above mentioned bugs and verify that
> > > your config matches; iow, that you're using a virtio-blk boot device
Jamie Heilman wrote:
> Marc, you'll want to review the above mentioned bugs and verify that
> your config matches; iow, that you're using a virtio-blk boot device.
Actually, I can reproduce this on guests without any virtio devices
present, the in-kernel irqchip implementation itself appears to be
Marc Haber wrote:
> On Sun, Jul 29, 2012 at 09:12:26AM +, Jamie Heilman wrote:
> > Marc, you'll want to review the above mentioned bugs and verify that
> > your config matches; iow, that you're using a virtio-blk boot device.
>
> I am using a virtio-blk boot device, yes.
>
> Does current libv
On Sun, Jul 29, 2012 at 09:12:26AM +, Jamie Heilman wrote:
> Marc, you'll want to review the above mentioned bugs and verify that
> your config matches; iow, that you're using a virtio-blk boot device.
I am using a virtio-blk boot device, yes.
Does current libvirt offer a possibility to set a
I suspect this is very much related to 680719 (upstream 1021649). If
you disable the in-kernel irqchip, I bet you'll get your grub menu
back. I experimented some with my guests that use -display sdl and
the difference is quite noticable. For example, with an ubuntu server
instance that has a gru
Package: qemu-kvm
Version: 1.1.0+dfsg-3
Severity: normal
Booting a Linux VM inside KVM (using virt-manager, libvirt, qemu-kvm
1.1.0 from unstable) does not show the grub boot menu at all. It just
immediatly boots and runs fine then.
Downgrading qemu-kvm fo 1.0+dfsg-11 from testing made the grub-m
12 matches
Mail list logo
