Dor Laor <[EMAIL PROTECTED]> writes:
> Sven Rudolph wrote:
...
> > Trying a summary: When using virtio Ethernet and "-usb"; Windows
> > leaves something (virtio Ethernet or USB ?) in a state that isn't
> > reset by my reboot sequence (etherboot/pxegrub) and makes the next
> > Windows boot hang. Booting Linux inbetween resets that state, and
> > using the "-boot c" path does that too.
...
> It seems like the virtio and the usb root hub share the same pci irq. Probably
> on reboot
> the usb root hub does not reset the irq status and just after boot the driver
> gets into infnit loop.
> Can you try to compile the following:
> diff --git a/qemu/hw/usb-uhci.c b/qemu/hw/usb-uhci.c
> index b90cf78..773ad54 100644
> --- a/qemu/hw/usb-uhci.c
> +++ b/qemu/hw/usb-uhci.c
> @@ -1098,6 +1098,7 @@ void usb_uhci_piix3_init(PCIBus *bus, int devfn)
> s->frame_timer = qemu_new_timer(vm_clock, uhci_frame_timer, s);
>
> uhci_reset(s);
> + qemu_register_reset(uhci_reset, s);
>
> /* Use region 4 for consistency with real hardware. BSD guests seem
> to rely on this. */
> @@ -1135,6 +1136,7 @@ void usb_uhci_piix4_init(PCIBus *bus, int devfn)
> s->frame_timer = qemu_new_timer(vm_clock, uhci_frame_timer, s);
>
> uhci_reset(s);
> + qemu_register_reset(uhci_reset, s);
>
> /* Use region 4 for consistency with real hardware. BSD guests seem
> to rely on this. */
This patch didn't help...
> Alternatively you can try -no-kvm-irqchip
... but this option helps. I hope this is a useful hint for finding
the origin of the problem.
Thanks,
Sven
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
