add new classifier result

1 files changed, 91 insertions, 0 deletions

diff --git a/results/classifier/105/socket/1870331 b/results/classifier/105/socket/1870331
new file mode 100644
index 00000000..a70f94e7
--- /dev/null
+++ b/results/classifier/105/socket/1870331
@@ -0,0 +1,91 @@
+socket: 0.830
+instruction: 0.747
+network: 0.747
+other: 0.729
+device: 0.722
+assembly: 0.700
+graphic: 0.626
+semantic: 0.562
+boot: 0.560
+vnc: 0.555
+KVM: 0.503
+mistranslation: 0.498
+
+default nic device created even though supplied by configfile
+
+QEMU emulator version 4.1.94
+
+Documentation states that qemu will create a default nic as long as not explicitly forbidden (-nic none) or defined ( e.g. -nic <options>).
+
+Observation:
+Even though qemu-system-ppc is started with "-readconfig" (which defines a nic), another nic gets created. When additionally suppling "-nic none", only the nic of the config file is created.
+As matter of fact, if all items that are defined in config file are supplied as command line arguments, no further nic is created. 
+
+Expectation:
+When a nic is defined in config file, the default guest-nic should not get created.
+That would match behavior when all items, defined in config file are supplied as command line arguments.
+
+
+Attached config file.
+
+(qemu) info pci
+ Bus 0, device 0, function 0:
+ Host bridge: PCI device 1057:0002
+ PCI subsystem 1af4:1100
+ id ""
+ Bus 0, device 1, function 0:
+ VGA controller: PCI device 1234:1111
+ PCI subsystem 1af4:1100
+ BAR0: 32 bit prefetchable memory at 0x80000000 [0x80ffffff].
+ BAR2: 32 bit memory at 0x81000000 [0x81000fff].
+ BAR6: 32 bit memory at 0xffffffffffffffff [0x0000fffe].
+ id ""
+ Bus 0, device 2, function 0:
+ Ethernet controller: PCI device 10ec:8029
+ PCI subsystem 1af4:1100
+ IRQ 23.
+ BAR0: I/O at 0x1000 [0x10ff].
+ BAR6: 32 bit memory at 0xffffffffffffffff [0x0007fffe].
+ id ""
+ Bus 0, device 3, function 0:
+ Ethernet controller: PCI device 10ec:8029
+ PCI subsystem 1af4:1100
+ IRQ 24.
+ BAR0: I/O at 0x1100 [0x11ff].
+ BAR6: 32 bit memory at 0xffffffffffffffff [0x0007fffe].
+ id ""
+
+
+
+The QEMU project is currently moving its bug tracking to another system.
+For this we need to know which bugs are still valid and which could be
+closed already. Thus we are setting the bug state to "Incomplete" now.
+
+If the bug has already been fixed in the latest upstream version of QEMU,
+then please close this ticket as "Fix released".
+
+If it is not fixed yet and you think that this bug report here is still
+valid, then you have two options:
+
+1) If you already have an account on gitlab.com, please open a new ticket
+for this problem in our new tracker here:
+
+    https://gitlab.com/qemu-project/qemu/-/issues
+
+and then close this ticket here on Launchpad (or let it expire auto-
+matically after 60 days). Please mention the URL of this bug ticket on
+Launchpad in the new ticket on GitLab.
+
+2) If you don't have an account on gitlab.com and don't intend to get
+one, but still would like to keep this ticket opened, then please switch
+the state back to "New" or "Confirmed" within the next 60 days (other-
+wise it will get closed as "Expired"). We will then eventually migrate
+the ticket automatically to the new system (but you won't be the reporter
+of the bug in the new system and thus you won't get notified on changes
+anymore).
+
+Thank you and sorry for the inconvenience.
+
+
+[Expired for QEMU because there has been no activity for 60 days.]
+