summary refs log tree commit diff stats
path: root/results/classifier/gemma3:12b/device/133
diff options
context:
space:
mode:
Diffstat (limited to '')
-rw-r--r--results/classifier/gemma3:12b/device/1332
-rw-r--r--results/classifier/gemma3:12b/device/133223411
-rw-r--r--results/classifier/gemma3:12b/device/133321637
-rw-r--r--results/classifier/gemma3:12b/device/133368858
-rw-r--r--results/classifier/gemma3:12b/device/13362
-rw-r--r--results/classifier/gemma3:12b/device/133612312
-rw-r--r--results/classifier/gemma3:12b/device/13361926
7 files changed, 128 insertions, 0 deletions
diff --git a/results/classifier/gemma3:12b/device/133 b/results/classifier/gemma3:12b/device/133
new file mode 100644
index 00000000..e2b3e6e9
--- /dev/null
+++ b/results/classifier/gemma3:12b/device/133
@@ -0,0 +1,2 @@
+
+Chardev websocket might not support pasting more than a few chars
diff --git a/results/classifier/gemma3:12b/device/1332234 b/results/classifier/gemma3:12b/device/1332234
new file mode 100644
index 00000000..2ceda31b
--- /dev/null
+++ b/results/classifier/gemma3:12b/device/1332234
@@ -0,0 +1,11 @@
+
+qemu-system-ppc no longer able to read real cdrom
+
+When I use to send the -cdrom /dev/cdrom option to QEMU, I would be able to use a real cdrom. With QEMU v2.0.0, real cdroms don't work. A quick look at the output from the "info block" command shows this:
+
+ide1-cd0: /dev/cdrom (raw, read-only)
+      Removable device: not locked, tray closed
+
+This indicates that the cdrom is set to /dev/cdrom. I remember versions of QEMU prior to 1.5 were able to use a real cdrom. 
+
+qemu-system-ppc is being run on Mac OS 10.6.8.
\ No newline at end of file
diff --git a/results/classifier/gemma3:12b/device/1333216 b/results/classifier/gemma3:12b/device/1333216
new file mode 100644
index 00000000..50206197
--- /dev/null
+++ b/results/classifier/gemma3:12b/device/1333216
@@ -0,0 +1,37 @@
+
+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/gemma3:12b/device/1333688 b/results/classifier/gemma3:12b/device/1333688
new file mode 100644
index 00000000..064495cf
--- /dev/null
+++ b/results/classifier/gemma3:12b/device/1333688
@@ -0,0 +1,58 @@
+
+vhost-user: VHOST_USER_SET_MEM_TABLE doesn't contain all regions
+
+
+
+vhost-user implementation doesn't provide information about all memory regions, 
+and in some cases client is not able to map buffer memory as he is missing 
+memory region information for specific address.
+
+Same thing is implemented properly for vhost-net. Below gdb outputs are 
+showing memory regions information provided to the vhost-net and vhost-user.
+
+
+
+==== memory regions information provided to vhost-net  ====
+
+(gdb) p/x hdev->mem->regions[0]
+$21 = {
+  guest_phys_addr = 0x100000000,
+  memory_size = 0xc0000000,
+  userspace_addr = 0x2aab6ac00000,
+  flags_padding = 0x0
+}
+(gdb) p/x hdev->mem->regions[1]
+$22 = {
+  guest_phys_addr = 0xfffc0000,
+  memory_size = 0x40000,
+  userspace_addr = 0x7ffff4a00000,
+  flags_padding = 0x0
+}
+(gdb) p/x hdev->mem->regions[2]
+$23 = {
+  guest_phys_addr = 0x0,
+  memory_size = 0xa0000,
+  userspace_addr = 0x2aaaaac00000,
+  flags_padding = 0x0
+}
+(gdb) p/x hdev->mem->regions[3]
+$24 = {
+  guest_phys_addr = 0xc0000,
+  memory_size = 0xbff40000,
+  userspace_addr = 0x2aaaaacc0000,
+  flags_padding = 0x0
+}
+(gdb)
+
+
+==== memory regions information provided to vhost-user  ====
+
+(gdb) p/x msg.memory.nregions
+$28 = 0x1
+(gdb) p/x msg.memory.regions[0]
+$29 = {
+  guest_phys_addr = 0x0,
+  memory_size = 0x180000000,
+  userspace_addr = 0x2aaaaac00000
+}
+(gdb)
\ No newline at end of file
diff --git a/results/classifier/gemma3:12b/device/1336 b/results/classifier/gemma3:12b/device/1336
new file mode 100644
index 00000000..bc5d8cee
--- /dev/null
+++ b/results/classifier/gemma3:12b/device/1336
@@ -0,0 +1,2 @@
+
+QEMU qxl_phys2virt Unsafe Address Translation Lead to OOB Read
diff --git a/results/classifier/gemma3:12b/device/1336123 b/results/classifier/gemma3:12b/device/1336123
new file mode 100644
index 00000000..86bbfff7
--- /dev/null
+++ b/results/classifier/gemma3:12b/device/1336123
@@ -0,0 +1,12 @@
+
+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/gemma3:12b/device/1336192 b/results/classifier/gemma3:12b/device/1336192
new file mode 100644
index 00000000..ca9320f0
--- /dev/null
+++ b/results/classifier/gemma3:12b/device/1336192
@@ -0,0 +1,6 @@
+
+delvm does not delete snapshots on every disks
+
+Using more than one block device, using delvm does remove snapshot from the first block device, but does not remove snapshots from other blockdevs (complains about not finding snapshot on 1st blockdev).
+
+Attached patch fixes that.
\ No newline at end of file