Re: [Qemu-devel] [Bug 818673] Re: virtio: trying to map MMIO memory
I experience this on uni-processor. On Tuesday 24 January 2012 16:48:04 Vitalis wrote: > And more: i have too more virtual PC with WindowsXP SP3 and with one > CPU, but them doesnt have any problems. Maybe this bug depends on 2 and > more CPU?? -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/818673 Title: virtio: trying to map MMIO memory Status in QEMU: New Bug description: Qemu host is Core i7, running Linux. Guest is Windows XP sp3. Often, qemu will crash shortly after starting (1-5 minutes) with a statement "qemu-system-x86_64: virtio: trying to map MMIO memory" This has occured with qemu-kvm 0.14, qemu-kvm 0.14.1, qemu-0.15.0-rc0 and qemu 0.15.0-rc1. Qemu is started as such: qemu-system-x86_64 -cpu host -enable-kvm -pidfile /home/rick/qemu/hds/wxp.pid -drive file=/home/rick/qemu/hds/wxp.raw,if=virtio -m 768 -name WinXP -net nic,model=virtio -net user -localtime -usb -vga qxl -device virtio-serial -chardev spicevmc,name=vdagent,id=vdagent -device virtserialport,chardev=vdagent,name=com.redhat.spice.0 -spice port=1234,disable-ticketing -daemonize -monitor telnet:localhost:12341,server,nowait The WXP guest has virtio 1.1.16 drivers for net and scsi, and the most current spice binaries from spice-space.org. To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/818673/+subscriptions
Re: [Qemu-devel] [Bug 818673] Re: virtio: trying to map MMIO memory
On Friday 23 September 2011 14:07:17 Alon Levy wrote: > On Thu, Sep 22, 2011 at 02:10:04PM -0500, Rick Vernam wrote: > > On Friday 16 September 2011 12:42:02 Rick Vernam wrote: > > > On Friday 16 September 2011 03:52:34 hkran wrote: > > > [snip] > > > > > > > I have tried many times with many restarts or shutdown-and-boot xp > > > > guest but failed to meet the crashing. > > > > (I am using the virtio drivers referenced in the earlier mail list.) > > > > my command: > > > > > > > > /home/huikai/qemu15/bin/qemu --enable-kvm -m 768 -drive > > > > file=/home/huikai/winxp_dev.img,if=virtio -net nic,model=virtio -net > > > > user -usb -usbdevice tablet -localtime -vga qxl -device > > > > virtio-serial -chardev spicevmc,name=vdagent,id=vdagent -device > > > > virtserialport,chardev=vdagent,name=spice0 -spice > > > > port=1234,disable-ticketing -monitor > > > > telnet:localhost:12341,server,nowait > > > > > > Okay, I tried a variation of that: > > > qemu-system-x86_64 -cpu host -enable-kvm -m 1536 -pidfile > > > /home/rick/qemu/hds/wxp.pid -drive > > > file=/home/rick/qemu/hds/wxp.raw,if=virtio -net nic,model=virtio -net > > > user -localtime -usb -vga qxl -device virtio-serial -chardev > > > spicevmc,name=vdagent,id=vdagent -device > > > virtserialport,chardev=vdagent,name=spice0 -spice > > > port=1234,disable-ticketing -monitor > > > telnet:localhost:12341,server,nowait > > > > > > And it's been running stable all day. > > > The differences between the command line that crashes and yours are: > > > - yours doesn't have "aio=native" in the -drive declaration. > > > - yours has some differences in the virtio-serial device declaration. > > > - yours has some differences in the virtserialport device declaration. > > > > > > As time permits I'm going to try each of those differences > > > individually. > > > > Without "aio=native" ... > > in the definition of virtserialport, I changed "name=spice0" to > > "name=com.redhat.spice.0" - with this change, the guest vdagent works, > > but it crashed... > > If you provide details on the crash maybe someone can help. This email thread has details early on the thread, and there is a bug report here: https://bugs.launchpad.net/bugs/818673 All the details of the crash that are available to me are previously described. > > > > Thanks, > > > -Rick
Re: [Qemu-devel] [Bug 818673] Re: virtio: trying to map MMIO memory
On Thu, Sep 22, 2011 at 02:10:04PM -0500, Rick Vernam wrote: > On Friday 16 September 2011 12:42:02 Rick Vernam wrote: > > On Friday 16 September 2011 03:52:34 hkran wrote: > > [snip] > > > > > I have tried many times with many restarts or shutdown-and-boot xp guest > > > but failed to meet the crashing. > > > (I am using the virtio drivers referenced in the earlier mail list.) > > > my command: > > > > > > /home/huikai/qemu15/bin/qemu --enable-kvm -m 768 -drive > > > file=/home/huikai/winxp_dev.img,if=virtio -net nic,model=virtio -net > > > user -usb -usbdevice tablet -localtime -vga qxl -device virtio-serial > > > -chardev spicevmc,name=vdagent,id=vdagent -device > > > virtserialport,chardev=vdagent,name=spice0 -spice > > > port=1234,disable-ticketing -monitor > > > telnet:localhost:12341,server,nowait > > > > Okay, I tried a variation of that: > > qemu-system-x86_64 -cpu host -enable-kvm -m 1536 -pidfile > > /home/rick/qemu/hds/wxp.pid -drive > > file=/home/rick/qemu/hds/wxp.raw,if=virtio -net nic,model=virtio -net user > > -localtime -usb -vga qxl -device virtio-serial -chardev > > spicevmc,name=vdagent,id=vdagent -device > > virtserialport,chardev=vdagent,name=spice0 -spice > > port=1234,disable-ticketing -monitor telnet:localhost:12341,server,nowait > > > > And it's been running stable all day. > > The differences between the command line that crashes and yours are: > > - yours doesn't have "aio=native" in the -drive declaration. > > - yours has some differences in the virtio-serial device declaration. > > - yours has some differences in the virtserialport device declaration. > > > > As time permits I'm going to try each of those differences individually. > Without "aio=native" ... > in the definition of virtserialport, I changed "name=spice0" to > "name=com.redhat.spice.0" - with this change, the guest vdagent works, but it > crashed... If you provide details on the crash maybe someone can help. > > > > > Thanks, > > -Rick >
Re: [Qemu-devel] [Bug 818673] Re: virtio: trying to map MMIO memory
On Friday 16 September 2011 12:42:02 Rick Vernam wrote: > On Friday 16 September 2011 03:52:34 hkran wrote: > [snip] > > > I have tried many times with many restarts or shutdown-and-boot xp guest > > but failed to meet the crashing. > > (I am using the virtio drivers referenced in the earlier mail list.) > > my command: > > > > /home/huikai/qemu15/bin/qemu --enable-kvm -m 768 -drive > > file=/home/huikai/winxp_dev.img,if=virtio -net nic,model=virtio -net > > user -usb -usbdevice tablet -localtime -vga qxl -device virtio-serial > > -chardev spicevmc,name=vdagent,id=vdagent -device > > virtserialport,chardev=vdagent,name=spice0 -spice > > port=1234,disable-ticketing -monitor > > telnet:localhost:12341,server,nowait > > Okay, I tried a variation of that: > qemu-system-x86_64 -cpu host -enable-kvm -m 1536 -pidfile > /home/rick/qemu/hds/wxp.pid -drive > file=/home/rick/qemu/hds/wxp.raw,if=virtio -net nic,model=virtio -net user > -localtime -usb -vga qxl -device virtio-serial -chardev > spicevmc,name=vdagent,id=vdagent -device > virtserialport,chardev=vdagent,name=spice0 -spice > port=1234,disable-ticketing -monitor telnet:localhost:12341,server,nowait > > And it's been running stable all day. > The differences between the command line that crashes and yours are: > - yours doesn't have "aio=native" in the -drive declaration. > - yours has some differences in the virtio-serial device declaration. > - yours has some differences in the virtserialport device declaration. > > As time permits I'm going to try each of those differences individually. Without "aio=native" ... in the definition of virtserialport, I changed "name=spice0" to "name=com.redhat.spice.0" - with this change, the guest vdagent works, but it crashed... > > Thanks, > -Rick
Re: [Qemu-devel] [Bug 818673] Re: virtio: trying to map MMIO memory
On Friday 16 September 2011 12:42:02 Rick Vernam wrote: > On Friday 16 September 2011 03:52:34 hkran wrote: > [snip] > > > I have tried many times with many restarts or shutdown-and-boot xp guest > > but failed to meet the crashing. > > (I am using the virtio drivers referenced in the earlier mail list.) > > my command: > > > > /home/huikai/qemu15/bin/qemu --enable-kvm -m 768 -drive > > file=/home/huikai/winxp_dev.img,if=virtio -net nic,model=virtio -net > > user -usb -usbdevice tablet -localtime -vga qxl -device virtio-serial > > -chardev spicevmc,name=vdagent,id=vdagent -device > > virtserialport,chardev=vdagent,name=spice0 -spice > > port=1234,disable-ticketing -monitor > > telnet:localhost:12341,server,nowait > > Okay, I tried a variation of that: > qemu-system-x86_64 -cpu host -enable-kvm -m 1536 -pidfile > /home/rick/qemu/hds/wxp.pid -drive > file=/home/rick/qemu/hds/wxp.raw,if=virtio -net nic,model=virtio -net user > -localtime -usb -vga qxl -device virtio-serial -chardev > spicevmc,name=vdagent,id=vdagent -device > virtserialport,chardev=vdagent,name=spice0 -spice > port=1234,disable-ticketing -monitor telnet:localhost:12341,server,nowait > > And it's been running stable all day. > The differences between the command line that crashes and yours are: > - yours doesn't have "aio=native" in the -drive declaration. > - yours has some differences in the virtio-serial device declaration. > - yours has some differences in the virtserialport device declaration. I added "aio=native" and it crashed. If it helps, I ran config like so: ./configure --target-list=x86_64-softmmu --disable-curses --disable-curl -- audio-drv-list=alsa --audio-card-list=sb16,ac97,hda --enable-vnc-thread -- disable-bluez --enable-vhost-net --enable-spice and I've attached config.log, as well as the output of configure. Thanks, -Rick gcc -D_FORTIFY_SOURCE=2 -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -Wstrict-prototypes -Wredundant-decls -Wall -Wundef -Wwrite-strings -Wmissing-prototypes -fno-strict-aliasing -c -o /tmp/qemu-conf-31139-7999-27429.o /tmp/qemu-conf-23994-7999-24982.c /tmp/qemu-conf-23994-7999-24982.c:2:2: error: #error Not defined gcc -D_FORTIFY_SOURCE=2 -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -Wstrict-prototypes -Wredundant-decls -Wall -Wundef -Wwrite-strings -Wmissing-prototypes -fno-strict-aliasing -c -o /tmp/qemu-conf-31139-7999-27429.o /tmp/qemu-conf-23994-7999-24982.c gcc -D_FORTIFY_SOURCE=2 -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -Wstrict-prototypes -Wredundant-decls -Wall -Wundef -Wwrite-strings -Wmissing-prototypes -fno-strict-aliasing -c -o /tmp/qemu-conf-31139-7999-27429.o /tmp/qemu-conf-23994-7999-24982.c gcc -m64 -D_FORTIFY_SOURCE=2 -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -Wstrict-prototypes -Wredundant-decls -Wall -Wundef -Wwrite-strings -Wmissing-prototypes -fno-strict-aliasing -c -o /tmp/qemu-conf-31139-7999-27429.o /tmp/qemu-conf-23994-7999-24982.c /tmp/qemu-conf-23994-7999-24982.c: In function 'main': /tmp/qemu-conf-23994-7999-24982.c:1: warning: control reaches end of non-void function gcc -m64 -D_FORTIFY_SOURCE=2 -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -Wstrict-prototypes -Wredundant-decls -Wall -Wundef -Wwrite-strings -Wmissing-prototypes -fno-strict-aliasing -Werror -m64 -D_FORTIFY_SOURCE=2 -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -Wstrict-prototypes -Wredundant-decls -Wall -Wundef -Wwrite-strings -Wmissing-prototypes -fno-strict-aliasing -o /tmp/qemu-conf-25046-7999-13049.exe /tmp/qemu-conf-23994-7999-24982.c -m64 -g -Werror -fstack-protector-all gcc -m64 -D_FORTIFY_SOURCE=2 -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -Wstrict-prototypes -Wredundant-decls -Wall -Wundef -Wwrite-strings -Wmissing-prototypes -fno-strict-aliasing -fstack-protector-all -Werror -m64 -D_FORTIFY_SOURCE=2 -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -Wstrict-prototypes -Wredundant-decls -Wall -Wundef -Wwrite-strings -Wmissing-prototypes -fno-strict-aliasing -fstack-protector-all -o /tmp/qemu-conf-25046-7999-13049.exe /tmp/qemu-conf-23994-7999-24982.c -m64 -g -Werror -Wendif-labels gcc -m64 -D_FORTIFY_SOURCE=2 -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -Wstrict-prototypes -Wredundant-decls -Wall -Wundef -Wwrite-strings -Wmissing-prototypes -fno-strict-aliasing -fstack-protector-all -Wendif-labels -Werror -m64 -D_FORTIFY_SOURCE=2 -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -Wstrict-prototypes -Wredundant-decls -Wall -Wundef -Wwrite-strings -Wmissing-prototypes -fno-strict-aliasing -fstack-protector-all -Wendif-labels -o /tmp/qemu-conf-25046-7999-13049.exe /tmp/qemu-conf-23994-7999-24982.c -m64 -g -Werror -Wmissing-include-dirs gcc -m64 -D_FORTIFY_SOURCE=2 -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -Wstrict-prototypes -Wredundant-decls -Wall -Wundef -Wwrite-strings -Wmissing-prototypes -fno-strict-aliasing -fstack-protector-all -Wendif-labels -Wmissing
Re: [Qemu-devel] [Bug 818673] Re: virtio: trying to map MMIO memory
On Friday 16 September 2011 03:52:34 hkran wrote: [snip] > > I have tried many times with many restarts or shutdown-and-boot xp guest > but failed to meet the crashing. > (I am using the virtio drivers referenced in the earlier mail list.) > my command: > > /home/huikai/qemu15/bin/qemu --enable-kvm -m 768 -drive > file=/home/huikai/winxp_dev.img,if=virtio -net nic,model=virtio -net > user -usb -usbdevice tablet -localtime -vga qxl -device virtio-serial > -chardev spicevmc,name=vdagent,id=vdagent -device > virtserialport,chardev=vdagent,name=spice0 -spice > port=1234,disable-ticketing -monitor telnet:localhost:12341,server,nowait Okay, I tried a variation of that: qemu-system-x86_64 -cpu host -enable-kvm -m 1536 -pidfile /home/rick/qemu/hds/wxp.pid -drive file=/home/rick/qemu/hds/wxp.raw,if=virtio -net nic,model=virtio -net user -localtime -usb -vga qxl -device virtio-serial -chardev spicevmc,name=vdagent,id=vdagent -device virtserialport,chardev=vdagent,name=spice0 -spice port=1234,disable-ticketing -monitor telnet:localhost:12341,server,nowait And it's been running stable all day. The differences between the command line that crashes and yours are: - yours doesn't have "aio=native" in the -drive declaration. - yours has some differences in the virtio-serial device declaration. - yours has some differences in the virtserialport device declaration. As time permits I'm going to try each of those differences individually. Thanks, -Rick
Re: [Qemu-devel] [Bug 818673] Re: virtio: trying to map MMIO memory
On 09/16/2011 03:37 AM, Rick Vernam wrote: On Thursday 15 September 2011 11:23:53 Rick Vernam wrote: On Wednesday 14 September 2011 16:30:11 Rick Vernam wrote: On Wednesday 14 September 2011 14:42:09 vrozenfe wrote: Thank you, Rick. Could you help me to narrow this problem down? Absolutely. As I see, you have three virtio drivers installed on your system - block, net, and virtio serial. Technically, anyone of them can create "trying to map MMIO memory" problem. The best way to find a buggy driver ( or drivers) will be to isolate one from the other. If you can, please try running only one virtio device every time to see which driver sends incorrect scatter/gather list element to QEMU. Sure, no problem. I'll have that in the next few days. I started qemu without any of the virt-serial stuff, specfically: qemu-system-x86_64 -cpu host -enable-kvm -pidfile /home/rick/qemu/hds/wxp.pid - drive file=/home/rick/qemu/hds/wxp.raw,if=virtio,aio=native -m 1536 -name WinXP -net nic,model=virtio -net user -localtime -usb -vga qxl -spice port=1234,disable-ticketing -monitor stdio It's been running for around 2 hours and no crash yet. So without virt-serial, the machine ran until I rebooted the guest OS, then crashed with the same error message. Without virt-serial it seemed to be stable so long as it was just left running. Now I'll run it without virt-net, and let you know how that goes. Thanks, -Rick Another question. You said, the problem happens after every second or third restart. Do you shutdown your VM, or just restart it? Have to shut down the VM guest so that the qemu process exits. How does it work after going through several hibernate/resume, and/or suspend/resume cycles. I often will suspend with or without pausing qemu (via monitor commands 'stop' and 'cont'). I have never experienced any problem with the qemu process that was running prior to the suspend. Best regards, Vadim. Thanks, -Rik I have tried many times with many restarts or shutdown-and-boot xp guest but failed to meet the crashing. (I am using the virtio drivers referenced in the earlier mail list.) my command: /home/huikai/qemu15/bin/qemu --enable-kvm -m 768 -drive file=/home/huikai/winxp_dev.img,if=virtio -net nic,model=virtio -net user -usb -usbdevice tablet -localtime -vga qxl -device virtio-serial -chardev spicevmc,name=vdagent,id=vdagent -device virtserialport,chardev=vdagent,name=spice0 -spice port=1234,disable-ticketing -monitor telnet:localhost:12341,server,nowait
Re: [Qemu-devel] [Bug 818673] Re: virtio: trying to map MMIO memory
On Thursday 15 September 2011 11:23:53 Rick Vernam wrote: > On Wednesday 14 September 2011 16:30:11 Rick Vernam wrote: > > On Wednesday 14 September 2011 14:42:09 vrozenfe wrote: > > > Thank you, Rick. > > > > > > Could you help me to narrow this problem down? > > > > Absolutely. > > > > > As I see, you have three virtio drivers installed on your system - > > > block, net, and virtio serial. Technically, anyone of them can create > > > "trying to map MMIO memory" problem. The best way to find a buggy > > > driver ( or drivers) will be to isolate one from the other. If you > > > can, please try running only one virtio device every time to see which > > > driver sends incorrect scatter/gather list element to QEMU. > > > > Sure, no problem. I'll have that in the next few days. > > I started qemu without any of the virt-serial stuff, specfically: > qemu-system-x86_64 -cpu host -enable-kvm -pidfile > /home/rick/qemu/hds/wxp.pid - drive > file=/home/rick/qemu/hds/wxp.raw,if=virtio,aio=native -m 1536 -name WinXP > -net nic,model=virtio -net user -localtime -usb -vga qxl -spice > port=1234,disable-ticketing -monitor stdio > > It's been running for around 2 hours and no crash yet. So without virt-serial, the machine ran until I rebooted the guest OS, then crashed with the same error message. Without virt-serial it seemed to be stable so long as it was just left running. Now I'll run it without virt-net, and let you know how that goes. > > Thanks, > -Rick > > > > Another question. You said, the problem happens after every second or > > > third restart. Do you shutdown your VM, or just restart it? > > > > Have to shut down the VM guest so that the qemu process exits. > > > > > How does it work > > > after going through several hibernate/resume, and/or suspend/resume > > > cycles. > > > > I often will suspend with or without pausing qemu (via monitor commands > > 'stop' and 'cont'). I have never experienced any problem with the qemu > > process that was running prior to the suspend. > > > > > Best regards, > > > Vadim. > > > > Thanks, > > -Rik -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/818673 Title: virtio: trying to map MMIO memory Status in QEMU: New Bug description: Qemu host is Core i7, running Linux. Guest is Windows XP sp3. Often, qemu will crash shortly after starting (1-5 minutes) with a statement "qemu-system-x86_64: virtio: trying to map MMIO memory" This has occured with qemu-kvm 0.14, qemu-kvm 0.14.1, qemu-0.15.0-rc0 and qemu 0.15.0-rc1. Qemu is started as such: qemu-system-x86_64 -cpu host -enable-kvm -pidfile /home/rick/qemu/hds/wxp.pid -drive file=/home/rick/qemu/hds/wxp.raw,if=virtio -m 768 -name WinXP -net nic,model=virtio -net user -localtime -usb -vga qxl -device virtio-serial -chardev spicevmc,name=vdagent,id=vdagent -device virtserialport,chardev=vdagent,name=com.redhat.spice.0 -spice port=1234,disable-ticketing -daemonize -monitor telnet:localhost:12341,server,nowait The WXP guest has virtio 1.1.16 drivers for net and scsi, and the most current spice binaries from spice-space.org. To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/818673/+subscriptions
Re: [Qemu-devel] [Bug 818673] Re: virtio: trying to map MMIO memory
On Wednesday 14 September 2011 16:30:11 Rick Vernam wrote: > On Wednesday 14 September 2011 14:42:09 vrozenfe wrote: > > Thank you, Rick. > > > > Could you help me to narrow this problem down? > > Absolutely. > > > As I see, you have three virtio drivers installed on your system - block, > > net, and virtio serial. Technically, anyone of them can create "trying to > > map MMIO memory" problem. The best way to find a buggy driver ( or > > drivers) will be to isolate one from the other. If you can, please try > > running only one virtio device every time to see which driver sends > > incorrect scatter/gather list element to QEMU. > > Sure, no problem. I'll have that in the next few days. I started qemu without any of the virt-serial stuff, specfically: qemu-system-x86_64 -cpu host -enable-kvm -pidfile /home/rick/qemu/hds/wxp.pid - drive file=/home/rick/qemu/hds/wxp.raw,if=virtio,aio=native -m 1536 -name WinXP -net nic,model=virtio -net user -localtime -usb -vga qxl -spice port=1234,disable-ticketing -monitor stdio It's been running for around 2 hours and no crash yet. Thanks, -Rick > > > Another question. You said, the problem happens after every second or > > third restart. Do you shutdown your VM, or just restart it? > > Have to shut down the VM guest so that the qemu process exits. > > > How does it work > > after going through several hibernate/resume, and/or suspend/resume > > cycles. > > I often will suspend with or without pausing qemu (via monitor commands > 'stop' and 'cont'). I have never experienced any problem with the qemu > process that was running prior to the suspend. > > > Best regards, > > Vadim. > > Thanks, > -Rik
Re: [Qemu-devel] [Bug 818673] Re: virtio: trying to map MMIO memory
On Wednesday 14 September 2011 14:42:09 vrozenfe wrote: > Thank you, Rick. > > Could you help me to narrow this problem down? Absolutely. > > As I see, you have three virtio drivers installed on your system - block, > net, and virtio serial. Technically, anyone of them can create "trying to > map MMIO memory" problem. The best way to find a buggy driver ( or > drivers) will be to isolate one from the other. If you can, please try > running only one virtio device every time to see which driver sends > incorrect scatter/gather list element to QEMU. Sure, no problem. I'll have that in the next few days. > > Another question. You said, the problem happens after every second or third > restart. Do you shutdown your VM, or just restart it? Have to shut down the VM guest so that the qemu process exits. > How does it work > after going through several hibernate/resume, and/or suspend/resume > cycles. I often will suspend with or without pausing qemu (via monitor commands 'stop' and 'cont'). I have never experienced any problem with the qemu process that was running prior to the suspend. > > Best regards, > Vadim. Thanks, -Rik -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/818673 Title: virtio: trying to map MMIO memory Status in QEMU: New Bug description: Qemu host is Core i7, running Linux. Guest is Windows XP sp3. Often, qemu will crash shortly after starting (1-5 minutes) with a statement "qemu-system-x86_64: virtio: trying to map MMIO memory" This has occured with qemu-kvm 0.14, qemu-kvm 0.14.1, qemu-0.15.0-rc0 and qemu 0.15.0-rc1. Qemu is started as such: qemu-system-x86_64 -cpu host -enable-kvm -pidfile /home/rick/qemu/hds/wxp.pid -drive file=/home/rick/qemu/hds/wxp.raw,if=virtio -m 768 -name WinXP -net nic,model=virtio -net user -localtime -usb -vga qxl -device virtio-serial -chardev spicevmc,name=vdagent,id=vdagent -device virtserialport,chardev=vdagent,name=com.redhat.spice.0 -spice port=1234,disable-ticketing -daemonize -monitor telnet:localhost:12341,server,nowait The WXP guest has virtio 1.1.16 drivers for net and scsi, and the most current spice binaries from spice-space.org. To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/818673/+subscriptions
Re: [Qemu-devel] [Bug 818673] Re: virtio: trying to map MMIO memory
On Thu, 2011-08-25 at 16:54 +0100, Stefan Hajnoczi wrote: > On Thu, Aug 25, 2011 at 3:53 PM, David Rando wrote: > > Do you know if it's something related to the virtio net driver? anyone > > tried going to the e1000 only? i have some machines with e1000 and some > > of them with virtio-net, but i have crash no matter what driver is using > > (but the virtio driver is installed anyway, despite i'm using the > > e1000). > > > > I was searching in the git repository for windows drivers, > > (http://git.kernel.org/?p=virt/kvm/kvm-guest-drivers- > > windows.git;a=history;f=NetKVM/Common/ndis56common.h;hb=HEAD ) but > > couldn't find anything related to this. > > > > Any news? i can't debug the driver, i would do it if i knew how. > > > > David Rando. > > > > -- > > You received this bug notification because you are a member of qemu- > > devel-ml, which is subscribed to QEMU. > > https://bugs.launchpad.net/bugs/818673 > > > > Title: > > virtio: trying to map MMIO memory > > > > Status in QEMU: > > New > > > > Bug description: > > Qemu host is Core i7, running Linux. Guest is Windows XP sp3. > > Often, qemu will crash shortly after starting (1-5 minutes) with a > > statement "qemu-system-x86_64: virtio: trying to map MMIO memory" > > This has occured with qemu-kvm 0.14, qemu-kvm 0.14.1, qemu-0.15.0-rc0 and > > qemu 0.15.0-rc1. > > Qemu is started as such: > > qemu-system-x86_64 -cpu host -enable-kvm -pidfile > > /home/rick/qemu/hds/wxp.pid -drive > > file=/home/rick/qemu/hds/wxp.raw,if=virtio -m 768 -name WinXP -net > > nic,model=virtio -net user -localtime -usb -vga qxl -device virtio-serial > > -chardev spicevmc,name=vdagent,id=vdagent -device > > virtserialport,chardev=vdagent,name=com.redhat.spice.0 -spice > > port=1234,disable-ticketing -daemonize -monitor > > telnet:localhost:12341,server,nowait > > The WXP guest has virtio 1.1.16 drivers for net and scsi, and the most > > current spice binaries from spice-space.org. > > > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/qemu/+bug/818673/+subscriptions > > Vadim, > Have you had any luck reproducing this issue or any advice for David? Guys, I'm sorry. Not yet. I'll try my best to trace this problem on the following weekend. Best, Vadim. > > Thanks, > Stefan
Re: [Qemu-devel] [Bug 818673] Re: virtio: trying to map MMIO memory
On Thu, Aug 25, 2011 at 3:53 PM, David Rando wrote: > Do you know if it's something related to the virtio net driver? anyone > tried going to the e1000 only? i have some machines with e1000 and some > of them with virtio-net, but i have crash no matter what driver is using > (but the virtio driver is installed anyway, despite i'm using the > e1000). > > I was searching in the git repository for windows drivers, > (http://git.kernel.org/?p=virt/kvm/kvm-guest-drivers- > windows.git;a=history;f=NetKVM/Common/ndis56common.h;hb=HEAD ) but > couldn't find anything related to this. > > Any news? i can't debug the driver, i would do it if i knew how. > > David Rando. > > -- > You received this bug notification because you are a member of qemu- > devel-ml, which is subscribed to QEMU. > https://bugs.launchpad.net/bugs/818673 > > Title: > virtio: trying to map MMIO memory > > Status in QEMU: > New > > Bug description: > Qemu host is Core i7, running Linux. Guest is Windows XP sp3. > Often, qemu will crash shortly after starting (1-5 minutes) with a statement > "qemu-system-x86_64: virtio: trying to map MMIO memory" > This has occured with qemu-kvm 0.14, qemu-kvm 0.14.1, qemu-0.15.0-rc0 and > qemu 0.15.0-rc1. > Qemu is started as such: > qemu-system-x86_64 -cpu host -enable-kvm -pidfile > /home/rick/qemu/hds/wxp.pid -drive file=/home/rick/qemu/hds/wxp.raw,if=virtio > -m 768 -name WinXP -net nic,model=virtio -net user -localtime -usb -vga qxl > -device virtio-serial -chardev spicevmc,name=vdagent,id=vdagent -device > virtserialport,chardev=vdagent,name=com.redhat.spice.0 -spice > port=1234,disable-ticketing -daemonize -monitor > telnet:localhost:12341,server,nowait > The WXP guest has virtio 1.1.16 drivers for net and scsi, and the most > current spice binaries from spice-space.org. > > To manage notifications about this bug go to: > https://bugs.launchpad.net/qemu/+bug/818673/+subscriptions Vadim, Have you had any luck reproducing this issue or any advice for David? Thanks, Stefan
Re: [Qemu-devel] [Bug 818673] Re: virtio: trying to map MMIO memory
On Sun, Aug 14, 2011 at 7:11 AM, Rick Vernam <818...@bugs.launchpad.net> wrote: > So that would point to virtio. This appears to be the place for virtio bugs, > correct? > Should I be doing anything to help usher this along? Either we need to help Vadim reproduce this so he can take a look. Vadim: were you able to reproduce this? Or someone interested in Windows driver debugging can see if they can debug this. The symptom is that the guest driver is placing invalid descriptors into the vring. QEMU tries to map the memory and finds the address is in a memory-mapped I/O region instead of a RAM region. Normally the vring descriptors only point into RAM, so this is a guest driver bug where the vring is being corrupted somehow. If anyone wants to take a look I can try to help guide them along the virtio-specifics. Stefan
