On 10/15/2009 01:42 PM, Asdo wrote:
Vadim Rozenfeld wrote:
On 10/14/2009 07:52 PM, Asdo wrote:
...
So I tried adding another drive, a virtio one, (a new 100MB file at
host side) to the virtual machine and rebooting.
A first problem is that Windows does not detect the new device upon
boot or Add Hardware scan.
Check PCI devices with "info pci". You must have "SCSI controller:
PCI device 1af4:1001" device reported.
It's not there. Does this make it a KVM bug?
Looks like virtio-blk device wasn't initialized. Otherwise I cannot
explain why 0x1100 device is here.
Try to start block device without "index=1"
Anyway, if you can, please send "info pci" output from QEMU monitor console.
Thank you,
Vadim.
I'm attaching the PCI32.EXE output at the bottom of this email
BTW I would probably be able to switch to virtio anyway on this
installation of Windows 2003, if I knew the way to insert the viostor
driver into the windows boot image (windows's initrd), because if I
set the first disk hda as virtio then kvm really makes it virtio (so
maybe it's a configuration with one IDE and one virtio that does not
work in KVM) and Windows bluescreens at boot. However I don't know how
to insert the viostor driver in the windows boot image. Any suggestions?
Here is the kvm commandline (it's complex because it comes from
libvirt):
/usr/local/kvm/bin/qemu-system-x86_64 -S -M pc -m 4096-smp 4 -name
winserv2 -uuid xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx -monitor pty
-boot c -drive
file=/virtual_machines/kvm/nfsimport/winserv2.raw,if=ide,index=0,boot=on
-drive
file=/virtual_machines/kvm/nfsimport/zerofile,if=virtio,index=1 -net
nic,macaddr=xx:xx:xx:xx:xx:xx,vlan=0,model=virtio -net
tap,fd=25,vlan=0 -serial none -parallel none -usb -vnc 127.0.0.1:4
Craig Hart's PCI+AGP bus sniffer, Version 1.6, freeware made in
1996-2005.
Searching for Devices using CFG Mechanism 1 [OS: Win 2003 Service Pack 1]
Bus 0 (PCI), Device Number 0, Device Function 0
Vendor 8086h Intel Corporation
Device 1237h 82441FX 440FX (Natoma) System Controller Rev 2 (SU053)
Command 0000h (Bus Access Disabled!!)
Status 0000h
Revision 02h, Header Type 00h, Bus Latency Timer 00h
Self test 00h (Self test not supported)
PCI Class Bridge, type PCI to HOST
Subsystem ID 11001AF4h Unknown
Subsystem Vendor 1AF4h Unknown
Bus 0 (PCI), Device Number 1, Device Function 0
Vendor 8086h Intel Corporation
Device 7000h 82371SB PIIX3 ISA Bridge
Command 0007h (I/O Access, Memory Access, BusMaster)
Status 0200h (Medium Timing)
Revision 00h, Header Type 80h, Bus Latency Timer 00h
Self test 00h (Self test not supported)
PCI Class Bridge, type PCI to ISA
Subsystem ID 11001AF4h Unknown
Subsystem Vendor 1AF4h Unknown
Bus 0 (PCI), Device Number 1, Device Function 1
Vendor 8086h Intel Corporation
Device 7010h 82371SB PIIX3 EIDE Controller
Command 0007h (I/O Access, Memory Access, BusMaster)
Status 0280h (Supports Back-To-Back Trans., Medium Timing)
Revision 00h, Header Type 00h, Bus Latency Timer 00h
Self test 00h (Self test not supported)
PCI Class Storage, type IDE (ATA)
PCI EIDE Controller Features :
BusMaster EIDE is supported
Primary Channel is at I/O Port 01F0h and IRQ 14
Secondary Channel is at I/O Port 0170h and IRQ 15
Subsystem ID 11001AF4h Unknown
Subsystem Vendor 1AF4h Unknown
Address 4 is an I/O Port : 0000C000h
Bus 0 (PCI), Device Number 1, Device Function 2
Vendor 8086h Intel Corporation
Device 7020h 82371SB PIIX3 USB Controller Rev 1 (SU093)
Command 0007h (I/O Access, Memory Access, BusMaster)
Status 0000h
Revision 01h, Header Type 00h, Bus Latency Timer 00h
Self test 00h (Self test not supported)
PCI Class Serial, type USB (UHCI)
Subsystem ID 11001AF4h Unknown
Subsystem Vendor 1AF4h Unknown
Address 4 is an I/O Port : 0000C020h
System IRQ 11, INT# D
Bus 0 (PCI), Device Number 1, Device Function 3
Vendor 8086h Intel Corporation
Device 7113h 82371MB PIIX4M Power Management Controller
Command 0000h (Bus Access Disabled!!)
Status 0280h (Supports Back-To-Back Trans., Medium Timing)
Revision 03h, Header Type 00h, Bus Latency Timer 00h
Self test 00h (Self test not supported)
PCI Class Bridge, type PCI to Other
Subsystem ID 11001AF4h Unknown
Subsystem Vendor 1AF4h Unknown
System IRQ 9, INT# A
Bus 0 (PCI), Device Number 2, Device Function 0
Vendor 1013h Cirrus Logic
Device 00B8h CL-GD5446 PCI
Command 0007h (I/O Access, Memory Access, BusMaster)
Status 0000h
Revision 00h, Header Type 00h, Bus Latency Timer 00h
Self test 00h (Self test not supported)
PCI Class Display, type VGA
Subsystem ID 11001AF4h Unknown
Subsystem Vendor 1AF4h Unknown
Address 0 is a Memory Address (anywhere in 0-4Gb, Prefetchable) :
F0000000h
Address 1 is a Memory Address (anywhere in 0-4Gb) : F2000000h
Bus 0 (PCI), Device Number 3, Device Function 0
Vendor 1AF4h Unknown
Device 1000h Unknown
Command 0007h (I/O Access, Memory Access, BusMaster)
Status 0000h
Revision 00h, Header Type 00h, Bus Latency Timer 00h
Self test 00h (Self test not supported)
PCI Class Network, type Ethernet
Subsystem ID 00011AF4h Unknown
Subsystem Vendor 1AF4h Unknown
Address 0 is an I/O Port : 0000C040h
System IRQ 10, INT# A
Bus 0 (PCI), Device Number 4, Device Function 0
Vendor 1AF4h Unknown
Device 1002h Unknown
Command 0001h (I/O Access)
Status 0000h
Revision 00h, Header Type 00h, Bus Latency Timer 00h
Self test 00h (Self test not supported)
PCI Class Memory, type RAM
Subsystem ID 00051AF4h Unknown
Subsystem Vendor 1AF4h Unknown
Address 0 is an I/O Port : 0000C060h
System IRQ 11, INT# A
IRQ Summary: IRQs 9,10,11,14,15 are used by PCI devices
Shared IRQs: IRQ 11 is shared by 2 PCI Devices
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
