mail archive Server bug tracker changes
ubuntu-server-bugs.lists.ubuntu.com
(List home) (Recent threads) (280 other Ubuntu lists)
Subscription Options
- RSS or Atom: Read-only subscription using a browser or aggregator. This is the recommended way if you don't need to send messages to the list. You can learn more about feed syndication and clients here.
- Conventional: All messages are delivered to your mail address, and you can reply. To subscribe, send an email to the list's subscribe address with "subscribe" in the subject line, or visit the list's homepage here.
- High traffic list: 30+ messages per day
- This list contains about 96,679 messages, beginning Feb 2008
- 90 messages added yesterday
Report the Spam
This button sends a spam report to the moderator. Please use it sparingly. For other removal requests, read this.
Are you sure? yes no
[NEW] qemu-kvm windows 2003 block virtio problem
Ad
Public bug reported: Binary package hint: qemu-kvm Description: Ubuntu lucid (development branch) Release: 10.04 qemu-kvm: 0.12.3+noroms-0ubuntu6 windows 2003 guest on qemu-kvm with viostor block drivers should boot and operate normally with viostor release "viostor-31-03-2010-floppy.img" from http://www.linux-kvm.com/content/block-driver... but it doesnt work. system show 100% cpu usage, screen is black and nothing happens. ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: qemu-kvm 0.12.3+noroms-0ubuntu6 ProcVersionSignature: Ubuntu 2.6.32-21.32-generic 2.6.32.11+drm33.2 Uname: Linux 2.6.32-21-generic x86_64 Architecture: amd64 Date: Fri Apr 23 21:29:07 2010 InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Beta amd64 (20100406.1) KvmCmdLine: Error: command ['ps', '-C', 'kvm', '-F'] failed with exit code 1: UID PID PPID C SZ RSS PSR STIME TTY TIME CMD MachineType: ASUSTeK Computer Inc. F6A ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-21-generic root=UUID=e72e3b0a-ac01-45c0-90de-ee0ee23e9d14 ro quiet splash ProcEnviron: LANG=pl_PL.utf8 SHELL=/bin/bash SourcePackage: qemu-kvm dmi.bios.date: 10/20/2008 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 207 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: F6A dmi.board.vendor: ASUSTeK Computer Inc. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK Computer Inc. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr207:bd10/20/2008:svnASUSTeKComputerInc.:pnF6A:pvr1.0:rvnASUSTeKComputerInc.:rnF6A:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0: dmi.product.name: F6A dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK Computer Inc. ** Affects: qemu-kvm (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug lucid
** Attachment added: "BootDmesg.txt" http://launchpadlibrarian.net/45122279/BootDm... ** Attachment added: "CurrentDmesg.txt" http://launchpadlibrarian.net/45122280/Curren... ** Attachment added: "Dependencies.txt" http://launchpadlibrarian.net/45122281/Depend... ** Attachment added: "Lspci.txt" http://launchpadlibrarian.net/45122282/Lspci.... ** Attachment added: "Lsusb.txt" http://launchpadlibrarian.net/45122283/Lsusb.... ** Attachment added: "ProcCpuinfo.txt" http://launchpadlibrarian.net/45122284/ProcCp... ** Attachment added: "ProcInterrupts.txt" http://launchpadlibrarian.net/45122285/ProcIn... ** Attachment added: "ProcModules.txt" http://launchpadlibrarian.net/45122286/ProcMo... ** Attachment added: "RelatedPackageVersions.txt" http://launchpadlibrarian.net/45122287/Relate... ** Attachment added: "UdevDb.txt" http://launchpadlibrarian.net/45122288/UdevDb... ** Attachment added: "UdevLog.txt" http://launchpadlibrarian.net/45122290/UdevLo...
Thank you for taking the time to report this bug and helping to make Ubuntu better. Please answer these questions:
1. Is this reproducible?
2. If so, what specific steps should we take to recreate this bug? Be as detailed as possible.
This will help us to find and resolve the problem.
** Changed in: qemu-kvm (Ubuntu)
Importance: Undecided => Low
** Changed in: qemu-kvm (Ubuntu)
Status: New => Incomplete
it is reproducible (tested on another configuration - dell optiplex 580) download viostor windows 2003 32-bit drivers image from: http://www.linux-kvm.com/sites/default/files/... to /var/lib/libvirt/images/ put windows 2003 server installation iso to /var/lib/libvirt/images/w2k3sp2.iso create lvm volume for vm sotrage (in this example 20GB volume at /dev/vg/w2k3). launch qemu-kvm windows 2003 server installer with additional mounted floppy with image from above and with lvm volume as virtio block device. when installation begin hit F6 and add additional drivers for block device and choose windows 2003 32-bit. follow installation instructions. when installation finish and system should start (second reboot) screen goes black, cpu load is 100% and nothing happens. attached example libvirt configuration. below example qemu parameters: /usr/bin/kvm -M pc-0.12 -enable-kvm -m 512 -smp 1 -name w2k3 -localtime -boot c -drive file=/var/lib/libvirt/images/w2k3sp2.iso,if=ide,media=cdrom,index=2,format=raw -drive file=/var/lib/libvirt/images/viostor-31-03-2010-floppy.img,if=floppy,index=0,format=raw -drive file=/dev/vg/w2k3,if=virtio,index=0,boot=on,format=raw -net nic,macaddr=52:54:00:67:2e:84,vlan=0,name=nic.0 -net tap,fd=38,vlan=0,name=tap.0 -vga cirrus -monitor stdio ** Attachment added: "libvirt configuration" http://launchpadlibrarian.net/45567795/w2k3.x...
I have the same problem with win2003 guests on lucid. Thread goes to
100% cpu usage and is unreponsive. I am not using viostor at all though.