From d0c85e36e4de67af628d54e9ab577cc3fad7796a Mon Sep 17 00:00:00 2001 From: Christian Krinitsin Date: Thu, 3 Jul 2025 07:27:52 +0000 Subject: add deepseek and gemma results --- .../deepseek-2-tmp/output/device/1004050 | 17 --- .../deepseek-2-tmp/output/device/1013241 | 27 ----- .../deepseek-2-tmp/output/device/1013691 | 15 --- .../deepseek-2-tmp/output/device/1014099 | 8 -- .../deepseek-2-tmp/output/device/1014681 | 35 ------ .../classifier/deepseek-2-tmp/output/device/1015 | 2 - .../classifier/deepseek-2-tmp/output/device/1018 | 24 ----- .../deepseek-2-tmp/output/device/1026176 | 22 ---- .../deepseek-2-tmp/output/device/1031955 | 36 ------- .../deepseek-2-tmp/output/device/1038136 | 9 -- .../deepseek-2-tmp/output/device/1047470 | 60 ----------- .../classifier/deepseek-2-tmp/output/device/1049 | 2 - .../deepseek-2-tmp/output/device/1055090 | 22 ---- .../deepseek-2-tmp/output/device/1062220 | 29 ----- .../deepseek-2-tmp/output/device/1070762 | 38 ------- .../classifier/deepseek-2-tmp/output/device/1071 | 13 --- .../deepseek-2-tmp/output/device/1073952 | 29 ----- .../classifier/deepseek-2-tmp/output/device/1076 | 13 --- .../deepseek-2-tmp/output/device/1077708 | 17 --- .../deepseek-2-tmp/output/device/1077838 | 31 ------ .../deepseek-2-tmp/output/device/1086782 | 85 --------------- .../deepseek-2-tmp/output/device/1087114 | 45 -------- .../deepseek-2-tmp/output/device/1088617 | 15 --- .../deepseek-2-tmp/output/device/1089006 | 12 --- .../classifier/deepseek-2-tmp/output/device/1090 | 16 --- .../deepseek-2-tmp/output/device/1090558 | 10 -- .../deepseek-2-tmp/output/device/1090604 | 12 --- .../deepseek-2-tmp/output/device/1093360 | 14 --- .../deepseek-2-tmp/output/device/1096713 | 9 -- .../deepseek-2-tmp/output/device/1096714 | 11 -- .../deepseek-2-tmp/output/device/1101210 | 10 -- .../classifier/deepseek-2-tmp/output/device/1106 | 10 -- .../classifier/deepseek-2-tmp/output/device/1110 | 4 - .../classifier/deepseek-2-tmp/output/device/1112 | 2 - .../classifier/deepseek-2-tmp/output/device/112 | 2 - .../classifier/deepseek-2-tmp/output/device/1134 | 4 - .../classifier/deepseek-2-tmp/output/device/1139 | 79 -------------- .../deepseek-2-tmp/output/device/1162227 | 17 --- .../deepseek-2-tmp/output/device/1162644 | 91 ---------------- .../classifier/deepseek-2-tmp/output/device/1168 | 14 --- .../deepseek-2-tmp/output/device/1173490 | 21 ---- .../classifier/deepseek-2-tmp/output/device/1174 | 14 --- .../classifier/deepseek-2-tmp/output/device/1175 | 9 -- .../deepseek-2-tmp/output/device/1175513 | 12 --- .../classifier/deepseek-2-tmp/output/device/1176 | 8 -- .../classifier/deepseek-2-tmp/output/device/118 | 2 - .../deepseek-2-tmp/output/device/1181796 | 10 -- .../deepseek-2-tmp/output/device/1185888 | 26 ----- .../deepseek-2-tmp/output/device/1186303 | 23 ---- .../deepseek-2-tmp/output/device/1187529 | 12 --- .../deepseek-2-tmp/output/device/1188018 | 6 -- .../deepseek-2-tmp/output/device/1188991 | 61 ----------- .../classifier/deepseek-2-tmp/output/device/1191 | 10 -- .../deepseek-2-tmp/output/device/1191326 | 16 --- .../classifier/deepseek-2-tmp/output/device/1193 | 17 --- .../deepseek-2-tmp/output/device/1194954 | 4 - .../deepseek-2-tmp/output/device/1196145 | 19 ---- .../deepseek-2-tmp/output/device/1198350 | 46 -------- .../deepseek-2-tmp/output/device/1200212 | 15 --- .../deepseek-2-tmp/output/device/1207228 | 14 --- .../deepseek-2-tmp/output/device/1219234 | 15 --- .../classifier/deepseek-2-tmp/output/device/1220 | 17 --- .../deepseek-2-tmp/output/device/1222034 | 20 ---- .../deepseek-2-tmp/output/device/1223467 | 23 ---- .../deepseek-2-tmp/output/device/1223477 | 31 ------ .../deepseek-2-tmp/output/device/1225187 | 13 --- .../classifier/deepseek-2-tmp/output/device/1226 | 26 ----- .../deepseek-2-tmp/output/device/1230232 | 34 ------ .../classifier/deepseek-2-tmp/output/device/1234 | 4 - .../classifier/deepseek-2-tmp/output/device/1237 | 2 - .../deepseek-2-tmp/output/device/1237625 | 49 --------- .../deepseek-2-tmp/output/device/1242765 | 70 ------------ .../deepseek-2-tmp/output/device/1248469 | 4 - .../classifier/deepseek-2-tmp/output/device/1250 | 4 - .../deepseek-2-tmp/output/device/1256122 | 23 ---- .../deepseek-2-tmp/output/device/1257334 | 4 - .../deepseek-2-tmp/output/device/1267520 | 6 -- .../deepseek-2-tmp/output/device/1268596 | 25 ----- .../deepseek-2-tmp/output/device/1268671 | 45 -------- .../deepseek-2-tmp/output/device/1269628 | 6 -- .../deepseek-2-tmp/output/device/1276879 | 17 --- .../deepseek-2-tmp/output/device/1280521 | 4 - .../deepseek-2-tmp/output/device/1284874 | 31 ------ .../classifier/deepseek-2-tmp/output/device/1288 | 10 -- .../deepseek-2-tmp/output/device/1292037 | 15 --- .../classifier/deepseek-2-tmp/output/device/1294 | 2 - .../deepseek-2-tmp/output/device/1295587 | 20 ---- .../classifier/deepseek-2-tmp/output/device/1300 | 12 --- .../deepseek-2-tmp/output/device/1306818 | 44 -------- .../deepseek-2-tmp/output/device/1307281 | 11 -- .../classifier/deepseek-2-tmp/output/device/1311 | 2 - .../deepseek-2-tmp/output/device/1314857 | 20 ---- .../classifier/deepseek-2-tmp/output/device/1318 | 20 ---- .../deepseek-2-tmp/output/device/1320360 | 18 ---- .../deepseek-2-tmp/output/device/1321684 | 47 -------- .../classifier/deepseek-2-tmp/output/device/133 | 2 - .../deepseek-2-tmp/output/device/1333216 | 37 ------- .../deepseek-2-tmp/output/device/1334397 | 9 -- .../deepseek-2-tmp/output/device/1336123 | 12 --- .../deepseek-2-tmp/output/device/1338957 | 12 --- .../classifier/deepseek-2-tmp/output/device/1342 | 25 ----- .../deepseek-2-tmp/output/device/1352179 | 29 ----- .../deepseek-2-tmp/output/device/1352465 | 8 -- .../deepseek-2-tmp/output/device/1353456 | 18 ---- .../classifier/deepseek-2-tmp/output/device/1354 | 2 - .../deepseek-2-tmp/output/device/1354279 | 53 --------- .../classifier/deepseek-2-tmp/output/device/1356 | 18 ---- .../classifier/deepseek-2-tmp/output/device/1366 | 85 --------------- .../deepseek-2-tmp/output/device/1367365 | 10 -- .../deepseek-2-tmp/output/device/1368178 | 26 ----- .../deepseek-2-tmp/output/device/1368204 | 16 --- .../deepseek-2-tmp/output/device/1373362 | 28 ----- .../deepseek-2-tmp/output/device/1378407 | 6 -- .../classifier/deepseek-2-tmp/output/device/1380 | 5 - .../deepseek-2-tmp/output/device/1381879 | 34 ------ .../deepseek-2-tmp/output/device/1386478 | 6 -- .../deepseek-2-tmp/output/device/1390520 | 27 ----- .../classifier/deepseek-2-tmp/output/device/1391 | 29 ----- .../classifier/deepseek-2-tmp/output/device/1392 | 15 --- .../deepseek-2-tmp/output/device/1392504 | 4 - .../classifier/deepseek-2-tmp/output/device/1393 | 66 ------------ .../deepseek-2-tmp/output/device/1393440 | 18 ---- .../deepseek-2-tmp/output/device/1399943 | 29 ----- .../classifier/deepseek-2-tmp/output/device/1403 | 2 - .../classifier/deepseek-2-tmp/output/device/1404 | 15 --- .../deepseek-2-tmp/output/device/1404610 | 12 --- .../deepseek-2-tmp/output/device/1407454 | 31 ------ .../deepseek-2-tmp/output/device/1407808 | 10 -- .../classifier/deepseek-2-tmp/output/device/1413 | 23 ---- .../deepseek-2-tmp/output/device/1422285 | 55 ---------- .../deepseek-2-tmp/output/device/1423668 | 12 --- .../deepseek-2-tmp/output/device/1426593 | 9 -- .../deepseek-2-tmp/output/device/1428958 | 66 ------------ .../classifier/deepseek-2-tmp/output/device/143 | 2 - .../deepseek-2-tmp/output/device/1435973 | 61 ----------- .../deepseek-2-tmp/output/device/1437970 | 45 -------- .../classifier/deepseek-2-tmp/output/device/144 | 2 - .../deepseek-2-tmp/output/device/1440843 | 15 --- .../classifier/deepseek-2-tmp/output/device/1442 | 2 - .../deepseek-2-tmp/output/device/1445633 | 14 --- .../classifier/deepseek-2-tmp/output/device/1451 | 2 - .../deepseek-2-tmp/output/device/1453025 | 16 --- .../classifier/deepseek-2-tmp/output/device/1457 | 2 - .../classifier/deepseek-2-tmp/output/device/1458 | 28 ----- .../classifier/deepseek-2-tmp/output/device/1460 | 6 -- .../classifier/deepseek-2-tmp/output/device/1465 | 2 - .../classifier/deepseek-2-tmp/output/device/1468 | 7 -- .../classifier/deepseek-2-tmp/output/device/147 | 2 - .../deepseek-2-tmp/output/device/1470536 | 13 --- .../deepseek-2-tmp/output/device/1476183 | 18 ---- .../deepseek-2-tmp/output/device/1481750 | 19 ---- .../classifier/deepseek-2-tmp/output/device/1483 | 2 - .../deepseek-2-tmp/output/device/1486768 | 18 ---- .../deepseek-2-tmp/output/device/1488363 | 54 ---------- .../classifier/deepseek-2-tmp/output/device/1490 | 62 ----------- .../deepseek-2-tmp/output/device/1490886 | 33 ------ .../deepseek-2-tmp/output/device/1499908 | 56 ---------- .../deepseek-2-tmp/output/device/1500175 | 38 ------- .../deepseek-2-tmp/output/device/1502613 | 8 -- .../classifier/deepseek-2-tmp/output/device/1504 | 2 - .../deepseek-2-tmp/output/device/1509336 | 54 ---------- .../deepseek-2-tmp/output/device/1511887 | 35 ------ .../deepseek-2-tmp/output/device/1518969 | 29 ----- .../classifier/deepseek-2-tmp/output/device/1519 | 13 --- .../classifier/deepseek-2-tmp/output/device/1521 | 2 - .../classifier/deepseek-2-tmp/output/device/1522 | 41 ------- .../deepseek-2-tmp/output/device/1523246 | 16 --- .../classifier/deepseek-2-tmp/output/device/1526 | 2 - .../deepseek-2-tmp/output/device/1529449 | 4 - .../deepseek-2-tmp/output/device/1529859 | 49 --------- .../deepseek-2-tmp/output/device/1530035 | 24 ----- .../deepseek-2-tmp/output/device/1530278 | 13 --- .../deepseek-2-tmp/output/device/1543057 | 17 --- .../deepseek-2-tmp/output/device/1544524 | 23 ---- .../deepseek-2-tmp/output/device/1550743 | 27 ----- .../classifier/deepseek-2-tmp/output/device/1563 | 4 - .../deepseek-2-tmp/output/device/1568621 | 19 ---- .../classifier/deepseek-2-tmp/output/device/1569 | 28 ----- .../classifier/deepseek-2-tmp/output/device/157 | 2 - .../deepseek-2-tmp/output/device/1572959 | 8 -- .../deepseek-2-tmp/output/device/1575561 | 7 -- .../classifier/deepseek-2-tmp/output/device/1576 | 29 ----- .../deepseek-2-tmp/output/device/1576347 | 27 ----- .../classifier/deepseek-2-tmp/output/device/1577 | 85 --------------- .../deepseek-2-tmp/output/device/1579306 | 15 --- .../deepseek-2-tmp/output/device/1579645 | 13 --- .../classifier/deepseek-2-tmp/output/device/158 | 2 - .../deepseek-2-tmp/output/device/1580459 | 16 --- .../deepseek-2-tmp/output/device/1580586 | 10 -- .../deepseek-2-tmp/output/device/1581308 | 17 --- .../classifier/deepseek-2-tmp/output/device/1583 | 20 ---- .../deepseek-2-tmp/output/device/1583421 | 8 -- .../deepseek-2-tmp/output/device/1585433 | 11 -- .../deepseek-2-tmp/output/device/1585971 | 21 ---- .../deepseek-2-tmp/output/device/1586611 | 14 --- .../deepseek-2-tmp/output/device/1586613 | 14 --- .../deepseek-2-tmp/output/device/1587065 | 51 --------- .../deepseek-2-tmp/output/device/1587970 | 6 -- .../deepseek-2-tmp/output/device/1592336 | 28 ----- .../deepseek-2-tmp/output/device/1596832 | 56 ---------- .../classifier/deepseek-2-tmp/output/device/1597 | 57 ---------- .../classifier/deepseek-2-tmp/output/device/1598 | 59 ----------- .../deepseek-2-tmp/output/device/1600563 | 17 --- .../deepseek-2-tmp/output/device/1603693 | 78 -------------- .../deepseek-2-tmp/output/device/1603779 | 19 ---- .../deepseek-2-tmp/output/device/1608802 | 50 --------- .../classifier/deepseek-2-tmp/output/device/1614 | 2 - .../deepseek-2-tmp/output/device/1618265 | 4 - .../deepseek-2-tmp/output/device/1618431 | 66 ------------ .../deepseek-2-tmp/output/device/1622582 | 37 ------- .../deepseek-2-tmp/output/device/1623998 | 13 --- .../deepseek-2-tmp/output/device/1624726 | 30 ------ .../classifier/deepseek-2-tmp/output/device/1625 | 14 --- .../deepseek-2-tmp/output/device/1625216 | 72 ------------- .../deepseek-2-tmp/output/device/1626207 | 46 -------- .../deepseek-2-tmp/output/device/1630723 | 7 -- .../deepseek-2-tmp/output/device/1634069 | 6 -- .../deepseek-2-tmp/output/device/1637693 | 8 -- .../deepseek-2-tmp/output/device/1637974 | 49 --------- .../deepseek-2-tmp/output/device/1639322 | 12 --- .../deepseek-2-tmp/output/device/1639791 | 24 ----- .../deepseek-2-tmp/output/device/1639983 | 22 ---- .../deepseek-2-tmp/output/device/1643342 | 26 ----- .../classifier/deepseek-2-tmp/output/device/1645 | 9 -- .../classifier/deepseek-2-tmp/output/device/1646 | 62 ----------- .../deepseek-2-tmp/output/device/1646610 | 71 ------------- .../deepseek-2-tmp/output/device/1648726 | 21 ---- .../classifier/deepseek-2-tmp/output/device/1654 | 82 -------------- .../deepseek-2-tmp/output/device/1656234 | 38 ------- .../deepseek-2-tmp/output/device/1658506 | 12 --- .../deepseek-2-tmp/output/device/1661758 | 118 --------------------- .../deepseek-2-tmp/output/device/1667613 | 15 --- .../deepseek-2-tmp/output/device/1674114 | 28 ----- .../deepseek-2-tmp/output/device/1675332 | 4 - .../deepseek-2-tmp/output/device/1675333 | 4 - .../deepseek-2-tmp/output/device/1677247 | 13 --- .../deepseek-2-tmp/output/device/1677492 | 11 -- .../deepseek-2-tmp/output/device/1680679 | 80 -------------- .../deepseek-2-tmp/output/device/1681398 | 11 -- .../deepseek-2-tmp/output/device/1681404 | 9 -- .../deepseek-2-tmp/output/device/1681439 | 36 ------- .../deepseek-2-tmp/output/device/1681688 | 14 --- .../deepseek-2-tmp/output/device/1688231 | 32 ------ .../deepseek-2-tmp/output/device/1689003 | 14 --- .../classifier/deepseek-2-tmp/output/device/1691 | 11 -- .../deepseek-2-tmp/output/device/1691379 | 46 -------- .../deepseek-2-tmp/output/device/1693050 | 12 --- .../deepseek-2-tmp/output/device/1699628 | 18 ---- .../deepseek-2-tmp/output/device/1702621 | 35 ------ .../deepseek-2-tmp/output/device/1706058 | 27 ----- .../deepseek-2-tmp/output/device/1707587 | 9 -- .../deepseek-2-tmp/output/device/1708551 | 18 ---- .../classifier/deepseek-2-tmp/output/device/1713 | 41 ------- .../deepseek-2-tmp/output/device/1714538 | 4 - .../deepseek-2-tmp/output/device/1715296 | 17 --- .../deepseek-2-tmp/output/device/1716132 | 21 ---- .../deepseek-2-tmp/output/device/1718118 | 26 ----- .../deepseek-2-tmp/output/device/1719689 | 15 --- .../deepseek-2-tmp/output/device/1720971 | 14 --- .../deepseek-2-tmp/output/device/1721187 | 18 ---- .../deepseek-2-tmp/output/device/1721222 | 16 --- .../deepseek-2-tmp/output/device/1721224 | 15 --- .../deepseek-2-tmp/output/device/1722857 | 6 -- .../classifier/deepseek-2-tmp/output/device/1731 | 13 --- .../deepseek-2-tmp/output/device/1731347 | 31 ------ .../deepseek-2-tmp/output/device/1731588 | 14 --- .../deepseek-2-tmp/output/device/1733720 | 56 ---------- .../deepseek-2-tmp/output/device/1736376 | 11 -- .../deepseek-2-tmp/output/device/1740887 | 17 --- .../deepseek-2-tmp/output/device/1743191 | 42 -------- .../deepseek-2-tmp/output/device/1743337 | 5 - .../deepseek-2-tmp/output/device/1744654 | 4 - .../deepseek-2-tmp/output/device/1745354 | 13 --- .../classifier/deepseek-2-tmp/output/device/1746 | 4 - .../deepseek-2-tmp/output/device/1747056 | 26 ----- .../deepseek-2-tmp/output/device/1747393 | 4 - .../deepseek-2-tmp/output/device/1748434 | 8 -- .../deepseek-2-tmp/output/device/1749223 | 17 --- .../classifier/deepseek-2-tmp/output/device/1753 | 4 - .../deepseek-2-tmp/output/device/1753186 | 17 --- .../deepseek-2-tmp/output/device/1753309 | 57 ---------- .../deepseek-2-tmp/output/device/1753314 | 14 --- .../classifier/deepseek-2-tmp/output/device/1754 | 17 --- .../deepseek-2-tmp/output/device/1756728 | 17 --- .../classifier/deepseek-2-tmp/output/device/1759 | 11 -- .../deepseek-2-tmp/output/device/1759338 | 44 -------- .../deepseek-2-tmp/output/device/1759492 | 15 --- .../deepseek-2-tmp/output/device/1759522 | 57 ---------- .../classifier/deepseek-2-tmp/output/device/176 | 2 - .../deepseek-2-tmp/output/device/1760176 | 6 -- .../deepseek-2-tmp/output/device/1760262 | 32 ------ .../deepseek-2-tmp/output/device/1761798 | 28 ----- .../deepseek-2-tmp/output/device/1762707 | 17 --- .../classifier/deepseek-2-tmp/output/device/1764 | 2 - .../deepseek-2-tmp/output/device/1766904 | 17 --- .../classifier/deepseek-2-tmp/output/device/1767 | 4 - .../deepseek-2-tmp/output/device/1767200 | 10 -- .../deepseek-2-tmp/output/device/1769067 | 4 - .../deepseek-2-tmp/output/device/1769189 | 11 -- .../deepseek-2-tmp/output/device/1771042 | 15 --- .../deepseek-2-tmp/output/device/1772075 | 13 --- .../deepseek-2-tmp/output/device/1772086 | 4 - .../deepseek-2-tmp/output/device/1777232 | 11 -- .../deepseek-2-tmp/output/device/1777235 | 4 - .../deepseek-2-tmp/output/device/1777315 | 73 ------------- .../deepseek-2-tmp/output/device/1777777 | 12 --- .../deepseek-2-tmp/output/device/1779017 | 44 -------- .../deepseek-2-tmp/output/device/1779120 | 19 ---- .../deepseek-2-tmp/output/device/1782107 | 12 --- .../deepseek-2-tmp/output/device/1785972 | 49 --------- .../deepseek-2-tmp/output/device/1786343 | 37 ------- .../classifier/deepseek-2-tmp/output/device/179 | 2 - .../deepseek-2-tmp/output/device/1790975 | 18 ---- .../deepseek-2-tmp/output/device/1791947 | 15 --- .../deepseek-2-tmp/output/device/1792523 | 51 --------- .../deepseek-2-tmp/output/device/1793016 | 23 ---- .../deepseek-2-tmp/output/device/1793275 | 27 ----- .../deepseek-2-tmp/output/device/1793635 | 7 -- .../classifier/deepseek-2-tmp/output/device/1794 | 28 ----- .../deepseek-2-tmp/output/device/1794187 | 15 --- .../deepseek-2-tmp/output/device/1794202 | 4 - .../deepseek-2-tmp/output/device/1794950 | 84 --------------- .../deepseek-2-tmp/output/device/1795527 | 68 ------------ .../deepseek-2-tmp/output/device/1798434 | 6 -- .../deepseek-2-tmp/output/device/1799919 | 14 --- .../deepseek-2-tmp/output/device/1801674 | 53 --------- .../deepseek-2-tmp/output/device/1806114 | 30 ------ .../deepseek-2-tmp/output/device/1806824 | 10 -- .../deepseek-2-tmp/output/device/1809075 | 32 ------ .../deepseek-2-tmp/output/device/1809546 | 45 -------- .../deepseek-2-tmp/output/device/1809665 | 31 ------ .../deepseek-2-tmp/output/device/1809684 | 27 ----- .../deepseek-2-tmp/output/device/1810975 | 25 ----- .../classifier/deepseek-2-tmp/output/device/1811 | 37 ------- .../deepseek-2-tmp/output/device/1811543 | 73 ------------- .../deepseek-2-tmp/output/device/1811653 | 42 -------- .../deepseek-2-tmp/output/device/1811758 | 6 -- .../classifier/deepseek-2-tmp/output/device/1815 | 83 --------------- .../deepseek-2-tmp/output/device/1815413 | 28 ----- .../deepseek-2-tmp/output/device/1815445 | 16 --- .../deepseek-2-tmp/output/device/1815721 | 15 --- .../deepseek-2-tmp/output/device/1815993 | 30 ------ .../deepseek-2-tmp/output/device/1816052 | 72 ------------- .../deepseek-2-tmp/output/device/1816189 | 27 ----- .../deepseek-2-tmp/output/device/1816614 | 24 ----- .../deepseek-2-tmp/output/device/1816805 | 13 --- .../deepseek-2-tmp/output/device/1817525 | 79 -------------- .../classifier/deepseek-2-tmp/output/device/182 | 2 - .../deepseek-2-tmp/output/device/1821054 | 5 - .../deepseek-2-tmp/output/device/1823169 | 6 -- .../deepseek-2-tmp/output/device/1824744 | 8 -- .../deepseek-2-tmp/output/device/1826422 | 50 --------- .../deepseek-2-tmp/output/device/1828272 | 22 ---- .../deepseek-2-tmp/output/device/1828508 | 25 ----- .../deepseek-2-tmp/output/device/1829498 | 18 ---- .../classifier/deepseek-2-tmp/output/device/183 | 2 - .../deepseek-2-tmp/output/device/1833661 | 20 ---- .../deepseek-2-tmp/output/device/1834113 | 48 --------- .../deepseek-2-tmp/output/device/1835827 | 6 -- .../deepseek-2-tmp/output/device/1836855 | 33 ------ .../deepseek-2-tmp/output/device/1839060 | 19 ---- .../deepseek-2-tmp/output/device/1839807 | 49 --------- .../deepseek-2-tmp/output/device/1842530 | 62 ----------- .../deepseek-2-tmp/output/device/1842774 | 4 - .../deepseek-2-tmp/output/device/1842787 | 82 -------------- .../classifier/deepseek-2-tmp/output/device/1843 | 16 --- .../deepseek-2-tmp/output/device/1843711 | 12 --- .../deepseek-2-tmp/output/device/1845580 | 10 -- .../deepseek-2-tmp/output/device/1846451 | 19 ---- .../deepseek-2-tmp/output/device/1847793 | 46 -------- .../deepseek-2-tmp/output/device/1847861 | 31 ------ .../deepseek-2-tmp/output/device/1848231 | 18 ---- .../classifier/deepseek-2-tmp/output/device/1849 | 72 ------------- .../deepseek-2-tmp/output/device/1849894 | 45 -------- .../deepseek-2-tmp/output/device/1850570 | 38 ------- .../deepseek-2-tmp/output/device/1851547 | 21 ---- .../deepseek-2-tmp/output/device/1851552 | 16 --- .../deepseek-2-tmp/output/device/1851664 | 7 -- .../deepseek-2-tmp/output/device/1851972 | 60 ----------- .../deepseek-2-tmp/output/device/1853898 | 25 ----- .../classifier/deepseek-2-tmp/output/device/1856 | 14 --- .../deepseek-2-tmp/output/device/1856724 | 19 ---- .../deepseek-2-tmp/output/device/1856834 | 28 ----- .../deepseek-2-tmp/output/device/1859021 | 33 ------ .../deepseek-2-tmp/output/device/1859359 | 28 ----- .../deepseek-2-tmp/output/device/1859418 | 27 ----- .../deepseek-2-tmp/output/device/1859916 | 53 --------- .../deepseek-2-tmp/output/device/1860759 | 16 --- .../deepseek-2-tmp/output/device/1861692 | 4 - .../deepseek-2-tmp/output/device/1862619 | 15 --- .../deepseek-2-tmp/output/device/1863333 | 73 ------------- .../deepseek-2-tmp/output/device/1863441 | 9 -- .../deepseek-2-tmp/output/device/1863710 | 10 -- .../deepseek-2-tmp/output/device/1865626 | 26 ----- .../classifier/deepseek-2-tmp/output/device/1866 | 2 - .../deepseek-2-tmp/output/device/1866792 | 62 ----------- .../deepseek-2-tmp/output/device/1867519 | 48 --------- .../deepseek-2-tmp/output/device/1868116 | 44 -------- .../deepseek-2-tmp/output/device/1868617 | 16 --- .../deepseek-2-tmp/output/device/1869006 | 26 ----- .../deepseek-2-tmp/output/device/1869426 | 35 ------ .../deepseek-2-tmp/output/device/1871270 | 35 ------ .../deepseek-2-tmp/output/device/1873338 | 6 -- .../deepseek-2-tmp/output/device/1873769 | 12 --- .../deepseek-2-tmp/output/device/1875080 | 10 -- .../deepseek-2-tmp/output/device/1877418 | 7 -- .../deepseek-2-tmp/output/device/1878136 | 45 -------- .../deepseek-2-tmp/output/device/1878253 | 57 ---------- .../deepseek-2-tmp/output/device/1878255 | 39 ------- .../classifier/deepseek-2-tmp/output/device/1880 | 14 --- .../deepseek-2-tmp/output/device/1880424 | 41 ------- .../deepseek-2-tmp/output/device/1880822 | 4 - .../deepseek-2-tmp/output/device/1881231 | 32 ------ .../deepseek-2-tmp/output/device/1882350 | 37 ------- .../deepseek-2-tmp/output/device/1882787 | 59 ----------- .../deepseek-2-tmp/output/device/1883729 | 16 --- .../deepseek-2-tmp/output/device/1883732 | 16 --- .../deepseek-2-tmp/output/device/1883733 | 16 --- .../deepseek-2-tmp/output/device/1884169 | 6 -- .../deepseek-2-tmp/output/device/1884684 | 40 ------- .../deepseek-2-tmp/output/device/1884693 | 56 ---------- .../deepseek-2-tmp/output/device/1884831 | 22 ---- .../classifier/deepseek-2-tmp/output/device/1885 | 25 ----- .../deepseek-2-tmp/output/device/1887641 | 8 -- .../deepseek-2-tmp/output/device/1887745 | 26 ----- .../deepseek-2-tmp/output/device/1888417 | 6 -- .../deepseek-2-tmp/output/device/1888663 | 14 --- .../classifier/deepseek-2-tmp/output/device/1889 | 48 --------- .../deepseek-2-tmp/output/device/1890152 | 56 ---------- .../deepseek-2-tmp/output/device/1890311 | 51 --------- .../deepseek-2-tmp/output/device/1890333 | 24 ----- .../deepseek-2-tmp/output/device/1890360 | 71 ------------- .../deepseek-2-tmp/output/device/1890775 | 15 --- .../deepseek-2-tmp/output/device/1891830 | 35 ------ .../classifier/deepseek-2-tmp/output/device/1892 | 34 ------ .../deepseek-2-tmp/output/device/1892581 | 43 -------- .../deepseek-2-tmp/output/device/1892761 | 11 -- .../classifier/deepseek-2-tmp/output/device/1893 | 14 --- .../deepseek-2-tmp/output/device/1893634 | 11 -- .../classifier/deepseek-2-tmp/output/device/1894 | 12 --- .../deepseek-2-tmp/output/device/1894071 | 20 ---- .../deepseek-2-tmp/output/device/1894617 | 24 ----- .../deepseek-2-tmp/output/device/1895895 | 30 ------ .../deepseek-2-tmp/output/device/1896317 | 58 ---------- .../deepseek-2-tmp/output/device/1897568 | 11 -- .../deepseek-2-tmp/output/device/1897680 | 15 --- .../classifier/deepseek-2-tmp/output/device/1900 | 2 - .../deepseek-2-tmp/output/device/1900122 | 111 ------------------- .../deepseek-2-tmp/output/device/1900918 | 15 --- .../deepseek-2-tmp/output/device/1900919 | 15 --- .../deepseek-2-tmp/output/device/1901440 | 18 ---- .../deepseek-2-tmp/output/device/1901532 | 20 ---- .../deepseek-2-tmp/output/device/1902306 | 11 -- .../deepseek-2-tmp/output/device/1903752 | 11 -- .../deepseek-2-tmp/output/device/1904490 | 25 ----- .../deepseek-2-tmp/output/device/1904652 | 51 --------- .../deepseek-2-tmp/output/device/1905226 | 16 --- .../deepseek-2-tmp/output/device/1905297 | 30 ------ .../deepseek-2-tmp/output/device/1905444 | 47 -------- .../deepseek-2-tmp/output/device/1906155 | 14 --- .../deepseek-2-tmp/output/device/1906181 | 14 --- .../deepseek-2-tmp/output/device/1906184 | 29 ----- .../deepseek-2-tmp/output/device/1906295 | 12 --- .../deepseek-2-tmp/output/device/1906463 | 19 ---- .../deepseek-2-tmp/output/device/1907042 | 37 ------- .../deepseek-2-tmp/output/device/1907427 | 13 --- .../deepseek-2-tmp/output/device/1907497 | 59 ----------- .../deepseek-2-tmp/output/device/1907776 | 21 ---- .../deepseek-2-tmp/output/device/1907926 | 6 -- .../deepseek-2-tmp/output/device/1908062 | 73 ------------- .../deepseek-2-tmp/output/device/1908450 | 47 -------- .../deepseek-2-tmp/output/device/1908832 | 63 ----------- .../deepseek-2-tmp/output/device/1909261 | 36 ------- .../deepseek-2-tmp/output/device/1910586 | 46 -------- .../deepseek-2-tmp/output/device/1910603 | 45 -------- .../deepseek-2-tmp/output/device/1911188 | 15 --- .../deepseek-2-tmp/output/device/1912846 | 18 ---- .../deepseek-2-tmp/output/device/1912857 | 12 --- .../deepseek-2-tmp/output/device/1913344 | 10 -- .../deepseek-2-tmp/output/device/1913667 | 37 ------- .../deepseek-2-tmp/output/device/1913917 | 35 ------ .../deepseek-2-tmp/output/device/1913926 | 30 ------ .../deepseek-2-tmp/output/device/1914535 | 6 -- .../deepseek-2-tmp/output/device/1916501 | 31 ------ .../deepseek-2-tmp/output/device/1917394 | 40 ------- .../deepseek-2-tmp/output/device/1920013 | 20 ---- .../deepseek-2-tmp/output/device/1921061 | 8 -- .../deepseek-2-tmp/output/device/1921635 | 35 ------ .../deepseek-2-tmp/output/device/1922252 | 8 -- .../deepseek-2-tmp/output/device/1922325 | 24 ----- .../deepseek-2-tmp/output/device/1922391 | 57 ---------- .../deepseek-2-tmp/output/device/1922611 | 44 -------- .../deepseek-2-tmp/output/device/1923663 | 20 ---- .../deepseek-2-tmp/output/device/1924738 | 27 ----- .../deepseek-2-tmp/output/device/1925109 | 18 ---- .../deepseek-2-tmp/output/device/1925496 | 65 ------------ .../deepseek-2-tmp/output/device/1925966 | 34 ------ .../deepseek-2-tmp/output/device/1926111 | 86 --------------- .../deepseek-2-tmp/output/device/1926231 | 38 ------- .../deepseek-2-tmp/output/device/1927408 | 49 --------- .../classifier/deepseek-2-tmp/output/device/1933 | 42 -------- .../classifier/deepseek-2-tmp/output/device/1935 | 6 -- .../classifier/deepseek-2-tmp/output/device/1940 | 21 ---- .../classifier/deepseek-2-tmp/output/device/1943 | 25 ----- .../classifier/deepseek-2-tmp/output/device/1982 | 10 -- .../classifier/deepseek-2-tmp/output/device/2001 | 44 -------- .../classifier/deepseek-2-tmp/output/device/2018 | 19 ---- .../classifier/deepseek-2-tmp/output/device/2025 | 27 ----- .../classifier/deepseek-2-tmp/output/device/2031 | 14 --- .../classifier/deepseek-2-tmp/output/device/2033 | 2 - .../classifier/deepseek-2-tmp/output/device/2046 | 2 - .../classifier/deepseek-2-tmp/output/device/2049 | 12 --- .../classifier/deepseek-2-tmp/output/device/2061 | 14 --- .../classifier/deepseek-2-tmp/output/device/2075 | 11 -- .../classifier/deepseek-2-tmp/output/device/2081 | 10 -- .../classifier/deepseek-2-tmp/output/device/2086 | 16 --- .../classifier/deepseek-2-tmp/output/device/2117 | 28 ----- .../classifier/deepseek-2-tmp/output/device/2126 | 2 - .../classifier/deepseek-2-tmp/output/device/2178 | 18 ---- .../classifier/deepseek-2-tmp/output/device/2186 | 35 ------ .../classifier/deepseek-2-tmp/output/device/2211 | 28 ----- .../classifier/deepseek-2-tmp/output/device/2212 | 18 ---- .../classifier/deepseek-2-tmp/output/device/2240 | 5 - .../classifier/deepseek-2-tmp/output/device/2272 | 22 ---- .../classifier/deepseek-2-tmp/output/device/2306 | 2 - .../classifier/deepseek-2-tmp/output/device/2308 | 80 -------------- .../classifier/deepseek-2-tmp/output/device/2342 | 2 - .../classifier/deepseek-2-tmp/output/device/2350 | 15 --- .../classifier/deepseek-2-tmp/output/device/2357 | 19 ---- .../classifier/deepseek-2-tmp/output/device/2359 | 33 ------ .../classifier/deepseek-2-tmp/output/device/2388 | 18 ---- .../classifier/deepseek-2-tmp/output/device/2395 | 61 ----------- .../classifier/deepseek-2-tmp/output/device/2399 | 28 ----- .../classifier/deepseek-2-tmp/output/device/241119 | 20 ---- .../classifier/deepseek-2-tmp/output/device/2415 | 54 ---------- .../classifier/deepseek-2-tmp/output/device/2428 | 30 ------ .../classifier/deepseek-2-tmp/output/device/2449 | 2 - .../classifier/deepseek-2-tmp/output/device/2455 | 9 -- .../classifier/deepseek-2-tmp/output/device/2471 | 2 - .../classifier/deepseek-2-tmp/output/device/2513 | 14 --- .../classifier/deepseek-2-tmp/output/device/2521 | 17 --- .../classifier/deepseek-2-tmp/output/device/2561 | 40 ------- .../classifier/deepseek-2-tmp/output/device/2576 | 2 - .../classifier/deepseek-2-tmp/output/device/259 | 2 - .../classifier/deepseek-2-tmp/output/device/2615 | 11 -- .../classifier/deepseek-2-tmp/output/device/2635 | 13 --- .../classifier/deepseek-2-tmp/output/device/2645 | 24 ----- .../classifier/deepseek-2-tmp/output/device/2651 | 9 -- .../classifier/deepseek-2-tmp/output/device/2659 | 2 - .../classifier/deepseek-2-tmp/output/device/2703 | 41 ------- .../classifier/deepseek-2-tmp/output/device/2705 | 18 ---- .../classifier/deepseek-2-tmp/output/device/2707 | 11 -- .../classifier/deepseek-2-tmp/output/device/2714 | 8 -- .../classifier/deepseek-2-tmp/output/device/2716 | 8 -- .../classifier/deepseek-2-tmp/output/device/272 | 2 - .../classifier/deepseek-2-tmp/output/device/2722 | 49 --------- .../classifier/deepseek-2-tmp/output/device/2732 | 40 ------- .../classifier/deepseek-2-tmp/output/device/2765 | 2 - .../classifier/deepseek-2-tmp/output/device/2777 | 60 ----------- .../classifier/deepseek-2-tmp/output/device/278 | 2 - .../classifier/deepseek-2-tmp/output/device/2801 | 2 - .../classifier/deepseek-2-tmp/output/device/2805 | 23 ---- .../classifier/deepseek-2-tmp/output/device/2843 | 34 ------ .../classifier/deepseek-2-tmp/output/device/2845 | 33 ------ .../classifier/deepseek-2-tmp/output/device/2863 | 2 - .../classifier/deepseek-2-tmp/output/device/2872 | 2 - .../classifier/deepseek-2-tmp/output/device/2880 | 4 - .../classifier/deepseek-2-tmp/output/device/2937 | 2 - .../classifier/deepseek-2-tmp/output/device/2939 | 2 - .../classifier/deepseek-2-tmp/output/device/2945 | 30 ------ .../classifier/deepseek-2-tmp/output/device/2947 | 11 -- .../classifier/deepseek-2-tmp/output/device/2953 | 67 ------------ .../classifier/deepseek-2-tmp/output/device/2963 | 25 ----- .../classifier/deepseek-2-tmp/output/device/2985 | 9 -- .../classifier/deepseek-2-tmp/output/device/305 | 2 - .../classifier/deepseek-2-tmp/output/device/307 | 2 - .../classifier/deepseek-2-tmp/output/device/327 | 2 - .../classifier/deepseek-2-tmp/output/device/332 | 2 - .../classifier/deepseek-2-tmp/output/device/350 | 2 - .../classifier/deepseek-2-tmp/output/device/360 | 2 - .../classifier/deepseek-2-tmp/output/device/388 | 2 - .../classifier/deepseek-2-tmp/output/device/392 | 2 - .../classifier/deepseek-2-tmp/output/device/399 | 2 - .../classifier/deepseek-2-tmp/output/device/401 | 2 - .../classifier/deepseek-2-tmp/output/device/406 | 2 - .../classifier/deepseek-2-tmp/output/device/413 | 2 - .../classifier/deepseek-2-tmp/output/device/424450 | 15 --- .../classifier/deepseek-2-tmp/output/device/433 | 2 - .../classifier/deepseek-2-tmp/output/device/450 | 2 - .../classifier/deepseek-2-tmp/output/device/451 | 2 - .../classifier/deepseek-2-tmp/output/device/455 | 35 ------ .../classifier/deepseek-2-tmp/output/device/462 | 44 -------- .../classifier/deepseek-2-tmp/output/device/464 | 2 - .../classifier/deepseek-2-tmp/output/device/469 | 2 - .../classifier/deepseek-2-tmp/output/device/471 | 65 ------------ .../classifier/deepseek-2-tmp/output/device/484 | 2 - .../classifier/deepseek-2-tmp/output/device/485 | 2 - .../classifier/deepseek-2-tmp/output/device/486 | 2 - .../classifier/deepseek-2-tmp/output/device/487 | 2 - .../classifier/deepseek-2-tmp/output/device/492 | 28 ----- .../classifier/deepseek-2-tmp/output/device/498417 | 15 --- .../classifier/deepseek-2-tmp/output/device/521 | 2 - .../classifier/deepseek-2-tmp/output/device/526 | 16 --- .../classifier/deepseek-2-tmp/output/device/531 | 2 - .../classifier/deepseek-2-tmp/output/device/541 | 2 - .../classifier/deepseek-2-tmp/output/device/542 | 2 - .../classifier/deepseek-2-tmp/output/device/543 | 2 - .../classifier/deepseek-2-tmp/output/device/545089 | 18 ---- .../classifier/deepseek-2-tmp/output/device/546 | 2 - .../classifier/deepseek-2-tmp/output/device/548 | 2 - .../classifier/deepseek-2-tmp/output/device/552 | 2 - .../classifier/deepseek-2-tmp/output/device/556 | 20 ---- results/classifier/deepseek-2-tmp/output/device/56 | 2 - .../classifier/deepseek-2-tmp/output/device/583 | 2 - .../classifier/deepseek-2-tmp/output/device/584146 | 8 -- .../classifier/deepseek-2-tmp/output/device/588688 | 8 -- .../classifier/deepseek-2-tmp/output/device/588693 | 4 - results/classifier/deepseek-2-tmp/output/device/59 | 2 - .../classifier/deepseek-2-tmp/output/device/591666 | 19 ---- .../classifier/deepseek-2-tmp/output/device/602544 | 7 -- .../classifier/deepseek-2-tmp/output/device/604 | 2 - .../classifier/deepseek-2-tmp/output/device/612452 | 16 --- .../classifier/deepseek-2-tmp/output/device/613529 | 14 --- results/classifier/deepseek-2-tmp/output/device/62 | 2 - .../classifier/deepseek-2-tmp/output/device/628082 | 8 -- .../classifier/deepseek-2-tmp/output/device/648 | 2 - .../classifier/deepseek-2-tmp/output/device/657329 | 48 --------- .../classifier/deepseek-2-tmp/output/device/659 | 42 -------- results/classifier/deepseek-2-tmp/output/device/66 | 2 - .../classifier/deepseek-2-tmp/output/device/660 | 10 -- .../classifier/deepseek-2-tmp/output/device/660060 | 33 ------ .../classifier/deepseek-2-tmp/output/device/663 | 12 --- .../classifier/deepseek-2-tmp/output/device/666 | 8 -- .../classifier/deepseek-2-tmp/output/device/669 | 24 ----- .../classifier/deepseek-2-tmp/output/device/670769 | 15 --- .../classifier/deepseek-2-tmp/output/device/674740 | 16 --- .../classifier/deepseek-2-tmp/output/device/678 | 48 --------- .../classifier/deepseek-2-tmp/output/device/680 | 2 - .../classifier/deepseek-2-tmp/output/device/684 | 2 - .../classifier/deepseek-2-tmp/output/device/685096 | 16 --- .../classifier/deepseek-2-tmp/output/device/697510 | 34 ------ .../classifier/deepseek-2-tmp/output/device/703 | 18 ---- .../classifier/deepseek-2-tmp/output/device/707 | 63 ----------- .../classifier/deepseek-2-tmp/output/device/712337 | 43 -------- .../classifier/deepseek-2-tmp/output/device/716 | 4 - .../classifier/deepseek-2-tmp/output/device/721659 | 17 --- .../classifier/deepseek-2-tmp/output/device/721825 | 77 -------------- .../classifier/deepseek-2-tmp/output/device/727134 | 4 - .../classifier/deepseek-2-tmp/output/device/740895 | 65 ------------ .../classifier/deepseek-2-tmp/output/device/764 | 46 -------- .../classifier/deepseek-2-tmp/output/device/764252 | 4 - .../classifier/deepseek-2-tmp/output/device/772275 | 29 ----- .../classifier/deepseek-2-tmp/output/device/775 | 5 - .../classifier/deepseek-2-tmp/output/device/778 | 2 - .../classifier/deepseek-2-tmp/output/device/778032 | 71 ------------- .../classifier/deepseek-2-tmp/output/device/779151 | 17 --- .../classifier/deepseek-2-tmp/output/device/782 | 6 -- .../classifier/deepseek-2-tmp/output/device/786208 | 10 -- .../classifier/deepseek-2-tmp/output/device/786209 | 8 -- .../classifier/deepseek-2-tmp/output/device/786211 | 4 - .../classifier/deepseek-2-tmp/output/device/800 | 26 ----- .../classifier/deepseek-2-tmp/output/device/802 | 27 ----- .../classifier/deepseek-2-tmp/output/device/804517 | 45 -------- .../classifier/deepseek-2-tmp/output/device/810588 | 6 -- .../classifier/deepseek-2-tmp/output/device/811 | 2 - .../classifier/deepseek-2-tmp/output/device/811683 | 25 ----- .../classifier/deepseek-2-tmp/output/device/813546 | 6 -- .../classifier/deepseek-2-tmp/output/device/818673 | 9 -- .../classifier/deepseek-2-tmp/output/device/820 | 14 --- .../classifier/deepseek-2-tmp/output/device/821078 | 14 --- .../classifier/deepseek-2-tmp/output/device/822408 | 46 -------- .../classifier/deepseek-2-tmp/output/device/830 | 2 - .../classifier/deepseek-2-tmp/output/device/839790 | 18 ---- results/classifier/deepseek-2-tmp/output/device/84 | 2 - .../classifier/deepseek-2-tmp/output/device/877498 | 4 - .../classifier/deepseek-2-tmp/output/device/878 | 43 -------- .../classifier/deepseek-2-tmp/output/device/884401 | 56 ---------- .../classifier/deepseek-2-tmp/output/device/893367 | 11 -- .../classifier/deepseek-2-tmp/output/device/895 | 39 ------- .../classifier/deepseek-2-tmp/output/device/897466 | 22 ---- .../classifier/deepseek-2-tmp/output/device/904617 | 16 --- .../classifier/deepseek-2-tmp/output/device/905 | 2 - .../classifier/deepseek-2-tmp/output/device/906804 | 42 -------- .../classifier/deepseek-2-tmp/output/device/912983 | 45 -------- .../classifier/deepseek-2-tmp/output/device/924943 | 15 --- .../classifier/deepseek-2-tmp/output/device/932487 | 57 ---------- .../classifier/deepseek-2-tmp/output/device/932490 | 10 -- .../classifier/deepseek-2-tmp/output/device/933 | 27 ----- .../classifier/deepseek-2-tmp/output/device/938552 | 24 ----- .../classifier/deepseek-2-tmp/output/device/940 | 2 - .../classifier/deepseek-2-tmp/output/device/946043 | 13 --- .../classifier/deepseek-2-tmp/output/device/959992 | 44 -------- .../classifier/deepseek-2-tmp/output/device/960378 | 46 -------- .../classifier/deepseek-2-tmp/output/device/961757 | 20 ---- .../classifier/deepseek-2-tmp/output/device/965 | 2 - results/classifier/deepseek-2-tmp/output/device/97 | 2 - .../classifier/deepseek-2-tmp/output/device/972 | 2 - .../classifier/deepseek-2-tmp/output/device/990364 | 19 ---- 698 files changed, 15915 deletions(-) delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1004050 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1013241 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1013691 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1014099 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1014681 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1015 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1018 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1026176 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1031955 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1038136 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1047470 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1049 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1055090 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1062220 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1070762 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1071 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1073952 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1076 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1077708 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1077838 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1086782 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1087114 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1088617 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1089006 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1090 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1090558 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1090604 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1093360 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1096713 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1096714 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1101210 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1106 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1110 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1112 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/112 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1134 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1139 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1162227 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1162644 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1168 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1173490 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1174 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1175 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1175513 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1176 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/118 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1181796 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1185888 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1186303 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1187529 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1188018 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1188991 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1191 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1191326 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1193 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1194954 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1196145 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1198350 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1200212 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1207228 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1219234 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1220 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1222034 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1223467 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1223477 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1225187 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1226 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1230232 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1234 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1237 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1237625 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1242765 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1248469 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1250 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1256122 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1257334 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1267520 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1268596 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1268671 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1269628 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1276879 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1280521 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1284874 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1288 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1292037 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1294 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1295587 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1300 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1306818 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1307281 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1311 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1314857 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1318 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1320360 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1321684 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/133 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1333216 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1334397 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1336123 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1338957 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1342 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1352179 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1352465 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1353456 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1354 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1354279 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1356 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1366 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1367365 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1368178 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1368204 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1373362 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1378407 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1380 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1381879 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1386478 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1390520 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1391 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1392 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1392504 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1393 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1393440 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1399943 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1403 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1404 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1404610 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1407454 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1407808 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1413 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1422285 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1423668 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1426593 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1428958 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/143 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1435973 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1437970 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/144 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1440843 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1442 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1445633 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1451 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1453025 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1457 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1458 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1460 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1465 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1468 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/147 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1470536 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1476183 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1481750 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1483 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1486768 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1488363 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1490 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1490886 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1499908 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1500175 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1502613 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1504 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1509336 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1511887 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1518969 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1519 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1521 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1522 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1523246 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1526 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1529449 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1529859 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1530035 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1530278 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1543057 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1544524 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1550743 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1563 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1568621 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1569 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/157 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1572959 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1575561 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1576 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1576347 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1577 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1579306 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1579645 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/158 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1580459 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1580586 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1581308 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1583 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1583421 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1585433 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1585971 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1586611 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1586613 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1587065 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1587970 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1592336 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1596832 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1597 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1598 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1600563 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1603693 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1603779 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1608802 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1614 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1618265 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1618431 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1622582 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1623998 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1624726 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1625 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1625216 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1626207 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1630723 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1634069 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1637693 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1637974 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1639322 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1639791 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1639983 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1643342 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1645 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1646 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1646610 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1648726 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1654 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1656234 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1658506 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1661758 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1667613 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1674114 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1675332 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1675333 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1677247 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1677492 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1680679 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1681398 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1681404 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1681439 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1681688 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1688231 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1689003 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1691 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1691379 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1693050 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1699628 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1702621 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1706058 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1707587 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1708551 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1713 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1714538 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1715296 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1716132 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1718118 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1719689 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1720971 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1721187 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1721222 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1721224 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1722857 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1731 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1731347 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1731588 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1733720 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1736376 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1740887 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1743191 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1743337 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1744654 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1745354 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1746 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1747056 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1747393 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1748434 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1749223 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1753 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1753186 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1753309 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1753314 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1754 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1756728 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1759 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1759338 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1759492 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1759522 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/176 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1760176 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1760262 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1761798 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1762707 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1764 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1766904 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1767 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1767200 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1769067 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1769189 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1771042 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1772075 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1772086 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1777232 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1777235 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1777315 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1777777 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1779017 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1779120 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1782107 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1785972 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1786343 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/179 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1790975 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1791947 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1792523 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1793016 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1793275 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1793635 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1794 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1794187 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1794202 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1794950 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1795527 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1798434 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1799919 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1801674 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1806114 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1806824 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1809075 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1809546 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1809665 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1809684 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1810975 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1811 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1811543 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1811653 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1811758 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1815 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1815413 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1815445 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1815721 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1815993 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1816052 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1816189 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1816614 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1816805 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1817525 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/182 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1821054 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1823169 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1824744 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1826422 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1828272 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1828508 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1829498 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/183 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1833661 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1834113 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1835827 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1836855 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1839060 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1839807 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1842530 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1842774 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1842787 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1843 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1843711 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1845580 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1846451 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1847793 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1847861 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1848231 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1849 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1849894 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1850570 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1851547 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1851552 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1851664 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1851972 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1853898 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1856 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1856724 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1856834 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1859021 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1859359 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1859418 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1859916 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1860759 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1861692 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1862619 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1863333 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1863441 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1863710 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1865626 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1866 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1866792 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1867519 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1868116 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1868617 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1869006 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1869426 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1871270 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1873338 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1873769 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1875080 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1877418 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1878136 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1878253 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1878255 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1880 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1880424 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1880822 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1881231 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1882350 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1882787 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1883729 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1883732 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1883733 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1884169 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1884684 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1884693 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1884831 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1885 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1887641 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1887745 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1888417 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1888663 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1889 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1890152 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1890311 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1890333 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1890360 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1890775 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1891830 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1892 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1892581 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1892761 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1893 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1893634 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1894 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1894071 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1894617 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1895895 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1896317 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1897568 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1897680 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1900 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1900122 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1900918 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1900919 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1901440 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1901532 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1902306 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1903752 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1904490 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1904652 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1905226 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1905297 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1905444 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1906155 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1906181 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1906184 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1906295 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1906463 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1907042 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1907427 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1907497 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1907776 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1907926 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1908062 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1908450 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1908832 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1909261 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1910586 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1910603 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1911188 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1912846 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1912857 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1913344 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1913667 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1913917 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1913926 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1914535 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1916501 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1917394 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1920013 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1921061 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1921635 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1922252 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1922325 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1922391 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1922611 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1923663 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1924738 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1925109 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1925496 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1925966 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1926111 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1926231 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1927408 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1933 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1935 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1940 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1943 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/1982 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/2001 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/2018 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/2025 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/2031 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/2033 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/2046 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/2049 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/2061 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/2075 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/2081 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/2086 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/2117 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/2126 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/2178 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/2186 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/2211 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/2212 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/2240 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/2272 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/2306 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/2308 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/2342 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/2350 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/2357 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/2359 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/2388 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/2395 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/2399 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/241119 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/2415 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/2428 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/2449 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/2455 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/2471 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/2513 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/2521 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/2561 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/2576 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/259 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/2615 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/2635 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/2645 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/2651 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/2659 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/2703 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/2705 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/2707 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/2714 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/2716 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/272 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/2722 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/2732 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/2765 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/2777 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/278 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/2801 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/2805 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/2843 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/2845 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/2863 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/2872 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/2880 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/2937 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/2939 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/2945 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/2947 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/2953 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/2963 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/2985 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/305 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/307 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/327 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/332 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/350 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/360 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/388 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/392 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/399 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/401 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/406 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/413 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/424450 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/433 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/450 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/451 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/455 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/462 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/464 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/469 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/471 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/484 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/485 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/486 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/487 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/492 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/498417 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/521 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/526 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/531 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/541 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/542 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/543 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/545089 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/546 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/548 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/552 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/556 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/56 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/583 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/584146 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/588688 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/588693 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/59 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/591666 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/602544 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/604 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/612452 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/613529 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/62 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/628082 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/648 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/657329 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/659 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/66 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/660 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/660060 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/663 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/666 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/669 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/670769 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/674740 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/678 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/680 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/684 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/685096 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/697510 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/703 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/707 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/712337 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/716 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/721659 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/721825 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/727134 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/740895 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/764 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/764252 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/772275 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/775 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/778 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/778032 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/779151 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/782 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/786208 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/786209 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/786211 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/800 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/802 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/804517 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/810588 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/811 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/811683 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/813546 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/818673 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/820 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/821078 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/822408 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/830 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/839790 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/84 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/877498 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/878 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/884401 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/893367 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/895 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/897466 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/904617 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/905 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/906804 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/912983 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/924943 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/932487 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/932490 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/933 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/938552 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/940 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/946043 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/959992 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/960378 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/961757 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/965 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/97 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/972 delete mode 100644 results/classifier/deepseek-2-tmp/output/device/990364 (limited to 'results/classifier/deepseek-2-tmp/output/device') diff --git a/results/classifier/deepseek-2-tmp/output/device/1004050 b/results/classifier/deepseek-2-tmp/output/device/1004050 deleted file mode 100644 index a0e0bb8c..00000000 --- a/results/classifier/deepseek-2-tmp/output/device/1004050 +++ /dev/null @@ -1,17 +0,0 @@ - -qemu-system-ppc64 by default has non-working keyboard - -Compile qemu from git and do: - - ./ppc64-softmmu/qemu-system-ppc64 - -(ie. no parameters). It boots to an OpenBIOS prompt. However the keyboard doesn't work. After ~10 keypresses, qemu just says: - -usb-kbd: warning: key event queue full -usb-kbd: warning: key event queue full -usb-kbd: warning: key event queue full -usb-kbd: warning: key event queue full - -There is no indication inside the guest that OpenBIOS is seeing keyboard events. - -Also there's no indication of what type of keyboard devices are available, nor what we should use. \ No newline at end of file diff --git a/results/classifier/deepseek-2-tmp/output/device/1013241 b/results/classifier/deepseek-2-tmp/output/device/1013241 deleted file mode 100644 index 6756f0cc..00000000 --- a/results/classifier/deepseek-2-tmp/output/device/1013241 +++ /dev/null @@ -1,27 +0,0 @@ - -qemu-system-ppc64 hanging occasionally in disk writes - -I found last week that qemu-system-ppc64 (from git) hangs occasionally -under load, and I have a reproducer for it now. Unfortunately the -reproducer really takes a long time to run -- usually I can get a hang -in under 12 hours. - -Here is the reproducer case: - - https://lists.fedoraproject.org/pipermail/ppc/2012-June/001698.html - -Notes: - -(1) Verified by one other person (other than me). Happens on both - ppc64 and x86-64 host. - -(2) Happens with both Fedora guest kernel 3.3.4-5.fc17.ppc64 and kernel - 3.5.0 that I compiled myself. The test case above contains 3.3.4-5. - -(3) Seems to be a problem in qemu, not the guest. The reason I think - this is because I tried to capture a backtrace of the hang using - remote gdb, but gdb just hung when trying to connect to qemu - (gdb connects fine before the bug happens). - -(4) Judging by guest messages, appears to be happening when writing - to the disk. \ No newline at end of file diff --git a/results/classifier/deepseek-2-tmp/output/device/1013691 b/results/classifier/deepseek-2-tmp/output/device/1013691 deleted file mode 100644 index 6f4668f9..00000000 --- a/results/classifier/deepseek-2-tmp/output/device/1013691 +++ /dev/null @@ -1,15 +0,0 @@ - -ppc64 + virtio-scsi: only first scsi disk shows up in the guest - -When adding two virtio-scsi targets to a single guest, only the first -disk is seen inside the guest. For some unknown reason the guest -doesn't enumerate the second disk. - -For full qemu-system-ppc64 command line and 'dmesg' output, see: - -http://lists.nongnu.org/archive/html/qemu-devel/2012-06/msg02430.html - -I have also tried this with Linus's git tree (3.5.0-rc2+ at time of writing), -same thing. - -In both cases I'm using qemu from git. \ No newline at end of file diff --git a/results/classifier/deepseek-2-tmp/output/device/1014099 b/results/classifier/deepseek-2-tmp/output/device/1014099 deleted file mode 100644 index 98979f07..00000000 --- a/results/classifier/deepseek-2-tmp/output/device/1014099 +++ /dev/null @@ -1,8 +0,0 @@ - -hw/esp.c does not properly deal with TEST_UNIT_READY in NetBSD/sparc - -The NetBSD ncr53c9x.c driver does a TEST_UNIT_READY command with SELATN but dma disabled sometimes (early during bus enumeration). This is fine, as the command will not produce nor consume any data, and works on real hardware. - -However, the qemu emulation does not allow this (for reasons I don't understand). - -The change below fixes the problem. \ No newline at end of file diff --git a/results/classifier/deepseek-2-tmp/output/device/1014681 b/results/classifier/deepseek-2-tmp/output/device/1014681 deleted file mode 100644 index 7ac3964f..00000000 --- a/results/classifier/deepseek-2-tmp/output/device/1014681 +++ /dev/null @@ -1,35 +0,0 @@ - -BSOD with newer host kernels (x64) and W2k8S guest (x64) - -Hallo, I attempted to move virtual machines from one host to another but got stuck with Windows-BSODs on the target host. The host-side console message is "virtio_ioport_write: unexpected address 0x13 value 0x1". Eventually there are overlaps to bug #990364, but I'm not sure. - -Host machine: 2x Opteron 4238 a 6 cores, 32GB RAM, Linux x86_64 -Guest machine(s): Windows 2008 Server R2 x64 - -I tried different combinations of component versions, but only kernel 2.6.34 could run the guests (but has other difficulties): - -host kernel Qemu-KVM paravirtualization guest paravirt driver -============================================= -2.6.34 1.0.1 virtio 0.1.15 ok - 0.1.22 ok - 0.1.prewhql ok - git 20120615 virtio 0.1.15 ok - 0.1.22 ok - 0.1.prewhql ok -============================================= -2.6.39 1.0.1 virtio 0.1.15 BSOD - git 20120615 virtio 0.1.15 BSOD -3.0.3 1.0.1 virtio 0.1.15 BSOD - git 20120615 virtio 0.1.15 BSOD -3.3.8 1.0.1 virtio 0.1.15 BSOD - git 20120615 virtio 0.1.15 BSOD - virtio-pci 0.1.15 BSOD -3.4.2 1.0.1 virtio 0.1.15 BSOD - 0.1.prewhql BSOD - virtio-pci 0.1.15 BSOD - git 20120615 virtio 0.1.15 BSOD - 0.1.prewhql BSOD - virtio-pci 0.1.15 BSOD -============================================= - -Run arguments are attached. Minidump follows immediately. \ No newline at end of file diff --git a/results/classifier/deepseek-2-tmp/output/device/1015 b/results/classifier/deepseek-2-tmp/output/device/1015 deleted file mode 100644 index be3717b1..00000000 --- a/results/classifier/deepseek-2-tmp/output/device/1015 +++ /dev/null @@ -1,2 +0,0 @@ - -qemu-7.0 there is no device "hostdev0" defined diff --git a/results/classifier/deepseek-2-tmp/output/device/1018 b/results/classifier/deepseek-2-tmp/output/device/1018 deleted file mode 100644 index 8635b71f..00000000 --- a/results/classifier/deepseek-2-tmp/output/device/1018 +++ /dev/null @@ -1,24 +0,0 @@ - -virtio-scsi-pci with iothread results in 100% CPU in qemu 7.0.0 -Description of problem: -Top reports constant 100% host CPU usage by `qemu-system-x86`. I have narrowed the issue down to the following section of the config: -``` - -object iothread,id=t0 \ - -device virtio-scsi-pci,iothread=t0,num_queues=4 \ -``` -If this is replaced by -``` - -device virtio-scsi-pci \ -``` -Then CPU usage is normal (near 0%). - -This problem doesn't appear with qemu 6.2.0 where CPU usage is near 0% even with iothread in the qemu options. -Steps to reproduce: -1. Download Kubuntu 22.04 LTS ISO (https://cdimage.ubuntu.com/kubuntu/releases/22.04/release/kubuntu-22.04-desktop-amd64.iso), -2. Create a root virtual drive for the guest with 'qemu-img create -f qcow2 -o cluster_size=4k kubuntu.img 256G', -3. Start the guest with the config given above, -4. Connect to the guest (using spicy for example, password 'p'), select "try kubuntu" in grub menu AND later in the GUI, let it boot to plasma desktop, monitor host CPU usage using 'top'. - -(there could be a faster way to reproduce it) -Additional information: - diff --git a/results/classifier/deepseek-2-tmp/output/device/1026176 b/results/classifier/deepseek-2-tmp/output/device/1026176 deleted file mode 100644 index c163b695..00000000 --- a/results/classifier/deepseek-2-tmp/output/device/1026176 +++ /dev/null @@ -1,22 +0,0 @@ - -unable to boot squashfs through mtd device - -Hi, - -I have built latest qemu archive qemu-1.1.1 to be sure of up to date source code. -I have then built buildroot squashfs image, which can be used correctly with cmdline like: - -qemu-system-i386 -m 64 -k fr -boot c -kernel images/bzImage -drive if=ide,file=images/rootfs.squashfs -append "root=/dev/sda" - -Then I wanted to modify cmdline to use real MTD device, like: - -qemu-system-i386 -m 64 -k fr -boot c -kernel images/bzImage -drive if=mtd,file=images/rootfs.squashfs -append "root=/dev/mtdblock0". - -But nothing was good under kernel. -Even if mtd0 is reported through qemu interface (Ctrl Alt+2), no device can be found under kernel even if all drivers are built to use it. - -Is this feature okay on qemu-1.1.1 ?? -did I do mistake in my cmdline?? - -thank you for your help. -regards, \ No newline at end of file diff --git a/results/classifier/deepseek-2-tmp/output/device/1031955 b/results/classifier/deepseek-2-tmp/output/device/1031955 deleted file mode 100644 index 3b05d428..00000000 --- a/results/classifier/deepseek-2-tmp/output/device/1031955 +++ /dev/null @@ -1,36 +0,0 @@ - -qemu-system-arm -M lm3s811evb fails - -I am trying out examples from StellarisWare. - -When I try the uart_echo example, that initially tries to talk to the -display, I get this: - - $ .../qemu-1.1.1/bin/qemu-system-arm -M lm3s811evb -kernel uart_echo/gcc/uart_echo.bin - qemu: hardware error: strllaris_i2c_read: Bad offset 0xfc0 - - CPU #0: - R00=00000001 R01=005b8d80 R02=00061a80 R03=007a11ff - R04=40020000 R05=005b8d80 R06=00000002 R07=00000000 - R08=00000000 R09=00000000 R10=00000000 R11=00000000 - R12=00000000 R13=200000d4 R14=00000995 R15=000009cc - PSR=20000173 --C- T svc32 - Aborted - -The example is located in boards/ek-lm3s811/uart_echo in the -StellarisWare distribution. - -With the latest from git: - - $ .../qemu-git/qemu/bin/qemu-system-arm -M lm3s811evb -kernel uart_echo/gcc/uart_echo.bin - qemu-system-arm: hw/qdev.c:310: qdev_get_gpio_in: Assertion `n >= 0 && n < dev->num_gpio_in' failed. - -This however seems to be reported already (Bug #1028260). - -Both versions compiled from sources: - - ./configure --target-list=arm-linux-user,arm-softmmu,armeb-linux-user --enable-sdl --prefix=/path/to/... - -Running Ubunti 10.04 with Linux 2.6.32-40-generic-pae. - -/Lars \ No newline at end of file diff --git a/results/classifier/deepseek-2-tmp/output/device/1038136 b/results/classifier/deepseek-2-tmp/output/device/1038136 deleted file mode 100644 index 5b7c2a1f..00000000 --- a/results/classifier/deepseek-2-tmp/output/device/1038136 +++ /dev/null @@ -1,9 +0,0 @@ - -lack of keycode 89 for br-abnt2 keyboards - -qemu-kvm-1.1.1 -host system: slackware64-13.37 -Bug detailed description: -Independent of Guest OS nothing happens when keycode 89 is pressed. -If you select option "-k pt-br" at qemu commandline you get keycode 89 but there is no more keycode 26 (dead_acute dead_grave) and keycode 51 fails on "less" sign. -If you have a numeric keyboard you can use its "slash" key but there is no means to use the question mark, causing discomfort when you are scripting or programming. \ No newline at end of file diff --git a/results/classifier/deepseek-2-tmp/output/device/1047470 b/results/classifier/deepseek-2-tmp/output/device/1047470 deleted file mode 100644 index 07d46bef..00000000 --- a/results/classifier/deepseek-2-tmp/output/device/1047470 +++ /dev/null @@ -1,60 +0,0 @@ - -qemu/kvm hangs reading from serial console - -This is for a qemu-kvm running on RHEL 5, so it's pretty old, -but i think the problem still exists in 1.2 - -We have conman running on our hosts, connecting to the -kvm/qemu's using - virsh console -which just opens up the console /dev/pts/slave that qemu -opens up when run with options - -nographic - -serial mon:pty - -Sometimes virsh console exits and then qemu locks up. -My guess is that something like this happens: - -virsh console exits -qemu does a select() on /dev/ptmx (and other FDs) -select() returns the FD of /dev/ptmx in the read-fdset -qemu does a read() -read() returns -1 (EIO) -qemu does other stuff for a while -select() ... /dev/ptmx -read() .. EIO -other stuff -select() ... read() ... select() ... read() ... select() -conman starts a new virsh console that connects -qemu does a read() -read() blocks b/c there is now a writer on the tty slave - -So i don't see any way around this, given the sorta rudi- -mentary semantics of TTY IO on Linux (not that i know of -any platform that does it better ... ?), except ... - -maybe qemu should - fcntl(master_fd, F_SETFL, flags | O_NONBLOCK) -in qemu-char.c:qemu_char_open_pty() -and be prepared to handle E_WOULDBLOCK|E_AGAIN in -qemu-char.c:fd_chr_read() ... ? - ---buck - -[*] i think, b/c in the old version we are running, sometimes - the guest spits out the - ^] - character to its console, and virsh console reads it and - doesn't check to see if its from stdin or the pty and exits, - which, i think, can be fixed like this: - ---- libvirt-0.8.2/tools/console.c.ctrl_close_bracket_handling_fix 2012-09-06 10:30:43.606997191 -0400 -+++ libvirt-0.8.2/tools/console.c 2012-09-06 10:34:52.154000464 -0400 -@@ -155,6 +155,7 @@ int vshRunConsole(const char *tty) { - - /* Quit if end of file, or we got the Ctrl-] key */ - if (!got || -+ fds[i].fd == STDIN_FILENO && - (got == 1 && - buf[0] == CTRL_CLOSE_BRACKET)) - goto done; \ No newline at end of file diff --git a/results/classifier/deepseek-2-tmp/output/device/1049 b/results/classifier/deepseek-2-tmp/output/device/1049 deleted file mode 100644 index ede7a14e..00000000 --- a/results/classifier/deepseek-2-tmp/output/device/1049 +++ /dev/null @@ -1,2 +0,0 @@ - -Have DeviceRealize return boolean indicating error diff --git a/results/classifier/deepseek-2-tmp/output/device/1055090 b/results/classifier/deepseek-2-tmp/output/device/1055090 deleted file mode 100644 index e5f057db..00000000 --- a/results/classifier/deepseek-2-tmp/output/device/1055090 +++ /dev/null @@ -1,22 +0,0 @@ - -esp error: NetBSD/sparc on qemu-system-sparc - -On qemu-1.2.0's qemu-system-sparc, NetBSD/sparc (32bit) 5.1.2 and 6.0_RC2 generates the following NetBSD's errors. - -esp0: !TC on DATA XFER [intr 18, stat 82, step 4] prevphase 2, resid 0 -esp0: !TC on DATA XFER [intr 10, stat 83, step 0] prevphase 2, resid 0 - -On qemu-0.15.1's qemu-system-sparc, NetBSD/sparc 5.1.2 and 6.0_RC2 works fine. - -To reproduce with NetBSD/sparc 6.0_RC2, run - -% qemu-system-sparc -M SS-20 -m 265M -hda NetBSD-sparc-6.0_RC2.qed -nographic -cdrom NetBSD-6.0_RC2-sparc.iso -boot d - -and try to install NetBSD. You can get above errors when newfs command is invoked. -I can reporduce this problem on NetBSD/i386 (32bit) and NetBSD/amd64(64bit; x86_64) host OSes. - -NetBSD-6.0_RC2-sparc.iso is here, -ftp://ftp.netbsd.org/pub/NetBSD/NetBSD-6.0_RC2/images/NetBSD-6.0_RC2-sparc.iso - -NetBSD-sparc-6.0_RC2.qed is created with -% qemu-img create -f qed NetBSD-sparc-6.0_RC2.qed 3G \ No newline at end of file diff --git a/results/classifier/deepseek-2-tmp/output/device/1062220 b/results/classifier/deepseek-2-tmp/output/device/1062220 deleted file mode 100644 index 1eded393..00000000 --- a/results/classifier/deepseek-2-tmp/output/device/1062220 +++ /dev/null @@ -1,29 +0,0 @@ - -qemu-system-arm crashed with SIGABRT in cpu_abort() - --kernel u-boot.bin - -ProblemType: Crash -DistroRelease: Ubuntu 12.10 -Package: qemu-system 1.2.0-2012.09-0ubuntu1 -ProcVersionSignature: Ubuntu 3.5.0-10.10-generic 3.5.1 -Uname: Linux 3.5.0-10-generic x86_64 -NonfreeKernelModules: nvidia -ApportVersion: 2.6.1-0ubuntu1 -Architecture: amd64 -CrashCounter: 1 -Date: Fri Oct 5 19:30:23 2012 -ExecutablePath: /usr/bin/qemu-system-arm -InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Alpha amd64 (20110804) -ProcCmdline: qemu-system-arm -M versatilepb -kernel u-boot.bin -Signal: 6 -SourcePackage: qemu-linaro -StacktraceTop: - raise () from /lib/x86_64-linux-gnu/libc.so.6 - abort () from /lib/x86_64-linux-gnu/libc.so.6 - ?? () - ?? () - ?? () -Title: qemu-system-arm crashed with SIGABRT in raise() -UpgradeStatus: Upgraded to quantal on 2012-08-11 (54 days ago) -UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare vboxusers \ No newline at end of file diff --git a/results/classifier/deepseek-2-tmp/output/device/1070762 b/results/classifier/deepseek-2-tmp/output/device/1070762 deleted file mode 100644 index 46c7d622..00000000 --- a/results/classifier/deepseek-2-tmp/output/device/1070762 +++ /dev/null @@ -1,38 +0,0 @@ - -savevm fails with inserted CD, "Device '%s' is writable but does not support snapshots." - -Hi, - -yesterday unfortunately a customer reported a failed snapshot of his VM. Going through the logfile I discovered: - -"Device 'ide1-cd0' is writable but does not support snapshots" - -this is with qemu-1.2.0 and 1.0.1 at least... - -Why writeable? -Even if I specify "-drive ...,readonly=on,snapshot=off" to qemu the monitor-command sees the CD-ROM-device as being writeable?! - -Somewhere I saw a "hint" for blockdev.c: -=== snip === - ---- /tmp/blockdev.c 2012-10-24 11:37:10.000000000 +0200 -+++ blockdev.c 2012-10-24 11:37:17.000000000 +0200 -@@ -551,6 +551,7 @@ - case IF_XEN: - case IF_NONE: - dinfo->media_cd = media == MEDIA_CDROM; -+ dinfo->bdrv->read_only = 1; - break; - case IF_SD: - case IF_FLOPPY: - -=== snap === - -after installing with this small patch applied it works, so insert CD, savevm succeeds. -This should be fixed at all correct places, and the tags "readonly=on,snapshot=off" should do it, too. Or even just work after specifying a drive being a CD-rom should do the trick ;-) - -Another "bad habit" is, that the ISO/DVD-file has to be writeable to be changed? - -Thnx for attention and regards, - -Oliver. \ No newline at end of file diff --git a/results/classifier/deepseek-2-tmp/output/device/1071 b/results/classifier/deepseek-2-tmp/output/device/1071 deleted file mode 100644 index 70d6fdaa..00000000 --- a/results/classifier/deepseek-2-tmp/output/device/1071 +++ /dev/null @@ -1,13 +0,0 @@ - -Cannot passthrough two network devices (Mellanox ConnectX-3) to VM. -Description of problem: -Cannot passthrough two network devices (Mellanox ConnectX-3) to VM. - -It generated me an error: -[ 6322.674602] genirq: Flags mismatch irq 16. 00000000 (vfio-intx(0000:05:00.0)) vs. 00000000 (vfio-intx(0000:88:00.0)) - -Passthrough only one device to VM goes well. -Steps to reproduce: -1. Add a first passthrough network device. -2. Add a second passthrough network device. -3. Run VM. diff --git a/results/classifier/deepseek-2-tmp/output/device/1073952 b/results/classifier/deepseek-2-tmp/output/device/1073952 deleted file mode 100644 index dc633607..00000000 --- a/results/classifier/deepseek-2-tmp/output/device/1073952 +++ /dev/null @@ -1,29 +0,0 @@ - -data sent to serial interface gets truncated after 64kb - -When sending more than 64kb of data to the serial interface in a short timespan, the data seems to disappear. - -I tested it with the latest release (qemu-kvm-1.2.0-rc2.tar.gz) where the bug still occurs. I stumbled upon it when I upraged my qemu version. The bug did not occur in the last version i had (0.12.5). - -You can reproduce it as follows: - -1. Start a dd or cat command in one terminal and pipe the output to a netcat. The testfile has to be larger than 64kb. I used one that had 93kb and did contain only ascii text. - - $ dd if= | nc -l 127.0.0.1 65432 - or - $ cat | nc -l 127.0.0.1 65432 - -2. Start a qemu and let the first serial port connect to the listening netcat. I suppose that the testsystem can be any system that does not read from the serial port on its own (e.g. during boot process). I used a self compiled minimal linux. - - $ qemu -cdrom -serial tcp:127.0.0.1:65432 - -3. When the testsystem is booted, read from the serial device and write it to a file. - - $ dd if=/dev/ttyS0 of=/tmp/testFile - or - $ cat /dev/ttyS0 > /tmp/testFile - - -The result in almost all of my testruns is, that the /tmp/testFile does only has the size of 64kb. The rest of the data vanished. In some cases the file was slightly bigger (65kb or 67kb) but allways under 70kb. The complete file (93kb) was not trasmitted in any of the runs. - -I hope my explanation is exactly enough for you to reproduce it. \ No newline at end of file diff --git a/results/classifier/deepseek-2-tmp/output/device/1076 b/results/classifier/deepseek-2-tmp/output/device/1076 deleted file mode 100644 index 0dc6f6da..00000000 --- a/results/classifier/deepseek-2-tmp/output/device/1076 +++ /dev/null @@ -1,13 +0,0 @@ - -AC97+DirectSound only polls for audio every 10ms with no way to change it -Description of problem: -The AC97 device emulation, at least in combination with the DirectSound backend, only polls for audio every 10ms, meaning that DMA interrupts are received at a maximum frequency of 100Hz. This applies regardless of how large the buffers in the AC97's buffer list are, meaning that if one buffer takes less than 10ms to play, glitches can be heard with no possible mitigations on the host system. - -I came across this when fiddling with Serenity's own latencies in the AC97 driver and userland mixer. As soon as less than 512-sample buffers are used, audio becomes glitchy. Based on timing tests, kernel and userland processing of audio combined takes less than 200μs for one buffer, while the lowest average rate that DMA interrupts are received at is almost exactly 10ms. - -No changes to the dsound latency option, as listed [here](https://www.qemu.org/docs/master/system/invocation.html?highlight=dsound), made any difference; I tried as low as 2ms: `-audiodev dsound,id=snd0,latency=2000`. As far as I can tell there are no IRQ- or latency-related options for the AC97 emulation. -Steps to reproduce: -1. Use SerenityOS as of the above commit. -2. Before building, include an audio file in Base/home/anon; most ordinary FLAC, WAV and MP3 files created without options with ffmpeg should work. -3. Boot Serenity in QEMU on Windows without any special run configuration. -4. Play the audio file with `aplay `, hear glitches. diff --git a/results/classifier/deepseek-2-tmp/output/device/1077708 b/results/classifier/deepseek-2-tmp/output/device/1077708 deleted file mode 100644 index 5aeafd5a..00000000 --- a/results/classifier/deepseek-2-tmp/output/device/1077708 +++ /dev/null @@ -1,17 +0,0 @@ - -Video capture from webcam with USB passthrough freezes - -QEMU version: 1.2.0 -Graphics: Spice -Guest: Windows 7 32-bit -Host: Ubuntu 12.10 amd64 (using distro package qemu-kvm-spice) - -I am using USB 2.0 passthrough of a Logitech C920 webcam. The guest is running the proprietary Logitech drivers. When video chatting with either Google+ Hangouts or Skype 3.8.0.115, video capture from the webcam is initially fine but eventually freezes. It remains frozen for up to several minutes and then resumes on its own. The process then repeats. Audio recorded from the webcam's mic works continuously. - -The problem also affects video recording in Logitech's bundled software. Strangely though, the live preview is _not_ affected. The freezing is only present in the recorded video file. - -I can tell that the problem is not introduced by Spice during playback, because the user on the other end of Hangouts/Skype sees the same problem, and the freezes in a recorded video file are seen at the same point every time the file is played. - -Command line: - -/usr/bin/kvm-spice -name Windows7 -S -M pc-1.0 -enable-kvm -m 2048 -smp 3,sockets=3,cores=1,threads=1 -uuid cfcc7e85-7873-1c32-0a00-d1c35f3eb073 -no-user-config -nodefaults -chardev socket,id=charmonitor,path=/var/lib/libvirt/qemu/Windows7.monitor,server,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=localtime -no-shutdown -device ich9-usb-ehci1,id=usb,bus=pci.0,addr=0x6.0x7 -device ich9-usb-uhci1,masterbus=usb.0,firstport=0,bus=pci.0,multifunction=on,addr=0x6 -device ich9-usb-uhci2,masterbus=usb.0,firstport=2,bus=pci.0,addr=0x6.0x1 -device ich9-usb-uhci3,masterbus=usb.0,firstport=4,bus=pci.0,addr=0x6.0x2 -drive file=/data/libvirt/images/Windows7.img,if=none,id=drive-ide0-0-0,format=raw -device ide-hd,bus=ide.0,unit=0,drive=drive-ide0-0-0,id=ide0-0-0,bootindex=1 -drive if=none,id=drive-ide0-1-0,readonly=on,format=raw -device ide-cd,bus=ide.1,unit=0,drive=drive-ide0-1-0,id=ide0-1-0 -netdev tap,fd=21,id=hostnet0 -device rtl8139,netdev=hostnet0,id=net0,mac=52:54:00:7e:0b:d9,bus=pci.0,addr=0x3 -chardev pty,id=charserial0 -device isa-serial,chardev=charserial0,id=serial0 -device usb-tablet,id=input0 -spice port=5900,addr=127.0.0.1,disable-ticketing -vga std -device intel-hda,id=sound0,bus=pci.0,addr=0x4 -device hda-duplex,id=sound0-codec0,bus=sound0.0,cad=0 -device usb-host,hostbus=2,hostaddr=8,id=hostdev0 -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x5 \ No newline at end of file diff --git a/results/classifier/deepseek-2-tmp/output/device/1077838 b/results/classifier/deepseek-2-tmp/output/device/1077838 deleted file mode 100644 index 2655ad11..00000000 --- a/results/classifier/deepseek-2-tmp/output/device/1077838 +++ /dev/null @@ -1,31 +0,0 @@ - -qemu-nbd -r -c taints device for subsequent usage, even after -d - -Something about qemu-nbd -r -c /dev/nbd0 someimg leaves cruft behind - subsequent connections get marked readonly. - -This is on quantal, haven't checked precise or raring. - -To demonstrate: -# use one image -qemu-img create -f qcow2 /tmp/1.qcow2 100M -sudo qemu-nbd -c /dev/nbd2 /tmp/1.qcow2 -sudo mkfs -t ext4 /dev/nbd2 -sudo qemu-nbd -d /dev/nbd2 -# use a second one on the same nbd device, shows that reuse works: -qemu-img create -f qcow2 /tmp/2.qcow2 100M -sudo qemu-nbd -c /dev/nbd2 /tmp/2.qcow2 -sudo mkfs -t ext4 /dev/nbd2 -sudo qemu-nbd -d /dev/nbd2 -# connect an image in read only mode -sudo qemu-nbd -r -c /dev/nbd2 /tmp/2.qcow2 -sudo dumpe2fs /dev/nbd2 | head -n 3 -sudo qemu-nbd -d /dev/nbd2 -# now try to reuse in read-write mode again: -qemu-img create -f qcow2 /tmp/3.qcow2 100M -sudo qemu-nbd -c /dev/nbd2 /tmp/3.qcow2 -sudo mkfs -t ext4 /dev/nbd2 -# here it goes boom: -mke2fs 1.42.5 (29-Jul-2012) -/dev/nbd2: Operation not permitted while setting up superblock -# still need to cleanup -sudo qemu-nbd -d /dev/nbd2 \ No newline at end of file diff --git a/results/classifier/deepseek-2-tmp/output/device/1086782 b/results/classifier/deepseek-2-tmp/output/device/1086782 deleted file mode 100644 index e09b850c..00000000 --- a/results/classifier/deepseek-2-tmp/output/device/1086782 +++ /dev/null @@ -1,85 +0,0 @@ - -HPET time drift windows 7 64bits guest - -Using latest qemu-kvm (1.2.0), time drift (clock slow in guest) in Windows 7 64 bits guest when HPET is enabled (default). -Disabling HPET (-no-hpet) solves the time drift. - -UsePlatformClock enable/disable doesn't make a difference in the guest. -bcdedit /set useplatformclock true - -Using driftfix slew doesn't make a difference too. - - -# qemu-system-x86_64 --version -QEMU emulator version 1.2.0 (qemu-kvm-1.2.0), Copyright (c) 2003-2008 Fabrice Bellard - -Kernel is 3.6.8: -# uname -a -Linux pulsar 3.6.8 #1 SMP Sat Dec 1 16:26:10 CET 2012 x86_64 x86_64 x86_64 GNU/Linux - -TSC is stable in the host: -=== -# cat /sys/devices/system/clocksource/clocksource0/current_clocksource -tsc - -Dmesg: -[ 0.000000] hpet clockevent registered -[ 0.000000] tsc: Fast TSC calibration using PIT -[ 0.000000] tsc: Detected 2660.096 MHz processor -[ 0.001002] Calibrating delay loop (skipped), value calculated using timer frequency.. 5320.19 BogoMIPS (lpj=2660096) -[ 0.001138] pid_max: default: 32768 minimum: 301 -... -[ 1.492019] tsc: Refined TSC clocksource calibration: 2659.973 MHz -[ 1.492093] Switching to clocksource tsc - - -CPUinfo, constant_tsc: -vendor_id : GenuineIntel -cpu family : 6 -model : 23 -model name : Intel(R) Core(TM)2 Quad CPU Q8400 @ 2.66GHz -stepping : 10 -microcode : 0xa0b -cpu MHz : 2667.000 -cache size : 2048 KB -flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx lm constant_tsc arch_perfmon pebs bts rep_good nopl aperfmperf pni dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm sse4_1 xsave lahf_lm dtherm tpr_shadow vnmi flexpriority -bogomips : 5320.19 - -# grep -i hpet .config -CONFIG_HPET_TIMER=y -CONFIG_HPET_EMULATE_RTC=y -CONFIG_HPET=y -# CONFIG_HPET_MMAP is not set -=== - -Qemu command line: -/usr/bin/qemu-system-x86_64 -drive file=/dev/vol0/KVMORION01,cache=none,aio=native,if=virtio \ - -drive file=/dev/vol0/KVMORION02,cache=none,aio=native,if=virtio \ - -cpu host \ - -m 2048 \ - -smp 4,maxcpus=4,cores=4,threads=1,sockets=1 \ - -rtc base=localtime,driftfix=slew \ - -vnc 10.124.241.211:0,password -k es \ - -monitor telnet:localhost:37200,server,nowait \ - -netdev tap,id=kvmorion,ifname=kvmorion,script=/etc/qemu-ifup-br0,downscript=/etc/qemu-ifdown-br0 \ - -device virtio-net-pci,netdev=kvmorion,id=virtio-nic0,mac=02:85:64:02:c2:aa \ - -device virtio-balloon-pci,id=balloon0 \ - -boot menu=on \ - -pidfile /var/run/kvmorion.pid \ - -daemonize - -Using 1 CPU doesn't make a difference. -Only workaround is disabling hpet (-no-hpet) - -Sample time drift in guest: ->ntpdate -q 10.124.241.211 - 5 Dec 13:36:06 ntpdate[3464]: Raised to realtime priority class -server 10.124.241.211, stratum 2, offset 3.694184, delay 0.02551 - 5 Dec 13:36:12 ntpdate[3464]: step time server 10.124.241.211 offset 3.694184 s -ec - ->ntpdate -q 10.124.241.211 - 5 Dec 13:52:02 ntpdate[1964]: Raised to realtime priority class -server 10.124.241.211, stratum 2, offset 4.719968, delay 0.02554 - 5 Dec 13:52:08 ntpdate[1964]: step time server 10.124.241.211 offset 4.719968 s -ec \ No newline at end of file diff --git a/results/classifier/deepseek-2-tmp/output/device/1087114 b/results/classifier/deepseek-2-tmp/output/device/1087114 deleted file mode 100644 index cc26b603..00000000 --- a/results/classifier/deepseek-2-tmp/output/device/1087114 +++ /dev/null @@ -1,45 +0,0 @@ - -assertion "QLIST_EMPTY(&bs->tracked_requests)" failed - -QEMU 1.3.0 on OpenBSD now crashes with an error as shown below and the command line params do not seem to matter. - -assertion "QLIST_EMPTY(&bs->tracked_requests)" failed: file "block.c", line 1220, function "bdrv_drain_all" - -#1 0x0000030d1bce24aa in abort () at /usr/src/lib/libc/stdlib/abort.c:70 - p = (struct atexit *) 0x30d11897000 - mask = 4294967263 - cleanup_called = 1 -#2 0x0000030d1bc5ff44 in __assert2 (file=Variable "file" is not available. -) at /usr/src/lib/libc/gen/assert.c:52 -No locals. -#3 0x0000030b0d383a03 in bdrv_drain_all () at block.c:1220 - bs = (BlockDriverState *) 0x30d13f3b630 - busy = false - __func__ = "bdrv_drain_all" -#4 0x0000030b0d43acfc in bmdma_cmd_writeb (bm=0x30d0f5f56a8, val=8) at hw/ide/pci.c:312 - __func__ = "bmdma_cmd_writeb" -#5 0x0000030b0d43b450 in bmdma_write (opaque=0x30d0f5f56a8, addr=0, val=8, size=1) at hw/ide/piix.c:76 - bm = (BMDMAState *) 0x30d0f5f56a8 -#6 0x0000030b0d5c2ce6 in memory_region_write_accessor (opaque=0x30d0f5f57d0, addr=0, value=0x30d18c288f0, size=1, shift=0, mask=255) - at /home/ports/pobj/qemu-1.3.0-debug/qemu-1.3.0/memory.c:334 - mr = (MemoryRegion *) 0x30d0f5f57d0 - tmp = 8 -#7 0x0000030b0d5c2dc5 in access_with_adjusted_size (addr=0, value=0x30d18c288f0, size=1, access_size_min=1, access_size_max=4, - access=0x30b0d5c2c6b , opaque=0x30d0f5f57d0) at /home/ports/pobj/qemu-1.3.0-debug/qemu-1.3.0/memory.c:364 - access_mask = 255 - access_size = 1 - i = 0 -#8 0x0000030b0d5c3222 in memory_region_iorange_write (iorange=0x30d1d5e7400, offset=0, width=1, data=8) - at /home/ports/pobj/qemu-1.3.0-debug/qemu-1.3.0/memory.c:439 - mrio = (MemoryRegionIORange *) 0x30d1d5e7400 - mr = (MemoryRegion *) 0x30d0f5f57d0 - __func__ = "memory_region_iorange_write" -#9 0x0000030b0d5c019a in ioport_writeb_thunk (opaque=0x30d1d5e7400, addr=49216, data=8) at /home/ports/pobj/qemu-1.3.0-debug/qemu-1.3.0/ioport.c:212 - ioport = (IORange *) 0x30d1d5e7400 -#10 0x0000030b0d5bfb65 in ioport_write (index=0, address=49216, data=8) at /home/ports/pobj/qemu-1.3.0-debug/qemu-1.3.0/ioport.c:83 - func = (IOPortWriteFunc *) 0x30b0d5c0148 - default_func = {0x30b0d5bfbbc , 0x30b0d5bfc61 , 0x30b0d5bfd0c } -#11 0x0000030b0d5c0704 in cpu_outb (addr=49216, val=8 '\b') at /home/ports/pobj/qemu-1.3.0-debug/qemu-1.3.0/ioport.c:289 -No locals. -#12 0x0000030b0d6067dd in helper_outb (port=49216, data=8) at /home/ports/pobj/qemu-1.3.0-debug/qemu-1.3.0/target-i386/misc_helper.c:72 -No locals. \ No newline at end of file diff --git a/results/classifier/deepseek-2-tmp/output/device/1088617 b/results/classifier/deepseek-2-tmp/output/device/1088617 deleted file mode 100644 index 6100a9f2..00000000 --- a/results/classifier/deepseek-2-tmp/output/device/1088617 +++ /dev/null @@ -1,15 +0,0 @@ - -qemu-system-mipsel save/restore broken - -Save and restore on mipsel seems to be broken (tested with commit 1c97e303d4ea80a2691334b0febe87a50660f99d). To reproduce: - -1. Download debian_squeeze_mipsel_standard.qcow2 and vmlinux-2.6.32-5-4kc-malta from from http://people.debian.org/~aurel32/qemu/mipsel/ - -2. Boot the system. I had to ^D past a Bus error in fsck, which may be another bug (haven't investigated). The command line used was: -qemu-system-mipsel -M malta -kernel vmlinux-2.6.32-5-4kc-malta -hda debian_squeeze_mipsel_standard.qcow2 -append "root=/dev/sda1 console=tty0" -k en-us -vnc :0 - -3. Once the system is booted, go to the monitor and do "savevm booted". Then quit. - -4. Re-run qemu-system-mipsel again with "-loadvm booted". The guest system comes back but is hung (the monitor remains responsive, however). - -I also captured a debug log, which is attached. The immediate cause of the freeze seems to be that it's stuck in a loop repeatedly handling the same page fault over and over. \ No newline at end of file diff --git a/results/classifier/deepseek-2-tmp/output/device/1089006 b/results/classifier/deepseek-2-tmp/output/device/1089006 deleted file mode 100644 index 15b39558..00000000 --- a/results/classifier/deepseek-2-tmp/output/device/1089006 +++ /dev/null @@ -1,12 +0,0 @@ - -Qemu scrambles order of eth devices in vm - -HV = 12.04 LTS plus libvirt 1.0x -VM = 12.04 LTS - -On the HV there are 12 eth interfaces which we make available to the VM. We have 4 10G virtual function interfaces, and 8 1G conventionally bridged interfaces. No matter what order we present the interfaces in the xml file, they come up in eth0-eth11 order on the VM as follows: ( the interfcaes do work, once you figure out which is which) - -eth0-eth7 not in order as compoared to the bridges on the HV (interfaces file) or compared to the xml file for the VM, or compared to the bus numbers. MAC addresses are random. -eth8-eth11 show up in the VM in order of PCU bus numbers just as you'd expect, always after the bridged interfaces. - -Consulting the libvirt mailing list, the developer says they present the list in bus order to qemu, but qemu scrambles that order. That appears to me too, to be the case. \ No newline at end of file diff --git a/results/classifier/deepseek-2-tmp/output/device/1090 b/results/classifier/deepseek-2-tmp/output/device/1090 deleted file mode 100644 index 94d1dae6..00000000 --- a/results/classifier/deepseek-2-tmp/output/device/1090 +++ /dev/null @@ -1,16 +0,0 @@ - -can't create rocker device because setting device array properties on the command line is broken -Description of problem: -it does not accept the prop_array parameter: - -``` -qemu-system-x86_64 -enable-kvm -m 1g -cpu host -netdev socket,id=dev0,udp=10.10.10.227:30042,localaddr=:30042 -device rocker,len-ports=4,name=sw,len-ports=2,ports[0]=dev0 -qemu-system-x86_64: -device rocker,len-ports=4,name=sw,len-ports=2,ports[0]=dev0: Property 'rocker.ports[0]' not found -``` -Steps to reproduce: -1. just run the command -Additional information: -the latest qemu i find working is 6.1.1... if you start a fedora vm and `dnf install kernel-modules-internal` then the rocker ports appear and work properly... - -thanks, -cs diff --git a/results/classifier/deepseek-2-tmp/output/device/1090558 b/results/classifier/deepseek-2-tmp/output/device/1090558 deleted file mode 100644 index 24c36816..00000000 --- a/results/classifier/deepseek-2-tmp/output/device/1090558 +++ /dev/null @@ -1,10 +0,0 @@ - -hw/mc146818: error reading RTC_HOURS_ALARM - -get_next_alarm() doesn't read the RTC_HOURS_ALARM field correctly. - -- Bit 7 must be masked before conversion from BCD. -- Care must be taken to check the don't care condition before masking. -- The PM bit must be read from RTC_HOURS_ALARM, not from RTC_HOURS (as is done in convert_hour()). - -Seen in commit e376a788ae130454ad5e797f60cb70d0308babb6. \ No newline at end of file diff --git a/results/classifier/deepseek-2-tmp/output/device/1090604 b/results/classifier/deepseek-2-tmp/output/device/1090604 deleted file mode 100644 index a92ab6da..00000000 --- a/results/classifier/deepseek-2-tmp/output/device/1090604 +++ /dev/null @@ -1,12 +0,0 @@ - -RFE: Implement support for SMBIOS Type 41 structures - -This was originally filed in Fedora bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=669955 - -""" -Please extend the existing support for SMBIOS in qemu to add a capability to provide "Onboard Devices Extended Information" (Type 41). Not only is this replacing one of the existing types, but it also provides a mapping between devices and physical system chassis locations. But there is no physical chassis! Right. However, this doesn't mean you don't want to tell the guest OS which virtual (e.g. network) interface is which. You can do that, if you implement this extension that is already going into real hardware, and likely other VMs too. - -See also page 117 of the v2.7 of the SMBIOS spec. - -FWIW, VMware ESX and Workstation expose their PCI NICs in the PCI IRQ Routing Table. Kind of odd the first time you see it with biosdevname, as your NIC becomes pci3#1, but that's "correct" from a BIOS perspective. :-) -""" \ No newline at end of file diff --git a/results/classifier/deepseek-2-tmp/output/device/1093360 b/results/classifier/deepseek-2-tmp/output/device/1093360 deleted file mode 100644 index 9167dc55..00000000 --- a/results/classifier/deepseek-2-tmp/output/device/1093360 +++ /dev/null @@ -1,14 +0,0 @@ - -files on microsoft iso images mounted to qemu VM get stripped from Version info. E.G. Microsoft UAG installation fails - -QEMU 0.9.0-0.14.1 -KVM 60-88-0.14.1 -there is a reference for a root cause, why installation of Microsoft UAG fails. -http://blogs.technet.com/b/isablog/archive/2010/07/13/another-tmg-2010-installation-failure-with-error-0x80070643.aspx - -when checking available information on the mounted UAG ISO in my qemu machine, I realized simliar reduced information. -this was found: -using AQEMU 0.8.2 of 2011.07.27 - -using QEMU 0.9.0-0.14.1 and KVM 60-88-0.14.1 -in an KVM managed machine \ No newline at end of file diff --git a/results/classifier/deepseek-2-tmp/output/device/1096713 b/results/classifier/deepseek-2-tmp/output/device/1096713 deleted file mode 100644 index 297d78c4..00000000 --- a/results/classifier/deepseek-2-tmp/output/device/1096713 +++ /dev/null @@ -1,9 +0,0 @@ - -qemu 1.3.0: Windows XP crashes when reconizing the USB keyboard - -I'm trying to use the usb tablet and the usb keyboard as follows: -./qemu-system-i386 -device pci-ohci -device usb-tablet -device usb-kbd -or -./qemu-system-i386 -device ich9-usb-ehci1 -device ich9-usb-uhci1 -device usb-tablet -device ich9-usb-uhci2 -device usb-kbd - -While Windows XP works fine if I only use the tablet but not the keyboard, it crashed with a BSOD when I use both keyboard and tablet. It crashed during the detection of the keyboard. \ No newline at end of file diff --git a/results/classifier/deepseek-2-tmp/output/device/1096714 b/results/classifier/deepseek-2-tmp/output/device/1096714 deleted file mode 100644 index 18650b12..00000000 --- a/results/classifier/deepseek-2-tmp/output/device/1096714 +++ /dev/null @@ -1,11 +0,0 @@ - -qemu 1.3.0: usb devices shouldn't have same vendor/product ID and same serial - -Boot Windows XP with -./qemu-system-i386 -device pci-ohci -device usb-tablet -and then with -./qemu-system-i386 -device pci-ohci -device usb-kbd - -and you will notice, that the usb keyboard is not detected. In fact, Windows XP detects the usb tablet and loads the driver for the tablet instead of the driver for the keyboard. - -The problem seems to be, that vendor and product ID and even the seriel of both the usb tablet and the usb keyboard are the same as an lsusb reveiles. Hence, Windows XP doesn't detect when you replace the tablet by a keyboard and vice versa. I didn't check other USB devices, but it seems a bad idea to me to have devices with the same vendor/product Id. I'm not aware, whether it is sufficient to change the seriel numbers of the devices. \ No newline at end of file diff --git a/results/classifier/deepseek-2-tmp/output/device/1101210 b/results/classifier/deepseek-2-tmp/output/device/1101210 deleted file mode 100644 index 25d39406..00000000 --- a/results/classifier/deepseek-2-tmp/output/device/1101210 +++ /dev/null @@ -1,10 +0,0 @@ - -qemu 1.4.2: usb keyboard not fully working - -When using the usb keyboard, I can't type the | character. I'm using german keyboard layout (de) on the host and inside the guest. As a guest OS, I use Linux (e.g. a recent KNOPPIX cd). To obtain the | character on a german keyboard, I need to press AltGr + the < or > key, i.e. the key right to the left shift. - -The qemu command line is something like this: -./qemu-system-i386 -device pci-ohci -device usb-kbd -I also tried -./qemu-system-i386 -usb -usbdevice keyboard -with the same effect. \ No newline at end of file diff --git a/results/classifier/deepseek-2-tmp/output/device/1106 b/results/classifier/deepseek-2-tmp/output/device/1106 deleted file mode 100644 index f2335918..00000000 --- a/results/classifier/deepseek-2-tmp/output/device/1106 +++ /dev/null @@ -1,10 +0,0 @@ - -undefined address access cause failure -Description of problem: -Hi, -I used serial device as below: -qemu/hw/char/serial.c -It defines only support 8 registers address space(offset 0x00-0x32). And in guest os, the hardware is synopsys dw_apb_uart which is compatible with 16550. -when it access low 8 registers, it works ok. but it may access high address(0x8c) which serial.c not defined, then fail occur. - -Is there anyway to handle this, access address which device not defined, expect it no handle, but not cause system crash. like read is zero and write ignore. diff --git a/results/classifier/deepseek-2-tmp/output/device/1110 b/results/classifier/deepseek-2-tmp/output/device/1110 deleted file mode 100644 index 319b3f77..00000000 --- a/results/classifier/deepseek-2-tmp/output/device/1110 +++ /dev/null @@ -1,4 +0,0 @@ - -Add vhost-user-gpu support for cross architecture emulation -Additional information: -host:Android 12 with Linux kernel 4.14.186+ diff --git a/results/classifier/deepseek-2-tmp/output/device/1112 b/results/classifier/deepseek-2-tmp/output/device/1112 deleted file mode 100644 index 4247c522..00000000 --- a/results/classifier/deepseek-2-tmp/output/device/1112 +++ /dev/null @@ -1,2 +0,0 @@ - -Heap-overflow in scsi_disk_emulate_write_same diff --git a/results/classifier/deepseek-2-tmp/output/device/112 b/results/classifier/deepseek-2-tmp/output/device/112 deleted file mode 100644 index fc225b7a..00000000 --- a/results/classifier/deepseek-2-tmp/output/device/112 +++ /dev/null @@ -1,2 +0,0 @@ - -setting unsupported timeout for i6300esb watchdog causes hw reset diff --git a/results/classifier/deepseek-2-tmp/output/device/1134 b/results/classifier/deepseek-2-tmp/output/device/1134 deleted file mode 100644 index ec3e9136..00000000 --- a/results/classifier/deepseek-2-tmp/output/device/1134 +++ /dev/null @@ -1,4 +0,0 @@ - -Make ivshmem more generic not only a PCI device -Additional information: -It will also benefit from making it more portable, see https://gitlab.com/qemu-project/qemu/-/issues/666 diff --git a/results/classifier/deepseek-2-tmp/output/device/1139 b/results/classifier/deepseek-2-tmp/output/device/1139 deleted file mode 100644 index 4a0c9a6f..00000000 --- a/results/classifier/deepseek-2-tmp/output/device/1139 +++ /dev/null @@ -1,79 +0,0 @@ - -block/nbd.c and drive backup to a remote nbd server -Description of problem: -Good afternoon! - -I trying to copy attached drive content to remote NBD server via drive-backup QMP method. I'he tested two very similar ways but with very different performance. First is a backuping to exported NBD at another server. Second way is a backuping to same server but with connecting to /dev/nbd*. - -Exporting qcow2 via nbd: -``` -(nbd) ~ # qemu-nbd -p 12345 -x backup --cache=none --aio=native --persistent -f qcow2 backup.qcow2 - -(qemu) ~ # qemu-img info nbd://10.0.0.1:12345/backup -image: nbd://10.0.0.1:12345/backup -file format: raw -virtual size: 10 GiB (10737418240 bytes) -disk size: unavailable -``` - -Starting drive backuping via QMP: - -``` -{ - "execute": "drive-backup", - "arguments": { - "device": "disk", - "sync": "full", - "target": "nbd://10.0.0.1:12345/backup", - "mode": "existing" - } -} -``` - -With process starting qemu notifying about warning: - -> warning: The target block device doesn't provide information about the block size and it doesn't have a backing file. The default block size of 65536 bytes is used. If the actual block size of the target exceeds this default, the backup may be unusable - -And backup process is limited by speed around 30MBps, watched by iotop - - -Second way to creating backup - -Exporting qcow2 via nbd: -``` -(nbd) ~ # qemu-nbd -p 12345 -x backup --cache=none --aio=native --persistent -f qcow2 backup.qcow2 -``` - -``` -(qemu) ~ # qemu-img info nbd://10.0.0.1:12345/backup -image: nbd://10.0.0.1:12345/backup -file format: raw -virtual size: 10 GiB (10737418240 bytes) -disk size: unavailable -(qemu) ~ # qemu-nbd -c /dev/nbd0 nbd://10.0.0.1:12345/backup -(qemu) ~ # qemu-img info /dev/nbd0 -image: /dev/nbd0 -file format: raw -virtual size: 10 GiB (10737418240 bytes) -disk size: 0 B -``` - -Starting drive backuping via QMP to local nbd device: - -``` -{ - "execute": "drive-backup", - "arguments": { - "device": "disk", - "sync": "full", - "target": "/dev/nbd0", - "mode": "existing" - } -} -``` - -Backup process started without previous warning, and speed limited around 100MBps (network limit) - -So I have question: how I can get same performance without connection network device to local block nbd device at the qemu host? - -Kind regards diff --git a/results/classifier/deepseek-2-tmp/output/device/1162227 b/results/classifier/deepseek-2-tmp/output/device/1162227 deleted file mode 100644 index 6a030f02..00000000 --- a/results/classifier/deepseek-2-tmp/output/device/1162227 +++ /dev/null @@ -1,17 +0,0 @@ - -Mouse works badly when connecting to host via vnc - -Let's assume we have some physical host A. This host runs qemu guest B locally without any options like "-vnc" etc. -Then I connect from some physical host C to the host A via VNC or Teamviewer ( www.teamviewer.com ). And then I try to remote control (via this vnc connection) qemu guest. But I cannot do this because my mouse disappears when I click at my qemu guest. I see little black square only. (This square is vnc feature, it automatically appears when mouse disappears.) When I click to some objects inside guest I will instead click to another random object inside guest. - -I saw this bug in the following configurations: -* A: Debian squeeze 64-bit, Teamviewer 8, Qemu 0.12.5, C: Ubuntu precise 64-bit, Teamviewer 8, B: Windows 7 32-bit, command line: -qemu-system-x86_64 --enable-kvm -m 2048 -daemonize -localtime -drive cache=none,file=/root/vm/w7-sp1-i386-en.cow -* A: Debian squeeze 64-bit, Teamviewer 8, Qemu 0.12.5, C: Ubuntu precise 64-bit, Teamviewer 8, B: Debian squeeze 64-bit, command line: -qemu-system-x86_64 -enable-kvm -m 256 -daemonize -snapshot -net none -drive cache=none,file=/dev/sda -* A: Debian squeeze 64-bit, x11vnc 0.9.10, Qemu 0.12.5, C: Ubuntu precise 64-bit, xvnc4viewer 4.1.1, B: Windows 7 32-bit, command line: -qemu-system-x86_64 --enable-kvm -m 2048 -daemonize -localtime -drive cache=none,file=/root/vm/w7-sp1-i386-en.cow - -Also, if I add "-usbdevice tablet" option, this bug will disappear. So, probably, this bug is not a bug. But in this case you should document it. I. e. you should add to docs something like "add -usbdevice tablet if you remote control qemu host". - -Also, if I use "-vnc" option (in the text above I didn't use it!) my mouse doesn't work as expected, too. The pointers don't line up, i. e. are not synced. But if I add "-usbdevice tablet" option, mouse will work. As far as I know this is not a bug. But then document it, too. Qemu's man page already says "It is very useful to enable the usb tablet device when using this option (option -usbdevice tablet)" in qemu 0.12.5. But I think this is not enough. The man page should say: "You should add -usbdevice tablet option and your guest OS should support tablet device or your mouse will not work". \ No newline at end of file diff --git a/results/classifier/deepseek-2-tmp/output/device/1162644 b/results/classifier/deepseek-2-tmp/output/device/1162644 deleted file mode 100644 index 6f611f37..00000000 --- a/results/classifier/deepseek-2-tmp/output/device/1162644 +++ /dev/null @@ -1,91 +0,0 @@ - -qemu-system-x86_64 crashed with SIGABRT in __assert_fail_base() - -Description: -When QEMU tries to boot with a usb 3.0 tablet (xhci) on a Raring ringtail box (QEMU package1.4.0+dfsg-1expubuntu4) it will crash soon afterwards: - -qemu-system-x86_64: /build/buildd/qemu-1.4.0+dfsg/hw/usb/core.c:552: usb_packet_setup: Assertion `p->iov.iov != ((void *)0)' failed. - -Component: -qemu-system -> 1.4.0+dfsg-1expubuntu4 - -Ubuntu Version: - -Description: Ubuntu Raring Ringtail (development branch) -Release: 13.04 - -Steps to reproduce it: - -I met this bug while running the virt-test suite - -https://github.com/autotest/virt-test - -Instructions to install and run it can be seen on the README file - -https://github.com/autotest/virt-test#readme - -After the suite is set, it can be reproduced on a raring (13.04) simply by running: - -./run -t qemu --tests usb.usb_reboot.usb_tablet.xhci - -Command line: - -23:52:42 INFO | Running qemu command (reformatted): -/usr/bin/kvm \ - -S \ - -name 'virt-tests-vm1' \ - -nodefaults \ - -chardev socket,id=hmp_id_hmp1,path=/tmp/monitor-hmp1-20130331-233911-ndvUEvrV,server,nowait \ - -mon chardev=hmp_id_hmp1,mode=readline \ - -chardev socket,id=serial_id_serial1,path=/tmp/serial-serial1-20130331-233911-ndvUEvrV,server,nowait \ - -device isa-serial,chardev=serial_id_serial1 \ - -chardev socket,id=seabioslog_id_20130331-233911-ndvUEvrV,path=/tmp/seabios-20130331-233911-ndvUEvrV,server,nowait \ - -device isa-debugcon,chardev=seabioslog_id_20130331-233911-ndvUEvrV,iobase=0x402 \ - -device ich9-usb-uhci1,id=usb1 \ - -device nec-usb-xhci,id=usbtest \ - -drive file='/home/lmr/Code/virt-test.git/shared/data/images/jeos-17-64.qcow2',if=none,id=virtio0 \ - -device virtio-blk-pci,drive=virtio0,bootindex=1 \ - -device virtio-net-pci,netdev=idumV1TE,mac='9a:c0:c1:c2:c3:c4',id='idmN7iHv' \ - -netdev user,id=idumV1TE,hostfwd=tcp::5000-:22 \ - -m 1024 \ - -smp 2,maxcpus=2,cores=1,threads=1,sockets=2 \ - -cpu 'SandyBridge' \ - -M pc \ - -device usb-tablet,id=usb-tablet1,bus=usb1.0,port=1 \ - -device usb-tablet,id=usb-testdev,bus=usbtest.0,port=1 \ - -vnc :0 \ - -vga std \ - -rtc base=utc,clock=host,driftfix=none \ - -boot order=cdn,once=c,menu=off \ - -enable-kvm - -ProblemType: Crash -DistroRelease: Ubuntu 13.04 -Package: qemu-system-x86 1.4.0+dfsg-1expubuntu4 -ProcVersionSignature: Ubuntu 3.8.0-15.25-generic 3.8.4 -Uname: Linux 3.8.0-15-generic x86_64 -ApportVersion: 2.9.2-0ubuntu5 -Architecture: amd64 -Date: Sun Mar 31 23:52:46 2013 -EcryptfsInUse: Yes -ExecutablePath: /usr/bin/qemu-system-x86_64 -InstallationDate: Installed on 2013-03-31 (0 days ago) -InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5) -MarkForUpload: True -ProcEnviron: - TERM=dumb - PATH=(custom, no user) - XDG_RUNTIME_DIR= - LANG=en_US.UTF-8 - SHELL=/bin/bash -Signal: 6 -SourcePackage: qemu -StacktraceTop: - raise () from /lib/x86_64-linux-gnu/libc.so.6 - abort () from /lib/x86_64-linux-gnu/libc.so.6 - ?? () from /lib/x86_64-linux-gnu/libc.so.6 - __assert_fail () from /lib/x86_64-linux-gnu/libc.so.6 - ?? () -Title: qemu-system-x86_64 crashed with SIGABRT in raise() -UpgradeStatus: Upgraded to raring on 2013-03-31 (0 days ago) -UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo \ No newline at end of file diff --git a/results/classifier/deepseek-2-tmp/output/device/1168 b/results/classifier/deepseek-2-tmp/output/device/1168 deleted file mode 100644 index 1f5c37a1..00000000 --- a/results/classifier/deepseek-2-tmp/output/device/1168 +++ /dev/null @@ -1,14 +0,0 @@ - -ivshmem: ivshmem-doorbell can't notify the MSI-X interrupt on Arm64 guest -Description of problem: -I init several qemu-kvm VMs on my arm64 host, which is a NVIDIA Xavier board. I want to use qemu's ivshmem-doorbell to build a sync shared memory communition with its MSI-X interrupt mechanism. I init the ivshmem-server and ivshmem-client on the host first, after then init the guests. The visul PCI-e device named "Inter-VM shared memory" can be successfully seen in my guests with command "lspci". -I write a driver for this pci-e device to request and handle the MSI-X interrupts, which init well in the guest and can ring or receive from an interrupt vector on other peerID with the driver's IOCTL interface, the peer that receive vector in my environment is the ivshmem-client. However, when i use the ivshmem-client command "int" to ring my guest , the guest can't receive the msi-x interrupt notification. -Steps to reproduce: -1. init ivshmem-server on the host, with command "ivshmem-server -l 4M -M fg-doorbell -n 8 -F -v". -2. init ivshmem-client on the host, with command "ivshmem-client -v". -3. init the qemu-kvm VM . -4. init the driver with "insmod" in guest to request the msi-x interrupt, while "cat /proc/interrupts" shows the interrupt request successfully! -5. on host, ivshmem-client use command "int 1 0" to ring the guest's interrupt trigger, however ,nothing happened. -Additional information: -I am fully sure that there is no problem about the driver I wrote for the pci-e inter-VM shared memory device, for i has tested that the driver works on my X86 PC, where I deployed qemu-x86 VMs and the driver can work well in X86 guests with the inshmem-doorbell mechanism. The ivshmem-client work on host can notify the guest to trigger the correct msix-x interrupt. -Therefore, I digged the msi-x interrupt structure and use devmem tool to write the data to the messageAddress manually, which can correctly trigger the msi-x interrupt in my arm64 guest in the Xavier board, meaning the msi-x interrupt is OK in the guest. So I doubt maybe there is any issue on the ivshmem-doorbell mechanism that ring a interrupt vector in the guset of qemu-aarch64. diff --git a/results/classifier/deepseek-2-tmp/output/device/1173490 b/results/classifier/deepseek-2-tmp/output/device/1173490 deleted file mode 100644 index 5ea58f0d..00000000 --- a/results/classifier/deepseek-2-tmp/output/device/1173490 +++ /dev/null @@ -1,21 +0,0 @@ - -virtio net adapter driver with kvm slow on winxp - -# lsb_release -a -No LSB modules are available. -Distributor ID: Ubuntu -Description: Ubuntu 12.04.1 LTS -Release: 12.04 -Codename: precise - -#virsh version -Compiled against library: libvirt 1.0.4 -Using library: libvirt 1.0.4 -Using API: QEMU 1.0.4 -Running hypervisor: QEMU 1.2.0 - -windows xp clean install with spice-guest-tools-0.52.exe from - http://spice-space.org/download/windows/spice-guest-tools/spice-guest-tools-0.52.exe - -it comes very slow , and the Interrupts process got very high cpu usage(above 60%). -when i switch the net adapter from virtio to default(rtl8139) ,it works well. \ No newline at end of file diff --git a/results/classifier/deepseek-2-tmp/output/device/1174 b/results/classifier/deepseek-2-tmp/output/device/1174 deleted file mode 100644 index dc783fac..00000000 --- a/results/classifier/deepseek-2-tmp/output/device/1174 +++ /dev/null @@ -1,14 +0,0 @@ - -aspeed: Fix first byte in I2C old register mode slave receive -Description of problem: -The first byte of data received through the Aspeed I2C slave controller through the old-register mode (specifically byte-buffered, not pool buffered or DMA buffered) is incorrect. It should be the 8-bit I2C slave address for the transfer, which will be the 7-bit I2C slave address of the I2C controller shifted left 1, and 1 or 0 for the lowest bit (is-slave-to-master-transfer, or is-master-to-slave-transfer). -Steps to reproduce: -You could use the simulated I2C slave EEPROM https://docs.kernel.org/i2c/slave-eeprom-backend.html, but you need another I2C model to send data to it. - -Alternatively, you can take this downstream patch and run the qtest in it. It has a test case for slave-mode rx in old-register mode: - -https://github.com/facebook/openbmc/blob/helium/common/recipes-devtools/qemu/qemu/0008-hw-misc-Add-byte-by-byte-i2c-network-device.patch -Additional information: -I already created the fix, it's pretty simple, I submitted it to the mailing list and Klaus (the author of that section of the Aspeed I2C controller) reviewed it. https://lore.kernel.org/qemu-devel/20220820225712.713209-1-peter@pjd.dev/#t - -This is relatively critical fix, but since slave-mode I2C is not widely used at this point, it's probably fine to ship with this bug. My team uses the master branch for everything anyways. diff --git a/results/classifier/deepseek-2-tmp/output/device/1175 b/results/classifier/deepseek-2-tmp/output/device/1175 deleted file mode 100644 index f3c73441..00000000 --- a/results/classifier/deepseek-2-tmp/output/device/1175 +++ /dev/null @@ -1,9 +0,0 @@ - -Crash / Assert in VVFAT.c while installaling WinXP from QEMU 7.0 running in Raspberry OS -Description of problem: -- Windows XP installation crashes QEMU with : -qemu-system-i386: ../block/vvfat.c:103: array_get: Assertion `index < array->next' failed. -Steps to reproduce: -Use command line above and run WindowsXP installation -Additional information: -Execution also leads to many "Invalid file name" being reported by QEMU diff --git a/results/classifier/deepseek-2-tmp/output/device/1175513 b/results/classifier/deepseek-2-tmp/output/device/1175513 deleted file mode 100644 index e8557ccd..00000000 --- a/results/classifier/deepseek-2-tmp/output/device/1175513 +++ /dev/null @@ -1,12 +0,0 @@ - -Qemu 1.5-git gpu clock control doesn`t work after guest reboot - -I run qemu from git with such command: - -qemu-system-x86_64 -nodefaults -m 4096 -smp 8,cores=4,threads=2,sockets=1 -cpu 'kvm64' -device usb-mouse -M q35 -vga qxl -no-hpet -boot once=c,menu=on -device vfio-pci,host=02:00.0,x-vga=on \ --enable-kvm -monitor stdio -chardev socket,path=/tmp/qga.sock,server,nowait,id=qga0 -device virtio-serial -device virtserialport,chardev=qga0,name=org.qemu.guest_agent.0 -net nic,vlan=0,model=e1000 -net tap,ifname=tap0,script=/etc/guest-ifup -usb -device intel-hda -device hda-duplex \ --drive file='/home//qemu/win7',if=none,id=drive-virtio-disk0,cache=writeback,aio=native,format=qed,discard=on -device virtio-blk-pci,drive=drive-virtio-disk0,id=virtio-disk \ --drive file='/dev/sr0',if=none,id=drive-ide1-0-0,media=cdrom,snapshot=off,format=raw -device ide-drive,bus=ide.1,unit=0,drive=drive-ide1-0-0,id=ide1-0-0 \ --spice port=5930,disable-ticketing - -Before guest (Windows 7) reboot, videocard works in 3D mode with full frequency. But after reboot videocard works in 3D only with powersafe frequency. Then I must reboot host for recover gpu clock control. \ No newline at end of file diff --git a/results/classifier/deepseek-2-tmp/output/device/1176 b/results/classifier/deepseek-2-tmp/output/device/1176 deleted file mode 100644 index 749fb33e..00000000 --- a/results/classifier/deepseek-2-tmp/output/device/1176 +++ /dev/null @@ -1,8 +0,0 @@ - -VVFAT :rw writes from guest (ReactOS, windowsXP) not visible by host -Description of problem: -As described in https://jira.reactos.org/browse/CORE-18327 -While ./LMS is mounted as a :rw VVFAT drive, guest OS (ReactOS) is able to read files BUT when files are "written" from the guest, they are not visible on host side. -QEMU execution is also massively polluted by "invalid file name" messages coming from https://git.qemu.org/?p=qemu.git;a=blob_plain;f=block/vvfat.c;hb=HEAD (but this is not specific to the use with ReactOS, as this is also observed with other guest : WXP, ...) - -See attached screenshot showing WXPSP3 as guest with file created in VVFAT drive while guest misses the newly created file. diff --git a/results/classifier/deepseek-2-tmp/output/device/118 b/results/classifier/deepseek-2-tmp/output/device/118 deleted file mode 100644 index e50eb4e1..00000000 --- a/results/classifier/deepseek-2-tmp/output/device/118 +++ /dev/null @@ -1,2 +0,0 @@ - -USB device 1.1 not correctly passedthru from Linux host to Windows guest diff --git a/results/classifier/deepseek-2-tmp/output/device/1181796 b/results/classifier/deepseek-2-tmp/output/device/1181796 deleted file mode 100644 index 09e59666..00000000 --- a/results/classifier/deepseek-2-tmp/output/device/1181796 +++ /dev/null @@ -1,10 +0,0 @@ - -Qemu locks up when incoming serial fills up - -I'm using Windows, I'm not sure if this happens on Linux, but for all I know it does. To repro, fire up any image (ideally one that does almost nothing, and doesn't read the serial port), and use the option "-serial pipe:mypipe". Then use Putty or something else to connect to that named pipe so Qemu starts up. Now start typing into Putty. For a VM image that never reads the serial port, upon typing the 16th character Qemu stops executing instructions in the guest (as evidenced either by being unable to step in gdb, seeing that "info registers" in the monitor always reports the same value, or just by observing that the guest is hung). For OS images that do regularly read the serial port, this may require pasting >16 bytes into Putty at once. This occurs with more than just Putty, use anything that can write at a named pipe. - -I would have expected that bytes get dropped, or even more ideally blocked at the sender's side of the named pipe. I would not expect that the entire VM stops. You seem to be able to unwedge the VM by switching to the monitor and running "i /1c 0x3f8" until you've pulled enough out of buffer that it's happy to run again. Interestingly, all bytes seem to come through (more than just the 16) when read from the monitor. - -I haven't been able to get a source environment set up, but I have tried a few of the Windows binaries. This repros in 1.4.1, 1.3.0, 1.2, and 1.0, the most recent build I found that did not have this behavior was 0.15.0. - -Maybe I'm missing something very obvious, and if so, I apologize in advance. I'm also happy to create an OS image that highlights this problem if it would help. \ No newline at end of file diff --git a/results/classifier/deepseek-2-tmp/output/device/1185888 b/results/classifier/deepseek-2-tmp/output/device/1185888 deleted file mode 100644 index 30ada1ea..00000000 --- a/results/classifier/deepseek-2-tmp/output/device/1185888 +++ /dev/null @@ -1,26 +0,0 @@ - --device nec-usb-xhci (usb 3) breaks VM snapshots - -Enabling the USB 3.0 controller apparently breaks "live" snapshotting. - -To reproduce: - - $ qemu-system-x86_64 -device nec-usb-xhci vm.qcow2 - -then, at the Monitor: - - (qemu) savevm - Error -22 while writing VM - (qemu) - -Instead, if I remove -device nec-usb-xhci from the cmdline, everything works fine. - -Some QEMU and OS info: - - $ qemu-system-x86_64 -version - QEMU emulator version 1.5.0, Copyright (c) 2003-2008 Fabrice Bellard - - $ uname -a - Linux localhost 3.2.0-4-amd64 #1 SMP Debian 3.2.41-2 x86_64 GNU/Linux - -The same also happens with 1.4.2. All compiled from source, not Debiabn package (btw, this *also* happens with distro packages/older versions). \ No newline at end of file diff --git a/results/classifier/deepseek-2-tmp/output/device/1186303 b/results/classifier/deepseek-2-tmp/output/device/1186303 deleted file mode 100644 index 3f329d01..00000000 --- a/results/classifier/deepseek-2-tmp/output/device/1186303 +++ /dev/null @@ -1,23 +0,0 @@ - -virtual fat do not working in qemu 1.5.0 - -Guest : windows Seven / XP -Qemu version : 1.5.0 -cmd line : --drive file=fat:floppy:/mnt/vdisk/diskconf/TEST004/,if=none,id=drive-fdc0-0-0,readonly=on -generated by libvirt : - - - - - - - -
- - -works with qemu <= 1.4.1 - -with qemu 1.5.0 , guest does not see the floppy content. - -Regards \ No newline at end of file diff --git a/results/classifier/deepseek-2-tmp/output/device/1187529 b/results/classifier/deepseek-2-tmp/output/device/1187529 deleted file mode 100644 index 065f91fb..00000000 --- a/results/classifier/deepseek-2-tmp/output/device/1187529 +++ /dev/null @@ -1,12 +0,0 @@ - -Devices on PCI bridge stop working when live-migrated - -qemu version: 1.4.50 (0ca5aa4f4c4a8bcc73988dd52a536241d35e5223) -host: x86_64, Linux 3.6.10 (Fedora 17) -client: x86_64 Centos 6.3 (doesn't matter, really) - -If a device, e.g. an lsi53c895a, is on a pci-bridge, after migration, the device stops working (e.g., commands like "poweroff" -get an Input/Output error. Fails under either xen or kvm. If "top" was running, some cpus go to ~100% wait. - -Sample KVM invocation line: -qemu-system-x86_64 -machine type=pc,accel=kvm -m 4096 -device pci-bridgemsi=on,chassis_nr=1,id=pciBridge1.0,addr=0x11.0 -device lsi53c895a,id=sas,bus=pciBridge1.0,addr=0x1.0x0 -drive if=none,id=disk0,file=/path/to/disk/image -device scsi-disk,bus=sas.0,scsi-id=0,drive=disk0 -vnc 127.0.0.1:0,to=99 -serial pty -boot order=cda -smp 4,maxcpus=4 -monitor vc \ No newline at end of file diff --git a/results/classifier/deepseek-2-tmp/output/device/1188018 b/results/classifier/deepseek-2-tmp/output/device/1188018 deleted file mode 100644 index e2e0c573..00000000 --- a/results/classifier/deepseek-2-tmp/output/device/1188018 +++ /dev/null @@ -1,6 +0,0 @@ - -qemu monitor does not suppot rbd "savevm" command - -1. I used ceph rbd as my block device, /usr/local/bin/qemu-system-x86_64 -drive format=rbd,file=rbd:rbd/sles.img:rbd_cache=true,cache=writeback -boot c -m 1024 -enable-kvm -vnc 0.0.0.0:0 -monitor stdio - -2. when in monitor command line "savevm", it reports "Error -95 while writing VM" in the monitor \ No newline at end of file diff --git a/results/classifier/deepseek-2-tmp/output/device/1188991 b/results/classifier/deepseek-2-tmp/output/device/1188991 deleted file mode 100644 index 7b8c79df..00000000 --- a/results/classifier/deepseek-2-tmp/output/device/1188991 +++ /dev/null @@ -1,61 +0,0 @@ - -Unable to do serial communication using -chardev tty - - - -Im running an Linux Image (kernel 3.2.8) for beagleboard-xm on QEMU's 1.4.0 emulator. - - -What I want to do is to have a communication between guest and host across serial the 4 differents ttyO present on the guest. QEMU offer facilities to redirect the trafic to some device in the host side. - -The command that I use to lauch QEMU is : - - sudo qemu-system-arm -M beaglexm -m 1024 -sd ./test.img -clock unix -see -device usb-kbd -chardev tty,id=mytty,path=/dev/ttyS0 - -As it says in the QEMU's manual -chardev is suppose to connect to a local tty device at the path given - -My problem goes like this: - -At the guest kernel boot I'm able to see that my UART where enabled - - [ 2.682040] Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled - [ 2.777947] omap_uart.0: ttyO0 at MMIO 0x4806a000 (irq = 72) is a OMAP UART0 - [ 2.794967] omap_uart.1: ttyO1 at MMIO 0x4806c000 (irq = 73) is a OMAP UART1 - [ 2.814942] omap_uart.2: ttyO2 at MMIO 0x49020000 (irq = 74) is a OMAP UART2 - [ 2.966825] console [ttyO2] enabled - [ 2.984777] omap_uart.3: ttyO3 at MMIO 0x49042000 (irq = 80) is a OMAP UART3 - -In fact, when I go see in to /proc/tty/driver and I do a cat on OMAP-SERIAL Im able to see this serinfo:1.0 driver revision: - - 0: uart:OMAP UART0 mmio:0x4806A000 irq:72 tx:0 rx:0 CTS|DSR|CD - 1: uart:OMAP UART1 mmio:0x4806C000 irq:73 tx:0 rx:0 CTS|DSR|CD - 2: uart:OMAP UART2 mmio:0x49020000 irq:74 tx:268 rx:37 RTS|CTS|DTR|DSR|CD - 3: uart:OMAP UART3 mmio:0x49042000 irq:80 tx:0 rx:0 CTS|DSR|CD - -I know that ttyO2 is working because my console is been redirected to it. The thing is that doing a set serial on any of the ttyO I get the following message: - - [root@enu driver]# setserial -a /dev/ttyO0 - /dev/ttyO0, Line 0, UART: undefined, Port: 0x0000, IRQ: 72 - Baud_base: 3000000, close_delay: 50, divisor: 0 - closing_wait: 3000 - Flags: spd_normal - -The same goes with ttyO2. I tryed to set some sethings to any of the ttyO with setserial but I always get the same message: - - [root@enu ~]# setserial /dev/ttyO0 uart 8250 - setserial: can't set serial info: Invalid argument - [root@enu ~]# setserial /dev/ttyO0 port 0x4806a000 - setserial: can't set serial info: Invalid argument - -basicly I want to establish a serial communication between a guest and a host, but the serial ports on the guest side aren't well configured. - -When I open ttyS0 with minicom on the host side and do on the guest side - - echo "test" > /dev/ttyO0 - -The host recives nothing. - -Anyone can tell me how I could remove tty modules on the guest side and try to insert it again to see if the setup resets properly or give me any advice on how to solve this problem. Plus if anyone has already tryed doing this kind on serial communication I would like to here from you. - -Thank, -Francisco \ No newline at end of file diff --git a/results/classifier/deepseek-2-tmp/output/device/1191 b/results/classifier/deepseek-2-tmp/output/device/1191 deleted file mode 100644 index c13787af..00000000 --- a/results/classifier/deepseek-2-tmp/output/device/1191 +++ /dev/null @@ -1,10 +0,0 @@ - -AC97+CoreAudio no audio when out frequency not 44,1KHz & always forces host to use 44,1KHz (or less if frequency not supported) -Description of problem: -AC97+CoreAudio outputs no audio when output frequency not 44,1KHz. Also always forces host to use 44,1KHz (or less if frequency not supported on host output) -Steps to reproduce: -1. Boot any OS with (only) AC97 audio on macOS -2. Attempt to play audio with output frequency in guest set to 48KHz -3. Observe lack of output -Additional information: -I'm using QEMU to test a Custom OS written by me, but this shouldn't be a code issue on our side, rather an issue with QEMU itself, if this is mistaken, please inform us. diff --git a/results/classifier/deepseek-2-tmp/output/device/1191326 b/results/classifier/deepseek-2-tmp/output/device/1191326 deleted file mode 100644 index 1d941c08..00000000 --- a/results/classifier/deepseek-2-tmp/output/device/1191326 +++ /dev/null @@ -1,16 +0,0 @@ - -QNX 4 doesn't boot on qemu >= 1.3 - - -I am using virtual machine with QNX4 operating system installed on it. I updated my qemu from version -to newer and QNX4 doesn't start any more. All is ok on version 1.2 but when I try to use any newer version -(1.3, 1.4, 1.5) QNX4 doesn't boot. I tried on windows and linux ubuntu hosts - effects are the same. - -When virtual machine boots qnx bootloader loads and starts operating system. In the next step -qnx starts its ide driver, which detects qemu harddisk and cdrom. Problem starts when operating system -tries mount partition - an error occur and qnx stop booting procedure: - -mount -p "No bios signature in partition sector on /dev/hd0" - -I have tried install qnx from cdrom but it seems that there is the same problem. QNX installer boot from -cdrom, detects hard disk and cdrom, but cdrom can't be mounted in the next step of installation procedure. \ No newline at end of file diff --git a/results/classifier/deepseek-2-tmp/output/device/1193 b/results/classifier/deepseek-2-tmp/output/device/1193 deleted file mode 100644 index f560436b..00000000 --- a/results/classifier/deepseek-2-tmp/output/device/1193 +++ /dev/null @@ -1,17 +0,0 @@ - -io_uring / iothread regression 7.1.0 -Description of problem: -After upgrading to 7.1.0, some of my libvirt VM's failed to boot. I have narrowed down the issue to the combination of: - -- io_uring -- iothread -Steps to reproduce: -1. set up a VM with iothread and io_uring -2. try to boot and watch it "hang" -Additional information: -Here's the relevant command line from the libvirt log: -``` --blockdev '{"driver":"file","filename":"/mnt/data/VMs/Arch-Linux-x86_64-basic.qcow2","aio":"io_uring","node-name":"libvirt-1-storage","auto-read-only":true,"discard":"unmap"}' \ --blockdev '{"node-name":"libvirt-1-format","read-only":false,"driver":"qcow2","file":"libvirt-1-storage","backing":null}' \ --device '{"driver":"virtio-blk-pci","iothread":"iothread1","bus":"pci.4","addr":"0x0","drive":"libvirt-1-format","id":"virtio-disk0","bootindex":1 }' \ -``` diff --git a/results/classifier/deepseek-2-tmp/output/device/1194954 b/results/classifier/deepseek-2-tmp/output/device/1194954 deleted file mode 100644 index 8ca7e71e..00000000 --- a/results/classifier/deepseek-2-tmp/output/device/1194954 +++ /dev/null @@ -1,4 +0,0 @@ - -Windows 95 guest reboots itself on qemu 1.5.0 & 1.5.50 (GIT) - -When I begin to run a Windows 95 guest on these releases of qemu, it reboots itself more times without my permission (eg. without shutting it down properly), and when I'm installing Netscape 4.08 at, for example, 46% or 75%, it still reboots itself without completing the installation of the web browser. Is this an issue of main-loop.c? \ No newline at end of file diff --git a/results/classifier/deepseek-2-tmp/output/device/1196145 b/results/classifier/deepseek-2-tmp/output/device/1196145 deleted file mode 100644 index 45db9129..00000000 --- a/results/classifier/deepseek-2-tmp/output/device/1196145 +++ /dev/null @@ -1,19 +0,0 @@ - -usb-host: hostaddr=0XX is parsed as octal number - -when doing - -device_add usb-host,hostaddr=010 - -taking 010 in the format of both lsusb or udev, qemu parses an octal number and assumes hostaddr=8. -(i used a 2.0 device on the ehci.0 bus) -at least to me that is confusing. - -also: - -when adding a non-existent usb device (bogus hostaddr), the following is created according to 'usb info': - - Device 1.0, Port 1, Speed 1.5 Mb/s, Product USB Host Device - -in usb_qdev_init(): -usb_claim_port is called but usb_device_init does not report an error and thus usb_release_port is not called. \ No newline at end of file diff --git a/results/classifier/deepseek-2-tmp/output/device/1198350 b/results/classifier/deepseek-2-tmp/output/device/1198350 deleted file mode 100644 index 3a0bbd63..00000000 --- a/results/classifier/deepseek-2-tmp/output/device/1198350 +++ /dev/null @@ -1,46 +0,0 @@ - -USB pass-through fails with USBDEVFS_DISCONNECT: Invalid argument - -Host Gentoo linux 32bit -Guest Windows XP SP3 -qemu 1.4.2 and -qemu fresh get clone and build 2013-07-04 (version1.5.50) -qemu command line - -qemu-system-i386 -enable-kvm localtime -m 2047 -boot d /archive3/qemu/WindowsXP.img -net nic,model=rtl8139 -net user -usb -device usb-ehci,id=ehci -usbdevice host:1493:19 - -The device I am trying to use with the guest is an interface for the Suunto Ambit 2 GPS watch which has no linux support. - -When the USB device is plugged in qemu reports to the command line: - -USBDEVFS_DISCONNECT: Invalid argument -Invalid argument - -dmesg shows - -[237755.495968] usb 2-1.5: new full-speed USB device number 34 using ehci-pci -[237755.582778] usb 2-1.5: config 1 has an invalid interface number: 1 but max is 0 -[237755.582781] usb 2-1.5: config 1 has no interface number 0 -[237755.583628] usb 2-1.5: New USB device found, idVendor=1493, idProduct=0019 -[237755.583631] usb 2-1.5: New USB device strings: Mfr=1, Product=2, SerialNumber=3 -[237755.583633] usb 2-1.5: Product: Ambit -[237755.583634] usb 2-1.5: Manufacturer: Suunto -[237755.583636] usb 2-1.5: SerialNumber: CE83095110000700 -[237756.584937] usb 2-1.5: reset full-speed USB device number 34 using ehci-pci -[237756.832658] usb 2-1.5: reset full-speed USB device number 34 using ehci-pci -[237757.143585] usb 2-1.5: usbfs: process 12684 (qemu-system-i38) did not claim interface 1 before use - -In the windows guest Device Manager a HID device is listed but nothing else happens, no found new hardware dialog or the Suunto software (which is sitting there waiting) is not triggered as it should be. - -I have tried successfully with several other devices (flash drive, mouse, printer and video capture device). Because this device pretends to be an HID device my kernel's hid-generic driver was picking it up first until I modified hid-core.c to ignore this vendorid/productid. But still no joy. - -I'm guessing it has something to do with the the dmesg lines: - -[237755.582778] usb 2-1.5: config 1 has an invalid interface number: 1 but max is 0 -[237755.582781] usb 2-1.5: config 1 has no interface number 0 - -But read that these warnings are not important though I don't get them for other devices. Nor do I get: - -[237757.143585] usb 2-1.5: usbfs: process 12684 (qemu-system-i38) did not claim interface 1 before use - -I've done alot of searching and I've run out of ideas. Any help would be great. \ No newline at end of file diff --git a/results/classifier/deepseek-2-tmp/output/device/1200212 b/results/classifier/deepseek-2-tmp/output/device/1200212 deleted file mode 100644 index 8393ea51..00000000 --- a/results/classifier/deepseek-2-tmp/output/device/1200212 +++ /dev/null @@ -1,15 +0,0 @@ - -qemu-system-arm aborts in lsi_soft_reset - -Qemu compiled from master branch (fetched on 11th Jul 2013, qemu-system-arm -version prints "QEMU emulator version 1.5.50, Copyright (c) 2003-2008 Fabrice Bellard") running on OSX 10.6.8 crashes during Debian 7.1 netboot installation with error: "Assertion failed: (QTAILQ_EMPTY(&s->queue)), function lsi_soft_reset, file hw/scsi/lsi53c895a.c, line 351." - -Steps to reproduce: - -1. Get kernel and initrd from http://ftp.debian.org/debian/dists/Debian7.1/main/installer-armel/20130613/images/versatile/netboot/ . -2. Create a hard disk image with qemu-img: qemu-img create -f qcow2 debian.qcow2 2G. -3. Run arm-softmmu/qemu-system-arm -M versatilepb -kernel vmlinuz-3.2.0-4-versatile \ - -initrd initrd-3.2.0-4-versatile-netboot -drive file=debian.qcow2,index=0,if=scsi,media=disk \ - -append "console=ttyAMA0" -nographic -net user,hostfwd=tcp:127.0.0.1:22080-:80,vlan=0 \ - -net nic,vlan=0 -smp 1,cores=4 - -The installation should proceed past partition setup and start downloading packages onto hard disk. After several tries I've never got past 31% with the package downloads before getting Abort trap with "Assertion failed: (QTAILQ_EMPTY(&s->queue)), function lsi_soft_reset, file hw/scsi/lsi53c895a.c, line 351." message. \ No newline at end of file diff --git a/results/classifier/deepseek-2-tmp/output/device/1207228 b/results/classifier/deepseek-2-tmp/output/device/1207228 deleted file mode 100644 index 876f0945..00000000 --- a/results/classifier/deepseek-2-tmp/output/device/1207228 +++ /dev/null @@ -1,14 +0,0 @@ - -Qemu (trunk code) crashes when using --soundhw all option in ioport.c - -After not building qemu (git version) for about 3 weeks, I've done it again this morning. - -With up-to-date trunk code, I got this error on start, when using --soundhw all option - -$ qemu-system-i386 -soundhw all -qemu-system-i386: /home/fred/Téléchargements/logs/qemu-git/src/qemu/ioport.c:240: portio_list_add: Assertion `pio->offset >= off_last' failed. -Abandon (core dumped) - -And if I use only soundhw with one or more options, it doesn't crash. - -Tell me what you'll need to fix this bug. \ No newline at end of file diff --git a/results/classifier/deepseek-2-tmp/output/device/1219234 b/results/classifier/deepseek-2-tmp/output/device/1219234 deleted file mode 100644 index 0d3e6bd4..00000000 --- a/results/classifier/deepseek-2-tmp/output/device/1219234 +++ /dev/null @@ -1,15 +0,0 @@ - --device ide-hd will assign bus with with no free units - -Originally filed here: https://bugzilla.redhat.com/show_bug.cgi?id=1000118 - -./x86_64-softmmu/qemu-system-x86_64 -device ahci -drive id=aa,file=/tmp/foo,if=none -drive id=bb,file=/tmp/foo,if=none -device ide-hd,drive=aa -device ide-hd,drive=bb -qemu-system-x86_64: -device ide-hd,drive=bb: Can't create IDE unit 1, bus supports only 1 units -qemu-system-x86_64: -device ide-hd,drive=bb: Device initialization failed. -qemu-system-x86_64: -device ide-hd,drive=bb: Device 'ide-hd' could not be initialized - -If a bus isn't specified for -device ide-hd, it just uses the first bus it finds, not taking into account if that bus was already assigned for another device. So users are forced to do -device ide-hd,bus=ide.0 -device ide-hd,bus=ide.1, etc. - -This isn't specific to -device ahci, but it's worse there since there isn't any -drive if=IDE or -hda convenience option, which both seem to get the logic correct. - -I know -device is the 'build it yourself' approach so I understand if this is WONTFIX. \ No newline at end of file diff --git a/results/classifier/deepseek-2-tmp/output/device/1220 b/results/classifier/deepseek-2-tmp/output/device/1220 deleted file mode 100644 index 0c7c9d8a..00000000 --- a/results/classifier/deepseek-2-tmp/output/device/1220 +++ /dev/null @@ -1,17 +0,0 @@ - -when migrate,I unplugged the disk, why can't I force cancel the job task use qmp -Description of problem: -when migrate,I unplugged the disk,the block job will hung,but why can't I force cancel the job task -Steps to reproduce: -1.migrate a guset to another host with non-share disk (iscsi) - -2.unplug the disk - -3.then force cancel the block job task - - -but it not work,the cancle handle is not work - -![image](/uploads/e01464f45188df92abc1fe15ccd96777/image.png) - -![image](/uploads/0b8ebb654eae4feae06e7fa6dba071ea/image.png) diff --git a/results/classifier/deepseek-2-tmp/output/device/1222034 b/results/classifier/deepseek-2-tmp/output/device/1222034 deleted file mode 100644 index 6d84b913..00000000 --- a/results/classifier/deepseek-2-tmp/output/device/1222034 +++ /dev/null @@ -1,20 +0,0 @@ - -QEMU + SPICE + AUDIO = FAILURE - -Hello it's my first time doing this, since the major round of timer/block changes in August I have not been able to have audio working in any guest with the spice protocol. - -64 bit linux , AMD SVM, IOMMUv1 M5A99X EVO R2.0 - - -Example command line: - -qemu-system-x86_64 -m 1024 -cdrom /common/stor8/torrents/Sabayon_Linux_DAILY_x86_Xfce.iso -soundhw hda -vga qxl -spice port=5999,addr=0.0.0.0,disable-ticketing -enable-kvm - - - -Any time the guest tries to access the emulated hardware it will hang for a very long period of time and play no audio through spice. - -This issue does not happen with the 1.6.0 release. - - -If you are unable to replicate this I will go to the trouble of getting the race message that happens in the guest but I am assuming at this point that my configuration is not exotic and it should be very easy to see the issue. \ No newline at end of file diff --git a/results/classifier/deepseek-2-tmp/output/device/1223467 b/results/classifier/deepseek-2-tmp/output/device/1223467 deleted file mode 100644 index 68730f60..00000000 --- a/results/classifier/deepseek-2-tmp/output/device/1223467 +++ /dev/null @@ -1,23 +0,0 @@ - -Unable to use USB as hda in Windows - -I built qemu 1.6.0 from source in MinGW (and all dependents not available with mingw-get) -The command line: -qemu-system-i386.exe -m 1024 -hda \\.\PhysicalDrive1 -L pc-bios -or -qemu-system-x86_64.exe -m 1024 -hda \\.\PhysicalDrive1 -L pc-bios -(or the *w.exe equivalents) -reports in stderr.txt: -qemu-system-i386.exe: -hda \\.\PhysicalDrive1: Block protocol 'host_device' doesn't support the option 'filename' -qemu-system-i386.exe: -hda \\.\PhysicalDrive1: could not open disk image \\.\PhysicalDrive1: Invalid argument - -I have also found this bug in 1.5 but not in 1.4 - -Some Help: -The code in Qemu is a bit beyond me at 1am, but I was able to determine the root cause seems to be that block.c is becoming confused about referring to a file but not having a file name. I have been able to work around this by changing line 860 of block.c from: "if (qdict_size(options) != 0) {" to "if (qdict_size(options) != 0 && !is_windows_drive(filename)) {" - -But I don't think this is a good solution (it is assuming that nothing else could be wrong), and I can't be sure that I'm not masking some real issue. - -FWIW; Build is on XP, but execution is on Win7. - -Thanks. \ No newline at end of file diff --git a/results/classifier/deepseek-2-tmp/output/device/1223477 b/results/classifier/deepseek-2-tmp/output/device/1223477 deleted file mode 100644 index 48b1cf6c..00000000 --- a/results/classifier/deepseek-2-tmp/output/device/1223477 +++ /dev/null @@ -1,31 +0,0 @@ - -Unable to read USB filesystems with EFI Bios - -Preamble and version: -With respect to my fix for using USB devices as -hda mentioned in bug 1223467 -Using Qemu 1.6.0 with OVMF r11337-alpha (Qemu is built from Source, OVMF is pre built) - -Command: -qemu-system-i386.exe -m 1024 -hda \\.\PhysicalDrive1 -L ovmf-ia32 - -Fault: -The EFI Shell is able to detect the hda block device, report its capacity and usage; -but it sees no files or directories on the device. - -Similar commands: -I have also seen the same with -qemu-system-x86_64.exe -m 1024 -hda \\.\PhysicalDrive1 -L ovmf-ia32 -and -qemu-system-x86_64.exe -m 1024 -hda \\.\PhysicalDrive1 -L ovmf-x64 - -Investigations: -I tried very small (500MB) and very large (32 GB) USB devices with no difference. -I re-built several versions of Qemu in an identical build environment, and found that: -Qemu 1.2.2 and before, all the above commands work and the EFI boot loader is called. -Qemu 1.3.0-rc0 and after do not work and the USB device appears blank. -I'm reporting the bug here and not with OVMF because older versions of Qemu with the same OVMF bios work perfectly. - -In all cases using '-L pc-bios' works perfectly. -In all cases using an image of the USB device works. - -Thanks \ No newline at end of file diff --git a/results/classifier/deepseek-2-tmp/output/device/1225187 b/results/classifier/deepseek-2-tmp/output/device/1225187 deleted file mode 100644 index 37eeface..00000000 --- a/results/classifier/deepseek-2-tmp/output/device/1225187 +++ /dev/null @@ -1,13 +0,0 @@ - -qemu hangs in windows 7 host with -serial pipe:windbg - -Execution line: -qemu-system-i386.exe -m 512 c:\Disks\Qemu_XP_en.vhd -serial pipe:windbg - -It waits for the pipe. -Execute windbg -c:\WINDDK\7600.16385.1\Debuggers\windbg.exe -k com:pipe,port=\\.\pipe\windbg,resets=0,reconnect - -GUI black screen shown. QEMU hangs. - -qemu v1.5.3 (c0b1a7e207094dba0b37a892b41fe4cab3195e44). MinGW built. \ No newline at end of file diff --git a/results/classifier/deepseek-2-tmp/output/device/1226 b/results/classifier/deepseek-2-tmp/output/device/1226 deleted file mode 100644 index 94e0b377..00000000 --- a/results/classifier/deepseek-2-tmp/output/device/1226 +++ /dev/null @@ -1,26 +0,0 @@ - -wheel-axis=false does not get applied at hardware init stage -Description of problem: -`-device virtio-tablet,id=touch0,wheel-axis=false` does not get applied at initalization stage, causing android to see it and treat the device as a pointer instead of a tablet. it seems to look for the prop at init stage, I have verified that this is an issue by fixing it with a quick hack below. ~~setting `-device virtio-tablet,id=touch0,wheel-axis=true` will still work fine and cause android to pick it up as a pointer again~~ - - -EDIT: It does not seem to work actually. if set when the default is set to false -Steps to reproduce: -1. Boot android based VM -2. test an app that forces touch only over pointer -Additional information: -``` -diff --git a/hw/input/virtio-input-hid.c b/hw/input/virtio-input-hid.c -index a7a244a95d..3175f9c7d5 100644 ---- a/hw/input/virtio-input-hid.c -+++ b/hw/input/virtio-input-hid.c -@@ -477,7 +477,7 @@ static struct virtio_input_config virtio_tablet_config_v2[] = { - }; - - static Property virtio_tablet_properties[] = { -- DEFINE_PROP_BOOL("wheel-axis", VirtIOInputHID, wheel_axis, true), -+ DEFINE_PROP_BOOL("wheel-axis", VirtIOInputHID, wheel_axis, false), - DEFINE_PROP_END_OF_LIST(), - }; - -``` diff --git a/results/classifier/deepseek-2-tmp/output/device/1230232 b/results/classifier/deepseek-2-tmp/output/device/1230232 deleted file mode 100644 index 5b4b461f..00000000 --- a/results/classifier/deepseek-2-tmp/output/device/1230232 +++ /dev/null @@ -1,34 +0,0 @@ - -mac99 does not find mac os x 10.4 dvd - -Hi there, - -I've compiled qemu 1.6.0 and ripped my Mac OS X 10.4 dvd to iso format. -Now I'm trying to get qemu to boot the dvd and install the OS with: - -qemu-system-ppc64 -M mac99 -m 256 -cdrom ./tiger.iso -boot d -sdl -display sdl -net nic -net user -prom-env 'boot-args=-v' -cpu G4 -hda ./tiger.img - -It shows the grey apple logo for a few seconds and then I get the following boot prompt: -------------------------------------------------- -standard timeslicing quantum is 10000 us -vm_page_bootstrap: 60198 free pages -mig_table_max_displ = 70 -Copyright (c) 1982, 1986, 1989, 1991, 1993 - The Regents of the University of California. All rights reserved. - -using 655 buffer headers and 655 cluster IO buffer headers -ApplePlatformExpert::getGMTTimeOfDay can not provide time of day RTC did not show up -Security auditing service present -BSM auditing present -disabled -rooting via boot-uuid from /chosen: 8ABB5AFF-FC7A-310A-9BFE-8A263F654562 -Waiting on IOProviderClassIOResourcesIOResource -Matchboot-uuid-media -Still waiting for root device -Still waiting for root device -Still waiting for root device -Still waiting for root device -Still waiting for root device -------------------------------------------------- - -It keeps repeating the "Still waiting for root device" ? \ No newline at end of file diff --git a/results/classifier/deepseek-2-tmp/output/device/1234 b/results/classifier/deepseek-2-tmp/output/device/1234 deleted file mode 100644 index c7351fcd..00000000 --- a/results/classifier/deepseek-2-tmp/output/device/1234 +++ /dev/null @@ -1,4 +0,0 @@ - -Migration: Device state not saved for msmouse/chardevs -Additional information: -This missing feature was discovered while fixing msmouse here: https://patchew.org/QEMU/20220908173120.16779-1-arwed.meyer@gmx.de/20220908173120.16779-2-arwed.meyer@gmx.de/ diff --git a/results/classifier/deepseek-2-tmp/output/device/1237 b/results/classifier/deepseek-2-tmp/output/device/1237 deleted file mode 100644 index 5ccfd4df..00000000 --- a/results/classifier/deepseek-2-tmp/output/device/1237 +++ /dev/null @@ -1,2 +0,0 @@ - -after OS upgrade usb-redir connection broken during migration and qemu-kvm: terminating on signal 15 diff --git a/results/classifier/deepseek-2-tmp/output/device/1237625 b/results/classifier/deepseek-2-tmp/output/device/1237625 deleted file mode 100644 index 9ff3d040..00000000 --- a/results/classifier/deepseek-2-tmp/output/device/1237625 +++ /dev/null @@ -1,49 +0,0 @@ - -Cannot read serial from /sys/bus/usb/devices/ - -After an update to qemu 1.6 I can't start any of my images. Qemu always crashs. I tried it with root and as a normal user... Here are some log entries I get: - -Type: Warning Num: 85 -Date: 2013.10.09 23:48:46 549 -Sender: bool System_Info::Scan_USB_Sys( QList &list ) -Message: Cannot read serial from /sys/bus/usb/devices/ - -Type: Debug Num: 86 -Date: 2013.10.09 23:48:46 553 -Sender: void Virtual_Machine::QEMU_Started() -Message: QEMU Start - -Type: Debug Num: 87 -Date: 2013.10.09 23:48:46 554 -Sender: bool Virtual_Machine::operator==( const Virtual_Machine &vm ) const -Message: Begin - -Type: Debug Num: 88 -Date: 2013.10.09 23:48:46 554 -Sender: bool Virtual_Machine::operator==( const Virtual_Machine &vm ) const -Message: End - -Type: Debug Num: 89 -Date: 2013.10.09 23:48:46 575 -Sender: void Virtual_Machine::QEMU_Started() -Message: emit Loading_Complete() - -Type: Debug Num: 90 -Date: 2013.10.09 23:48:47 470 -Sender: void Virtual_Machine::QEMU_Finished( int exitCode, QProcess::ExitStatus exitStatus ) -Message: QEMU Finished - -Type: Debug Num: 91 -Date: 2013.10.09 23:48:47 470 -Sender: bool Virtual_Machine::operator==( const Virtual_Machine &vm ) const -Message: Begin - -Type: Debug Num: 92 -Date: 2013.10.09 23:48:47 470 -Sender: bool Virtual_Machine::operator==( const Virtual_Machine &vm ) const -Message: End - -Type: Error Num: 93 -Date: 2013.10.09 23:48:47 498 -Sender: QEMU Crashed! -Message: \ No newline at end of file diff --git a/results/classifier/deepseek-2-tmp/output/device/1242765 b/results/classifier/deepseek-2-tmp/output/device/1242765 deleted file mode 100644 index 2431ee92..00000000 --- a/results/classifier/deepseek-2-tmp/output/device/1242765 +++ /dev/null @@ -1,70 +0,0 @@ - -USB passthrough to Windows 7 guest fails with error -110, hangs - -Description of problem: - -Using a Sandisk Cruzer Fit 16GB USB thumb drive. -Using virt-manager on Fedora 19 host, and Windows 7 32 bit guest. - -I set up a USB2 controller on Windows 7 guest in virt-manager. Windows sees the USB drive and can open the file manager and correctly show the files. I can copy a file from the thumb drive to the Fedora desktop, and then play the file on the desktop. However, any attempt to open a file directly on the thumb drive (example, play an MP3 using Windows Media Player) results in guest hang and host kernel messages: - - -Oct 19 21:15:35 localhost kernel: [187592.977839] usb 1-1.3: reset high-speed USB device number 13 using ehci-pci -Oct 19 21:15:40 localhost kernel: [187598.065274] usb 1-1.3: device descriptor read/all, error -110 -Oct 19 21:15:40 localhost kernel: [187598.138167] usb 1-1.3: reset high-speed USB device number 13 using ehci-pci -Oct 19 21:15:56 localhost kernel: [187613.218119] usb 1-1.3: device descriptor read/64, error -110 -Oct 19 21:16:11 localhost kernel: [187628.399275] usb 1-1.3: device descriptor read/64, error -110 -Oct 19 21:16:11 localhost kernel: [187628.573355] usb 1-1.3: reset high-speed USB device number 13 using ehci-pci -Oct 19 21:16:16 localhost kernel: [187633.587778] usb 1-1.3: device descriptor read/8, error -110 -Oct 19 21:16:21 localhost kernel: [187638.702244] usb 1-1.3: device descriptor read/8, error -110 -Oct 19 21:16:21 localhost kernel: [187638.876201] usb 1-1.3: reset high-speed USB device number 13 using ehci-pci -Oct 19 21:16:26 localhost kernel: [187643.890642] usb 1-1.3: device descriptor read/8, error -110 -Oct 19 21:16:31 localhost kernel: [187649.005071] usb 1-1.3: device descriptor read/8, error -110 -Oct 19 21:16:31 localhost kernel: [187649.106188] usb 1-1.3: USB disconnect, device number 13 -Oct 19 21:16:31 localhost kernel: [187649.178969] usb 1-1.3: new high-speed USB device number 14 using ehci-pci -Oct 19 21:16:47 localhost kernel: [187664.258945] usb 1-1.3: device descriptor read/64, error -110 -Oct 19 21:17:02 localhost kernel: [187679.440092] usb 1-1.3: device descriptor read/64, error -110 -Oct 19 21:17:02 localhost kernel: [187679.614194] usb 1-1.3: new high-speed USB device number 15 using ehci-pci -Oct 19 21:17:17 localhost kernel: [187694.694148] usb 1-1.3: device descriptor read/64, error -110 -Oct 19 21:17:32 localhost kernel: [187709.875297] usb 1-1.3: device descriptor read/64, error -110 -Oct 19 21:17:32 localhost kernel: [187710.049386] usb 1-1.3: new high-speed USB device number 16 using ehci-pci -Oct 19 21:17:37 localhost kernel: [187715.063803] usb 1-1.3: device descriptor read/8, error -110 -Oct 19 21:17:41 localhost kernel: [187719.005453] usb 1-1.3: device descriptor read/8, error -71 - -After that -71 error, the thumb drive completely disappears from the host, as if it is powered down. - -I read that -110 is supposedly a power issue. I can play media files directly from the thumb drive on the host, so the power seems fine on the host. - - -How reproducible: -always - - -Steps to reproduce: -1. use virt-manager, create a Windows 7 32 bit guest -2. in virt-manager, set Controller USB to USB2 -3. on host, insert Sandisk Cruser Fit thumb drive FAT32 format, with an MP3 file on it -4. in virt-manager, add a USB passthrough device and assign it to thumb drive -5. boot Windows 7 guest -6. verify that Windows 7 can see the thumb drive -7. use Windows Media Player to play MP3 - -Actual results: -guest hangs, then host powers off thumb drive - -Expected results: -The MP3 file should play :) - - -Additional info: - -Fedora 19 - -Installed Packages -qemu-common.x86_64 2:1.4.2-11.fc19 @updates -qemu-guest-agent.x86_64 2:1.4.2-11.fc19 @updates -qemu-img.x86_64 2:1.4.2-11.fc19 @updates -qemu-kvm.x86_64 2:1.4.2-11.fc19 @updates -qemu-system-x86.x86_64 2:1.4.2-11.fc19 @updates -virt-manager.noarch 0.10.0-3.fc19 @updates -kernel.x86_64 3.11.1-200.fc19 @updates \ No newline at end of file diff --git a/results/classifier/deepseek-2-tmp/output/device/1248469 b/results/classifier/deepseek-2-tmp/output/device/1248469 deleted file mode 100644 index 8a37a402..00000000 --- a/results/classifier/deepseek-2-tmp/output/device/1248469 +++ /dev/null @@ -1,4 +0,0 @@ - -qemu 1.6.1 q35 ioh3420 not work in windows 7 32bit - -boot windows 7 32bit guest with -readconfig q35-chipset.cfg paramter,in guest's device manager,there's a device 3420 not work,it shows error "This device cannot find enough free resources that it can use(code 12)". \ No newline at end of file diff --git a/results/classifier/deepseek-2-tmp/output/device/1250 b/results/classifier/deepseek-2-tmp/output/device/1250 deleted file mode 100644 index fe78e6c8..00000000 --- a/results/classifier/deepseek-2-tmp/output/device/1250 +++ /dev/null @@ -1,4 +0,0 @@ - -[RFE] on windows, attach any storport disk directly, not just physicaldrives -Additional information: - diff --git a/results/classifier/deepseek-2-tmp/output/device/1256122 b/results/classifier/deepseek-2-tmp/output/device/1256122 deleted file mode 100644 index 175f4434..00000000 --- a/results/classifier/deepseek-2-tmp/output/device/1256122 +++ /dev/null @@ -1,23 +0,0 @@ - -vfio bug with all no VGA card - -Hello, - -I whant to report to you a realy big bug. - -vfio passthrough work only with VGA card ! When i try to use vfio with any other PCI or PCI-E card it does not work. - -When i use vfio for VGA i can reboot (or shutdown and start again) my VM with out problem, but for any other PCI card the VM refuse to reboot. - -In dmesg i have this error : - -dmar: DRHD: handling fault status reg 2 -dmar: DMAR:[DMA Read] Request device [xx:xx.x] fault addr 2affde000 -DMAR:[fault reason 06] PTE Read access is not set - -and some time the same but for Write and not Read. - -I found a kind of work around but it's ugly. Just detach your devices from vfio, re-atach to his normal driver and bind again to vfio. - -For information i use an Asrock Z87 Extrem 6 with a CoreI5 4570S -My kernel is 3.12 and Qemu is 1.7-rc0 \ No newline at end of file diff --git a/results/classifier/deepseek-2-tmp/output/device/1257334 b/results/classifier/deepseek-2-tmp/output/device/1257334 deleted file mode 100644 index 463091c2..00000000 --- a/results/classifier/deepseek-2-tmp/output/device/1257334 +++ /dev/null @@ -1,4 +0,0 @@ - -diffuse handling of image creation from another path - -see attachement! \ No newline at end of file diff --git a/results/classifier/deepseek-2-tmp/output/device/1267520 b/results/classifier/deepseek-2-tmp/output/device/1267520 deleted file mode 100644 index 2ba4176a..00000000 --- a/results/classifier/deepseek-2-tmp/output/device/1267520 +++ /dev/null @@ -1,6 +0,0 @@ - -Keyboard input not working when the "-k en-us" argument is specified. - -This bug occurs on qemu compiled with i386_softmmu and x86-64_softmmu on linux kernel 3.5.0. -Whenever I run qemu (both i386 and x86_64) to use the en-us language (even though it is the default), I get "Warning: no scancode found for keysym X" (X is an integer). -In the disk image I need qemu to run, I had a shell set up. The shell doesn't register keyboard input when the '-k en-us' command line argument is set when running qemu. I did not have this problem with earlier versions of qemu. \ No newline at end of file diff --git a/results/classifier/deepseek-2-tmp/output/device/1268596 b/results/classifier/deepseek-2-tmp/output/device/1268596 deleted file mode 100644 index 65182294..00000000 --- a/results/classifier/deepseek-2-tmp/output/device/1268596 +++ /dev/null @@ -1,25 +0,0 @@ - -Compilation Error: hw/virtio/dataplane/vring.c:400:5: error: ‘ret’ may be used uninitialised in this function - -Qemu git-cloned from mo. 13.01.14 (ca. 13:00 GMT), Version 1.7.50 - - -#git clone git://git.qemu-project.org/qemu.git -# cd qemu; git submodule update --init dtc -#./configure --disable-xen --enable-kvm -...No Errors... - -#CC="ccache gcc" make -j8 -.... - GEN qemu.1 - Signing optionrom/kvmvapic.bin - GEN qemu-img.1 - CC qapi-types.o -hw/virtio/dataplane/vring.c: In function ‘vring_pop’: -hw/virtio/dataplane/vring.c:400:5: error: ‘ret’ may be used uninitialised in this function [-Werror=uninitialized] -cc1: all warnings being treated as errors -make: *** [hw/virtio/dataplane/vring.o] Error 1 -make: *** Waiting for unfinished jobs.... - - -Thx. \ No newline at end of file diff --git a/results/classifier/deepseek-2-tmp/output/device/1268671 b/results/classifier/deepseek-2-tmp/output/device/1268671 deleted file mode 100644 index 3d0ec29e..00000000 --- a/results/classifier/deepseek-2-tmp/output/device/1268671 +++ /dev/null @@ -1,45 +0,0 @@ - -CentOS guest crashing due to assertion failure in qemu-char.c - -Here is the log in /var/log/libvirt/qemu/centos_heavy.log - -qemu-kvm: /builddir/build/BUILD/qemu-kvm-0.12.1.2/qemu-char.c:630: io_watch_poll_finalize: Assertion `iwp->src == ((void *)0)' failed. -2014-01-13 16:50:31.576+0000: shutting down - -The code it's failing the assertion on has an interesting comment: - - static void io_watch_poll_finalize(GSource *source) - { - /* Due to a glib bug, removing the last reference to a source - * inside a finalize callback causes recursive locking (and a - * deadlock). This is not a problem inside other callbacks, - * including dispatch callbacks, so we call io_remove_watch_poll - * to remove this source. A t this point, iwp->src must - * be NULL, or we would leak it. - * - * This would be solved much more elegantly by child sources, - * but we support older glib versions that do not have them. - */ - IOWatchPoll *iwp = io_watch_poll_from_source(source); - assert(iwp->src == NULL); - } - ------- -CPU Info: - -http://pastebin.com/U7MrzFxK - --------- - -Relevant RPM versions: - -qemu-kvm-0.12.1.2-2.415.el6_5.3.x86_64 -libvirt-0.10.2-29.el6_5.2.x86_64 - --------- - -Domain config: - -http://pastebin.com/Nf2VsER8 - -(Note the use of the vmchannels; I believe this is playing a part in this crash) \ No newline at end of file diff --git a/results/classifier/deepseek-2-tmp/output/device/1269628 b/results/classifier/deepseek-2-tmp/output/device/1269628 deleted file mode 100644 index e7a6eb85..00000000 --- a/results/classifier/deepseek-2-tmp/output/device/1269628 +++ /dev/null @@ -1,6 +0,0 @@ - -Feature Request: Please add TCG OPAL 2 emulation support to the virtio disk emulation - -In order to allow windows guests (and soon, linux guests) which are TCG OPAL 2 aware to perform disk encryption in a native fashion with hardware acceleration, please add TCG OPAL 2 emulation to the VIRTIO driver. - -Encryption should occur at the host level using any cryptographic facilities available to the host, for example AES-NI, Cryptography Hardware, underlying block device cryptography support where available or any other cryptography facility that may be developed and implemented in the future. \ No newline at end of file diff --git a/results/classifier/deepseek-2-tmp/output/device/1276879 b/results/classifier/deepseek-2-tmp/output/device/1276879 deleted file mode 100644 index c8c1dbb9..00000000 --- a/results/classifier/deepseek-2-tmp/output/device/1276879 +++ /dev/null @@ -1,17 +0,0 @@ - -lots of dma command 10, 14 not supported - -Trying to install NeXTSTEP 3.3 onto a 2GB file with QEMU 1.7.0. -In the terminal that started QEMU, there are a lot of - dma: command 10 not supported -and - dma: command 14 not supported -messages. When the installation of NeXTSTEP gets to -'preparing disk for nextstep installation', there are a lot -of messages that ATA command c5 failed and other info. -The result is a failed installation. - -Is this a bug in QEMU? Is there a workaround, e.g. by -disabling DMA altogether? - -thank you \ No newline at end of file diff --git a/results/classifier/deepseek-2-tmp/output/device/1280521 b/results/classifier/deepseek-2-tmp/output/device/1280521 deleted file mode 100644 index dac9c108..00000000 --- a/results/classifier/deepseek-2-tmp/output/device/1280521 +++ /dev/null @@ -1,4 +0,0 @@ - -Plan 9 can't use GUI well emulating a RTL8139 card - -The OS Plan 9 from Bell Labs runs fine in QEMU/KVM for the most part buy is unable to boot its GUI when emulating a RTL8139 WiFi card. I hear someone was able to get it working under a Windows XP host but I can't seem to do it under a Gentoo host. If you have any idea what may be doing this I would love to hear it. \ No newline at end of file diff --git a/results/classifier/deepseek-2-tmp/output/device/1284874 b/results/classifier/deepseek-2-tmp/output/device/1284874 deleted file mode 100644 index 480cd0b6..00000000 --- a/results/classifier/deepseek-2-tmp/output/device/1284874 +++ /dev/null @@ -1,31 +0,0 @@ - -Guest hangs during option rom loading with certain cards - -With a Broadcom Corporation NetXtreme II BCM57810 10 Gigabit Ethernet card, device assignment does not work. The guest hangs during option rom execution. Moreover, if an attempt is made to quit qemu when the guest is in the hung state, the card gets into an inoperable state. Only a powercycle then, restores the card back into working order, just unloading/loading the driver does not help. - -Qemu version - 1.6.2 or current master -Distribution - FC19 -Kernel Version - 3.12.9-201.fc19.x86_64 - -Details of the card - - # ethtool -i p2p2 -driver: bnx2x -version: 1.78.17-0 -firmware-version: bc 7.8.22 -bus-info: 0000:08:00.1 -supports-statistics: yes -supports-test: yes -supports-eeprom-access: yes -supports-register-dump: yes -supports-priv-flags: yes - -The output of lspci when the card is broken - -03:00.0 Ethernet controller: Broadcom Corporation NetXtreme II BCM57810 10 Gigabit Ethernet (rev ff) (prog-if ff) - !!! Unknown header type 7f - Kernel driver in use: bnx2x -00: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff -10: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff -20: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff -30: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff - -I will post if I get a chance to try out a newer than 7.8.22 for the option rom and see if this issue is fixed. However it appears we need to have a unified approach to automatically avoid loading the rom based on certain criteria. Manually, looking out for fixes to firmware and hard coding decisions based on those is neither desirable nor easy to maintain. \ No newline at end of file diff --git a/results/classifier/deepseek-2-tmp/output/device/1288 b/results/classifier/deepseek-2-tmp/output/device/1288 deleted file mode 100644 index 37ac4c0d..00000000 --- a/results/classifier/deepseek-2-tmp/output/device/1288 +++ /dev/null @@ -1,10 +0,0 @@ - -GPU passing through guest crashes -Description of problem: -First and foremost, I don't know if this is a QEMU, KVM or GPU driver issue. -I began emailing libvirt project and they advised me to contact you, then KVM and then GPU driver developer(NVIDIA). -Host is crashing from time to time. I have guest's kernel dumps(~2GB each). -Steps to reproduce: -Unfortunately, I don't have steps to reproduce. -Additional information: -I'm aware I'm not running the latest qmeu version but I'm willing to install developer version and try to reproduce or test patch if developer requires it. diff --git a/results/classifier/deepseek-2-tmp/output/device/1292037 b/results/classifier/deepseek-2-tmp/output/device/1292037 deleted file mode 100644 index 8dca5543..00000000 --- a/results/classifier/deepseek-2-tmp/output/device/1292037 +++ /dev/null @@ -1,15 +0,0 @@ - -Solaris 10 x86 guest crashes qemu with -icount 1 option - -Commit: f53f3d0a00b6df39ce8dfca942608e5b6a9a4f71 on qemu.git - -Solaris image: Solaris 10 x86 (32 bit) - -command: ./i386-softmmu/qemu-system-i386 -hda -m 2G -icount 1 -monitor stdio - -Crashes saying: -qemu: Fatal: Raised interrupt while not in I/O function - -Host: -ubuntu x86_64 3.2.0-56 generic -intel xeon E5649 @ 2.53GHz \ No newline at end of file diff --git a/results/classifier/deepseek-2-tmp/output/device/1294 b/results/classifier/deepseek-2-tmp/output/device/1294 deleted file mode 100644 index 64ba4532..00000000 --- a/results/classifier/deepseek-2-tmp/output/device/1294 +++ /dev/null @@ -1,2 +0,0 @@ - -pflash size check appears to be incompatible with OVMF on x86 diff --git a/results/classifier/deepseek-2-tmp/output/device/1295587 b/results/classifier/deepseek-2-tmp/output/device/1295587 deleted file mode 100644 index 38d78147..00000000 --- a/results/classifier/deepseek-2-tmp/output/device/1295587 +++ /dev/null @@ -1,20 +0,0 @@ - -Temporal freeze and slowdown while using emulated sb16 - -I have been carrying around this bug since previous versions and on different machines: When I use the -soundhw sb16 option, while playing any sound on the virtual machine it freezes and loops the last bit of such sound effect for 1-2 minutes, then goes back to normal speed. - -Console shows: - - sb16: warning: command 0xf9,1 is not truly understood yet - sb16: warning: command 0xf9,1 is not truly understood yet -(...) -main-loop: WARNING: I/O thread spun for 1000 iterations - --One of my emulated machines is Windows 3.11: I managed to overrun this bug by switching from the local 1.5 version of the sound blaster driver to the 1.0, although since I updated qemu it freezes that machine, so I can't test if it still works. - -I am using the 1.7.90 version, but I suffered this bug for over one year - -this bug happens anytime I use the -soundhw sb16 switch, but the full command I am using in this specific case is: - - -qemu-system-i386 -localtime -cpu pentium -m 32 -display sdl -vga cirrus -hda c.img -cdrom win95stuff.iso -net nic,model=ne2k_pci -net user -soundhw sb16 \ No newline at end of file diff --git a/results/classifier/deepseek-2-tmp/output/device/1300 b/results/classifier/deepseek-2-tmp/output/device/1300 deleted file mode 100644 index 69ba1438..00000000 --- a/results/classifier/deepseek-2-tmp/output/device/1300 +++ /dev/null @@ -1,12 +0,0 @@ - -Build failure when configuring CONFIG_VHOST_USER_FS/CONFIG_VIRTIO -Description of problem: -Attempting to configure CONFIG_VHOST_USER_FS or CONFIG_VIRTIO results in a build failure. Complete build log (with configure output) is attached. -Steps to reproduce: -1. Add `CONFIG_VIRTIO` and `CONFIG_VHOST_USER_FS` (`y` *or* `n`) to `configs/devices/x86_64-softmmu/gentoo.mak` (done via the [ebuild](https://github.com/gentoo/gentoo/blob/master/app-emulation/qemu/qemu-7.1.0.ebuild)) -2. Configure with `--with-devices-x86_64=gentoo` -3. Attempt building -Additional information: -[build.log](/uploads/72fc1284f5245d9384e521d3b1c65953/build.log) - -Reported downstream [here](https://bugs.gentoo.org/873190). diff --git a/results/classifier/deepseek-2-tmp/output/device/1306818 b/results/classifier/deepseek-2-tmp/output/device/1306818 deleted file mode 100644 index d18ff66a..00000000 --- a/results/classifier/deepseek-2-tmp/output/device/1306818 +++ /dev/null @@ -1,44 +0,0 @@ - -resetting moder register in opencores_eth.c code (ethernet IP core specification code) - -Hi, I would like to report a possible error in the code qemu/hw/net/opencores_eth.c - -The corresponding data sheet : http://www.cprover.org/firmware/doc/ethoc/eth_speci.pdf - - -In the code, there is a function open_eth_moder_host_write. - -static void open_eth_moder_host_write(OpenEthState *s, uint32_t val) -{ - uint32_t set = val & ~s->regs[MODER]; - - if (set & MODER_RST) { - open_eth_reset(s); - } - - s->regs[MODER] = val; - - if (set & MODER_RXEN) { - s->rx_desc = s->regs[TX_BD_NUM]; - open_eth_notify_can_receive(s); - } - if (set & MODER_TXEN) { - s->tx_desc = 0; - open_eth_check_start_xmit(s); - } -} - -This piece of code is executed when MODER (Mode Register) resister is command to updated to ‘val’. - -In case of reset, as you can see, if the MODER_RST bit (0x800) bit is set && the old MODER_RST bit (0x800) of MODER register is clear, the code falls into the if(set & MODER_RST) branch. Then, it calls open_eth_reset(s), which does “s->regs[MODER] = 0xa000;”. Now, the MODER register is reset to 0xa000. Page 9 of the data sheet (http://www.cprover.org/firmware/doc/ethoc/eth_speci.pdf) specifies the reset value of the moder is 0000A000h. So far, the code works fine. -Then, the open_eth_moder_host_write function does not end but executes but executes “s->regs[MODER] = val;” line. Now, the MODER register is not 0xa000 any more. -In fact, since the MODER_RST bit of ‘val’ is 1, now the MODER_RST bit of the MODER register becomes 1 as well. Suppose one somehow calls this open_eth_moder_host_write again with val = MODER_RST with purpose of resetting again. Since the MODER_RST bit is 1, (set = val & ~s->regs[MODER]) & MODER_RST is zero. So after this, resetting again is not possible. - -Hence, I doubt the function’s correctness here. I think it could be better if the function changes to : - - if (set & MODER_RST) { - open_eth_reset(s); - return; - } - -Please let me know if I am correct. \ No newline at end of file diff --git a/results/classifier/deepseek-2-tmp/output/device/1307281 b/results/classifier/deepseek-2-tmp/output/device/1307281 deleted file mode 100644 index 2ba6a7d8..00000000 --- a/results/classifier/deepseek-2-tmp/output/device/1307281 +++ /dev/null @@ -1,11 +0,0 @@ - -qemu crash with assertion in usb_packet_complete_one - -qemu release verison: 1.7.1 -guest os : win7 32bits -qemu cmdline: -/usr/bin/qemu-system-x86_64 -name hch_test -S -machine pc-i440fx-1.7,accel=kvm,usb=off -cpu SandyBridge,+erms,+smep,+fsgsbase,+pdpe1gb,+rdrand,+f16c,+osxsave,+dca,+pcid,+pdcm,+xtpr,+tm2,+est,+smx,+vmx,+ds_cpl,+monitor,+dtes64,+pbe,+tm,+ht,+ss,+acpi,+ds,+vme -m 2048 -realtime mlock=off -smp 2,sockets=2,cores=12,threads=2 -uuid 5ad433c9-e490-42f3-b365-c30d756fbd70 -no-user-config -nodefaults -chardev socket,id=charmonitor,path=/var/lib/libvirt/qemu/hch_test.monitor,server,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=localtime -no-shutdown -global PIIX4_PM.disable_s3=1 -global PIIX4_PM.disable_s4=0 -device ich9-usb-ehci1,id=usb,bus=pci.0,addr=0x5.0x7 -device ich9-usb-uhci1,masterbus=usb.0,firstport=0,bus=pci.0,multifunction=on,addr=0x5 -device virtio-serial-pci,id=virtio-serial0,bus=pci.0,addr=0x6 -drive file=/opt/cvm/hch_test/hch_test.inst,if=none,id=drive-virtio-disk0,format=qcow2,cache=writeback -device virtio-blk-pci,scsi=off,bus=pci.0,addr=0x7,drive=drive-virtio-disk0,id=virtio-disk0,bootindex=1 -drive file=/opt/data/hugedisk/hch_test/hch_test_share.add,if=none,id=drive-virtio-disk1,format=qcow2,cache=writeback -device virtio-blk-pci,scsi=off,bus=pci.0,addr=0x8,drive=drive-virtio-disk1,id=virtio-disk1 -netdev tap,fd=26,id=hostnet0,vhost=on,vhostfd=27 -device virtio-net-pci,netdev=hostnet0,id=net0,mac=52:54:00:f2:05:b7,bus=pci.0,addr=0x3 -chardev pty,id=charserial0 -device isa-serial,chardev=charserial0,id=serial0 -chardev spicevmc,id=charchannel0,name=vdagent -device virtserialport,bus=virtio-serial0.0,nr=1,chardev=charchannel0,id=channel0,name=com.redhat.spice.0 -chardev socket,id=charchannel1,path=/var/lib/libvirt/qemu/hch_test.agent,server,nowait -device virtserialport,bus=virtio-serial0.0,nr=2,chardev=charchannel1,id=channel1,name=org.qemu.guest_agent.0 -device usb-tablet,id=input0 -spice port=5903,addr=0.0.0.0,disable-ticketing,seamless-migration=on -device qxl-vga,id=video0,ram_size=67108864,vram_size=67108864,bus=pci.0,addr=0x2 -device intel-hda,id=sound0,bus=pci.0,addr=0x4 -device hda-duplex,id=sound0-codec0,bus=sound0.0,cad=0 -readconfig /etc/qemu/ich9-ehci-uhci.cfg -chardev spicevmc,name=usbredir,id=usbredirchardev1 -device usb-redir,chardev=usbredirchardev1,id=usbredirdev1,bus=ehci.0 -chardev spicevmc,name=usbredir,id=usbredirchardev2 -device usb-redir,chardev=usbredirchardev2,id=usbredirdev2,bus=ehci.0 -chardev spicevmc,name=usbredir,id=usbredirchardev3 -device usb-redir,chardev=usbredirchardev3,id=usbredirdev3,bus=ehci.0 - -i use spice to connect to vm and utilize usb redirection. i plug a u-disk into a remote computer and start copy a big file (3G+) to u-disk and qemu was crashed in the middle of the transmission. - -i check the qemu log and found this log: "qemu-system-x86_64: hw/usb/core.c:438: usb_packet_complete_one: Assertion `p->stream || ((&ep->queue)->tqh_first) == p' failed". this crash can be reproduced every time. \ No newline at end of file diff --git a/results/classifier/deepseek-2-tmp/output/device/1311 b/results/classifier/deepseek-2-tmp/output/device/1311 deleted file mode 100644 index eacffe78..00000000 --- a/results/classifier/deepseek-2-tmp/output/device/1311 +++ /dev/null @@ -1,2 +0,0 @@ - -riscv-qemu can't record interrupt diff --git a/results/classifier/deepseek-2-tmp/output/device/1314857 b/results/classifier/deepseek-2-tmp/output/device/1314857 deleted file mode 100644 index bc359352..00000000 --- a/results/classifier/deepseek-2-tmp/output/device/1314857 +++ /dev/null @@ -1,20 +0,0 @@ - -seg fault in ivshmem when using ioeventfd=on - -When launching qemu with the ivshmem device and the nahanni guest server there is segmentation fault in the setup_ioeventfds function of ivshmem.c. If the ioeventfd=on flag is set the pci_ivshmem_init will call setup_ioeventfds at line 668. This function relies on the 'peers' member of the server info which is not allocated until line 669. - -To reproduce you will need the nahanni guest server code. The driver code is not needed. You will also need a qcow2 or other bootable image to use for launching qemu. The error occurs before the actual image launch. - -Start the nahanni ivshmem server with a small global memory space ( although the bug is not allocation specific ) -ivshmem -m 1 -n 2 -p /tmp/ivshmem_socket - -Next launch qemu with initialization for the ivshmem device. -qemu-system-x86_64 -hda test_iso.qcow2 -localtime -boot c -chardev socket,path="/tmp/ivshmem_socket",id=ivshmem_socket -device ivshmem,chardev=ivshmem_socket,size=1,ioeventfd=on - -If gdb is used the following error is recorded: -Program received signal SIGSEGV, Segmentation fault. -0x000055555579dd52 in setup_ioeventfds (s=0x555556619580) - at /home/genes/work/ubuntu/qemu-kvm-1.0+noroms/hw/ivshmem.c:367 -367 for (j = 0; j < s->peers[i].nb_eventfds; j++) { -(gdb) print s->peers -$2 = (Peer *) 0x0 \ No newline at end of file diff --git a/results/classifier/deepseek-2-tmp/output/device/1318 b/results/classifier/deepseek-2-tmp/output/device/1318 deleted file mode 100644 index 7581c440..00000000 --- a/results/classifier/deepseek-2-tmp/output/device/1318 +++ /dev/null @@ -1,20 +0,0 @@ - -vsock device fails with "qemu-system-x86_64: vhost_set_features failed: Operation not supported (95)" when queue_reset=true -Description of problem: -Immediately after guest vsock driver initialize, qemu prints error messages. I'm not able to connect to the guest with vsock: - -``` -[ 0.654463] Run /init as init process -[ 0.679778] NET: Registered PF_VSOCK protocol family -qemu-system-x86_64: vhost_set_features failed: Operation not supported (95) -qemu-system-x86_64: Error starting vhost: 95 -ssh-keygen: generating new host keys: RSA DSA ECDSA ED25519 -# -``` -Steps to reproduce: -1. Clone `git://passt.top/passt` -2. In `passt/test`, run `make mbuto.img` -3. Run `qemu-system-x86_64 -enable-kvm -m 2048 -kernel KERNEL -initrd mbuto.img -nographic -serial stdio -nodefaults -append "console=ttyS0" -device vhost-vsock-pci,guest-cid=31415,queue_reset=true` replacing KERNEL with the host kernel image. -Additional information: -- Problem goes away if `queue_reset=false`, which means it goes away with default options prior to `69e1c14aa222` ("virtio: core: vq reset feature negotation support") -- Occurs both with and without KVM diff --git a/results/classifier/deepseek-2-tmp/output/device/1320360 b/results/classifier/deepseek-2-tmp/output/device/1320360 deleted file mode 100644 index 9db58e31..00000000 --- a/results/classifier/deepseek-2-tmp/output/device/1320360 +++ /dev/null @@ -1,18 +0,0 @@ - -usb passthrough not working anymore - -Hi, - -I'm using qemu 2.0.0 with opensuse 13.1 x84_64 bit as host and window7 as guest. Til qemu version 1.6.2 USB passthrough works perfectly, but starting with qemu 2.0.0 passthrough stop working. I can still add the usb device but when I start the guest following message appears: - -"unable to execute QEMU command 'device_add': 'usb-host' is not a valid device model name" - -Then the guest will not start. - -I try it with different usb devices (iphone, stick, hdd), always the same error. - -Are there any news / hints about this ? - -Regards - -Martin \ No newline at end of file diff --git a/results/classifier/deepseek-2-tmp/output/device/1321684 b/results/classifier/deepseek-2-tmp/output/device/1321684 deleted file mode 100644 index 2d8ecb84..00000000 --- a/results/classifier/deepseek-2-tmp/output/device/1321684 +++ /dev/null @@ -1,47 +0,0 @@ - -block_stream command stalls - -block_stream command stalls near finishing. -I tried 1.7.1, 2.0.0 and the master versions. All of them stalled. -But the 1.1.2 could finish the job. - -Here is how to reproduce it: - -$ sudo $QEMU \ --enable-kvm -cpu qemu64 -m 1024 \ --monitor stdio \ --drive file=./i1,if=none,id=drive_0,cache=none,aio=native -device virtio-blk-pci,drive=drive_0,bus=pci.0,addr=0x5 \ - -QEMU 2.0.50 monitor - type 'help' for more information -(qemu) VNC server running on `127.0.0.1:5900' -(qemu) snapshot_blkdev drive_0 s1 -Formatting 's1', fmt=qcow2 size=26843545600 backing_file='./i1' backing_fmt='qcow2' encryption=off cluster_size=65536 lazy_refcounts=off -(qemu) block_stream drive_0 -(qemu) info block-jobs -Streaming device drive_0: Completed 400818176 of 26843545600 bytes, speed limit 0 bytes/s -(qemu) info block-jobs -Streaming device drive_0: Completed 904396800 of 26843545600 bytes, speed limit 0 bytes/s -(qemu) info block-jobs -Streaming device drive_0: Completed 23401070592 of 26843545600 bytes, speed limit 0 bytes/s -(qemu) info block-jobs -Streaming device drive_0: Completed 26513768448 of 26843545600 bytes, speed limit 0 bytes/s -(qemu) main-loop: WARNING: I/O thread spun for 1000 iterations -info block-jobs -Streaming device drive_0: Completed 26841513984 of 26843545600 bytes, speed limit 0 bytes/s -(qemu) info block-jobs -Streaming device drive_0: Completed 26841513984 of 26843545600 bytes, speed limit 0 bytes/s -(qemu) info block-jobs -Streaming device drive_0: Completed 26841513984 of 26843545600 bytes, speed limit 0 bytes/s - -#### here, the progress stopped at 26841513984 #### - - -$ qemu-img info i1 -image: i1 -file format: qcow2 -virtual size: 25G (26843545600 bytes) -disk size: 1.0G -cluster_size: 2097152 -Format specific information: - compat: 1.1 - lazy refcounts: false \ No newline at end of file diff --git a/results/classifier/deepseek-2-tmp/output/device/133 b/results/classifier/deepseek-2-tmp/output/device/133 deleted file mode 100644 index e2b3e6e9..00000000 --- a/results/classifier/deepseek-2-tmp/output/device/133 +++ /dev/null @@ -1,2 +0,0 @@ - -Chardev websocket might not support pasting more than a few chars diff --git a/results/classifier/deepseek-2-tmp/output/device/1333216 b/results/classifier/deepseek-2-tmp/output/device/1333216 deleted file mode 100644 index 50206197..00000000 --- a/results/classifier/deepseek-2-tmp/output/device/1333216 +++ /dev/null @@ -1,37 +0,0 @@ - -Xen 4.4 with qemu 1.6.2 VGA passthru NVIDIA - -Hi! - -Please, give me an advice. - -I try use VGA passthough NVidia k40 on SuperMicro Server, but server is having error. -My Xen is using qemu (a9e8aeb3755bccb7b51174adcf4a3fc427e0d147)2.0.0 - -My VirtualMachine is have config: -device_model_version = "qemu-xen" -device_model_override = "/opt/sources/qemu-a9e8aeb/x86_64-softmmu/qemu-system-x86_64" - -When I start VM: -dmesg -[ 0.906181] pci 0000:00:05.0: BAR 1: can't assign mem pref (size 0x100000000) -[ 0.906187] pci 0000:00:05.0: BAR 1: trying firmware assignment [mem 0x100000000-0x1ffffffff 64bit pref] -[ 0.906193] pci 0000:00:05.0: BAR 1: assigned [mem 0x100000000-0x1ffffffff 64bit pref] -and lspci -s 00:05.0 -vvv - Region 0: Memory at 85000000 (32-bit, non-prefetchable) [size=16M] - Region 1: Memory at 100000000 (64-bit, prefetchable) [size=4G] - Region 3: Memory at 82000000 (64-bit, prefetchable) [size=32M] - -Why? - -This is message in DOM0: -lspci -s 03:00.0 -vvv -.... -Region 0: Memory at de000000 (32-bit, non-prefetchable) [size=16M] -Region 1: Memory at 5800000000 (64-bit, prefetchable) [size=16G] -Region 3: Memory at 5c00000000 (64-bit, prefetchable) [size=32M] - - -Why Qemu don`t mapping BAR1? -Thanks! -Regards! \ No newline at end of file diff --git a/results/classifier/deepseek-2-tmp/output/device/1334397 b/results/classifier/deepseek-2-tmp/output/device/1334397 deleted file mode 100644 index 349d8fa1..00000000 --- a/results/classifier/deepseek-2-tmp/output/device/1334397 +++ /dev/null @@ -1,9 +0,0 @@ - -cmos RTC alarms no longer wake system from suspend - -Running QEMU emulator version 2.0.0 (Debian 2.0.0+dfsg-2ubuntu1.1), booting Linux kernels with qemu-system-x86_64 and qemu-system-i386, I no longer see the system resume from suspend when an RTC alarm is set. - -My simple test application can be found here: -https://github.com/johnstultz-work/timetests/blob/master/alarmtimer-suspend.c - -Previously this worked w/ QEMU 1.5 (bascially up until I upgraded from Ubuntu 13.10 to Ubuntu 14.04, which came with 2.0). \ No newline at end of file diff --git a/results/classifier/deepseek-2-tmp/output/device/1336123 b/results/classifier/deepseek-2-tmp/output/device/1336123 deleted file mode 100644 index 86bbfff7..00000000 --- a/results/classifier/deepseek-2-tmp/output/device/1336123 +++ /dev/null @@ -1,12 +0,0 @@ - -bad switch, segfault in hw/pci-host/bonito.c bonito_readl - -http://git.qemu.org/?p=qemu.git;a=blob;f=hw/pci-host/bonito.c;h=56292adb03cd1a9873c2c9e5a0b2978fd0572214;hb=master#l301 - -The switch statement is error-prone, since two branches return the same result. - -Segfault reproducing steps: -1. make a Linux kernel(for example 3.16.0-rc2) with fuloong2e_defconfig -2. use 'qemu-system-mips64el -machine fulong2e' to boot the vmlinux - -qemu versions tried: 2.0.0, 1.6.2 \ No newline at end of file diff --git a/results/classifier/deepseek-2-tmp/output/device/1338957 b/results/classifier/deepseek-2-tmp/output/device/1338957 deleted file mode 100644 index e7eff4ef..00000000 --- a/results/classifier/deepseek-2-tmp/output/device/1338957 +++ /dev/null @@ -1,12 +0,0 @@ - -RFE: add an event to report block devices watermark - -Add an event to report if a block device usage exceeds a threshold. The threshold should be configurable with a monitor command. The event should report the affected block device. Additional useful information could be the offset of the highest sector , like in the query-blockstats output. - -Rationale for the RFE -Managing applications, like oVirt (http://www.ovirt.org), make extensive use of thin-provisioned disk images. -In order to let the guest run flawlessly and be not unnecessarily paused, oVirt sets a watermark and automatically resized the image once the watermark is reached or exceeded. - -In order to detect the mark crossing, the managing application has no choice than aggressively polling the QEMU monitor -using the query-blockstats command. This lead to unnecessary system load, and is made even worse under scale: scenarios -with hunderds of VM are becoming not unusual. \ No newline at end of file diff --git a/results/classifier/deepseek-2-tmp/output/device/1342 b/results/classifier/deepseek-2-tmp/output/device/1342 deleted file mode 100644 index 7af9e044..00000000 --- a/results/classifier/deepseek-2-tmp/output/device/1342 +++ /dev/null @@ -1,25 +0,0 @@ - -Default machine setting of force-legacy=true causes problems for any modern VirtIO device using MMIO -Description of problem: -The default causes problems if you enable any non-legacy VirtIO device which has the VIRTIO_F_VERSION_1 feature bit will not properly read all feature bits. This is because reading VIRTIO_MMIO_VERSION returns VIRT_VERSION_LEGACY which in turn results in the driver not reading all feature bits, e.g. the qtest access: - -``` -static uint64_t qvirtio_mmio_get_features(QVirtioDevice *d) -{ - QVirtioMMIODevice *dev = container_of(d, QVirtioMMIODevice, vdev); - uint64_t lo; - uint64_t hi = 0; - - qtest_writel(dev->qts, dev->addr + QVIRTIO_MMIO_HOST_FEATURES_SEL, 0); - lo = qtest_readl(dev->qts, dev->addr + QVIRTIO_MMIO_HOST_FEATURES); - - if (dev->version >= 2) { - qtest_writel(dev->qts, dev->addr + QVIRTIO_MMIO_HOST_FEATURES_SEL, 1); - hi = qtest_readl(dev->qts, dev->addr + QVIRTIO_MMIO_HOST_FEATURES); - } - - return (hi << 32) | lo; -} -``` -Additional information: - diff --git a/results/classifier/deepseek-2-tmp/output/device/1352179 b/results/classifier/deepseek-2-tmp/output/device/1352179 deleted file mode 100644 index 71163466..00000000 --- a/results/classifier/deepseek-2-tmp/output/device/1352179 +++ /dev/null @@ -1,29 +0,0 @@ - -could not open disk image - -After restart the server it's show this error: - -Error starting domain: internal error process exited while connecting to monitor: char device redirected to /dev/pts/1 -qemu-kvm: -drive file=/var/lib/nova/instances/b4535ce9-54b5-4581-a906-16b83bf1ba2f/disk,if=none,id=drive-virtio-disk0,format=qcow2,cache=none: could not open disk image /var/lib/nova/instances/b4535ce9-54b5-4581-a906-16b83bf1ba2f/disk: No such file or directory - -the disk info show - qemu-img info disk -image: disk -file format: qcow2 -virtual size: 100G (107374182400 bytes) -disk size: 22G -cluster_size: 65536 -backing file: /var/lib/nova/instances/_base/b4535ce9-54b5-4581-a906-16b83bf1ba2f - -but this file (backing file : /var/lib/nova/instances/_base/b4535ce9-54b5-4581-a906-16b83bf1ba2f) is empty. -And all the instances cant't find the disk image - -We use CentOS release 6.5 (64bit) -kernel version : 2.6.32-431.11.2.el6.x86_64 -qemu-kvm-0.12.1.2-2.415.el6_5.10.x86_64 - -virsh version -Compiled against library: libvirt 0.10.2 -Using library: libvirt 0.10.2 -Using API: QEMU 0.10.2 -Running hypervisor: QEMU 0.12.1 \ No newline at end of file diff --git a/results/classifier/deepseek-2-tmp/output/device/1352465 b/results/classifier/deepseek-2-tmp/output/device/1352465 deleted file mode 100644 index b746158f..00000000 --- a/results/classifier/deepseek-2-tmp/output/device/1352465 +++ /dev/null @@ -1,8 +0,0 @@ - -Can't install virtio block drivers during Windows setup - -Hi! -Apparently there's no way to install the virtio block drivers during Windows setup, as they're simply not recognized by the installer when it looks for them on the CD drive. -The only way to setup virtio block drivers is to first install Windows on a IDE drive, then add a dummy virtio disk, then load the drivers and swap the two disks. -I'm using virtio-win-0.1-81.iso. I can confirm the issue with Windows Server 2012 R2 and Windows 7 Professional, 64 bit. -Thanks! \ No newline at end of file diff --git a/results/classifier/deepseek-2-tmp/output/device/1353456 b/results/classifier/deepseek-2-tmp/output/device/1353456 deleted file mode 100644 index 71edaee3..00000000 --- a/results/classifier/deepseek-2-tmp/output/device/1353456 +++ /dev/null @@ -1,18 +0,0 @@ - -qemu-io: Failure on a qcow2 image with the fuzzed refcount table - -'qemu-io -c write' and 'qemu-io -c aio_write' crashes on a qcow2 image with a fuzzed refcount table. - -Sequence: - 1. Unpack the attached archive, make a copy of test.img - 2. Put copy.img and backing_img.file in the same directory - 3. Execute - qemu-io copy.img -c write 279552 322560 - or - qemu-io copy.img -c aio_write 836608 166400 - -Result: qemu-io was killed by SIGIOT with the reason: - -qemu-io: block/qcow2-cluster.c:1291: qcow2_alloc_cluster_offset: Assertion `*host_offset != 0' failed. - -qemu.git HEAD 69f87f713069f1f \ No newline at end of file diff --git a/results/classifier/deepseek-2-tmp/output/device/1354 b/results/classifier/deepseek-2-tmp/output/device/1354 deleted file mode 100644 index d812fdaf..00000000 --- a/results/classifier/deepseek-2-tmp/output/device/1354 +++ /dev/null @@ -1,2 +0,0 @@ - --device usb-tablet not working on android guest. diff --git a/results/classifier/deepseek-2-tmp/output/device/1354279 b/results/classifier/deepseek-2-tmp/output/device/1354279 deleted file mode 100644 index 10fb8631..00000000 --- a/results/classifier/deepseek-2-tmp/output/device/1354279 +++ /dev/null @@ -1,53 +0,0 @@ - -The guest will be destroyed after hot remove the VF from the guest. - -Environment: ------------- -Host OS (ia32/ia32e/IA64):ia32e -Guest OS (ia32/ia32e/IA64):ia32e -Guest OS Type (Linux/Windows):Linux -kvm.git Commit:9f6226a762c7ae02f6a23a3d4fc552dafa57ea23 -qemu.git Commit:5a7348045091a2bc15d85bb177e5956aa6114e5a -Host Kernel Version:3.16.0-rc1 -Hardware:Romley_EP, Ivytown_EP,Haswell_EP - - -Bug detailed description: --------------------------- -hot add the VF to the guest, then hot remove the VF from the guest, the guest will be destroyed. - -note: -1. when hot add the VF with vfio, the hot remove the VF from the guest, the guest works fine. -2. this shoule be a qemu bug: -kvm + qemu = result -9f6226a7 + 5a734804 = bad -9f6226a7 + 9f862687 = good - - - -Reproduce steps: ----------------- -1. create guest -qemu-system-x86_64 --enable-kvm -m 1024 -smp 4 -net none rhel6u5.qcow -monitor pty -2. hot add the vf to guest -echo "device_add pci-assign,host=05:10.0,id=nic" >/dev/pts/x -cat /dev/pts/x -3. hot remove the VF froem guest -echo "device_del nic" >/dev/pts/x - -Current result: ----------------- -the guest willl be destroyed after hot remove the VF from the guest - -Expected result: ----------------- -the guest works fine after hot remove the VF from the guest - - -Basic root-causing log: ----------------------- -[root@vt-snb9 qemu.git]# qemu-system-x86_64 -enable-kvm -m 1024 -smp 2 -net none rhel6u5.qcow -monitor pty -VNC server running on `::1:5900' -** -ERROR:qom/object.c:725:object_unref: assertion failed: (obj->ref > 0) -Aborted (core dumped) \ No newline at end of file diff --git a/results/classifier/deepseek-2-tmp/output/device/1356 b/results/classifier/deepseek-2-tmp/output/device/1356 deleted file mode 100644 index dae7eacb..00000000 --- a/results/classifier/deepseek-2-tmp/output/device/1356 +++ /dev/null @@ -1,18 +0,0 @@ - -"-set device" doesn't work with device specified in json -Description of problem: -The above QEMU command line results in: -``` -qemu-system-x86_64: -set device.ua-igd.x-igd-gms=1: there is no device "ua-igd" defined -``` -While the following command works: -``` -qemu-system-x86_64 -accel kvm -m 8192 -nodefaults -display none -net none -device vfio-pci,host=0000:00:02.0,id=ua-igd -set device.ua-igd.x-igd-gms=1 -``` -libvirt has moved to the json device specification, therefore I can no longer associate use a section to set driver options for a specific device with this broken id association. -Steps to reproduce: -1. Create a device with an ID and use -set device.$ID to set a driver option for the device -2. Note failure when using json device format vs legacy device specification -3. Profit -Additional information: - diff --git a/results/classifier/deepseek-2-tmp/output/device/1366 b/results/classifier/deepseek-2-tmp/output/device/1366 deleted file mode 100644 index 322ee709..00000000 --- a/results/classifier/deepseek-2-tmp/output/device/1366 +++ /dev/null @@ -1,85 +0,0 @@ - -Data inconsistency on LVM logical volume mounted as partition on ubuntu guest, when the written file's size is equal or greater than 27G. -Description of problem: -On the guest, writing a 27Gib file or larger result in inconsistent file checksum upon subsequent read. -Steps to reproduce: -**On the host** - -0. Create a LVM logical volume on a Linux RAID 1 (with 1 disk only) - -``` - --- Logical volume --- - LV Path /dev/davidahw2-vg4/lv0 - LV Name lv0 - VG Name davidahw2-vg4 - LV UUID 5FbDcl-eSDe-7cXL-22tj-Lg6O-79AL-4Gq7gx - LV Write Access read/write - LV Creation host, time davida-hw2, 2021-12-06 16:45:00 +0800 - LV Status available - # open 1 - LV Size <7.28 TiB - Current LE 1907688 - Segments 1 - Allocation inherit - Read ahead sectors auto - - currently set to 256 - Block device 253:4 - - --- Segments --- - Logical extents 0 to 1907687: - Type linear - Physical volume /dev/md4 - Physical extents 0 to 1907687 -``` - -1. Format the logical volume as ext4 - -``` -mkfs -t ext4 /dev/davidahw2-vg4/lv0 -``` - -2. Create a libvirt x86 64bits Ubuntu 22.04 machine mounting a LVM logical volume - -``` - - - - - - - - -
- -``` - - -**On the guest** - -3. Mount libvirt/qemu provided block device /dev/sdd as ext4 partition - -``` -mount /dev/sdd /mnt/test -``` - -4. Write **27G file** or larger **on the guest** causing the **2nd checksum to be different** - -``` -sync; head -c 27G myfile; sha256sum myfile; sha256sum myfile -8d3b4b263961d2c510390f99879be89b4b9134dc588139ede75573be1590115b myfile -a8e886b3c39d9b4721e582c5e2ca25c76ff6561750ac6dc7aa7e70404661d1cf myfile <== ERROR: Inconsistent checksum -``` - -5. Write **26G file** or larger **on the guest** and **both checksum are the same** - -``` -sync; head -c 26G myfile; sha256sum myfile; sha256sum myfile -598ac5da9b5bfa14d0ee664ae2590e09da772cba64cbc83ec049a656223c9401 myfile -598ac5da9b5bfa14d0ee664ae2590e09da772cba64cbc83ec049a656223c9401 myfile <== CORRECT: Consistent checksum -``` - -**Important**: -- With the VM shutdown, the same commands on the same mounted ext4 partition **on the host** has consistent checksum every time for file sizes from 20G to 40G. -- The disk has no sign of failure (no badblocks reported to the filesystem, MD raid reports a healthy raid setup, smart reports on error) -Additional information: - diff --git a/results/classifier/deepseek-2-tmp/output/device/1367365 b/results/classifier/deepseek-2-tmp/output/device/1367365 deleted file mode 100644 index 22b30a8b..00000000 --- a/results/classifier/deepseek-2-tmp/output/device/1367365 +++ /dev/null @@ -1,10 +0,0 @@ - -qemu-img fixed vhd issues - -qemu-img returns fixed vhd images file format to be raw. - -This happens because only the header is seeked for image signatures when getting the image format. In fact, unlike dynamic vhd images, differencing vhds don't have the footer copied in the header. - -An easy fix would be to just search the last 512B for the 'conectix' signature. - -Also, the fixed vhds created by qemu-img seem to be corrupted from Powershell POV. \ No newline at end of file diff --git a/results/classifier/deepseek-2-tmp/output/device/1368178 b/results/classifier/deepseek-2-tmp/output/device/1368178 deleted file mode 100644 index 278cfc5a..00000000 --- a/results/classifier/deepseek-2-tmp/output/device/1368178 +++ /dev/null @@ -1,26 +0,0 @@ - -Windows ME falsely detects qemu's videocards as Number Nine Imagine 128 - -A fresh installation of Windows Millennium Edition (Windows ME, WinME) as guest OS on qemu interprets qemu's videocards as Number Nine Imagine 128 with the consequence, that - -1. It is impossible to change color depth. -2. WinME uses the i128.drv Driver that is shipped with WinMe. -3. Forcing WinME to use other drivers has no effect. - - -It also doesn't matter what option for -vga was given to QEMU at command line. -cirrus, std, vmware, qxl etc. all have no effect, the videocard detected by Windows Me stays at Number Nine Imagine 128. - -Even selecting another driver in WinME and forcing WinME to use drivers such as the Cirrus Logic 5446 PCI driver has no effect. - -I also want to mention, that the BIOS isn't detected by WinME properly. -The device manager of WinME shows errors with the Plug & Play BIOS driver BIOS.vxd. - - -That is the QEMU Version: - -# qemu-system-i386 --version -QEMU emulator version 2.0.0 (Debian 2.0.0+dfsg-2ubuntu1.3), Copyright (c) 2003-2008 Fabrice Bellard - -And this was the complete command line, that was given: -# sudo /usr/bin/qemu-system-i386 -hda WinME_QEMU.img -cdrom drivers.iso -boot c -no-acpi -no-hpet -soundhw sb16 -net nic -cpu pentium3 -m 256 -vga cirrus \ No newline at end of file diff --git a/results/classifier/deepseek-2-tmp/output/device/1368204 b/results/classifier/deepseek-2-tmp/output/device/1368204 deleted file mode 100644 index ff183e09..00000000 --- a/results/classifier/deepseek-2-tmp/output/device/1368204 +++ /dev/null @@ -1,16 +0,0 @@ - -WinME isn't able to detect QEMU's cdrom drive and other hard drives automatically - -On a fresh installation of Windows Millennium (WinME) in qemu, Windows Me isn't able to find the CD-ROM drive or additional hard drives other than -hda at first place. - -Only if i add manually an IDE controller driver in Windows ME's device manager, the CD-ROM inserted in QEMU is found. -Thus an IDE controller isn't found automatically either. - -This shouldn't be the case. On normal real hardware, Windows ME would find at least one IDE or SCSI controller. - -The command line that was used is the following: -sudo /usr/bin/qemu-system-i386 -hda WinME_QEMU.img -cdrom drivers.iso -boot c -no-acpi -no-hpet -soundhw sb16 -net nic -cpu pentium3 -m 256 -vga cirrus - -qemu's version is: -qemu-system-i386 --version -QEMU emulator version 2.0.0 (Debian 2.0.0+dfsg-2ubuntu1.3), Copyright (c) 2003-2008 Fabrice Bellard \ No newline at end of file diff --git a/results/classifier/deepseek-2-tmp/output/device/1373362 b/results/classifier/deepseek-2-tmp/output/device/1373362 deleted file mode 100644 index 38a3991b..00000000 --- a/results/classifier/deepseek-2-tmp/output/device/1373362 +++ /dev/null @@ -1,28 +0,0 @@ - -qemu-2.1.1 i386-softmmu compile error: q35_dsdt_applesmc_sta undeclared - -I try to compile qemu-2.1.1 (Gentoo/x86), but the i386-softmmu fails to compile: - - CPP i386-softmmu/q35-acpi-dsdt.dsl.i.orig - ACPI_PREPROCESS i386-softmmu/q35-acpi-dsdt.dsl.i - IASL i386-softmmu/q35-acpi-dsdt.dsl.i - ACPI_EXTRACT i386-softmmu/q35-acpi-dsdt.off - CAT i386-softmmu/hw/i386/q35-acpi-dsdt.hex - CC i386-softmmu/hw/i386/acpi-build.o -/tmp/portage/app-emulation/qemu-2.1.1/work/qemu-2.1.1/hw/i386/acpi-build.c: In function 'acpi_get_dsdt': -/tmp/portage/app-emulation/qemu-2.1.1/work/qemu-2.1.1/hw/i386/acpi-build.c:119:24: error: 'q35_dsdt_applesmc_sta' undeclared (first use in this function) - applesmc_sta = q35_dsdt_applesmc_sta; - ^ -/tmp/portage/app-emulation/qemu-2.1.1/work/qemu-2.1.1/hw/i386/acpi-build.c:119:24: note: each undeclared identifier is reported only once for each function it appears in -make[1]: *** [hw/i386/acpi-build.o] Error 1 -make: *** [subdir-i386-softmmu] Error 2 - -Something seems to go wrong when generating the file i386-softmmu/hw/i386/q35-acpi-dsdt.hex: - -# grep -r q35_dsdt_applesmc_sta ../ -../softmmu-build/x86_64-softmmu/q35-acpi-dsdt.dsl.i:/* ACPI_EXTRACT_NAME_BYTE_CONST q35_dsdt_applesmc_sta */ -../softmmu-build/x86_64-softmmu/q35-acpi-dsdt.dsl.i.orig: ACPI_EXTRACT_NAME_BYTE_CONST q35_dsdt_applesmc_sta -../softmmu-build/i386-softmmu/q35-acpi-dsdt.dsl.i:/* ACPI_EXTRACT_NAME_BYTE_CONST q35_dsdt_applesmc_sta */ -../softmmu-build/i386-softmmu/q35-acpi-dsdt.dsl.i.orig: ACPI_EXTRACT_NAME_BYTE_CONST q35_dsdt_applesmc_sta -../hw/i386/acpi-build.c: applesmc_sta = q35_dsdt_applesmc_sta; -../hw/i386/q35-acpi-dsdt.dsl:#define DSDT_APPLESMC_STA q35_dsdt_applesmc_sta \ No newline at end of file diff --git a/results/classifier/deepseek-2-tmp/output/device/1378407 b/results/classifier/deepseek-2-tmp/output/device/1378407 deleted file mode 100644 index c6acf687..00000000 --- a/results/classifier/deepseek-2-tmp/output/device/1378407 +++ /dev/null @@ -1,6 +0,0 @@ - -[feature request] Partition table wrapper for single-filesystem images - -Suppose you have a single filesystem image. It would be nice if QEMU could generate a virtual partition table for it and make it available to the guest as a partitioned disk. Otherwise you have to use workarounds like this: wiki.archlinux.org/index.php/QEMU#Simulate_virtual_disk_with_MBR_using_linear_RAID - -It should be relatively easy to do on top of existing vvfat code. \ No newline at end of file diff --git a/results/classifier/deepseek-2-tmp/output/device/1380 b/results/classifier/deepseek-2-tmp/output/device/1380 deleted file mode 100644 index 6b889d7c..00000000 --- a/results/classifier/deepseek-2-tmp/output/device/1380 +++ /dev/null @@ -1,5 +0,0 @@ - -vdagent is not working properly after live migration -Additional information: -when validating on windows server 2016 Datacenter Evaluation, i found that if vdagent process or vdservice is restarted, copy/paste from host to guest or reverse will work again. i am wondering if we should send something(eg, a event?) to guest to let it reopen the port after live migration? -![image](/uploads/706117c797b13bc8b9fe15d1e2cd81bd/image.png) diff --git a/results/classifier/deepseek-2-tmp/output/device/1381879 b/results/classifier/deepseek-2-tmp/output/device/1381879 deleted file mode 100644 index 56fc25aa..00000000 --- a/results/classifier/deepseek-2-tmp/output/device/1381879 +++ /dev/null @@ -1,34 +0,0 @@ - -can not run vm with a serial port - -environment: -server: centOS 6.5, 3.14.19, x86_64 -qemu-kvm: QEMU PC emulator version 0.12.1 (qemu-kvm-0.12.1.2), Copyright (c) 2003-2008 Fabrice Bellard -qemu-system-x86_64 :QEMU emulator version 1.2.0 (qemu-kvm-1.2.0), Copyright (c) 2003-2008 Fabrice Bellard -virt-manager: 0.9.0 - -VM: centOS 6.5, 3.12.30, x86_64 - -reproduce step: -1. add serial device -2. select device type: unix socket - device parameters: path=/dev/ttyS0 - mode=client mode(connect) -3. run the VM - -phenomenon: -Error starting domain: internal error process exited while connecting to monitor: qemu-kvm: -chardev socket,id=charserial0,path=/dev/ttyS0,server,nowait: socket bind failed: Address already in use -qemu-kvm: -chardev socket,id=charserial0,path=/dev/ttyS0,server,nowait: chardev: opening backend "socket" failed - - -Traceback (most recent call last): - File "/usr/share/virt-manager/virtManager/asyncjob.py", line 44, in cb_wrapper - callback(asyncjob, *args, **kwargs) - File "/usr/share/virt-manager/virtManager/asyncjob.py", line 65, in tmpcb - callback(*args, **kwargs) - File "/usr/share/virt-manager/virtManager/domain.py", line 1114, in startup - self._backend.create() - File "/usr/lib64/python2.6/site-packages/libvirt.py", line 678, in create - if ret == -1: raise libvirtError ('virDomainCreate() failed', dom=self) -libvirtError: internal error process exited while connecting to monitor: qemu-kvm: -chardev socket,id=charserial0,path=/dev/ttyS0,server,nowait: socket bind failed: Address already in use -qemu-kvm: -chardev socket,id=charserial0,path=/dev/ttyS0,server,nowait: chardev: opening backend "socket" failed \ No newline at end of file diff --git a/results/classifier/deepseek-2-tmp/output/device/1386478 b/results/classifier/deepseek-2-tmp/output/device/1386478 deleted file mode 100644 index a0ef5c74..00000000 --- a/results/classifier/deepseek-2-tmp/output/device/1386478 +++ /dev/null @@ -1,6 +0,0 @@ - -PS/2 keyboard returns incorrect scan code for F7 to guest - -Using qemu 2.1 as supplied in Debian jessie, the F7 scan code (scan set 2) is being returned by qemu to the guest as 0x02, and not the correct value of 0x83. (I assume 0x83 is correct, given that I cannot locate any scan set 2 charts that use any other value for F7. Including those published by Microsoft.) - -I see the map in hw/input/ps2.c ps2_raw_keycode[] using the correct values, starting at F1: 5, 6, 4, 12 (0x0C). 3. 11 (0x0B), 2, 10 (0x0A), 1, 9, ... but nowhere in that map do I see 131 (0x83). \ No newline at end of file diff --git a/results/classifier/deepseek-2-tmp/output/device/1390520 b/results/classifier/deepseek-2-tmp/output/device/1390520 deleted file mode 100644 index de9d0591..00000000 --- a/results/classifier/deepseek-2-tmp/output/device/1390520 +++ /dev/null @@ -1,27 +0,0 @@ - -virtual machine fails to start with connected audio cd - -when connecting a data cd with a virtual machine (IDE CDROM 1), the virtual machine starts up and the data cd is accessable (for example to install software package or drivers), -but connecting an audio cd the following error appears: - -------------------------------------------------------------------------------------------------------------------------------- -cannot read header '/dev/sr0': Input/output error - -Traceback (most recent call last): - File "/usr/share/virt-manager/virtManager/details.py", line 2530, in _change_config_helper - func(*args) - File "/usr/share/virt-manager/virtManager/domain.py", line 850, in hotplug_storage_media - self.attach_device(devobj) - File "/usr/share/virt-manager/virtManager/domain.py", line 798, in attach_device - self._backend.attachDevice(devxml) - File "/usr/lib/python2.7/dist-packages/libvirt.py", line 493, in attachDevice - if ret == -1: raise libvirtError ('virDomainAttachDevice() failed', dom=self) -libvirtError: cannot read header '/dev/sr0': Input/output error ----------------------------------------------------------------------------------------------------------------------------- - -Description: Ubuntu 14.04.1 LTS -Release: 14.04 - -qemu: - Installiert: 2.0.0+dfsg-2ubuntu1.6 - Installationskandidat: 2.0.0+dfsg-2ubuntu1.6 \ No newline at end of file diff --git a/results/classifier/deepseek-2-tmp/output/device/1391 b/results/classifier/deepseek-2-tmp/output/device/1391 deleted file mode 100644 index 6dbfe010..00000000 --- a/results/classifier/deepseek-2-tmp/output/device/1391 +++ /dev/null @@ -1,29 +0,0 @@ - -virtio-blk: BDRV_REQ_REGISTERED_BUF optimization hint crashes on macOS -Description of problem: -When using QEMU 7.2.0 on macOS with the virtio-blk drive, the process will exit and QMP shows a `BLOCK_IO_ERROR` event. This appears to be caused by this line: https://gitlab.com/qemu-project/qemu/-/blob/master/hw/block/virtio-blk.c#L405 introduced in https://gitlab.com/qemu-project/qemu/-/commit/baf422684d73c7bf38e2c18815e18d44fcf395b6 - -Commenting that line out fixes the issue. -Steps to reproduce: -1. Run the QEMU command above with a Ubuntu 22.04 server ISO image. -2. Follow the installer and try to get to the end. -3. The process will crash before you can finish installing. -Additional information: -Following event appears on QMP: -``` -{ - data = { - action = report; - device = "drive437EC806-41A4-4CCE-A747-713352E7C27C"; - "node-name" = "#block785"; - nospace = 0; - operation = write; - reason = "Invalid argument"; - }; - event = "BLOCK_IO_ERROR"; - timestamp = { - microseconds = 808474; - seconds = 1671867673; - }; -} -``` diff --git a/results/classifier/deepseek-2-tmp/output/device/1392 b/results/classifier/deepseek-2-tmp/output/device/1392 deleted file mode 100644 index 75609cde..00000000 --- a/results/classifier/deepseek-2-tmp/output/device/1392 +++ /dev/null @@ -1,15 +0,0 @@ - -qemu 7.2.0 almalinux 9.1 guest vda io error -Description of problem: -after update the qemu from 7.1.0 to 7.2.0 guest almalinux 9.1 have disk io error ,log : -```log -Dec 24 00:17:39 rlh1 kernel: I/O error, dev vda, sector 109770720 op 0x1:(WRITE) flags 0x0 phys_seg 1 prio class 0 -Dec 24 00:17:42 rlh1 kernel: dm-0: writeback error on inode 33585275, offset 4096, sector 33359840 -Dec 24 00:17:42 rlh1 kernel: I/O error, dev vda, sector 109770776 op 0x1:(WRITE) flags 0x0 phys_seg 1 prio class 0 -Dec 24 00:17:42 rlh1 kernel: dm-0: writeback error on inode 33585275, offset 4096, sector 33359896 -Dec 24 00:17:42 rlh1 kernel: I/O error, dev vda, sector 109770832 op 0x1:(WRITE) flags 0x0 phys_seg 1 prio class 0 -``` - -then I switch back to version 7.1.0 it work as normal -Additional information: - diff --git a/results/classifier/deepseek-2-tmp/output/device/1392504 b/results/classifier/deepseek-2-tmp/output/device/1392504 deleted file mode 100644 index 08867cb5..00000000 --- a/results/classifier/deepseek-2-tmp/output/device/1392504 +++ /dev/null @@ -1,4 +0,0 @@ - -libvirt not relabeling devices on USB Passthrough - -After upgrading from Ubuntu 14.04 to Ubuntu 14.10 USB passthrough in QEMU (version is now 2.1.0 - Debian2.1+dfsg-4ubuntu6.1) is not working any more. Already tried to remove and attach the USB devices. I use 1 USB2 HDD + 1 USB3 HDD to a virtual linux machine; 1 USB2 HDD to a virual FNAS machine and a USB 2camera to virtual Win7 machine. All these devices are not working any more. \ No newline at end of file diff --git a/results/classifier/deepseek-2-tmp/output/device/1393 b/results/classifier/deepseek-2-tmp/output/device/1393 deleted file mode 100644 index 85cd7cb3..00000000 --- a/results/classifier/deepseek-2-tmp/output/device/1393 +++ /dev/null @@ -1,66 +0,0 @@ - -Abort in audio_calloc() of ac97 -Description of problem: -Section 5.10.2 of the AC97 specification (https://hands.com/~lkcl/ac97_r23.pdf) -shows the feasibility to support for rates other than 48kHZ. Specifically, -AC97_PCM_Front_DAC_Rate (reg 2Ch) should be from 8kHZ to 48kHZ. - - -An adversary can leverage this to crash QEMU. - -A nornal 48kHZ setting is like this. - -``` -ac97_realize - open_voice - as->freq = 0xbb80 # 0xbb80=48000 - AUD_open_out - audio_pcm_create_voice_pair_out (sw is NULL) - audio_pcm_sw_init_out - sw->info.freq = as->freq (in audio_pcm_init_info()) - sw->ratio = ((int64_t) sw->hw->info.freq << 32) / sw->info.freq - samples = ((int64_t) sw->HWBUF->size << 32) / sw->ratio (in audio_pcm_sw_alloc_resources_out()) -``` - -A non-48kHZ setting is like this. Since `as->freq` is too small, `sw->ratio` is -too large. Finally, `samples` is zero, failing the audio_calloc() in -audio_pcm_sw_alloc_resources_out(). - -``` -nam_writew - open_voice - as->freq = 0x6 - AUD_open_out - audio_pcm_sw_init_out (sw is not NULL) - sw->info.freq = as->freq (in audio_pcm_init_info()) - sw->ratio = ((int64_t) sw->hw->info.freq << 32) / sw->info.freq - samples = ((int64_t) sw->HWBUF->size << 32) / sw->ratio (in audio_pcm_sw_alloc_resources_out()) - audio_calloc(.., samples, ) (in audio_pcm_sw_alloc_resources_out()) -``` -Steps to reproduce: -1. download the prepared rootfs and the image. - - https://drive.google.com/file/d/1IfVCvn76HY-Eb4AZU7yvuyPzM3QC1q10/view?usp=sharing - https://drive.google.com/file/d/1JN6JgvOSI5aSLIdTEFKiskKbrGWFo0BO/view?usp=sharing - -2. run the following script. - -``` bash -QEMU_PATH=../../../qemu-devel/build/x86_64-softmmu/qemu-system-x86_64 -KERNEL_PATH=./bzImage -ROOTFS_PATH=./rootfs.ext2 -$QEMU_PATH \ - -M q35 -m 1G \ - -kernel $KERNEL_PATH \ - -drive file=$ROOTFS_PATH,if=virtio,format=raw \ - -append "root=/dev/vda console=ttyS0" \ - -net nic,model=virtio -net user \ - -device ac97,audiodev=snd0 -audiodev none,id=snd0 \ - -nographic -``` - -3. with spawned shell (the user is root and the password is empty), run -`ac97-00`. -Additional information: -In the latest QEMU, this issue was generally fixed by 12f4abf6a245c43d8411577fd400373c85f08c6b and 0cbc8bd4694f32687bf47c6da48efa48fac35fd2 that remove abort() from the source code. Even though, I still plan to send a -patch so that the warning about the invalid freq will be gone. diff --git a/results/classifier/deepseek-2-tmp/output/device/1393440 b/results/classifier/deepseek-2-tmp/output/device/1393440 deleted file mode 100644 index c642e0cc..00000000 --- a/results/classifier/deepseek-2-tmp/output/device/1393440 +++ /dev/null @@ -1,18 +0,0 @@ - -pcie.c:148: possible error in OR expression ? - -[qemu/hw/pci/pcie.c:148] -> [qemu/hw/pci/pcie.c:148]: (style) Same expression on both sides of '|'. - - pci_long_test_and_set_mask(dev->w1cmask + pos + PCI_EXP_DEVSTA, - PCI_EXP_DEVSTA_CED | PCI_EXP_DEVSTA_NFED | - PCI_EXP_DEVSTA_URD | PCI_EXP_DEVSTA_URD); - -I am guessing that something like - - pci_long_test_and_set_mask(dev->w1cmask + pos + PCI_EXP_DEVSTA, - PCI_EXP_DEVSTA_CED | PCI_EXP_DEVSTA_NFED | - PCI_EXP_DEVSTA_FED | PCI_EXP_DEVSTA_URD); - -was intended. - -I used static analyser cppcheck to find this bug. \ No newline at end of file diff --git a/results/classifier/deepseek-2-tmp/output/device/1399943 b/results/classifier/deepseek-2-tmp/output/device/1399943 deleted file mode 100644 index 1e8cf2c6..00000000 --- a/results/classifier/deepseek-2-tmp/output/device/1399943 +++ /dev/null @@ -1,29 +0,0 @@ - -qemu-system-sparc loses serial console data on EAGAIN - -When running a guest OS with a serial console under -"qemu-system-sparc -nographic", parts of the serial console output -are sometimes lost. - -This happens when a write() to standard output by qemu returns EAGAIN, -as may be the case when the guest is generating console output faster -than the tty (or pty/pipe/socket, etc.) connected to qemu's standard -output accepts it. The bug affects all releases of qemu since 1.5, -which was the first version to set stdout to O_NONBLOCK mode. Version -1.4.2 and earlier work correctly. - -To reproduce the bug, you will need a guest OS configured with a -serial console, and a host with a slow tty. The attached shell script -"sparc-test.sh" does this by using Aboriginal Linux as the serial -console guest, and a pty controlled by a Python script and the -"pexpect" Python module as the slow tty. A "seq" command is sent -to the guest to generate 100,000 lines of output containing sequential -integers, and the output is checked for gaps. The script limits the -tty output rate by occasionally sleeping for 1/10 of a second. - -This bug was originally reported against qemu-system-i386 as -bug #1335444, and has since been fixed in qemu-system-i386, -but remains in qemu-system-sparc as of today's git sources -(d00e6cddc220de993573dfb5fd160ac72ccd49ab). I am opening -this separate bug for the sparc case because I was asked -to do so by Paolo Bonzini in #1335444. \ No newline at end of file diff --git a/results/classifier/deepseek-2-tmp/output/device/1403 b/results/classifier/deepseek-2-tmp/output/device/1403 deleted file mode 100644 index 3732da14..00000000 --- a/results/classifier/deepseek-2-tmp/output/device/1403 +++ /dev/null @@ -1,2 +0,0 @@ - -qemu 7.2: test-io-channel-command fails sporadically diff --git a/results/classifier/deepseek-2-tmp/output/device/1404 b/results/classifier/deepseek-2-tmp/output/device/1404 deleted file mode 100644 index 8209ea85..00000000 --- a/results/classifier/deepseek-2-tmp/output/device/1404 +++ /dev/null @@ -1,15 +0,0 @@ - -qemu-7.2: virtio-blk-pci I/O errors with detect-zeroes=unmap -Description of problem: -Since upgrading from qemu-7.1 to qemu-7.2 I have seen many anomalies with VMs that use the virtio-blk-pci device for the root filesystem and the `detect-zeroes=unmap` option, typically in the form of I/O errors or huge decreases in read/write performance. This has been observed for both pre-existing Linux & Windows systems using the QCOW2 disk format, and a freshly created Linux system. - -* For an existing x86_64 Windows-10 guest system, hosted on Debian-11, the guest system takes many minutes to boot and Task Manager shows the virtual disk showing read/write latencies measured in seconds rather than milliseconds. -* Attempts to create a new x86_64 Debian-11 guest on a Debian-11 host produce an input/output error when trying to partition the QCOW2 hard disk /dev/vda (as per attached screenshot) ![deb11-partition-error](/uploads/de743ef1fbaf84739943b2563cb429de/deb11-partition-error.png) -* Using a pre-existing Debian-11 guest that works perfectly with qemu-7.1, fails to format a basic ext3 /dev/loop filesystem when this guest is booted with qemu-7.2, giving `mke2fs: Input/output error while writing out and closing file system` -Steps to reproduce: -(installer error) -1. Create fresh QCOW2 image: `qemu-img create -f qcow2 deb11.img 8G` -2. Run standard Debian-11 installer from ISO image and virtio-blk-pci drive and options `-drive if=none,media=disk,id=drive0,file=deb11.img,cache=writeback,discard=unmap,detect-zeroes=unmap` -3. Use default options with "guided partitioning" -Additional information: -I'm not aware of any changes to the setup of my system that would account for these problems, and have successfully tried many similar experiments with QEMU version up to and including version 7.1. Obviously, I'm hoping there's some trivial configuration error I've overlooked in qemu-7.2 - any suggestions would be much appreciated. diff --git a/results/classifier/deepseek-2-tmp/output/device/1404610 b/results/classifier/deepseek-2-tmp/output/device/1404610 deleted file mode 100644 index ff555bbc..00000000 --- a/results/classifier/deepseek-2-tmp/output/device/1404610 +++ /dev/null @@ -1,12 +0,0 @@ - -[feature request] HP300 m68k system? - -QEMU seems to support nothing (specific) that 4.4BSD was targeted to...would be useful to have a complete emulator for a full HP300 to run the binary dist from McKusick's CD set. - -Devices that'd be needed: -* 68020, 68030, or 68040 (How much of these are already present? Not sure if there was a non-standard MMU/FPU...but there was definitely a slightly-uncommon bus used for some peripherals) -* Networking was lance I am pretty sure...at least the onboard one. -* SCSI (Probably a standard chip as used EVERYWHERE ELSE..not sure off hand) -* Framebuffers optional, serial is sufficient for basic booting of 4.4. - -Tape/disk can also be done via HP-IB...but SCSI would probably be easier unless extra peripherals were required (some serial stuff.) \ No newline at end of file diff --git a/results/classifier/deepseek-2-tmp/output/device/1407454 b/results/classifier/deepseek-2-tmp/output/device/1407454 deleted file mode 100644 index afd5e534..00000000 --- a/results/classifier/deepseek-2-tmp/output/device/1407454 +++ /dev/null @@ -1,31 +0,0 @@ - -assertion failed when using "-usb" option - -SUMMARY: ----------- -Description: Latest 'master' makes it impossible to use "-usb" command line on any target -Host platform: Linux x86-64 -Guest platform: probably all (at least x86-64, i386, arm and ppc) - -REPRODUCE: ----------- -How to reproduce: -1. Run the following command: -$ qemu-system-x86_64 -usb - -Expected result: -Starting virtual machine with empty configuration - -Actual result: -Qemu crashes with following message: - -qemu-system-x86_64: /home/mplucinski/Developer/Open_Source/qemu/qemu.git/util/qemu-option.c:387: qemu_opt_get_bool_helper: Assertion `opt->desc && opt->desc->type == QEMU_OPT_BOOL' failed. -Aborted - -MORE INFORMATION: ----------- -Same happens when trying to run other target, e.g. -$ qemu-system-i386 -usb -$ qemu-system-arm -machine kmz -usb - -First commit where the issue occurs (bisection result): 49d2e648e8087d154d8bf8b91f27c8e05e79d5a6 \ No newline at end of file diff --git a/results/classifier/deepseek-2-tmp/output/device/1407808 b/results/classifier/deepseek-2-tmp/output/device/1407808 deleted file mode 100644 index f855ee5e..00000000 --- a/results/classifier/deepseek-2-tmp/output/device/1407808 +++ /dev/null @@ -1,10 +0,0 @@ - -virtual console gives strange response to ANSI DSR - -With "-serial vc" (which is the default), qemu make strange responses to the ANSI DSR escape sequence (\033[6n) which can confuse guests. - -Terminal emulators supporting the ANSI escape sequences usually support the "Device Status Report" escape sequence, \033[6n, to which as a response the terminal injects as input the response \033[n;mR, containing the current cursor position. An application running in the guest can use this escape sequence to, for example, figure out the size of the terminal it is running under, which can be useful as the guest has no other standard way to figure out a "size" for the serial port. - -Unfortunately, it seems that qemu when run with "-serial vc" (which appears to be the default), when qemu gets the \033[6n escape sequence on the serial port, it just responds with a single \033, and that's it! This can confuse an application, could concievably assume that a terminal either supports this escape sequence and injects the correct response (\033[n;mR), or doesn't support it and injects absolutely nothing as input - but not something in between. - -This caused a problem on one shell implementation on OSv that tried to figure out the terminal's size, and had to work around this unexpected behavior (see https://github.com/cloudius-systems/osv/commit/b79223584be40459861d1c12e1cb67e3e49e2a12). \ No newline at end of file diff --git a/results/classifier/deepseek-2-tmp/output/device/1413 b/results/classifier/deepseek-2-tmp/output/device/1413 deleted file mode 100644 index e910af28..00000000 --- a/results/classifier/deepseek-2-tmp/output/device/1413 +++ /dev/null @@ -1,23 +0,0 @@ - -I tried to use qemu-nbd in the shell script, but it seems that qemu-nbd has some delay. -Description of problem: - -Steps to reproduce: -1. -``` -cat ~/test.sh -#!/bin/bash -qemu-nbd -c /dev/nbd0 $1 -mount -t ntfs3 -o uid=1000,gid=1000 /dev/disk/by-label/OS /mnt/OS -``` -2. -``` -sudo ~/test.sh ~/VM/win7_i386.qcow2 -mount: /mnt/OS: special device /dev/disk/by-label/OS does not exist. - dmesg(1) may have more information after failed mount system call. - -``` -Additional information: -But when I added a one-second delay between qemu-nbd and mount commands, the problem was solved. - -The qemu-img convert command also has a similar problem. It seems that these commands have a certain delay. Is this in line with expectations? diff --git a/results/classifier/deepseek-2-tmp/output/device/1422285 b/results/classifier/deepseek-2-tmp/output/device/1422285 deleted file mode 100644 index 4caf6dad..00000000 --- a/results/classifier/deepseek-2-tmp/output/device/1422285 +++ /dev/null @@ -1,55 +0,0 @@ - -The guest will be destroyed when hot plug the VF to guest for the second time. - -Environment: ------------- -Host OS (ia32/ia32e/IA64):ia32e -Guest OS (ia32/ia32e/IA64):ia32e -Guest OS Type (Linux/Windows):linux -kvm.git Commit: 6557bada461afeaa920a189fae2cff7c8fdce39f -qemu.kvm Commit: cd2d5541271f1934345d8ca42f5fafff1744eee7 -Host Kernel Version:3.19.0-rc3 -Hardware:Haswell_EP,Ivytown_EP - - -Bug detailed description: --------------------------- -create guest , then hot plug the VF to the guest for the second time, the guest will be destroyed. - -note: -1. hot plug the device to guest with vfio, the guest works fine -2.this should be a qemu bug: -kvm + qemu = result -6557bada + cd2d5541 = bad -6557bada + a805ca54 = good - - -Reproduce steps: ----------------- -1. qemu-system-x86_64 -enable-kvm -m 2G -net none -monitor pty rhel6u5.qcow -2. echo "device_add pci-assign,host=03:10.1,id=nic" >/dev/pts/2 -3. cat /dev/pts/2 & -4. echo "device_del nic" >/dev/pts/2 -5. echo "device_add pci-assign,host=03:10.0,id=nic" >/dev/pts/2 - -Current result: ----------------- -guest will be destroyed when hot plug the vf to guest for the second time. - -Expected result: ----------------- -guest works fine when hot plug the vf to guest for the second time - -Basic root-causing log: ----------------------- -[root@vt-hsw2 cathy]# qemu-system-x86_64 -enable-kvm -m 2G -net none -monitor pty rhel6u5.qcow -char device redirected to /dev/pts/2 (label compat_monitor0) -Segmentation fault (core dumped) - - -some dmesg log: - -pci-stub 0000:03:10.1: kvm deassign device -pci-stub 0000:03:10.1: enabling device (0000 -> 0002) -qemu-system-x86[9894]: segfault at 0 ip (null) sp 00007fa73df0cae8 error 14 -pci-stub 0000:03:10.1: kvm assign device \ No newline at end of file diff --git a/results/classifier/deepseek-2-tmp/output/device/1423668 b/results/classifier/deepseek-2-tmp/output/device/1423668 deleted file mode 100644 index 38d493c0..00000000 --- a/results/classifier/deepseek-2-tmp/output/device/1423668 +++ /dev/null @@ -1,12 +0,0 @@ - -Unable to set scsi drive serial if it contains spaces. - -I am virtualzing a physical server for which I need to set the SCSI/SATA drive serial. It is comprised of 12 " " spaces then 8 letter/digits. If I exclude the spaces, the drive serial is not accurate. If I include the spaces I get the following error. - -error: Failed to start domain test1 -error: internal error: driver serial ' ABCD1234' contains unsafe characters - -virsh edit -Centos 7.0 -3.19.0-1.el7.elrepo.x86_64 -QEMU emulator version 1.5.3 (qemu-kvm-1.5.3-60.el7.centos.7), Copyright (c) 2003-2008 Fabrice Bellard \ No newline at end of file diff --git a/results/classifier/deepseek-2-tmp/output/device/1426593 b/results/classifier/deepseek-2-tmp/output/device/1426593 deleted file mode 100644 index 4876e796..00000000 --- a/results/classifier/deepseek-2-tmp/output/device/1426593 +++ /dev/null @@ -1,9 +0,0 @@ - -linux-user: doesn't handle guest setting its memory ulimit very small - -using the latest build from git (hash 041ccc922ee474693a2869d4e3b59e920c739bc0 ) and all older versions i have tested. -i am using an amd64 host with an arm chroot using "qemu-user arm cortex-a8" cpu emulation to run it - -building coreutils hangs on "checking whether printf survives out-of-memory conditions" - -i have not had time to dig into the build system to isolate the test yet, there were old reports of this bug but i can no longer find them on google. \ No newline at end of file diff --git a/results/classifier/deepseek-2-tmp/output/device/1428958 b/results/classifier/deepseek-2-tmp/output/device/1428958 deleted file mode 100644 index 60dce689..00000000 --- a/results/classifier/deepseek-2-tmp/output/device/1428958 +++ /dev/null @@ -1,66 +0,0 @@ - -random IO errors / data corruption in VMs (created and executed via virt-manager) - -I have recurring problems with VM installation and usage - data on VM disk gets corrupted at some point and it causes all sorts of problems - sometimes I cannot even install base system, other times some .so files are corrupt after isntallation, etc - totally random. -I use virt-manager to create and run VMs. I have also tried creating VMs via virt-install, result is identical. -If I use VirtualBox I have no such problems. -My OS is Fedora 20 upgraded to 21, qemu and libvirt are installed from Fedora official repos. - -Here's an example qemu command-line: -/usr/bin/qemu-system-x86_64 --machine accel=kvm --name fuel --S --machine pc-i440fx-2.1,accel=kvm,usb=off --cpu SandyBridge,+invpcid,+erms,+bmi2,+smep,+avx2,+bmi1,+fsgsbase,+abm,+pdpe1gb,+rdrand,+f16c,+osxsave,+movbe,+pcid,+pdcm,+xtpr,+fma,+tm2,+est,+smx,+vmx,+ds_cpl,+monitor,+dtes64,+pbe,+tm,+ht,+ss,+acpi,+ds,+vme --m 3142 --realtime mlock=off --smp 2,sockets=2,cores=1,threads=1 --uuid 27693a46-7a50-4a3c-bcaf-bf061ba469ed --no-user-config --nodefaults --chardev socket,id=charmonitor,path=/var/lib/libvirt/qemu/fuel.monitor,server,nowait --mon chardev=charmonitor,id=monitor,mode=control --rtc base=utc,driftfix=slew --global kvm-pit.lost_tick_policy=discard --no-hpet --no-shutdown --boot menu=on,strict=on --device ich9-usb-ehci1,id=usb,bus=pci.0,addr=0x6.0x7 --device ich9-usb-uhci1,masterbus=usb.0,firstport=0,bus=pci.0,multifunction=on,addr=0x6 --device ich9-usb-uhci2,masterbus=usb.0,firstport=2,bus=pci.0,addr=0x6.0x1 --device ich9-usb-uhci3,masterbus=usb.0,firstport=4,bus=pci.0,addr=0x6.0x2 --device lsi,id=scsi0,bus=pci.0,addr=0xa --device virtio-serial-pci,id=virtio-serial0,bus=pci.0,addr=0x7 --drive file=/home/virtual-disks/fuel.vdi,if=none,id=drive-virtio-disk0,format=vdi --device virtio-blk-pci,scsi=off,bus=pci.0,addr=0x8,drive=drive-virtio-disk0,id=virtio-disk0,bootindex=1 --drive file=/home/dsutyagin/Downloads/iso/MirantisOpenStack-6.0.iso,if=none,id=drive-scsi0-0-0,readonly=on,format=raw --device scsi-cd,bus=scsi0.0,scsi-id=0,drive=drive-scsi0-0-0,id=scsi0-0-0,bootindex=2 --netdev tap,fd=23,id=hostnet0,vhost=on,vhostfd=24 --device virtio-net-pci,netdev=hostnet0,id=net0,mac=52:54:00:0d:42:2d,bus=pci.0,addr=0x3 --netdev tap,fd=25,id=hostnet1,vhost=on,vhostfd=26 --device virtio-net-pci,netdev=hostnet1,id=net1,mac=52:54:00:a4:8c:ef,bus=pci.0,addr=0x4 --chardev pty,id=charserial0 --device isa-serial,chardev=charserial0,id=serial0 --chardev socket,id=charchannel0,path=/var/lib/libvirt/qemu/channel/target/fuel.org.qemu.guest_agent.0,server,nowait --device virtserialport,bus=virtio-serial0.0,nr=1,chardev=charchannel0,id=channel0,name=org.qemu.guest_agent.0 --chardev spicevmc,id=charchannel1,name=vdagent --device virtserialport,bus=virtio-serial0.0,nr=2,chardev=charchannel1,id=channel1,name=com.redhat.spice.0 --device usb-tablet,id=input0 --spice port=5900,addr=127.0.0.1,disable-ticketing,seamless-migration=on --device qxl-vga,id=video0,ram_size=67108864,vram_size=67108864,bus=pci.0,addr=0x2 --device intel-hda,id=sound0,bus=pci.0,addr=0x5 -device hda-duplex,id=sound0-codec0,bus=sound0.0,cad=0 --chardev spicevmc,id=charredir0,name=usbredir --device usb-redir,chardev=charredir0,id=redir0 --chardev spicevmc,id=charredir1,name=usbredir --device usb-redir,chardev=charredir1,id=redir1 --device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x9 --msg timestamp=on - -If this is not a bug, I'd be happy if you help me fix this problem. I am sorry if this is not the proper place to post such a problem. - -qemu-system-x86_64 --version -QEMU emulator version 2.1.3 (qemu-2.1.3-2.fc21), Copyright (c) 2003-2008 Fabrice Bellard - -qemu-kvm --version -QEMU emulator version 2.1.3 (qemu-2.1.3-2.fc21), Copyright (c) 2003-2008 Fabrice Bellard \ No newline at end of file diff --git a/results/classifier/deepseek-2-tmp/output/device/143 b/results/classifier/deepseek-2-tmp/output/device/143 deleted file mode 100644 index 63010496..00000000 --- a/results/classifier/deepseek-2-tmp/output/device/143 +++ /dev/null @@ -1,2 +0,0 @@ - -xhci HCIVERSION register read emulation incorrectly handled diff --git a/results/classifier/deepseek-2-tmp/output/device/1435973 b/results/classifier/deepseek-2-tmp/output/device/1435973 deleted file mode 100644 index 3e0a8a27..00000000 --- a/results/classifier/deepseek-2-tmp/output/device/1435973 +++ /dev/null @@ -1,61 +0,0 @@ - -Qemu crash when a guest linux issues specific scsi command via ioctl(SG_IO) with SCSI disk emulation. - -As of git revision 362ca922eea03240916287a8a6267801ab095d12, when guest linux issues specifit scsi command, qemu crashes. - -To reproduce. - -1. launch qemu with scsi emulatoin -qemu-sysytem-i386.exe -kernel bzImage -drive file=rootfs.ext2,index=0,if=scsi -append root=/dev/sda -drive file=\\.\PhysicalDrive1,index=1,if=scsi -2. issues scsi command via ioctl(SG_IO) on guest linux. like below. - -------------------------- -struct request_sense sens; -struct sg_io_hdr sg; -unsigned char cdb[6]; -unsigned char buf[127]; - -memset( &sens, 0, sizeof(sens) ); -memset(&sg, 0, sizeof(sg)); -memset(cdb, 0, sizeof(cdb)); -memset(buf, 0, sizeof(buf)); - -// qemu crash!!! -cdb[0] = 0xff; - -sg.dxferp = buf; -sg.dxfer_len = sizeof(buf); -sg.dxfer_direction = SG_DXFER_FROM_DEV; -sg.flags = 0; -sg.interface_id = 'S'; -sg.cmdp = cdb; -sg.cmd_len = sizeof( cdb ); -sg.sbp = (unsigned char*)&sens; -sg.mx_sb_len = sizeof( sens ); - -ioctl( fd, SG_IO, &sg ); -------------------------- - -I think cause is below code. - -scsi-bus.c L1239 -int scsi_req_parse_cdb(SCSIDevice *dev, SCSICommand *cmd, uint8_t *buf) -{ - int rc; - - cmd->lba = -1; - cmd->len = scsi_cdb_length(buf); - ... - memcpy(cmd->buf, buf, cmd->len); -} - -scsi_cdb_length(buf) returns -1 when buf[0] is unexpected value. -Then memcpy(cmd->buf, buf, 4294967295); is executed and crash. - -Environment -Qemu: git revision 362ca922eea03240916287a8a6267801ab095d12 -Guest: linux kernel 3.18.4 + buildroot -Host: Windows 7 64bit - -Thanks, -hiroaki \ No newline at end of file diff --git a/results/classifier/deepseek-2-tmp/output/device/1437970 b/results/classifier/deepseek-2-tmp/output/device/1437970 deleted file mode 100644 index da497c22..00000000 --- a/results/classifier/deepseek-2-tmp/output/device/1437970 +++ /dev/null @@ -1,45 +0,0 @@ - -qemu-system-x86_64 - two mouse pointers & fast scrolling problem - -Hello, - -System Specs - -Host: --------- -Slackware 14.1 x86_64 -Openbox 3.5.2 -tint2 panel (svn version) -Nvidia GTX660M -nvidia-driver-346.35 -Screen: 17" @1920x1080@60Hz - - -Guest ---------- -Slackware 14.1 x86_64 -XFce 4.10 -Screen 17" @1920x1080 -xf86-video-vmware 13.0.1 - -QEMU 2.2.1 - -I start Slackware in QEMU using 'Zoom To Fit' when it first boots up and I log into X, at this point I notice the mouse shows with 2 pointers and when I move the mouse around, shows as trails, but it's actually a second pointer that appears under the first. - -If I use 'Ctrl Alt F' and go into full screen mode the mouse gets corrected and only appears as one pointer and no pointer under the second one when moving around. So this mouse problem only appears the first time I log into X with 'Zoom To Fit'. - -Also if log in instead as 'Full Screen' I do not see the issue, as well as if I log in 'Full Screen' and change back to 'Zoom To Fit' it does not happen. - -I also noticed that if I scroll with the mouse wheel very fast while, as an example, in any application and wanting to move quickly around, the mouse ends up moving me instead to another virtual desktop, XFce by default uses 4. If I just scroll slowly nothing happens, it's only when moving the mouse wheel quickly that the focus gets taken off the application for some reason and put on the desktop and moves you. - -Command line options: --------------------------------- -qemu-system-x86_64 -rtc base=localtime Slackware\ 14.1\ x64.img -m 4096 --enable-kvm -smp 2 -vga vmware -usbdevice tablet - -I wanted to use -usbdevice tablet to have seamless mouse movement back and forth from Host to Guest without having to Grab... - -If I remove '-usbdevice tablet' and log into X the frst time as 'Zoom To Fit' I see two mouse pointers, but as soon as I click the desktop and the mouse is grabbed the second one goes away and when I move the mouse there is only one pointer. - -Also without the optiion '-usbdevice tablet' and I move the scroll wheel quickly the mouse stays focused on the application and it doesn't move the desktop. - -Please see the attached screen shots, qemu_1.jpg shows 2 mouse pointers when I first log into X and qemu_2.jpg shows when I'm staying in 'Zoom To Fit' mode and moving the mouse around, with a pointer under the pointer. \ No newline at end of file diff --git a/results/classifier/deepseek-2-tmp/output/device/144 b/results/classifier/deepseek-2-tmp/output/device/144 deleted file mode 100644 index 21388e8e..00000000 --- a/results/classifier/deepseek-2-tmp/output/device/144 +++ /dev/null @@ -1,2 +0,0 @@ - -Passthrough USB Host Keyboard doesn't work on Q35 platform on boot-up diff --git a/results/classifier/deepseek-2-tmp/output/device/1440843 b/results/classifier/deepseek-2-tmp/output/device/1440843 deleted file mode 100644 index 17b3eba2..00000000 --- a/results/classifier/deepseek-2-tmp/output/device/1440843 +++ /dev/null @@ -1,15 +0,0 @@ - -Guest WinXP crashes when trying to use a USB spectrometer - -I'm using Amadeus spectrometer (OceanOptics USB250) via Windows-based software "Quantum". I've tried six ways of attaching it to QEMU: - -1. command line parameter "-device usb-host,hostbus=3,hostaddr=25" -2. command line parameter "-device usb-host,vendorid=0x2457,productid=0x1030" -3. command line parameter "-usbdevice host:2457:1030 -4. command line parameter "-usbdevice host:3.25" -5. qemu console command "usb_add host:2457:1030" -5. qemu console command "usb_add host:3.25" - -From these, only "-device ..." options work, i.e. numbers 1 and 2 in the list above, and all others lead to IRQL_NOT_LESS_OR_EQUAL BSOD in usbuhci.sys when I launch Quantum, which tries to start acquiring spectra. - -I've also tried to reproduce the crash with a flash drive, but couldn't — it seems to work reliably in this case. \ No newline at end of file diff --git a/results/classifier/deepseek-2-tmp/output/device/1442 b/results/classifier/deepseek-2-tmp/output/device/1442 deleted file mode 100644 index ebffc707..00000000 --- a/results/classifier/deepseek-2-tmp/output/device/1442 +++ /dev/null @@ -1,2 +0,0 @@ - -RISC-V qemu, get cpu tick diff --git a/results/classifier/deepseek-2-tmp/output/device/1445633 b/results/classifier/deepseek-2-tmp/output/device/1445633 deleted file mode 100644 index 7a24462f..00000000 --- a/results/classifier/deepseek-2-tmp/output/device/1445633 +++ /dev/null @@ -1,14 +0,0 @@ - -Creating a passthrough USB device causes excessive CPU usage in the guest - -My host machine is a Lenovo X1 Carbon (3rd gen) laptop running 64-bit Ubuntu Linux 14.04. My guest machine is running 64-bit Ubuntu Linux 12.04. My QEMU was compiled moments ago from the git repository, and it says its version is: -qemu-x86_64 version 2.2.93, Copyright (c) 2003-2008 Fabrice Bellard - -My issue is that when I create a passthrough for a USB host device to the guest, it causes qemu's CPU utilization on the host to increase significantly and stay there. After the passthrough is created, qemu's CPU usage in top hovers between 20% and 30% (evenly spread across CPUs). In virt-manager's CPU usage chart, it shows the guest's CPU usage growing from 0% to about 5%, although running "top" in the guest does not show an increase in CPU usage. These usage levels drop back down to normal (0 to 1%) only after I physically unplug the device or remove the passthrough mapping. - -It doesn't seem to matter what the device is. I have tested it using: -A Realtek rtl8192cu-based 802.11n adapter -An HP optical mouse -A Samsung Galaxy S5 phone - -The behavior is the same regardless of device, and they otherwise seem to work properly in the guest machine. \ No newline at end of file diff --git a/results/classifier/deepseek-2-tmp/output/device/1451 b/results/classifier/deepseek-2-tmp/output/device/1451 deleted file mode 100644 index 879b366a..00000000 --- a/results/classifier/deepseek-2-tmp/output/device/1451 +++ /dev/null @@ -1,2 +0,0 @@ - -Assertion failure: virtio_net_get_subqueue(nc)->async_tx.elem failed. diff --git a/results/classifier/deepseek-2-tmp/output/device/1453025 b/results/classifier/deepseek-2-tmp/output/device/1453025 deleted file mode 100644 index 426d65b0..00000000 --- a/results/classifier/deepseek-2-tmp/output/device/1453025 +++ /dev/null @@ -1,16 +0,0 @@ - -remote usb3.0 redir failed, when guest os has more than one vcpus - -I was testing usb3.0 redirection, it worked fine with one vcpu. -But when I set vcpu to a number greater than one, the redirection failed. - -Host and guest are Fedora 20 and Windows 7. -Client is remote-viwer. - -version: qemu 2.3.0 libvirt 1.2.15 spice 0.12.5 - -libvirt xml: - -2 - - \ No newline at end of file diff --git a/results/classifier/deepseek-2-tmp/output/device/1457 b/results/classifier/deepseek-2-tmp/output/device/1457 deleted file mode 100644 index 19cbbd91..00000000 --- a/results/classifier/deepseek-2-tmp/output/device/1457 +++ /dev/null @@ -1,2 +0,0 @@ - -ide: assertion `bmdma->bus->retry_unit != (uint8_t)-1' failed. diff --git a/results/classifier/deepseek-2-tmp/output/device/1458 b/results/classifier/deepseek-2-tmp/output/device/1458 deleted file mode 100644 index 899edb3b..00000000 --- a/results/classifier/deepseek-2-tmp/output/device/1458 +++ /dev/null @@ -1,28 +0,0 @@ - -ns16550a reg-shift incorrect for qemu-system-riscv64 -Description of problem: -Missing reg-shift 0 on the ns16550n in qemu-system-riscv64 creates an impossible assumption case. -Steps to reproduce: -1. qemu-system-riscv64 -M virt,dumpdtb=dtb -2. dtc dtb | less - - serial@10000000 { - interrupts = <0x0a>; - interrupt-parent = <0x03>; - clock-frequency = "\08@"; - reg = <0x00 0x10000000 0x00 0x100>; - compatible = "ns16550a"; - }; - -Generally, ns16550a has a default reg-shift of 0 on x86,x86_64 for compatibility reasons. All other architectures have an assumed reg-shift of 2 (or having the reg-shift assumption overridden by fdt providing a reg-shift property) - -Beyond the above, anything non-standard is assumed to be specified by the "reg-shift" property fdt. - -qemu-system-riscv64 seems to "assume" a reg-shift of 0. Other riscv64 devices don't supply "reg-shift" (SiFive Unmatched) and "assume" 2. -The above means driver writers don't actually know what to "assume" on riscv64 ns16550a when no reg-shift is present. - - -Essentially, qemu-system-riscv64 needs to do one of the following: - -* If serial ns16550a with a uart reg-shift of 0 is intentional, qemu needs to advertise the deviance via "reg-shift 0" -* If serial ns16550a with a uart reg-shift of 0 is unintentional, it needs updated to 2 so drivers can assume 2 on riscv64. diff --git a/results/classifier/deepseek-2-tmp/output/device/1460 b/results/classifier/deepseek-2-tmp/output/device/1460 deleted file mode 100644 index dcf6aea3..00000000 --- a/results/classifier/deepseek-2-tmp/output/device/1460 +++ /dev/null @@ -1,6 +0,0 @@ - -block_load fails if last block is included in snapshot and block device isn't multiple of BLK_MIG_BLOCK_SIZE -Description of problem: -The `block_load` function in `migration/block.c` has a bug where `blk_pwrite` or `blk_pwrite_zeroes` always write `cluster_size` bytes. If the underlying device is not a multiple of `BLK_MIG_BLOCK_SIZE`, the write will fail with -EIO when trying to write past the end of the device, as `blk_check_byte_request` checks the length of the device. - -This can be fixed by ensuring that `cur_addr` + write length passed to `blk_pwrite`/`blk_pwrite_zeroes` never exceeds the total length of the block device. diff --git a/results/classifier/deepseek-2-tmp/output/device/1465 b/results/classifier/deepseek-2-tmp/output/device/1465 deleted file mode 100644 index 73617f41..00000000 --- a/results/classifier/deepseek-2-tmp/output/device/1465 +++ /dev/null @@ -1,2 +0,0 @@ - -MBR/Partition table corruption/loss , probably related to virtual sata disks and backup diff --git a/results/classifier/deepseek-2-tmp/output/device/1468 b/results/classifier/deepseek-2-tmp/output/device/1468 deleted file mode 100644 index 792e37a2..00000000 --- a/results/classifier/deepseek-2-tmp/output/device/1468 +++ /dev/null @@ -1,7 +0,0 @@ - -qemu hangs on white windows when connecting to virtual port using -serial option when using Windows OS -Description of problem: -I was trying to connect windbg with a qemu vm. -First I try using named pipes but all the tutorials I found online result in the qemu windows not even showing. So I give up and trying to use virtual COMs to connect the qemu machine with windbg over serial port. So I created using professional Virtual come driver a link between COM2 and COM4. Now I run qemu with -serial COM2 and I do not run windbg than it run correctly and no problem is present. As soon as I run windbg qemu hangs at startup just after the main window is created. The qemu window remains white and windows shows the normal "The application is not responding". It's like the program is in a infinite loop situation. -Also I noted that If I run qemu and not windbg as soon as the other COM port is connected qemu would stop working and remain frozed. Again showing the "The application is not responding". -If instead of qemu I use other "commercial" software with the same setup (of course there I could use named pipes anyway) I can connect windbg with the machine and do the debug session. diff --git a/results/classifier/deepseek-2-tmp/output/device/147 b/results/classifier/deepseek-2-tmp/output/device/147 deleted file mode 100644 index 1ba41df5..00000000 --- a/results/classifier/deepseek-2-tmp/output/device/147 +++ /dev/null @@ -1,2 +0,0 @@ - -Interacting with NetBSD serial console boot blocks no longer works diff --git a/results/classifier/deepseek-2-tmp/output/device/1470536 b/results/classifier/deepseek-2-tmp/output/device/1470536 deleted file mode 100644 index 26cd71c5..00000000 --- a/results/classifier/deepseek-2-tmp/output/device/1470536 +++ /dev/null @@ -1,13 +0,0 @@ - -qemu-img incorrectly prints "qemu-img: Host floppy pass-through is deprecated" - -qemu-img incorrectly prints this warning when you use /dev/fd/ to pass in file descriptors. A simple way to demonstrate this uses bash process substitution, so the following will only work if you are using bash as your shell: - -$ qemu-img info <( cat /dev/null ) -qemu-img: Host floppy pass-through is deprecated -Support for it will be removed in a future release. -qemu-img: Could not open '/dev/fd/63': Could not refresh total sector count: Illegal seek - -The root cause is a bug in block/raw-posix.c:floppy_probe_device() where it thinks anything starting with /dev/fd is a floppy drive, which is not the case here: - -http://git.qemu.org/?p=qemu.git;a=blob;f=block/raw-posix.c;h=cbe6574bf4da90a124436a40422dce3667da71e6;hb=HEAD#l2425 \ No newline at end of file diff --git a/results/classifier/deepseek-2-tmp/output/device/1476183 b/results/classifier/deepseek-2-tmp/output/device/1476183 deleted file mode 100644 index ee693c08..00000000 --- a/results/classifier/deepseek-2-tmp/output/device/1476183 +++ /dev/null @@ -1,18 +0,0 @@ - -can not create 4 serial port on window (guest os) - -qemu ver: 2.1.2-Latest - -guest os: window 7 64bit with 2 cpu - -problem: when qemu start with 4 serial port, on linux(rhel 7) guest os, /dev/ttyS0-4 is work fine. but on window 7 guest os, only show com1,com2 in device manager, how to get com3 & com4 ? - -qemu cmd: - -chardev spiceport,id=charserial0,name=org.qemu.console.serial.0 - -device isa-serial,chardev=charserial0,id=serial0 - -chardev spiceport,id=charserial1,name=org.qemu.console.serial.1 - -device isa-serial,chardev=charserial1,id=serial1 - -chardev spiceport,id=charserial2,name=org.qemu.console.serial.2 - -device isa-serial,chardev=charserial2,id=serial2 - -chardev spiceport,id=charserial3,name=org.qemu.console.serial.3 - -device isa-serial,chardev=charserial3,id=serial3 \ No newline at end of file diff --git a/results/classifier/deepseek-2-tmp/output/device/1481750 b/results/classifier/deepseek-2-tmp/output/device/1481750 deleted file mode 100644 index 9029b3f9..00000000 --- a/results/classifier/deepseek-2-tmp/output/device/1481750 +++ /dev/null @@ -1,19 +0,0 @@ - -qemu-system-ppc hangs when running -M ppce500 -bios u-boot.e500 - -On recent qemu versions (tested on locally built versions 2.3.50 and 2.3.93) -the command below causes qemu to hang before the u-boot command prompt is reached. -However in an older version (2.2.1) the u-boot bootprompt is reached and can be typed into, -so apparenly something has broken along the way. - - -ppc-softmmu/qemu-system-ppc -d guest_errors -d in_asm -M ppce500 -nographic -bios pc-bios/u-boot.e500 - - -From the -d in_asm argument you can compare the runs and the 2.2.1 version -outputs a lot more. - ------- -- I use the unmodified u-boot.e500 that is inlcuded with each respective version. -- when building qemu my configure paramters were in all three cases : -'./configure' '--target-list=ppc-softmmu,arm-softmmu' '--audio-drv-list=' '--enable-debug' \ No newline at end of file diff --git a/results/classifier/deepseek-2-tmp/output/device/1483 b/results/classifier/deepseek-2-tmp/output/device/1483 deleted file mode 100644 index 33219fd2..00000000 --- a/results/classifier/deepseek-2-tmp/output/device/1483 +++ /dev/null @@ -1,2 +0,0 @@ - -Failed to mount pmem device in qemu diff --git a/results/classifier/deepseek-2-tmp/output/device/1486768 b/results/classifier/deepseek-2-tmp/output/device/1486768 deleted file mode 100644 index 89266637..00000000 --- a/results/classifier/deepseek-2-tmp/output/device/1486768 +++ /dev/null @@ -1,18 +0,0 @@ - -BlackMagic USB3 video capture returns only blank frames in Windows (xHCI issue) - -Hi, - -I've got an Intensity Shuttle USB3; it's a HDMI video capture card. It doesn't have any Linux drivers, so I'm trying to get it to work in a Windows 10 guest inside QEMU. I'm running latest git as of today (2015-08-20). I use this command line: - -sudo x86_64-softmmu/qemu-system-x86_64 -enable-kvm -smp 2 -m 4096 -acpitable file=/sys/firmware/acpi/tables/MSDM -drive file=/home/sesse/windows.raw,if=virtio,format=raw -cpu host -netdev tap,id=hostnet0 -device virtio-net-pci,netdev=hostnet0,id=net0 -monitor stdio -device nec-usb-xhci,id=xhci -device usb-host,bus=xhci.0,vendorid=0x1edb,productid=0xbd3b -usbdevice tablet - -(I will add that the seemingly logical “host:1edb:bd3b,bus=xhci.0” did _not_ add the device at all. I don't know why, probably some parser issue?) - -The card is properly detected, and the driver thinks everything is fine, running on the virtualized USB3 host and all. Looking at usbmon, there's lots of isochronous frames during capture, and they reach the host (looking at USBpcap on the Windows 10 side). However, the driver refuses to capture any video—all frames become black in all applications I try (well, Media Express seems to hardly store any frames at all in the .avi). However, audio is captured without a hitch. Curiously enough, no dropped frames are reported. There's no sign of CPU shortage; both host and guest seem to be happy around 20% of one core. - -I am fairly certain this is an issue with the xHCI driver in QEMU, because if I give it the entire USB controller via VT-d, it works flawlessly, with video and all. For reference, here's the associated command line I use for that (after I've unbound it from the Linux system): - -sudo x86_64-softmmu/qemu-system-x86_64 -enable-kvm -smp 2 -m 4096 -acpitable file=/sys/firmware/acpi/tables/MSDM -drive file=/home/sesse/windows.raw,if=virtio,format=raw -cpu host -netdev tap,id=hostnet0 -device virtio-net-pci,netdev=hostnet0,id=net0 -monitor stdio -usbdevice tablet -device pci-assign,host=00:14.0 - -I can get USB pcap logs from both sides if you want, but they are huge (gigabytes) since the data rate is so high. \ No newline at end of file diff --git a/results/classifier/deepseek-2-tmp/output/device/1488363 b/results/classifier/deepseek-2-tmp/output/device/1488363 deleted file mode 100644 index c62957e8..00000000 --- a/results/classifier/deepseek-2-tmp/output/device/1488363 +++ /dev/null @@ -1,54 +0,0 @@ - -qemu 2.4.0 hangs using vfio for pci passthrough of graphics card - -2.3.0 (manjaro distro package) works fine. 2.4.0 (manjaro or the arch vanilla one) hangs on the SeaBIOS screen when saying "Press F12 for boot menu". All tested with the same hardware, OS, command and configuration. It also starts without the GPU passed through, even with the USB passed through. I am using the latest SeaBIOS 1.8.2. - -The release notes say: - VFIO - Support for resetting AMD Bonaire and Hawaii GPUs - Platform device passthrough support for Calxeda xgmac devices - -So maybe something there broke it. - -I am using the arch qemu 2.4.0 PKGBUILD (modified to have make -j8 and removed iscsi, gluster, ceph, etc.), which uses vanilla sources and no patches. https://projects.archlinux.org/svntogit/packages.git/tree/trunk?h=packages/qemu - -I am not using a frontend. I am using a script I wrote that generates the command below. - -Guest OS here would be 64 bit windows 7, but it didn't start so that's not relevant. Also a Manjaro Linux VM won't start. - -CPU is AMD FX-8150; board is Gigabyte GA-990FXA-UD5 (990FX chipset). - -full command line (without the \ after each line) is: - -qemu-system-x86_64 - -enable-kvm - -M q35 - -m 3584 - -cpu host - -boot c - -smp 7,sockets=1,cores=7,threads=1 - -vga none - -device ioh3420,bus=pcie.0,addr=1c.0,port=1,chassis=1,id=root.1 - -device vfio-pci,host=04:00.0,bus=root.1,multifunction=on,x-vga=on,addr=0.0,romfile=Sapphire.R7260X.1024.131106.rom - -device vfio-pci,host=00:14.2,bus=pcie.0 - -device vfio-pci,host=00:16.0,bus=root.1 - -device vfio-pci,host=00:16.2,bus=root.1 - -usb - -device ahci,bus=pcie.0,id=ahci - -drive file=/dev/data/vm1,id=disk1,format=raw,if=virtio,index=0,media=disk,discard=on - -drive media=cdrom,id=cdrom,index=5,media=cdrom - -netdev type=tap,id=net0,ifname=tap-vm1 - -device virtio-net-pci,netdev=net0,mac=00:01:02:03:04:05 - -monitor stdio - -boot menu=on - - -$ lspci -nn | grep -E "04:00.0|00:14.2|00:16.0|00:16.2" -00:14.2 Audio device [0403]: Advanced Micro Devices, Inc. [AMD/ATI] SBx00 Azalia (Intel HDA) [1002:4383] (rev 40) -00:16.0 USB controller [0c03]: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 USB OHCI0 Controller [1002:4397] -00:16.2 USB controller [0c03]: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 USB EHCI Controller [1002:4396] -04:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Bonaire XTX [Radeon R7 260X] [1002:6658] - - -Also I have this one that also hangs: -05:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Juniper XT [Radeon HD 6770] [1002:68ba] \ No newline at end of file diff --git a/results/classifier/deepseek-2-tmp/output/device/1490 b/results/classifier/deepseek-2-tmp/output/device/1490 deleted file mode 100644 index a5f4493e..00000000 --- a/results/classifier/deepseek-2-tmp/output/device/1490 +++ /dev/null @@ -1,62 +0,0 @@ - -Keystrokes for F13-24 are not forwarded by an evdev input device -Description of problem: -Currently, keystrokes for F13-F24 are not forwarded by an evdev input device. -Steps to reproduce: -``` -/usr/bin/qemu-system-x86_64 \ --name guest=win10,debug-threads=on \ --S \ --object '{"qom-type":"secret","id":"masterKey0","format":"raw","file":"/var/lib/libvirt/qemu/domain-11-win10/master-key.aes"}' \ --machine pc-q35-7.2,usb=off,vmport=off,dump-guest-core=off,memory-backend=pc.ram \ --accel kvm \ --cpu host,migratable=on,hv-time=on,hv-relaxed=on,hv-vapic=on,hv-spinlocks=0x1fff \ --m 4096 \ --object '{"qom-type":"memory-backend-ram","id":"pc.ram","size":4294967296}' \ --overcommit mem-lock=off \ --smp 4,sockets=1,dies=1,cores=4,threads=1 \ --uuid ca2e9d01-6e02-4aa7-9feb-7846499f7d8a \ --no-user-config \ --nodefaults \ --chardev socket,id=charmonitor,fd=33,server=on,wait=off \ --mon chardev=charmonitor,id=monitor,mode=control \ --rtc base=localtime,driftfix=slew \ --global kvm-pit.lost_tick_policy=delay \ --no-hpet \ --no-shutdown \ --global ICH9-LPC.disable_s3=1 \ --global ICH9-LPC.disable_s4=1 \ --boot strict=on \ --device '{"driver":"pcie-root-port","port":16,"chassis":1,"id":"pci.1","bus":"pcie.0","multifunction":true,"addr":"0x2"}' \ --device '{"driver":"pcie-root-port","port":17,"chassis":2,"id":"pci.2","bus":"pcie.0","addr":"0x2.0x1"}' \ --device '{"driver":"pcie-root-port","port":18,"chassis":3,"id":"pci.3","bus":"pcie.0","addr":"0x2.0x2"}' \ --device '{"driver":"pcie-root-port","port":19,"chassis":4,"id":"pci.4","bus":"pcie.0","addr":"0x2.0x3"}' \ --device '{"driver":"pcie-root-port","port":20,"chassis":5,"id":"pci.5","bus":"pcie.0","addr":"0x2.0x4"}' \ --device '{"driver":"pcie-root-port","port":21,"chassis":6,"id":"pci.6","bus":"pcie.0","addr":"0x2.0x5"}' \ --device '{"driver":"pcie-root-port","port":22,"chassis":7,"id":"pci.7","bus":"pcie.0","addr":"0x2.0x6"}' \ --device '{"driver":"pcie-root-port","port":23,"chassis":8,"id":"pci.8","bus":"pcie.0","addr":"0x2.0x7"}' \ --device '{"driver":"pcie-root-port","port":24,"chassis":9,"id":"pci.9","bus":"pcie.0","multifunction":true,"addr":"0x3"}' \ --device '{"driver":"pcie-root-port","port":25,"chassis":10,"id":"pci.10","bus":"pcie.0","addr":"0x3.0x1"}' \ --device '{"driver":"pcie-root-port","port":26,"chassis":11,"id":"pci.11","bus":"pcie.0","addr":"0x3.0x2"}' \ --device '{"driver":"pcie-root-port","port":27,"chassis":12,"id":"pci.12","bus":"pcie.0","addr":"0x3.0x3"}' \ --device '{"driver":"pcie-root-port","port":28,"chassis":13,"id":"pci.13","bus":"pcie.0","addr":"0x3.0x4"}' \ --device '{"driver":"pcie-root-port","port":29,"chassis":14,"id":"pci.14","bus":"pcie.0","addr":"0x3.0x5"}' \ --device '{"driver":"qemu-xhci","id":"usb","bus":"pci.1","addr":"0x0"}' \ --blockdev '{"driver":"file","filename":"/tmp/win10.qcow2","node-name":"libvirt-1-storage","auto-read-only":true,"discard":"unmap"}' \ --blockdev '{"node-name":"libvirt-1-format","read-only":false,"driver":"qcow2","file":"libvirt-1-storage","backing":null}' \ --device '{"driver":"ide-hd","bus":"ide.0","drive":"libvirt-1-format","id":"sata0-0-0","bootindex":2}' \ --object '{"qom-type":"input-linux","id":"input2","evdev":"/dev/input/by-id/usb-04d9_f50e-event-mouse"}' \ --object '{"qom-type":"input-linux","id":"input3","evdev":"/dev/input/by-id/usb-0c45_6515-event-kbd","repeat":true,"grab_all":true,"grab-toggle":"scrolllock"}' \ --audiodev '{"id":"audio1","driver":"spice"}' \ --spice port=5900,addr=127.0.0.1,disable-ticketing=on,image-compression=off,seamless-migration=on \ --device '{"driver":"qxl-vga","id":"video0","max_outputs":1,"ram_size":67108864,"vram_size":67108864,"vram64_size_mb":0,"vgamem_mb":16,"bus":"pcie.0","addr":"0x1"}' \ --device '{"driver":"virtio-balloon-pci","id":"balloon0","bus":"pci.2","addr":"0x0"}' \ --sandbox on,obsolete=deny,elevateprivileges=deny,spawn=deny,resourcecontrol=deny \ --msg timestamp=on -``` - -This is probably not a minimal example, but I didn't know how to generate one. I think the only relevant lines are these: -``` --object '{"qom-type":"input-linux","id":"input2","evdev":"/dev/input/by-id/usb-04d9_f50e-event-mouse"}' \ --object '{"qom-type":"input-linux","id":"input3","evdev":"/dev/input/by-id/usb-0c45_6515-event-kbd","repeat":true,"grab_all":true,"grab-toggle":"scrolllock"}' -``` diff --git a/results/classifier/deepseek-2-tmp/output/device/1490886 b/results/classifier/deepseek-2-tmp/output/device/1490886 deleted file mode 100644 index f5161294..00000000 --- a/results/classifier/deepseek-2-tmp/output/device/1490886 +++ /dev/null @@ -1,33 +0,0 @@ - -spice-qemu-char.c Assert - -spice-qemu-char.c:173: spice_chr_add_watch: Assertion `cond == G_IO_OUT' failed. -I trace the code virtio-console.c: -ret = qemu_chr_fe_write(vcon->chr, buf, len); - trace_virtio_console_flush_buf(port->id, len, ret); - - if (ret < len) { - VirtIOSerialPortClass *k = VIRTIO_SERIAL_PORT_GET_CLASS(port); - - /* - * Ideally we'd get a better error code than just -1, but - * that's what the chardev interface gives us right now. If - * we had a finer-grained message, like -EPIPE, we could close - * this connection. - */ - if (ret < 0) - ret = 0; - if (!k->is_console) { - virtio_serial_throttle_port(port, true); - if (!vcon->watch) { - vcon->watch = qemu_chr_fe_add_watch(vcon->chr, - G_IO_OUT|G_IO_HUP, - chr_write_unblocked, vcon); - } - } - } -and spice-qemu-char.c in function:spice_chr_add_watch -assert(cond == G_IO_OUT); -so run in this code,will trigger this assert. - -My qemu version is 2.3.0 and spice-server version is 0.12.5 \ No newline at end of file diff --git a/results/classifier/deepseek-2-tmp/output/device/1499908 b/results/classifier/deepseek-2-tmp/output/device/1499908 deleted file mode 100644 index 4558c42b..00000000 --- a/results/classifier/deepseek-2-tmp/output/device/1499908 +++ /dev/null @@ -1,56 +0,0 @@ - -hda sound capture broken with VNC - -QEmu is being used to run the Wine conformance tests in Windows virtual machines. Wine's conformance tests check the behavior of various Windows APIs and verify that they behave as expected. One of the tests checks the behavior of the mmdevapi sound capture APIs. This test works fine on real hardware and also works fine in various QEmu VMs but fails in some others. Further investigation showed that: - - * The mmdevapi:capture tests work on the two Vista VMs. Those use the ac97 sound card and are configured for VNC access to the VM. - - * The mmdevapi:capture tests fail in the Windows 7+ VMs. Those use an hda sound card and are configured for VNC access to the VM (so '-device intel-hda,id=sound0,bus=pci.0,addr=0x4 -device hda-duplex,id=sound0-codec0,bus=sound0.0,cad=0' and '-vnc 127.0.0.1:0'). - - * Furthermore configuring the VM for Spice access fixes the mmdevapi:capture test (so replacing -vnc with '-spice port=5900,addr=127.0.0.1,disable-ticketing,seamless-migration=on'), this even if no client connects to the VM. - -So in effect the -spice and -vnc options change the behavior of the sound device. - -To reproduce this bug: -1. Set up a Windows 7+ VM with an hda sound card ('ich6' in libvirt). -2. Set it up for access using VNC. -3. Copy the attached mmdevapi_test.exe file to it. (*) -4. Run the tests as follows: - mmdevapi_test.exe capture - -If you see these 'Test Failed' lines then the bug is still present: - -capture.c:586: Returned latency: 5.8050 ms -capture.c:178: Test failed: Position 1015 expected 0 -capture.c:186: Wait'ed position 1015 pad 0 flags 1, amount of frames locked: 448 -capture.c:228: Test failed: Position 2167 expected 1463 -capture.c:248: Sleep.1 position 2167 pad 4032 flags 1, amount of frames locked: 448 -capture.c:256: Test failed: Position 2167 expected 1463 -capture.c:292: GetBufferSize 21996 period size 448 -capture.c:302: Overrun position 4215 pad 8960 flags 1, amount of frames locked: 448 -capture.c:308: Test failed: GCP 8960 vs. BufferSize 21996 -capture.c:313: Test failed: Position 4215 gap 2304 -capture.c:329: Cont'ed position 5303 pad 8512 flags 1, amount of frames locked: 448 -capture.c:333: Test failed: Position 5303 expected 4663 -capture.c:334: Test failed: flags 1 -capture.c:353: Restart position 7351 pad 8064 flags 1, amount of frames locked: 448 -capture.c:358: Test failed: Position 7351 expected 5111 -capture.c:359: Test failed: flags 1 - -In case it helps, here is the source of mmdevapi_test.exe: -https://source.winehq.org/git/wine.git/?a=blob;f=dlls/mmdevapi/tests/capture.c;hb=60d1d6f5952e8b5d6fb0327a28c047058851fa70#l178 - - -So far I have confirmed that this bug is present in QEmu as shipped in the following Debian packages: - * qemu-kvm + qemu-system-x86 1:2.1+dfsg-12+deb8u2 + linux-image-3.16.0-4-amd64 3.16.7-ckt11-1+deb8u3 - * qemu-system-x86 1:2.3+dfsg-6a + linux-image-4.1.0-1-amd64 4.1.3-1 - - -(*) As alternatives to using the attached binary you can: -- Compile it from Wine's source. See: - https://source.winehq.org/git/wine.git/ - -- Or download the latest WineTest binary from https://test.winehq.org/builds/winetest-latest.exe - And extract the mmdevapi_test.exe from there: - winetest.exe -x tests - tests\mmdevapi_test.exe capture \ No newline at end of file diff --git a/results/classifier/deepseek-2-tmp/output/device/1500175 b/results/classifier/deepseek-2-tmp/output/device/1500175 deleted file mode 100644 index 1d964fd2..00000000 --- a/results/classifier/deepseek-2-tmp/output/device/1500175 +++ /dev/null @@ -1,38 +0,0 @@ - -unable to init msix vectors - -Using the latest stable (2.4.0.1) and earlier releases (at least down to 2.3.1), I am unable to run a qemu-system-arm virtualization on a Mac OS X Yosemite machine. QEMU was compiled with --enable-sdl. - -Command line: - -qemu-system-arm -device virtio-net,netdev=user.0 -drive file=pack,if=virtio,cache=writeback,discard=ignore -netdev user,id=user.0,hostfwd=tcp::3499-:22 -cdrom /opt/node-4.1.0/packer/2015-05-05-raspbian-wheezy.img -m 512M -boot once=d -vnc 0.0.0.0:87 -name packer-qemu -machine type=versatilepb -nographic - -Output: - -qemu-system-arm: -device virtio-net,netdev=user.0: unable to init msix vectors to 3 -qemu-system-arm: -drive file=pack,if=virtio,cache=writeback,discard=ignore: unable to init msix vectors to 2 -qemu: fatal: Trying to execute code outside RAM or ROM at 0x10000000 - -R00=00000000 R01=00000000 R02=00000000 R03=00000000 -R04=00000000 R05=00000000 R06=00000000 R07=00000000 -R08=00000000 R09=00000000 R10=00000000 R11=00000000 -R12=00000000 R13=00000000 R14=00000000 R15=10000000 -PSR=400001d3 -Z-- A svc32 -s00=00000000 s01=00000000 d00=0000000000000000 -s02=00000000 s03=00000000 d01=0000000000000000 -s04=00000000 s05=00000000 d02=0000000000000000 -s06=00000000 s07=00000000 d03=0000000000000000 -s08=00000000 s09=00000000 d04=0000000000000000 -s10=00000000 s11=00000000 d05=0000000000000000 -s12=00000000 s13=00000000 d06=0000000000000000 -s14=00000000 s15=00000000 d07=0000000000000000 -s16=00000000 s17=00000000 d08=0000000000000000 -s18=00000000 s19=00000000 d09=0000000000000000 -s20=00000000 s21=00000000 d10=0000000000000000 -s22=00000000 s23=00000000 d11=0000000000000000 -s24=00000000 s25=00000000 d12=0000000000000000 -s26=00000000 s27=00000000 d13=0000000000000000 -s28=00000000 s29=00000000 d14=0000000000000000 -s30=00000000 s31=00000000 d15=0000000000000000 -FPSCR: 00000000 -[1] 1322 abort qemu-system-arm -device virtio-net,netdev=user.0 -drive -netdev -cdrom -m \ No newline at end of file diff --git a/results/classifier/deepseek-2-tmp/output/device/1502613 b/results/classifier/deepseek-2-tmp/output/device/1502613 deleted file mode 100644 index a6295628..00000000 --- a/results/classifier/deepseek-2-tmp/output/device/1502613 +++ /dev/null @@ -1,8 +0,0 @@ - -[Feature Request] Battery Status / Virtual Battery - -When using virtualization on notebooks heavily then virtual machines do not realize that they're running on a notebook device causing high power consumption because they're not switching into a optimized "laptop mode". This leads to the circumstance that they are trying to do things like defragmentation / virtus scan / etc. while the host is still running on batteries. - -So it would be great if QEMU / KVM would have support for emulating "Virtual Batteries" to guests causing them to enable power-saving options like disabling specific services / devices / file operations automatically by OS. - -Optionally a great feature would be to set virtual battery's status manually. For example: Current charge rate / charging / discharging / ... \ No newline at end of file diff --git a/results/classifier/deepseek-2-tmp/output/device/1504 b/results/classifier/deepseek-2-tmp/output/device/1504 deleted file mode 100644 index 62f69d28..00000000 --- a/results/classifier/deepseek-2-tmp/output/device/1504 +++ /dev/null @@ -1,2 +0,0 @@ - -Implement Synopsys DesignWare PCI-I2C adapter model diff --git a/results/classifier/deepseek-2-tmp/output/device/1509336 b/results/classifier/deepseek-2-tmp/output/device/1509336 deleted file mode 100644 index cd1ac79c..00000000 --- a/results/classifier/deepseek-2-tmp/output/device/1509336 +++ /dev/null @@ -1,54 +0,0 @@ - -USB passthru not work with Mac OS X El Capitan - -QEMU emulator version 2.4.50 with kernel kvm module from linux kernel 3.16.0 or 4.2.3 - -Since upgrading from Yosemite to El Capitan - USB passthru does not work. Note USB passthru worked perfectly with Maverick and Yosemite. I attempt to use different USB hosts. I found a patch for widows xp that had similar problem the patch was applied in 2012. Note NO problems with USB passthru with windows or linux clients. If it matters the devices that I am trying to passthru USB are smartcard reader and webcam. The devices are present in El Capitan but do not function. - -These are the massages from loading the VM (El Capitan). The first two lines are from the clover bootloader. The ehci warnings are generated when loading Mac Os X El Capitan. - -QEMU 2.4.50 monitor - type 'help' for more information -### These messages below started when using the clover bootloader and occur when loading El Capitan, Maverick or Yosemite. -### The bootloader is Clover version 3292 -(qemu) ehci: PERIODIC list base register set while periodic schedule - is enabled and HC is enabled -ehci: ASYNC list address register set while async schedule - is enabled and HC is enabled - -#### Below are errors when the guest host (El Capitan) is loading from qemu monitor. The messages below only occur when loading El Capitan. -ehci warning: guest requested more bytes than allowed -processing error - resetting ehci HC -ehci warning: guest requested more bytes than allowed -processing error - resetting ehci HC -ehci warning: guest requested more bytes than allowed -processing error - resetting ehci HC - -This is the errors from the guest os - Mac Os X - El Capitan -000000.580358 AppleUSBLegacyRoot@: AppleUSBLegacyRoot::init: enabling legacy matching -000001.803455 AppleUSBEHCIPCI@fd000000: AppleUSBEHCI::WaitForAsyncSchedule: USBC -MD (0x00080020) and USBSTS (0x00001000) did not synchronize - -the following qemu command has worked flawlessly with Yosemite and Maverick. -qemu-system-x86_64 -enable-kvm -m 4096 -cpu core2duo -machine q35 \ --bios /usr/local/share/qemu/bios.bin \ --name "El Capitan" \ --mem-path /hugetlbfs \ --rtc base=utc,clock=vm,driftfix=slew \ --balloon none \ --parallel none \ --smp 4,sockets=1,cores=2,threads=2 \ --boot menu=on \ --usb -device usb-kbd -device usb-mouse \ --device usb-host,vendorid=0x0455,productid=0x0777 \ --vga std \ --monitor stdio \ --device isa-applesmc,osk="youknowwhatitis" \ --smbios type=2 \ --device ich9-intel-hda,bus=pcie.0,addr=1b.0,id=sound0 \ --device hda-duplex,id=sound0-codec0,bus=sound0.0,cad=0 \ --device e1000-82545em,netdev=hub0port0,id=mac_vnet0,mac=62:64:44:34:64:54 \ --netdev bridge,id=hub0port0,br=br0,helper=/usr/local/libexec/qemu-bridge-helper \ --device ide-drive,bus=ide.0,drive=elcapitan \ --drive id=elcapitan,format=qcow2,if=none,file=./iElCapitan.qcow2 - -If anything else I can do to debug the problem please let me know. \ No newline at end of file diff --git a/results/classifier/deepseek-2-tmp/output/device/1511887 b/results/classifier/deepseek-2-tmp/output/device/1511887 deleted file mode 100644 index 70478d92..00000000 --- a/results/classifier/deepseek-2-tmp/output/device/1511887 +++ /dev/null @@ -1,35 +0,0 @@ - -USB device 1.1 not correctly passedthru from Linux host to Windows guest - -I have USB Digital Oscilloscope which works great on pure Windows machine but not work on virtualized one. I tried passthru the device from my Debian Jessie (64bit) host machine to Windows 7 (32bit) guest machine but unfortunately it does not work very well. It looks that device is passed thru so Windows machine knows about new device and loads HID device driver for it but the device driver failed to start the device and details of an error provided by device manager is "This device cannot start" Code 10. - -Installed Qemu version: 2.1+dfsg-12+deb8u4 0 - -USB device spec: Dynon Instruments ELAB-080, USB 1.1 - -On linux host computer ---------------------------- -lsusb identify it as: -Bus 003 Device 009: ID 13a3:0001 - -lsusb -t identify it as: -/: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M - |__ Port 1: Dev 9, If 0, Class=Human Interface Device, Driver=usbhid, 12M - -This is how I started my Windows guest machine ------------------------------------------------------- -kvm -cpu host \ - -m 2048MiB \ - -hda test.vdi \ - -ctrl-grab \ - -parallel /dev/parport0 \ - -usbdevice host:13a3:0001 - -...also instead of last line I tried this one: - -device usb-host,vendorid=0x13a3,productid=0x0001 - -none of them help to properly handle my device inside guest machine. - -Only one time the Windows guest machine properly start the device so software for that oscilloscope can identify the Oscilloscope and measure for a while but unfortunately after I guess 5 seconds of measurement the device was disconnected from Windows and never start working again even after couple of restarts of guest machine even after plug and unplug it's USB cable and power cable. - -I searched for a solution or some clues to get it work but none of my searching over the internet was successful. Because device works on pure Windows but not work on virtualized one, I think there is a problem with handling not standard USB devices (like sticks, keyboards, mouses etc.) \ No newline at end of file diff --git a/results/classifier/deepseek-2-tmp/output/device/1518969 b/results/classifier/deepseek-2-tmp/output/device/1518969 deleted file mode 100644 index b1a630a1..00000000 --- a/results/classifier/deepseek-2-tmp/output/device/1518969 +++ /dev/null @@ -1,29 +0,0 @@ - -Instance of QEMU doesn't unplug virtio scsi disk after device_del and drive_del commands - -device_del and drive_del commands don't cause virtio disk detaching - -Steps to reproduce: -1. Run instance - -2. Attach virtio scsi disk - -3. Reboot instance - -4. Immediately after reboot detach disk with QEMU commands: -device_del -drive_del - -Expected result: -Disk should be detached anyway - -Actual: -Domain info contains attached disk even after waiting long period of time(5 min in my case). - -Additional info: -QEMU process: -root 29010 42.6 1.9 562036 61272 ? Rl 03:42 0:01 /usr/bin/qemu-system-x86_64 -name instance-00000069 -S -machine pc-i440fx-trusty,accel=tcg,usb=off -m 64 -realtime mlock=off -smp 1,sockets=1,cores=1,threads=1 -uuid d2418536-2547-4740-96b5-0d4f1d74b9f3 -smbios type=1,manufacturer=OpenStack Foundation,product=OpenStack Nova,version=13.0.0,serial=1fd8f69a-909b-4ed1-aae9-4fc9318fc622,uuid=d2418536-2547-4740-96b5-0d4f1d74b9f3,family=Virtual Machine -no-user-config -nodefaults -chardev socket,id=charmonitor,path=/var/lib/libvirt/qemu/instance-00000069.monitor,server,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=utc -no-shutdown -boot strict=on -kernel /opt/stack/data/nova/instances/d2418536-2547-4740-96b5-0d4f1d74b9f3/kernel -initrd /opt/stack/data/nova/instances/d2418536-2547-4740-96b5-0d4f1d74b9f3/ramdisk -append root=/dev/vda console=tty0 console=ttyS0 no_timer_check -device piix3-usb-uhci,id=usb,bus=pci.0,addr=0x1.0x2 -drive file=/opt/stack/data/nova/instances/d2418536-2547-4740-96b5-0d4f1d74b9f3/disk,if=none,id=drive-virtio-disk0,format=qcow2,cache=none -device virtio-blk-pci,scsi=off,bus=pci.0,addr=0x4,drive=drive-virtio-disk0,id=virtio-disk0,bootindex=1 -drive file=/opt/stack/data/nova/instances/d2418536-2547-4740-96b5-0d4f1d74b9f3/disk.config,if=none,id=drive-ide0-1-1,readonly=on,format=raw,cache=none -device ide-cd,bus=ide.1,unit=1,drive=drive-ide0-1-1,id=ide0-1-1 -netdev tap,fd=18,id=hostnet0 -device virtio-net-pci,netdev=hostnet0,id=net0,mac=fa:16:3e:1a:10:3d,bus=pci.0,addr=0x3 -chardev file,id=charserial0,path=/opt/stack/data/nova/instances/d2418536-2547-4740-96b5-0d4f1d74b9f3/console.log -device isa-serial,chardev=charserial0,id=serial0 -chardev pty,id=charserial1 -device isa-serial,chardev=charserial1,id=serial1 -vnc 127.0.0.1:1 -k en-us -device cirrus-vga,id=video0,bus=pci.0,addr=0x2 -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x5 - -QEMU version: -qemu-system-x86_64 --version -QEMU emulator version 2.0.0 (Debian 2.0.0+dfsg-2ubuntu1.19), Copyright (c) 2003-2008 Fabrice Bellard \ No newline at end of file diff --git a/results/classifier/deepseek-2-tmp/output/device/1519 b/results/classifier/deepseek-2-tmp/output/device/1519 deleted file mode 100644 index f5a8e2f9..00000000 --- a/results/classifier/deepseek-2-tmp/output/device/1519 +++ /dev/null @@ -1,13 +0,0 @@ - -audio recording not working on qemu -Description of problem: -QEMU fails to record audio from the guest even when the device options hda-duplex and hda-micro options are used. Tried using the other available audio backends (alsa and sdl) but recording on the guest still fails -Steps to reproduce: -1. run the qemu command line above with any of the available audio backends -2. record audio on the guest -3. arecord -vv -d 5 recordng.wav -4. there's an attempt to record but it hangs -5. play recorded audio, there's no output -6. aplay recordng.wav -Additional information: - diff --git a/results/classifier/deepseek-2-tmp/output/device/1521 b/results/classifier/deepseek-2-tmp/output/device/1521 deleted file mode 100644 index bb83f38e..00000000 --- a/results/classifier/deepseek-2-tmp/output/device/1521 +++ /dev/null @@ -1,2 +0,0 @@ - -USB HID not using the keycodemapdb and thus lacking new entries diff --git a/results/classifier/deepseek-2-tmp/output/device/1522 b/results/classifier/deepseek-2-tmp/output/device/1522 deleted file mode 100644 index 94003634..00000000 --- a/results/classifier/deepseek-2-tmp/output/device/1522 +++ /dev/null @@ -1,41 +0,0 @@ - -Floppy controller returns the wrong thing for multitrack reads which span tracks -Description of problem: -I've just discovered that the Minix 1 and 2 operating systems no longer boot on qemu. - -Investigation reveals the following: - -- when Minix reads a 1024-byte block from disk, it issues a two-sector multitrack read to the FDC. -- if the FDC runs out of sectors when it's on head 0, it automatically switches to head 1 (this is correct). -- if the FDC runs out of sectors when it's on head 1, it stops the transfer (which is what is supposed to happen). - -What qemu does for the latter case is that it will automatically seek to the next track and switch to head 0. It then sets the SEEK COMPLETE bit in the status register. Minix sees this but isn't expecting it, because this shouldn't be emitted for reads and writes, and fails thinking it's an error. - -For example, here's the logging for such a transfer: - -``` -FLOPPY: Start transfer at 0 1 4f 11 (2878) -FLOPPY: direction=1 (1024 - 10240) -FLOPPY: copy 512 bytes (1024 0 10240) 0 pos 1 4f (17-0x00000b3e 0x00167c00) -FLOPPY: seek to next sector (1 4f 11 => 2878) <--- reads the last sector of head 1 track 0x4f -FLOPPY: copy 512 bytes (1024 512 10240) 0 pos 1 4f (18-0x00000b3f 0x00167e00) -FLOPPY: seek to next sector (1 4f 12 => 2879) <--- attempt to move to the next sector, which fails -FLOPPY: seek to next track (0 50 01 => 2879) <--- moved to next track, which shouldn't happen -FLOPPY: end transfer 1024 1024 10240 -FLOPPY: transfer status: 00 00 00 (20) <--- status report -``` - -Transfer status 20 is the SEEK COMPLETE bit. For a normal head switch, that should be 04 (with the NOW ON HEAD 1 bit set). - -For reference, see page 5-13 of the uPD765 datasheet here: https://www.cpcwiki.eu/imgs/f/f3/UPD765_Datasheet_OCRed.pdf It says: - -> IF MT is high, a multitrack operation is performed. -> If MT = 1 after finishing read/write operation on side 0, -> FDC will automatically start command searching for sector -> 1 on side 1 -Steps to reproduce: -1. `qemu-system-i386 --fda images/minix-2.0-root-720kB.img` -2. Press = to boot. -3. Observe the 'Unrecoverable Read` errors as the ramdisk is loaded. (The system will still boot, but will then crash if you try to do anything due to a corrupt ramdisk.) - -[minix-2.0-root-720kB.img.bz2](/uploads/77d34db96f353d92cdb2d01928b8fc01/minix-2.0-root-720kB.img.bz2) diff --git a/results/classifier/deepseek-2-tmp/output/device/1523246 b/results/classifier/deepseek-2-tmp/output/device/1523246 deleted file mode 100644 index 0918f4fd..00000000 --- a/results/classifier/deepseek-2-tmp/output/device/1523246 +++ /dev/null @@ -1,16 +0,0 @@ - -Virtio-blk does not support TRIM - -When model=virtio is used, TRIM is not supported. - -# mount -o discard /dev/vda4 /mnt -# mount | tail -1 -/dev/vda4 on /mnt type fuseblk (rw,nosuid,nodev,relatime,user_id=0,group_id=0,allow_other,blksize=4096) -# fstrim /mnt/ -fstrim: /mnt/: the discard operation is not supported - -Booting without model=virtio allows using TRIM (in Windows as well). - -Full QEMU line: - -qemu-system-x86_64 -enable-kvm -cpu host -bios /usr/share/ovmf/ovmf_x64.bin -smp 2 -m 7G -vga qxl -usbdevice tablet -net nic,model=virtio -net user -drive discard=unmap,detect-zeroes=unmap,cache=none,file=vms/win10.hd.img.vmdk,format=vmdk,if=virtio \ No newline at end of file diff --git a/results/classifier/deepseek-2-tmp/output/device/1526 b/results/classifier/deepseek-2-tmp/output/device/1526 deleted file mode 100644 index fd608d38..00000000 --- a/results/classifier/deepseek-2-tmp/output/device/1526 +++ /dev/null @@ -1,2 +0,0 @@ - -hw/vfio/trace-events incorrect format diff --git a/results/classifier/deepseek-2-tmp/output/device/1529449 b/results/classifier/deepseek-2-tmp/output/device/1529449 deleted file mode 100644 index 78dd37ea..00000000 --- a/results/classifier/deepseek-2-tmp/output/device/1529449 +++ /dev/null @@ -1,4 +0,0 @@ - -serial is required for -device nvme - -I am not exactly sure if this is a bug, but I don't see why the option "serial" is required for -device nvme like drive. Truth is it seem to accept random string as its value anyway, if that's the case, couldn't qemu just generate one for it when it's not specified? \ No newline at end of file diff --git a/results/classifier/deepseek-2-tmp/output/device/1529859 b/results/classifier/deepseek-2-tmp/output/device/1529859 deleted file mode 100644 index 38d0dea0..00000000 --- a/results/classifier/deepseek-2-tmp/output/device/1529859 +++ /dev/null @@ -1,49 +0,0 @@ - -qemu 2.5.0 ivshmem segfault with msi=off option - -Launching qemu with "-device ivshmem,chardev=ivshmemid,msi=off -chardev socket,path=/tmp/ivshmem_socket,id=ivshmemid" - -Causes segfault because, s->msi_vectors is not initialized and s->msi_vectors == 0. - -Does ivshmem exactly need this line ? : - -s->msi_vectors[vector].pdev = pdev; - -It makes no sence for me. - -Subject: [PATCH] fixed ivshmem empty msi vector on msi=off segfault - ---- - hw/misc/ivshmem.c | 9 ++++----- - 1 file changed, 4 insertions(+), 5 deletions(-) - -diff --git a/hw/misc/ivshmem.c b/hw/misc/ivshmem.c -index f73f0c2..2087d5e 100644 ---- a/hw/misc/ivshmem.c -+++ b/hw/misc/ivshmem.c -@@ -359,8 +359,6 @@ static CharDriverState* create_eventfd_chr_device(void * opaque, EventNotifier * - int eventfd = event_notifier_get_fd(n); - CharDriverState *chr; - -- s->msi_vectors[vector].pdev = pdev; -- - chr = qemu_chr_open_eventfd(eventfd); - - if (chr == NULL) { -@@ -1038,10 +1036,11 @@ static void pci_ivshmem_exit(PCIDevice *dev) - } - - if (ivshmem_has_feature(s, IVSHMEM_MSI)) { -- msix_uninit_exclusive_bar(dev); -+ msix_uninit_exclusive_bar(dev); - } -- -- g_free(s->msi_vectors); -+ -+ if(s->msi_vectors) -+ g_free(s->msi_vectors); - } - - static bool test_msix(void *opaque, int version_id) --- -2.3.6 \ No newline at end of file diff --git a/results/classifier/deepseek-2-tmp/output/device/1530035 b/results/classifier/deepseek-2-tmp/output/device/1530035 deleted file mode 100644 index 785ce5ee..00000000 --- a/results/classifier/deepseek-2-tmp/output/device/1530035 +++ /dev/null @@ -1,24 +0,0 @@ - -usb-host: ATI Technologies, Inc. TV Wonder acts as a different device if used - -Title says it all. If you try to use the "ATI Technologies, Inc. TV Wonder" USB 1.1 TV Tuner for passthrough under any OS that has drivers for the device, the usb-host driver will confuse itself and give the device a new PID number for Linux. - -Tested on ReactOS and Windows XP with stable QEMU package from pacman on Arch Linux. - -Commands used: sudo qemu-system-x86_64 -enable-kvm -hda ~/QEMU/hd/winxp.img -usb -device usb-host,hostbus=2,hostaddr=3 -vga vmware - -Before starting qemu-kvm, lsusb reports: -[ -Bus 002 Device 003: ID 0528:7561 ATI Technologies, Inc. TV Wonder -] - -After starting qemu-kvm, usb-host and lsusb report: -[ -libusb: error [_get_usbfs_fd] File doesn't exist, wait 10 ms and try again -libusb: error [_get_usbfs_fd] libusb couldn't open USB device /dev/bus/usb/002/003: No such file or directory - -The device in Bus 2, Device 3 is gone and it appears as this instead: -Bus 002 Device 005: ID 0573:0400 Zoran Co. Personal Media Division (Nogatech) D-Link V100 -] - -This weird effect only lasts until you unplug the TV Wonder. \ No newline at end of file diff --git a/results/classifier/deepseek-2-tmp/output/device/1530278 b/results/classifier/deepseek-2-tmp/output/device/1530278 deleted file mode 100644 index 3b2fce91..00000000 --- a/results/classifier/deepseek-2-tmp/output/device/1530278 +++ /dev/null @@ -1,13 +0,0 @@ - -vhost-user: can not detach chardev which is used by vhost-user backend - -I launch a VM which use vhost-user netdevice as follows.When detach the netdevice in qemu monitor, the chardevice which used by the netdevice also should be deatched.The netdevice can be detached sucessfully.But the chardevice failed when it was being detaching. -Full command line : -qemu-system-x86_64 \ --cpu host -boot c -hda /home/lining/ubuntu_12_04.img -snapshot -m 2048 -smp 2 \ ---enable-kvm -name "client1" -vnc :1 \ --object memory-backend-file,id=mem,size=2048M,mem-path=/dev/hugepages,share=on -numa node,memdev=mem \ --chardev socket,id=chr1,path=/opt/network/ovdk/bin/vhost-user \ --netdev vhost-user,id=net12,chardev=chr1,ifname=port80, vhostforce \ --device virtio-net-pci,netdev=net12,mac=00:00:00:00:00:01,\ -csum=off,gso=off,guest_tso4=off,guest_tso6=off,guest_ecn=off,guest_ufo=off,any_layout=off \ No newline at end of file diff --git a/results/classifier/deepseek-2-tmp/output/device/1543057 b/results/classifier/deepseek-2-tmp/output/device/1543057 deleted file mode 100644 index 1ac4a892..00000000 --- a/results/classifier/deepseek-2-tmp/output/device/1543057 +++ /dev/null @@ -1,17 +0,0 @@ - -Warnings are treated as errors - -System: Ubuntu 14.04, 32bit -Kernel: 3.13.0-55-generic -Qemu: v. 2.2.50 - -Error msg: - -hw/acpi/pcihp.c: In function ‘acpi_pcihp_pc_no_hotplug’: -hw/acpi/pcihp.c:117:34: error: ‘PCIDevice’ has no member named ‘qdev’ - return (pc->is_bridge && !dev->qdev.hotplugged) || !dc->hotpluggable; - ^ -hw/acpi/pcihp.c:118:1: error: control reaches end of non-void function [-Werror=return-type] - } - ^ -cc1: all warnings being treated as errors \ No newline at end of file diff --git a/results/classifier/deepseek-2-tmp/output/device/1544524 b/results/classifier/deepseek-2-tmp/output/device/1544524 deleted file mode 100644 index 5166298a..00000000 --- a/results/classifier/deepseek-2-tmp/output/device/1544524 +++ /dev/null @@ -1,23 +0,0 @@ - -"info chardev" not showing the real port in use - -With Qemu 2.1.2 -============== -pharidos@uks2:~/work/tplaf/☸ qemu-system-x86_64 -hda /space/pharidos/Disks/Blank_disk.qcow2 -serial telnet::0,server,nowait -nographic -QEMU 2.1.2 monitor - type 'help' for more information -(qemu) info chardev -parallel0: filename=null -serial0: filename=telnet:0.0.0.0:44189,server <====<<< serial console is using port 44189 -compat_monitor0: filename=stdio -(qemu) - - -With Qemu 2.5.0 -============== -pharidos@kvm:~/$ qemu-system-x86_64 -hda /space/pharidos/Disks/Blank_disk.qcow2 -serial telnet::0,server,nowait -nographic -QEMU 2.5.0 monitor - type 'help' for more information -(qemu) info chardev -parallel0: filename=null -serial0: filename=disconnected:telnet::0,server <====<<< serial console port not shown -compat_monitor0: filename=stdio -(qemu) \ No newline at end of file diff --git a/results/classifier/deepseek-2-tmp/output/device/1550743 b/results/classifier/deepseek-2-tmp/output/device/1550743 deleted file mode 100644 index c2d819b4..00000000 --- a/results/classifier/deepseek-2-tmp/output/device/1550743 +++ /dev/null @@ -1,27 +0,0 @@ - -connect low speed host devices to qemu ehci does not work - -$ qemu-system-i386 -hda my_x86.img -device ich9-usb-ehci1,id=ehci -device usb-host,vendorid=0x045e,productid=0x071d -serial stdio -qemu-system-i386: Warning: speed mismatch trying to attach usb device "Microsoft? 2.4GHz Transceiver V" ( speed) to bus "ehci.0", port "1" (high speed) -qemu-system-i386: Warning: speed mismatch trying to attach usb device "Microsoft? 2.4GHz Transceiver V" ( speed) to bus "ehci.0", port "1" (high speed) -qemu-system-i386: Warning: speed mismatch trying to attach usb device "Microsoft? 2.4GHz Transceiver V" ( speed) to bus "ehci.0", port "1" (high speed) - -Which is obviously wrong. The ehci specification states: - -Low-speed device, release ownership of port <= Table 2-16. - -Table 2-6: - -Number of Companion Controller (N_CC). This field indicates the number of -companion controllers associated with this USB 2.0 host controller. -A zero in this field indicates there are no companion host controllers. Port-ownership -hand-off is not supported. Only high-speed devices are supported on the host controller -root ports. -A value larger than zero in this field indicates there are companion USB 1.1 host -controller(s). Port-ownership hand-offs are supported. High, Full- and Low-speed -devices are supported on the host controller root ports. - -Which is not longer true, as for example skylake and baytrail offers a dual usb stack of ehci and xhci. In that case, EHCI handles the low speed device as well. - -brgds, -Bert \ No newline at end of file diff --git a/results/classifier/deepseek-2-tmp/output/device/1563 b/results/classifier/deepseek-2-tmp/output/device/1563 deleted file mode 100644 index d6b8bee8..00000000 --- a/results/classifier/deepseek-2-tmp/output/device/1563 +++ /dev/null @@ -1,4 +0,0 @@ - -lsi53c895a: DMA reentrancy issue leads to stack overflow (CVE-2023-0330) -Description of problem: -See https://bugzilla.redhat.com/show_bug.cgi?id=2160151. diff --git a/results/classifier/deepseek-2-tmp/output/device/1568621 b/results/classifier/deepseek-2-tmp/output/device/1568621 deleted file mode 100644 index 7b96ff35..00000000 --- a/results/classifier/deepseek-2-tmp/output/device/1568621 +++ /dev/null @@ -1,19 +0,0 @@ - -input-linux misdetects Logitech keyboard as a mouse - -The new input-linux.c code misdetects my Logitech K350 keyboard as a mouse. The bug is in the input_linux_complete function. The evdev for this keyboard returns an "evtmap" with the EV_REL bit set. Full evtmap is 0x0012001F. Using a different keyboard everything works as intended, so my configuration and setup are correct otherwise. - - -Suggestion: - -I suggest adding an object property called something like "type" where the user can specify what the device type is manually. This K350 keyboard shows that "evtmap" cannot be used to reliably detect the device type. Since specifying the device type manually is not an undue burden, perhaps it should be a required option and there should be no autodetection? - - -System: - -Arch linux, using qemu-git AUR package installed 20160409. - - -Command line: - -LC_ALL=C PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin QEMU_AUDIO_DRV=none /usr/sbin/qemu-system-x86_64 -name win10,debug-threads=on -S -machine pc-i440fx-2.4,accel=kvm,usb=off,vmport=off -cpu host,kvm=off -drive file=/usr/share/edk2.git/ovmf-x64/OVMF_CODE-pure-efi.fd,if=pflash,format=raw,unit=0,readonly=on -drive file=/var/lib/libvirt/qemu/nvram/win10_VARS.fd,if=pflash,format=raw,unit=1 -m 8196 -realtime mlock=off -smp 8,sockets=1,cores=4,threads=2 -uuid 58623778-9d9d-4d30-8ec0-b37e12a30fdc -nographic -no-user-config -nodefaults -chardev socket,id=charmonitor,path=/var/lib/libvirt/qemu/domain-17-win10/monitor.sock,server,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=localtime,driftfix=slew -global kvm-pit.lost_tick_policy=discard -no-hpet -no-shutdown -global PIIX4_PM.disable_s3=1 -global PIIX4_PM.disable_s4=1 -boot strict=on -device ich9-usb-ehci1,id=usb,bus=pci.0,addr=0x6.0x7 -device ich9-usb-uhci1,masterbus=usb.0,firstport=0,bus=pci.0,multifunction=on,addr=0x6 -device ich9-usb-uhci2,masterbus=usb.0,firstport=2,bus=pci.0,addr=0x6.0x1 -device ich9-usb-uhci3,masterbus=usb.0,firstport=4,bus=pci.0,addr=0x6.0x2 -drive file=/var/lib/libvirt/images/ISOs/Win10_1511_English_x64.iso,format=raw,if=none,id=drive-ide0-0-1,readonly=on -device ide-cd,bus=ide.0,unit=1,drive=drive-ide0-0-1,id=ide0-0-1 -drive file=/var/lib/libvirt/images/ISOs/virtio-win-0.1.112.iso,format=raw,if=none,id=drive-ide0-1-0,readonly=on -device ide-cd,bus=ide.1,unit=0,drive=drive-ide0-1-0,id=ide0-1-0 -drive file=/dev/sda,format=raw,if=none,id=drive-virtio-disk1 -device virtio-blk-pci,scsi=off,bus=pci.0,addr=0x8,drive=drive-virtio-disk1,id=virtio-disk1,bootindex=1 -netdev tap,fd=26,id=hostnet0 -device rtl8139,netdev=hostnet0,id=net0,mac=52:54:00:70:8a:db,bus=pci.0,addr=0x3 -netdev tap,fd=28,id=hostnet1 -device rtl8139,netdev=hostnet1,id=net1,mac=d4:be:d9:56:2e:35,bus=pci.0,addr=0x9 -device intel-hda,id=sound0,bus=pci.0,addr=0x4 -device hda-duplex,id=sound0-codec0,bus=sound0.0,cad=0 -device vfio-pci,host=04:00.0,id=hostdev0,bus=pci.0,addr=0x2 -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x7 -object input-linux,id=kbd1,evdev=/dev/input/event19,grab_all=on -object input-linux,id=kbb2,evdev=/dev/input/event2 -msg timestamp=on \ No newline at end of file diff --git a/results/classifier/deepseek-2-tmp/output/device/1569 b/results/classifier/deepseek-2-tmp/output/device/1569 deleted file mode 100644 index 4cbcf1bb..00000000 --- a/results/classifier/deepseek-2-tmp/output/device/1569 +++ /dev/null @@ -1,28 +0,0 @@ - -NVMe FS operations hang after suspending and resuming both guest and host -Description of problem: -Hello and thank you for your work on QEMU! - -Using the NVMe driver with my Seagate FireCuda 530 2TB M.2 works fine until I encounter this problem, which is reliably reproducible for me. - -When I suspend the guest and then suspend (s2idle) my host all is well until I resume the guest (manually with `virsh dompmwakeup $VMNAME`, after the host has resumed). Although the guest resumes and is interactive, it seems that anything involving filesystem operations hang forever and do not return. - -Suspending and resuming the Linux guest seems to work perfectly if I don't suspend/resume the host. - -Ultimately what I'm wanting to do is share the drive between VMs with qemu-storage-daemon. I can reproduce the problem in that scenario in much the same way. Using PCI passthrough with the same VM and device works fine and doesn't exhibit this problem. - -Hopefully that's clear enough - let me know if there's anything else I can provide. -Steps to reproduce: -1. Create a VM with a dedicated NVMe disk. -2. Boot an ISO and install to the disk. -3. Verify that suspend and resume works when not suspending the host. -4. Suspend the guest. -5. Suspend the host. -6. Wake the host. -7. Wake the guest. -8. Try just about anything that isn't likely already cached somewhere: `du -s /etc`. -Additional information: -I've attached the libvirt domain XML[1] and libvirtd debug logs for QEMU[2] ("1:qemu") that covers suspending the guest & host, resuming host & guest and doing something to cause a hang. I tried to leave enough time afterwards for any timeout to occur. - -1. [nvme-voidlinux.xml](/uploads/1dea47af096ce58175f7aa526eca455e/nvme-voidlinux.xml) -2. [nvme-qemu-debug.log](/uploads/42d3bed456a795069023a61d38fa5ccd/nvme-qemu-debug.log) diff --git a/results/classifier/deepseek-2-tmp/output/device/157 b/results/classifier/deepseek-2-tmp/output/device/157 deleted file mode 100644 index 0031d62b..00000000 --- a/results/classifier/deepseek-2-tmp/output/device/157 +++ /dev/null @@ -1,2 +0,0 @@ - -Xbox One controller USB passthrough disconnections and stops diff --git a/results/classifier/deepseek-2-tmp/output/device/1572959 b/results/classifier/deepseek-2-tmp/output/device/1572959 deleted file mode 100644 index 284e7470..00000000 --- a/results/classifier/deepseek-2-tmp/output/device/1572959 +++ /dev/null @@ -1,8 +0,0 @@ - -bcm2835_property: inconsistent values when both setting and querying the framebuffer - -As the framebuffer settings are copied into the result message before it is reconfigured, inconsistent behavior can happen when, for instance, you set with a single message the width, height, and depth, and ask at the same time to allocate the buffer and get the pitch and the size. - -In this case, the reported pitch and size would be incorrect as they were computed with the initial values of width, height and depth, not the ones the client requested. - -Attached is a patch also sent to the qemu-devel mailing list. \ No newline at end of file diff --git a/results/classifier/deepseek-2-tmp/output/device/1575561 b/results/classifier/deepseek-2-tmp/output/device/1575561 deleted file mode 100644 index a2b9c2ac..00000000 --- a/results/classifier/deepseek-2-tmp/output/device/1575561 +++ /dev/null @@ -1,7 +0,0 @@ - -config qemu virtio_queue_size to 1024，create vm boot from network failed - -config qemu virtio_queue_size to 1024，create vm boot from network failed。 -in the vm vncviewer，see the error log： -“ERROR queue size 1024 > 256 -could not open net0: no such file or directory" \ No newline at end of file diff --git a/results/classifier/deepseek-2-tmp/output/device/1576 b/results/classifier/deepseek-2-tmp/output/device/1576 deleted file mode 100644 index 831118dc..00000000 --- a/results/classifier/deepseek-2-tmp/output/device/1576 +++ /dev/null @@ -1,29 +0,0 @@ - -Migration from v8.0.0-rc2 to v7.2.0 with pcie-root-port device fails -Description of problem: -Loading the VM state fails with: -``` -qemu-system-x86_64: get_pci_config_device: Bad config data: i=0x10a read: 40 device: 0 cmask: ff wmask: 0 w1cmask:0 -qemu-system-x86_64: Failed to load PCIDevice:config -qemu-system-x86_64: Failed to load pcie-root-port:parent_obj.parent_obj.parent_obj -qemu-system-x86_64: error while loading state for instance 0x0 of device '0000:00:1c.0/pcie-root-port' -qemu-system-x86_64: Error -22 while loading VM state -``` -Steps to reproduce: -Used the following script with the first argument being a build directory of v8.0.0-rc2 and the second a build directory of v7.2.0 -``` -#!/bin/bash -rm /tmp/disk.qcow2 -args=" - -device pcie-root-port,multifunction=on,bus=pcie.0,addr=1c.0,port=1,chassis=1 - -machine type=pc-q35-7.2" -$1/qemu-img create -f qcow2 /tmp/disk.qcow2 1G -$1/qemu-system-x86_64 --qmp stdio --blockdev qcow2,node-name=node0,file.driver=file,file.filename=/tmp/disk.qcow2 $args <sg_vpd -i PD1 -Device Identification VPD page: - Addressed logical unit: - designator type: SCSI name string, code set: UTF-8 - SCSI name string: - 8086QEMU NVMe Ctrl 00012BDAC262CF831698 - -C:\Windows\system32>sg_vpd -p sn PD1 -Unit serial number VPD page: - Unit serial number: 0000_0000_0000_0000." \ No newline at end of file diff --git a/results/classifier/deepseek-2-tmp/output/device/1577 b/results/classifier/deepseek-2-tmp/output/device/1577 deleted file mode 100644 index 5bad6187..00000000 --- a/results/classifier/deepseek-2-tmp/output/device/1577 +++ /dev/null @@ -1,85 +0,0 @@ - -device_del return is already in the process of unplug frequently -Description of problem: -recently we update qemu 6.1.1 to qemu 7.1.0, and run into an issue with the following error: - -command '{ "execute": "device_del", "arguments": { "id": "virtio-diskX" } }' for VM "id" failed ({ "return": {"class": "GenericError", "desc": "Device virtio-diskX is already in the process of unplug"} }). - -The issue is reproducible. With a few seconds delay before hot-unplug, hot-unplug just works fine. - -After a few digging, we found that the commit 9323f892b39 may incur the issue. ------------------- - failover: fix unplug pending detection - - Failover needs to detect the end of the PCI unplug to start migration - after the VFIO card has been unplugged. - - To do that, a flag is set in pcie_cap_slot_unplug_request_cb() and reset in - pcie_unplug_device(). - - But since - 17858a169508 ("hw/acpi/ich9: Set ACPI PCI hot-plug as default on Q35") - we have switched to ACPI unplug and these functions are not called anymore - and the flag not set. So failover migration is not able to detect if card - is really unplugged and acts as it's done as soon as it's started. So it - doesn't wait the end of the unplug to start the migration. We don't see any - problem when we test that because ACPI unplug is faster than PCIe native - hotplug and when the migration really starts the unplug operation is - already done. - - See c000a9bd06ea ("pci: mark device having guest unplug request pending") - a99c4da9fc2a ("pci: mark devices partially unplugged") - - Signed-off-by: Laurent Vivier - Reviewed-by: Ani Sinha - Message-Id: <20211118133225.324937-4-lvivier@redhat.com> - Reviewed-by: Michael S. Tsirkin - Signed-off-by: Michael S. Tsirkin ------------------- -The purpose is for detecting the end of the PCI device hot-unplug. However, we feel the error confusing. How is it possible that a disk "is already in the process of unplug" during the first hot-unplug attempt? So far as I know, the issue was also encountered by libvirt, but they simply ignored it: - - https://bugzilla.redhat.com/show_bug.cgi?id=1878659 - -Hence, a question is: should we have the line below in acpi_pcihp_device_unplug_request_cb()? - - pdev->qdev.pending_deleted_event = true; - -It would be great if you as the author could give us a few hints. - -Thank you very much for your reply! - -Sincerely, - -Yu Zhang @ Compute Platform IONOS - - -The issue is reproducible in our own stack, which is not quite easy to describe in a few command lines. We simplified it a bit by a script instead. Although it's not able to reproduce, it could be somewhat helpful to understand the issue. - -``` -#!/bin/bash - -HOME=~ -QEMU=$HOME/qemu/bin/qemu-system-x86_64 -DISK1=$HOME/img/disk1.qcow2 -DISK4=$HOME/img/disk4.qcow2 -DISK5=$HOME/img/disk5.qcow2 - -$QEMU \ - -cpu host -enable-kvm -m 2048 -smp 2 \ - -object iothread,id=iothread1 \ - -drive file=$DISK1,if=none,id=drive-virtio-disk1,format=qcow2,snapshot=off,discard=on,cache=none \ - -device virtio-blk-pci,bus=pci.0,addr=0x4,drive=drive-virtio-disk1,iothread=iothread1,num-queues=1,discard=on,id=virtio-disk1 \ - -object iothread,id=iothread4 \ - -drive file=$DISK4,if=none,id=drive-virtio-disk4,format=qcow2,snapshot=off,discard=on,cache=none \ - -device virtio-blk-pci,bus=pci.0,addr=0x5,drive=drive-virtio-disk4,iothread=iothread4,num-queues=1,discard=on,id=virtio-disk4 \ - -object iothread,id=iothread5 \ - -drive file=$DISK5,if=none,id=drive-virtio-disk5,format=qcow2,snapshot=off,discard=on,cache=none \ - -device virtio-blk-pci,bus=pci.0,addr=0x6,drive=drive-virtio-disk5,iothread=iothread5,num-queues=1,discard=on,id=virtio-disk5 \ - -qmp unix:./qmp-sock,server,nowait & - -sleep 5 - -echo '{"execute":"qmp_capabilities"}{"execute": "device_del","arguments": { "id": "virtio-disk5"}}{"execute": "query-block"}' | nc -U -w 1 ./qmp-sock -echo '{"execute":"qmp_capabilities"}{"execute": "device_del","arguments": { "id": "virtio-disk5"}}{"execute": "query-block"}' | nc -U -w 1 ./qmp-sock``` -Additional information: -Possible workaround: https://lore.kernel.org/qemu-devel/20230403131833-mutt-send-email-mst@kernel.org/T/#t diff --git a/results/classifier/deepseek-2-tmp/output/device/1579306 b/results/classifier/deepseek-2-tmp/output/device/1579306 deleted file mode 100644 index f362925f..00000000 --- a/results/classifier/deepseek-2-tmp/output/device/1579306 +++ /dev/null @@ -1,15 +0,0 @@ - -usb-uas does not work in Windows (10) guest - -When I attach a "-device usb-uas" to a VM with Windows 10 10586, the device fail to start with the following error in the guest: - -"The device cannot start. (Code 10) - -{Operation Failed} -The requested operation was unsuccessful" - -If the host controller is nec-usb-xhci, there will be two of the following error on the terminal of the host as well: - -"qemu-system-x86_64: usb_uas_handle_control: unhandled control request" - -If it's usb-ehci, ich9-usb-ehci1 or ich9-usb-echi2, this will not show up on the host side, but the device stil fails with the same error on the guest side. \ No newline at end of file diff --git a/results/classifier/deepseek-2-tmp/output/device/1579645 b/results/classifier/deepseek-2-tmp/output/device/1579645 deleted file mode 100644 index 225cee38..00000000 --- a/results/classifier/deepseek-2-tmp/output/device/1579645 +++ /dev/null @@ -1,13 +0,0 @@ - - [XEN/KVM] pch audio doesn't work on both Windows and linux guest with soundhw="ac97" - -Environment: - -when try to boot a guest by qemu with parameter "-soundhw ac97", it showed like below: -"audio: Could no init “oss” audio driver.", -then login the guest and try run audio, no sound output. -Reproduce: -1. kvm: qemu-system-x86_64 -enable-kvm -m 2048 -smp 4 -net nic,model=rtl8139 -net tap,script=/etc/kvm/qemu-ifup -soundhw ac97 -hda [target.img] - xen: add the audio device in guest configure file by soundhw="ac97", xl create $guest-configure -2. it will show "audio: Could no init “oss” audio driver". -3. login in guest, it can detect audio device, but actually it is not working. \ No newline at end of file diff --git a/results/classifier/deepseek-2-tmp/output/device/158 b/results/classifier/deepseek-2-tmp/output/device/158 deleted file mode 100644 index ea354971..00000000 --- a/results/classifier/deepseek-2-tmp/output/device/158 +++ /dev/null @@ -1,2 +0,0 @@ - -qemu system emulator crashed when using xhci usb controller diff --git a/results/classifier/deepseek-2-tmp/output/device/1580459 b/results/classifier/deepseek-2-tmp/output/device/1580459 deleted file mode 100644 index b1b3dccf..00000000 --- a/results/classifier/deepseek-2-tmp/output/device/1580459 +++ /dev/null @@ -1,16 +0,0 @@ - -Windows (10?) guest freezes entire host on shutdown if using PCI passthrough - -Problem: after leaving a Windows VM that uses PCI passthrough (as we do for gaming graphics cards, sound cards, and in my case, a USB card) running for some amount of time between 1 and 2 hours (it's not consistent with exactly how long), and for any amount of time longer than that, shutting down that guest will, right as it finishes shutting down, freeze the host computer, making it require a hard reboot. Unbinding (or in the other user's case, unbinding and THEN binding) any PCI device in sysfs, even one that has nothing to do with the VM, also has the same effect as shutting down the VM (if the VM has been running long enough). So, it's probably an issue related to unbinding and binding PCI devices. - -There's a lot of info on this problem over at https://bbs.archlinux.org/viewtopic.php?id=206050 -Here's a better-organized list of main details: --at least 2 confirmed victims of this bug; 2 (including me) have provided lots of info in the link --I'm on Arch Linux and the other one is on Gentoo (distro-nonspecific) --issue affects my Windows 10 guest and others' Windows guests, but not my Arch Linux guest (the others don't have non-Windows guests to test) --I'm using libvirt but the other user is not, so it's not an issue with libvirt --It seems to be version non-specific, too. I first noticed it at, or when testing versions still had the issue at (whichever version is lower), Linux 4.1 and qemu 2.4.0. It still persists in all releases of both since, including the newest ones. --I can't track down exactly what package downgrade can fix it, as downgrading further than Linux 4.1 and qemu 2.4.0 requires Herculean and system-destroying changes such as downgrading ncurses, meaning I don't know whether it's a bug in QEMU, the Linux kernel, or some weird seemingly unrelated thing. --According to the other user, "graphics intensive gameplay (GTA V) can cause the crash to happen sooner," as soon as "15 minutes" --Also, "bringing up a second passthrough VM with separate hardware will cause the same crash," and "bringing up another VM before the two-hour mark will not result in a crash," further cementing that it's triggered by the un/binding of PCI devices. --This is NOT related to the very similar bug that can be worked around by not passing through the HDMI device or sound card. Even when we removed all traces of any sort of sound card from the VM, it still had the same behavior. \ No newline at end of file diff --git a/results/classifier/deepseek-2-tmp/output/device/1580586 b/results/classifier/deepseek-2-tmp/output/device/1580586 deleted file mode 100644 index 9ee90a15..00000000 --- a/results/classifier/deepseek-2-tmp/output/device/1580586 +++ /dev/null @@ -1,10 +0,0 @@ - -Qemu WinXP SP3 second loadvm freezes Guest OS - -Using Qemu-system-i386 to run WinXP SP3 with the following command line: - -qemu-system-i386 -hda qcow2/windowsxp_32bits_dd.qcow2 -m 1024 -net user,smb=/shared -vga std -net nic,model=rtl8139 -rtc base=localtime,clock=vm -s -snapshot - -savevm works fine, and the first loadvm to the snapshot works properly, but the next ones will all freeze the guest OS. - -First I thought it was due to the clock but adding the rtc options did not fix it. \ No newline at end of file diff --git a/results/classifier/deepseek-2-tmp/output/device/1581308 b/results/classifier/deepseek-2-tmp/output/device/1581308 deleted file mode 100644 index 7fd95c23..00000000 --- a/results/classifier/deepseek-2-tmp/output/device/1581308 +++ /dev/null @@ -1,17 +0,0 @@ - -ohci doesn't check the 'num-ports' property - -command: -qemu-system-x86_64 -m 1024 -enable-kvm /root/centos6.img -enable-kvm -device pci-ohci,num-ports=100,masterbus=1 - -The ohci doesn't check the 'num-ports' property and would case an out-of-bands write,crash the qemu process. - - ohci->num_ports = num_ports; - if (masterbus) { - USBPort *ports[OHCI_MAX_PORTS]; - for(i = 0; i < num_ports; i++) { - ports[i] = &ohci->rhport[i].port; - } - -The version of qemu is 2.6.0 release from -http://wiki.qemu-project.org/download/qemu-2.6.0.tar.bz2 \ No newline at end of file diff --git a/results/classifier/deepseek-2-tmp/output/device/1583 b/results/classifier/deepseek-2-tmp/output/device/1583 deleted file mode 100644 index 02675e09..00000000 --- a/results/classifier/deepseek-2-tmp/output/device/1583 +++ /dev/null @@ -1,20 +0,0 @@ - -SGX Device mapping is not listed into QEMU KVM -Description of problem: -I want to run SGX into QEMU VM, the vm is up and running but SGX device mappings are not listed there. I also looked in dmesg | grep sgx and it returned "There are zero epc section" - -I have upgraded the libvirt to 8.6.0 because of below issue -https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1982896 - -I tried with libvirt-8.0.0 but it did not help - -I have attached the xml, please let me know why sgx mappings are not showing inside VM -Steps to reproduce: -1. Create a Ubuntu 20.04 VM with SGX mapping -Additional information: -Please let me know if any other logs are required - - - - -[ubuntu20.04.xml](/uploads/2609abc31db08e04cc3e3dbf923cd8d7/ubuntu20.04.xml) diff --git a/results/classifier/deepseek-2-tmp/output/device/1583421 b/results/classifier/deepseek-2-tmp/output/device/1583421 deleted file mode 100644 index 152ea168..00000000 --- a/results/classifier/deepseek-2-tmp/output/device/1583421 +++ /dev/null @@ -1,8 +0,0 @@ - -Please provide an option to print the default hardware configuration as command-line options, to make -nodefaults easier to use - -For full customization of the default set of hardware qemu supports, a user can pass -nodefaults and then manually specify each device they want. Many specific options document what they translate to in terms of the full configuration model; however, the defaults for any given platform don't. - -I'd love to have documentation of the default hardware configuration, in terms of qemu command-line options, to make it easy to run qemu -nodefaults, paste in the default command-line, and edit it. - -As this varies by emulated machine, perhaps qemu could have a command-line option to print a specific machine (e.g. pc-i440fx-2.5) in the form of qemu command-line options? \ No newline at end of file diff --git a/results/classifier/deepseek-2-tmp/output/device/1585433 b/results/classifier/deepseek-2-tmp/output/device/1585433 deleted file mode 100644 index 9ec7006d..00000000 --- a/results/classifier/deepseek-2-tmp/output/device/1585433 +++ /dev/null @@ -1,11 +0,0 @@ - -if docker-volume-size of baymodel lessthan 3, bay cann't create - -magnum is running on centos7, - - -magnum baymodel-create --name k8sbaymodel5 --image-id fedora-23-atomic-20160405 --keypair-id testkey --external-network-id public --dns-nameserver 8.8.8.8 --flavor-id m1.small --coe kubernetes --docker-volume-size 5 - -magnum bay-create --name k8sbay5 --baymodel k8sbaymodel5 --node-count 1 - -Execute the above command can get a completed bay,but when docker-volume-size is 1 or 2,the status of bay is FAILED. \ No newline at end of file diff --git a/results/classifier/deepseek-2-tmp/output/device/1585971 b/results/classifier/deepseek-2-tmp/output/device/1585971 deleted file mode 100644 index c0857bb1..00000000 --- a/results/classifier/deepseek-2-tmp/output/device/1585971 +++ /dev/null @@ -1,21 +0,0 @@ - -Host system crashes on qemu with DMA remapping - -Hy, - -the host system crashes completely, when i try to pass an physical device without boot option intel_iommu=on set. In older kernel versions you didn't have to pass that option. - -I wonder if this can be easily checked by asking iommu state, avoiding a crash of the complete system. - -My data: -cpu model: Intel(R) Core(TM) i7 CPU -qemu version: 2.4.1-r2 -kernel version: 4.1.2 x86_64 -command line: -qemu-system-x86_64 -enable-kvm -drive file=/vms/prod/fw/fw.iso,if=virtio,format=raw -drive file=/vms/prod/fw/swap,if=virtio,format=raw -drive file=/vms/prod/fw/fwdata.iso,if=virtio,format=raw -m 512 -nographic -kernel /data/kernels/vmlinuz-2.6.36-gentoo-r8 -append "root=/dev/vda console=ttyS0 earlyprintk=serial" -net nic,model=virtio,macaddr=DE:AD:BE:EF:2D:AD -net tap,ifname=tapfw0,script=/etc/qemu/qemu-ifup -device pci-assign,host=03:00.0 - -There are also more detailed informations (if needed) here: -https://forums.gentoo.org/viewtopic-p-7923976.html - -Thanks, -Antonios. \ No newline at end of file diff --git a/results/classifier/deepseek-2-tmp/output/device/1586611 b/results/classifier/deepseek-2-tmp/output/device/1586611 deleted file mode 100644 index bad3d5bf..00000000 --- a/results/classifier/deepseek-2-tmp/output/device/1586611 +++ /dev/null @@ -1,14 +0,0 @@ - -usb-hub can not be detached when detach usb device from VM - -I give a host usb device to guest in the way of passthrough,use "virsh attach-device" cmd. In guest os,use "lsusb" cmd I can see two devices have been added,one is usb device and the other is usb-hub（0409:55aa NEC Corp. Hub）. -when I use "virsh detach-device" detach the usb device,in guest os the usb-hub was still exists. -It can create a bad impression when operating the VM,for example,suspend and resume the VM,qemu would report that: - -2016-05-24T12:03:54.434369Z qemu-kvm: Unknown savevm section or instance '0000:00:01.2/2/usb-hub' 0 - -2016-05-24T12:03:54.434742Z qemu-kvm: load of migration failed: Invalid argument - -From qemu's code,it can be sure that the usb-hub is generated by qemu,and the process of detaching usb-hub has already been executed,but failed.With adding print information,error as follows: -libusbx: error [do_close] Device handle closed while transfer was still being processed, but the device is still connected as far as we know -libusbx: warning [do_close] A cancellation for an in-flight transfer hasn't completed but closing the device handle \ No newline at end of file diff --git a/results/classifier/deepseek-2-tmp/output/device/1586613 b/results/classifier/deepseek-2-tmp/output/device/1586613 deleted file mode 100644 index 395e2f0a..00000000 --- a/results/classifier/deepseek-2-tmp/output/device/1586613 +++ /dev/null @@ -1,14 +0,0 @@ - -usb-hub can not be detached when detach usbdevice VM - -I give a host usb device to guest in the way of passthrough,use "virsh attach-device" cmd. In guest os,use "lsusb" cmd I can see two devices have been added,one is usb device and the other is usb-hub（0409:55aa NEC Corp. Hub）. -when I use "virsh detach-device" detach the usb device,in guest os the usb-hub was still exists. -It can create a bad impression when operating the VM,for example,suspend and resume the VM,qemu would report that: - -2016-05-24T12:03:54.434369Z qemu-kvm: Unknown savevm section or instance '0000:00:01.2/2/usb-hub' 0 - -2016-05-24T12:03:54.434742Z qemu-kvm: load of migration failed: Invalid argument - -From qemu's code,it can be sure that the usb-hub is generated by qemu,and the process of detaching usb-hub has already been executed,but failed.With adding print information,error as follows: -libusbx: error [do_close] Device handle closed while transfer was still being processed, but the device is still connected as far as we know -libusbx: warning [do_close] A cancellation for an in-flight transfer hasn't completed but closing the device handle \ No newline at end of file diff --git a/results/classifier/deepseek-2-tmp/output/device/1587065 b/results/classifier/deepseek-2-tmp/output/device/1587065 deleted file mode 100644 index 18b6ac44..00000000 --- a/results/classifier/deepseek-2-tmp/output/device/1587065 +++ /dev/null @@ -1,51 +0,0 @@ - -btrfs qemu-ga - multiple mounts block fsfreeze - -Having two mounts of the same device makes fsfreeze through qemu-ga impossible. -root@CmsrvMTA:/# mount -l | grep /dev/vda2 -/dev/vda2 on / type btrfs (rw,relatime,space_cache,subvolid=257,subvol=/@) -/dev/vda2 on /home type btrfs (rw,relatime,space_cache,subvolid=258,subvol=/@home) - -Having two mounts is rather common with btrfs, so the feature fsfreeze is unusable on these systems. - - -Below more information about how we encountered this issue... - -Message send to