summary refs log tree commit diff stats
path: root/results/classifier/zero-shot/118/all/990364
blob: 4a1f5a5cdbb8a8168080f22e24c0652bcf8ffc65 (plain) (blame)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
device: 0.981
assembly: 0.975
architecture: 0.975
socket: 0.974
network: 0.973
peripherals: 0.971
graphic: 0.971
register: 0.970
arm: 0.969
PID: 0.968
permissions: 0.967
semantic: 0.967
files: 0.967
boot: 0.965
kernel: 0.965
performance: 0.964
vnc: 0.962
debug: 0.958
virtual: 0.957
ppc: 0.954
user-level: 0.942
risc-v: 0.941
mistranslation: 0.940
x86: 0.930
hypervisor: 0.929
TCG: 0.925
KVM: 0.921
VMM: 0.915
i386: 0.882

virtio_ioport_write: unexpected address 0x13 value 0x1

Hello! I have:

virtio_ioport_write: unexpected address 0x13 value 0x1

on config:

LC_ALL=C PATH=/usr/local/sbin:/usr/local/bin:/usr/bin:/usr/sbin:/sbin:/bin QEMU_AUDIO_DRV=none /usr/bin/kvm -S -M pc-0.12 -cpu qemu32 -enable-kvm -m 3072 -smp 1 -name nata_xp -uuid da607499-1d8f-e7ef-d1d2-38
1c1839e4ba -chardev socket,id=monitor,path=/var/lib/libvirt/qemu/nata_xp.monitor,server,nowait -monitor chardev:monitor -localtime -boot c -drive file=/root/nata_xp.qcow2,if=virtio,index=0,boot=on,format=raw
,cache=none -drive file=/home/admino/virtio-win-0.1-22.iso,if=ide,media=cdrom,index=2,format=raw -net nic,macaddr=00:16:36:06:02:69,vlan=0,model=virtio,name=virtio.0 -net tap,fd=43,vlan=0,name=tap.0 -serial
none -parallel none -usb -usbdevice tablet -vnc 127.0.0.1:3 -k en-us -vga cirrus
pci_add_option_rom: failed to find romfile "pxe-virtio.bin"

with kernel 2.6.32-40-generic #87-Ubuntu SMP Tue Mar 6 00:56:56 UTC 2012 x86_64 GNU/Linux
qemu drivers are virtio-win-0.1-22.iso
kvm version 1:84+dfsg-0ubuntu16+0.12.3+noroms+0ubuntu9.18
qemu 0.12.3+noroms-0ubuntu9.18



I forgot: guest os is Windows XP Pro SP3



Hi Vadim,
Here is a recent bug report with virtio-win-0.1-22.iso.  Wanted to
bring it to your attention, please let me know if you already monitor
these bug emails.

Stefan

On Sat, Apr 28, 2012 at 9:49 AM, Vitalis <email address hidden> wrote:
> Public bug reported:
>
> Hello! I have:
>
> virtio_ioport_write: unexpected address 0x13 value 0x1
>
> on config:
>
> LC_ALL=C PATH=/usr/local/sbin:/usr/local/bin:/usr/bin:/usr/sbin:/sbin:/bin QEMU_AUDIO_DRV=none /usr/bin/kvm -S -M pc-0.12 -cpu qemu32 -enable-kvm -m 3072 -smp 1 -name nata_xp -uuid da607499-1d8f-e7ef-d1d2-38
> 1c1839e4ba -chardev socket,id=monitor,path=/var/lib/libvirt/qemu/nata_xp.monitor,server,nowait -monitor chardev:monitor -localtime -boot c -drive file=/root/nata_xp.qcow2,if=virtio,index=0,boot=on,format=raw
> ,cache=none -drive file=/home/admino/virtio-win-0.1-22.iso,if=ide,media=cdrom,index=2,format=raw -net nic,macaddr=00:16:36:06:02:69,vlan=0,model=virtio,name=virtio.0 -net tap,fd=43,vlan=0,name=tap.0 -serial
> none -parallel none -usb -usbdevice tablet -vnc 127.0.0.1:3 -k en-us -vga cirrus
> pci_add_option_rom: failed to find romfile "pxe-virtio.bin"
>
> with kernel 2.6.32-40-generic #87-Ubuntu SMP Tue Mar 6 00:56:56 UTC 2012 x86_64 GNU/Linux
> qemu drivers are virtio-win-0.1-22.iso
> kvm version 1:84+dfsg-0ubuntu16+0.12.3+noroms+0ubuntu9.18
> qemu 0.12.3+noroms-0ubuntu9.18
>
> ** Affects: qemu
>     Importance: Undecided
>         Status: New
>
>
> ** Tags: bug kvm virtio
>
> --
> You received this bug notification because you are a member of qemu-
> devel-ml, which is subscribed to QEMU.
> https://bugs.launchpad.net/bugs/990364
>
> Title:
>  virtio_ioport_write: unexpected address 0x13 value 0x1
>
> Status in QEMU:
>  New
>
> Bug description:
>  Hello! I have:
>
>  virtio_ioport_write: unexpected address 0x13 value 0x1
>
>  on config:
>
>  LC_ALL=C PATH=/usr/local/sbin:/usr/local/bin:/usr/bin:/usr/sbin:/sbin:/bin QEMU_AUDIO_DRV=none /usr/bin/kvm -S -M pc-0.12 -cpu qemu32 -enable-kvm -m 3072 -smp 1 -name nata_xp -uuid da607499-1d8f-e7ef-d1d2-38
>  1c1839e4ba -chardev socket,id=monitor,path=/var/lib/libvirt/qemu/nata_xp.monitor,server,nowait -monitor chardev:monitor -localtime -boot c -drive file=/root/nata_xp.qcow2,if=virtio,index=0,boot=on,format=raw
>  ,cache=none -drive file=/home/admino/virtio-win-0.1-22.iso,if=ide,media=cdrom,index=2,format=raw -net nic,macaddr=00:16:36:06:02:69,vlan=0,model=virtio,name=virtio.0 -net tap,fd=43,vlan=0,name=tap.0 -serial
>  none -parallel none -usb -usbdevice tablet -vnc 127.0.0.1:3 -k en-us -vga cirrus
>  pci_add_option_rom: failed to find romfile "pxe-virtio.bin"
>
>  with kernel 2.6.32-40-generic #87-Ubuntu SMP Tue Mar 6 00:56:56 UTC 2012 x86_64 GNU/Linux
>  qemu drivers are virtio-win-0.1-22.iso
>  kvm version 1:84+dfsg-0ubuntu16+0.12.3+noroms+0ubuntu9.18
>  qemu 0.12.3+noroms-0ubuntu9.18
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/qemu/+bug/990364/+subscriptions
>


On Monday, April 30, 2012 03:31:03 PM Stefan Hajnoczi wrote:
> Hi Vadim,
> Here is a recent bug report with virtio-win-0.1-22.iso.  Wanted to
> bring it to your attention, please let me know if you already monitor
> these bug emails.
Hi Stefan,
Yes, it's on my radar.
Cheers,
Vadim.
> 
> Stefan
> 
> On Sat, Apr 28, 2012 at 9:49 AM, Vitalis <email address hidden> wrote:
> > Public bug reported:
> > 
> > Hello! I have:
> > 
> > virtio_ioport_write: unexpected address 0x13 value 0x1
> > 
> > on config:
> > 
> > LC_ALL=C
> > PATH=/usr/local/sbin:/usr/local/bin:/usr/bin:/usr/sbin:/sbin:/bin
> > QEMU_AUDIO_DRV=none /usr/bin/kvm -S -M pc-0.12 -cpu qemu32 -enable-kvm
> > -m 3072 -smp 1 -name nata_xp -uuid da607499-1d8f-e7ef-d1d2-38 1c1839e4ba
> > -chardev
> > socket,id=monitor,path=/var/lib/libvirt/qemu/nata_xp.monitor,server,nowa
> > it -monitor chardev:monitor -localtime -boot c -drive
> > file=/root/nata_xp.qcow2,if=virtio,index=0,boot=on,format=raw
> > ,cache=none -drive
> > file=/home/admino/virtio-win-0.1-22.iso,if=ide,media=cdrom,index=2,forma
> > t=raw -net
> > nic,macaddr=00:16:36:06:02:69,vlan=0,model=virtio,name=virtio.0 -net
> > tap,fd=43,vlan=0,name=tap.0 -serial none -parallel none -usb -usbdevice
> > tablet -vnc 127.0.0.1:3 -k en-us -vga cirrus pci_add_option_rom: failed
> > to find romfile "pxe-virtio.bin"
> > 
> > with kernel 2.6.32-40-generic #87-Ubuntu SMP Tue Mar 6 00:56:56 UTC 2012
> > x86_64 GNU/Linux qemu drivers are virtio-win-0.1-22.iso
> > kvm version 1:84+dfsg-0ubuntu16+0.12.3+noroms+0ubuntu9.18
> > qemu 0.12.3+noroms-0ubuntu9.18
> > 
> > ** Affects: qemu
> >     Importance: Undecided
> >         Status: New
> > 
> > 
> > ** Tags: bug kvm virtio
> > 
> > --
> > You received this bug notification because you are a member of qemu-
> > devel-ml, which is subscribed to QEMU.
> > https://bugs.launchpad.net/bugs/990364
> > 
> > Title:
> >  virtio_ioport_write: unexpected address 0x13 value 0x1
> > 
> > Status in QEMU:
> >  New
> > 
> > Bug description:
> >  Hello! I have:
> > 
> >  virtio_ioport_write: unexpected address 0x13 value 0x1
> > 
> >  on config:
> > 
> >  LC_ALL=C
> > PATH=/usr/local/sbin:/usr/local/bin:/usr/bin:/usr/sbin:/sbin:/bin
> > QEMU_AUDIO_DRV=none /usr/bin/kvm -S -M pc-0.12 -cpu qemu32 -enable-kvm
> > -m 3072 -smp 1 -name nata_xp -uuid da607499-1d8f-e7ef-d1d2-38 1c1839e4ba
> > -chardev
> > socket,id=monitor,path=/var/lib/libvirt/qemu/nata_xp.monitor,server,nowa
> > it -monitor chardev:monitor -localtime -boot c -drive
> > file=/root/nata_xp.qcow2,if=virtio,index=0,boot=on,format=raw
> > ,cache=none -drive
> > file=/home/admino/virtio-win-0.1-22.iso,if=ide,media=cdrom,index=2,forma
> > t=raw -net
> > nic,macaddr=00:16:36:06:02:69,vlan=0,model=virtio,name=virtio.0 -net
> > tap,fd=43,vlan=0,name=tap.0 -serial none -parallel none -usb -usbdevice
> > tablet -vnc 127.0.0.1:3 -k en-us -vga cirrus pci_add_option_rom: failed
> > to find romfile "pxe-virtio.bin"
> > 
> >  with kernel 2.6.32-40-generic #87-Ubuntu SMP Tue Mar 6 00:56:56 UTC 2012
> > x86_64 GNU/Linux qemu drivers are virtio-win-0.1-22.iso
> >  kvm version 1:84+dfsg-0ubuntu16+0.12.3+noroms+0ubuntu9.18
> >  qemu 0.12.3+noroms-0ubuntu9.18
> > 
> > To manage notifications about this bug go to:
> > https://bugs.launchpad.net/qemu/+bug/990364/+subscriptions


On Monday, April 30, 2012 07:17:09 PM Vadim Rozenfeld wrote:
> On Monday, April 30, 2012 03:31:03 PM Stefan Hajnoczi wrote:
> > Hi Vadim,
> > Here is a recent bug report with virtio-win-0.1-22.iso.  Wanted to
> > bring it to your attention, please let me know if you already monitor
> > these bug emails.
> 
> Hi Stefan,
> Yes, it's on my radar.
> Cheers,
> Vadim.
> 
seems to be ndis related 
(https://bugzilla.redhat.com/show_bug.cgi?id=808654#c10)
cc'ing Yan.

> > Stefan
> > 
> > On Sat, Apr 28, 2012 at 9:49 AM, Vitalis <email address hidden> wrote:
> > > Public bug reported:
> > > 
> > > Hello! I have:
> > > 
> > > virtio_ioport_write: unexpected address 0x13 value 0x1
> > > 
> > > on config:
> > > 
> > > LC_ALL=C
> > > PATH=/usr/local/sbin:/usr/local/bin:/usr/bin:/usr/sbin:/sbin:/bin
> > > QEMU_AUDIO_DRV=none /usr/bin/kvm -S -M pc-0.12 -cpu qemu32 -enable-kvm
> > > -m 3072 -smp 1 -name nata_xp -uuid da607499-1d8f-e7ef-d1d2-38
> > > 1c1839e4ba -chardev
> > > socket,id=monitor,path=/var/lib/libvirt/qemu/nata_xp.monitor,server,now
> > > a it -monitor chardev:monitor -localtime -boot c -drive
> > > file=/root/nata_xp.qcow2,if=virtio,index=0,boot=on,format=raw
> > > ,cache=none -drive
> > > file=/home/admino/virtio-win-0.1-22.iso,if=ide,media=cdrom,index=2,form
> > > a t=raw -net
> > > nic,macaddr=00:16:36:06:02:69,vlan=0,model=virtio,name=virtio.0 -net
> > > tap,fd=43,vlan=0,name=tap.0 -serial none -parallel none -usb -usbdevice
> > > tablet -vnc 127.0.0.1:3 -k en-us -vga cirrus pci_add_option_rom: failed
> > > to find romfile "pxe-virtio.bin"
> > > 
> > > with kernel 2.6.32-40-generic #87-Ubuntu SMP Tue Mar 6 00:56:56 UTC
> > > 2012 x86_64 GNU/Linux qemu drivers are virtio-win-0.1-22.iso
> > > kvm version 1:84+dfsg-0ubuntu16+0.12.3+noroms+0ubuntu9.18
> > > qemu 0.12.3+noroms-0ubuntu9.18
> > > 
> > > ** Affects: qemu
> > > 
> > >     Importance: Undecided
> > >     
> > >         Status: New
> > > 
> > > ** Tags: bug kvm virtio
> > > 
> > > --
> > > You received this bug notification because you are a member of qemu-
> > > devel-ml, which is subscribed to QEMU.
> > > https://bugs.launchpad.net/bugs/990364
> > > 
> > > Title:
> > >  virtio_ioport_write: unexpected address 0x13 value 0x1
> > > 
> > > Status in QEMU:
> > >  New
> > > 
> > > Bug description:
> > >  Hello! I have:
> > >  
> > >  virtio_ioport_write: unexpected address 0x13 value 0x1
> > >  
> > >  on config:
> > >  
> > >  LC_ALL=C
> > > 
> > > PATH=/usr/local/sbin:/usr/local/bin:/usr/bin:/usr/sbin:/sbin:/bin
> > > QEMU_AUDIO_DRV=none /usr/bin/kvm -S -M pc-0.12 -cpu qemu32 -enable-kvm
> > > -m 3072 -smp 1 -name nata_xp -uuid da607499-1d8f-e7ef-d1d2-38
> > > 1c1839e4ba -chardev
> > > socket,id=monitor,path=/var/lib/libvirt/qemu/nata_xp.monitor,server,now
> > > a it -monitor chardev:monitor -localtime -boot c -drive
> > > file=/root/nata_xp.qcow2,if=virtio,index=0,boot=on,format=raw
> > > ,cache=none -drive
> > > file=/home/admino/virtio-win-0.1-22.iso,if=ide,media=cdrom,index=2,form
> > > a t=raw -net
> > > nic,macaddr=00:16:36:06:02:69,vlan=0,model=virtio,name=virtio.0 -net
> > > tap,fd=43,vlan=0,name=tap.0 -serial none -parallel none -usb -usbdevice
> > > tablet -vnc 127.0.0.1:3 -k en-us -vga cirrus pci_add_option_rom: failed
> > > to find romfile "pxe-virtio.bin"
> > > 
> > >  with kernel 2.6.32-40-generic #87-Ubuntu SMP Tue Mar 6 00:56:56 UTC
> > >  2012
> > > 
> > > x86_64 GNU/Linux qemu drivers are virtio-win-0.1-22.iso
> > > 
> > >  kvm version 1:84+dfsg-0ubuntu16+0.12.3+noroms+0ubuntu9.18
> > >  qemu 0.12.3+noroms-0ubuntu9.18
> > > 
> > > To manage notifications about this bug go to:
> > > https://bugs.launchpad.net/qemu/+bug/990364/+subscriptions


And what? Where can I get new drivers for WinXP?

On Thursday, May 03, 2012 10:17:15 PM Vitalis wrote:
> And what? Where can I get new drivers for WinXP?

http://people.redhat.com/vrozenfe/build-27/virtio-win-prewhql-0.1.zip


But with new drivers i got "virtio_ioport_write: unexpected address 0x13 value 0x1" again.

can you upload the corresponding dump file?

I see in properties of drivers version 51.63.103.2700 (date is 20.04.2012). 

It doesn't look like as a vritio-win driver problem. 
you get the following message 
"virtio_ioport_write: unexpected address 0x13 value 0x1"
because netkvm driver triggers BSOD event, which  happened in 
different stack, and then kills the hosting QEMU prccess
by writing to ISR register. 

In your case (minidumps in comments #1 and #11) BSOD
happened inside of Raw Input Thread, which usually caused
by all kind of key and mouse filters/loggers. 

Unfortunately minidump doesn't provide enough information
to troubleshoot such kind of problems. If it's possible - try disabling 
antivirus  and RDP on your system.
Vadim.  

I change network card in guest to RTL and no have BSOD, on all guest. Why?
How can we detect the cause?

and how can i use winXP without antivirus and RDP? Its nonsense!!! :-) no sense!

Hard to say at the moment. 
In both cases the crash stack looks absolutely the same:

nt!KiDeliverApc+0x66
hal!HalpApcInterrupt+0xc5                                                                                                                  
hal!HalRequestSoftwareInterrupt+0x3b                                                                                                       
win32k!RawInputThread+0x625                                                                                                                
win32k!xxxCreateSystemThreads+0x60                                                                                                         
win32k!NtUserCallOneParam+0x23                                                                                                             
nt!KiFastCallEntry+0xf8

Try reproducing the problem with Kernel
memory dump option turned on instead of 
minidump. In this case it will be possible
to extract more useful information.

Vadim.

How turn on kernel memory dump in XP?

http://support.microsoft.com/kb/316450

Hello!
ANd again "virtio_ioport_write: unexpected address 0x13 value 0x1".
Drvers: from virtio-win-0.1-30.iso
config: <domain type='kvm'>
  <name>buh_xp</name>
  <uuid>f0e8ac00-4545-eb5d-e8f2-c885063e5ad0</uuid>
  <memory>1097152</memory>
  <currentMemory>1097152</currentMemory>
  <vcpu>1</vcpu>
  <os>
    <type arch='i686' machine='pc-0.12'>hvm</type>
    <boot dev='hd'/>
  </os>
  <features>
    <acpi/>
  </features>
  <clock offset='localtime'/>
  <on_poweroff>destroy</on_poweroff>
  <on_reboot>restart</on_reboot>
  <on_crash>restart</on_crash>
  <devices>
    <emulator>/usr/bin/kvm</emulator>
    <disk type='file' device='disk'>
      <driver name='qemu' type='raw' cache='none'/>
      <source file='/root/buh_xp.qcow2'/>
      <target dev='hda' bus='virtio'/>
    </disk>
    <disk type='file' device='cdrom'>
      <driver name='qemu' type='raw'/>
      <source file='/home/worky/virtio-win-0.1-30.iso'/>
      <target dev='hdc' bus='ide'/>
      <readonly/>
    </disk>
    <interface type='bridge'>
      <mac address='00:16:36:2f:11:31'/>
      <source bridge='br0'/>
      <model type='virtio'/>
    </interface>
    <console type='pty'>
      <target port='0'/>
    </console>
    <console type='pty'>
      <target port='0'/>
    </console>
    <input type='tablet' bus='usb'/>
    <input type='mouse' bus='ps2'/>
    <graphics type='vnc' port='-1' autoport='yes' keymap='en-us'/>
    <video>
      <model type='cirrus' vram='9216' heads='1'/>
    </video>
  </devices>
</domain>

uname: Linux test-2 2.6.32-43-server #97-Ubuntu SMP Wed Sep 5 16:56:41 UTC 2012 x86_64 GNU/Linux
qemu-kvm: 0.12.3+noroms-0ubuntu9.20
kvm: 1:84+dfsg-0ubuntu16+0.12.3+noroms+0ubuntu9.20
hardware: SuperMicro x8sil-f


I can't add much, except that I started noticing his issue when migrating my VMs to an Ubuntu Precise server hypervisor where under (heavy?) load my Win 2008 Server VM started to crash very frequently with the error showing up in the libvirt log of the VM.

It might be useful information that I ended up moving the VM back to a Debian Squeeze hypervisor which hosted it originally and things were running smoothly until earlier today when a crash with the same message happened again. What's sure is that under Squeeze the issue is far-far less frequent, on Precise the VM got reset a dozen times during the first 48 h, while on Squeeze it's been running fine even under heavy load for weeks without a hiccup.

Details of the Precise hypervisor:
kvm: 1:84+dfsg-0ubuntu16+1.0+noroms+0ubuntu14.3
qemu-kvm: 1.0+noroms-0ubuntu14.3
kernel: 3.2.0-32-generic
(tested with virtio drivers virtio-win-0.1-15.iso and virtio-win-0.1-30.iso)

Details of the Squeeze hypervisor:
kvm: 1:0.12.5+dfsg-5+squeeze8
qemu-kvm: 0.12.5+dfsg-5+squeeze8
kernel: 2.6.32-5-amd64
(tested with virtio drivers virtio-win-0.1-15.iso)


IMHO, Ubuntu Server for KVM virtualization - is BAD idea! Very BAD idea......

Status changed to 'Confirmed' because the bug affects multiple users.

Hi,
this got to my attention after being reassigned from upstream to Ubuntu's qemu.

I'd assume that this is very much timed out and no more applicable and mark it incomplete by that to give everybody a chance to object and describe what they face today.