[ kvm-Bugs-2998292 ] XP Guest Crash on Ubuntu 10.04
Bugs item #2998292, was opened at 2010-05-08 01:28 Message generated for change (Comment added) made by epipe You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=893831aid=2998292group_id=180599 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open Resolution: None Priority: 7 Private: No Submitted By: cheesewright () Assigned to: Nobody/Anonymous (nobody) Summary: XP Guest Crash on Ubuntu 10.04 Initial Comment: OS: Ubuntu Server 64-bit 10.04, kernel 2.6.32 Server: Supermicro X8DTN+ 2x Xeon E5530 2.4GHz Nehalem quad core cpu, 12GB RAM Guest: Windows XP SP3 32-bit Below is my kvm command line: /usr/bin/kvm -S -M pc-0.11 -enable-kvm -m 1024 -smp 2 -name data2 -uuid 9a85ee7a-4db9-9108-df3c-61d04d3c943d -chardev socket,id=monitor,path=/var/lib/libvirt/qemu/data2.monitor,server,nowait -monitor chardev:monitor -localtime -boot c -drive file=/san/data2/winxp.img,if=ide,index=0,boot=on -drive file=/dev/cdrom,if=ide,media=cdrom,index=2 -net nic,macaddr=52:54:00:38:a8:af,vlan=0,name=nic.0 -net tap,fd=62,vlan=0,name=tap.0 -chardev pty,id=serial0 -serial chardev:serial0 -parallel none -usb -usbdevice tablet -vnc 0.0.0.0:2,password -k en-us -vga cirrus I have two XP SP3 guests which crash frequently on random events when connecting via remote desktop. The Windows Event Log reports Event ID 1003. These errors result in either a system freeze or full reboot. There are several types of errors recorded: Event Source: System Error Event Category: (102) Event ID: 1003 Error code 0005, parameter1 04c0, parameter2 8653a6c8, parameter3 , parameter4 . Event Source: System Error Event Category: (102) Event ID: 1003 Error code 000a, parameter1 3008, parameter2 0002, parameter3 , parameter4 804ff806. Event Source: System Error Event Category: (102) Event ID: 1003 Error code 100a, parameter1 3008, parameter2 0002, parameter3 , parameter4 804ff806. -- Comment By: J Snabb (epipe) Date: 2011-04-28 16:48 Message: I am seeing this problem also. Using Debian packaged qemu-kvm 0.12.5+dfsg-5 with Debian Linux kernel 2.6.32-5-amd64 on similar hardware. kvm command line is: /usr/bin/kvm -S -M pc-0.12 -enable-kvm -m 1024 -smp 2,sockets=2,cores=1,threads=1 -name -uuid ---- -nodefaults -chardev socket,id=monitor,path=/var/lib/libvirt/qemu/.monitor,server,nowait -mon chardev=monitor,mode=readline -rtc base=utc -boot c -drive file=/dev//XXX,if=none,id=drive-ide0-0-0,boot=on,format=raw -device ide-drive,bus=ide.0,unit=0,drive=drive-ide0-0-0,id=ide0-0-0 -device rtl8139,vlan=0,id=net0,mac=XX:XX:XX:XX:XX:XX,bus=pci.0,addr=0x3 -net tap,fd=70,vlan=0,name=hostnet0 -chardev pty,id=serial0 -device isa-serial,chardev=serial0 -usb -vnc 127.0.0.1:6 -vga cirrus -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x6 -- Comment By: Jes Sorensen (jessorensen) Date: 2010-11-26 18:01 Message: Hi, Are you still able to reproduce this with uptodate kvm/qemu? If you are, would you mind opening a bug in https://bugs.launchpad.net/qemu and close this one ? Does this only happen when you access the systems via remote desktop? (I presume this is some windows thing?) Thanks, Jes -- Comment By: cheesewright () Date: 2010-05-08 01:32 Message: The crash also happens when using kvm -M pc-0.12. It is easily reproducible after clicking through windows such control panel apps, or web browsers, for a few minutes. -- You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=893831aid=2998292group_id=180599 -- To unsubscribe from this list: send the line unsubscribe kvm in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
[ kvm-Bugs-2998292 ] XP Guest Crash on Ubuntu 10.04
Bugs item #2998292, was opened at 2010-05-07 20:28 Message generated for change (Settings changed) made by jessorensen You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=893831aid=2998292group_id=180599 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Closed Resolution: Invalid Priority: 7 Private: No Submitted By: cheesewright () Assigned to: Nobody/Anonymous (nobody) Summary: XP Guest Crash on Ubuntu 10.04 Initial Comment: OS: Ubuntu Server 64-bit 10.04, kernel 2.6.32 Server: Supermicro X8DTN+ 2x Xeon E5530 2.4GHz Nehalem quad core cpu, 12GB RAM Guest: Windows XP SP3 32-bit Below is my kvm command line: /usr/bin/kvm -S -M pc-0.11 -enable-kvm -m 1024 -smp 2 -name data2 -uuid 9a85ee7a-4db9-9108-df3c-61d04d3c943d -chardev socket,id=monitor,path=/var/lib/libvirt/qemu/data2.monitor,server,nowait -monitor chardev:monitor -localtime -boot c -drive file=/san/data2/winxp.img,if=ide,index=0,boot=on -drive file=/dev/cdrom,if=ide,media=cdrom,index=2 -net nic,macaddr=52:54:00:38:a8:af,vlan=0,name=nic.0 -net tap,fd=62,vlan=0,name=tap.0 -chardev pty,id=serial0 -serial chardev:serial0 -parallel none -usb -usbdevice tablet -vnc 0.0.0.0:2,password -k en-us -vga cirrus I have two XP SP3 guests which crash frequently on random events when connecting via remote desktop. The Windows Event Log reports Event ID 1003. These errors result in either a system freeze or full reboot. There are several types of errors recorded: Event Source: System Error Event Category: (102) Event ID: 1003 Error code 0005, parameter1 04c0, parameter2 8653a6c8, parameter3 , parameter4 . Event Source: System Error Event Category: (102) Event ID: 1003 Error code 000a, parameter1 3008, parameter2 0002, parameter3 , parameter4 804ff806. Event Source: System Error Event Category: (102) Event ID: 1003 Error code 100a, parameter1 3008, parameter2 0002, parameter3 , parameter4 804ff806. -- Comment By: Jes Sorensen (jessorensen) Date: 2011-04-28 11:52 Message: This bug tracker isn't taking any new bugs, please submit your bug in https://bugs.launchpad.net/qemu/ In addition this is against a vendor kernel (Ubuntu), so please start by filing the bug with them. Thanks, Jes -- Comment By: J Snabb (epipe) Date: 2011-04-28 11:48 Message: I am seeing this problem also. Using Debian packaged qemu-kvm 0.12.5+dfsg-5 with Debian Linux kernel 2.6.32-5-amd64 on similar hardware. kvm command line is: /usr/bin/kvm -S -M pc-0.12 -enable-kvm -m 1024 -smp 2,sockets=2,cores=1,threads=1 -name -uuid ---- -nodefaults -chardev socket,id=monitor,path=/var/lib/libvirt/qemu/.monitor,server,nowait -mon chardev=monitor,mode=readline -rtc base=utc -boot c -drive file=/dev//XXX,if=none,id=drive-ide0-0-0,boot=on,format=raw -device ide-drive,bus=ide.0,unit=0,drive=drive-ide0-0-0,id=ide0-0-0 -device rtl8139,vlan=0,id=net0,mac=XX:XX:XX:XX:XX:XX,bus=pci.0,addr=0x3 -net tap,fd=70,vlan=0,name=hostnet0 -chardev pty,id=serial0 -device isa-serial,chardev=serial0 -usb -vnc 127.0.0.1:6 -vga cirrus -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x6 -- Comment By: Jes Sorensen (jessorensen) Date: 2010-11-26 12:01 Message: Hi, Are you still able to reproduce this with uptodate kvm/qemu? If you are, would you mind opening a bug in https://bugs.launchpad.net/qemu and close this one ? Does this only happen when you access the systems via remote desktop? (I presume this is some windows thing?) Thanks, Jes -- Comment By: cheesewright () Date: 2010-05-07 20:32 Message: The crash also happens when using kvm -M pc-0.12. It is easily reproducible after clicking through windows such control panel apps, or web browsers, for a few minutes. -- You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=893831aid=2998292group_id=180599 -- To unsubscribe from this list: send the line unsubscribe kvm in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
[ kvm-Bugs-1814637 ] Windows 2000 setup unstable
Bugs item #1814637, was opened at 2007-10-16 20:39 Message generated for change (Comment added) made by jessorensen You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=893831aid=1814637group_id=180599 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Closed Resolution: Out of Date Priority: 5 Private: No Submitted By: Technologov (technologov) Assigned to: Nobody/Anonymous (nobody) Summary: Windows 2000 setup unstable Initial Comment: The testing reveals that Windows 2000 setup stucks very often after the reboot and before the Regional Settings stage. Host: Fedora7, 64-bit, Intel CPU, KVM-46. (A different error happens on AMD machines. But this bug focuses on Intel) Those errors are not always reproduceble, and those fail about half of the time. Tested with: qemu-kvm -hda /disks/win2000.vmdk -cdrom /iso/win2000.iso -m 128 -boot d -Alexey Technologov. 16.10.2007. -- Comment By: Jes Sorensen (jessorensen) Date: 2011-03-03 10:29 Message: No reply from bug submitter to query of June 11, so closing as out of date. -- Comment By: Jes Sorensen (jessorensen) Date: 2010-06-11 11:16 Message: Hi, Again looking through old bugs Could you please let us know if this is still a problem with a recent QEMU/KVM. If not, lets close this bug. Thanks, Jes -- Comment By: Technologov (technologov) Date: 2007-11-01 12:59 Message: Logged In: YES user_id=1839746 Originator: YES Update: this seems to be VMDK-related issue. Windows 2000 setup works fine with qcow2 and raw formats. -Technologov -- Comment By: Technologov (technologov) Date: 2007-11-01 08:17 Message: Logged In: YES user_id=1839746 Originator: YES Update: There are 3 ways to see if you have buggy version of KVM - 1. Detecting devices setup step in the buggy version takes ~25-30 minutes. 2. You will get not enough disk space (-win2k-hack will not help you!) 3. You will get strange error saying: SAM User database damaged and setup will close. KVM-36-1 seems to be the commit, that destroyed Windows 2000. (SHA: 263773f7a6606efda85f7b184a067b5f560ed39b) -Technologov -- Comment By: Technologov (technologov) Date: 2007-10-17 19:31 Message: Logged In: YES user_id=1839746 Originator: YES While this is strange, but this Win2000 stage often succeeds if I want about 20 minutes. Just usually people don't have that _much_ patience, and they shut down VMs in about 5 minutes of non-progress. -Technologov -- Comment By: Technologov (technologov) Date: 2007-10-17 10:00 Message: Logged In: YES user_id=1839746 Originator: YES File Added: KVM46-VMX64-Windows2000-loop-screenshot.jpg -- Comment By: Technologov (technologov) Date: 2007-10-17 09:45 Message: Logged In: YES user_id=1839746 Originator: YES Update: The guest is not fully dead: the mouse responds, but it is looped forever trying to detect some kind of hardware. I made strace logs screenshot. -Technologov -- You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=893831aid=1814637group_id=180599 -- To unsubscribe from this list: send the line unsubscribe kvm in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
[ kvm-Bugs-1858949 ] USB is unstable
Bugs item #1858949, was opened at 2007-12-27 15:26 Message generated for change (Comment added) made by jessorensen You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=893831aid=1858949group_id=180599 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Closed Resolution: Out of Date Priority: 5 Private: No Submitted By: Technologov (technologov) Assigned to: Nobody/Anonymous (nobody) Summary: USB is unstable Initial Comment: USB often locks up VMs/slows down/loses responsiveness/or BSODs. Windows XP VM loses responsiveness is the most common scenario. This is especially true for complex, multi-function USB devices. Some simpler devices work. Tested on: Intel 64, F7/x64, KVM-58. It happens both with KVM and -no-kvm. -Alexey Technologov, 27.12.2007. -- Comment By: Jes Sorensen (jessorensen) Date: 2011-03-03 10:30 Message: No reply to question of June 11 (8 months ago), closing as out of date -- Comment By: Jes Sorensen (jessorensen) Date: 2010-06-11 15:36 Message: Could you please test against a recent QEMU/KVM and let us know if this is still a problem? If it is still a problem, it would be ideal if you could open a launchpad bug instead and close this one. Thanks, Jes -- Comment By: Technologov (technologov) Date: 2008-01-11 10:59 Message: Logged In: YES user_id=1839746 Originator: YES Bug still exists, reopened. -- Comment By: SourceForge Robot (sf-robot) Date: 2008-01-11 04:20 Message: Logged In: YES user_id=1312539 Originator: NO This Tracker item was closed automatically by the system. It was previously set to a Pending status, and the original submitter did not respond within 14 days (the time period specified by the administrator of this Tracker). -- Comment By: Amit Shah (amitshah) Date: 2007-12-27 18:39 Message: Logged In: YES user_id=201894 Originator: NO Do these complex multi-function devices cause this with slightly older kvm userspace? Like = kvm-56? -- Comment By: Technologov (technologov) Date: 2007-12-27 16:40 Message: Logged In: YES user_id=1839746 Originator: YES update: The problem happens when you plug-in some USB 1.1 and/or 2.0 devices into Windows XP guest. Some USB Flash disks cause that. -- You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=893831aid=1858949group_id=180599 -- To unsubscribe from this list: send the line unsubscribe kvm in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
[ kvm-Bugs-2104487 ] Soft lockups when installing RHEL5 over PXE
Bugs item #2104487, was opened at 2008-09-11 00:07 Message generated for change (Comment added) made by jessorensen You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=893831aid=2104487group_id=180599 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: intel Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Shawn starr (sh0nx) Assigned to: Nobody/Anonymous (nobody) Summary: Soft lockups when installing RHEL5 over PXE Initial Comment: CPU Type: = Family: 15 Model: 6 Stepping: 2 model name: Intel(R) Pentium(R) D CPU 3.00GHz This CPU has VT extensions Steps to reproduce (you may need to retry a few times to trigger this to fail) 1) Try to install RHEL 5.1 64bit guest with a PXE installation. Not using any virtio drivers. 2) Sometimes when trying to format a disk CPU gets stuck, install hangs but the vm is still responsive to control (reboot, etc) 3) I have a 32bit Windows XP VM running also with kvm * Note: If it doesn't soft lockup, on reboot into the newly installed VM, ssh-keygen segfaults (this has happened 3 times). KVM version: (kvm 75 snapshot) [ 1489.698357] loaded kvm module (kvm-snapshot-20080909) RHEL5 64bit GUEST Crash Output: === 3BUG: soft lockup - CPU#0 stuck for 10s! [mke2fs:573] 4CPU 0: 4Modules linked in: dm_emc dm_round_robin dm_multipath dm_snapshot dm_mirror dm_zero dm_mod lock_nolock gfs2 ext3 jbd msdos raid456 xor raid1 raid0 ata_piix libata 8139cp mii uhci_hcd iscsi_ibft iscsi_tcp libiscsi scsi_transport_iscsi sr_mod sd_mod scsi_mod ide_cd cdrom squashfs pcspkr edd floppy loop nfs nfs_acl fscache lockd sunrpc vfat fat cramfs 4Pid: 573, comm: mke2fs Not tainted 2.6.18-92.el5 #1 4RIP: 0010:[80011ec7] [80011ec7] __do_softirq+0x53/0xd6 4RSP: 0018:80416f60 EFLAGS: 0206 4RAX: 0002 RBX: 803b5f80 RCX: 0080 4RDX: 810016431fd8 RSI: 0080 RDI: 81001f792040 4RBP: 80416ee0 R08: 0001 R09: 810080c29000 4R10: 0046 R11: 800076cd R12: 8005dc8e 4R13: 0002 R14: 80076f1d R15: 80416ee0 4FS: 2b486effcb90() GS:8039e000() knlGS: 4CS: 0010 DS: ES: CR0: 8005003b 4CR2: 2b486e684ef0 CR3: 1cbe7000 CR4: 06e0 4 4Call Trace: 4 IRQ [8005e2fc] call_softirq+0x1c/0x28 4 [8006c571] do_softirq+0x2c/0x85 4 [8005dc8e] apic_timer_interrupt+0x66/0x6c 4 EOI [800076cd] ide_outb+0x0/0x9 4 [80064aa8] _spin_unlock_irqrestore+0x8/0x9 4 [801c959a] do_rw_taskfile+0x198/0x1f4 4 [8000ecfb] ide_do_request+0x46a/0x78d 4 [800d3432] kmem_freepages+0xe6/0x110 4 [80137887] elv_insert+0xd6/0x1f7 4 [800413d3] ide_do_drive_cmd+0xc0/0x116 4 [801c97c0] ide_diag_taskfile+0xbe/0xcc 4 [80138a05] blk_end_sync_rq+0x0/0x2e 4 [801cc798] ide_cacheflush_p+0x6a/0x85 4 [8003f5ae] pagevec_lookup+0x17/0x1e 4 [801c9ace] task_no_data_intr+0x0/0x87 4 [801ccbb2] idedisk_release+0x31/0x9e 4 [80064bd5] lock_kernel+0x1b/0x32 4 [800dc1a2] __blkdev_put+0x6d/0x169 4 [800dc270] __blkdev_put+0x13b/0x169 4 [80012535] __fput+0xae/0x198 4 [800239d6] filp_close+0x5c/0x64 4 [8001d9e5] sys_close+0x88/0xa2 4 [8005d116] system_call+0x7e/0x83 4 6kjournald starting. Commit interval 5 seconds 6EXT3 FS on hda3, internal journal 6EXT3-fs: mounted filesystem with ordered data mode. -- Comment By: Jes Sorensen (jessorensen) Date: 2011-03-03 10:40 Message: Hi, Looking at old bugs - is this still a problem for you? Thanks, Jes -- Comment By: Shawn starr (sh0nx) Date: 2008-09-11 00:12 Message: Kernel is: 2.6.27-0.321.rc6.fc10.x86_64 -- You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=893831aid=2104487group_id=180599 -- To unsubscribe from this list: send the line unsubscribe kvm in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
[ kvm-Bugs-2113643 ] guests AND host still getting stuck under CPU load
Bugs item #2113643, was opened at 2008-09-16 09:34 Message generated for change (Comment added) made by jessorensen You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=893831aid=2113643group_id=180599 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Closed Resolution: Out of Date Priority: 5 Private: No Submitted By: Nikola Ciprich (nikola_ciprich) Assigned to: Nobody/Anonymous (nobody) Summary: guests AND host still getting stuck under CPU load Initial Comment: I'm experiencing problems with some KVM guests getting stuck for long time when all their CPUs are loaded. Host: 8xCPU intel, 2.6.26 x86_64, kvm-74, 12GB RAM Guest: 8XCPU, 2.6.24 x86_64 1GB RAM while doing kernel compilation on guest (using -j8), the guest sometimes hangs for long time, and on host I see: Sep 12 19:04:34 vbox1 [420515.344071] BUG: soft lockup - CPU#3 stuck for 99s! [qemu-system-x86:17351] Sep 12 19:04:34 vbox1 [420515.344071] Modules linked in: tun bitrev drbd lock_dlm gfs2 cn crc32 dlm configfs ipmi_si ipmi_devintf ipmi_m sghandler ipt_REJECT xt_tcpudp xt_multiport nf_conntrack_ipv4 xt_state nf_conntrack iptable_filter ip_tables x_tables kvm_intel kvm ipv6 nfs lockd nfs_acl sunrpc 8021q bridge llc dm_mirror dm_log dm_mod wmi sbs sbshc fan battery backlight acpi_memhotplug ac lp nvram e1000 e sg snd_seq_dummy snd_seq_oss snd_seq_midi_event snd_seq snd_seq_device snd_pcm_oss snd_mixer_oss piix snd_pcm container pata_acpi ide_ pci_generic snd_timer snd soundcore snd_page_alloc parport_pc parport thermal processor ata_piix ata_generic button rng_core thermal_sys iTCO_wdt rtc_cmos rtc_core rtc_lib i5000_edac shpchp i2c_i801 i2c_core pci_hotplug edac_core pcspkr ide_disk ide_core aic94xx libsas fi rmware_class scsi_transport_sas ahci libata dock sd_mod scsi_mod raid456 async_xor async_memcpy async_tx xor raid1 ext3 jbd uhci_hcd ohc i_hcd ehci_hcd [last unloaded: scsi_wait_scan] Sep 12 19:04:34 vbox1 [420515.344071] CPU 3: Sep 12 19:04:34 vbox1 [420515.344071] Pid: 17351, comm: qemu-system-x86 Not tainted 2.6.26lb.02 #1 Sep 12 19:04:34 vbox1 [420515.344071] RIP: 0010:[803e8cc1] [803e8cc1] sock_poll+0x11/0x20 Sep 12 19:04:34 vbox1 [420515.344071] RSP: 0018:8100bd355a50 EFLAGS: 0246 Sep 12 19:04:34 vbox1 [420515.344071] RAX: RBX: 0080 RCX: 804c3520 Sep 12 19:04:34 vbox1 [420515.344071] RDX: RSI: 8102632fe140 RDI: 8101b4c8bbc0 Sep 12 19:04:34 vbox1 [420515.344071] RBP: 810217faa800 R08: 0001 R09: 8029e9df Sep 12 19:04:34 vbox1 [420515.344071] R10: R11: R12: 8023e743 Sep 12 19:04:34 vbox1 [420515.344071] R13: 0001 R14: 8100bd355a08 R15: Sep 12 19:04:34 vbox1 [420515.344071] FS: 7f47f0a5e6f0() GS:81032fce65c0() knlGS: Sep 12 19:04:34 vbox1 [420515.344071] CS: 0010 DS: ES: CR0: 8005003b Sep 12 19:04:34 vbox1 [420515.344071] CR2: b7f43000 CR3: c01d6000 CR4: 26e0 Sep 12 19:04:34 vbox1 [420515.344071] DR0: DR1: DR2: Sep 12 19:04:34 vbox1 [420515.344071] DR3: DR6: 0ff0 DR7: 0400 Sep 12 19:04:34 vbox1 [420515.344071] Sep 12 19:04:34 vbox1 [420515.344071] Call Trace: Sep 12 19:04:34 vbox1 [420515.344071] [802ac800] ? do_select+0x330/0x590 Sep 12 19:04:34 vbox1 [420515.344071] [802ad040] ? __pollwait+0x0/0x130 Sep 12 19:04:34 vbox1 [420515.344071] [8022a440] ? default_wake_function+0x0/0x10 Sep 12 19:04:34 vbox1 [420515.344071] [8022a440] ? default_wake_function+0x0/0x10 Sep 12 19:04:34 vbox1 [420515.344071] [8022a440] ? default_wake_function+0x0/0x10 Sep 12 19:04:34 vbox1 [420515.344071] [8022a440] ? default_wake_function+0x0/0x10 Sep 12 19:04:34 vbox1 [420515.344071] [8022a440] ? default_wake_function+0x0/0x10 Sep 12 19:04:34 vbox1 [420515.344071] [8022a440] ? default_wake_function+0x0/0x10 Sep 12 19:04:34 vbox1 [420515.344071] [80249d99] ? autoremove_wake_function+0x9/0x30 Sep 12 19:04:34 vbox1 [420515.344071] [80227cca] ? __wake_up_common+0x5a/0x90 Sep 12 19:04:34 vbox1 [420515.344071] [80480a07] ? _spin_lock_irqsave+0x37/0x50 Sep 12 19:04:34 vbox1 [420515.344071] [a05624dd] ? :tun:tun_chr_aio_read+0x12d/0x3b0 Sep 12 19:04:34 vbox1 [420515.344071] [802acca9] ? core_sys_select+0x249/0x340 Sep 12 19:04:34 vbox1 [420515.344071] [80249d90] ? autoremove_wake_function+0x0/0x30 Sep 12 19:04:34 vbox1 [420515.344071] [a03e7c6e] ? :kvm:kvm_vm_ioctl+0x8e/0x270 Sep 12 19:04:34 vbox1 [420515.344071] [80316229] ? file_has_perm+0xe9/0xf0 Sep 12 19:04
[ kvm-Bugs-2121747 ] bug with kernel 0.0.1
Bugs item #2121747, was opened at 2008-09-21 15:58 Message generated for change (Comment added) made by jessorensen You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=893831aid=2121747group_id=180599 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Closed Resolution: Works For Me Priority: 5 Private: No Submitted By: mariuz (mapopa) Assigned to: Nobody/Anonymous (nobody) Summary: bug with kernel 0.0.1 Initial Comment: I have downloaded the linux kernel 0.0.1 image for qemu but it crashes the kvm (tested on hardy with kvm from repository ) http://kerneltrap.org/Linux/Dusting_Off_the_0.01_Kernel#comment-305046 sudo kvm -hdb hd_oldlinux.img -fda linux0.01-3.3.img -boot a -no-kvm-irqchip unhandled vm exit: 0x200101 vcpu_id 0 rax 000f rbx 000f rcx 00012660 rdx 0030 rsi 0001 rdi 0080 rsp 00013618 rbp 0013 r8 r9 r10 r11 r12 r13 r14 r15 rip 5834 rflags 0687 cs 0008 (/007f p 1 dpl 0 db 1 s 1 type b l 0 g 0 avl 0) ds 0010 (/007f p 1 dpl 0 db 1 s 1 type 3 l 0 g 1 avl 0) es 0010 (/007f p 1 dpl 0 db 1 s 1 type 3 l 0 g 1 avl 0) ss 0010 (/007f p 1 dpl 0 db 1 s 1 type 3 l 0 g 1 avl 0) fs 0017 (/0009 p 1 dpl 3 db 1 s 1 type 3 l 0 g 1 avl 0) gs 0017 (/0009 p 1 dpl 3 db 1 s 1 type 3 l 0 g 1 avl 0) tr 0020 (000127c0/0068 p 1 dpl 0 db 0 s 0 type 9 l 0 g 0 avl 0) ldt 0028 (000127a8/0068 p 1 dpl 0 db 0 s 0 type 2 l 0 g 0 avl 0) gdt 4878/7ff idt 4078/7ff cr0 8011 cr2 0 cr3 0 cr4 0 cr8 0 efer 0 Aborted -- Comment By: Jes Sorensen (jessorensen) Date: 2011-03-03 10:54 Message: kernel and disk image from http://draconux.free.fr/download/os-dev/linux0.01/Image/ boots just fine for me on a Fedora 14 system. closing -- You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=893831aid=2121747group_id=180599 -- To unsubscribe from this list: send the line unsubscribe kvm in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
[ kvm-Bugs-2122614 ] Guests do not boot (W2k/Lilo) when using boot=on flag
Bugs item #2122614, was opened at 2008-09-22 11:46 Message generated for change (Comment added) made by jessorensen You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=893831aid=2122614group_id=180599 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: intel Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: martinmaurer (martinmaurer) Assigned to: Nobody/Anonymous (nobody) Summary: Guests do not boot (W2k/Lilo) when using boot=on flag Initial Comment: I am working on KVM 75 (Debian 2.6.24 amd64 Kernel, but the error is also on KVM 71, others not tested) I used the following command (here for Windows 2000): With boot=on option: /usr/bin/kvm -smp 1 -localtime -k de -drive file=/var/lib/vz/images/115/vm-115-disk.qcow2,if=ide,index=0,boot=on -drive file=/var/lib/vz/template/iso/EN_WINDOWS_2000_PRO_SERVER_ADVSERVER.ISO,if=ide,index=2,media=cdrom -m 512 -net tap -net nic And get this: (see also screenshot) ___ Disk I/o error: Status = 0001 Disk I/o error: Status = 0001 Disk I/o error: Status = 0001 Windows 2000 could not start because the following file is missing or corrupt: windows 2000 root\system32\ntoskrnl.exe. ___ Without the boot=on option everything works: /usr/bin/kvm -smp 1 -localtime -k de -drive file=/var/lib/vz/images/115/vm-115-disk.qcow2,if=ide,index=0 -drive file=/var/lib/vz/template/iso/EN_WINDOWS_2000_PRO_SERVER_ADVSERVER.ISO,if=ide,index=2,media=cdrom -m 512 -net tap -net nic __ Linux with Lilo Bootloader: If you try to install a Linux with Lilo boot manager, the system does also not boot: LILO - Keytable read/checksum error (see screenshot) This issue is also easy reproducable, easiest way is to get a netinstall ISO for debian etch: http://cdimage.debian.org/debian-cd/4.0_r4a/i386/iso-cd/debian-40r4a-etchnhalf-i386-netinst.iso on the last step you need to point the installer not to use grub (just go back and select LILO to install). -- Comment By: Jes Sorensen (jessorensen) Date: 2011-03-03 10:56 Message: Hi, This really should not be an issue anymore - could you let us know if you still see this? Thanks, Jes -- You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=893831aid=2122614group_id=180599 -- To unsubscribe from this list: send the line unsubscribe kvm in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
[ kvm-Bugs-2135076 ] Lilo boot on virtio; keytable read / checksum error
Bugs item #2135076, was opened at 2008-09-29 04:02 Message generated for change (Comment added) made by jessorensen You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=893831aid=2135076group_id=180599 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: intel Group: None Status: Closed Resolution: Works For Me Priority: 5 Private: No Submitted By: Shen Okinudo (okinu) Assigned to: Nobody/Anonymous (nobody) Summary: Lilo boot on virtio; keytable read / checksum error Initial Comment: When booting a virtio disk using lilo (v1.22.8-3.1ubuntu1) on an intel 64 bit Ubuntu 8.04 guest, I get the message keytable read / checksum error. The host system is the same one. The problem exists since kvm-70 up to and including kvm-76. The same guest can be booted using kvm-69. The vm had been created using the qcow2 format. BTW, the current grub boot loader (0.97-29ubuntu21) does not work either. -- Comment By: Jes Sorensen (jessorensen) Date: 2011-03-03 10:57 Message: booting using virtio works just fine here on Intel systems - this seems to have been fixed a long time ago. Cheers, Jes -- You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=893831aid=2135076group_id=180599 -- To unsubscribe from this list: send the line unsubscribe kvm in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
[ kvm-Bugs-2235570 ] 100% cpu usage with KVM-78
Bugs item #2235570, was opened at 2008-11-07 18:58 Message generated for change (Settings changed) made by jessorensen You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=893831aid=2235570group_id=180599 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Closed Resolution: Out of Date Priority: 5 Private: No Submitted By: James Bailey (dgym) Assigned to: Nobody/Anonymous (nobody) Summary: 100% cpu usage with KVM-78 Initial Comment: When I start a guest it consumes 100% CPU on the host, even after it has booted and is sitting idle at a login prompt. The odd thing is that if I then live migrate the guest to another (identical) machine, the problem goes away. The guest continues to run just fine on the new host, and the new host's CPU usage is normal. I have tried the obvious: starting on the other machine and migrating to the first, and even multiple migrations. It is always the same, the qemu-system-x86_64 process sits at 100% unless it was started with -incoming ... Migrating machines every time you start up is not a very convenient work around, so it would be nice to find out what is different between the normal start up and the -incoming start up and fix the former. Versions and settings: KVM: 78 Host Kernel: Vanilla 2.6.25.2 Compiled with: gcc version 4.1.2 CPU: AMD Phenom Guest OS: Linux (have tried a few distros) Guest Kernels: Debian etch, and an OpenVZ 2.6.18 Command line: qemu-system-x86_64 -m 128 -smp 1 -drive file=/dev/drbd0 -vnc :1 Things I have tried which have not worked: Using -nographics. Using SDL graphics. Using -snapshot, and doing a savevm and loadvm. Things I have tried which have worked: Using -no-kvm. I have attached gdb and found the busy thread, here is its backtrace: #0 0x7f06f017ea17 in ioctl () from /lib/libc.so.6 #1 0x0051b423 in kvm_run (kvm=0xa93040, vcpu=0) at libkvm.c:892 #2 0x004f1116 in kvm_cpu_exec (env=value optimized out) at /opt/setup/kvm-78/qemu/qemu-kvm.c:230 #3 0x004f13e4 in ap_main_loop (_env=value optimized out) at /opt/setup/kvm-78/qemu/qemu-kvm.c:432 #4 0x7f06f0565135 in start_thread () from /lib/libpthread.so.0 #5 0x7f06f01852ce in clone () from /lib/libc.so.6 #6 0x in ?? () Because this indicates business within the kernel module it is as far as I have got. I will attempt to identify the previous working version, I know I never had this problem with 68, but I haven't yet tried anything in between. -- Comment By: Jes Sorensen (jessorensen) Date: 2011-03-03 10:59 Message: No reply to inquiry in November, and it seems to work for me, closing. -- Comment By: Jes Sorensen (jessorensen) Date: 2010-11-29 09:00 Message: Hi, Given that there has been no updates to this bug for a long time, I presume the problem has been resolved? Would you mind letting us know if you still see this problem? Thanks, Jes -- Comment By: James Bailey (dgym) Date: 2008-11-08 22:35 Message: Using the -no-kvm-pit option fixes the CPU problem. There were some changes to arch/x86/kvm/i8254.c so this definitely looks PIT related. -- Comment By: James Bailey (dgym) Date: 2008-11-08 21:28 Message: I have been able to narrow the problem down to a single commit. KVM-76 was fine, but I get this broken behaviour with KVM-77. I checked out the KVM userspace and went back to 76, and I also checked out the KVM kernel and tried different versions. Commit 666c4a43cba0cbaa30cd3c86b515dfdab2a6fa98 on git://git.kernel.org/pub/scm/linux/kernel/git/avi/kvm.git is the first version to show the 100% CPU behaviour. -- You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=893831aid=2235570group_id=180599 -- To unsubscribe from this list: send the line unsubscribe kvm in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
[ kvm-Bugs-2275173 ] savevm is extremely slow
Bugs item #2275173, was opened at 2008-11-13 09:36 Message generated for change (Comment added) made by jessorensen You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=893831aid=2275173group_id=180599 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Closed Resolution: Out of Date Priority: 5 Private: No Submitted By: Daniel van Vugt (danv) Assigned to: Nobody/Anonymous (nobody) Summary: savevm is extremely slow Initial Comment: In kvm-79, a 1.3MB snapshot has taken several minutes to savevm. In kvm-78 it was slightly faster taking only about one minute to savevm 2.4MB. It doesn't sound right to me. Also, Michael Tokarev is reporting the same thing on the kvm mailing list. kvm-79 Intel(R) Core(TM)2 Quad CPUQ6600 @ 2.40GHz Ubuntu 8.04 Desktop amd64(x86_64) -- Comment By: Jes Sorensen (jessorensen) Date: 2011-03-03 11:00 Message: No reply to inquiry of July 22, closing as out of date -- Comment By: Jes Sorensen (jessorensen) Date: 2010-07-22 18:23 Message: Are you still seeing this problem with uptodate KVM or can we close the bug? Thanks, Jes -- Comment By: Avi Kivity (avik) Date: 2008-11-23 19:44 Message: A temporary workaround is to use -drive file=...,cache=writeback -- You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=893831aid=2275173group_id=180599 -- To unsubscribe from this list: send the line unsubscribe kvm in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
[ kvm-Bugs-2725367 ] KVM userspace segfaults due to internal VNC server
Bugs item #2725367, was opened at 2009-04-01 18:57 Message generated for change (Comment added) made by jessorensen You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=893831aid=2725367group_id=180599 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: qemu Group: None Status: Closed Resolution: Works For Me Priority: 8 Private: No Submitted By: Technologov (technologov) Assigned to: Nobody/Anonymous (nobody) Summary: KVM userspace segfaults due to internal VNC server Initial Comment: KVM's internal VNC server is unstable. When running KVM (KVM-84 or 85rc2), the userspace segfaults when I try to connect to it with VNC client. Only some VNC clients can trigger it. It happens on both Intel AMD. I used TightVNC 1.3 client for Linux 64-bit. No problems happen with SDL rendering. Host: Intel Core 2 CPU, KVM-85rc2, Fedora 7 x64 Guest: Windows XP SP2 32-bit The Command sent to Qemu/KVM: /usr/local/bin/qemu-system-x86_64 -m 256 -monitor tcp:localhost:4502,server,nowait -cdrom /isos/windows/WindowsXP-sp2-vlk.iso -hda /vm/winxp.qcow2 -name WindowsXP -vnc :1 GDB output: (gdb) c Continuing. Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 46912498463376 (LWP 18803)] 0x00438cfc in vga_draw_line24_32 (s1=value optimized out, d=0x2aaabc822000 Address 0x2aaabc822000 out of bounds, s=0x2aaabb3eeef7 , width=36) at /root/Linstall/kvm-85rc2/qemu/hw/vga_template.h:484 484 ((PIXEL_TYPE *)d)[0] = glue(rgb_to_pixel, PIXEL_NAME)(r, g, b); (gdb) bt #0 0x00438cfc in vga_draw_line24_32 (s1=value optimized out, d=0x2aaabc822000 Address 0x2aaabc822000 out of bounds, s=0x2aaabb3eeef7 , width=36) at /root/Linstall/kvm-85rc2/qemu/hw/vga_template.h:484 #1 0x00437b0d in vga_update_display (opaque=value optimized out) at /root/Linstall/kvm-85rc2/qemu/hw/vga.c:1767 #2 0x00490c45 in vnc_listen_read (opaque=0x2aaabb3eeef7) at vnc.c:2020 #3 0x004093dc in main_loop_wait (timeout=value optimized out) at /root/Linstall/kvm-85rc2/qemu/vl.c:3818 #4 0x0051724a in kvm_main_loop () at /root/Linstall/kvm-85rc2/qemu/qemu-kvm.c:588 #5 0x0040e28a in main (argc=13, argv=0x7fff25e77658, envp=value optimized out) at /root/Linstall/kvm-85rc2/qemu/vl.c:3875 (gdb) c Continuing. Program terminated with signal SIGSEGV, Segmentation fault. The program no longer exists. (gdb) The program is not being run. -Alexey -- Comment By: Jes Sorensen (jessorensen) Date: 2011-03-03 11:08 Message: Connecting to KVM session using tightvnc works just fine here. -- You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=893831aid=2725367group_id=180599 -- To unsubscribe from this list: send the line unsubscribe kvm in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
[ kvm-Bugs-2519737 ] DHCP/NAT: Vista fails to get IP from NAT engine
Bugs item #2519737, was opened at 2009-01-19 14:07 Message generated for change (Comment added) made by jessorensen You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=893831aid=2519737group_id=180599 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Closed Resolution: Fixed Priority: 5 Private: No Submitted By: Technologov (technologov) Assigned to: Nobody/Anonymous (nobody) Summary: DHCP/NAT: Vista fails to get IP from NAT engine Initial Comment: Host: Fedora7/x64, KVM-83, Intel Core 2 Guest: Windows Vista 32-bit Problem: When I use userspace networking - Qemu NAT engine with DHCP - Vista VM fails to reconginze it. The only way for Vista to work is to manually set IP address: IP: 10.0.2.2 Gateway: 10.0.2.15 DNS: 10.0.2.3 This problem does not happen with Windows XP VM. It happens with older KVMs too... tested since KVM-75... ./qemu-kvm -hda /isos/disks-vm/alexeye/WindowsVista-32-mypc.qcow2 -m 512 -snapshot -name Vista-32-mypc -Alexey, 19.1.2008. -- Comment By: Jes Sorensen (jessorensen) Date: 2011-03-03 11:09 Message: Fixed per post of 2009-01-21 - closing -- Comment By: Dor Laor (thekozmo) Date: 2009-01-21 08:42 Message: Avi just fixed it in qemu. You can take the patch with this subject: [Qemu-devel] [PATCH] Use broadcast address for slirp dhcp replies -- Comment By: Daniel van Vugt (danv) Date: 2009-01-21 08:06 Message: I've found this problem is common (but not consistent) on both Vista and Windows 7 guests, using kvm-82 and kvm-83, with rtl8139, e1000 or virtio. There's something about these specific Windows releases that breaks with KVM/QEMU DHCP. -- Comment By: Technologov (technologov) Date: 2009-01-19 16:35 Message: Since this also happens with -no-kvm , I opened a similar bug in Qemu bugzilla: https://bugs.launchpad.net/qemu/+bug/318824 -- Comment By: Technologov (technologov) Date: 2009-01-19 16:25 Message: Same happens with -no-kvm (Qemu) and with e1000 NIC (instead of RTL8139). -- Comment By: Technologov (technologov) Date: 2009-01-19 14:08 Message: btw: NAT itself works - after IPs are manually configured. Emulated NIC is RTL8139. -- You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=893831aid=2519737group_id=180599 -- To unsubscribe from this list: send the line unsubscribe kvm in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
[ kvm-Bugs-2609069 ] cannot create guests with 3584 mb memory with =kvm-81
Bugs item #2609069, was opened at 2009-02-17 13:38 Message generated for change (Settings changed) made by jessorensen You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=893831aid=2609069group_id=180599 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Closed Resolution: Works For Me Priority: 5 Private: No Submitted By: Albert Weichselbraun (albert2611) Assigned to: Nobody/Anonymous (nobody) Summary: cannot create guests with 3584 mb memory with =kvm-81 Initial Comment: Creating guest with more 3584 mb of memory leads to the following error message with = kvm-81: qemu: loading initrd (0x4c852c bytes) at 0x7fb37000 create_userspace_phys_mem: Invalid argument kvm_cpu_register_physical_memory: failed The following startup script works with = kvm-80, but fails with higher version (last version tested: kvm-84): /usr/local/bin/qemu-system-x86_64 \ -drive file=/dev/mapper/g3-forge,if=virtio,boot=on \ -drive file=/dev/mapper/g3-tmp,if=virtio \ -net nic,vlan=0,model=virtio,macaddr=00:56:3E:39:55:66 \ -net tap,vlan=0,script=/etc/kvm/kvm-ifup \ -m 3585 \ -kernel /boot/vmlinuz-2.6.27 \ -initrd /boot/initrd.img-2.6.27 \ -append root=/dev/vda ro \ -vnc localhost:0 additional information: cpu model: Intel(R) Xeon(R) CPU X5355 kvm version: 81+ host kernel arch: x86_64 guest: Debian Linux (amd64), 2.6.27.17 (guest and host) qemu command: see above The problem disappears if the -no-kvm switch is used. The -no-kvm-irqchip or -no-kvm-pit switch have no influence on this behavior. Cheers albert and gerhard -- Comment By: Jes Sorensen (jessorensen) Date: 2011-03-03 12:01 Message: Bug seems to have been fixed - works fine here. -- You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=893831aid=2609069group_id=180599 -- To unsubscribe from this list: send the line unsubscribe kvm in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
[ kvm-Bugs-2351433 ] unhandled vm exit: 0x80000021 running UnixWare guest
Bugs item #2351433, was opened at 2008-11-26 17:39 Message generated for change (Comment added) made by jessorensen You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=893831aid=2351433group_id=180599 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: intel Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: John Hughes (hughesj) Assigned to: Nobody/Anonymous (nobody) Summary: unhandled vm exit: 0x8021 running UnixWare guest Initial Comment: CPU: Xeon 3050 Vendor: Intel Bits: 64 Host distribution: Debian Lenny, kernel kernel 2.6.26-1-amd64 Guest: SCO UnixWare 7.1.1 (SVR5), 32 bits Running a UnixWare (SVR5) guest with kvm 79, debian build kernel 2.6.26-1-amd64 on an Intel Xeon 3050 it crashes during boot with: $ qemu-system-x86_64 -net nic,model=ne2k_isa -net user -hda UnixWare.img unhandled vm exit: 0x8021 vcpu_id 0 rax b101 rbx rcx rdx rsi rdi rsp 0ff8 rbp r8 r9 r10 r11 r12 r13 r14 r15 rip fe6e rflags 00023002 cs 0100 (/ p 1 dpl 0 db 1 s 1 type b l 0 g 1 avl 0) ds 0108 (/ p 1 dpl 0 db 1 s 1 type 3 l 0 g 1 avl 0) es (/ p 0 dpl 0 db 0 s 0 type 0 l 0 g 0 avl 0) ss 0108 (/ p 1 dpl 0 db 1 s 1 type 3 l 0 g 1 avl 0) fs (/ p 0 dpl 0 db 0 s 0 type 0 l 0 g 0 avl 0) gs (/ p 0 dpl 0 db 0 s 0 type 0 l 0 g 0 avl 0) tr 0148 (c04405c0/2067 p 1 dpl 0 db 0 s 0 type b l 0 g 0 avl 0) ldt (/ p 0 dpl 0 db 0 s 0 type 0 l 0 g 0 avl 0) gdt 5020/2cf idt 52f0/7ff cr0 8001003b cr2 0 cr3 1005000 cr4 2d4 cr8 0 efer 0 Aborted -- Comment By: Jes Sorensen (jessorensen) Date: 2011-03-03 12:02 Message: Hi, Would you be able to test this against a recent version of KVM? Trying to track down old bugs, but have no way of testing unixware. Cheers, Jes -- Comment By: John Hughes (hughesj) Date: 2008-12-09 12:35 Message: Amusingly Xen 3.3 gives almost exactly the same bug, see http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1391 -- Comment By: John Hughes (hughesj) Date: 2008-11-26 19:09 Message: Using kvm 72 in 32 bit mode on the same hardware I get unhandled vm exit: 0x9 vcpu_id 0 rax 8001003b rbx 0ff8 rcx f000 rdx f000 rsi fffda500 rdi 0001 rsp fffda4b4 rbp c043d818 r8 r9 r10 r11 r12 r13 r14 r15 rip c005f980 rflags 0202 cs 0100 (/ p 1 dpl 0 db 1 s 1 type b l 0 g 1 avl 0) ds 0108 (/ p 1 dpl 0 db 1 s 1 type 3 l 0 g 1 avl 0) es 0108 (/ p 1 dpl 0 db 1 s 1 type 3 l 0 g 1 avl 0) ss 0108 (/ p 1 dpl 0 db 1 s 1 type 3 l 0 g 1 avl 0) fs (/ p 0 dpl 0 db 0 s 0 type 0 l 0 g 0 avl 0) gs (/ p 0 dpl 0 db 0 s 0 type 0 l 0 g 0 avl 0) tr 0110 (5af0/0067 p 1 dpl 0 db 0 s 0 type b l 0 g 0 avl 0) ldt 0118 (c0812bf8/0047 p 1 dpl 0 db 0 s 0 type 2 l 0 g 0 avl 0) gdt 5020/2cf idt 52f0/7ff cr0 8001003b cr2 0 cr3 1005000 cr4 2d4 cr8 0 efer 0 Aborted -- Comment By: John Hughes (hughesj) Date: 2008-11-26 17:41 Message: (Works with -no-kvm). -- You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=893831aid=2351433group_id=180599 -- To unsubscribe from this list: send the line unsubscribe kvm in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
[ kvm-Bugs-2584543 ] Migration failed on kvm 83 (regression from 79)
Bugs item #2584543, was opened at 2009-02-10 11:16 Message generated for change (Comment added) made by jessorensen You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=893831aid=2584543group_id=180599 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Closed Resolution: Out of Date Priority: 5 Private: No Submitted By: Guido Trotter (ultrotter) Assigned to: Nobody/Anonymous (nobody) Summary: Migration failed on kvm 83 (regression from 79) Initial Comment: Hi, I'm running kvm on a Dual-Core AMD Opteron(tm) Processor and I'm having problems with live migration, since moving to version 83. Everything works fine on version 79. Basically I'm trying to do a live migration while a process is pinging, and the vm dies with a kernel dump, while on kvm 79 everything continued to run. The vm has a default debian lenny installed in it (with the 2.6.26 lenny kernel and everything) while the host is running a custom 2.6.27 kernel. Kvm is started (by ganeti 2.0, whose support for kvm I'm developing) with the following options: /usr/bin/kvm -m 128 -smp 1 -pidfile /var/run/ganeti/kvm-hypervisor/pid/instance -name instance -daemonize -boot c -drive file=/var/run/ganeti/instance-disks/instance:0,format=raw,if=virtio,boot=on -drive file=/usr/src/debian-Lenny-DI-rc2-amd64-netinst.iso,format=raw,media=cdrom,if=virtio -vnc :5364 -monitor unix:/var/run/ganeti/kvm-hypervisor/ctrl/instance.monitor,server,nowait -serial none -net nic,macaddr=MAC,model=virtio -net tap,script=/tmp/tmpQQ5yTE -incoming tcp:IP:8102 (the tap script is autogenerated by ganeti and connects the interface to the correct bridge) I suspect it might be something introduced in the patch to make networking on live migration more smooth... Thanks, Guido -- Comment By: Jes Sorensen (jessorensen) Date: 2011-03-03 12:11 Message: No response to inquiry of 2010-11-26 so assume it is fixed as we're not seeing similar reports with migration with the current tree. Closing -- Comment By: Jes Sorensen (jessorensen) Date: 2010-11-26 09:24 Message: Hi, Is this still a problem? There has been a lot of fixes to the migration code since you reported this bug. Sorry that you didn't see any answers earlier. Regards, Jes -- You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=893831aid=2584543group_id=180599 -- To unsubscribe from this list: send the line unsubscribe kvm in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
[ kvm-Bugs-2840321 ] Qemu/KVM Can't boot scsi or virtio
Bugs item #2840321, was opened at 2009-08-19 16:11 Message generated for change (Comment added) made by jessorensen You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=893831aid=2840321group_id=180599 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: qemu Group: None Status: Closed Resolution: Fixed Priority: 5 Private: No Submitted By: Donald Dupuis (dondster) Assigned to: Nobody/Anonymous (nobody) Summary: Qemu/KVM Can't boot scsi or virtio Initial Comment: I am running on Fedora 11 with kernel 2.6.29.6-217.2.8.fc11.x86_64 and also using Qemu version 0.11.50 Using the following command works. I have my pxe entry on the server to localboot. /usr/bin/qemu-kvm -M pc -m 1024 -smp 2 -name vmgenserv -uuid 535a7862-170d-d93e-aa47-fa07e74892a6 -monitor pty -pidfile /var/run/libvirt/qemu//vmgenserv.pid -boot order=nc -drive file=/var/lib/libvirt/images/vmgenserve-sda.img -drive file=/var/lib/libvirt/images/vmgenserv-sdb.img -net nic,macaddr=54:52:00:66:4e:d8,vlan=0,model=rtl8139 -net tap,vlan=0,ifname=tap0,script=/etc/qemu-ifup -serial pty -parallel none -usb -vga cirrus -option-rom /usr/share/gpxe/rtl8139.rom This command where the if=scsi,index=0 or if=virtio will fail /usr/bin/qemu-kvm -M pc -m 1024 -smp 2 -name vmgenserv -uuid 535a7862-170d-d93e-aa47-fa07e74892a6 -monitor pty -pidfile /var/run/libvirt/qemu//vmgenserv.pid -boot order=nc -drive file=/var/lib/libvirt/images/vmgenserve-sda.img,if=scsi,index=0 -drive file=/var/lib/libvirt/images/vmgenserv-sdb.img,if=scsi,index=1 -net nic,macaddr=54:52:00:66:4e:d8,vlan=0,model=rtl8139 -net tap,vlan=0,ifname=tap0,script=/etc/qemu-ifup -serial pty -parallel none -usb -vga cirrus -option-rom /usr/share/gpxe/rtl8139.rom It will also fail if I don't pxeboot The screen will just read: ata0 master: QEMU HARDDISK ATA-7 Hard-Disk ( 98 GBytes ) ata1 master: QEMU DVD-ROM Booting from Hard Disk... I read in another bug report that this was supposed to work in 0.11.x -- Comment By: Jes Sorensen (jessorensen) Date: 2011-03-03 12:14 Message: This is now due to missing extboot.bin BIOS. If you still see this problem after making sure you have this in place, please open a new bug with the problem over at launchpad.net -- Comment By: Donald Dupuis (dondster) Date: 2009-08-19 19:20 Message: Ok, I have switched to the latest code that is in qemu-kvm.git. After adding the boot=on parameter, I now get the Could not load option rom 'extboot.bin' message Just for verification I am running qemu-kvm version 0.11.50 -- Comment By: Brian Jackson (iggy_cav) Date: 2009-08-19 18:37 Message: You need to run qemu-kvm or kvm and add boot=on to your drive args for the one you want to boot off of. Upstream qemu doesn't support booting off scsi/virtio -- You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=893831aid=2840321group_id=180599 -- To unsubscribe from this list: send the line unsubscribe kvm in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
[ kvm-Bugs-2834538 ] low network speed with Windows virtio NIC drivers
Bugs item #2834538, was opened at 2009-08-09 19:23 Message generated for change (Comment added) made by jessorensen You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=893831aid=2834538group_id=180599 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Closed Resolution: Out of Date Priority: 5 Private: No Submitted By: Andreas Unterkircher (unki) Assigned to: Nobody/Anonymous (nobody) Summary: low network speed with Windows virtio NIC drivers Initial Comment: Host-CPU: 2x Intel Xeon E5420 (Quad cores) Host: KVM 85 Host: 64-bit Guest: Windows XP (SP3) and Windows 2003 (SP2) We are powering several guests on a KVM host. All of them using TAP interfaces bridged together via one bridge. Within the guests we installed the lasted virtio NIC drivers (from that ISO file). While the Interface status show that the interfaces are set to 1Gbit/s, the maximum bandwidth we can achieve is about 100-120Mbit/s (tested with iperf). Funilly, one the same host, two Debian Lenny guests (so using 2.6.26 with builtin virtio modules) can achieve the full bandwidth of 1Gbit/s and more without a problem. So we suspect that the Windows virtio drivers for the NICs are causing this problem. How can we track down that problem? Can we provide more infos? We are willing to help in debuggig! Thx, Andreas -- Comment By: Jes Sorensen (jessorensen) Date: 2011-03-03 12:27 Message: New drivers have been out for a long time now - if you still see this problem, please open a new bug over at launchpad.net Closing -- Comment By: Dor Laor (thekozmo) Date: 2009-08-20 12:00 Message: They were just announced last week: http://www.mail-archive.com/kvm@vger.kernel.org/msg20969.html Currently you'll need to build them from the source and binaries will soon follow. -- Comment By: Andreas Unterkircher (unki) Date: 2009-08-20 08:18 Message: Hi, Can you give us an outlook to, when this new driver will be available? Or can we have it already to test if they are able to increase the performance? Cheers, -- Comment By: Andreas Unterkircher (unki) Date: 2009-08-14 13:19 Message: Many thanks for that first hint. I tried first to increase the window size for iperf (1M or 4M) like you suggested - and indeed it immediately showed up a higher bandwidth. Then I applied those few registry settings you have put on linux-kvm.org and now iperf shows the better performance also without explictly setting the window size. But all my other tries - like SFTP/SCP over SSH or a simple file copy between to KVM Windows guests still not show improvements. A max. was now about 200Mbit/s (neither CPU nor Disk are reaching their limit in this case). You were saying: Also, make sure TSO is on On the Windows guests, in the driver settings (advanced) there is no option to enable segmentation-offload. On the Linux hosts TSO and GSO is enabled. Do I need to enable this in the registry? And I was wondering, because from the 1GB Interface option you copied here, all the offload parameters are disabled: HwOffload=0 OffLoad.TxIP=0 OffLoad.TxLSO=0 OffLoad.TxTCP=0 -- Comment By: Dor Laor (thekozmo) Date: 2009-08-10 13:33 Message: Here is more precise/pin-point data: http://www.linux-kvm.org/page/WindowsGuestDrivers/kvmnet/registry -- Comment By: Dor Laor (thekozmo) Date: 2009-08-10 10:15 Message: The driver should be able to saturate 1G link. We'll soon post new version of the driver but there are no massive changes. You can try and play with the socket buffers (iperf -w), windows is very sensitive for it. Also, make sure TSO is on. Here is the windows registry configuration we use: TCPIP Params from the registry: [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters] NV Hostname=marksbox NameServer= ForwardBroadcasts=dword: IPEnableRouter=dword: Domain= Hostname=marksbox SearchList= UseDomainNameDevolution=dword: EnableICMPRedirect=dword:0001 DeadGWDetectDefault=dword:0001 DontAddDefaultGatewayDefault=dword: EnableSecurityFilters=dword: ReservedPorts=hex(7):33,00,33,00,34,00,33,00,2d,00,33,00,33,00,34,00,33,00,00,00,00,00 EnableTCPA=dword: EnableRSS=dword: EnableTCPChimney=dword: Tcp1323Opts=dword:0003 TcpAckFrequency=dword:0002 TcpWindowSize=dword:0010 DhcpNameServer=192.168.122.1 For the Windows Socket Layer [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\AFD
[ kvm-Bugs-2792656 ] System freeze after modprobe kvm-intel
Bugs item #2792656, was opened at 2009-05-16 14:32 Message generated for change (Comment added) made by jessorensen You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=893831aid=2792656group_id=180599 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: intel Group: None Status: Closed Resolution: Out of Date Priority: 5 Private: No Submitted By: zorn (uzorn) Assigned to: Nobody/Anonymous (nobody) Summary: System freeze after modprobe kvm-intel Initial Comment: Hi, I just enabled Intel-VT on my Toshiba Tecra A8 and get the following problem: If I try to load the module kvm-intel, the whole system freezes after a short time ( 1s). No errors, no logs... CPU: Intel(R) Core(TM)2 CPU KVM: kvm-85 Host distro: Ubuntu 9.04 (32-bit) Host kernel: 2.6.30-020630rc5-generic #020630rc5 (i686) Command line: modprobe kvm-intel # cat /proc/cpuinfo processor : 0 vendor_id : GenuineIntel cpu family : 6 model : 15 model name : Intel(R) Core(TM)2 CPU T7200 @ 2.00GHz stepping: 6 cpu MHz : 1000.000 cache size : 4096 KB physical id : 0 siblings: 2 core id : 0 cpu cores : 2 apicid : 0 initial apicid : 0 fdiv_bug: no hlt_bug : no f00f_bug: no coma_bug: no fpu : yes fpu_exception : yes cpuid level : 10 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe nx lm constant_tsc arch_perfmon pebs bts pni dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm lahf_lm tpr_shadow bogomips: 3990.45 clflush size: 64 power management: processor : 1 vendor_id : GenuineIntel cpu family : 6 model : 15 model name : Intel(R) Core(TM)2 CPU T7200 @ 2.00GHz stepping: 6 cpu MHz : 1000.000 cache size : 4096 KB physical id : 0 siblings: 2 core id : 1 cpu cores : 2 apicid : 1 initial apicid : 1 fdiv_bug: no hlt_bug : no f00f_bug: no coma_bug: no fpu : yes fpu_exception : yes cpuid level : 10 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe nx lm constant_tsc arch_perfmon pebs bts pni dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm lahf_lm tpr_shadow bogomips: 3990.04 clflush size: 64 power management: -- Comment By: Jes Sorensen (jessorensen) Date: 2011-03-03 12:33 Message: No reply to inquiry of 2010-11-26 so assuming problem resolved. -- Comment By: Jes Sorensen (jessorensen) Date: 2010-11-26 11:39 Message: Do you still see the problem with recent KVM? Do you have anything in syslog indicating what went wrong? Thanks, Jes -- Comment By: zorn (uzorn) Date: 2009-05-21 16:34 Message: I updated to current Toshiba BIOS v1.40 today, it is still the same. -- Comment By: Avi Kivity (avik) Date: 2009-05-17 11:40 Message: Is your BIOS updated to the latest version provided by the vendor? -- You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=893831aid=2792656group_id=180599 -- To unsubscribe from this list: send the line unsubscribe kvm in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
[ kvm-Bugs-2835276 ] segfault using -cpu pentium3 on coreduo
Bugs item #2835276, was opened at 2009-08-11 03:38
Message generated for change (Comment added) made by jessorensen
You can respond by visiting:
https://sourceforge.net/tracker/?func=detailatid=893831aid=2835276group_id=180599
Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: qemu
Group: None
Status: Closed
Resolution: Works For Me
Priority: 5
Private: No
Submitted By: Aron Griffis (agriffis)
Assigned to: Nobody/Anonymous (nobody)
Summary: segfault using -cpu pentium3 on coreduo
Initial Comment:
qemu-0.11.0-rc1 and qemu-kvm-HEAD segfault with -cpu pentium3 on ProLiant DL380
G5 (dual-socket dual-core Intel Xeon 5160). This is a regression from
qemu-0.10.6 which does not have the problem.
Using -cpu coreduo avoids the segfault. -cpu athlon works too.
I bisected to find that the problem is introduced by
0ed8cfc05bb012e52b92771bb13bef0e2e80c828 and can be worked around by the
following patch to HEAD which effectively reverts that commit:
--- a/hw/pc.c
+++ b/hw/pc.c
@@ -1096,11 +1096,11 @@ CPUState *pc_new_cpu(const char *cpu_model)
}
if ((env-cpuid_features CPUID_APIC) || smp_cpus 1) {
env-cpuid_apic_id = env-cpu_index;
-/* APIC reset callback resets cpu */
-apic_init(env);
} else {
qemu_register_reset((QEMUResetHandler*)cpu_reset, env);
}
+/* APIC reset callback resets cpu */
+apic_init(env);
/* kvm needs this to run after the apic is initialized. Otherwise,
* it can access invalid state and crash.
--
Comment By: Jes Sorensen (jessorensen)
Date: 2011-03-03 12:36
Message:
Tested current qemu and qemu-kvm, both works with pentium3 and coreduo, so
bug looks to have
been fixed.
Jes
--
You can respond by visiting:
https://sourceforge.net/tracker/?func=detailatid=893831aid=2835276group_id=180599
--
To unsubscribe from this list: send the line unsubscribe kvm in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
[ kvm-Bugs-2729621 ] usb_add on garmin gps fails
Bugs item #2729621, was opened at 2009-04-04 05:02
Message generated for change (Comment added) made by jessorensen
You can respond by visiting:
https://sourceforge.net/tracker/?func=detailatid=893831aid=2729621group_id=180599
Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: qemu
Group: None
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Byron Clark (byron_clark)
Assigned to: Nobody/Anonymous (nobody)
Summary: usb_add on garmin gps fails
Initial Comment:
When I attempt to usb_add my Garmin Venture HC GPS with this command:
usb_add host:091e:0003
I get the following error:
usb_linux_update_endp_table: Broken pipe
strace log:
write(1, husb: open device 5.3\n, 22) = 22
open(/proc/bus/usb/005/003, O_RDWR|O_NONBLOCK) = 26
read(26,
\22\1\20\1\377\377\377@\36\t\3\0\1\0\0\0\0\1\t\2'\0\1\1\0\300\0\t\4\0\0\3...,
1024) = 57
write(1, husb: config #1 need -1\n, 24) = 24
ioctl(26, USBDEVFS_IOCTL, 0x7fff0bb74300) = -1 ENODATA (No data available)
ioctl(26, USBDEVFS_CLAIMINTERFACE, 0x7fff0bb7431c) = 0
write(1, husb: 1 interfaces claimed for c..., 47) = 47
ioctl(26, USBDEVFS_CONNECTINFO, 0x7fff0bb74750) = 0
write(1, husb: grabbed usb device 5.3\n, 29) = 29
ioctl(26, USBDEVFS_CONTROL, 0x7fff0bb742f0) = -1 EPIPE (Broken pipe)
dup(2) = 27
fcntl(27, F_GETFL) = 0x8802 (flags
O_RDWR|O_NONBLOCK|O_LARGEFILE)
fstat(27, {st_mode=S_IFCHR|0620, st_rdev=makedev(136, 9), ...}) = 0
mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) =
0x7f4e03b67000
lseek(27, 0, SEEK_CUR) = -1 ESPIPE (Illegal seek)
write(27, usb_linux_update_endp_table: Bro..., 41) = 41
close(27) = 0
cpu:
processor : 0
vendor_id : GenuineIntel
cpu family : 6
model : 15
model name : Intel(R) Core(TM)2 Duo CPU T7500 @ 2.20GHz
stepping: 11
cpu MHz : 2194.427
cache size : 4096 KB
physical id : 0
siblings: 2
core id : 0
cpu cores : 2
apicid : 0
initial apicid : 0
fpu : yes
fpu_exception : yes
cpuid level : 10
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov
pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx lm
constant_tsc arch_perfmon pebs bts rep_good pni dtes64 monitor ds_cpl vmx est
tm2 ssse3 cx16 xtpr pdcm lahf_lm ida tpr_shadow vnmi flexpriority
bogomips: 4388.85
clflush size: 64
cache_alignment : 64
address sizes : 36 bits physical, 48 bits virtual
power management:
host distribution: debian sid
bitness: 64
guest distribution: windows xp
bitness: 32
--
Comment By: Jes Sorensen (jessorensen)
Date: 2011-03-03 12:39
Message:
Last comment is a bit unclear - can you confirm that this actually works?
Thanks,
Jes
--
Comment By: Nicholas J Kreucher (kreucher)
Date: 2009-12-03 20:18
Message:
Scratch the hal comment... it actually works perfectly :)
--
Comment By: Nicholas J Kreucher (kreucher)
Date: 2009-12-03 20:05
Message:
Perhaps this is a usb serial device? Seems there is a workaround for such
devices here:
http://ubuntuforums.org/archive/index.php/t-910796.html
See IntuitiveNipple's Sep 7th post. The patch worked for me (sort of, the
guest device now exists and works, but the hal properties don't seem to be
populated correctly).
--
Comment By: Byron Clark (byron_clark)
Date: 2009-04-04 05:08
Message:
kvm-84, kernel 2.6.29.
--
You can respond by visiting:
https://sourceforge.net/tracker/?func=detailatid=893831aid=2729621group_id=180599
--
To unsubscribe from this list: send the line unsubscribe kvm in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
[ kvm-Bugs-2914397 ] Virtio drivers for Windows - large volumes fail
Bugs item #2914397, was opened at 2009-12-14 22:06 Message generated for change (Comment added) made by jessorensen You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=893831aid=2914397group_id=180599 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Closed Resolution: Out of Date Priority: 5 Private: No Submitted By: Brian Jackson (iggy_cav) Assigned to: Nobody/Anonymous (nobody) Summary: Virtio drivers for Windows - large volumes fail Initial Comment: When passing a 3T volume to a Windows 2008 guest using virtio drivers, the guest is unable to properly initialize the drive. Windows logs the following error: VDS fails to write boot code on a disk during clean operation. Error code: 80070013@02070008 It works correctly when using IDE emulation. This occurs with self built drivers from a checkout on Dec. 8 Host: Xeon 5130 Volumes are attached via iSCSI Guest: Windows 2008R2 64bit kvm -smp 2 -m 2000 -name p3hq-share01 -drive file=/dev/mapper/SPIVOT3__RAIGE_VOLUME___600176c3547ddd11a18e92c748d535e6,cache=none -drive file=/dev/mapper/SPIVOT3__RAIGE_VOLUME___600176c3851660644b72bd9548d535e6,cache=none,if=virtio -net nic,macaddr=52:54:00:41:86:28,vlan=0,model=virtio -net tap,vlan=0,script=/etc/kvm/kvm-ifup -usb -vnc :0 -vga std -daemonize -- Comment By: Jes Sorensen (jessorensen) Date: 2011-03-03 12:42 Message: No reply to suggestion of 2010-11-26, so assuming fixed. -- Comment By: Jes Sorensen (jessorensen) Date: 2010-11-26 13:06 Message: Make sure you have the latest virtio-win drivers from: http://www.linux-kvm.com/content/latest-windows-virtio-drivers If this still fails, please open a bug in launchpad. Thanks, Jes -- You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=893831aid=2914397group_id=180599 -- To unsubscribe from this list: send the line unsubscribe kvm in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
[ kvm-Bugs-2962575 ] MINIX 3.1.6 works in QEMU-0.12.3 only with KVM disabled
Bugs item #2962575, was opened at 2010-03-03 13:20 Message generated for change (Comment added) made by jessorensen You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=893831aid=2962575group_id=180599 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: intel Group: None Status: Closed Resolution: Works For Me Priority: 5 Private: No Submitted By: Erik van der Kouwe (erikvdk) Assigned to: Nobody/Anonymous (nobody) Summary: MINIX 3.1.6 works in QEMU-0.12.3 only with KVM disabled Initial Comment: Dear all, If one runs the following commands after installing qemu-0.12.3 or qemu-kvm-0.12.3: wget http://www.minix3.org/download/minix_R3.1.6-r6084.iso.bz2 bunzip2 minix_R3.1.6-r6084.iso.bz2 qemu-system-x86_64 -cdrom minix_R3.1.6-r6084.iso -enable-kvm and presses 1 (Regular MINIX 3), the following error message results when loading MINIX: kvm: unhandled exit 8021 kvm_run returned -22 The guest stops after that. This error message does not occur without the -enable-kvm switch. It does not occur with qemu-kvm-0.11.0 as bundled with Ubuntu. The problem occurs with the qemu binary from qemu-0.12.3 as well as qemu-system-x86_64 from qemu-kvm-0.12.3, but in the former case no error message is printed. The code that is running when it fails is in https://gforge.cs.vu.nl/gf/project/minix/scmsvn/?action=browsepath=%2Ftrunk%2Fsrc%2Fboot%2Fboothead.srevision=5918view=markup. It happens in ext_copy: ext_copy: mov x_dst_desc+2, ax movbx_dst_desc+4, dl ! Set base of destination segment mov ax, 8(bp) mov dx, 10(bp) mov x_src_desc+2, ax movbx_src_desc+4, dl ! Set base of source segment mov si, #x_gdt ! es:si = global descriptor table shr cx, #1 ! Words to move movbah, #0x87 ! Code for extended memory move int 0x15 The line that fails is int 0x15, which performs a BIOS call to copy data from low memory to above the 1MB barrier. The machine is running in 16-bit real mode when this code is executed. Output for uname -a on the host: Linux hp364 2.6.31-20-generic #57-Ubuntu SMP Mon Feb 8 09:05:19 UTC 2010 i686 GNU/Linux Output for cat /proc/cpuinfo on the host: processor : 0 vendor_id : GenuineIntel cpu family : 6 model : 23 model name : Intel(R) Core(TM)2 Duo CPU E8600 @ 3.33GHz stepping: 10 cpu MHz : 1998.000 cache size : 6144 KB physical id : 0 siblings: 2 core id : 0 cpu cores : 2 apicid : 0 initial apicid : 0 fdiv_bug: no hlt_bug : no f00f_bug: no coma_bug: no fpu : yes fpu_exception : yes cpuid level : 13 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe nx lm constant_tsc arch_perfmon pebs bts pni dtes64 monitor ds_cpl vmx smx est tm2 ssse3 cx16 xtpr pdcm sse4_1 xsave lahf_lm tpr_shadow vnmi flexpriority bogomips: 6650.50 clflush size: 64 power management: processor : 1 vendor_id : GenuineIntel cpu family : 6 model : 23 model name : Intel(R) Core(TM)2 Duo CPU E8600 @ 3.33GHz stepping: 10 cpu MHz : 1998.000 cache size : 6144 KB physical id : 0 siblings: 2 core id : 1 cpu cores : 2 apicid : 1 initial apicid : 1 fdiv_bug: no hlt_bug : no f00f_bug: no coma_bug: no fpu : yes fpu_exception : yes cpuid level : 13 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe nx lm constant_tsc arch_perfmon pebs bts pni dtes64 monitor ds_cpl vmx smx est tm2 ssse3 cx16 xtpr pdcm sse4_1 xsave lahf_lm tpr_shadow vnmi flexpriority bogomips: 6649.80 clflush size: 64 power management: With kind regards, Erik -- Comment By: Jes Sorensen (jessorensen) Date: 2011-03-03 12:46 Message: Checked exact command and works fine with current QEMU on a Fedora 14 system. Looks to be fixed, so closing. -- Comment By: Erik van der Kouwe (erikvdk) Date: 2010-03-10 15:16 Message: Thanks to Avi Kivity I now have a workaround for this issue, namely 16-byte align the addresses in the GDT passed to the BIOS extended copy function. The BIOS left the unaligned descriptor causing MINIX to operate in unreal mode, which is not well supported by KVM on Intel. -- You can respond by visiting: https://sourceforge.net/tracker/?func
[ kvm-Bugs-2219215 ] SVM: WinXP install with the --no-kvm-irqchip fails with BSOD
Bugs item #2219215, was opened at 2008-11-03 17:17 Message generated for change (Comment added) made by jessorensen You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=893831aid=2219215group_id=180599 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: amd Group: None Status: Closed Resolution: Fixed Priority: 5 Private: No Submitted By: Amit Shah (amitshah) Assigned to: Nobody/Anonymous (nobody) Summary: SVM: WinXP install with the --no-kvm-irqchip fails with BSOD Initial Comment: Installing Win XP 32-bit on an AMD machine without NPT results in a BSOD: page_fault_in_non_paged_area. The kernel and userspace are from git, hashes: userspace: a08db73bca2bfe05ad446f40af7bea1cdd09d6b1 kernel: 6e6c4599ba4bb105c05f21882af70771b12a0561 Screenshot attached. -- Comment By: Jes Sorensen (jessorensen) Date: 2011-03-03 14:26 Message: Spoke to Amit - this is no longer a problem -- You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=893831aid=2219215group_id=180599 -- To unsubscribe from this list: send the line unsubscribe kvm in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
[ kvm-Bugs-2530908 ] QEMU segfaults in reboot test
Bugs item #2530908, was opened at 2009-01-23 12:31 Message generated for change (Comment added) made by jessorensen You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=893831aid=2530908group_id=180599 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: qemu Group: None Status: Closed Resolution: Out of Date Priority: 5 Private: No Submitted By: Joerg Roedel (jroedel) Assigned to: Nobody/Anonymous (nobody) Summary: QEMU segfaults in reboot test Initial Comment: When running QEMU on KVM with a Linux operating system which reboots again and again the QMEU process dies with a segfault within a few hours. Should be easily reproducible. -- Comment By: Jes Sorensen (jessorensen) Date: 2011-03-03 14:36 Message: Joerg, If you see this again, please reopen in launchpad. Cheers, Jes -- Comment By: Marcelo Tosatti (mtosatti) Date: 2009-01-30 22:21 Message: Joerg, I can't reproduce it with kvm.git / kvm-userspace.git. A FC10 host with NPT has successfully rebooted an SMP guest (2 vcpus) 800 times since last night. What command line are you using? Perhaps you could share the core file and the qemu binary? qemu/x86_64-softmmu/qemu-system-x86_64 -hda /images/fc10-64.img \ -cdrom /home/marcelo/isos/Fedora-10-x86_64-DVD.iso -vnc :2 -m 1000 \ -net nic,model=e1000 -net tap,script=/home/marcelo/ifup,ifname=tap1 \ -localtime $1 -serial stdio -- You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=893831aid=2530908group_id=180599 -- To unsubscribe from this list: send the line unsubscribe kvm in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
[ kvm-Bugs-1906272 ] Debian 4 fails to boot on KVM-AMD
Bugs item #1906272, was opened at 2008-03-03 14:53 Message generated for change (Comment added) made by jessorensen You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=893831aid=1906272group_id=180599 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Closed Resolution: Duplicate Priority: 5 Private: No Submitted By: Technologov (technologov) Assigned to: Nobody/Anonymous (nobody) Summary: Debian 4 fails to boot on KVM-AMD Initial Comment: Host: AMD Barcelona K10, F7/x64, KVM-62. Guest: Debian 4 (32-bit). Problem: When installing Debian 4 (32-bit) on KVM-AMD host, it installs k7 kernel by default, and the resulting image is not bootable. It can be booted only with -no-kvm. This problem can be avoided when installing on KVM-intel host, which uses i686 kernel for Debian guests. This is because Debian's setup check for CPUID and setups the kernel, that best matches the current CPU. This kernel (i686) can be booted from kvm-intel or from kvm-amd without problems. Perhaps KVM-AMD doesn't emulate something K7 specific (3Dnow ?). I don't know what is the best solution to this problem, but I think using custom CPUID when installing Debian guests might do it. Any ideas? === (gdb) bt #0 0x003dd02c9117 in ioctl () from /lib64/libc.so.6 #1 0x0051bb29 in kvm_run (kvm=0x2a9b040, vcpu=0) at libkvm.c:850 #2 0x004fda86 in kvm_cpu_exec (env=value optimized out) at /root/Linstall/kvm-62rc2/qemu/qemu-kvm.c:127 #3 0x004fe5d5 in kvm_main_loop_cpu (env=0x2b82bb0) at /root/Linstall/kvm-62rc2/qemu/qemu-kvm.c:307 #4 0x004110fd in main (argc=44675488, argv=value optimized out) at /root/Linstall/kvm-62rc2/qemu/vl.c:7862 === kvm statistics efer_reload 0 0 exits 11387804 324872 fpu_reload 1340894 296 halt_exits 0 0 halt_wakeup 0 0 host_state_reload 1340931 295 hypercalls 0 0 insn_emulation10053389 323534 insn_emulation_fail 10009814 323534 invlpg 0 0 io_exits 13347571004 irq_exits0 0 irq_window 0 0 largepages 0 0 mmio_exits 27231 0 mmu_cache_miss 20 0 mmu_flooded 0 0 mmu_pde_zapped 0 0 mmu_pte_updated 0 0 mmu_pte_write0 0 mmu_recycled 0 0 -Alexey, 3.3.2008. -- Comment By: Jes Sorensen (jessorensen) Date: 2011-03-03 16:06 Message: Joerg moved this to https://bugzilla.kernel.org/show_bug.cgi?id=30402 -- Comment By: Joerg Roedel (jroedel) Date: 2008-03-03 17:54 Message: Logged In: YES user_id=2019182 Originator: NO I was able to reproduce this problem. The instruction emulater lacks support for mmx memory instructions. Needs to be fixed. -- You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=893831aid=1906272group_id=180599 -- To unsubscribe from this list: send the line unsubscribe kvm in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
[ kvm-Bugs-3196108 ] pci-stub.o: In function `do_pci_info\':0.14.0 compile problem
Bugs item #3196108, was opened at 2011-03-01 13:22 Message generated for change (Tracker Item Submitted) made by alephlg You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=893831aid=3196108group_id=180599 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Aleph (alephlg) Assigned to: Nobody/Anonymous (nobody) Summary: pci-stub.o: In function `do_pci_info\':0.14.0 compile problem Initial Comment: Plase see this build log. I didn\'t compile thq qemu-kvm on Mandriva Cooker and haven\'t any idea. I\'m the qemu maintainer on Mandriva. -- You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=893831aid=3196108group_id=180599 -- To unsubscribe from this list: send the line unsubscribe kvm in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
[ kvm-Bugs-3196108 ] pci-stub.o: In function `do_pci_info\':0.14.0 compile problem
Bugs item #3196108, was opened at 2011-03-01 13:22 Message generated for change (Comment added) made by nikola_ciprich You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=893831aid=3196108group_id=180599 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Aleph (alephlg) Assigned to: Nobody/Anonymous (nobody) Summary: pci-stub.o: In function `do_pci_info\':0.14.0 compile problem Initial Comment: Plase see this build log. I didn\'t compile thq qemu-kvm on Mandriva Cooker and haven\'t any idea. I\'m the qemu maintainer on Mandriva. -- Comment By: Nikola Ciprich (nikola_ciprich) Date: 2011-03-01 17:25 Message: see this thread: http://www.mail-archive.com/kvm@vger.kernel.org/msg50035.html for the resolution. -- You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=893831aid=3196108group_id=180599 -- To unsubscribe from this list: send the line unsubscribe kvm in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
[ kvm-Bugs-2067179 ] Possible Bug in ATA Emulation Code
Bugs item #2067179, was opened at 2008-08-22 12:25
Message generated for change (Settings changed) made by jessorensen
You can respond by visiting:
https://sourceforge.net/tracker/?func=detailatid=893831aid=2067179group_id=180599
Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
Group: None
Status: Closed
Resolution: Out of Date
Priority: 5
Private: No
Submitted By: Johannes Truschnigg (c0l0)
Assigned to: Nobody/Anonymous (nobody)
Summary: Possible Bug in ATA Emulation Code
Initial Comment:
CPU: Intel Core 2 Quad Q6600 (4 cores)
Distro, kernel: Gentoo GNU/Linux ~amd64, Kernel 2.6.26.3
Bitness, compiler: x86_64, GCC 4.3.1
KVM versions: kvm-72
Before going on vacation, I decided to stress-test a KVM Guest running Ubuntu
8.04.1 (x86) on my Gentoo x86_84 host - it ran the `stress`-program (
http://weather.ou.edu/~apw/projects/stress ) with all hardware components
tested for about 10 days. After 178338 seconds of guest-uptime, something in
the emulated disk subsystem bombed:
[178338.511058] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen
[178338.511080] ata1.00: cmd 35/00:00:9f:96:0d/00:04:01:00:00/e0 tag 0 dma
524288 out
[178338.511082] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4
(timeout)
[178338.511085] ata1.00: status: { DRDY }
[178343.540203] ata1: port is slow to respond, please be patient (Status 0xd8)
[178348.513648] ata1: device not ready (errno=-16), forcing hardreset
[178348.513655] ata1: soft resetting link
[178348.670875] ata1.00: configured for MWDMA2
[178348.670889] ata1: EH complete
The full guest dmesg output is available at http://pasted.at/e548758180.html
and as an attachment to this report.
This problem lead to the guest OS remounting the filesystem residing on the
disk/partition in question read-only, and `stress` killing itself - it did not
crash the system completely.
The filesystem on the host storing the RAW image containing the guest-OS was
perfectly OK when the error occurred. The host's dmesg output remained
unchanged all the time, with no errors or info regarding kvm (or anything else,
for that matter) whatsoever reported.
--
Comment By: Jes Sorensen (jessorensen)
Date: 2011-01-07 13:45
Message:
No update to my question in August so assuming it is fixed by now. There
have been a lot of IDE fixes
since this bug was initially reported.
If you see this again, please feel free to open a new bug in the
launchpad.net bug tracker.
Cheers,
Jes
--
Comment By: Jes Sorensen (jessorensen)
Date: 2010-08-19 12:29
Message:
Hi,
Going through old bugs trying to clean up the queue.
Are you still seeing this problem with recent KVM or can we close the
bug?
Thanks,
Jes
--
Comment By: Peter A. Peterson II (unclepedro)
Date: 2009-02-05 01:41
Message:
I just had a very similar issue, and it turned out that I did not have
write permission on the image file (because I had copied it from a
different UID). I fixed the permissions on the image, fully restarted qemu
(this was critical), and then it worked. HTH.
--
You can respond by visiting:
https://sourceforge.net/tracker/?func=detailatid=893831aid=2067179group_id=180599
--
To unsubscribe from this list: send the line unsubscribe kvm in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
[ kvm-Bugs-1868937 ] eepro100.c:1570: nic_receive: Assertion `0' failed.
Bugs item #1868937, was opened at 2008-01-11 00:08
Message generated for change (Comment added) made by jessorensen
You can respond by visiting:
https://sourceforge.net/tracker/?func=detailatid=893831aid=1868937group_id=180599
Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: qemu
Group: None
Status: Closed
Resolution: Out of Date
Priority: 5
Private: No
Submitted By: Philipp Morger (swissphoenix)
Assigned to: Nobody/Anonymous (nobody)
Summary: eepro100.c:1570: nic_receive: Assertion `0' failed.
Initial Comment:
Hi there
:: System
Using kvm-58 on linux 2.6.22 (ubuntu gutsy) guest is openbsd-4.1
:: StartUp Command
Executing with parameters: -pidfile /var/run/kvm/raven.pid -no-acpi -k de-ch
-boot c -m 64 -hda /srv/kvm/vmx/4I/raven/wd0-openbsd-4_1-MkI.img -serial
telnet:localhost:10057,server,nowait -net
nic,vlan=1,model=i82559er,macaddr=00:16:3E:22:24:94 -net
tap,vlan=1,ifname=tap97 -net
nic,vlan=2,model=i82559er,macaddr=00:16:3E:46:81:09 -net
tap,vlan=2,ifname=tap98 -net
nic,vlan=3,model=i82559er,macaddr=00:16:3E:93:40:42 -net
tap,vlan=3,ifname=tap99 -net
nic,vlan=4,model=i82559er,macaddr=00:16:3E:49:97:04 -net
tap,vlan=4,ifname=tap100 -net
nic,vlan=5,model=i82559er,macaddr=00:16:3E:30:35:89 -net
tap,vlan=5,ifname=tap101 -net
nic,vlan=6,model=i82559er,macaddr=00:16:3E:12:02:75 -net
tap,vlan=6,ifname=tap102 -net
nic,vlan=7,model=i82559er,macaddr=00:16:3E:03:40:50 -net
tap,vlan=7,ifname=tap103 -net
nic,vlan=8,model=i82559er,macaddr=00:16:3E:93:90:45 -net
tap,vlan=8,ifname=tap104 -net
nic,vlan=9,model=i82559er,macaddr=00:16:3E:08:47:60 -net
tap,vlan=9,ifname=tap105
qemu: /usr/src/kvm-58/qemu/hw/eepro100.c:1570: nic_receive: Assertion `0'
failed.
/srv/kvm/scripts/kvm_start_wrapper.sh: line 59: 9116 Aborted
sudo -u kvm nice qemu ${COMMAND}
CRITICAL: We had a software error! RC: 134
:: Code
eepro100.c:1570
if (rfd_command 0x8000) {
/* EL bit is set, so this was the last frame. */
assert(0);
}
:: Figuring what happens...
I managed to figure what's an assertion is, so I guess the assert(0) always
fails, and thus qemu is intended to fail here, so assumption is that
rfd_command should never enter the state or the code is incomplete or some
other error, would be nice to know :)
regards
Philipp
--
Comment By: Jes Sorensen (jessorensen)
Date: 2011-01-07 15:41
Message:
Basic testing on this one seems to work here - not an openbsd wiz though,
so if you see this problem again, please open a new bug at launchpad.net
Thanks,
Jes
--
Comment By: Jes Sorensen (jessorensen)
Date: 2010-06-11 17:32
Message:
Hi,
I notice this is a very old bug - any chance you can test that this still
happens with a recent version of QEMU/KVM?
Cheers,
Jes
--
Comment By: Philipp Morger (swissphoenix)
Date: 2008-01-28 21:20
Message:
Logged In: YES
user_id=1433191
Originator: YES
Some documentation about the End Of List Bit
http://www.intel.com/design/network/specupdt/559er_si_11b.pdf
--
You can respond by visiting:
https://sourceforge.net/tracker/?func=detailatid=893831aid=1868937group_id=180599
--
To unsubscribe from this list: send the line unsubscribe kvm in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
[ kvm-Bugs-2314737 ] 100% host CPU usage with Win2k guest
Bugs item #2314737, was opened at 2008-11-19 13:53 Message generated for change (Comment added) made by jessorensen You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=893831aid=2314737group_id=180599 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: amd Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: krwi (krwi) Assigned to: Nobody/Anonymous (nobody) Summary: 100% host CPU usage with Win2k guest Initial Comment: After installing Windows 2000 guest with sp4 all seems work fine. But after short time Windows download a large pack of updates (about 68), when I installed this updates and rebooted guest host CPU utilization rised to 100% even if guest is idle. Before installing updates this problem was not observed. I trying with two Win2k installation with the same results. Host CPU utilization is equal to number of vCPUs, for example with -smp 2 host CPU usage is 200%. Host: 2x Quad Core Opteron 8356 64GB RAM OS: Gentoo 64bit kernel: 2.6.25 KVM-78 (modules from package not from kernel) Guest: Windows 2000 sp4 32bit started with command: kvm -M pc -m 2048 -smp 2 -name Win200032sp4 -monitor pty -localtime -boot d -drive file=/dev/MDvg_InstallVM/Win200032sp4,if=ide,index=0 -drive file=/mnt/MD_isos/Windows32/pl_win2000_pro_win2000_server.iso,if=ide,media=cdrom,index=2 -net nic,macaddr=00:16:3e:44:b2:45,vlan=0,model=virtio -net tap,fd=44,script=,vlan=0,ifname=vnet9 On the guest was installed virtio net driver. On the same host I running several other guests systems including Win2003 Server sp2 32bit, WinXP sp2 32bit and Linux Gentoo 64bit without problem like this. -- Comment By: Jes Sorensen (jessorensen) Date: 2011-01-07 15:48 Message: Hi, Do you still see this problem? If so, would you mind opening a bug about it over at launchpad.net? Thanks, Jes -- Comment By: Kevin Shanahan (kmshanah) Date: 2009-07-21 08:46 Message: I spent a whole lot of time today trying to work out which patch causes the host CPU usage to peg at 100% (even though the guest task manager shows everything is idle). As the original poster says, a clean install of Windows 2000 and up to service pack 4 works fine. As soon as I installed Update Rollup 1 for Windows 2000 SP4 (KB891861), the host CPU usage problem starts. I can uninstall the rollup package and the problem goes away again. http://support.microsoft.com/?kbid=891861 I tried going through all the individual updates that are supposed to be included in the rollup (listed on the KB page above), but installing them individually never made the issue come up. So it must be something else that is included in the rollup package but not documented I guess... something which modifies the method the OS uses for idling? FWIW, whatever is causing the host CPU usage to go so high does not cause the CPUs to get hot. They remain cool as if they were idle. This test was done on a dual Intel Xeon 5130 machine with 32GB RAM. Linux kernel 2.6.30, kvm-86. /usr/local/kvm/bin/qemu-system-x86_64 \ -smp 2 \ -localtime -m 2048 \ -drive if=ide,index=0,media=disk,file=disk1.img,boot=on \ -drive if=ide,index=1,media=cdrom \ -drive if=ide,index=2,media=disk,file=disk2.img \ -net nic,vlan=0,macaddr=52:54:00:12:34:6A,model=virtio \ -net tap,vlan=0,ifname=tap20,script=no \ -vnc 127.0.0.1:20 \ -usbdevice tablet \ -daemonize -- Comment By: Kevin Shanahan (kmshanah) Date: 2009-02-22 12:29 Message: Just confirming that the problem is still present with kvm-84 (on Linux 2.6.28.7). -- Comment By: Kevin Shanahan (kmshanah) Date: 2009-01-19 10:05 Message: Roy, you didn't say whether you have fully patched your install with all the post-sp4 updates. As the original reported said, the host CPU usage problem doesn't occur until after the post-sp4 updates have been applied. -- Comment By: roy anonymous (roy-anonymous) Date: 2009-01-19 09:46 Message: Sorry for my late reply. Here is my configuration. Host: Intel Q9550 8GB RAM OS: Fedora 10 64bit Kernel: 2.6.27.9-159.fc10.x86_64 KVM: kvm-74-10.fc10.x86_64 (All come with yum) Guest: Windows 2000 sp4 32bit: Start with virt-manager that come with Fedora 10. Yes, you could have SMP without ACPI one. For me, If I do a new installation with ACPI Multiprocessor (with acpi enabled in libvirt), it's working fine.(also try tested with virtio net driver installed) If I use Multiprocessor PC (with acpi disabled) it will have high cpu usage problem. May be this is really the problem
[ kvm-Bugs-2942079 ] [SR] qemu return form migrate command spend long time
Bugs item #2942079, was opened at 2010-01-29 17:13 Message generated for change (Comment added) made by haoxudong You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=893831aid=2942079group_id=180599 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open Resolution: Fixed Priority: 5 Private: No Submitted By: Xudong Hao (haoxudong) Assigned to: Nobody/Anonymous (nobody) Summary: [SR] qemu return form migrate command spend long time Initial Comment: Environment: kvm.git Commit: 51ef04ce3219d05c88f204342b2db294b5590d0a qemu-kvm Commit: 3e6f07b0c86b7fabfce72c1a42e54b2ad79dc587 Host Kernel Version: 2.6.33-rc4 Bug detailed description: -- KVM guest Save-Restore command changed, the new command function can work. However, when we do migrate exec:dd of=test.img in guest qemu console, it will cost much long time to return(~2 minutes of a 256M memory guest), the speed of saving only has ~1MB/s 344640+0 records in 344640+0 records out 176455680 bytes (176 MB) copied, 183.226 s, 963 kB/s Reproduce steps: 1) qemu-system-x86_64 -m 256 -smp 4 -net nic,macaddr=00:16:3e:57:87:39,model=rtl8139 -net tap,script=/etc/kvm/qemu-ifup -hda /share/xvs/var/guest.img 2) Ctrl+Alt+2migrate exec:dd of=test.img This step takes ~2 minutes with a 256MB memory guest, it will be more long for a 256MB memory guest. 3) qemu-system-x86_64 -m 256 -smp 4 -net nic,macaddr=00:16:3e:57:87:39,model=rtl8139 -net tap,script=/etc/kvm/qemu-ifup -hda /share/xvs/var/guest.img --incoming exec:dd if=test.img -- Comment By: Xudong Hao (haoxudong) Date: 2010-12-15 14:02 Message: On kvm 66fc6be8d2b04153b753182610f919faf9c705bc and qemu-kvm 53b6d3d5c2522e881c8d194f122de3114f6f76eb, the issue is not exist. it will take 10s to save, speed: ~45MB/s mark this bug fixed and verified. -- You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=893831aid=2942079group_id=180599 -- To unsubscribe from this list: send the line unsubscribe kvm in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
[ kvm-Bugs-1808970 ] CDROM eject doesn't work via Qemu Monitor
Bugs item #1808970, was opened at 2007-10-07 16:42 Message generated for change (Comment added) made by jessorensen You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=893831aid=1808970group_id=180599 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Closed Resolution: Works For Me Priority: 5 Private: No Submitted By: Technologov (technologov) Assigned to: Nobody/Anonymous (nobody) Summary: CDROM eject doesn't work via Qemu Monitor Initial Comment: When ejecting CD/DVD via Qemu monitor, then inserting another CD, the first CD is always shown, instead of the newly inserted one, unless I eject the CD from the guest. This bug prevents setup of Windows XP Tablet Edition, because this OS requires 2 CDs to install, and since this is Windows there are no workarounds. Guest: any Windows, especially Windows XP Tablet Edition. Host: Fedora7, 64-bit, Intel CPU, KVM-45. Other KVM versions and -no-kvm didn't help. -Alexey Technologov. 7.oct.2007. -- Comment By: Jes Sorensen (jessorensen) Date: 2010-12-02 11:30 Message: Works fine here under Fedora 14: A change like this was detected instantly: (qemu) eject drive-ide0-1-0 (qemu) change drive-ide0-1-0 en_winxp_sp1a_tablet_pc_cd1.iso Closing Jes -- Comment By: Wilco (paranoidt) Date: 2008-03-07 17:52 Message: Logged In: YES user_id=902376 Originator: NO It works for me (with some quirks) if I first eject the old CD: eject ide1-cd0 Then change to the new one: change ide1-cd0 /path/to/newiso.iso This does not always seem to work. Sometimes you have to access your CDROM (from the installation) so windows finds no cd. Then repeat these steps. Hope this helps. -- Comment By: Technologov (technologov) Date: 2007-10-12 16:58 Message: Logged In: YES user_id=1839746 Originator: YES chenghuan_jia: I have tried that too, with the exception that I used ISO instead of real CD-ROM. -Technologov -- Comment By: Neo Jia (chenghuan_jia) Date: 2007-10-12 07:10 Message: Logged In: YES user_id=446034 Originator: NO Can you try change cdrom /dev/scd0 after you insert the 2nd disc? Thanks, Neo -- You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=893831aid=1808970group_id=180599 -- To unsubscribe from this list: send the line unsubscribe kvm in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
[ kvm-Bugs-2494730 ] Guests stalling on kvm-82 / Linux 2.6.28
Bugs item #2494730, was opened at 2009-01-09 00:29 Message generated for change (Comment added) made by jessorensen You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=893831aid=2494730group_id=180599 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Closed Resolution: Duplicate Priority: 5 Private: No Submitted By: Kevin Shanahan (kmshanah) Assigned to: Nobody/Anonymous (nobody) Summary: Guests stalling on kvm-82 / Linux 2.6.28 Initial Comment: I am seeing periodic stalls in Linux and Windows guests with kvm-82 on an IBM X3550 server with 2 x Xeon 5130 CPUs and 32GB RAM. I am *reasonably* certain that this is a regression somewhere between kvm-72 and kvm-82. We had been running kvm-72 (actually, the debian kvm-source package) up until now and never noticed the problem. Now the stalls are very obvious. When the guest stalls, the at least one kvm process on the host gobbles up 100% CPU. I'll do my debugging with the Linux guest, as that's sure to be easier to deal with. As a simple demostration that the guest is unresponsive, here is the result of me pinging the guest from another machine on the (very quiet) LAN: --- hermes-old.wumi.org.au ping statistics --- 600 packets transmitted, 600 received, 0% packet loss, time 599659ms rtt min/avg/max/mdev = 0.255/181.211/6291.871/558.706 ms, pipe 7 The latency varies pretty badly, with spikes up to several seconds as you can see. The problem is not reproducable on other VT capable hardware that I have - e.g. my desktop has a E8400 CPU which runs the VMs just fine. Does knowing that make it any easier to guess where the problem might be? The Xeon 5130 does not have the smx, est, sse4_1, xsave, vnmi and flexpriority CPU flags that the E8400 does. Because this server is the only hardware I have which exhibits the problem and it's a production machine, I have limited times where I can do testing. However, I will try confirm that kvm-72 is okay and then bisect. Currently the host is running a 2.6.28 kernel with the kvm-82 modules. I guess I'm likely to have problems compiling the older kvm releases against this kernel, so I'll have to drop back to 2.6.27.something to run the tests. CPU Vendor: Intel CPU Type: Xeon 5130 Number of CPUs: 2 Host distribution: Debain Lenny/Sid KVM version: kvm-82 Host kernel: Linux 2.6.28 x86_64 Guest Distribution: Debian Etch Guest kernel: Linux 2.6.27.10 i686 Host's /proc/cpuinfo: processor : 0 vendor_id : GenuineIntel cpu family : 6 model : 15 model name : Intel(R) Xeon(R) CPU5130 @ 2.00GHz stepping: 6 cpu MHz : 1995.117 cache size : 4096 KB physical id : 0 siblings: 2 core id : 0 cpu cores : 2 apicid : 0 initial apicid : 0 fpu : yes fpu_exception : yes cpuid level : 10 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx lm constant_tsc arch_perfmon pebs bts rep_good pni dtes64 monitor ds_cpl vmx tm2 ssse3 cx16 xtpr pdcm dca lahf_lm tpr_shadow bogomips: 3990.23 clflush size: 64 cache_alignment : 64 address sizes : 36 bits physical, 48 bits virtual power management: processor : 1 vendor_id : GenuineIntel cpu family : 6 model : 15 model name : Intel(R) Xeon(R) CPU5130 @ 2.00GHz stepping: 6 cpu MHz : 1995.117 cache size : 4096 KB physical id : 0 siblings: 2 core id : 1 cpu cores : 2 apicid : 1 initial apicid : 1 fpu : yes fpu_exception : yes cpuid level : 10 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx lm constant_tsc arch_perfmon pebs bts rep_good pni dtes64 monitor ds_cpl vmx tm2 ssse3 cx16 xtpr pdcm dca lahf_lm tpr_shadow bogomips: 3989.96 clflush size: 64 cache_alignment : 64 address sizes : 36 bits physical, 48 bits virtual power management: processor : 2 vendor_id : GenuineIntel cpu family : 6 model : 15 model name : Intel(R) Xeon(R) CPU5130 @ 2.00GHz stepping: 6 cpu MHz : 1995.117 cache size : 4096 KB physical id : 3 siblings: 2 core id : 0 cpu cores : 2 apicid : 6 initial apicid : 6 fpu : yes fpu_exception : yes cpuid level : 10 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx lm constant_tsc arch_perfmon pebs bts rep_good pni dtes64 monitor ds_cpl vmx tm2 ssse3 cx16 xtpr pdcm dca
[ kvm-Bugs-2042889 ] guest: device offline, then kernel panic
Bugs item #2042889, was opened at 2008-08-08 13:16 Message generated for change (Settings changed) made by jessorensen You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=893831aid=2042889group_id=180599 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Closed Resolution: Duplicate Priority: 5 Private: No Submitted By: Rafal Wijata (ravpl) Assigned to: Nobody/Anonymous (nobody) Summary: guest: device offline, then kernel panic Initial Comment: host: kvm71, 64bit 2.6.18-92.1.6.el5, 16Gram, 2*X5450(8cores) guest: 64bit 2.6.18-92.1.6.el5, 3.5Gram, 2cpus, 5hdds on raw partitions(!). In the guest, i'm getting quite often messages like kernel: sd 0:0:0:0: ABORT operation started. kernel: sd 0:0:0:0: ABORT operation timed-out. [many times like that] [there was more messages concerning the device is offline, but I lost them, will update if it happens again] then filesystem gets remounted read-only, then kernel panics with message(part of the message only, that's what i got on the screen) FS: () GS:8039f000() knlGS: CS: 0010 DS: ES: CR0: 8005003b CR2: 00040013 CR3: 00201000 CR4: 06e0 Process sshd (pid: 23911, threadinfo 81006f53a000, task 8100dc2ca0c0) Stack: 800075dc 8100dc1ba960 8100dc1ba688 810096b52300 8100dd15acc0 8100dc1ba758 8100dc1ba758 810003f2a680 8000d11c 0008 0008 8100dd15acc0 Call Trace: [800075dc] kmem_cache_free+0x13c/0x1dd [8000d11c] dput+0xf6/0x114 [800125f3] __fput+0x16c/0x198 [8001a6a7] remove_vma+0x3d/0x64 [80039c60] exit_mmap+0xcf/0xf3 [8003bd73] mmput+0x30/0x83 [800151b6] do_exit+0x28b/0x8d0 [80048a1c] cpuset_exit+0x0/0x6c [8005d28d] tracesys+0xd5/0xe0 Code: f0 ff 0f 0f 88 6c 01 00 00 c3 f0 81 2f 00 00 00 01 74 05 e8 RIP [80064a2d] _spin_lock+0x0/0xa RSP 81006f53be10 CR2: 00040013 0Kernel panic - not syncing: Fatal exception Even though the kernel panic, the kvm process was still taking 100% CPU. gdb shows following info - no clue though if it's helpful in any way. Thread 4 (Thread 1938626880 (LWP 17006)): #0 0x00368bec6fa7 in ioctl () from /lib64/libc.so.6 #1 0x0050f726 in kvm_run (kvm=0x11b15010, vcpu=0) at libkvm.c:903 #2 0x004e9426 in kvm_cpu_exec (env=value optimized out) at /usr/src/kvm-71/qemu/qemu-kvm.c:218 #3 0x004e9700 in ap_main_loop (_env=value optimized out) at /usr/src/kvm-71/qemu/qemu-kvm.c:407 #4 0x00368ca062e7 in start_thread () from /lib64/libpthread.so.0 #5 0x00368bece3bd in clone () from /lib64/libc.so.6 Thread 3 (Thread 1087498560 (LWP 17007)): #0 0x00368bec6fa7 in ioctl () from /lib64/libc.so.6 #1 0x0050f726 in kvm_run (kvm=0x11b15010, vcpu=1) at libkvm.c:903 #2 0x004e9426 in kvm_cpu_exec (env=value optimized out) at /usr/src/kvm-71/qemu/qemu-kvm.c:218 #3 0x004e9700 in ap_main_loop (_env=value optimized out) at /usr/src/kvm-71/qemu/qemu-kvm.c:407 #4 0x00368ca062e7 in start_thread () from /lib64/libpthread.so.0 #5 0x00368bece3bd in clone () from /lib64/libc.so.6 Thread 2 (Thread 1949133120 (LWP 17014)): #0 0x00368ca0a687 in pthread_cond_timedwait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x003692202ee5 in handle_fildes_io () from /lib64/librt.so.1 #2 0x00368ca062e7 in start_thread () from /lib64/libpthread.so.0 #3 0x00368bece3bd in clone () from /lib64/libc.so.6 Thread 1 (Thread 47523282295136 (LWP 16990)): #0 0x00368bec7922 in select () from /lib64/libc.so.6 #1 0x004094b2 in main_loop_wait (timeout=value optimized out) at /usr/src/kvm-71/qemu/vl.c:7545 #2 0x004e9342 in kvm_main_loop () at /usr/src/kvm-71/qemu/qemu-kvm.c:587 #3 0x00411662 in main (argc=20, argv=0x7fffca7a9b38) at /usr/src/kvm-71/qemu/vl.c:7705 #0 0x00368bec7922 in select () from /lib64/libc.so.6 -- Comment By: Jes Sorensen (jessorensen) Date: 2010-11-30 12:39 Message: This looks like a duplicate of https://bugs.launchpad.net/qemu/+bug/587993 If you can reproduce this problem, it would be great if you can add the info to the bug in launchpad. Thanks, Jes -- Comment By: Rafal Wijata (ravpl) Date: 2008-08-13 10:53 Message: Logged In: YES user_id=996150 Originator: YES Another crash with guest bt, please advise how to debug? R13: 8100dd107000 R14: 80077090 R15: 80418e80 FS: () GS:8039f000() knlGS
[ kvm-Bugs-2235570 ] 100% cpu usage with KVM-78
Bugs item #2235570, was opened at 2008-11-07 18:58 Message generated for change (Comment added) made by jessorensen You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=893831aid=2235570group_id=180599 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: James Bailey (dgym) Assigned to: Nobody/Anonymous (nobody) Summary: 100% cpu usage with KVM-78 Initial Comment: When I start a guest it consumes 100% CPU on the host, even after it has booted and is sitting idle at a login prompt. The odd thing is that if I then live migrate the guest to another (identical) machine, the problem goes away. The guest continues to run just fine on the new host, and the new host's CPU usage is normal. I have tried the obvious: starting on the other machine and migrating to the first, and even multiple migrations. It is always the same, the qemu-system-x86_64 process sits at 100% unless it was started with -incoming ... Migrating machines every time you start up is not a very convenient work around, so it would be nice to find out what is different between the normal start up and the -incoming start up and fix the former. Versions and settings: KVM: 78 Host Kernel: Vanilla 2.6.25.2 Compiled with: gcc version 4.1.2 CPU: AMD Phenom Guest OS: Linux (have tried a few distros) Guest Kernels: Debian etch, and an OpenVZ 2.6.18 Command line: qemu-system-x86_64 -m 128 -smp 1 -drive file=/dev/drbd0 -vnc :1 Things I have tried which have not worked: Using -nographics. Using SDL graphics. Using -snapshot, and doing a savevm and loadvm. Things I have tried which have worked: Using -no-kvm. I have attached gdb and found the busy thread, here is its backtrace: #0 0x7f06f017ea17 in ioctl () from /lib/libc.so.6 #1 0x0051b423 in kvm_run (kvm=0xa93040, vcpu=0) at libkvm.c:892 #2 0x004f1116 in kvm_cpu_exec (env=value optimized out) at /opt/setup/kvm-78/qemu/qemu-kvm.c:230 #3 0x004f13e4 in ap_main_loop (_env=value optimized out) at /opt/setup/kvm-78/qemu/qemu-kvm.c:432 #4 0x7f06f0565135 in start_thread () from /lib/libpthread.so.0 #5 0x7f06f01852ce in clone () from /lib/libc.so.6 #6 0x in ?? () Because this indicates business within the kernel module it is as far as I have got. I will attempt to identify the previous working version, I know I never had this problem with 68, but I haven't yet tried anything in between. -- Comment By: Jes Sorensen (jessorensen) Date: 2010-11-29 09:00 Message: Hi, Given that there has been no updates to this bug for a long time, I presume the problem has been resolved? Would you mind letting us know if you still see this problem? Thanks, Jes -- Comment By: James Bailey (dgym) Date: 2008-11-08 22:35 Message: Using the -no-kvm-pit option fixes the CPU problem. There were some changes to arch/x86/kvm/i8254.c so this definitely looks PIT related. -- Comment By: James Bailey (dgym) Date: 2008-11-08 21:28 Message: I have been able to narrow the problem down to a single commit. KVM-76 was fine, but I get this broken behaviour with KVM-77. I checked out the KVM userspace and went back to 76, and I also checked out the KVM kernel and tried different versions. Commit 666c4a43cba0cbaa30cd3c86b515dfdab2a6fa98 on git://git.kernel.org/pub/scm/linux/kernel/git/avi/kvm.git is the first version to show the 100% CPU behaviour. -- You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=893831aid=2235570group_id=180599 -- To unsubscribe from this list: send the line unsubscribe kvm in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
[ kvm-Bugs-2905358 ] Doesn't support MS-DOS compatibility FPU mode
Bugs item #2905358, was opened at 2009-11-28 16:37 Message generated for change (Comment added) made by jessorensen You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=893831aid=2905358group_id=180599 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Closed Resolution: Later Priority: 5 Private: No Submitted By: Samuel Thibault (youpi_486) Assigned to: Nobody/Anonymous (nobody) Summary: Doesn't support MS-DOS compatibility FPU mode Initial Comment: Hello, Apparently, KVM always enables CR0_NE, i.e. FPU errors are always reported via the EXCP10_COPR exception rather than via the FPU interrupt. This breaks operating systems which assume MS-DOS compatability mode, i.e. exceptions are always reported via the FPU interrupt (like GNU Mach). Samuel -- Comment By: Jes Sorensen (jessorensen) Date: 2010-11-29 17:17 Message: Hi, I checked with Avi, this is still not supported but patches are welcome, so I have opened an RFE in bugzilla.kernel.org and migrated the bug there: https://bugzilla.kernel.org/show_bug.cgi?id=23992 Please use the bugzilla thread for further discussions of this problem. Thanks, Jes -- You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=893831aid=2905358group_id=180599 -- To unsubscribe from this list: send the line unsubscribe kvm in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
[ kvm-Bugs-2493108 ] Win2k problems on some (not all) Intel hosts
Bugs item #2493108, was opened at 2009-01-08 12:53 Message generated for change (Comment added) made by kmshanah You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=893831aid=2493108group_id=180599 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: intel Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Kevin Shanahan (kmshanah) Assigned to: Nobody/Anonymous (nobody) Summary: Win2k problems on some (not all) Intel hosts Initial Comment: I have a Windows 2000 guest that I have been testing on an desktop machine (E8400 CPU) and that has been working well (apart from being affected by bug 2314737). When I moved (not a live migration, just shutdown, rsync and boot on the new server) the guest to our server, which is an IBM X3550 with two Xeon 5130 CPUs the guest has short freezes where the guest CPU usage spikes on both virtual CPUs and the guest becomes unresponsive for several seconds at a time. These guest CPU spikes can last over a minute, but the guest might have moments where it briefly responds to the delayed keystrokes, etc. every few seconds. One symptom of this behaviour for me last night was that Win2k AD replication was failing, so it's not just interactive use that suffers. Something I noticed that may be relevant - due to the other bug (2314737) which causes each guest CPU to use 100% of the host CPU, whether the guest CPU is idle or not, I can tell when the guest is having this problem by looking at the 'top' output on the host. When the guest is operating normally, the host will show the qemu-system-x86_64 process using 200% CPU (the guest is using -smp 2). However, when the guest is misbehaving, the host will show the qemu-system-x86_64 process only using _100%_ CPU. Maybe one of the threads is stuck, or something is forcing them to share a single core? Both hosts are running Debian Lenny/Sid, 64-bit with a kernel.org 2.6.28 kernel and kvm-82. The command line used in both cases: /usr/local/kvm/bin/qemu-system-x86_64 \ -smp 2 \ -localtime -m 2048 \ -drive if=ide,file=kvm-ks-02a.img,index=0,media=disk,boot=on \ -drive if=ide,file=kvm-ks-02b.img,index=2,media=disk \ -net nic,vlan=0,macaddr=52:54:00:12:34:68,model=virtio \ -net tap,vlan=0,ifname=tap18,script=no \ -vnc 127.0.0.1:18 -usbdevice tablet \ -daemonize CPUs on the good host: processor : 0 vendor_id : GenuineIntel cpu family : 6 model : 23 model name : Intel(R) Core(TM)2 Duo CPU E8400 @ 3.00GHz stepping: 10 cpu MHz : 3000.000 cache size : 6144 KB physical id : 0 siblings: 2 core id : 0 cpu cores : 2 apicid : 0 initial apicid : 0 fpu : yes fpu_exception : yes cpuid level : 13 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx lm constant_tsc arch_perfmon pebs bts rep_good pni dtes64 monitor ds_cpl vmx smx est tm2 ssse3 cx16 xtpr pdcm sse4_1 xsave lahf_lm tpr_shadow vnmi flexpriority bogomips: 5984.98 clflush size: 64 cache_alignment : 64 address sizes : 36 bits physical, 48 bits virtual power management: processor : 1 vendor_id : GenuineIntel cpu family : 6 model : 23 model name : Intel(R) Core(TM)2 Duo CPU E8400 @ 3.00GHz stepping: 10 cpu MHz : 3000.000 cache size : 6144 KB physical id : 0 siblings: 2 core id : 1 cpu cores : 2 apicid : 1 initial apicid : 1 fpu : yes fpu_exception : yes cpuid level : 13 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx lm constant_tsc arch_perfmon pebs bts rep_good pni dtes64 monitor ds_cpl vmx smx est tm2 ssse3 cx16 xtpr pdcm sse4_1 xsave lahf_lm tpr_shadow vnmi flexpriority bogomips: 5984.97 clflush size: 64 cache_alignment : 64 address sizes : 36 bits physical, 48 bits virtual power management: And the bad host: processor : 0 vendor_id : GenuineIntel cpu family : 6 model : 15 model name : Intel(R) Xeon(R) CPU5130 @ 2.00GHz stepping: 6 cpu MHz : 1995.117 cache size : 4096 KB physical id : 0 siblings: 2 core id : 0 cpu cores : 2 apicid : 0 initial apicid : 0 fpu : yes fpu_exception : yes cpuid level : 10 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx lm constant _tsc arch_perfmon pebs bts rep_good pni dtes64 monitor ds_cpl vmx tm2 ssse3
[ kvm-Bugs-2494730 ] Guests stalling on kvm-82 / Linux 2.6.28
Bugs item #2494730, was opened at 2009-01-09 09:59 Message generated for change (Comment added) made by kmshanah You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=893831aid=2494730group_id=180599 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Kevin Shanahan (kmshanah) Assigned to: Nobody/Anonymous (nobody) Summary: Guests stalling on kvm-82 / Linux 2.6.28 Initial Comment: I am seeing periodic stalls in Linux and Windows guests with kvm-82 on an IBM X3550 server with 2 x Xeon 5130 CPUs and 32GB RAM. I am *reasonably* certain that this is a regression somewhere between kvm-72 and kvm-82. We had been running kvm-72 (actually, the debian kvm-source package) up until now and never noticed the problem. Now the stalls are very obvious. When the guest stalls, the at least one kvm process on the host gobbles up 100% CPU. I'll do my debugging with the Linux guest, as that's sure to be easier to deal with. As a simple demostration that the guest is unresponsive, here is the result of me pinging the guest from another machine on the (very quiet) LAN: --- hermes-old.wumi.org.au ping statistics --- 600 packets transmitted, 600 received, 0% packet loss, time 599659ms rtt min/avg/max/mdev = 0.255/181.211/6291.871/558.706 ms, pipe 7 The latency varies pretty badly, with spikes up to several seconds as you can see. The problem is not reproducable on other VT capable hardware that I have - e.g. my desktop has a E8400 CPU which runs the VMs just fine. Does knowing that make it any easier to guess where the problem might be? The Xeon 5130 does not have the smx, est, sse4_1, xsave, vnmi and flexpriority CPU flags that the E8400 does. Because this server is the only hardware I have which exhibits the problem and it's a production machine, I have limited times where I can do testing. However, I will try confirm that kvm-72 is okay and then bisect. Currently the host is running a 2.6.28 kernel with the kvm-82 modules. I guess I'm likely to have problems compiling the older kvm releases against this kernel, so I'll have to drop back to 2.6.27.something to run the tests. CPU Vendor: Intel CPU Type: Xeon 5130 Number of CPUs: 2 Host distribution: Debain Lenny/Sid KVM version: kvm-82 Host kernel: Linux 2.6.28 x86_64 Guest Distribution: Debian Etch Guest kernel: Linux 2.6.27.10 i686 Host's /proc/cpuinfo: processor : 0 vendor_id : GenuineIntel cpu family : 6 model : 15 model name : Intel(R) Xeon(R) CPU5130 @ 2.00GHz stepping: 6 cpu MHz : 1995.117 cache size : 4096 KB physical id : 0 siblings: 2 core id : 0 cpu cores : 2 apicid : 0 initial apicid : 0 fpu : yes fpu_exception : yes cpuid level : 10 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx lm constant_tsc arch_perfmon pebs bts rep_good pni dtes64 monitor ds_cpl vmx tm2 ssse3 cx16 xtpr pdcm dca lahf_lm tpr_shadow bogomips: 3990.23 clflush size: 64 cache_alignment : 64 address sizes : 36 bits physical, 48 bits virtual power management: processor : 1 vendor_id : GenuineIntel cpu family : 6 model : 15 model name : Intel(R) Xeon(R) CPU5130 @ 2.00GHz stepping: 6 cpu MHz : 1995.117 cache size : 4096 KB physical id : 0 siblings: 2 core id : 1 cpu cores : 2 apicid : 1 initial apicid : 1 fpu : yes fpu_exception : yes cpuid level : 10 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx lm constant_tsc arch_perfmon pebs bts rep_good pni dtes64 monitor ds_cpl vmx tm2 ssse3 cx16 xtpr pdcm dca lahf_lm tpr_shadow bogomips: 3989.96 clflush size: 64 cache_alignment : 64 address sizes : 36 bits physical, 48 bits virtual power management: processor : 2 vendor_id : GenuineIntel cpu family : 6 model : 15 model name : Intel(R) Xeon(R) CPU5130 @ 2.00GHz stepping: 6 cpu MHz : 1995.117 cache size : 4096 KB physical id : 3 siblings: 2 core id : 0 cpu cores : 2 apicid : 6 initial apicid : 6 fpu : yes fpu_exception : yes cpuid level : 10 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx lm constant_tsc arch_perfmon pebs bts rep_good pni dtes64 monitor ds_cpl vmx tm2 ssse3 cx16 xtpr pdcm dca lahf_lm
[ kvm-Bugs-2493108 ] Win2k problems on some (not all) Intel hosts
Bugs item #2493108, was opened at 2009-01-08 03:23 Message generated for change (Comment added) made by jessorensen You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=893831aid=2493108group_id=180599 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: intel Group: None Status: Closed Resolution: Out of Date Priority: 5 Private: No Submitted By: Kevin Shanahan (kmshanah) Assigned to: Nobody/Anonymous (nobody) Summary: Win2k problems on some (not all) Intel hosts Initial Comment: I have a Windows 2000 guest that I have been testing on an desktop machine (E8400 CPU) and that has been working well (apart from being affected by bug 2314737). When I moved (not a live migration, just shutdown, rsync and boot on the new server) the guest to our server, which is an IBM X3550 with two Xeon 5130 CPUs the guest has short freezes where the guest CPU usage spikes on both virtual CPUs and the guest becomes unresponsive for several seconds at a time. These guest CPU spikes can last over a minute, but the guest might have moments where it briefly responds to the delayed keystrokes, etc. every few seconds. One symptom of this behaviour for me last night was that Win2k AD replication was failing, so it's not just interactive use that suffers. Something I noticed that may be relevant - due to the other bug (2314737) which causes each guest CPU to use 100% of the host CPU, whether the guest CPU is idle or not, I can tell when the guest is having this problem by looking at the 'top' output on the host. When the guest is operating normally, the host will show the qemu-system-x86_64 process using 200% CPU (the guest is using -smp 2). However, when the guest is misbehaving, the host will show the qemu-system-x86_64 process only using _100%_ CPU. Maybe one of the threads is stuck, or something is forcing them to share a single core? Both hosts are running Debian Lenny/Sid, 64-bit with a kernel.org 2.6.28 kernel and kvm-82. The command line used in both cases: /usr/local/kvm/bin/qemu-system-x86_64 \ -smp 2 \ -localtime -m 2048 \ -drive if=ide,file=kvm-ks-02a.img,index=0,media=disk,boot=on \ -drive if=ide,file=kvm-ks-02b.img,index=2,media=disk \ -net nic,vlan=0,macaddr=52:54:00:12:34:68,model=virtio \ -net tap,vlan=0,ifname=tap18,script=no \ -vnc 127.0.0.1:18 -usbdevice tablet \ -daemonize CPUs on the good host: processor : 0 vendor_id : GenuineIntel cpu family : 6 model : 23 model name : Intel(R) Core(TM)2 Duo CPU E8400 @ 3.00GHz stepping: 10 cpu MHz : 3000.000 cache size : 6144 KB physical id : 0 siblings: 2 core id : 0 cpu cores : 2 apicid : 0 initial apicid : 0 fpu : yes fpu_exception : yes cpuid level : 13 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx lm constant_tsc arch_perfmon pebs bts rep_good pni dtes64 monitor ds_cpl vmx smx est tm2 ssse3 cx16 xtpr pdcm sse4_1 xsave lahf_lm tpr_shadow vnmi flexpriority bogomips: 5984.98 clflush size: 64 cache_alignment : 64 address sizes : 36 bits physical, 48 bits virtual power management: processor : 1 vendor_id : GenuineIntel cpu family : 6 model : 23 model name : Intel(R) Core(TM)2 Duo CPU E8400 @ 3.00GHz stepping: 10 cpu MHz : 3000.000 cache size : 6144 KB physical id : 0 siblings: 2 core id : 1 cpu cores : 2 apicid : 1 initial apicid : 1 fpu : yes fpu_exception : yes cpuid level : 13 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx lm constant_tsc arch_perfmon pebs bts rep_good pni dtes64 monitor ds_cpl vmx smx est tm2 ssse3 cx16 xtpr pdcm sse4_1 xsave lahf_lm tpr_shadow vnmi flexpriority bogomips: 5984.97 clflush size: 64 cache_alignment : 64 address sizes : 36 bits physical, 48 bits virtual power management: And the bad host: processor : 0 vendor_id : GenuineIntel cpu family : 6 model : 15 model name : Intel(R) Xeon(R) CPU5130 @ 2.00GHz stepping: 6 cpu MHz : 1995.117 cache size : 4096 KB physical id : 0 siblings: 2 core id : 0 cpu cores : 2 apicid : 0 initial apicid : 0 fpu : yes fpu_exception : yes cpuid level : 10 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx lm constant _tsc arch_perfmon pebs bts rep_good pni dtes64 monitor ds_cpl
[ kvm-Bugs-2432316 ] hotplug inexistent device will kill guest
Bugs item #2432316, was opened at 2008-12-16 10:44 Message generated for change (Comment added) made by haoxudong You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=893831aid=2432316group_id=180599 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Closed Resolution: Works For Me Priority: 5 Private: No Submitted By: Jiajun Xu (jiajun) Assigned to: Nobody/Anonymous (nobody) Summary: hotplug inexistent device will kill guest Initial Comment: Host OS (ia32/ia32e/IA64): ia32e Kernel Commit: KVM-77, 2.6.27-rc9, 4330ed8ed4da360ac1ca14b0fddff4c05b10de16 Userspace Commit: bebd13cd8eac7ac9cc3a1b2b3bbdc28a0b0efd9a Host Kernel Version: RHEL5u2 Bug detailed description: -- We create one guest, then do VT-d device hotplug, if we add a inexistent BDF number of device, guest will be killed. host print: get_real_device: /sys/bus/pci/devices/:00:30.0/config: No such file or directory init_assigned_device: Error: Couldn't get real device (00:30.0)! assigned_dev_pci_read_config: pread failed, ret = -1 errno = 29 Reproduce steps: 1) install kvm and create one guest 2) enter guest qemu monitor(print Ctrl+Alt+2) 3) run command pci_add 0 host host=00:30.0, 00:30.0 is a inexistent bdf number 4) guest will be killed -- Comment By: Xudong Hao (haoxudong) Date: 2010-11-29 10:31 Message: I checked on latest kvm 9ee00410d82a7c5cab5ae347d97fbf8a95c55506 and qemu-kvm b377474e589e5a1fe2abc7b13fafa8bad802637a, No crash now on RHEL5 system too. Sure, close this bug. -- Comment By: Jes Sorensen (jessorensen) Date: 2010-11-26 17:04 Message: Hi, Tested with upstream qemu/kvm - when trying to add a non existing device I get an error message, but no crash. If you still see this problem with a recent version of KVM please file a new bug in launhpad. If you have issues with the current RHEL5 host, please file a bug in Red Hat's bugzilla. Thanks, Jes -- You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=893831aid=2432316group_id=180599 -- To unsubscribe from this list: send the line unsubscribe kvm in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
[ kvm-Bugs-2525768 ] kvm image corruption
Bugs item #2525768, was opened at 2009-01-21 08:03 Message generated for change (Comment added) made by jessorensen You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=893831aid=2525768group_id=180599 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Closed Resolution: Out of Date Priority: 8 Private: No Submitted By: Daniel van Vugt (danv) Assigned to: Nobody/Anonymous (nobody) Summary: kvm image corruption Initial Comment: Creating a new bug from my original problems detailed in bug 2490866, because that technically is a different problem. Reproduced with kvm-83 and kvm-82 vanilla. Host: Ubuntu 8.04 amd64, Intel Q6600 Guests: Windows 2003 Server, Windows 7 beta at least. After shutting down the guest cleanly, it's image file is (often but not always) corrupt and unbootable. A fact confirmed by the change in information reported by qemu-img info Example 1 (qcow2 image): $ qemu-img info windows7beta.qcow2 image: windows7beta.qcow2 file format: qcow2 virtual size: 20G (21474836480 bytes) disk size: 5.0G cluster_size: 4096 Snapshot list: ID TAG VM SIZE DATE VM CLOCK 1 Fresh_install 1.3M 2009-01-09 15:34:31 00:00:00.000 2 Activated_kvm-82 1.3M 2009-01-09 15:43:27 00:00:00.000 $ qemu -m 512 -usbdevice tablet -redir tcp:3389::3389 windows7beta.qcow2 (use and then shut down windows) $ qemu-img info windows7beta.qcow2 image: windows7beta.qcow2 file format: raw INVALID virtual size: 5.0G (5353566208 bytes) - INVALID disk size: 5.0G $ qemu -m 512 -usbdevice tablet -redir tcp:3389::3389 windows7beta.qcow2 -S (qemu) info snapshots Snapshot devices: ide0-hd0 bdrv_snapshot_list: error -95 (And the image won't boot) Example 2 (raw image converted from Example 1): $ qemu-img info windows7beta.raw image: windows7beta.raw file format: raw virtual size: 20G (21474836480 bytes) disk size: 4.7G (Install and test lots on the guest) $ qemu-img info windows7beta.raw image: windows7beta.raw file format: raw virtual size: 7.5G (8049315840 bytes) - INVALID disk size: 7.5G (And now the image won't boot) -- Comment By: Jes Sorensen (jessorensen) Date: 2010-11-29 08:37 Message: Hi Dan, Thank you for the feedback, and sorry we didn't get to you in better time. If you see something like this again, please go ahead an open a new bug in https://bugs.launchpad.net/qemu/ It should get better attention over there. Thanks, Jes -- Comment By: Daniel van Vugt (danv) Date: 2010-11-27 09:04 Message: I don't have access to these VMs any more. Also I don't _remember_ experiencing this problem for quite a while. Assume it's fixed because I can no longer test or verify the bug. Close please... -- Comment By: Jes Sorensen (jessorensen) Date: 2010-11-26 09:28 Message: Hi, There has been a lot of fixes to the qcow2 code since your bug report - are you still able to reproduce it, or can we close the bug? Thanks, Jes -- Comment By: Daniel van Vugt (danv) Date: 2009-05-06 10:14 Message: Sad to say... I have reproduced the bug on kvm-85, qemu-0.10.0, qemu-0.10.2 and qemu-0.10.3. They all still corrupt some qcow2 images. -- Comment By: Daniel van Vugt (danv) Date: 2009-02-16 03:16 Message: Confirmed the bug is still present in kvm-84. Just booting up my guest, opening the browser and then shutting down turns the qcow2 image into a corrupt unbootable raw image file. -- You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=893831aid=2525768group_id=180599 -- To unsubscribe from this list: send the line unsubscribe kvm in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
[ kvm-Bugs-2796640 ] KVM Regression from 2.6.28-11 to 2.6.30-rc5
Bugs item #2796640, was opened at 2009-05-26 03:00 Message generated for change (Comment added) made by jessorensen You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=893831aid=2796640group_id=180599 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Closed Resolution: Out of Date Priority: 5 Private: No Submitted By: Bob Manners (bobmanners) Assigned to: Nobody/Anonymous (nobody) Summary: KVM Regression from 2.6.28-11 to 2.6.30-rc5 Initial Comment: Changing from the Ubuntu 09.04 stock kernel 2.6.28-11 to the current 'alpha' kernel in the Ubuntu development repository for 'Karmic' 2.6.30-rc5, some (but not all) of my KVM guests stop booting. I have the following guest OSs installed as KVM virtual machines: Ubuntu 09.04, FreeBSD 7.1, Minix 3, OpenSolaris 08.11, Windows XP and Windows 7RC Under 2.6.28-11 these all boot and run OK. With kernel 2.6.30-rc5, Ubuntu, FreeBSD and Minix boot and run OK, but OpenSolaris 08.11, Windows XP and Windows 7RC fail to boot. They appear to freeze very early in the boot process, after the boot loader is done and the OS kernel itself starts loading. There are no strange messages in the host system logs that I am aware of. When the guest OS freezes, it pins one of my CPUs at 100% utilization (I have KVM set to only give one CPU to the guest). This looks like a regression under 2.6.30-rc5. It is possible that it is caused by a Ubuntu patch, and I have filed a bug in Launchpad, but I suspect that this is an upstream problem, and so I am reporting it here also. Please let me know what I can do to assist in debugging this. -- Comment By: Jes Sorensen (jessorensen) Date: 2010-11-29 08:55 Message: Hi Bob, Given that you have a launchpad bug open too, and that it smells like an Ubuntu specific bug, plus we cannot reproduce it, I will close this as out of date. If we hit it again, lets track it over at bugs.launchpad.net/qemu Thanks for getting back on this! Jes -- Comment By: Bob Manners (bobmanners) Date: 2010-11-26 15:21 Message: I only experienced this problem on Intel Core Duo. On another system which has the more common Intel Core 2 Duo CPU I don't see this issue. Unfortunately my old (2006) laptop which was the Core Duo machine finally died last week so I am unable to confirm whether this KVM bug is still present in the 2.6.35 kernel (Ubuntu Maverick). -- Comment By: Jes Sorensen (jessorensen) Date: 2010-11-26 11:36 Message: Hi, Has this issue been resolved for you? Thanks, Jes -- Comment By: Kenni (kelu6) Date: 2009-05-28 10:26 Message: Your CPU still has the NX flag, which apparently also was my issue: http://thread.gmane.org/gmane.comp.emulators.kvm.devel/31206/focus=31774 -- Comment By: Bob Manners (bobmanners) Date: 2009-05-28 02:22 Message: In response to kelu6's question, actually I am running 32 bit host / 32 bit guest. My CPU is Intel Core Duo (not Core2 Duo) which is a 32 bit CPU: b...@gecko2:~$ cat /proc/cpuinfo processor : 0 vendor_id : GenuineIntel cpu family : 6 model : 14 model name : Genuine Intel(R) CPU T2400 @ 1.83GHz stepping: 8 cpu MHz : 1000.000 cache size : 2048 KB physical id : 0 siblings: 2 core id : 0 cpu cores : 2 apicid : 0 initial apicid : 0 fdiv_bug: no hlt_bug : no f00f_bug: no coma_bug: no fpu : yes fpu_exception : yes cpuid level : 10 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe nx constant_tsc arch_perfmon bts pni monitor vmx est tm2 xtpr pdcm
[ kvm-Bugs-1885747 ] KVM halts, when starting Fedora8 SMP guest
Bugs item #1885747, was opened at 2008-02-03 16:34 Message generated for change (Comment added) made by jessorensen You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=893831aid=1885747group_id=180599 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Closed Resolution: Out of Date Priority: 5 Private: No Submitted By: Technologov (technologov) Assigned to: Nobody/Anonymous (nobody) Summary: KVM halts, when starting Fedora8 SMP guest Initial Comment: This bug is similar to bug: [ 1885713 ] KVM crashes, when restarting Fedora8 SMP guest http://sourceforge.net/tracker/index.php?func=detailaid=1885713group_id=180599atid=893831 Host: Fedora7/x64, KVM-60, AMD. Guest:Fedora8/x64 Qemu Command:/usr/local/bin/qemu-system-x86_64 -hda /isos/disks-vm/alexeye/Fedora8-64.vmdk -m 1024 -smp 4 -net nic,macaddr=52:54:00:12:34:01,model=rtl8139 -net user -name F8-x64-SMP During guest OS boot, the VM halts/stucks. Trying to restart that results in a VM crash. Doesn't happens with single CPU. -Technologov, 3.2.2008. -- Comment By: Jes Sorensen (jessorensen) Date: 2010-11-29 08:58 Message: Closing as per xichencn's comment on 2008-05-14, should be fixed by now. -- Comment By: Jes Sorensen (jessorensen) Date: 2010-06-18 15:43 Message: Hi, Could you please let us know if this is still a problem with recent KVM and qemu-kvm? I would like to try and eliminate the bugs that are no longer valid so we can focus on fixing the ones that are. Thanks, Jes -- Comment By: Xi Chen (xichencn) Date: 2008-05-14 11:33 Message: Logged In: YES user_id=2081279 Originator: NO Run Fedora8/x64 guest on RHEL5. kvm and kvm-u are up to date of git. AMD 8220 dual-core. Command:qemu-system-x86_64 -hda image/fc8_x64.vmdk -m 1024 -smp 4 -net nic,macaddr=52:54:00:12:34:01,model=rtl8139 -net user -name F8-x64-SMP The guest works fine. -- You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=893831aid=1885747group_id=180599 -- To unsubscribe from this list: send the line unsubscribe kvm in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
[ kvm-Bugs-2525768 ] kvm image corruption
Bugs item #2525768, was opened at 2009-01-21 16:03 Message generated for change (Comment added) made by danv You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=893831aid=2525768group_id=180599 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open Resolution: None Priority: 8 Private: No Submitted By: Daniel van Vugt (danv) Assigned to: Nobody/Anonymous (nobody) Summary: kvm image corruption Initial Comment: Creating a new bug from my original problems detailed in bug 2490866, because that technically is a different problem. Reproduced with kvm-83 and kvm-82 vanilla. Host: Ubuntu 8.04 amd64, Intel Q6600 Guests: Windows 2003 Server, Windows 7 beta at least. After shutting down the guest cleanly, it's image file is (often but not always) corrupt and unbootable. A fact confirmed by the change in information reported by qemu-img info Example 1 (qcow2 image): $ qemu-img info windows7beta.qcow2 image: windows7beta.qcow2 file format: qcow2 virtual size: 20G (21474836480 bytes) disk size: 5.0G cluster_size: 4096 Snapshot list: ID TAG VM SIZE DATE VM CLOCK 1 Fresh_install 1.3M 2009-01-09 15:34:31 00:00:00.000 2 Activated_kvm-82 1.3M 2009-01-09 15:43:27 00:00:00.000 $ qemu -m 512 -usbdevice tablet -redir tcp:3389::3389 windows7beta.qcow2 (use and then shut down windows) $ qemu-img info windows7beta.qcow2 image: windows7beta.qcow2 file format: raw INVALID virtual size: 5.0G (5353566208 bytes) - INVALID disk size: 5.0G $ qemu -m 512 -usbdevice tablet -redir tcp:3389::3389 windows7beta.qcow2 -S (qemu) info snapshots Snapshot devices: ide0-hd0 bdrv_snapshot_list: error -95 (And the image won't boot) Example 2 (raw image converted from Example 1): $ qemu-img info windows7beta.raw image: windows7beta.raw file format: raw virtual size: 20G (21474836480 bytes) disk size: 4.7G (Install and test lots on the guest) $ qemu-img info windows7beta.raw image: windows7beta.raw file format: raw virtual size: 7.5G (8049315840 bytes) - INVALID disk size: 7.5G (And now the image won't boot) -- Comment By: Daniel van Vugt (danv) Date: 2010-11-27 16:04 Message: I don't have access to these VMs any more. Also I don't _remember_ experiencing this problem for quite a while. Assume it's fixed because I can no longer test or verify the bug. Close please... -- Comment By: Jes Sorensen (jessorensen) Date: 2010-11-26 16:28 Message: Hi, There has been a lot of fixes to the qcow2 code since your bug report - are you still able to reproduce it, or can we close the bug? Thanks, Jes -- Comment By: Daniel van Vugt (danv) Date: 2009-05-06 16:14 Message: Sad to say... I have reproduced the bug on kvm-85, qemu-0.10.0, qemu-0.10.2 and qemu-0.10.3. They all still corrupt some qcow2 images. -- Comment By: Daniel van Vugt (danv) Date: 2009-02-16 11:16 Message: Confirmed the bug is still present in kvm-84. Just booting up my guest, opening the browser and then shutting down turns the qcow2 image into a corrupt unbootable raw image file. -- You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=893831aid=2525768group_id=180599 -- To unsubscribe from this list: send the line unsubscribe kvm in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
[ kvm-Bugs-2493498 ] Link to latest virtio drivers dead in wiki
Bugs item #2493498, was opened at 2009-01-08 10:34 Message generated for change (Comment added) made by jessorensen You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=893831aid=2493498group_id=180599 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Closed Resolution: Fixed Priority: 5 Private: No Submitted By: Kenni (kelu6) Assigned to: Nobody/Anonymous (nobody) Summary: Link to latest virtio drivers dead in wiki Initial Comment: I've previously had success using the latest Virtio Windows drivers from the KVM Wiki instead of the latest (and older) version from Sourceforge on Windows Vista and 2008. The following page in the wiki links to both the new drivers and the older drivers currently in Sourceforge: http://kvm.qumranet.com/kvmwiki/VirtioWindowsDrivers However, the link to the latest drivers has been dead for at least two weeks, can someone please fix it or upload the latest version to Sourceforge? Is there any reason why the latest drivers wasn't uploaded to Sourceforge in the first place? -- Comment By: Jes Sorensen (jessorensen) Date: 2010-11-26 09:11 Message: Closing as fixed per Dor's posting on 2009-01-08 -- Comment By: Kenni (kelu6) Date: 2009-01-08 16:33 Message: Ahh, thank you...isn't it quite confusing to have both an old Windows driver as the latest Windows driver in SF and next to it a driver-iso, which apparently contains a newer version of the Windows driver??? I have always seen the iso as a collection of all the drivers, I would never expect the an driver-iso to contain newer versions of the individual drivers. If only the driver-iso will get updated in the future, you should really remove the old Windows driver to avoid confusing. -- Comment By: Dor Laor (thekozmo) Date: 2009-01-08 11:31 Message: The people.qumranet.com was blocked. I updated the new location for latest pv win drivers in the wiki. 10x -- You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=893831aid=2493498group_id=180599 -- To unsubscribe from this list: send the line unsubscribe kvm in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
[ kvm-Bugs-2494730 ] Guests stalling on kvm-82 / Linux 2.6.28
Bugs item #2494730, was opened at 2009-01-09 00:29 Message generated for change (Comment added) made by jessorensen You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=893831aid=2494730group_id=180599 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Kevin Shanahan (kmshanah) Assigned to: Nobody/Anonymous (nobody) Summary: Guests stalling on kvm-82 / Linux 2.6.28 Initial Comment: I am seeing periodic stalls in Linux and Windows guests with kvm-82 on an IBM X3550 server with 2 x Xeon 5130 CPUs and 32GB RAM. I am *reasonably* certain that this is a regression somewhere between kvm-72 and kvm-82. We had been running kvm-72 (actually, the debian kvm-source package) up until now and never noticed the problem. Now the stalls are very obvious. When the guest stalls, the at least one kvm process on the host gobbles up 100% CPU. I'll do my debugging with the Linux guest, as that's sure to be easier to deal with. As a simple demostration that the guest is unresponsive, here is the result of me pinging the guest from another machine on the (very quiet) LAN: --- hermes-old.wumi.org.au ping statistics --- 600 packets transmitted, 600 received, 0% packet loss, time 599659ms rtt min/avg/max/mdev = 0.255/181.211/6291.871/558.706 ms, pipe 7 The latency varies pretty badly, with spikes up to several seconds as you can see. The problem is not reproducable on other VT capable hardware that I have - e.g. my desktop has a E8400 CPU which runs the VMs just fine. Does knowing that make it any easier to guess where the problem might be? The Xeon 5130 does not have the smx, est, sse4_1, xsave, vnmi and flexpriority CPU flags that the E8400 does. Because this server is the only hardware I have which exhibits the problem and it's a production machine, I have limited times where I can do testing. However, I will try confirm that kvm-72 is okay and then bisect. Currently the host is running a 2.6.28 kernel with the kvm-82 modules. I guess I'm likely to have problems compiling the older kvm releases against this kernel, so I'll have to drop back to 2.6.27.something to run the tests. CPU Vendor: Intel CPU Type: Xeon 5130 Number of CPUs: 2 Host distribution: Debain Lenny/Sid KVM version: kvm-82 Host kernel: Linux 2.6.28 x86_64 Guest Distribution: Debian Etch Guest kernel: Linux 2.6.27.10 i686 Host's /proc/cpuinfo: processor : 0 vendor_id : GenuineIntel cpu family : 6 model : 15 model name : Intel(R) Xeon(R) CPU5130 @ 2.00GHz stepping: 6 cpu MHz : 1995.117 cache size : 4096 KB physical id : 0 siblings: 2 core id : 0 cpu cores : 2 apicid : 0 initial apicid : 0 fpu : yes fpu_exception : yes cpuid level : 10 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx lm constant_tsc arch_perfmon pebs bts rep_good pni dtes64 monitor ds_cpl vmx tm2 ssse3 cx16 xtpr pdcm dca lahf_lm tpr_shadow bogomips: 3990.23 clflush size: 64 cache_alignment : 64 address sizes : 36 bits physical, 48 bits virtual power management: processor : 1 vendor_id : GenuineIntel cpu family : 6 model : 15 model name : Intel(R) Xeon(R) CPU5130 @ 2.00GHz stepping: 6 cpu MHz : 1995.117 cache size : 4096 KB physical id : 0 siblings: 2 core id : 1 cpu cores : 2 apicid : 1 initial apicid : 1 fpu : yes fpu_exception : yes cpuid level : 10 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx lm constant_tsc arch_perfmon pebs bts rep_good pni dtes64 monitor ds_cpl vmx tm2 ssse3 cx16 xtpr pdcm dca lahf_lm tpr_shadow bogomips: 3989.96 clflush size: 64 cache_alignment : 64 address sizes : 36 bits physical, 48 bits virtual power management: processor : 2 vendor_id : GenuineIntel cpu family : 6 model : 15 model name : Intel(R) Xeon(R) CPU5130 @ 2.00GHz stepping: 6 cpu MHz : 1995.117 cache size : 4096 KB physical id : 3 siblings: 2 core id : 0 cpu cores : 2 apicid : 6 initial apicid : 6 fpu : yes fpu_exception : yes cpuid level : 10 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx lm constant_tsc arch_perfmon pebs bts rep_good pni dtes64 monitor ds_cpl vmx tm2 ssse3 cx16 xtpr pdcm dca lahf_lm
[ kvm-Bugs-2681442 ] Task Switch causes reboot
Bugs item #2681442, was opened at 2009-03-11 06:08 Message generated for change (Comment added) made by jessorensen You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=893831aid=2681442group_id=180599 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Closed Resolution: Fixed Priority: 5 Private: No Submitted By: Julian Stecklina (bliitz) Assigned to: Nobody/Anonymous (nobody) Summary: Task Switch causes reboot Initial Comment: I have a small test kernel that measures some x86 task switching stuff. KVM reboots the virtual machine when my test kernel tries to do a hardware task switch by CALLing a TSS descriptor in the GDT. I have attached an ISO which boots my test kernel. I can provide the source of this, if it's helpful. Output using: kvm -serial stdio -cdrom losysbench.iso losysbench [lots of debugging output] Calling TASK0_2 directly... [VM reboots] Output using kvm -no-kvm -serial stdio -cdrom losysbench.iso: losysbench [lots of debugging output] Calling TASK0_2 directly... 90730 [more stuff, i.e. everything went fine] My system info: Gentoo Linux Intel Core Duo L2400 KVM 84 Vanilla Linux 2.6.29-rc7 i386 -- Comment By: Jes Sorensen (jessorensen) Date: 2010-11-26 09:18 Message: Hi, Your test case runs to completion without problems here using a recent upstream KVM, so closing. If it happens again, please feel free to open a new bug over at Launchpad. Cheers, Jes -- Comment By: Julian Stecklina (bliitz) Date: 2009-03-16 21:29 Message: The patch from the mailing list does indeed fix this. The test case reports: jul...@tabernacle kvm-userspace % ./user/kvmctl user/test/x86/bootstrap user/test/x86/taskswitch.flat GUEST: task switching GUEST: Calling task (ring0) GUEST: Calling task (ring0) via gate GUEST: Calling task (ring3) GUEST: Done -- Comment By: Jan Kiszka (kiszka) Date: 2009-03-16 08:56 Message: Nice, with complete test case! But at least I'm too la^busy to try: Could you check if Bernhard Kohl's patch changes the picture for you? See http://permalink.gmane.org/gmane.comp.emulators.kvm.devel/29288 -- Comment By: Julian Stecklina (bliitz) Date: 2009-03-16 02:08 Message: File Added: taskswitch-test.patch -- Comment By: Avi Kivity (avik) Date: 2009-03-15 13:58 Message: A minimal test case (that can be added to kvm-xx/users/test/...) would be very useful. -- You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=893831aid=2681442group_id=180599 -- To unsubscribe from this list: send the line unsubscribe kvm in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
[ kvm-Bugs-2653899 ] seg fault with two nics
Bugs item #2653899, was opened at 2009-03-02 09:09 Message generated for change (Comment added) made by jessorensen You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=893831aid=2653899group_id=180599 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: amd Group: None Status: Closed Resolution: Works For Me Priority: 5 Private: No Submitted By: Oliver Kowalke (oliver_kowalke) Assigned to: Nobody/Anonymous (nobody) Summary: seg fault with two nics Initial Comment: starting an iso image with two nics results in a segfault - with one nic all is ok. kvm -cdrom tes.iso -net nic,macaddr=52:54:00:00:01:01 -net user -net nic,macaddr=52:54:00:00:00:02 -net user *** glibc detected *** /opt/kvm/bin/kvm: corrupted double-linked list: 0x08d04698 *** === Backtrace: = /lib/i686/cmov/libc.so.6[0xb7e1e14f] /lib/i686/cmov/libc.so.6[0xb7e1fb6d] /lib/i686/cmov/libc.so.6(__libc_malloc+0x95)[0xb7e21655] /opt/kvm/bin/kvm[0x80b7e31] /opt/kvm/bin/kvm[0x80b7f07] /opt/kvm/bin/kvm[0x80b9c17] /opt/kvm/bin/kvm[0x80505f7] /opt/kvm/bin/kvm[0x805186c] /lib/i686/cmov/libc.so.6(__libc_start_main+0xe5)[0xb7dc5455] /opt/kvm/bin/kvm[0x804c391] === Memory map: 08048000-081f3000 r-xp fe:02 1504441/opt/kvm/bin/qemu-system-x86_64 081f3000-081f6000 rw-p 001ab000 fe:02 1504441/opt/kvm/bin/qemu-system-x86_64 081f6000-08408000 rw-p 081f6000 00:00 0 08d04000-08d25000 rw-p 08d04000 00:00 0 [heap] ae60-ae621000 rw-p ae60 00:00 0 ae621000-ae70 ---p ae621000 00:00 0 ae7e-ae7ec000 r-xp fe:00 65068 /lib/libgcc_s.so.1 ae7ec000-ae7ed000 rw-p b000 fe:00 65068 /lib/libgcc_s.so.1 ae7ed000-b7bf2000 rw-p ae7ed000 00:00 0 b7bf2000-b7bfc000 r-xp fe:00 74266 /lib/i686/cmov/libnss_files-2.7.so b7bfc000-b7bfe000 rw-p 9000 fe:00 74266 /lib/i686/cmov/libnss_files-2.7.so b7bfe000-b7c0 rw-p b7bfe000 00:00 0 b7c0-b7c02000 r-xp fe:00 66786 /lib/libx86.so.1 b7c02000-b7c03000 rw-p 1000 fe:00 66786 /lib/libx86.so.1 b7c03000-b7c54000 r-xp fe:01 3452466/usr/lib/libvga.so.1.4.3 b7c54000-b7c5b000 rw-p 0005 fe:01 3452466/usr/lib/libvga.so.1.4.3 b7c5b000-b7c65000 rw-p b7c5b000 00:00 0 b7c65000-b7c78000 r-xp fe:01 3452157/usr/lib/libdirect-1.0.so.0.1.0 b7c78000-b7c79000 rw-p 00012000 fe:01 3452157/usr/lib/libdirect-1.0.so.0.1.0 b7c79000-b7c8 r-xp fe:01 3452159/usr/lib/libfusion-1.0.so.0.1.0 b7c8-b7c81000 rw-p 6000 fe:01 3452159/usr/lib/libfusion-1.0.so.0.1.0 b7c81000-b7ce6000 r-xp fe:01 3452158 /usr/lib/libdirectfb-1.0.so.0.1.0 b7ce6000-b7ce8000 rw-p 00065000 fe:01 3452158 /usr/lib/libdirectfb-1.0.so.0.1.0 b7ce8000-b7cea000 r-xp fe:00 74260 /lib/i686/cmov/libdl-2.7.so b7cea000-b7cec000 rw-p 1000 fe:00 74260 /lib/i686/cmov/libdl-2.7.so b7cec000-b7da9000 r-xp fe:01 3451739/usr/lib/libasound.so.2.0.0 b7da9000-b7dae000 rw-p 000bc000 fe:01 3451739/usr/lib/libasound.so.2.0.0 b7dae000-b7daf000 rw-p b7dae000 00:00 0 b7daf000-b7f04000 r-xp fe:00 74257 /lib/i686/cmov/libc-2.7.so b7f04000-b7f05000 r--p 00155000 fe:00 74257 /lib/i686/cmov/libc-2.7.so b7f05000-b7f07000 rw-p 00156000 fe:00 74257 /lib/i686/cmov/libc-2.7.so b7f07000-b7f0a000 rw-p b7f07000 00:00 0 b7f0a000-b7f39000 r-xp fe:00 65211 /lib/libncurses.so.5.7 b7f39000-b7f3c000 rw-p 0002f000 fe:00 65211 /lib/libncurses.so.5.7 b7f3c000-b7fa3000 r-xp fe:01 3452470/usr/lib/libSDL-1.2.so.0.11.1 b7fa3000-b7fa5000 rw-p 00067000 fe:01 3452470/usr/lib/libSDL-1.2.so.0.11.1 b7fa5000-b7fed000 rw-p b7fa5000 00:00 0 b7fed000-b7fef000 r-xp fe:00 74276 /lib/i686/cmov/libutil-2.7.so b7fef000-b7ff1000 rw-p 1000 fe:00 74276 /lib/i686/cmov/libutil-2.7.so b7ff1000-b7ff8000 r-xp fe:00 74273 /lib/i686/cmov/librt-2.7.so b7ff8000-b7ffa000 rw-p 6000 fe:00 74273 /lib/i686/cmov/librt-2.7.so b7ffa000-b800f000 r-xp fe:00 74271 /lib/i686/cmov/libpthread-2.7.so b800f000-b8011000 rw-p 00014000 fe:00 74271 /lib/i686/cmov/libpthread-2.7.so b8011000-b8014000 rw-p b8011000 00:00 0 b8014000-b8028000 r-xp fe:01 3450290/usr/lib/libz.so.1.2.3.3 b8028000-b8029000 rw-p 00013000 fe:01 3450290/usr/lib/libz.so.1.2.3.3 b8029000-b804d000 r-xp fe:00 74261 /lib/i686/cmov/libm-2.7.so b804d000-b804f000 rw-p 00023000 fe:00 74261 /lib/i686/cmov/libm-2.7.so b8062000-b8064000 rw-p b8062000 00:00 0 b8064000-b8065000 r-xp b8064000 00:00 0 [vdso] b8065000-b807f000 r-xp fe:00 65026 /lib/ld-2.7.so b807f000-b8081000 rw-p 0001a000 fe:00 65026 /Abgebrochen kernel 2.8.28.5 with kvm-84 cat /proc/cpuinfo processor : 0 vendor_id : AuthenticAMD cpu family : 15 model : 107
[ kvm-Bugs-2584662 ] No easy way to check kvm version
Bugs item #2584662, was opened at 2009-02-10 11:56 Message generated for change (Settings changed) made by jessorensen You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=893831aid=2584662group_id=180599 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Closed Resolution: Invalid Priority: 5 Private: No Submitted By: Guido Trotter (ultrotter) Assigned to: Nobody/Anonymous (nobody) Summary: No easy way to check kvm version Initial Comment: It would be nice if kvm reported its version with something like kvm --version Also it would be nice to be able to check for the in-kernel version, and its capabilities... :) Thanks, Guido -- Comment By: Jes Sorensen (jessorensen) Date: 2010-11-26 09:23 Message: [...@red-feather ~]$ qemu-kvm -version QEMU emulator version 0.13.0 (qemu-kvm-0.13.0), Copyright (c) 2003-2008 Fabrice Bellard For the kernel version of KVM there really isn't such a thing as a fixed version as the kernel is updated incrementally. Jes -- Comment By: Technologov (technologov) Date: 2009-02-11 11:25 Message: You can: KVM kernelspace: cat /sys/module/kvm/version KVM userspace: qemu | head -1 -- You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=893831aid=2584662group_id=180599 -- To unsubscribe from this list: send the line unsubscribe kvm in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
[ kvm-Bugs-2584543 ] Migration failed on kvm 83 (regression from 79)
Bugs item #2584543, was opened at 2009-02-10 11:16 Message generated for change (Comment added) made by jessorensen You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=893831aid=2584543group_id=180599 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Guido Trotter (ultrotter) Assigned to: Nobody/Anonymous (nobody) Summary: Migration failed on kvm 83 (regression from 79) Initial Comment: Hi, I'm running kvm on a Dual-Core AMD Opteron(tm) Processor and I'm having problems with live migration, since moving to version 83. Everything works fine on version 79. Basically I'm trying to do a live migration while a process is pinging, and the vm dies with a kernel dump, while on kvm 79 everything continued to run. The vm has a default debian lenny installed in it (with the 2.6.26 lenny kernel and everything) while the host is running a custom 2.6.27 kernel. Kvm is started (by ganeti 2.0, whose support for kvm I'm developing) with the following options: /usr/bin/kvm -m 128 -smp 1 -pidfile /var/run/ganeti/kvm-hypervisor/pid/instance -name instance -daemonize -boot c -drive file=/var/run/ganeti/instance-disks/instance:0,format=raw,if=virtio,boot=on -drive file=/usr/src/debian-Lenny-DI-rc2-amd64-netinst.iso,format=raw,media=cdrom,if=virtio -vnc :5364 -monitor unix:/var/run/ganeti/kvm-hypervisor/ctrl/instance.monitor,server,nowait -serial none -net nic,macaddr=MAC,model=virtio -net tap,script=/tmp/tmpQQ5yTE -incoming tcp:IP:8102 (the tap script is autogenerated by ganeti and connects the interface to the correct bridge) I suspect it might be something introduced in the patch to make networking on live migration more smooth... Thanks, Guido -- Comment By: Jes Sorensen (jessorensen) Date: 2010-11-26 09:24 Message: Hi, Is this still a problem? There has been a lot of fixes to the migration code since you reported this bug. Sorry that you didn't see any answers earlier. Regards, Jes -- You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=893831aid=2584543group_id=180599 -- To unsubscribe from this list: send the line unsubscribe kvm in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
[ kvm-Bugs-2530907 ] kvm-83 does not build with 2.6.28 with DMAR enabled
Bugs item #2530907, was opened at 2009-01-23 12:30 Message generated for change (Settings changed) made by jessorensen You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=893831aid=2530907group_id=180599 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: kernel Group: None Status: Closed Resolution: Out of Date Priority: 5 Private: No Submitted By: Joerg Roedel (jroedel) Assigned to: Nobody/Anonymous (nobody) Summary: kvm-83 does not build with 2.6.28 with DMAR enabled Initial Comment: Building KVM-83 fails to build the shipped kernel modules when building against a 2.6.28 Linux kernel which has DMAR enabled. Error is: make[3]: *** No rule to make target `/root/kvm-83/kernel/x86/vtd.o', needed by `/root/kvm-83/kernel/x86/kvm.o'. Stop. make[2]: *** [/root/kvm-83/kernel/x86] Error 2 make[1]: *** [_module_/root/kvm-83/kernel] Error 2 -- Comment By: Jes Sorensen (jessorensen) Date: 2010-11-26 09:26 Message: Ok this is pretty out of date by now, so closing. Regards, Jes -- Comment By: Mishehu Mashehu (mishehu) Date: 2009-01-24 01:30 Message: This is a known issue, and as I am not a developer on the project, I do not know if one day DMAR will be supported. But at this time, simply disable DMAR and everything should be fine. I spent a good 8 hours banging my head over this issue until I just happened to put in the right google search... -- You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=893831aid=2530907group_id=180599 -- To unsubscribe from this list: send the line unsubscribe kvm in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
[ kvm-Bugs-2525768 ] kvm image corruption
Bugs item #2525768, was opened at 2009-01-21 08:03 Message generated for change (Comment added) made by jessorensen You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=893831aid=2525768group_id=180599 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open Resolution: None Priority: 8 Private: No Submitted By: Daniel van Vugt (danv) Assigned to: Nobody/Anonymous (nobody) Summary: kvm image corruption Initial Comment: Creating a new bug from my original problems detailed in bug 2490866, because that technically is a different problem. Reproduced with kvm-83 and kvm-82 vanilla. Host: Ubuntu 8.04 amd64, Intel Q6600 Guests: Windows 2003 Server, Windows 7 beta at least. After shutting down the guest cleanly, it's image file is (often but not always) corrupt and unbootable. A fact confirmed by the change in information reported by qemu-img info Example 1 (qcow2 image): $ qemu-img info windows7beta.qcow2 image: windows7beta.qcow2 file format: qcow2 virtual size: 20G (21474836480 bytes) disk size: 5.0G cluster_size: 4096 Snapshot list: ID TAG VM SIZE DATE VM CLOCK 1 Fresh_install 1.3M 2009-01-09 15:34:31 00:00:00.000 2 Activated_kvm-82 1.3M 2009-01-09 15:43:27 00:00:00.000 $ qemu -m 512 -usbdevice tablet -redir tcp:3389::3389 windows7beta.qcow2 (use and then shut down windows) $ qemu-img info windows7beta.qcow2 image: windows7beta.qcow2 file format: raw INVALID virtual size: 5.0G (5353566208 bytes) - INVALID disk size: 5.0G $ qemu -m 512 -usbdevice tablet -redir tcp:3389::3389 windows7beta.qcow2 -S (qemu) info snapshots Snapshot devices: ide0-hd0 bdrv_snapshot_list: error -95 (And the image won't boot) Example 2 (raw image converted from Example 1): $ qemu-img info windows7beta.raw image: windows7beta.raw file format: raw virtual size: 20G (21474836480 bytes) disk size: 4.7G (Install and test lots on the guest) $ qemu-img info windows7beta.raw image: windows7beta.raw file format: raw virtual size: 7.5G (8049315840 bytes) - INVALID disk size: 7.5G (And now the image won't boot) -- Comment By: Jes Sorensen (jessorensen) Date: 2010-11-26 09:28 Message: Hi, There has been a lot of fixes to the qcow2 code since your bug report - are you still able to reproduce it, or can we close the bug? Thanks, Jes -- Comment By: Daniel van Vugt (danv) Date: 2009-05-06 10:14 Message: Sad to say... I have reproduced the bug on kvm-85, qemu-0.10.0, qemu-0.10.2 and qemu-0.10.3. They all still corrupt some qcow2 images. -- Comment By: Daniel van Vugt (danv) Date: 2009-02-16 03:16 Message: Confirmed the bug is still present in kvm-84. Just booting up my guest, opening the browser and then shutting down turns the qcow2 image into a corrupt unbootable raw image file. -- You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=893831aid=2525768group_id=180599 -- To unsubscribe from this list: send the line unsubscribe kvm in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
[ kvm-Bugs-2504388 ] Syslog on Ubuntu 8.10 (amd64) guest filled up with messages
Bugs item #2504388, was opened at 2009-01-13 13:01
Message generated for change (Comment added) made by jessorensen
You can respond by visiting:
https://sourceforge.net/tracker/?func=detailatid=893831aid=2504388group_id=180599
Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
Group: None
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: martinmaurer (martinmaurer)
Assigned to: Nobody/Anonymous (nobody)
Summary: Syslog on Ubuntu 8.10 (amd64) guest filled up with messages
Initial Comment:
hi all,
I am testing several guests on KVM-82, all with qcow2 and IDE disks, one cpu,
no virtio involved.
On Debian based systems including Ubuntu I got a lot error messages in the
syslog and during boot (dmesg). The systems can installed and looks usable in a
first run but what are these messages (see attached)?
Windows and Centos guests seems not to trigger this, I only got it on several
Debian/Ubuntu 64-bit based systems.
My host: Debian Etch 64-bit, KVM-82
here is a part of the syslog of the guest: (running ubuntu 8.10 amd64, 2.6.27-9)
Jan 13 12:47:35 ubuntu-810-amd64 kernel: [ 4793.565214] ata2.00: exception
Emask 0x0 SAct 0x0 SErr 0x0 action 0x6
Jan 13 12:47:35 ubuntu-810-amd64 kernel: [ 4793.565219] ata2.00: cmd
a0/00:00:00:00:00/00:00:00:00:00/a0 tag 0
Jan 13 12:47:35 ubuntu-810-amd64 kernel: [ 4793.565219] cdb 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00
Jan 13 12:47:35 ubuntu-810-amd64 kernel: [ 4793.565220] res
01/60:00:00:00:00/00:00:00:00:00/a0 Emask 0x3 (HSM violation)
Jan 13 12:47:35 ubuntu-810-amd64 kernel: [ 4793.565223] ata2.00: status: { ERR }
Jan 13 12:47:35 ubuntu-810-amd64 kernel: [ 4793.565315] ata2: soft resetting
link
Jan 13 12:47:35 ubuntu-810-amd64 kernel: [ 4793.720988] ata2.00: configured for
MWDMA2
Jan 13 12:47:35 ubuntu-810-amd64 kernel: [ 4793.720995] ata2: EH complete
Jan 13 12:47:35 ubuntu-810-amd64 kernel: [ 4793.721214] ata2.00: exception
Emask 0x0 SAct 0x0 SErr 0x0 action 0x6
Jan 13 12:47:35 ubuntu-810-amd64 kernel: [ 4793.721219] ata2.00: cmd
a0/00:00:00:00:00/00:00:00:00:00/a0 tag 0
Jan 13 12:47:35 ubuntu-810-amd64 kernel: [ 4793.721220] cdb 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00
Jan 13 12:47:35 ubuntu-810-amd64 kernel: [ 4793.721221] res
01/60:00:00:00:00/00:00:00:00:00/a0 Emask 0x3 (HSM violation)
Jan 13 12:47:35 ubuntu-810-amd64 kernel: [ 4793.721223] ata2.00: status: { ERR }
Jan 13 12:47:35 ubuntu-810-amd64 kernel: [ 4793.721315] ata2: soft resetting
link
Jan 13 12:47:35 ubuntu-810-amd64 kernel: [ 4793.876984] ata2.00: configured for
MWDMA2
Jan 13 12:47:35 ubuntu-810-amd64 kernel: [ 4793.876993] ata2: EH complete
Jan 13 12:47:35 ubuntu-810-amd64 kernel: [ 4793.877223] ata2.00: exception
Emask 0x0 SAct 0x0 SErr 0x0 action 0x6
Jan 13 12:47:35 ubuntu-810-amd64 kernel: [ 4793.877228] ata2.00: cmd
a0/00:00:00:00:00/00:00:00:00:00/a0 tag 0
Jan 13 12:47:35 ubuntu-810-amd64 kernel: [ 4793.877229] cdb 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00
Jan 13 12:47:35 ubuntu-810-amd64 kernel: [ 4793.877230] res
01/60:00:00:00:00/00:00:00:00:00/a0 Emask 0x3 (HSM violation)
Jan 13 12:47:35 ubuntu-810-amd64 kernel: [ 4793.877232] ata2.00: status: { ERR }
Jan 13 12:47:35 ubuntu-810-amd64 kernel: [ 4793.877324] ata2: soft resetting
link
Jan 13 12:47:35 ubuntu-810-amd64 kernel: [ 4794.032985] ata2.00: configured for
MWDMA2
Jan 13 12:47:35 ubuntu-810-amd64 kernel: [ 4794.032992] ata2: EH complete
Jan 13 12:47:35 ubuntu-810-amd64 kernel: [ 4794.033211] ata2.00: exception
Emask 0x0 SAct 0x0 SErr 0x0 action 0x6
Jan 13 12:47:35 ubuntu-810-amd64 kernel: [ 4794.033216] ata2.00: cmd
a0/00:00:00:00:00/00:00:00:00:00/a0 tag 0
Jan 13 12:47:35 ubuntu-810-amd64 kernel: [ 4794.033217] cdb 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00
Jan 13 12:47:35 ubuntu-810-amd64 kernel: [ 4794.033218] res
01/60:00:00:00:00/00:00:00:00:00/a0 Emask 0x3 (HSM violation)
Jan 13 12:47:35 ubuntu-810-amd64 kernel: [ 4794.033220] ata2.00: status: { ERR }
Jan 13 12:47:35 ubuntu-810-amd64 kernel: [ 4794.033311] ata2: soft resetting
link
__
--
Comment By: Jes Sorensen (jessorensen)
Date: 2010-11-26 09:35
Message:
Looks like a bug in the IDE emulation code - are you still seeing this with
recent version of KVM/QEMU or can we close the bug?
Thanks,
Jes
--
Comment By: martinmaurer (martinmaurer)
Date: 2009-01-13 15:23
Message:
I did more tests. seemed that ONLY newer ubuntu kernels as guests suffer
from this, Debian standard Kernels are working well as guests. I tested
with 8.04 and 8.10.
--
You can respond by visiting:
https://sourceforge.net
[ kvm-Bugs-2493108 ] Win2k problems on some (not all) Intel hosts
Bugs item #2493108, was opened at 2009-01-08 03:23 Message generated for change (Comment added) made by jessorensen You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=893831aid=2493108group_id=180599 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: intel Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Kevin Shanahan (kmshanah) Assigned to: Nobody/Anonymous (nobody) Summary: Win2k problems on some (not all) Intel hosts Initial Comment: I have a Windows 2000 guest that I have been testing on an desktop machine (E8400 CPU) and that has been working well (apart from being affected by bug 2314737). When I moved (not a live migration, just shutdown, rsync and boot on the new server) the guest to our server, which is an IBM X3550 with two Xeon 5130 CPUs the guest has short freezes where the guest CPU usage spikes on both virtual CPUs and the guest becomes unresponsive for several seconds at a time. These guest CPU spikes can last over a minute, but the guest might have moments where it briefly responds to the delayed keystrokes, etc. every few seconds. One symptom of this behaviour for me last night was that Win2k AD replication was failing, so it's not just interactive use that suffers. Something I noticed that may be relevant - due to the other bug (2314737) which causes each guest CPU to use 100% of the host CPU, whether the guest CPU is idle or not, I can tell when the guest is having this problem by looking at the 'top' output on the host. When the guest is operating normally, the host will show the qemu-system-x86_64 process using 200% CPU (the guest is using -smp 2). However, when the guest is misbehaving, the host will show the qemu-system-x86_64 process only using _100%_ CPU. Maybe one of the threads is stuck, or something is forcing them to share a single core? Both hosts are running Debian Lenny/Sid, 64-bit with a kernel.org 2.6.28 kernel and kvm-82. The command line used in both cases: /usr/local/kvm/bin/qemu-system-x86_64 \ -smp 2 \ -localtime -m 2048 \ -drive if=ide,file=kvm-ks-02a.img,index=0,media=disk,boot=on \ -drive if=ide,file=kvm-ks-02b.img,index=2,media=disk \ -net nic,vlan=0,macaddr=52:54:00:12:34:68,model=virtio \ -net tap,vlan=0,ifname=tap18,script=no \ -vnc 127.0.0.1:18 -usbdevice tablet \ -daemonize CPUs on the good host: processor : 0 vendor_id : GenuineIntel cpu family : 6 model : 23 model name : Intel(R) Core(TM)2 Duo CPU E8400 @ 3.00GHz stepping: 10 cpu MHz : 3000.000 cache size : 6144 KB physical id : 0 siblings: 2 core id : 0 cpu cores : 2 apicid : 0 initial apicid : 0 fpu : yes fpu_exception : yes cpuid level : 13 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx lm constant_tsc arch_perfmon pebs bts rep_good pni dtes64 monitor ds_cpl vmx smx est tm2 ssse3 cx16 xtpr pdcm sse4_1 xsave lahf_lm tpr_shadow vnmi flexpriority bogomips: 5984.98 clflush size: 64 cache_alignment : 64 address sizes : 36 bits physical, 48 bits virtual power management: processor : 1 vendor_id : GenuineIntel cpu family : 6 model : 23 model name : Intel(R) Core(TM)2 Duo CPU E8400 @ 3.00GHz stepping: 10 cpu MHz : 3000.000 cache size : 6144 KB physical id : 0 siblings: 2 core id : 1 cpu cores : 2 apicid : 1 initial apicid : 1 fpu : yes fpu_exception : yes cpuid level : 13 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx lm constant_tsc arch_perfmon pebs bts rep_good pni dtes64 monitor ds_cpl vmx smx est tm2 ssse3 cx16 xtpr pdcm sse4_1 xsave lahf_lm tpr_shadow vnmi flexpriority bogomips: 5984.97 clflush size: 64 cache_alignment : 64 address sizes : 36 bits physical, 48 bits virtual power management: And the bad host: processor : 0 vendor_id : GenuineIntel cpu family : 6 model : 15 model name : Intel(R) Xeon(R) CPU5130 @ 2.00GHz stepping: 6 cpu MHz : 1995.117 cache size : 4096 KB physical id : 0 siblings: 2 core id : 0 cpu cores : 2 apicid : 0 initial apicid : 0 fpu : yes fpu_exception : yes cpuid level : 10 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx lm constant _tsc arch_perfmon pebs bts rep_good pni dtes64 monitor ds_cpl vmx tm2
[ kvm-Bugs-2504388 ] Syslog on Ubuntu 8.10 (amd64) guest filled up with messages
Bugs item #2504388, was opened at 2009-01-13 13:01
Message generated for change (Comment added) made by martinmaurer
You can respond by visiting:
https://sourceforge.net/tracker/?func=detailatid=893831aid=2504388group_id=180599
Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
Group: None
Status: Closed
Resolution: Fixed
Priority: 5
Private: No
Submitted By: martinmaurer (martinmaurer)
Assigned to: Nobody/Anonymous (nobody)
Summary: Syslog on Ubuntu 8.10 (amd64) guest filled up with messages
Initial Comment:
hi all,
I am testing several guests on KVM-82, all with qcow2 and IDE disks, one cpu,
no virtio involved.
On Debian based systems including Ubuntu I got a lot error messages in the
syslog and during boot (dmesg). The systems can installed and looks usable in a
first run but what are these messages (see attached)?
Windows and Centos guests seems not to trigger this, I only got it on several
Debian/Ubuntu 64-bit based systems.
My host: Debian Etch 64-bit, KVM-82
here is a part of the syslog of the guest: (running ubuntu 8.10 amd64, 2.6.27-9)
Jan 13 12:47:35 ubuntu-810-amd64 kernel: [ 4793.565214] ata2.00: exception
Emask 0x0 SAct 0x0 SErr 0x0 action 0x6
Jan 13 12:47:35 ubuntu-810-amd64 kernel: [ 4793.565219] ata2.00: cmd
a0/00:00:00:00:00/00:00:00:00:00/a0 tag 0
Jan 13 12:47:35 ubuntu-810-amd64 kernel: [ 4793.565219] cdb 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00
Jan 13 12:47:35 ubuntu-810-amd64 kernel: [ 4793.565220] res
01/60:00:00:00:00/00:00:00:00:00/a0 Emask 0x3 (HSM violation)
Jan 13 12:47:35 ubuntu-810-amd64 kernel: [ 4793.565223] ata2.00: status: { ERR }
Jan 13 12:47:35 ubuntu-810-amd64 kernel: [ 4793.565315] ata2: soft resetting
link
Jan 13 12:47:35 ubuntu-810-amd64 kernel: [ 4793.720988] ata2.00: configured for
MWDMA2
Jan 13 12:47:35 ubuntu-810-amd64 kernel: [ 4793.720995] ata2: EH complete
Jan 13 12:47:35 ubuntu-810-amd64 kernel: [ 4793.721214] ata2.00: exception
Emask 0x0 SAct 0x0 SErr 0x0 action 0x6
Jan 13 12:47:35 ubuntu-810-amd64 kernel: [ 4793.721219] ata2.00: cmd
a0/00:00:00:00:00/00:00:00:00:00/a0 tag 0
Jan 13 12:47:35 ubuntu-810-amd64 kernel: [ 4793.721220] cdb 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00
Jan 13 12:47:35 ubuntu-810-amd64 kernel: [ 4793.721221] res
01/60:00:00:00:00/00:00:00:00:00/a0 Emask 0x3 (HSM violation)
Jan 13 12:47:35 ubuntu-810-amd64 kernel: [ 4793.721223] ata2.00: status: { ERR }
Jan 13 12:47:35 ubuntu-810-amd64 kernel: [ 4793.721315] ata2: soft resetting
link
Jan 13 12:47:35 ubuntu-810-amd64 kernel: [ 4793.876984] ata2.00: configured for
MWDMA2
Jan 13 12:47:35 ubuntu-810-amd64 kernel: [ 4793.876993] ata2: EH complete
Jan 13 12:47:35 ubuntu-810-amd64 kernel: [ 4793.877223] ata2.00: exception
Emask 0x0 SAct 0x0 SErr 0x0 action 0x6
Jan 13 12:47:35 ubuntu-810-amd64 kernel: [ 4793.877228] ata2.00: cmd
a0/00:00:00:00:00/00:00:00:00:00/a0 tag 0
Jan 13 12:47:35 ubuntu-810-amd64 kernel: [ 4793.877229] cdb 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00
Jan 13 12:47:35 ubuntu-810-amd64 kernel: [ 4793.877230] res
01/60:00:00:00:00/00:00:00:00:00/a0 Emask 0x3 (HSM violation)
Jan 13 12:47:35 ubuntu-810-amd64 kernel: [ 4793.877232] ata2.00: status: { ERR }
Jan 13 12:47:35 ubuntu-810-amd64 kernel: [ 4793.877324] ata2: soft resetting
link
Jan 13 12:47:35 ubuntu-810-amd64 kernel: [ 4794.032985] ata2.00: configured for
MWDMA2
Jan 13 12:47:35 ubuntu-810-amd64 kernel: [ 4794.032992] ata2: EH complete
Jan 13 12:47:35 ubuntu-810-amd64 kernel: [ 4794.033211] ata2.00: exception
Emask 0x0 SAct 0x0 SErr 0x0 action 0x6
Jan 13 12:47:35 ubuntu-810-amd64 kernel: [ 4794.033216] ata2.00: cmd
a0/00:00:00:00:00/00:00:00:00:00/a0 tag 0
Jan 13 12:47:35 ubuntu-810-amd64 kernel: [ 4794.033217] cdb 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00
Jan 13 12:47:35 ubuntu-810-amd64 kernel: [ 4794.033218] res
01/60:00:00:00:00/00:00:00:00:00/a0 Emask 0x3 (HSM violation)
Jan 13 12:47:35 ubuntu-810-amd64 kernel: [ 4794.033220] ata2.00: status: { ERR }
Jan 13 12:47:35 ubuntu-810-amd64 kernel: [ 4794.033311] ata2: soft resetting
link
__
--
Comment By: martinmaurer (martinmaurer)
Date: 2010-11-26 09:40
Message:
fixed long time ago in newer versions, sorry for not reporting.
br, martin
--
Comment By: Jes Sorensen (jessorensen)
Date: 2010-11-26 09:35
Message:
Looks like a bug in the IDE emulation code - are you still seeing this with
recent version of KVM/QEMU or can we close the bug?
Thanks,
Jes
--
Comment By: martinmaurer (martinmaurer)
Date: 2009-01-13 15:23
Message:
I did more tests. seemed that ONLY newer ubuntu kernels as guests
[ kvm-Bugs-2432316 ] hotplug inexistent device will kill guest
Bugs item #2432316, was opened at 2008-12-16 03:44 Message generated for change (Comment added) made by jessorensen You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=893831aid=2432316group_id=180599 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Closed Resolution: Works For Me Priority: 5 Private: No Submitted By: Jiajun Xu (jiajun) Assigned to: Nobody/Anonymous (nobody) Summary: hotplug inexistent device will kill guest Initial Comment: Host OS (ia32/ia32e/IA64): ia32e Kernel Commit: KVM-77, 2.6.27-rc9, 4330ed8ed4da360ac1ca14b0fddff4c05b10de16 Userspace Commit: bebd13cd8eac7ac9cc3a1b2b3bbdc28a0b0efd9a Host Kernel Version: RHEL5u2 Bug detailed description: -- We create one guest, then do VT-d device hotplug, if we add a inexistent BDF number of device, guest will be killed. host print: get_real_device: /sys/bus/pci/devices/:00:30.0/config: No such file or directory init_assigned_device: Error: Couldn't get real device (00:30.0)! assigned_dev_pci_read_config: pread failed, ret = -1 errno = 29 Reproduce steps: 1) install kvm and create one guest 2) enter guest qemu monitor(print Ctrl+Alt+2) 3) run command pci_add 0 host host=00:30.0, 00:30.0 is a inexistent bdf number 4) guest will be killed -- Comment By: Jes Sorensen (jessorensen) Date: 2010-11-26 10:04 Message: Hi, Tested with upstream qemu/kvm - when trying to add a non existing device I get an error message, but no crash. If you still see this problem with a recent version of KVM please file a new bug in launhpad. If you have issues with the current RHEL5 host, please file a bug in Red Hat's bugzilla. Thanks, Jes -- You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=893831aid=2432316group_id=180599 -- To unsubscribe from this list: send the line unsubscribe kvm in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
[ kvm-Bugs-2418470 ] libvirt save/restore broken after upgrading to kvm-80
Bugs item #2418470, was opened at 2008-12-11 22:44 Message generated for change (Comment added) made by jessorensen You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=893831aid=2418470group_id=180599 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: qemu Group: None Status: Closed Resolution: Invalid Priority: 5 Private: No Submitted By: Tuomas Jormola (tjormola) Assigned to: Nobody/Anonymous (nobody) Summary: libvirt save/restore broken after upgrading to kvm-80 Initial Comment: Hi, I'm running Ubuntu 8.10 on i386 (Intel Core2 Quad Q6600). virsh commands save and restore work just fine with the default kvm-72 based setup. I upgraded to kvm-80 by backporting the kvm-79 package from jaunty development tree with kvm-80 upstream source applied on top. Everything else seems to work ok for me except that now libvirt based restore stopped working. Save produces dump of the vm memory, but when running restore, the machine just boots, it does not resume the state. The save/restore also works if running kvm-72 users pace and kvm-80 kernel modules. Maybe there's something wrong with the migration code in kvm-80 user space, afaik libvirt uses that to implement save/restore. Tuomas Jormola -- Comment By: Jes Sorensen (jessorensen) Date: 2010-11-26 11:06 Message: If you do an upgrade you need to upgrade libvirt to match. -- You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=893831aid=2418470group_id=180599 -- To unsubscribe from this list: send the line unsubscribe kvm in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
[ kvm-Bugs-2417350 ] external module trace support kvm-80
Bugs item #2417350, was opened at 2008-12-11 16:05 Message generated for change (Comment added) made by jessorensen You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=893831aid=2417350group_id=180599 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Closed Resolution: Out of Date Priority: 5 Private: No Submitted By: Henning Schild (hensch) Assigned to: Nobody/Anonymous (nobody) Summary: external module trace support kvm-80 Initial Comment: kvm-80 calls marker_synchronize_unregister(); in kvm_trace. This call was introduced in 2.6.28 and thus can not be used in versions before that. Surrounding the call with #if LINUX_VERSION_CODE KERNEL_VERSION(2,6,27) seems to fix that. -- Comment By: Jes Sorensen (jessorensen) Date: 2010-11-26 11:13 Message: kvm-80 is out of date. Closing Jes -- You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=893831aid=2417350group_id=180599 -- To unsubscribe from this list: send the line unsubscribe kvm in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
[ kvm-Bugs-2804283 ] bug when using virtualbox and kvm
Bugs item #2804283, was opened at 2009-06-10 18:52 Message generated for change (Comment added) made by jessorensen You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=893831aid=2804283group_id=180599 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: kernel Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Leandro Costantino (obeliscolabs) Assigned to: Nobody/Anonymous (nobody) Summary: bug when using virtualbox and kvm Initial Comment: kvm module version: v2.6.30-rc8-84-gf555fb2 QEMU PC emulator version 0.9.1 (kvm-72), Copyright (c) 2003-2008 Fabrice Bellard CPU: AMD Turion(tm) 64 X2 Mobile Technology TL-58 Host: Debian (sid), 32 bits Guest: moblin developer image (linux, 32 bits ) Having kvm kvm_amd loaded, and later loading vboxdrv, running a machine inside Virtualbox, closed it and tried to run another machine but on kvm using virt-manager i got this: 72646.987931] kvm: guest NX capability removed [72647.211827] kvm: guest NX capability removed [72647.212598] [ cut here ] [72647.212602] kernel BUG at arch/x86/kvm/../../../virt/kvm/kvm_main.c:2108! [72647.212606] invalid opcode: [#1] SMP [72647.212610] last sysfs file: /sys/class/net/lo/operstate [72647.212613] Modules linked in: vboxnetflt vboxdrv xt_state ipt_MASQUERADE iptable_nat nf_nat nf_conntrack_ipv4 nf_conntrack nf_defrag_ipv4 ipt_REJECT xt_tcpudp iptable_filter ip_tables x_tables bridge stp llc tun radeon drm i2c_core rfkill_input kvm_amd kvm loop snd_hda_codec_realtek snd_hda_intel snd_hda_codec arc4 ecb cryptomgr aead pcompress crypto_blkcipher snd_hwdep crypto_hash snd_pcm_oss crypto_algapi snd_pcm b43 snd_mixer_oss snd_seq_oss snd_seq_midi_event snd_seq snd_timer snd_seq_device snd uvcvideo mac80211 soundcore cfg80211 nsc_ircc snd_page_alloc videodev v4l1_compat serio_raw pcspkr input_polldev yenta_socket rsrc_nonstatic irda crc_ccitt battery ac shpchp pci_hotplug rtc_cmos rtc_core rtc_lib video button processor acer_wmi rfkill led_class wmi dm_mirror dm_region_hash dm_log dm_snapshot ahci thermal fan pata_atiixp libata atiixp ext3 jbd reiserfs [last unloaded: vboxdrv] [72647.212690] [72647.212695] Pid: 19018, comm: kvm Not tainted (2.6.30-rc8-obelisco-generic #25) Extensa 5420 [72647.212699] EIP: 0060:[fa8d8341] EFLAGS: 00210046 CPU: 0 [72647.212718] EIP is at kvm_handle_fault_on_reboot+0x19/0x1d [kvm] [72647.212721] EAX: EBX: f7086160 ECX: 9629646d EDX: [72647.212725] ESI: f5f5 EDI: EBP: f5f5 ESP: c4495e40 [72647.212728] DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068 [72647.212732] Process kvm (pid: 19018, ti=c4494000 task=f5faa940 task.ti=c4494000) [72647.212735] Stack: [72647.212737] 9629646d fa93e32c 00d8 00e0 9629646d ae80 f5f5 [72647.212744] f5f50034 fa8e0d77 f5f5 f562457c c1f99000 f5f50690 f5f50890 f5f51220 [72647.212751] f5f51228 9629646d fa8e01f4 7ffbfeff fffe 9629646d ae80 f5cbb700 [72647.212759] Call Trace: [72647.212762] [fa93e32c] ? svm_vcpu_run+0x17a/0x29f [kvm_amd] [72647.212772] [fa8e0d77] ? kvm_arch_vcpu_ioctl_run+0x572/0x885 [kvm] [72647.212790] [fa8e01f4] ? kvm_arch_vcpu_ioctl_get_sregs+0x20f/0x22b [kvm] [72647.212808] [fa8d86a2] ? kvm_vcpu_ioctl+0xf0/0x574 [kvm] [72647.212823] [c014b489] ? do_futex+0xbb/0x78c [72647.212831] [fa8d85b2] ? kvm_vcpu_ioctl+0x0/0x574 [kvm] [72647.212846] [c019eeb2] ? vfs_ioctl+0x2a/0x7f [72647.212852] [c019f37a] ? do_vfs_ioctl+0x473/0x4c1 [72647.212857] [c014bc79] ? sys_futex+0x11f/0x147 [72647.212862] [c019f40d] ? sys_ioctl+0x45/0x72 [72647.212867] [c0102d0f] ? sysenter_do_call+0x12/0x26 [72647.212872] Code: 14 24 65 33 15 14 00 00 00 74 05 e8 1b 0f 85 c5 59 c3 83 ec 04 65 a1 14 00 00 00 89 04 24 31 c0 80 3d f4 b1 8f fa 00 74 02 eb fe 0f 0b eb fe 57 b9 07 00 00 00 83 ec 04 89 c7 65 a1 14 00 00 00 [72647.212909] EIP: [fa8d8341] kvm_handle_fault_on_reboot+0x19/0x1d [kvm] SS:ESP 0068:c4495e40 [72647.212926] ---[ end trace a16b443ec925cf9c ]--- (vboxdrv version: 2.2.4_OSE) Dont know if its a well known bug. Best Regards Costantino Leandro lcostant...@gmai.com -- Comment By: Jes Sorensen (jessorensen) Date: 2010-11-26 11:15 Message: Hi, Do you still see this problem with recent KVM? Jes -- You can respond by visiting: https://sourceforge.net/tracker/?func
[ kvm-Bugs-2803811 ] Intel Pro/1000 PT unable to get IP under Windows 7 guest.
Bugs item #2803811, was opened at 2009-06-10 00:03 Message generated for change (Comment added) made by jessorensen You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=893831aid=2803811group_id=180599 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: intel Group: None Status: Closed Resolution: Invalid Priority: 5 Private: No Submitted By: Scott Parker (scottparker) Assigned to: Nobody/Anonymous (nobody) Summary: Intel Pro/1000 PT unable to get IP under Windows 7 guest. Initial Comment: CPU: Intel 64bit (VT-x support ENABLED) Kernel: 2.6.29.4 KVM: 86 Host OS: Fedora Core 10 64bit Guest OS: Windows 7 Build 7100 RC 32bit Device: Intel Pro/1000 PT PCIe NIC. Control of device has been migrated to guest OS via PCI Passthru (Intel VT-d). Device is seen by OS and native OS drivers have been loaded. NIC never receives an IP address from DHCP Server. This issue is not seen when running a Windows XP 32bit Guest OS or when running Xen Unstable and the same build of Windows 7 using the same driver version. -- Comment By: Jes Sorensen (jessorensen) Date: 2010-11-26 11:18 Message: You are not providing any information about how you launch KVM, which version of QEMU or QEMU-KVM you are running etc. so closing as invalid. If still see this problem with recent KVM, please open a new bug over in launchpad. Thanks, Jes -- You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=893831aid=2803811group_id=180599 -- To unsubscribe from this list: send the line unsubscribe kvm in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
[ kvm-Bugs-2803638 ] kvm-86: winxp guest + kvmnet.sys virtio unstable
Bugs item #2803638, was opened at 2009-06-09 18:45 Message generated for change (Settings changed) made by jessorensen You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=893831aid=2803638group_id=180599 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Closed Resolution: Fixed Priority: 5 Private: No Submitted By: Geoffrey Brimhall (vinyvat) Assigned to: Nobody/Anonymous (nobody) Summary: kvm-86: winxp guest + kvmnet.sys virtio unstable Initial Comment: * cpu model: Core i7 920 * kvm version: kvm 86 * host kernel version: 2.6.29.4 debian lenny * host kernel arch: x86_64 * guest: winxp 32bit sp3 * qemu command line: qemu-system-x86_64 -boot c -hda ./winxp.qcow2 -cdrom winxp-sp3.iso -smp 2 -m 1024 -vga std -net nic,model=virtio,vlan=0,macaddr=00:15:60:51:09:BD -net tap,vlan=0,ifname=tap0,script=/etc/kvm/kvm-ifup -soundhw es1370 -localtime -k en-us -name -usb When using kvmnet.sys in guest winxp32, guest crashes ( blue-screen with IRQ_NOT_LESS_OR_EQUAL most common ) on complex web2.0 browser pages ( lots of ajax and form fields ). Switching back to default rtl8139 driver ( ie remove model=virtio from command line options ) gets system back to being very stable. Reproduced crash using all permutations of kvm-85 and 2.6.26 kernel also. -- Comment By: Jes Sorensen (jessorensen) Date: 2010-11-26 11:19 Message: You need virtio drivers more recent than 1.0.8 for this to work with a recent KVM. You can get updated drivers here: http://www.linux-kvm.com/content/latest-windows-virtio-drivers Closing Jes -- Comment By: Dor Laor (thekozmo) Date: 2009-06-15 14:43 Message: Once we'll get authorization to release new windows drivers it will get solved. -- Comment By: Geoffrey Brimhall (vinyvat) Date: 2009-06-09 19:32 Message: Also have 6GB ram on system. -- You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=893831aid=2803638group_id=180599 -- To unsubscribe from this list: send the line unsubscribe kvm in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
[ kvm-Bugs-2796640 ] KVM Regression from 2.6.28-11 to 2.6.30-rc5
Bugs item #2796640, was opened at 2009-05-26 03:00 Message generated for change (Comment added) made by jessorensen You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=893831aid=2796640group_id=180599 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Bob Manners (bobmanners) Assigned to: Nobody/Anonymous (nobody) Summary: KVM Regression from 2.6.28-11 to 2.6.30-rc5 Initial Comment: Changing from the Ubuntu 09.04 stock kernel 2.6.28-11 to the current 'alpha' kernel in the Ubuntu development repository for 'Karmic' 2.6.30-rc5, some (but not all) of my KVM guests stop booting. I have the following guest OSs installed as KVM virtual machines: Ubuntu 09.04, FreeBSD 7.1, Minix 3, OpenSolaris 08.11, Windows XP and Windows 7RC Under 2.6.28-11 these all boot and run OK. With kernel 2.6.30-rc5, Ubuntu, FreeBSD and Minix boot and run OK, but OpenSolaris 08.11, Windows XP and Windows 7RC fail to boot. They appear to freeze very early in the boot process, after the boot loader is done and the OS kernel itself starts loading. There are no strange messages in the host system logs that I am aware of. When the guest OS freezes, it pins one of my CPUs at 100% utilization (I have KVM set to only give one CPU to the guest). This looks like a regression under 2.6.30-rc5. It is possible that it is caused by a Ubuntu patch, and I have filed a bug in Launchpad, but I suspect that this is an upstream problem, and so I am reporting it here also. Please let me know what I can do to assist in debugging this. -- Comment By: Jes Sorensen (jessorensen) Date: 2010-11-26 11:36 Message: Hi, Has this issue been resolved for you? Thanks, Jes -- Comment By: Kenni (kelu6) Date: 2009-05-28 10:26 Message: Your CPU still has the NX flag, which apparently also was my issue: http://thread.gmane.org/gmane.comp.emulators.kvm.devel/31206/focus=31774 -- Comment By: Bob Manners (bobmanners) Date: 2009-05-28 02:22 Message: In response to kelu6's question, actually I am running 32 bit host / 32 bit guest. My CPU is Intel Core Duo (not Core2 Duo) which is a 32 bit CPU: b...@gecko2:~$ cat /proc/cpuinfo processor : 0 vendor_id : GenuineIntel cpu family : 6 model : 14 model name : Genuine Intel(R) CPU T2400 @ 1.83GHz stepping: 8 cpu MHz : 1000.000 cache size : 2048 KB physical id : 0 siblings: 2 core id : 0 cpu cores : 2 apicid : 0 initial apicid : 0 fdiv_bug: no hlt_bug : no f00f_bug: no coma_bug: no fpu : yes fpu_exception : yes cpuid level : 10 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe nx constant_tsc arch_perfmon bts pni monitor vmx est tm2 xtpr pdcm bogomips: 3658.94 clflush size: 64 power management: processor : 1 vendor_id : GenuineIntel cpu family : 6 model : 14 model name : Genuine Intel(R) CPU T2400 @ 1.83GHz stepping: 8 cpu MHz : 1000.000 cache size : 2048 KB physical id : 0 siblings: 2 core id : 1 cpu cores : 2 apicid : 1 initial apicid : 1 fdiv_bug: no hlt_bug : no f00f_bug: no coma_bug: no fpu : yes fpu_exception : yes cpuid level : 10 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat clflush dts acpi mmx
[ kvm-Bugs-2792656 ] System freeze after modprobe kvm-intel
Bugs item #2792656, was opened at 2009-05-16 14:32 Message generated for change (Comment added) made by jessorensen You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=893831aid=2792656group_id=180599 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: intel Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: zorn (uzorn) Assigned to: Nobody/Anonymous (nobody) Summary: System freeze after modprobe kvm-intel Initial Comment: Hi, I just enabled Intel-VT on my Toshiba Tecra A8 and get the following problem: If I try to load the module kvm-intel, the whole system freezes after a short time ( 1s). No errors, no logs... CPU: Intel(R) Core(TM)2 CPU KVM: kvm-85 Host distro: Ubuntu 9.04 (32-bit) Host kernel: 2.6.30-020630rc5-generic #020630rc5 (i686) Command line: modprobe kvm-intel # cat /proc/cpuinfo processor : 0 vendor_id : GenuineIntel cpu family : 6 model : 15 model name : Intel(R) Core(TM)2 CPU T7200 @ 2.00GHz stepping: 6 cpu MHz : 1000.000 cache size : 4096 KB physical id : 0 siblings: 2 core id : 0 cpu cores : 2 apicid : 0 initial apicid : 0 fdiv_bug: no hlt_bug : no f00f_bug: no coma_bug: no fpu : yes fpu_exception : yes cpuid level : 10 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe nx lm constant_tsc arch_perfmon pebs bts pni dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm lahf_lm tpr_shadow bogomips: 3990.45 clflush size: 64 power management: processor : 1 vendor_id : GenuineIntel cpu family : 6 model : 15 model name : Intel(R) Core(TM)2 CPU T7200 @ 2.00GHz stepping: 6 cpu MHz : 1000.000 cache size : 4096 KB physical id : 0 siblings: 2 core id : 1 cpu cores : 2 apicid : 1 initial apicid : 1 fdiv_bug: no hlt_bug : no f00f_bug: no coma_bug: no fpu : yes fpu_exception : yes cpuid level : 10 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe nx lm constant_tsc arch_perfmon pebs bts pni dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm lahf_lm tpr_shadow bogomips: 3990.04 clflush size: 64 power management: -- Comment By: Jes Sorensen (jessorensen) Date: 2010-11-26 11:39 Message: Do you still see the problem with recent KVM? Do you have anything in syslog indicating what went wrong? Thanks, Jes -- Comment By: zorn (uzorn) Date: 2009-05-21 16:34 Message: I updated to current Toshiba BIOS v1.40 today, it is still the same. -- Comment By: Avi Kivity (avik) Date: 2009-05-17 11:40 Message: Is your BIOS updated to the latest version provided by the vendor? -- You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=893831aid=2792656group_id=180599 -- To unsubscribe from this list: send the line unsubscribe kvm in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
[ kvm-Bugs-2791009 ] -vga vmware + X-windows: display errors, jumpy mouse, hangs
Bugs item #2791009, was opened at 2009-05-13 05:58 Message generated for change (Comment added) made by jessorensen You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=893831aid=2791009group_id=180599 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: intel Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Balzac von Jigglypuff (jiggly) Assigned to: Nobody/Anonymous (nobody) Summary: -vga vmware + X-windows: display errors, jumpy mouse, hangs Initial Comment: With -vga vmware, Xorg (in the guest) doesn't display properly. The display is vaguely legible, but it's scrambled. With -vga vmware -smp 2, I get the same display problem, plus the mouse jumps erratically and kvm hangs. CPU: Core 2 Duo P8600 KVM: kvm-85 (Gentoo ebuild kvm-85-r1, ncurses enabled, sdl enabled, all other USE flags disabled) Host kernel: 2.6.29 (linux-2.6.29-gentoo-r3) Host kernel arch: x86_64 Host distro: Gentoo AMD64 Guest kernel: 2.6.29 (linux-2.6.29-gentoo-r3), no virtio, no KVM_GUEST Guest kernel arch: x86_64 Guest distro: Gentoo AMD64 Command line: kvm -kernel vmlinuz -append root=/dev/hda -hda /dev/mapper/vg0-linroot -vga vmware Command line (alternate): kvm -smp 2 -kernel vmlinuz -append root=/dev/hda -hda /dev/mapper/vg0-linroot -vga vmware Here's a more detailed description of the problem: I'm trying to run Xorg on a Gentoo guest. With kvm -vga std and the vesa X driver, everything works fine, even with -smp 2. With kvm -vga vmware and the vmware X driver, though, the X display is scrambled. I can barely see some garbled twm xterm windows (see attached screenshot), and I can type in those xterms. I tried different resolutions and HorizSync/VertRefresh's, but it's always scrambled. If I use kvm -vga vmware -smp 2, the display is similarly scrambled, and additionally the mouse is unusable. If I move the mouse, the guest pointer starts jumping all over erratically. Sometimes the pointer settles down and stops (until I touch the mouse again), sometimes it keeps jumping around. Xorg usually outputs a bunch of [mi] EQ overflowing. The server is probably stuck in an infinite loop. errors while this is happening. If I keep moving the mouse, kvm eventually hangs: I can't ungrab the pointer from the kvm window, so I have to switch to VT1; top shows that kvm is using max CPU; kvm doesn't respond to SIGINT; and I have to kill -9 kvm. The amount of mouse waving it takes to hang kvm varies (~5s-120s), and it's only reproducible ~20% of the time. If the guest kernel has any paravirtualization, though, the hang happens much faster and is 100% reproducible. -- Comment By: Jes Sorensen (jessorensen) Date: 2010-11-26 11:40 Message: Sounds like a problem with the vmware vga emulation in QEMU. Do you still see these problems with recent versions of KVM/QEMU? Thanks, Jes -- Comment By: Balzac von Jigglypuff (jiggly) Date: 2009-05-13 06:47 Message: -no-kvm-pit doesn't change anything. With -no-kvm or -no-kvm-irqchip, the display is still garbled, but I don't get mouse jitters and hangs with -smp 2. -- You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=893831aid=2791009group_id=180599 -- To unsubscribe from this list: send the line unsubscribe kvm in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
[ kvm-Bugs-2894352 ] Ctrl+Alt+f doesn't work
Bugs item #2894352, was opened at 2009-11-09 03:03 Message generated for change (Comment added) made by jessorensen You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=893831aid=2894352group_id=180599 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: qemu Group: None Status: Closed Resolution: Works For Me Priority: 5 Private: No Submitted By: pjw (pawelwalaszek) Assigned to: Nobody/Anonymous (nobody) Summary: Ctrl+Alt+f doesn't work Initial Comment: Ctrl+Alt+f doesn't work in qemu-kvm 0.11.0. I have tested it on Ubuntu 9.10. Provisionally there is a workaround. To disable a full screen is Ctrl+Alt+f Ctrl+Alt+1 and to enable is Ctrl+Alt+1 Ctrl+Alt+f. -- Comment By: Jes Sorensen (jessorensen) Date: 2010-11-26 11:55 Message: This works fine in current upstream 0.13, so closing as fixed. Jes -- You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=893831aid=2894352group_id=180599 -- To unsubscribe from this list: send the line unsubscribe kvm in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
[ kvm-Bugs-2869748 ] KVM-88 broke VirtIO Hard Disks
Bugs item #2869748, was opened at 2009-09-29 14:47 Message generated for change (Comment added) made by jessorensen You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=893831aid=2869748group_id=180599 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: qemu Group: None Status: Closed Resolution: Out of Date Priority: 5 Private: No Submitted By: Dietmar Maurer (dietmarmaurer) Assigned to: Nobody/Anonymous (nobody) Summary: KVM-88 broke VirtIO Hard Disks Initial Comment: As already mentione on the list, VirtIO is still broken in qemu-kvm-0-11.0. Reverting the patch solves the problem. It turned out to be a Qemu merge into KVM userspace: kvm-87-119-ga8b7f95 (commit a8b7f959d1fd97c4ccaf08ce750020ecd08b4c88) Can you look into it? Not sure if you familiar with this, but anyway: $ git diff-tree -p bf011293f | patch -R -p1 -- Comment By: Jes Sorensen (jessorensen) Date: 2010-11-26 11:58 Message: virtio has been working fine for a long time, so closing as out of date. -- You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=893831aid=2869748group_id=180599 -- To unsubscribe from this list: send the line unsubscribe kvm in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
[ kvm-Bugs-2998292 ] XP Guest Crash on Ubuntu 10.04
Bugs item #2998292, was opened at 2010-05-07 20:28 Message generated for change (Comment added) made by jessorensen You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=893831aid=2998292group_id=180599 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open Resolution: None Priority: 7 Private: No Submitted By: cheesewright () Assigned to: Nobody/Anonymous (nobody) Summary: XP Guest Crash on Ubuntu 10.04 Initial Comment: OS: Ubuntu Server 64-bit 10.04, kernel 2.6.32 Server: Supermicro X8DTN+ 2x Xeon E5530 2.4GHz Nehalem quad core cpu, 12GB RAM Guest: Windows XP SP3 32-bit Below is my kvm command line: /usr/bin/kvm -S -M pc-0.11 -enable-kvm -m 1024 -smp 2 -name data2 -uuid 9a85ee7a-4db9-9108-df3c-61d04d3c943d -chardev socket,id=monitor,path=/var/lib/libvirt/qemu/data2.monitor,server,nowait -monitor chardev:monitor -localtime -boot c -drive file=/san/data2/winxp.img,if=ide,index=0,boot=on -drive file=/dev/cdrom,if=ide,media=cdrom,index=2 -net nic,macaddr=52:54:00:38:a8:af,vlan=0,name=nic.0 -net tap,fd=62,vlan=0,name=tap.0 -chardev pty,id=serial0 -serial chardev:serial0 -parallel none -usb -usbdevice tablet -vnc 0.0.0.0:2,password -k en-us -vga cirrus I have two XP SP3 guests which crash frequently on random events when connecting via remote desktop. The Windows Event Log reports Event ID 1003. These errors result in either a system freeze or full reboot. There are several types of errors recorded: Event Source: System Error Event Category: (102) Event ID: 1003 Error code 0005, parameter1 04c0, parameter2 8653a6c8, parameter3 , parameter4 . Event Source: System Error Event Category: (102) Event ID: 1003 Error code 000a, parameter1 3008, parameter2 0002, parameter3 , parameter4 804ff806. Event Source: System Error Event Category: (102) Event ID: 1003 Error code 100a, parameter1 3008, parameter2 0002, parameter3 , parameter4 804ff806. -- Comment By: Jes Sorensen (jessorensen) Date: 2010-11-26 12:01 Message: Hi, Are you still able to reproduce this with uptodate kvm/qemu? If you are, would you mind opening a bug in https://bugs.launchpad.net/qemu and close this one ? Does this only happen when you access the systems via remote desktop? (I presume this is some windows thing?) Thanks, Jes -- Comment By: cheesewright () Date: 2010-05-07 20:32 Message: The crash also happens when using kvm -M pc-0.12. It is easily reproducible after clicking through windows such control panel apps, or web browsers, for a few minutes. -- You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=893831aid=2998292group_id=180599 -- To unsubscribe from this list: send the line unsubscribe kvm in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
[ kvm-Bugs-2972152 ] guest crash when -cpu kvm64
Bugs item #2972152, was opened at 2010-03-17 20:43 Message generated for change (Comment added) made by jessorensen You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=893831aid=2972152group_id=180599 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: libkvm Group: None Status: Closed Resolution: Out of Date Priority: 5 Private: No Submitted By: hugohiggins (high33) Assigned to: Nobody/Anonymous (nobody) Summary: guest crash when -cpu kvm64 Initial Comment: When using -cpu kvm64 guest crashes when X starts up. dmesg on hypervisor says: [6149047.906364] kvm: 29020: cpu0 unhandled rdmsr: 0xc0010112 Guest boots OK without -cpu parameter cpu: dual opteron 2435 (12 cores total) ram: 32gig host dist: ubuntu 9.04 host kernel: 2.6.28-16-generic #55-Ubuntu SMP guest dist: xubuntu-9.10-amd64 # /usr/local/qemu-kvm-0.12.3/bin/qemu-system-x86_64 -name ubu64 localhost:69 -M pc \ -m 2048 -boot d -vga std \ -net nic,macaddr=BA:DD:C0:FF:EE:F6,model=virtio -net vde \ -drive file=/dev/sdp,if=scsi,boot=on \ -cpu kvm64 \ -cdrom iso/xubuntu-9.10-desktop-amd64.iso -k en-us -localtime -sdl -vnc localhost:69 -daemonize -usbdevice tablet -- Comment By: Jes Sorensen (jessorensen) Date: 2010-11-26 12:11 Message: No reply since question of August 19, so closing as out of date. Jes -- Comment By: Jes Sorensen (jessorensen) Date: 2010-08-19 12:32 Message: Hi, Are you still seeing this problem? I have been able to boot guests with recent KVM and -cpu kvm64 without problems. Note the kvm: 29020: cpu0 unhandled rdmsr: 0xc0010112 message is unrelated to the problem you have been seeing. Cheers, Jes -- You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=893831aid=2972152group_id=180599 -- To unsubscribe from this list: send the line unsubscribe kvm in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
[ kvm-Bugs-2971075 ] Assertion `bmdma-unit != (uint8_t)-1' failed.
Bugs item #2971075, was opened at 2010-03-16 07:02 Message generated for change (Comment added) made by jessorensen You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=893831aid=2971075group_id=180599 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: qemu Group: v1.0 (example) Status: Open Resolution: None Priority: 5 Private: No Submitted By: Andre Weidemann (zaphodbrx) Assigned to: Nobody/Anonymous (nobody) Summary: Assertion `bmdma-unit != (uint8_t)-1' failed. Initial Comment: Hi, I cloned the qemu-kvm git repository with git clone git://git.kernel.org/pub/scm/virt/kvm/qemu-kvm.git qemu-kvm-2010-03-14, ran configure and compiled it and did a make install. Everything went fine without warnings or errors. For configure output take a look here: http://pastebin.com/BL4DYCRY Here is my Server Hardware: Asus P5Q Mainboard Intel Q9300 8GB RAM I am running Ubuntu 9.10 x86_64 with kernel 2.6.31-20-server. RAID5 with mdadm consisting of 4x 1TB disks The volume /dev/storage/Windows7test mentioned below is on this RAID5. I ran my virtual machine with the following command: qemu-system-x86_64 -cpu core2duo -vga cirrus -boot order=ndc -vnc 192.168.3.42:2 -k de -smp 4,cores=4 -drive file=/vmware/Windows7Test_600G.img,if=ide,index=0,cache=writeback -m 1024 -net nic,model=e1000,macaddr=DE:AD:BE:EF:12:3A -net tap,script=/usr/local/bin/qemu-ifup -monitor pty -name Windows7test,process=Windows7test -drive file=/dev/storage/Windows7test,if=ide,index=1,cache=none,aio=native Windows7Test_600G.img is a qcow2 file and contains a Windows 7 Pro image. /dev/storage/Windows7test is formated with XFS(inside the VM) After starting the machine with the above command line, I booted into an Ubuntu 9.10 x86_64 Live Image via PXE and mounted /dev/sdb1 (/dev/storage/Windows7test) under /mnt. I then did cd /mnt/ and ran iozone -Ra -g 2G -b /tmp/iozone-aoi-linux.xls iozone ran some tests and then kvm simply quit with the following error message: qemu-system-x86_64: /usr/local/src/qemu-kvm-2010-03-10/hw/ide/internal.h:510: bmdma_active_if: Assertion `bmdma-unit != (uint8_t)-1' failed. /var/log/syslog contained the folowing: Mar 14 09:18:14 server kernel: [318080.627468] kvm: 1361: cpu0 kvm_set_msr_common: MSR_IA32_MCG_STATUS 0x0, nop Mar 14 09:18:14 server kernel: [318080.627473] kvm: 1361: cpu0 kvm_set_msr_common: MSR_IA32_MCG_CTL 0x, nop Mar 14 09:18:14 server kernel: [318080.627476] kvm: 1361: cpu0 unhandled wrmsr: 0x400 data Mar 14 09:18:14 server kernel: [318080.627506] kvm: 1361: cpu1 kvm_set_msr_common: MSR_IA32_MCG_STATUS 0x0, nop Mar 14 09:18:14 server kernel: [318080.627509] kvm: 1361: cpu1 kvm_set_msr_common: MSR_IA32_MCG_CTL 0x, nop Mar 14 09:18:14 server kernel: [318080.627511] kvm: 1361: cpu1 unhandled wrmsr: 0x400 data Mar 14 09:18:14 server kernel: [318080.627538] kvm: 1361: cpu2 kvm_set_msr_common: MSR_IA32_MCG_STATUS 0x0, nop Mar 14 09:18:14 server kernel: [318080.627540] kvm: 1361: cpu2 kvm_set_msr_common: MSR_IA32_MCG_CTL 0x, nop Mar 14 09:18:14 server kernel: [318080.627543] kvm: 1361: cpu2 unhandled wrmsr: 0x400 data I was able to reproduce this error 3 times in a row. -- Comment By: Jes Sorensen (jessorensen) Date: 2010-11-26 12:13 Message: Hi, Do you still see this with the latest KVM/QEMU? Looks like a bug in the IDE emulation, which may have been fixed since your report. Thanks, Jes -- You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=893831aid=2971075group_id=180599 -- To unsubscribe from this list: send the line unsubscribe kvm in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
[ kvm-Bugs-2964912 ] Web page wrong at /page/Vista_Net...
Bugs item #2964912, was opened at 2010-03-07 01:44 Message generated for change (Comment added) made by jessorensen You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=893831aid=2964912group_id=180599 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Closed Resolution: Fixed Priority: 5 Private: No Submitted By: Jakob Bohm (jbohmdk) Assigned to: Nobody/Anonymous (nobody) Summary: Web page wrong at /page/Vista_Net... Initial Comment: The page http://www.linux-kvm.org/page/Vista_Networking_Workaround currently contains two pieces of wrong (or at least misguided) information: Currently, the full text of that page is simply: This issue is now resolved and Vista works with the rtl8139 driver since CVS February and newer. 1. The page says that something changed in February, but it does not say which *year*, there is a huge difference between something changing in February 2010 or February 2008. 2. Just because some problem is solved in the CVS version of kvm (or *any* other software), it doesn't mean the change has made it to the actual real world copy of the software people are using, so any workaround, warning or other practical information for old bugs needs to stay available until you can be certain that the fix has been propagated all the way to all end users with regularly updated software. For a widely distributed project such as kvm, this means that all of the following must have happened: The change has made it into the stable release tarballs. These changed tarballs have been packaged by all distribution that previously packaged older affected releases. Those distributions have included the changed packages in released distributions or upgrades for all affected past distributions. Each distribution vendor has ended support for distribution versions containing only non-upgraded packages. At least 12 month have passed after this became true of all distributions that included the software versions affected by the issue. Yes, that is a very long time, but the only thing that needs to be done during that period is to keep the old contents available with a clear indication as to which tarballs included the problem and which tarballs included the fix, stating a CVS version or tag would be nice-to-have supplemental information but of little use for most people. -- Comment By: Jes Sorensen (jessorensen) Date: 2010-11-26 12:17 Message: Wiki updated to say Feb 2009 given that is most likely the date based on the wiki history of the page. -- You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=893831aid=2964912group_id=180599 -- To unsubscribe from this list: send the line unsubscribe kvm in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
[ kvm-Bugs-2961405 ] [Windows Virtio Net] repeatable lockup
Bugs item #2961405, was opened at 2010-03-01 18:56 Message generated for change (Comment added) made by jessorensen You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=893831aid=2961405group_id=180599 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Closed Resolution: Fixed Priority: 5 Private: No Submitted By: Brian Jackson (iggy_cav) Assigned to: Nobody/Anonymous (nobody) Summary: [Windows Virtio Net] repeatable lockup Initial Comment: I can get the virtio net drivers for Windows to repeatably lock up. I have a Windows 2008 R2 guest that has 3 virtio net connections connected to 3 bridges in the host. One network is for network traffic and two are for a storage network. The storage network interfaces are connecting to an iSCSI appliance. When syncing files from another server on the network (reading on interface 0, writing to iSCSI target on interfaces 1 2), the interfaces stop passing traffic for a period of time. It does eventually recover and is able to send/recv traffic. This causes the iSCSI volumes to be dropped and the guest subsequently gets into such a bad shape that it has to be rebooted. This is using self built virtio drivers from a git checkout on 20100226 Using qemu-kvm also from 20100226 (which does include a fix for a bug that I used to hit where the network would break and never come back) Let me know if you need any other info. -- Comment By: Jes Sorensen (jessorensen) Date: 2010-11-26 12:18 Message: This issue should be fixed in virtio-win-1.0.8 and later, you can get a more recent version here: http://www.linux-kvm.com/content/latest-windows-virtio-drivers Cheers, Jes -- You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=893831aid=2961405group_id=180599 -- To unsubscribe from this list: send the line unsubscribe kvm in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
[ kvm-Bugs-2950307 ] Linux not reboot when -no-kvm is used.
Bugs item #2950307, was opened at 2010-02-12 05:29 Message generated for change (Comment added) made by jessorensen You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=893831aid=2950307group_id=180599 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: amd Group: None Status: Closed Resolution: Invalid Priority: 5 Private: No Submitted By: Gerardo Exequiel Pozzi (djgera) Assigned to: Nobody/Anonymous (nobody) Summary: Linux not reboot when -no-kvm is used. Initial Comment: KVM Version: 0.12.2 Host: Linux 2.6.32.8 (tested in 32 and 64 bits) [Arch Linux] Guest: Linux-2.6.32.8/2.6.27.45 (tested in 32 and 64 bits) [Arch Linux] CPU: AMD 64 X2 5200+ What works: * Using in default KVM mode. * Using QEMU 0.12.2, without KVM mode. * Doing a halt, guest poweroff without any issues in all configurations. Steps: * qemu-system-x86_64 -no-kvm archlinux.img * reboot (guest) Symptoms: * kernel stop on message: machine restart. * At this point, on monitor doing a system_reset/system_poweroff does not restart/poweroff (just blank main screen) If you need more info, please ask me. Thanks. -- Comment By: Jes Sorensen (jessorensen) Date: 2010-11-26 12:20 Message: If this only fails when you are using -no-kvm, then it is obviously not a KVM problem. Please file a bug against QEMU in launchpad if you still see this. Cheers, Jes -- You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=893831aid=2950307group_id=180599 -- To unsubscribe from this list: send the line unsubscribe kvm in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
[ kvm-Bugs-2915201 ] Nested kvm (SVM)
Bugs item #2915201, was opened at 2009-12-16 01:35 Message generated for change (Comment added) made by jessorensen You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=893831aid=2915201group_id=180599 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: amd Group: v1.0 (example) Status: Open Resolution: None Priority: 5 Private: No Submitted By: jbl001 (jbl001) Assigned to: Nobody/Anonymous (nobody) Summary: Nested kvm (SVM) Initial Comment: I have seen a couple messages where people have stated that nested SVM works properly, but I cannot replicate it. I first attempted to use the following configurations: Hardware: desktop system: Gigabyte MA785GM board with Athlon X2 4400 server system: Tyan h2000M board with Opteron 2354 Software: Host OS: Ubuntu 9.10 with production kernel Host KVM: tried kmod 2.6.32 with qemu 0.11.1 and qemu 0.12.0rc2, also tried git-tip Guest VMM Host OS: Ubuntu 9.10 Guest VMM KVM: tried kmod 2.6.32 with qemu 0.11.1 and qemu 0.12.0rc2, also tried git-tip True guest: tried Slackware 10.2, 64-bit Ubuntu 8.10, 64-bit Ubuntu 9.10, and 32-bit XP All configurations result in the true guest not booting, but the Slackware 10.2 true guest is the easiest to analyze. It hangs at various places during boot with the most common being the calibrating delay loop, testing HLT instruction, mounting the hard disks, or starting the INIT processes. It seems it is losing interrupts. I also tried an older host (64-bit Ubuntu 8.10) and guest VMM (64-bit Ubuntu 8.10) with the KVM-88 release. With this configuration, the Slackware 10.2 true guest will usually boot, but will then get a constant flow of hda: lost interrupt and hda: dma_timer_expiry: dma status == 0x24. Again, it seems to be losing interrupts. I have ensured that the nested=1 is passed to the module and that enable-nesting is passed to the qemu. It obviously works for some time and I've tried printing out exit reasons in the handle_exit() function of the guest VMM, but it consistently fails in some form or another across all the hardware and software I have to try it on. -- Comment By: Jes Sorensen (jessorensen) Date: 2010-11-26 13:05 Message: Did this issue get resolved? Can we close the bug, there hasn't been any updates for over 9 months? -- Comment By: Alex Williamson (alex_williamson) Date: 2010-02-17 20:02 Message: Try reverting cd3ff653ae0b45bac7a19208e9c75034fcacc85f from kvm-kmod (kvm-svm). I ran into trouble with nested kvm about a month ago and bisected it back to this change. I alerted Joerg, but he might need another poke if this fixes nesting for you too. -- Comment By: jbl001 (jbl001) Date: 2010-02-17 18:47 Message: I tried this again with qemu-0.12.2 and kvm-kmod-2.6.32.3 while passing no-kvmclock to both the host and guest VMM kernels. It did not help the problem of lost interrupts in the true guest, however. -- Comment By: Brian Jackson (iggy_cav) Date: 2010-02-09 20:07 Message: Can you try disabling kvmclock in both guests? -- You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=893831aid=2915201group_id=180599 -- To unsubscribe from this list: send the line unsubscribe kvm in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
[ kvm-Bugs-2914397 ] Virtio drivers for Windows - large volumes fail
Bugs item #2914397, was opened at 2009-12-14 22:06 Message generated for change (Comment added) made by jessorensen You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=893831aid=2914397group_id=180599 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Brian Jackson (iggy_cav) Assigned to: Nobody/Anonymous (nobody) Summary: Virtio drivers for Windows - large volumes fail Initial Comment: When passing a 3T volume to a Windows 2008 guest using virtio drivers, the guest is unable to properly initialize the drive. Windows logs the following error: VDS fails to write boot code on a disk during clean operation. Error code: 80070...@02070008 It works correctly when using IDE emulation. This occurs with self built drivers from a checkout on Dec. 8 Host: Xeon 5130 Volumes are attached via iSCSI Guest: Windows 2008R2 64bit kvm -smp 2 -m 2000 -name p3hq-share01 -drive file=/dev/mapper/SPIVOT3__RAIGE_VOLUME___600176c3547ddd11a18e92c748d535e6,cache=none -drive file=/dev/mapper/SPIVOT3__RAIGE_VOLUME___600176c3851660644b72bd9548d535e6,cache=none,if=virtio -net nic,macaddr=52:54:00:41:86:28,vlan=0,model=virtio -net tap,vlan=0,script=/etc/kvm/kvm-ifup -usb -vnc :0 -vga std -daemonize -- Comment By: Jes Sorensen (jessorensen) Date: 2010-11-26 13:06 Message: Make sure you have the latest virtio-win drivers from: http://www.linux-kvm.com/content/latest-windows-virtio-drivers If this still fails, please open a bug in launchpad. Thanks, Jes -- You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=893831aid=2914397group_id=180599 -- To unsubscribe from this list: send the line unsubscribe kvm in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
[ kvm-Bugs-2886031 ] slowdown with smp switch
Bugs item #2886031, was opened at 2009-10-25 19:30 Message generated for change (Settings changed) made by jessorensen You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=893831aid=2886031group_id=180599 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Closed Resolution: Duplicate Priority: 5 Private: No Submitted By: Oliver Kowalke (oliver_kowalke) Assigned to: Nobody/Anonymous (nobody) Summary: slowdown with smp switch Initial Comment: slowdown (booting and character input) of Opensolaris 2009.06 with -smp2. Without -smp it works as before cat /proc/cpuinfo processor : 0 vendor_id : GenuineIntel cpu family : 6 model : 15 model name : Intel(R) Core(TM)2 Quad CPUQ6700 @ 2.66GHz stepping: 11 cpu MHz : 2660.000 cache size : 4096 KB physical id : 0 siblings: 4 core id : 0 cpu cores : 4 apicid : 0 initial apicid : 0 fpu : yes fpu_exception : yes cpuid level : 10 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx lm constant_tsc arch_perfmon pebs bts rep_good pni dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm lahf_lm tpr_shadow vnmi flexpriority bogomips: 6000.86 clflush size: 64 cache_alignment : 64 address sizes : 36 bits physical, 48 bits virtual power management: processor : 1 vendor_id : GenuineIntel cpu family : 6 model : 15 model name : Intel(R) Core(TM)2 Quad CPUQ6700 @ 2.66GHz stepping: 11 cpu MHz : 2660.000 cache size : 4096 KB physical id : 0 siblings: 4 core id : 1 cpu cores : 4 apicid : 1 initial apicid : 1 fpu : yes fpu_exception : yes cpuid level : 10 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx lm constant_tsc arch_perfmon pebs bts rep_good pni dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm lahf_lm tpr_shadow vnmi flexpriority bogomips: 5999.72 clflush size: 64 cache_alignment : 64 address sizes : 36 bits physical, 48 bits virtual power management: processor : 2 vendor_id : GenuineIntel cpu family : 6 model : 15 model name : Intel(R) Core(TM)2 Quad CPUQ6700 @ 2.66GHz stepping: 11 cpu MHz : 2660.000 cache size : 4096 KB physical id : 0 siblings: 4 core id : 2 cpu cores : 4 apicid : 2 initial apicid : 2 fpu : yes fpu_exception : yes cpuid level : 10 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx lm constant_tsc arch_perfmon pebs bts rep_good pni dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm lahf_lm tpr_shadow vnmi flexpriority bogomips: 5999.74 clflush size: 64 cache_alignment : 64 address sizes : 36 bits physical, 48 bits virtual power management: processor : 3 vendor_id : GenuineIntel cpu family : 6 model : 15 model name : Intel(R) Core(TM)2 Quad CPUQ6700 @ 2.66GHz stepping: 11 cpu MHz : 2660.000 cache size : 4096 KB physical id : 0 siblings: 4 core id : 3 cpu cores : 4 apicid : 3 initial apicid : 3 fpu : yes fpu_exception : yes cpuid level : 10 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx lm constant_tsc arch_perfmon pebs bts rep_good pni dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm lahf_lm tpr_shadow vnmi flexpriority bogomips: 5999.74 clflush size: 64 cache_alignment : 64 address sizes : 36 bits physical, 48 bits virtual power management: kvm version: 88 host: Linux c2dlx01 2.6.29.2-x86-64-raid #1 SMP PREEMPT Sat Oct 10 08:47:38 CEST 2009 x86_64 GNU/Linux (Debian/testing) quest: OpenSolaris 2009.06 x86_64 kvm -name solaris -hda /var/lib/libvirt/images/solaris-opensolaris.qcow2 -boot c -m 1024 -smp2 -net nic,macaddr=00:1a:92:bab:01:c1 -net tap -- Comment By: Jes Sorensen (jessorensen) Date: 2010-11-26 13:08 Message: Duplicate of 2885990 -- You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=893831aid=2886031group_id=180599 -- To unsubscribe from this list: send the line unsubscribe kvm in the body
[ kvm-Bugs-2885990 ] slowdown with smp switch
Bugs item #2885990, was opened at 2009-10-25 17:52 Message generated for change (Comment added) made by jessorensen You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=893831aid=2885990group_id=180599 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Oliver Kowalke (oliver_kowalke) Assigned to: Nobody/Anonymous (nobody) Summary: slowdown with smp switch Initial Comment: slowdown (booting and character input) of Opensolaris 2009.06 with -smp2. Without -smp it works as before cat /proc/cpuinfo processor : 0 vendor_id : GenuineIntel cpu family : 6 model : 15 model name : Intel(R) Core(TM)2 Quad CPUQ6700 @ 2.66GHz stepping: 11 cpu MHz : 2660.000 cache size : 4096 KB physical id : 0 siblings: 4 core id : 0 cpu cores : 4 apicid : 0 initial apicid : 0 fpu : yes fpu_exception : yes cpuid level : 10 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx lm constant_tsc arch_perfmon pebs bts rep_good pni dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm lahf_lm tpr_shadow vnmi flexpriority bogomips: 6000.86 clflush size: 64 cache_alignment : 64 address sizes : 36 bits physical, 48 bits virtual power management: processor : 1 vendor_id : GenuineIntel cpu family : 6 model : 15 model name : Intel(R) Core(TM)2 Quad CPUQ6700 @ 2.66GHz stepping: 11 cpu MHz : 2660.000 cache size : 4096 KB physical id : 0 siblings: 4 core id : 1 cpu cores : 4 apicid : 1 initial apicid : 1 fpu : yes fpu_exception : yes cpuid level : 10 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx lm constant_tsc arch_perfmon pebs bts rep_good pni dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm lahf_lm tpr_shadow vnmi flexpriority bogomips: 5999.72 clflush size: 64 cache_alignment : 64 address sizes : 36 bits physical, 48 bits virtual power management: processor : 2 vendor_id : GenuineIntel cpu family : 6 model : 15 model name : Intel(R) Core(TM)2 Quad CPUQ6700 @ 2.66GHz stepping: 11 cpu MHz : 2660.000 cache size : 4096 KB physical id : 0 siblings: 4 core id : 2 cpu cores : 4 apicid : 2 initial apicid : 2 fpu : yes fpu_exception : yes cpuid level : 10 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx lm constant_tsc arch_perfmon pebs bts rep_good pni dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm lahf_lm tpr_shadow vnmi flexpriority bogomips: 5999.74 clflush size: 64 cache_alignment : 64 address sizes : 36 bits physical, 48 bits virtual power management: processor : 3 vendor_id : GenuineIntel cpu family : 6 model : 15 model name : Intel(R) Core(TM)2 Quad CPUQ6700 @ 2.66GHz stepping: 11 cpu MHz : 2660.000 cache size : 4096 KB physical id : 0 siblings: 4 core id : 3 cpu cores : 4 apicid : 3 initial apicid : 3 fpu : yes fpu_exception : yes cpuid level : 10 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx lm constant_tsc arch_perfmon pebs bts rep_good pni dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm lahf_lm tpr_shadow vnmi flexpriority bogomips: 5999.74 clflush size: 64 cache_alignment : 64 address sizes : 36 bits physical, 48 bits virtual power management: kvm version: 88 host: Linux c2dlx01 2.6.29.2-x86-64-raid #1 SMP PREEMPT Sat Oct 10 08:47:38 CEST 2009 x86_64 GNU/Linux (Debian/testing) quest: OpenSolaris 2009.06 x86_64 kvm -name solaris -hda /var/lib/libvirt/images/solaris-opensolaris.qcow2 -boot c -m 1024 -smp2 -net nic,macaddr=00:1a:92:bab:01:c1 -net tap -- Comment By: Jes Sorensen (jessorensen) Date: 2010-11-26 13:09 Message: Do you still see this with recent KVM? Thanks, Jes -- Comment By: Oddjobz (oddjobz) Date: 2009-12-03 15:17 Message: I have the same problem. Stock Ubuntu 9.10, processor is an AMD Phenom II X4, QEMU PC emulator version 0.11.0
[ kvm-Bugs-2941282 ] Ubuntu 10.04 installer fails due to I/O errors with virtio
Bugs item #2941282, was opened at 2010-01-27 23:19
Message generated for change (Comment added) made by jessorensen
You can respond by visiting:
https://sourceforge.net/tracker/?func=detailatid=893831aid=2941282group_id=180599
Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
Group: None
Status: Closed
Resolution: Fixed
Priority: 7
Private: No
Submitted By: Marti Raudsepp (intgr)
Assigned to: Nobody/Anonymous (nobody)
Summary: Ubuntu 10.04 installer fails due to I/O errors with virtio
Initial Comment:
I tried installing Ubuntu 10.04 and Fedora 12 in a KVM virtual machine using
virtio, on a 8G raw file-backed disk. Both installers failed half-way due to
I/O errors. So I tried reproducing it and managed to repeat it 6 times. The bug
doesn't occur with IDE emulation. The bug happens fairly quickly with -smp 4 --
usually within 5 minutes -- but is much rarer with -smp 1.
Ubuntu installer has kernel 2.6.32-11-generic
Fedora 12 has kernel 2.6.31.5-127.fc12.x86_64
Host has kernel 2.6.32.6 (Arch Linux) and QEMU 0.12.2
When testing with -smp 1, it also produced a kernel oops from
block/blk-core.c:245. This line warns when the function is called with
interrupts enabled:
void blk_start_queue(struct request_queue *q)
{
WARN_ON(!irqs_disabled());
queue_flag_clear(QUEUE_FLAG_STOPPED, q);
__blk_run_queue(q);
}
--- host machine ---
[ma...@newn]% qemu-kvm --version
QEMU PC emulator version 0.12.2 (qemu-kvm-0.12.2), Copyright (c) 2003-2008
Fabrice Bellard
[ma...@newn]% ps aux |grep crash
root 16283 31.4 7.1 427020 289960 ? Sl 22:44 8:37
/usr/bin/qemu-kvm -S -M pc-0.11 -enable-kvm -m 256 -smp 1 -name
ubuntu-crashtest -uuid 0d7d4f2d-5589-160b-1f1b-75d46e293a2c -chardev
socket,id=monitor,path=/var/lib/libvirt/qemu/ubuntu-crashtest.monitor,server,nowait
-monitor chardev:monitor -boot d -drive
file=/store/iso/lucid-desktop-amd64.iso,if=ide,media=cdrom,index=2,format=raw
-drive file=/store/virt/ubuntu-crashtest.img,if=virtio,index=0,format=raw -net
nic,macaddr=52:54:00:45:e7:19,vlan=0,name=nic.0 -net
tap,fd=43,vlan=0,name=tap.0 -serial none -parallel none -usb -usbdevice tablet
-vnc 127.0.0.1:1 -k en-us -vga cirrus -soundhw es1370 -balloon virtio
marti17700 0.0 0.0 8360 968 pts/4S+ 23:11 0:00 grep crash
[ma...@newn]% stat /store/virt/ubuntu-crashtest.img
File: `/store/virt/ubuntu-crashtest.img'
Size: 8589934592 Blocks: 5615368IO Block: 4096 regular file
Device: fe01h/65025dInode: 4718596 Links: 1
Access: (0600/-rw---) Uid: (0/root) Gid: (0/root)
Access: 2010-01-27 22:43:45.128113080 +0200
Modify: 2010-01-27 23:09:11.523577452 +0200
Change: 2010-01-27 23:09:11.523577452 +0200
[ma...@newn]% uname -a
Linux newn 2.6.32-ARCH #1 SMP PREEMPT Mon Jan 25 20:33:50 CET 2010 x86_64 AMD
Phenom(tm) II X4 940 Processor AuthenticAMD GNU/Linux
[ma...@newn]% cat /proc/cpuinfo
processor : 0
vendor_id : AuthenticAMD
cpu family : 16
model : 4
model name : AMD Phenom(tm) II X4 940 Processor
stepping: 2
cpu MHz : 800.000
cache size : 512 KB
physical id : 0
siblings: 4
core id : 0
cpu cores : 4
apicid : 0
initial apicid : 0
fpu : yes
fpu_exception : yes
cpuid level : 5
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov
pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb
rdtscp lm 3dnowext 3dnow constant_tsc rep_good nonstop_tsc extd_apicid pni
monitor cx16 popcnt lahf_lm cmp_legacy svm extapic cr8_legacy abm sse4a
misalignsse 3dnowprefetch osvw ibs skinit wdt
bogomips: 6028.69
TLB size: 1024 4K pages
clflush size: 64
cache_alignment : 64
address sizes : 48 bits physical, 48 bits virtual
power management: ts ttp tm stc 100mhzsteps hwpstate
*snip* three more CPU cores
--- Ubuntu guest VM ---
ubu...@ubuntu:/tmp$ uname -a
Linux ubuntu 2.6.32-11-generic #15-Ubuntu SMP Tue Jan 19 20:38:41 UTC 2010
x86_64 GNU/Linux
ubu...@ubuntu:/tmp$ cat /sys/block/vda/stat
7388948289 1661218 39497026765 947851 6284676 9459960
0 987890 9893220
ubu...@ubuntu:/tmp$ dmesg
[0.00] Initializing cgroup subsys cpuset
[0.00] Initializing cgroup subsys cpu
[0.00] Linux version 2.6.32-11-generic (bui...@crested) (gcc version
4.4.3 20100116 (prerelease) (Ubuntu 4.4.2-9ubuntu4) ) #15-Ubuntu SMP Tue Jan 19
20:38:41 UTC 2010 (Ubuntu 2.6.32-11.15-generic)
[0.00] Command line: BOOT_IMAGE=/casper/vmlinuz
file=/cdrom/preseed/ubuntu.seed boot=casper only-ubiquity
initrd=/casper/initrd.lz quiet splash --
[0.00] KERNEL supported cpus:
[0.00] Intel GenuineIntel
[0.00] AMD AuthenticAMD
[0.00] Centaur CentaurHauls
[0.00] BIOS
[ kvm-Bugs-2949622 ] kvm - dmi rembo error on guest
Bugs item #2949622, was opened at 2010-02-11 11:12 Message generated for change (Comment added) made by jessorensen You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=893831aid=2949622group_id=180599 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: qemu Group: None Status: Closed Resolution: Invalid Priority: 7 Private: No Submitted By: Peter B. (jden44) Assigned to: Nobody/Anonymous (nobody) Summary: kvm - dmi rembo error on guest Initial Comment: Hello kvm experts, * cpu model host = XEON E5420 8 core * kvm version = 0.12.2 * host kernel = 2.6.31.8-desktop (opensuse 11.2 64 bit) * guest OS = ubuntu 8.04 32 bit , kernel = 2.6.24-16-server * quemu command line (done by aqemu)= /usr/bin/qemu-kvm -smp 2 -k de -no-kvm-irqchip -kvm-shadow-memory 4 -m 1528 -localtime -cdrom /home/iso/logodidact.iso -hda /home/vms/LogoDidact1_HDA -boot c -net nic,vlan=0 -net user,vlan=0 -net nic,vlan=0 -net tap,vlan=0,script=/etc/qemu01-ifup $* we are using logodidact sw, which consists of ubuntu 8.04 server with rembo5 sw and i want to migrate to a virtual machine with kvm. Host is opensuse 11.2 with kvm installed, and then using the gui aqemu to install VM's. Everthing is working fine with windows and linux systems as vm's, except with ubuntu 8.04/rembo. The guest ubuntu 8.04 is starting fine, until rembo (tivoli provisioning manager for os system 5.1) ist starting. We get the message, which blocks then the vm: starting rembo services.. loading rembo configuration into database.. --- DMI 5.31 found at ef2c0 (17293 tables at a43c6, max 17350) In a xenserver 5.5 enviroment it works fine in a virtual machine. please help. May the bios (bios.bin) is not supporting this dmi or the max is to small. Peter -- Comment By: Jes Sorensen (jessorensen) Date: 2010-11-26 13:13 Message: Sounds like it is trying to find something in the BIOS which isn't there, or something it thinks shouldn't be there. Looks like a bug in the rembo software, not a bug in KVM. Jes -- You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=893831aid=2949622group_id=180599 -- To unsubscribe from this list: send the line unsubscribe kvm in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
[ kvm-Bugs-2865820 ] kvm-88-r1 Intel E5450 Harpertown
Bugs item #2865820, was opened at 2009-09-24 17:44 Message generated for change (Comment added) made by jessorensen You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=893831aid=2865820group_id=180599 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: intel Group: None Status: Closed Resolution: Invalid Priority: 5 Private: No Submitted By: James Erickson (jimerickson) Assigned to: Nobody/Anonymous (nobody) Summary: kvm-88-r1 Intel E5450 Harpertown Initial Comment: i use kvm-88-r1 0n 64-bit gentoo. i recently install two quad core Intel E5450 Harpertown 64-bit processors. they do not have the vmx flag. so my /dev/kvm is not being created. is there a solution for this for this? my guest is usually 32-bit freedbsd. i have included /proc/cpuinfo as an attachment. -- Comment By: Jes Sorensen (jessorensen) Date: 2010-11-26 13:16 Message: If you don't have the vmx flag, then you haven't enabled virtualization in the bios. Closing Jes -- You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=893831aid=2865820group_id=180599 -- To unsubscribe from this list: send the line unsubscribe kvm in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
[ kvm-Bugs-2868883 ] netkvm.sys stops sending/receiving on Windows Server 2003 VM
Bugs item #2868883, was opened at 2009-09-28 16:27 Message generated for change (Comment added) made by jessorensen You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=893831aid=2868883group_id=180599 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Mark Weaver (mdw21) Assigned to: Nobody/Anonymous (nobody) Summary: netkvm.sys stops sending/receiving on Windows Server 2003 VM Initial Comment: This usually happens within an hour or two of starting the interface. It can be cured temporarily by disabling/enabling the adapter within Windows. I've run the Windows interface with log level set to 2 -- when traffic stops it still logs outgoing traffic as normal but ParaNdis_ProcessRxPath stops being logged. I suspect this is to do with the traffic content or timing as I cannot reproduce this with iperf, but only with external traffic to a website hosted on the machine. What further steps can I take to debug this issue? Host details: 2 x dual core xeons: processor : 0 vendor_id : GenuineIntel cpu family : 6 model : 23 model name : Intel(R) Xeon(R) CPU E5410 @ 2.33GHz stepping: 6 cpu MHz : 2327.685 cache size : 6144 KB physical id : 0 siblings: 4 core id : 0 cpu cores : 4 apicid : 0 initial apicid : 0 fpu : yes fpu_exception : yes cpuid level : 10 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx lm constant_tsc arch_perfmon pebs bts rep_good pni dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm dca sse4_1 lahf_lm tpr_shadow vnmi flexpriority bogomips: 4655.37 clflush size: 64 cache_alignment : 64 address sizes : 38 bits physical, 48 bits virtual power management: kernel is 2.6.31 from kernel.org, userspace is debian lenny, all 64-bit qemu is qemu-kvm-0.10.6 Guest details: Windows Server 2003 32-bit qemu is started as: qemu-system-x86_64 \ -boot c \ -drive file=/data/vms/stooge/boot.raw,if=virtio,boot=on,cache=off \ -m 3072 \ -smp 1 \ -vnc 10.80.80.89:2 \ -k en-gb \ -net nic,model=virtio,macaddr=DE:AD:BE:EF:11:29 \ -net tap,ifname=tap0 \ -localtime \ -usb -usbdevice tablet \ -mem-path /hugepages -- Comment By: Jes Sorensen (jessorensen) Date: 2010-11-26 13:17 Message: Please try the latest virtio-win drivers from: http://www.linux-kvm.com/content/latest-windows-virtio-drivers Cheers, Jes -- Comment By: Dor Laor (thekozmo) Date: 2009-10-12 00:42 Message: Sorry, /me wrong, I now saw you compiled the git code. Ignore the last comment -- Comment By: Dor Laor (thekozmo) Date: 2009-10-12 00:41 Message: Those drivers are old. Please use http://www.linux-kvm.org/page/WindowsGuestDrivers/Download_Drivers -- Comment By: amontezuma (amontezuma) Date: 2009-10-03 23:08 Message: This is probably the same bug as all these others: https://sourceforge.net/tracker/?func=detailaid=2506814group_id=180599atid=893831 https://sourceforge.net/tracker/?func=detailatid=893831aid=1771262group_id=180599 https://sourceforge.net/tracker/?func=detailatid=893831aid=2327497group_id=180599 it is the most serious and annoying bug in KVM imho and it has been there for SO LONG. -- Comment By: Mark Weaver (mdw21) Date: 2009-09-29 16:00 Message: 1. Could you please attach the log Too big for sf.net, I have put a log here: http://www.blushingpenguin.com/kvm/netkvm.log.bz2 During that log, it appeared that outgoing packets were still being transmitted, however incoming packets were not being received. This was verified by running ping on the guest and using tcpdump on the host. After a while packets started begin received again. The pattern can be seen with: grep received netkvm.log foo up to 2235.26074219 packets are being pulled out regularly -- generally 1-2 packets at a time. After that they start begin pulled out irregularly and in greater numbers. after 2870.28808594 normal service is resumed. 2. Could you be more specific on the scenario? Are you running some tests or network application? It's running websites under IIS. I tried to reproduce this issue with various iperf scenarios but failed to do so. 3. You could raise debug level even more to level 6 - that would give the information about the rings (how much space is left
[ kvm-Bugs-2763707 ] Soft lockup after migration in 64 bit SMP RHEL 5.3 guest
Bugs item #2763707, was opened at 2009-04-15 02:53 Message generated for change (Comment added) made by jessorensen You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=893831aid=2763707group_id=180599 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Dinesh K Subhraveti (subhraveti) Assigned to: Nobody/Anonymous (nobody) Summary: Soft lockup after migration in 64 bit SMP RHEL 5.3 guest Initial Comment: kvm: kvm-84-6607-ga317a1e kvm-userspace: kvm-84-519-ge97260d modinfo kvm: filename: /lib/modules/2.6.27.11-1-default/extra/kvm.ko license:GPL author: Qumranet version:kvm-84-6607-ga317a1e srcversion: 71C29061F9E400B2E7EE646 depends: vermagic: 2.6.27.11-1-default SMP mod_unload modversions parm: oos_shadow:bool modinfo kvm-intel: filename: /lib/modules/2.6.27.11-1-default/extra/kvm-intel.ko license:GPL author: Qumranet version:kvm-84-6607-ga317a1e srcversion: 4406015C2969CA7636B2C95 depends:kvm vermagic: 2.6.27.11-1-default SMP mod_unload modversions parm: bypass_guest_pf:bool parm: vpid:bool parm: flexpriority:bool parm: ept:bool parm: emulate_invalid_guest_state:bool Cmdline: qemu-system-x86_64 -m 1024 -drive file=/scratch/images/RHEL5.3-Server-x86_64.raw -net tap -net nic,model=e1000,macaddr=00:FF:FE:00:00:03 -vnc :21 -boot cd -monitor stdio -smp 4 -incoming tcp:0:1 -- Comment By: Jes Sorensen (jessorensen) Date: 2010-11-26 13:20 Message: Hi, You haven't specified how big a host system you are using, and how you are migrating. Is it on the same host or to a different host. Is this still a problem? Thanks, Jes -- Comment By: Dinesh K Subhraveti (subhraveti) Date: 2009-04-16 03:27 Message: Please see the attachment containing the guest printks: hda: dma_timer_expiry: dma status == 0x24 hda: DMA interrupt recovery hda: lost interrupt hda: dma_timer_expiry: dma status == 0x24 hda: DMA interrupt recovery hda: lost interrupt hda: dma_timer_expiry: dma status == 0x24 hda: DMA interrupt recovery hda: lost interrupt BUG: soft lockup - CPU#0 stuck for 10s! [events/0:14] CPU 0: Modules linked in: autofs4 hidp rfcomm l2cap bluetooth sunrpc ip_conntrack_netbios_ns ipt_REJECT xt_state ip_conntrack nfnetlink iptable_filter ip_tables ip6t_REJECT xt_tcpudp ip6table_filter ip6_tables x_tables ipv6 xfrm_nalgo crypto_api dm_multipath scsi_dh video hwmon backlight sbs i2c_ec button battery asus_acpi acpi_memhotplug ac lp floppy ide_cd cdrom parport_pc i2c_piix4 parport e1000 i2c_core virtio_pci pcspkr virtio_ring virtio serio_raw dm_raid45 dm_message dm_region_hash dm_mem_cache dm_snapshot dm_zero dm_mirror dm_log dm_mod ata_piix libata sd_mod scsi_mod ext3 jbd uhci_hcd ohci_hcd ehci_hcd Pid: 14, comm: events/0 Not tainted 2.6.18-128.el5 #1 RIP: 0010:[800759f3] [800759f3] __smp_call_function+0x66/0x8b RSP: 0018:810037f39d90 EFLAGS: 0293 RAX: RBX: RCX: RDX: 00ff RSI: 00bf RDI: 00c0 RBP: R08: 0004 R09: 003c R10: 810037f39cf0 R11: 810036b2cc80 R12: R13: R14: 000e R15: 0286 FS: () GS:803ac000() knlGS: CS: 0010 DS: 0018 ES: 0018 CR0: 8005003b CR2: 2adc9d793000 CR3: 34094000 CR4: 06e0 Call Trace: [800721dc] mcheck_check_cpu+0x0/0x2f [80075b25] smp_call_function+0x32/0x47 [800721dc] mcheck_check_cpu+0x0/0x2f [80091aa2] on_each_cpu+0x10/0x22 [8007151e] mcheck_timer+0x1c/0x6c [8004d139] run_workqueue+0x94/0xe4 [800499ba] worker_thread+0x0/0x122 [80049aaa] worker_thread+0xf0/0x122 [8008a461] default_wake_function+0x0/0xe [80032360] kthread+0xfe/0x132 [8005dfb1] child_rip+0xa/0x11 [80032262] kthread+0x0/0x132 [8005dfa7] child_rip+0x0/0x11 hda: dma_timer_expiry: dma status == 0x24 BUG: soft lockup - CPU#0 stuck for 10s! [events/0:14] CPU 0: Modules linked in: autofs4 hidp rfcomm l2cap bluetooth sunrpc ip_conntrack_netbios_ns ipt_REJECT xt_state ip_conntrack nfnetlink iptable_filter ip_tables ip6t_REJECT xt_tcpudp ip6table_filter ip6_tables x_tables ipv6 xfrm_nalgo crypto_api dm_multipath scsi_dh video hwmon backlight sbs i2c_ec button battery asus_acpi acpi_memhotplug ac lp floppy ide_cd cdrom parport_pc i2c_piix4 parport e1000 i2c_core virtio_pci pcspkr virtio_ring virtio serio_raw
[ kvm-Bugs-2629101 ] rdesktop doesnot work using KVM-84
Bugs item #2629101, was opened at 2009-02-23 02:12 Message generated for change (Comment added) made by jessorensen You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=893831aid=2629101group_id=180599 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Closed Resolution: Fixed Priority: 5 Private: No Submitted By: z axis (sw2wolf) Assigned to: Nobody/Anonymous (nobody) Summary: rdesktop doesnot work using KVM-84 Initial Comment: # what cpu model (examples: Intel Core Duo, Intel Core 2 Duo, AMD Opteron 2210). See /proc/cpuinfo if you're not sure. $ uname -a Linux myarch 2.6.28-ARCH #1 SMP PREEMPT Sun Feb 8 10:13:45 UTC 2009 i686 AMD Athlon(tm) 64 X2 Dual Core Processor 3600+ AuthenticAMD GNU/Linux The guest OS is Windows XP, rdesktop works fine when using KVM-83, however it doenot work when using KVM-84 ! $/usr/local/bin/qemu-system-x86_64 -M pc -m 256 -soundhw es1370 -hda /media/E/winxp.img -hdb /dev/sda7 -net nic,model=virtio -net user -localtime -vnc 127.0.0.1:0 -daemonize -redir tcp:3389::3389 $rdesktop localhost:3389 -u sw2wolf -p 123 -g 1440x880 -D -r sound:remote sincerely! -- Comment By: Jes Sorensen (jessorensen) Date: 2010-11-26 13:21 Message: Per reporter, it works now. -- Comment By: z axis (sw2wolf) Date: 2009-05-23 10:55 Message: It works fine now. Today i reinstall the guest XP using KVM-86 without the kvm-guest-drivers-windows (http://sourceforge.net/project/showfiles.php?group_id=180599package_id=267943) then rdesktop works very well. -- You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=893831aid=2629101group_id=180599 -- To unsubscribe from this list: send the line unsubscribe kvm in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
[ kvm-Bugs-2848498 ] COMPILATION ERRORS
Bugs item #2848498, was opened at 2009-09-01 16:51
Message generated for change (Comment added) made by jessorensen
You can respond by visiting:
https://sourceforge.net/tracker/?func=detailatid=893831aid=2848498group_id=180599
Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: qemu
Group: None
Status: Closed
Resolution: Invalid
Priority: 5
Private: No
Submitted By: Pavel Vasilyev (pavlinux)
Assigned to: Nobody/Anonymous (nobody)
Summary: COMPILATION ERRORS
Initial Comment:
CPU: Dual Core AMD Opteron(tm) Processor 265
KVM: kvm-88-905-g6025b2d (git)
KERNEL: 2.6.30.5
ARCH: x86_64
Guest OS: Windows XP SP3
qemu command: many
Unused variables, redefinition, etc.
--
Comment By: Jes Sorensen (jessorensen)
Date: 2010-11-26 13:23
Message:
Doesn't show how you configured qemu-kvm, and it does build in upstream.
Closing
--
Comment By: Pavel Vasilyev (pavlinux)
Date: 2009-09-01 16:52
Message:
diff --git a/qemu-kvm.c b/qemu-kvm.c
index d554749..245c4c7 100644
--- a/qemu-kvm.c
+++ b/qemu-kvm.c
@@ -1815,7 +1815,6 @@ static void *ap_main_loop(void *_env)
{
CPUState *env = _env;
sigset_t signals;
-struct ioperm_data *data = NULL;
current_env = env;
env-thread_id = kvm_get_thread_id();
@@ -1824,6 +1823,9 @@ static void *ap_main_loop(void *_env)
env-kvm_cpu_state.vcpu_ctx = kvm_create_vcpu(env, env-cpu_index);
#ifdef USE_KVM_DEVICE_ASSIGNMENT
+
+struct ioperm_data *data = NULL;
+
/* do ioperm for io ports of assigned devices */
LIST_FOREACH(data, ioperm_head, entries)
on_vcpu(env, kvm_arch_do_ioperm, data);
diff --git a/qemu-kvm.h b/qemu-kvm.h
index 2c1730b..2ffc600 100644
--- a/qemu-kvm.h
+++ b/qemu-kvm.h
@@ -1060,6 +1060,9 @@ int kvm_arch_init_irq_routing(void);
int kvm_mmio_read(void *opaque, uint64_t addr, uint8_t * data, int len);
int kvm_mmio_write(void *opaque, uint64_t addr, uint8_t * data, int
len);
+void kvm_mutex_unlock(void);
+void kvm_mutex_lock(void);
+
#ifdef USE_KVM_DEVICE_ASSIGNMENT
struct ioperm_data;
@@ -1072,6 +1075,7 @@ void kvm_arch_do_ioperm(void *_data);
#define ALIGN(x, y) (((x)+(y)-1) ~((y)-1))
#define BITMAP_SIZE(m) (ALIGN(((m)TARGET_PAGE_BITS), HOST_LONG_BITS) /
8)
+
#ifdef CONFIG_KVM
#include sys-queue.h
@@ -1124,10 +1128,6 @@ static inline void kvm_init_vcpu(CPUState *env)
static inline void kvm_load_tsc(CPUState *env)
{
}
-#endif
-
-void kvm_mutex_unlock(void);
-void kvm_mutex_lock(void);
static inline void qemu_mutex_unlock_iothread(void)
{
@@ -1140,6 +1140,9 @@ static inline void qemu_mutex_lock_iothread(void)
if (kvm_enabled())
kvm_mutex_lock();
}
+#endif
+
+void kvm_arch_do_ioperm(void *data);
int kvm_physical_sync_dirty_bitmap(target_phys_addr_t start_addr,
target_phys_addr_t end_addr);
--
You can respond by visiting:
https://sourceforge.net/tracker/?func=detailatid=893831aid=2848498group_id=180599
--
To unsubscribe from this list: send the line unsubscribe kvm in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
[ kvm-Bugs-2811454 ] CPU ID Emulation bug: AMD Athlon
Bugs item #2811454, was opened at 2009-06-24 13:40 Message generated for change (Comment added) made by jessorensen You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=893831aid=2811454group_id=180599 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: qemu Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Technologov (technologov) Assigned to: Nobody/Anonymous (nobody) Summary: CPU ID Emulation bug: AMD Athlon Initial Comment: Qemu incorrectly emulates CPU ID of AMD Athlon CPU. Namely: 1. It uses CPU Model of Qemu CPU 2. It shows SSE/SSE2 instructions as CPU flags, while AMD Athlons don't have it. 3. When running KVM on Intel CPU, it shows CPU vendor as Intel instead of AMD. In my opinion KVM should refuse to emulate AMD Athlon CPUID on Intel CPUs, due to lacking 3Dnow! (unless those instructions can be emulated) -Alexey, 24.6.2009. -- Comment By: Jes Sorensen (jessorensen) Date: 2010-11-26 13:24 Message: The CPUID code has been completely rewamped, do you still see this issue? Jes -- Comment By: Technologov (technologov) Date: 2009-06-24 13:57 Message: Tesed on KVM-87rc7 on Intel, AMD and -no-kvm (Qemu) -- Comment By: Technologov (technologov) Date: 2009-06-24 13:41 Message: Qemu command: ./qemu-kvm -hda /isos/disks-vm/alexeye/fc9-32.qcow2 -snapshot -m 512 -cpu athlon -- You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=893831aid=2811454group_id=180599 -- To unsubscribe from this list: send the line unsubscribe kvm in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
[ kvm-Bugs-2939216 ] Yellow bang on Win2008 when loading a network virtual func
Bugs item #2939216, was opened at 2010-01-25 02:48 Message generated for change (Comment added) made by alex_williamson You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=893831aid=2939216group_id=180599 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: qemu Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Lior Levy (llevy) Assigned to: Nobody/Anonymous (nobody) Summary: Yellow bang on Win2008 when loading a network virtual func Initial Comment: A network virtual device cannot load on Windows 2008. The network card is: Intel Corporation 82576 Gigabit Network Connection Getting an error of - The device cannot find enough free resources that it can use (Code 12). System information: - CPU - Intel(R) Xeon(R) CPU (2 sockets of quad core) - Host OS - RHEL 5.4 - Linux 2.6.18-160.el5 #1 SMP Mon Jul 27 17:28:29 EDT 2009 x86_64 x86_64 x86_64 GNU/Linux - The issue happens also on a newer kernel - 2.6.30.2 - Guest OS - Windows 2008 - Windows Server(R) Enterprise SP1 - 32 bit - KVM info filename: /lib/modules/2.6.18-160.el5/weak-updates/kmod-kvm/kvm.ko version:kvm-83-101.el5 srcversion: 45FED1544C648ADF0C59E7E vermagic: 2.6.18-159.el5 SMP mod_unload gcc-4.1 - QEMU info - QEMU PC emulator version 0.12.1 (qemu-kvm-0.12.1), Copyright (c) 2003-2008 Fabrice Bellard Steps to reproduce: (1) Put a network card -- Intel Corporation 82576 Gigabit Network Connection -- into the system (2) Load igb driver with flag to load a virtual function as well. insmod ./igb.ko max_vfs=2,2 (3) upload the interface ifconfig ethX up (4) Ensure that a VF exists in PCI enumeration lspci | grep Eth You should see a new virtual device like: 01:10.0 Ethernet controller: Intel Corporation 82576 Virtual Function (rev 01) (5) Load the guest VM with this VF qemu-system-x86_64 win2008.qcow2 -m 2048 -pcidevice host=01:10.0 -net none (6) Install the latest Intel drivers for Win2008 Install application can be found here: http://downloadcenter.intel.com/Detail_Desc.aspx?agr=YDwnldID=12197lang=eng (7) A Network device will appear in Device manager. Intel(R)Virtual Network Connection. But wirth yellow bang. Notes: When loading RHEL5.4 as a guest OS with the same flow, the device works as expected. The problem still exists when using the -no-kvm-irqchip or -no-kvm-pit switch. When using -no-kvm switch, the device is not seen in Windows device manager -- Comment By: Alex Williamson (alex_williamson) Date: 2010-11-26 06:48 Message: Boot the guest with -cpu qemu64,model=13 (or if you were on an AMD host -cpu qemu64,family=16). The problem is not with device assignment, but with 32bit Windows only enabling MSI support for minimum processor revisions. Since virtual functions only support MSI/X, they have no legacy interrupt fallback, so it's necessary to specify a newer vCPU model. -- You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=893831aid=2939216group_id=180599 -- To unsubscribe from this list: send the line unsubscribe kvm in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
[ kvm-Bugs-2800447 ] kvm fails to build against out of tree kernel builds+patch
Bugs item #2800447, was opened at 2009-06-03 13:17
Message generated for change (Comment added) made by jessorensen
You can respond by visiting:
https://sourceforge.net/tracker/?func=detailatid=893831aid=2800447group_id=180599
Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
Group: None
Status: Closed
Resolution: Fixed
Priority: 5
Private: No
Submitted By: James (tuxjay)
Assigned to: Nobody/Anonymous (nobody)
Summary: kvm fails to build against out of tree kernel builds+patch
Initial Comment:
Hi,
The first problem is the
--
Comment By: Jes Sorensen (jessorensen)
Date: 2010-11-26 15:00
Message:
Checked with Jan, bug was fixed a while ago.
If you see this again, please feel free to open a new bug in launchpad.
Thanks,
Jes
--
Comment By: Jan Kiszka (kiszka)
Date: 2009-06-03 14:24
Message:
That's trivial, look at other patches posted to the list: add a plain
Signed-off-by: YOUR NAME your-em...@address.
--
Comment By: James (tuxjay)
Date: 2009-06-03 14:19
Message:
I've prepared the patches and changelog entries, how do I get it signed
off? I've been searching the website for the patch procedure and couldn't
find it, sorry.
Thank you
--
Comment By: Jan Kiszka (kiszka)
Date: 2009-06-03 13:41
Message:
Please post your patches with individual changelogs and signed-off to
k...@vger.kernel.org. TiA.
--
Comment By: James (tuxjay)
Date: 2009-06-03 13:19
Message:
Hi,
The first problem is that kvm fails to detect the kernel source directory
correctly..
In configure the line
kernelsourcedir=${kerneldir%/*}/source
Only works if ../source is the build parent (e.g. if the source dir is
/lib/modules/version/source)
The first patch fixes that. The next is a build problem:
-Iarch/${ARCH_DIR}/include
should be: -I$(KERNELSOURCEDIR)/${ARCH_DIR}/include
In the case of out of place builds. The second patch fixes that.
Cheers, James
--
You can respond by visiting:
https://sourceforge.net/tracker/?func=detailatid=893831aid=2800447group_id=180599
--
To unsubscribe from this list: send the line unsubscribe kvm in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
[ kvm-Bugs-2796640 ] KVM Regression from 2.6.28-11 to 2.6.30-rc5
Bugs item #2796640, was opened at 2009-05-25 21:00 Message generated for change (Comment added) made by bobmanners You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=893831aid=2796640group_id=180599 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Bob Manners (bobmanners) Assigned to: Nobody/Anonymous (nobody) Summary: KVM Regression from 2.6.28-11 to 2.6.30-rc5 Initial Comment: Changing from the Ubuntu 09.04 stock kernel 2.6.28-11 to the current 'alpha' kernel in the Ubuntu development repository for 'Karmic' 2.6.30-rc5, some (but not all) of my KVM guests stop booting. I have the following guest OSs installed as KVM virtual machines: Ubuntu 09.04, FreeBSD 7.1, Minix 3, OpenSolaris 08.11, Windows XP and Windows 7RC Under 2.6.28-11 these all boot and run OK. With kernel 2.6.30-rc5, Ubuntu, FreeBSD and Minix boot and run OK, but OpenSolaris 08.11, Windows XP and Windows 7RC fail to boot. They appear to freeze very early in the boot process, after the boot loader is done and the OS kernel itself starts loading. There are no strange messages in the host system logs that I am aware of. When the guest OS freezes, it pins one of my CPUs at 100% utilization (I have KVM set to only give one CPU to the guest). This looks like a regression under 2.6.30-rc5. It is possible that it is caused by a Ubuntu patch, and I have filed a bug in Launchpad, but I suspect that this is an upstream problem, and so I am reporting it here also. Please let me know what I can do to assist in debugging this. -- Comment By: Bob Manners (bobmanners) Date: 2010-11-26 09:21 Message: I only experienced this problem on Intel Core Duo. On another system which has the more common Intel Core 2 Duo CPU I don't see this issue. Unfortunately my old (2006) laptop which was the Core Duo machine finally died last week so I am unable to confirm whether this KVM bug is still present in the 2.6.35 kernel (Ubuntu Maverick). -- Comment By: Jes Sorensen (jessorensen) Date: 2010-11-26 05:36 Message: Hi, Has this issue been resolved for you? Thanks, Jes -- Comment By: Kenni (kelu6) Date: 2009-05-28 04:26 Message: Your CPU still has the NX flag, which apparently also was my issue: http://thread.gmane.org/gmane.comp.emulators.kvm.devel/31206/focus=31774 -- Comment By: Bob Manners (bobmanners) Date: 2009-05-27 20:22 Message: In response to kelu6's question, actually I am running 32 bit host / 32 bit guest. My CPU is Intel Core Duo (not Core2 Duo) which is a 32 bit CPU: b...@gecko2:~$ cat /proc/cpuinfo processor : 0 vendor_id : GenuineIntel cpu family : 6 model : 14 model name : Genuine Intel(R) CPU T2400 @ 1.83GHz stepping: 8 cpu MHz : 1000.000 cache size : 2048 KB physical id : 0 siblings: 2 core id : 0 cpu cores : 2 apicid : 0 initial apicid : 0 fdiv_bug: no hlt_bug : no f00f_bug: no coma_bug: no fpu : yes fpu_exception : yes cpuid level : 10 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe nx constant_tsc arch_perfmon bts pni monitor vmx est tm2 xtpr pdcm bogomips: 3658.94 clflush size: 64 power management: processor : 1 vendor_id : GenuineIntel cpu family : 6 model : 14 model name : Genuine Intel(R) CPU T2400
[ kvm-Bugs-1841658 ] OpenSolaris 64bit panic with kvm-54
Bugs item #1841658, was opened at 2007-11-30 13:11 Message generated for change (Comment added) made by jessorensen You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=893831aid=1841658group_id=180599 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Closed Resolution: Works For Me Priority: 3 Private: No Submitted By: Carlo Marcelo Arenas Belon (carenas) Assigned to: Nobody/Anonymous (nobody) Summary: OpenSolaris 64bit panic with kvm-54 Initial Comment: Wouldn't mark it as a regression per-se as vanilla kvm-53 wouldn't work (because of the need for IDE patches to get it to run/install), but vanilla kvm-54 or kvm-54 + the same patches added to kvm-53 and including pre-kvm-55 patches like 71be592a14aa8d127315b2c47bf83cc0d810a341 wouldn't work. The panic is observed in kvm-54 (--no-kvm runs ok, and --no-kvm-irqchip doesn't help) while running nexenta OpenSolaris alpha 7 or beta 1 (other OpenSolaris distributions most likely affected as well) and with the following trace : panic[cpu0]/thread=fffec2de2260: BAD TRAP: type=e (#pf Page fault) rp=ff0001735f30 addr=0 occurred in module unix due to a NULL pointer dereference dbus: #pf Page fault Bad kernel fault at addr=0x0 pid=278, pc=0xfb83c189, sp=0xff0001736028, eflags=0x10246 cr0: 80050033pg,wp,ne,et,mp,pe cr4: 6b8xmme,fxsr,pge,pae,pse,de cr2: 0 cr3: 7dc4000 cr8: 0 rdi:0 rsi: fffec0025630 rdx: fffec2de2260 rcx:1 r8: fffec0025630 r9:3 rax:0 rbx:0 rbp: ff0001736080 r10:1 r11: fffec1ad31e0 r12:0 r13: fffec0025680 r14: c0025488 r15:0 fsb:0 gsb: fbc26ef0 ds: 4b es: 4b fs:0 gs: 1c3 trp:e err:0 rip: fb83c189 cs: 30 rfl:10246 rsp: ff0001736028 ss: 38 ff0001735e10 unix:die+c8 () ff0001735f20 unix:trap+135b () ff0001735f30 unix:cmntrap+e9 () ff0001736080 unix:mutex_exit+9 () ff00017360c0 genunix:kmem_alloc+88 () ff0001736110 zfs:zio_push_transform+3a () ff0001736190 zfs:zio_create+256 () ff0001736240 zfs:zio_vdev_child_io+97 () ff0001736320 zfs:vdev_cache_read+182 () ff0001736370 zfs:vdev_disk_io_start+41 () ff0001736390 zfs:vdev_io_start+1d () ff00017363d0 zfs:zio_vdev_io_start+123 () ff00017363f0 zfs:zio_next_stage_async+bb () ff0001736410 zfs:zio_nowait+11 () ff0001736450 zfs:vdev_mirror_io_start+18f () ff0001736490 zfs:zio_vdev_io_start+131 () ff00017364b0 zfs:zio_next_stage+b3 () ff00017364e0 zfs:zio_ready+10e () ff0001736500 zfs:zio_next_stage+b3 () ff0001736550 zfs:zio_wait_for_children+5d () ff0001736570 zfs:zio_wait_children_ready+20 () ff0001736590 zfs:zio_next_stage_async+bb () ff00017365b0 zfs:zio_nowait+11 () ff0001736660 zfs:arc_read+4e8 () ff0001736700 zfs:dbuf_read_impl+129 () ff0001736760 zfs:dbuf_read+c5 () ff0001736810 zfs:dmu_buf_hold_array_by_dnode+1c4 () ff00017368a0 zfs:dmu_buf_hold_array+74 () ff0001736930 zfs:dmu_read_uio+4d () ff00017369c0 zfs:zfs_read+15e () ff0001736a30 genunix:fop_read+69 () ff0001736af0 genunix:vn_rdwr+161 () ff0001736c70 genunix:gexec+11c () ff0001736e90 genunix:exec_common+41d () ff0001736ec0 genunix:exece+1b () ff0001736f10 unix:brand_sys_sysenter+1f2 () while running in a Gentoo Linux 2007.0 host with Intel(R) Core(TM)2 CPU 6320. 32bit OpenSolaris works fine -- Comment By: Jes Sorensen (jessorensen) Date: 2010-11-18 11:23 Message: Works for me per previous comments. If you see this again, please open a new bug in Launchpad. Thanks, Jes -- Comment By: Jes Sorensen (jessorensen) Date: 2010-08-19 12:09 Message: Hi, I didn't see any replies to my question as of June 21, are you still seeing this? I wasn't able to reproduce this in my testing. Regards, Jes -- Comment By: Jes Sorensen (jessorensen) Date: 2010-06-21 14:55 Message: Hi, I pulled down the iso image you mentioned, and it seems to boot fine for me here. I was able to run the install to a local disk image and boot it again afterwards. This is using a 64 bit guest CPU on a Fedora 12 system. What flags are you using to launch it when you see the crash? Are you running on an Intel or an AMD system and did you specify SMP by any chance? Cheers, Jes
[ kvm-Bugs-1998355 ] IO Performance
Bugs item #1998355, was opened at 2008-06-20 02:11 Message generated for change (Comment added) made by jessorensen You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=893831aid=1998355group_id=180599 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Closed Resolution: Out of Date Priority: 5 Private: No Submitted By: Joshua Rosen (bjrosen) Assigned to: Nobody/Anonymous (nobody) Summary: IO Performance Initial Comment: Is there any way of mapping a host's directory into a KVM VM similar to VMware's Shared Folder feature? I've been benchmarking the performance of NCVerilog under various VMs. The performance of KVM when using a virtual disk is excellent, in fact it's better than VMware Server or VMware Workstation, however if you use an NFS mounted host directory the performance is unspeakably awful. An NFS mounted directory under VMware Server 2.0 (Beta 2) is also slow but it's still significantly better than KVM. Using a Shared Folder with VMware Workstation eliminates the IO bottleneck, the performance there is about the same as accessing a virtual disk. The system that I did these benchmarks on is a 3GHz Core2 with 8G of RAM. VMware was running under CentOS5.1 with a 2.6.23.7 kernel. KVM is running on Fedora 9 with a 2.6.25.xx kernel. The Verilog simulation times for my test suite are as follows, Native 06:34 VM Server 2, virtual disk 08:05 VM Server 2, NFS18:37 VM Workstation, shared folder 08:14 KVM, Virtual disk 07:42 KVM, NFS38:36 -- Comment By: Jes Sorensen (jessorensen) Date: 2010-11-18 11:16 Message: Per previous comment, bug is out of date. There are a number of solutions in upstream and better performance. If you still feel this is an issue, please feel free to open a new bug in Launchpad. Thanks, Jes -- Comment By: Jes Sorensen (jessorensen) Date: 2010-08-19 12:18 Message: Hi, Did this get resolved? If so would you mind closing this bug. If I don't hear back, I will assume it is fixed and close it at some point :) Thanks, Jes -- Comment By: Joshua Rosen (bjrosen) Date: 2008-06-22 15:54 Message: Logged In: YES user_id=39829 Originator: YES I've tried the following command line, it brings up the VM but I can't configure the NIC, there is an error message about vlan 0. qemu-kvm -M pc -m 512 -smp 1 -monitor pty -net nic,macaddr=a0:1e:37:84:b1:da,model=virtio -boot c -hda /home/xen/panther Warning: vlan 0 is not connected to host network I've also tried the following, but the qemu-ifup command is missing an argument qemu-kvm -M pc -m 512 -smp 1 -monitor pty -net nic,macaddr=a0:1e:37:84:b1:da,model=virtio -net tap,script=/etc/xen/qemu-ifup -boot c -hda /home/xen/panther config qemu network with xen bridge for tap0 Incorrect number of arguments for command Usage: brctl addif bridge deviceadd interface to bridge char device redirected to /dev/pts/3 -- Comment By: Dor Laor (thekozmo) Date: 2008-06-22 08:08 Message: Logged In: YES user_id=2124464 Originator: NO Example cmdline: ./qemu/x86_64-softmmu/qemu-system-x86_64 -boot c -drive file=/images/xpbase.qcow2,if=ide,cache=on,format=qcow2,boot=on -m 384 -net nic,macaddr=a0:1e:37:84:b1:da,model=virtio -net tap,script=/etc/kvm/qemu-ifup -snapshot btw: you can use 'ps' to discover libvirt cmdline -- Comment By: Joshua Rosen (bjrosen) Date: 2008-06-22 03:18 Message: Logged In: YES user_id=39829 Originator: YES How do I use virtio-net instead of virtio-blk? I've been launching the VM using virt-manager which has no options. KVM doesn't have a MAN page so I have no idea about how to launch the VM using the CLI. Would you please give me specific step by step instructions. Thanks, -- Comment By: Joshua Rosen (bjrosen) Date: 2008-06-21 16:28 Message: Logged In: YES user_id=39829 Originator: YES How do I use virtio-net instead of virtio-blk? I've been launching the VM using virt-manager which has no options. KVM doesn't have a MAN page so I have no idea about how to launch the VM using the CLI. Would you please give me specific step by step instructions. Thanks, -- Comment By: Dor Laor (thekozmo) Date: 2008-06-21 15:45 Message: Logged In: YES user_id=2124464 Originator: NO If you don't boot from virtio-blk there is no need for this configuration. Just use virtio-net
[ kvm-Bugs-3073424 ] No picture from USB webcam (0.13-rc1)
Bugs item #3073424, was opened at 2010-09-22 17:54 Message generated for change (Tracker Item Submitted) made by willamowius You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=893831aid=3073424group_id=180599 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: intel Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Jan Willamowius (willamowius) Assigned to: Nobody/Anonymous (nobody) Summary: No picture from USB webcam (0.13-rc1) Initial Comment: I export my Linux webcam to KVM using the switches -usb -usbdevice host:046d:0929. The XP guest sees the webcam and the drivers install, but the camera only shows a black image. When I open the camera in Windows Explorer, it says 0 images and a black image, while on a real XP, it says 1 image and shows the video from the camera. Same problem with different webcams. Same cameras work fine on a native XP install. -- You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=893831aid=3073424group_id=180599 -- To unsubscribe from this list: send the line unsubscribe kvm in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
[ kvm-Bugs-3073424 ] No picture from USB webcam (0.13-rc1)
Bugs item #3073424, was opened at 2010-09-22 10:54 Message generated for change (Comment added) made by iggy_cav You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=893831aid=3073424group_id=180599 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: intel Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Jan Willamowius (willamowius) Assigned to: Nobody/Anonymous (nobody) Summary: No picture from USB webcam (0.13-rc1) Initial Comment: I export my Linux webcam to KVM using the switches -usb -usbdevice host:046d:0929. The XP guest sees the webcam and the drivers install, but the camera only shows a black image. When I open the camera in Windows Explorer, it says 0 images and a black image, while on a real XP, it says 1 image and shows the video from the camera. Same problem with different webcams. Same cameras work fine on a native XP install. -- Comment By: Brian Jackson (iggy_cav) Date: 2010-09-22 11:55 Message: You should really file this bug with upstream Qemu, but webcams are a known issue in general. Qemu only emulates a usb 1.1 controller, so you aren't really going to get decent performance from usb anyways. -- You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=893831aid=3073424group_id=180599 -- To unsubscribe from this list: send the line unsubscribe kvm in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
[ kvm-Bugs-2353510 ] Fedora 10 and F11 failures
Bugs item #2353510, was opened at 2008-11-27 13:46 Message generated for change (Comment added) made by jessorensen You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=893831aid=2353510group_id=180599 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Closed Resolution: Works For Me Priority: 9 Private: No Submitted By: Technologov (technologov) Assigned to: Nobody/Anonymous (nobody) Summary: Fedora 10 and F11 failures Initial Comment: Description: Fedora 10 fails to install on KVM. (KVM-79) The DVD version stucks at the near end setup stage, when trying to install GRUB bootloader into HDD. It didn't proceed within one hour, which indicates stucked VM. Sometimes it may stuck earlier - during init or during early setup. Live CD (32-bit) started fine on both Intel and AMD. (except top menu minor rendering bug) Guest(s): Fedora 10 64-bit Guest(s): Fedora 10 32-bit Host(s): Fedora 7 64-bit, Intel, KVM-79 Host(s): Fedora 7 64-bit, AMD, KVM-79 Command: (for DVD) qemu-kvm -cdrom /isos/linux/Fedora-10-x86_64-DVD.iso -m 512 -hda /vm/f10-64.qcow2 -boot d *and* (for LiveCD) qemu-kvm -cdrom /isos/linux/F10-i686-Live.iso -m 512 -Alexey, 27.11.2008. -- Comment By: Jes Sorensen (jessorensen) Date: 2010-09-08 15:35 Message: Tried here with recent KVM / F13 host - installing F11 works just dandy, so problem has been fixed. Closing Jes -- Comment By: Technologov (technologov) Date: 2009-06-11 16:18 Message: Not only Fedora 10, but also Fedora 11 fails in the same way. Raising bug priority. Guest(s): Fedora 10 64-bit DVD Tested on KVM-86, Intel CPU. -- Comment By: Technologov (technologov) Date: 2008-12-02 11:39 Message: I have opened similar bug against Fedora 10 bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=474116 -Alexey -- You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=893831aid=2353510group_id=180599 -- To unsubscribe from this list: send the line unsubscribe kvm in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
[ kvm-Bugs-2976863 ] 32PAE Windows guest is slow to boot with acpi on shadow
Bugs item #2976863, was opened at 2010-03-26 14:44 Message generated for change (Comment added) made by haoxudong You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=893831aid=2976863group_id=180599 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Closed Resolution: Fixed Priority: 5 Private: No Submitted By: Xudong Hao (haoxudong) Assigned to: Nobody/Anonymous (nobody) Summary: 32PAE Windows guest is slow to boot with acpi on shadow Initial Comment: Environment: Host OS (ia32/ia32e/IA64):32e and pae Guest OS (ia32/ia32e/IA64): ia32pae Guest OS Type (Linux/Windows): windows(xp, vista, and Win7) kvm.git Commit: b8ed93d4.. qemu-kvm Commit: aa4df134.. Host Kernel Version:2.6.34-rc2 Hardware: Stoakely Bug detailed description: -- when we boot a 32pae Windows guest with acpi on, the guest will become bule screen of death. Reproduce steps: 1. boot into host, loal kvm and kvm_intel module 2. use following command to boot a guest: qemu-system-x86_64 -m 256 -net nic,macaddr=00:16:3e:27:b6:8a,model=rtl8139 -net tap,script=/etc/kvm/qemu-ifup -hda /share/xvs/var/Windows.img 3. the guest will become bule screen of death. -- Comment By: Xudong Hao (haoxudong) Date: 2010-09-06 09:10 Message: This bug is fixed on kvm commit: 77a28e3547f8b041a6e940f5ec60296c091fd075. Close this bug as fixed. -- Comment By: Xudong Hao (haoxudong) Date: 2010-05-19 11:23 Message: Change bug title discription since bug behave changed. -- Comment By: Xudong Hao (haoxudong) Date: 2010-05-18 11:11 Message: This problem you are experiencing is only reproducible on 32-bit host, 64-bit host is OK, correct? No, on 64-bit host, 32pae guest get this booting slow problem with acpi on and shandow mode too. Mtosatti, What platform(CPU) do you use? -- Comment By: Marcelo Tosatti (mtosatti) Date: 2010-04-22 00:51 Message: Now BSOD issue got out on kvm commit: bc8a97a218d0d2367d125db3e11ec45bb0fa0a3f-a1b705841caa33fca0b95928505c01d5105b706f. Please save the BSOD message. However, boot a 32-bit XP with acpi on will cost about 9 minutes, did you meet similar issue on your side? No. It boots similarly fast as with 64-bit host. This problem you are experiencing is only reproducible on 32-bit host, 64-bit host is OK, correct? -- Comment By: Xudong Hao (haoxudong) Date: 2010-04-20 10:35 Message: Now BSOD issue got out on kvm commit: bc8a97a218d0d2367d125db3e11ec45bb0fa0a3f-a1b705841caa33fca0b95928505c01d5105b706f. However, boot a 32-bit XP with acpi on will cost about 9 minutes, did you meet similar issue on your side? -- Comment By: Marcelo Tosatti (mtosatti) Date: 2010-04-15 04:51 Message: 1) 32-bit WinXP qemu-system-x86_64 -drive file=/root/winxp-32-good.qcow2,cache=writeback -m 2000 -vnc :1 -usbdevice tablet -net nic,model=e1000 -net tap,script=/root/ifup 2) acpi on Control panes shows ACPI multiprocessor PC 3) shadow mode [r...@localhost ~]# cat /sys/module/kvm_intel/parameters/ept N host: Linux localhost.localdomain 2.6.34-rc3 #101 SMP Mon Apr 12 18:18:39 BRT 2010 i686 i686 i386 GNU/Linux Can you send a screenshot of the hang? -- Comment By: Xudong Hao (haoxudong) Date: 2010-04-13 13:45 Message: Motsatti, I checked again, guest still booting stop at the loading scroll bar. Let find what difference between ours. Can you check if your reproduce steps: 1) 32-bit WinXP 1) acpi on 2) shadow mode -- Comment By: Marcelo Tosatti (mtosatti) Date: 2010-04-13 06:28 Message: Xudong, Tested WinXP.32 and WinVista.32 on 32-bit host, both work fine. -- Comment By: Xudong Hao (haoxudong) Date: 2010-04-12 09:56 Message: Latest commit: 069c71e7a5e5f968099ca551f68e5dfe5a3f71bc qemu: 5c781061a45abe1855ad0a95d834336da574703c Windows guest did not blue screen with latest KVM commit, but guest hang at the loading scroll bar. This issue only happen on shadow mode. Windows guest can boot up with EPT mode. -- Comment By: Marcelo Tosatti (mtosatti) Date: 2010-04-06 02:50 Message: Xudong, Can you reproduce the problem with latest git repositories? The BSOD screenshot is truncated, the error number is not present
[ kvm-Bugs-3056363 ] cpu0 unhandled wrmsr:
Bugs item #3056363, was opened at 2010-08-31 01:56 Message generated for change (Settings changed) made by jessorensen You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=893831aid=3056363group_id=180599 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: kernel Group: None Status: Closed Resolution: Fixed Priority: 5 Private: No Submitted By: Ravi Ganapa (rganapa) Assigned to: Nobody/Anonymous (nobody) Summary: cpu0 unhandled wrmsr: Initial Comment: I see the following messages, loaded kvm module (kvm-kmod-2.6.35) kvm: 15442: cpu0 unhandled wrmsr: 0x198 data 0 kvm: 15442: cpu1 unhandled wrmsr: 0x198 data 0 kvm: 15447: cpu0 unhandled wrmsr: 0x198 data 0 kvm: 15447: cpu1 unhandled wrmsr: 0x198 data 0 kvm: 15451: cpu0 unhandled wrmsr: 0x198 data 0 kvm: 15451: cpu1 unhandled wrmsr: 0x198 data 0 kvm: 15920: cpu0 unhandled wrmsr: 0x198 data 0 kvm: 15920: cpu1 unhandled wrmsr: 0x198 data 0 Running QEMU emulator version 0.13.50 (qemu-kvm-devel), both kvm and qemu-kvm are from git clone on Aug 26th 2010 -- Comment By: Jes Sorensen (jessorensen) Date: 2010-09-02 13:27 Message: Fixed in upstream commit: c94c3ba901f87115cf574044e7faabfb1d0251fb For future reference, please do not open any more KVM bugs in this bug-tracker, use launchpad instead. Cheers, Jes -- You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=893831aid=3056363group_id=180599 -- To unsubscribe from this list: send the line unsubscribe kvm in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
[ kvm-Bugs-2005957 ] TAP networking stalls on large file transfers
Bugs item #2005957, was opened at 2008-06-29 17:12 Message generated for change (Settings changed) made by jessorensen You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=893831aid=2005957group_id=180599 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: qemu Group: None Status: Closed Resolution: Out of Date Priority: 5 Private: No Submitted By: Andrew Zabolotny (andyz) Assigned to: Nobody/Anonymous (nobody) Summary: TAP networking stalls on large file transfers Initial Comment: System: Fedora 9 KVM version: tried 65 and 70, both exhibit the same behaviour When using TAP networking if I copy a large file from host to guest OS, I get extremely low performance (under 1 megabyte/s) and sometimes file transfer stalls. If I run tcpdump in guest OS (even with a bogus filter - e.g. tcpdump -nn -i eth0 host 1.2.3.4) the stalled connection suddenly come alive. If I run repeatedly tcpdump/press Ctrl+C and so on, the file transfer visually goes much faster. I found a old thread about the same bug in QEMU: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=290569 The patch proposed there was applied in QEMU 0.7.3, but when I looked into QEMU 0.9.1 sources - it is not there, so it seems it was removed for some reason. However, if I run the same virtual machine with QEMU, I get stable performance with about 8-9 megabytes per second flowing both ways (from host to guest and from guest to host). I tried to apply the patch on KVM 70, but it does not make any difference :-( The guest OS is Ubuntu 8.04 but I guess that does not matter. I will be glad to cooperate to find/fix the bug but for now I'm out of ideas :-( -- Comment By: Jes Sorensen (jessorensen) Date: 2010-08-30 08:57 Message: Andy, Thanks for the reply, I'll close this as out of date. If someone else hits this problem they can go ahead and open a new bug in launchpad. Cheers, Jes -- Comment By: Andrew Zabolotny (andyz) Date: 2010-08-27 23:16 Message: Well, I haven't used rtl8139 for a long time, so I almost forgot about this problem. I think the report can be closed, as there are plenty of alternatives which will work for the average user (including virtio which I use now). If somebody cares explicitly about rtl8139, he can reopen this bug later. -- Comment By: Jes Sorensen (jessorensen) Date: 2010-08-19 12:22 Message: Hi, Trying to catch up on old bugs and clean up the queue. Are you still seeing this problem? If not would you mind closing the bug? For even more performance, you should try out virtio-net. Cheers, Jes -- Comment By: Andrew Zabolotny (andyz) Date: 2008-08-09 10:54 Message: Logged In: YES user_id=1815 Originator: YES Indeed, setting model=pcnet also works (same guest OS - Ubuntu 8.04). But still I like e1000 more now :-)) -- Comment By: Jerome Ibanes (jibanes) Date: 2008-08-09 08:04 Message: Logged In: YES user_id=2174347 Originator: NO It *seems* that a 'pcnet'-type doesn't shutdown the network emulation, can you repro? (I seem to have issues under Plan 9 with the e1000 nic). Sincerely, Jerome -- Comment By: Jerome Ibanes (jibanes) Date: 2008-08-09 07:51 Message: Logged In: YES user_id=2174347 Originator: NO I've observed the same behavior with kvm-72 and 2.6.26.2 on intel, the guest is a (very) up to date plan 9 operating system. I have tried ne2k_pci AND rtl8139 emulation with tap, still, after performing some file transfers I seem to lose network connectivity. Please note that I do not need to stress the network card significantly to lose network connectivity, transferring a file of roughly 20MB appears to be sufficient. I haven't tried a e1000 gigE nic at this time, let me know if other options or workaround are available? Thanks, Jerome -- Comment By: Andrew Zabolotny (andyz) Date: 2008-06-29 18:09 Message: Logged In: YES user_id=1815 Originator: YES Update: I was advised on irc to try e1000 network card emulation instead, and with it I get very good results - 32 megabytes per second and more. So the bug occurs only with rtl8139 emulation, perhaps because of bandwidth limitation (packets aren't read quick enough from the TAP handle)? -- You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=893831aid=2005957group_id=180599 -- To unsubscribe from this list: send the line
[ kvm-Bugs-3055533 ] guest clock runs 2 times faster than the host clock
Bugs item #3055533, was opened at 2010-08-29 19:07 Message generated for change (Comment added) made by jessorensen You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=893831aid=3055533group_id=180599 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: intel Group: None Status: Closed Resolution: Invalid Priority: 7 Private: No Submitted By: Bhasker C V (bcv) Assigned to: Nobody/Anonymous (nobody) Summary: guest clock runs 2 times faster than the host clock Initial Comment: Host: processor: Intel(R) Core(TM)2 Quad CPU @ 2.66GHz OS : debian squeeze Qemu : qemu-kvm-88 Kernel : Linux bcv 2.6.35.3 #1 SMP PREEMPT Mon Aug 23 17:55:19 BST 2010 x86_64 GNU/Linux Guest: processsor: Intel core2duo smp 2 OS: SUSE linux enterprise 10 64bit so running a 64 bit OS on 64 bit debian host. The clock runs double fast than the host OS. This results in guest gaining time and going ahead the host -- Comment By: Jes Sorensen (jessorensen) Date: 2010-08-30 12:03 Message: kvm-88 is over a year old as was also reported by mjtsf. Please check against a recent kvm release and open a new bug in https://bugs.launchpad.net/qemu/ Closing as invalid. It's pointless reporting bugs against such old releases. Jes -- Comment By: Bhasker C V (bcv) Date: 2010-08-29 22:55 Message: A quick workaround for this solution would be to use the following in the kernel command line along with using -clock dynticks append this notsc divider=10 clock=pmtmr the clock= option may change for various distributions and can be lookedup from http://kb.vmware.com/selfservice/microsites/search.do?language=en_UScmd=displayKCexternalId=1006427 Albeit this fairly makes the clock not to go haywire and keep counting fast, there is still a small gain which can be well managed using ntp or periodic rdate updates -- Comment By: Michael Tokarev (mjtsf) Date: 2010-08-29 20:45 Message: Come on, kvm-88 is ancient unsupported development snapshot. It isnt' even an alpha version. Please try current code (at least qemu-kvm-0.12.4 as available on backports.org) and file a new bugreport if the problem is still here. And if the issue _is_ present in real version, please file a bug in launchpad.net against qemu project, not here. This bugtracker is dead. Thanks. -- Comment By: Bhasker C V (bcv) Date: 2010-08-29 19:25 Message: Running a 32 bit OS instead of the 64 bit OS maintains time properly. It is just that running the 64 bit OS inside this qemu-kvm makes the guest to gain time. -- You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=893831aid=3055533group_id=180599 -- To unsubscribe from this list: send the line unsubscribe kvm in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
[ kvm-Bugs-3056363 ] cpu0 unhandled wrmsr:
Bugs item #3056363, was opened at 2010-08-30 23:56 Message generated for change (Tracker Item Submitted) made by rganapa You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=893831aid=3056363group_id=180599 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: kernel Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Ravi Ganapa (rganapa) Assigned to: Nobody/Anonymous (nobody) Summary: cpu0 unhandled wrmsr: Initial Comment: I see the following messages, loaded kvm module (kvm-kmod-2.6.35) kvm: 15442: cpu0 unhandled wrmsr: 0x198 data 0 kvm: 15442: cpu1 unhandled wrmsr: 0x198 data 0 kvm: 15447: cpu0 unhandled wrmsr: 0x198 data 0 kvm: 15447: cpu1 unhandled wrmsr: 0x198 data 0 kvm: 15451: cpu0 unhandled wrmsr: 0x198 data 0 kvm: 15451: cpu1 unhandled wrmsr: 0x198 data 0 kvm: 15920: cpu0 unhandled wrmsr: 0x198 data 0 kvm: 15920: cpu1 unhandled wrmsr: 0x198 data 0 Running QEMU emulator version 0.13.50 (qemu-kvm-devel), both kvm and qemu-kvm are from git clone on Aug 26th 2010 -- You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=893831aid=3056363group_id=180599 -- To unsubscribe from this list: send the line unsubscribe kvm in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
[ kvm-Bugs-3055533 ] guest clock runs 2 times faster than the host clock
Bugs item #3055533, was opened at 2010-08-29 22:37 Message generated for change (Tracker Item Submitted) made by bcv You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=893831aid=3055533group_id=180599 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: intel Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Bhasker C V (bcv) Assigned to: Nobody/Anonymous (nobody) Summary: guest clock runs 2 times faster than the host clock Initial Comment: Host: processor: Intel(R) Core(TM)2 Quad CPU @ 2.66GHz OS : debian squeeze Qemu : qemu-kvm-88 Kernel : Linux bcv 2.6.35.3 #1 SMP PREEMPT Mon Aug 23 17:55:19 BST 2010 x86_64 GNU/Linux Guest: processsor: Intel core2duo smp 2 OS: SUSE linux enterprise 10 64bit so running a 64 bit OS on 64 bit debian host. The clock runs double fast than the host OS. This results in guest gaining time and going ahead the host -- You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=893831aid=3055533group_id=180599 -- To unsubscribe from this list: send the line unsubscribe kvm in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
[ kvm-Bugs-3055533 ] guest clock runs 2 times faster than the host clock
Bugs item #3055533, was opened at 2010-08-29 22:37 Message generated for change (Settings changed) made by bcv You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=893831aid=3055533group_id=180599 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: intel Group: None Status: Open Resolution: None Priority: 7 Private: No Submitted By: Bhasker C V (bcv) Assigned to: Nobody/Anonymous (nobody) Summary: guest clock runs 2 times faster than the host clock Initial Comment: Host: processor: Intel(R) Core(TM)2 Quad CPU @ 2.66GHz OS : debian squeeze Qemu : qemu-kvm-88 Kernel : Linux bcv 2.6.35.3 #1 SMP PREEMPT Mon Aug 23 17:55:19 BST 2010 x86_64 GNU/Linux Guest: processsor: Intel core2duo smp 2 OS: SUSE linux enterprise 10 64bit so running a 64 bit OS on 64 bit debian host. The clock runs double fast than the host OS. This results in guest gaining time and going ahead the host -- You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=893831aid=3055533group_id=180599 -- To unsubscribe from this list: send the line unsubscribe kvm in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
