qemu-discuss
[Top][All Lists]
Advanced

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

Re: [Qemu-discuss] Qemu-discuss Digest, Vol 38, Issue 11


From: Roman Mashak
Subject: Re: [Qemu-discuss] Qemu-discuss Digest, Vol 38, Issue 11
Date: Tue, 11 Nov 2014 13:09:06 -0500

Hi Markus,

I looked at your original message
http://lists.gnu.org/archive/html/qemu-discuss/2014-06/msg00094.html
You observed assert failure trigger by the negative value of error
value passed to bdrv_error_action(), while I do not see assert fail
and error value is positive. I'm not sure if these are the same issue
or different.

2014-11-11 12:30 GMT-05:00 Markus Stockhausen <address@hidden>:
[skip]
>> % scp address@hidden:/home/user/image.iso .
>> ...
>>
>> After ~90-91% completed I get this in qemu:
>> [   88.198496] perf samples too long (2506 > 2500), lowering
>> kernel.perf_event_max_sample_rate to 50000
>> [  117.924805] perf samples too long (5060 > 5000), lowering
>> kernel.perf_event_max_sample_rate to 25000
>>
>> And shortly after in ovs-dpdk console:
>> APP: (0) Device has been removed from ovdk_pf port vhost0
>> ...
>>
>> I connected to running qemu with GDB and found that the qemu sends
>> ioctl to stop vhost:
>>
>> ...
>> It looks that an error has occurred during disk I/O (frame 8) and it
>> resulted in subsequent VM stop.
>
> Do you think this is similar behaviour like my (older) bug report:
> http://lists.gnu.org/archive/html/qemu-discuss/2014-09/msg00030.html
>

-- 
Roman Mashak



reply via email to

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