qemu-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Qemu-devel] Boot Problems Windows XP guest


From: Erik Rull
Subject: Re: [Qemu-devel] Boot Problems Windows XP guest
Date: Thu, 29 Aug 2013 17:31:03 +0200 (CEST)

> On August 29, 2013 at 4:55 PM Paolo Bonzini <address@hidden> wrote:
>
>
> Il 29/08/2013 16:51, Erik Rull ha scritto:
> >
> >
> >> On August 29, 2013 at 11:25 AM Benoît Canet <address@hidden>
> >> wrote:
> >>
> >>
> >>> My commandline section is (I played with bps between 0.5 and 2.0 MB/sec
> >>> and
> >>> iops
> >>> with 1000 and 500):
> >>> -drive file=/dev/sda2,cache=none,bps=548576,bps_max=1,iops_max=1000
> >>> Within qemu it looks like that:
> >>> QEMU 1.6.50 monitor - type 'help' for more information
> >>> (qemu) info block
> >>> ide0-hd0: /dev/sda2 (raw)
> >>>     I/O throttling:   bps=548576 bps_rd=0 bps_wr=0 bps_max=1 bps_rd_max=0
> >>> bps_wr_max=0 iops=0 iops_rd=0 iops_wr=0 iops_max=1000 iops_rd_max=0
> >>> iops_wr_max=0 iops_size=0
> >>> (qemu)
> >>
> >> Why did you set iops_max but not iops ?
> >>
> >> Best regards
> >>
> >> Benoît
> >>
> >
> > Good point, I added that, but it still keeps rebooting:
> > (qemu) info block
> > ide0-hd0: /dev/sda2 (raw)
> >     I/O throttling:   bps=548576 bps_rd=0 bps_wr=0 bps_max=1 bps_rd_max=0
> > bps_wr_max=0 iops=500 iops_rd=0 iops_wr=0 iops_max=500 iops_rd_max=0
> > iops_wr_max=0 iops_size=0
>
> Too bad.
>
> But iops_max w/o iops makes sense: it means no more than 1000 iops will
> be in flight at the same time.  Note that "s" is a plural in "*s_max",
> not "per seconds". :)
>
> You could try iops_max=1 and make it higher if it works.
>
> Paolo
>

My SSD died - I took another one, cloned again from the spinning disk - works
*douh* - without any throttling!

If I run again in this situation, the real hardware might be the culprit.
Sorry for the time this issue took.
But I will try to make some deeper investigation on this issue - because it
worked with 1.2.0 and 1.6.50 failed...

Best regards,

Erik



reply via email to

[Prev in Thread] Current Thread [Next in Thread]