summary refs log tree commit diff stats
path: root/results/scraper/launchpad-without-comments/1798434
diff options
context:
space:
mode:
authorChristian Krinitsin <mail@krinitsin.com>2025-06-30 12:24:58 +0000
committerChristian Krinitsin <mail@krinitsin.com>2025-06-30 12:27:06 +0000
commit33606b41d35115f887ea688b1a16f2ff85bf2fe4 (patch)
tree406b2c7b19a087ba437c68f3dbf0b589fa1d6150 /results/scraper/launchpad-without-comments/1798434
parentadedf8771bc4de3113041ca21bd4d0d1c0014b6a (diff)
downloadqemu-analysis-33606b41d35115f887ea688b1a16f2ff85bf2fe4.tar.gz
qemu-analysis-33606b41d35115f887ea688b1a16f2ff85bf2fe4.zip
add launchpad bug reports without comments
Diffstat (limited to 'results/scraper/launchpad-without-comments/1798434')
-rw-r--r--results/scraper/launchpad-without-comments/17984345
1 files changed, 5 insertions, 0 deletions
diff --git a/results/scraper/launchpad-without-comments/1798434 b/results/scraper/launchpad-without-comments/1798434
new file mode 100644
index 000000000..8ac6178ab
--- /dev/null
+++ b/results/scraper/launchpad-without-comments/1798434
@@ -0,0 +1,5 @@
+[Feature Request] Automatic device configuration discovery
+
+Would it be possible to have a script that enumerates the device tree of a Linux host and generates a qemu command line that would recreate it under emulation? The user would have to customize the arguments (for instance to point to disk image files), but it would take a lot of the guesswork out.
+
+Similarly, is there information that can be gleaned from the kernel build config that would help with configuration?
\ No newline at end of file