On Tue, Jan 18, 2022 at 1:34 PM John Snow wrote:
>
> On Tue, Jan 18, 2022 at 7:13 AM Peter Maydell
> wrote:
> >
> > On Mon, 17 Jan 2022 at 20:35, John Snow wrote:
> > > I do expect this to print more information on failure than it
> > > currently is, though (bug somewhere in machine.py, I think
On Tue, Jan 18, 2022 at 7:13 AM Peter Maydell wrote:
>
> On Mon, 17 Jan 2022 at 20:35, John Snow wrote:
> > I do expect this to print more information on failure than it
> > currently is, though (bug somewhere in machine.py, I think).
> > Can you please try applying this temporary patch and runni
On 1/18/22 12:08 AM, John Snow wrote:
On Mon, Jan 17, 2022 at 3:49 PM Peter Maydell wrote:
On Mon, 17 Jan 2022 at 20:35, John Snow wrote:
Can you please try applying this temporary patch and running `./check
-qcow2 040 041` until you see a breakage and show me the output from
that?
With t
On Mon, 17 Jan 2022 at 20:35, John Snow wrote:
> I do expect this to print more information on failure than it
> currently is, though (bug somewhere in machine.py, I think).
> Can you please try applying this temporary patch and running `./check
> -qcow2 040 041` until you see a breakage and show
On Mon, 17 Jan 2022 at 23:09, John Snow wrote:
> Well, today I learned that:
>
> (1) vm-build-XXX targets use your host system's QEMU to run that VM
> (2) my QMP library cannot talk to QEMU 2.11.
Whoops, I hadn't realised I was running with that ancient a QEMU.
For the scripted runs I set the PAT
On Mon, Jan 17, 2022 at 3:49 PM Peter Maydell wrote:
>
> On Mon, 17 Jan 2022 at 20:35, John Snow wrote:
>
> > Can you please try applying this temporary patch and running `./check
> > -qcow2 040 041` until you see a breakage and show me the output from
> > that?
>
> With this temporary patch the
On Mon, 17 Jan 2022 at 20:35, John Snow wrote:
> Can you please try applying this temporary patch and running `./check
> -qcow2 040 041` until you see a breakage and show me the output from
> that?
With this temporary patch the VM doesn't launch at all:
peter.mayd...@hackbox2.linaro.org:~/qemu-
On Mon, 17 Jan 2022 at 20:35, John Snow wrote:
>
> On Mon, Jan 17, 2022 at 5:05 AM Kevin Wolf wrote:
> >
> > Am 10.01.2022 um 16:55 hat Peter Maydell geschrieben:
> > > Just saw this failure of iotests in a netbsd VM
> This trace says that we timed out while awaiting a connection from
> QEMU dur
On Mon, Jan 17, 2022 at 5:05 AM Kevin Wolf wrote:
>
> Am 10.01.2022 um 16:55 hat Peter Maydell geschrieben:
> > Just saw this failure of iotests in a netbsd VM (the in-tree
> > tests/vm stuff). Pretty sure it's an intermittent as the
> > pulreq being tested has nothing io or block related.
> >
> >
Am 10.01.2022 um 16:55 hat Peter Maydell geschrieben:
> Just saw this failure of iotests in a netbsd VM (the in-tree
> tests/vm stuff). Pretty sure it's an intermittent as the
> pulreq being tested has nothing io or block related.
>
>
> TEST iotest-qcow2: 036
> TEST iotest-qcow2: 037
>
Just saw this failure of iotests in a netbsd VM (the in-tree
tests/vm stuff). Pretty sure it's an intermittent as the
pulreq being tested has nothing io or block related.
TEST iotest-qcow2: 036
TEST iotest-qcow2: 037
TEST iotest-qcow2: 038 [not run]
TEST iotest-qcow2: 039 [not run
11 matches
Mail list logo
