Re: Possible problem with -no-kvm-irqchip -no-kvm-pit qemu options detected during git daily testing

2009-09-23 Thread Avi Kivity
On 09/21/2009 10:24 PM, Lucas Meneghel Rodrigues wrote: Ok, tests ended, indeed a problem showed up - we still have the problem I reported with the options -no-kvm-irqchip -no-kvm-pit *when* are coupled with the option -smp 2. If -smp 2 is not present, qemu works fine with the options

Re: Possible problem with -no-kvm-irqchip -no-kvm-pit qemu options detected during git daily testing

2009-09-21 Thread Lucas Meneghel Rodrigues
Ok, tests ended, indeed a problem showed up - we still have the problem I reported with the options -no-kvm-irqchip -no-kvm-pit *when* are coupled with the option -smp 2. If -smp 2 is not present, qemu works fine with the options -no-kvm-irqchip -no-kvm-pit. An example of command line:

Re: Possible problem with -no-kvm-irqchip -no-kvm-pit qemu options detected during git daily testing

2009-09-18 Thread Gleb Natapov
On Thu, Sep 17, 2009 at 09:57:05PM -0300, Lucas Meneghel Rodrigues wrote: Hi folks, after looking at today's git testing results, it seems like we have a problem with the command line options: -no-kvm-irqchip -no-kvm-pit This patch series should fix it. Not yet committed:

Re: Possible problem with -no-kvm-irqchip -no-kvm-pit qemu options detected during git daily testing

2009-09-18 Thread Lucas Meneghel Rodrigues
On Fri, Sep 18, 2009 at 6:51 AM, Gleb Natapov g...@redhat.com wrote: On Thu, Sep 17, 2009 at 09:57:05PM -0300, Lucas Meneghel Rodrigues wrote: Hi folks, after looking at today's git testing results, it seems like we have a problem with the command line options: -no-kvm-irqchip -no-kvm-pit

Possible problem with -no-kvm-irqchip -no-kvm-pit qemu options detected during git daily testing

2009-09-17 Thread Lucas Meneghel Rodrigues
Hi folks, after looking at today's git testing results, it seems like we have a problem with the command line options: -no-kvm-irqchip -no-kvm-pit All VMs that started with those command line options just hang on the BIOS screen, therefore all tests failed due to timeouts. So this looks like a