diff options
Diffstat (limited to '')
| -rw-r--r-- | results/classifier/108/other/1239 | 51 | ||||
| -rw-r--r-- | results/classifier/108/other/1239008 | 92 |
2 files changed, 143 insertions, 0 deletions
diff --git a/results/classifier/108/other/1239 b/results/classifier/108/other/1239 new file mode 100644 index 000000000..011f36299 --- /dev/null +++ b/results/classifier/108/other/1239 @@ -0,0 +1,51 @@ +graphic: 0.880 +performance: 0.851 +other: 0.846 +device: 0.844 +KVM: 0.834 +vnc: 0.799 +socket: 0.784 +network: 0.776 +PID: 0.770 +permissions: 0.762 +files: 0.753 +semantic: 0.745 +debug: 0.734 +boot: 0.712 + +The help document of qemu-img misses some options +Description of problem: +The "--help" option of qemu-img misses the option "skip-broken-bitmaps" for convert , "image-opts" for bench, "object" for dd and "force-share" for measure. +Steps to reproduce: +1. For the option "skip-broken-bitmaps", the following code appears during option parsing for convert and modifies the skip_broken in qemu-img.c:2377-2379. + +``` + case OPTION_SKIP_BROKEN: + skip_broken = true; + break; +``` + +2. For the option "image-opts", the following code appears during option parsing for bench and modifies the image_opts in qemu-img.c:4511-4513. + +``` + case OPTION_IMAGE_OPTS: + image_opts = true; + break; +``` +3. For the option "object", the following code appears during option parsing for dd and calls the user_creatable_process_cmdline in qemu-img.c:4980-4982. + +``` + case OPTION_OBJECT: + user_creatable_process_cmdline(optarg); + break; +``` +4. For the option "force-share", the following code appears during option parsing for measure and modifies the force_share in qemu-img.c:5237-5239. +``` + case 'U': + force_share = true; + break; +``` +Additional information: +But they do not appear in the document provided by "--help". + +It may prevent users from using the relevant function. diff --git a/results/classifier/108/other/1239008 b/results/classifier/108/other/1239008 new file mode 100644 index 000000000..65937d66b --- /dev/null +++ b/results/classifier/108/other/1239008 @@ -0,0 +1,92 @@ +graphic: 0.685 +other: 0.584 +performance: 0.563 +device: 0.558 +PID: 0.504 +KVM: 0.484 +semantic: 0.477 +debug: 0.395 +vnc: 0.386 +socket: 0.375 +files: 0.341 +permissions: 0.336 +network: 0.334 +boot: 0.275 + +qemu fails to scroll screen on ^Vidmem output + +Pascal uses ^Vidmem for B800 console output. The terminal does not oblige the Pascal OS code to scroll the output. Virtualbox emulation works, so this must be a qemu bug. Using QEMU in KVM mode as Ubuntu LTS. + +Source line to trip bug(in theory pushes VideoMem up one line): + +procedure Scroll; +//this is whats causing crashes. FIXME:Virtualbox not affected.QEMU BUG? +begin + if scrolldisabled then exit; + if (CursorPosY >= 24) then begin //in case called before end of screen + blank:= $20 or (TextAttr shl 8); + Move((VidMem+(2*80))^,VidMem^,24*(2*80)); + // Empty last line + FillWord((VidMem+(24*2*80))^,80,Blank); + CursorPosX:=1; + CursorPosY:=23; + update_cursor; + end; +end; + +Thanks for reporting this bug. Is there any other reproducer you can give us? + +I dont know how to write it myself, but the original kernel scrolling +code is in C. +Might try OSDev forums. Not that I know of. + +On 11/27/2013 09:24 PM, Serge Hallyn wrote: +> Thanks for reporting this bug. Is there any other reproducer you can +> give us? +> +> ** No longer affects: kvm (Ubuntu) +> +> ** Also affects: qemu (Ubuntu) +> Importance: Undecided +> Status: New +> +> ** Changed in: qemu (Ubuntu) +> Status: New => Incomplete +> +> ** Changed in: qemu +> Status: New => Incomplete +> + + + +Can you test with the latest version to see if this still affects you? +If this still is a problem, any information on how to obtain the Guest OS in question that would also be helpful. + +It is hosted on google code, a dying service. FreePascal(coffee) OS.A +more basic version is posted there.I assume it works as the version that +I last built did not for some reason. Sources should be there via +subversion checkout.Thats what I tested with. +https://code.google.com/p/coffee-os/ + + It uses a basic VRAM scroll buffer and writes to it. + +Examples are found elsewhere in C. (OS Dev pages) +Im in the middle of a fedup upgrade at the moment, but will see what I +can do. + +On 06/17/2015 12:11 PM, Chris J Arges wrote: +> Can you test with the latest version to see if this still affects you? +> If this still is a problem, any information on how to obtain the Guest OS in question that would also be helpful. +> +> ** Changed in: qemu (Ubuntu) +> Status: New => Incomplete +> + + + +Triaging old bug tickets... can you still reproduce this issue with the latest version of QEMU? Or could we close this ticket nowadays? + +[Expired for QEMU because there has been no activity for 60 days.] + +[Expired for qemu (Ubuntu) because there has been no activity for 60 days.] + |