KVM-58 -- existing VM just hangs with black screen

KVM-58 -- existing VM just hangs with black screen

[Richard W.M. Jones]

[-- Attachment #1.1: Type: text/plain, Size: 967 bytes --]

I've just got an upgrade to KVM-58 as part of the latest Fedora.

Unfortunately my existing VM (a Windows 2008 Server instance) no longer 
boots.  In fact it hardly gets anywhere at all.  Immediately after 
running qemu-kvm, I just get a black screen (no BIOS/boot messages at 
all) and using 100% of CPU.

No kernel messages.  'strace' indicates that qemu-kvm is doing a lot of 
stuff (issuing lots of ioctl, gettimeofday, etc.).

I can get to the qemu monitor.  Are there any useful commands to issue?

'info blockstats' shows a single 512 byte read from ide-hd0, presumably 
it has read the boot sector but for some reason cannot boot from it.

Any ideas on what I can do to debug this further?

Rich.

-- 
Emerging Technologies, Red Hat - http://et.redhat.com/~rjones/
Registered Address: Red Hat UK Ltd, Amberley Place, 107-111 Peascod
Street, Windsor, Berkshire, SL4 1TE, United Kingdom.  Registered in
England and Wales under Company Registration No. 03798903

[-- Attachment #1.2: S/MIME Cryptographic Signature --]
[-- Type: application/x-pkcs7-signature, Size: 3237 bytes --]

[-- Attachment #2: Type: text/plain, Size: 228 bytes --]

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/

[-- Attachment #3: Type: text/plain, Size: 186 bytes --]

_______________________________________________
kvm-devel mailing list
kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
https://lists.sourceforge.net/lists/listinfo/kvm-devel

Re: KVM-58 -- existing VM just hangs with black screen

[Avi Kivity]

Richard W.M. Jones wrote:
> I've just got an upgrade to KVM-58 as part of the latest Fedora.
>
> Unfortunately my existing VM (a Windows 2008 Server instance) no 
> longer boots.  In fact it hardly gets anywhere at all.  Immediately 
> after running qemu-kvm, I just get a black screen (no BIOS/boot 
> messages at all) and using 100% of CPU.
>
> No kernel messages.  'strace' indicates that qemu-kvm is doing a lot 
> of stuff (issuing lots of ioctl, gettimeofday, etc.).
>
> I can get to the qemu monitor.  Are there any useful commands to issue?
>
> 'info blockstats' shows a single 512 byte read from ide-hd0, 
> presumably it has read the boot sector but for some reason cannot boot 
> from it.
>
> Any ideas on what I can do to debug this further?

Can you identify which version of kvm introduced the regression?

-- 
error compiling committee.c: too many arguments to function


-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/

Re: KVM-58 -- existing VM just hangs with black screen

[Richard W.M. Jones]

[-- Attachment #1.1: Type: text/plain, Size: 1364 bytes --]

Avi Kivity wrote:
> Richard W.M. Jones wrote:
>> I've just got an upgrade to KVM-58 as part of the latest Fedora.
>>
>> Unfortunately my existing VM (a Windows 2008 Server instance) no 
>> longer boots.  In fact it hardly gets anywhere at all.  Immediately 
>> after running qemu-kvm, I just get a black screen (no BIOS/boot 
>> messages at all) and using 100% of CPU.
>>
>> No kernel messages.  'strace' indicates that qemu-kvm is doing a lot 
>> of stuff (issuing lots of ioctl, gettimeofday, etc.).
>>
>> I can get to the qemu monitor.  Are there any useful commands to issue?
>>
>> 'info blockstats' shows a single 512 byte read from ide-hd0, 
>> presumably it has read the boot sector but for some reason cannot boot 
>> from it.
>>
>> Any ideas on what I can do to debug this further?
> 
> Can you identify which version of kvm introduced the regression?

kvm-56 for Fedora (from 
http://koji.fedoraproject.org/koji/packageinfo?packageID=2261) *works*.

I will try to build an RPM based on KVM-57 and see what that does, but 
at the moment it seems to be somewhere between KVM-56 and now.

Rich.

-- 
Emerging Technologies, Red Hat - http://et.redhat.com/~rjones/
Registered Address: Red Hat UK Ltd, Amberley Place, 107-111 Peascod
Street, Windsor, Berkshire, SL4 1TE, United Kingdom.  Registered in
England and Wales under Company Registration No. 03798903

[-- Attachment #1.2: S/MIME Cryptographic Signature --]
[-- Type: application/x-pkcs7-signature, Size: 3237 bytes --]

[-- Attachment #2: Type: text/plain, Size: 228 bytes --]

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/

[-- Attachment #3: Type: text/plain, Size: 186 bytes --]

_______________________________________________
kvm-devel mailing list
kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
https://lists.sourceforge.net/lists/listinfo/kvm-devel

Re: KVM-58 -- existing VM just hangs with black screen

[Richard W.M. Jones]

[-- Attachment #1.1.1: Type: text/plain, Size: 1396 bytes --]

Dan Kenigsberg wrote:
> On Wed, Jan 02, 2008 at 12:08:12PM +0000, Richard W.M. Jones wrote:
>> I've just got an upgrade to KVM-58 as part of the latest Fedora.
>>
>> Unfortunately my existing VM (a Windows 2008 Server instance) no longer 
>> boots.  In fact it hardly gets anywhere at all.  Immediately after running 
>> qemu-kvm, I just get a black screen (no BIOS/boot messages at all) and 
>> using 100% of CPU.
>>
>> No kernel messages.  'strace' indicates that qemu-kvm is doing a lot of 
>> stuff (issuing lots of ioctl, gettimeofday, etc.).
>>
>> I can get to the qemu monitor.  Are there any useful commands to issue?
>>
>> 'info blockstats' shows a single 512 byte read from ide-hd0, presumably it 
>> has read the boot sector but for some reason cannot boot from it.
>>
>> Any ideas on what I can do to debug this further?
> 
> Try -clock unix. I'm not sure about the dyntick code.

No difference.

BTW, I'm fairly sure this isn't anything to do with the Windows guest, 
since it just doesn't get that far.  It seems more likely to be down to 
the strange Intel development platform that I'm using.  See attachments.

Rich.

-- 
Emerging Technologies, Red Hat - http://et.redhat.com/~rjones/
Registered Address: Red Hat UK Ltd, Amberley Place, 107-111 Peascod
Street, Windsor, Berkshire, SL4 1TE, United Kingdom.  Registered in
England and Wales under Company Registration No. 03798903

[-- Attachment #1.1.2: cpuinfo.txt --]
[-- Type: text/plain, Size: 1338 bytes --]

processor	: 0
vendor_id	: GenuineIntel
cpu family	: 6
model		: 15
model name	: Intel(R) Core(TM)2 Duo CPU     E6850  @ 3.00GHz
stepping	: 11
cpu MHz		: 2000.000
cache size	: 4096 KB
physical id	: 0
siblings	: 2
core id		: 0
cpu cores	: 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 monitor ds_cpl vmx smx est tm2 ssse3 cx16 xtpr lahf_lm
bogomips	: 5992.17
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 Duo CPU     E6850  @ 3.00GHz
stepping	: 11
cpu MHz		: 2000.000
cache size	: 4096 KB
physical id	: 0
siblings	: 2
core id		: 1
cpu cores	: 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 monitor ds_cpl vmx smx est tm2 ssse3 cx16 xtpr lahf_lm
bogomips	: 5984.96
clflush size	: 64
cache_alignment	: 64
address sizes	: 36 bits physical, 48 bits virtual
power management:


[-- Attachment #1.1.3: dmidecode.txt --]
[-- Type: text/plain, Size: 14511 bytes --]

# dmidecode 2.9
SMBIOS 2.4 present.
48 structures occupying 2067 bytes.
Table at 0x000FD160.

Handle 0x0000, DMI type 0, 24 bytes
BIOS Information
	Vendor: American Megatrends Inc.
	Version: SDBLI944.86P
	Release Date: 05/08/2007
	Address: 0xF0000
	Runtime Size: 64 kB
	ROM Size: 1024 kB
	Characteristics:
		ISA is supported
		PCI is supported
		PNP is supported
		APM is supported
		BIOS is upgradeable
		BIOS shadowing is allowed
		ESCD support is available
		Boot from CD is supported
		Selectable boot is supported
		BIOS ROM is socketed
		EDD is supported
		5.25"/1.2 MB floppy services are supported (int 13h)
		3.5"/720 KB floppy services are supported (int 13h)
		3.5"/2.88 MB floppy services are supported (int 13h)
		Print screen service is supported (int 5h)
		8042 keyboard services are supported (int 9h)
		Serial services are supported (int 14h)
		Printer services are supported (int 17h)
		CGA/mono video services are supported (int 10h)
		ACPI is supported
		USB legacy is supported
		LS-120 boot is supported
		ATAPI Zip drive boot is supported
		BIOS boot specification is supported
		Targeted content distribution is supported
	BIOS Revision: 8.14

Handle 0x0001, DMI type 1, 27 bytes
System Information
	Manufacturer: To Be Filled By O.E.M.
	Product Name: To Be Filled By O.E.M.
	Version: To Be Filled By O.E.M.
	Serial Number: To Be Filled By O.E.M.
	UUID: 35363738-393A-3B3C-3D3E-3F4041424344
	Wake-up Type: Power Switch
	SKU Number: To Be Filled By O.E.M.
	Family: To Be Filled By O.E.M.

Handle 0x0002, DMI type 2, 15 bytes
Base Board Information
	Manufacturer: To be filled by O.E.M.
	Product Name: To be filled by O.E.M.
	Version: To be filled by O.E.M.
	Serial Number: To be filled by O.E.M.
	Asset Tag: To Be Filled By O.E.M.
	Features:
		Board is a hosting board
		Board is replaceable
	Location In Chassis: To Be Filled By O.E.M.
	Chassis Handle: 0x0003
	Type: Motherboard
	Contained Object Handles: 0

Handle 0x0003, DMI type 3, 21 bytes
Chassis Information
	Manufacturer: To Be Filled By O.E.M.
	Type: Desktop
	Lock: Not Present
	Version: To Be Filled By O.E.M.
	Serial Number: To Be Filled By O.E.M.
	Asset Tag: To Be Filled By O.E.M.
	Boot-up State: Safe
	Power Supply State: Safe
	Thermal State: Safe
	Security Status: None
	OEM Information: 0x00000000
	Height: Unspecified
	Number Of Power Cords: 1
	Contained Elements: 0

Handle 0x0004, DMI type 4, 35 bytes
Processor Information
	Socket Designation: CPU 1
	Type: Central Processor
	Family: <OUT OF SPEC>
	Manufacturer: Intel            
	ID: FB 60 00 00 FF FB EB BF
	Version: Intel(R) Core(TM)2 Duo CPU     E6850  @ 3.00GHz     
	Voltage: 1.3 V
	External Clock: 333 MHz
	Max Speed: 3000 MHz
	Current Speed: 2999 MHz
	Status: Populated, Enabled
	Upgrade: Other
	L1 Cache Handle: 0x0005
	L2 Cache Handle: 0x0006
	L3 Cache Handle: 0x0007
	Serial Number: To Be Filled By O.E.M.
	Asset Tag: To Be Filled By O.E.M.
	Part Number: To Be Filled By O.E.M.

Handle 0x0005, DMI type 7, 19 bytes
Cache Information
	Socket Designation: L1-Cache
	Configuration: Enabled, Not Socketed, Level 1
	Operational Mode: Write Back
	Location: Internal
	Installed Size: 64 KB
	Maximum Size: 64 KB
	Supported SRAM Types:
		Other
	Installed SRAM Type: Other
	Speed: Unknown
	Error Correction Type: Parity
	System Type: Data
	Associativity: 8-way Set-associative

Handle 0x0006, DMI type 7, 19 bytes
Cache Information
	Socket Designation: L2-Cache
	Configuration: Enabled, Not Socketed, Level 2
	Operational Mode: Write Back
	Location: Internal
	Installed Size: 4096 KB
	Maximum Size: 4096 KB
	Supported SRAM Types:
		Other
	Installed SRAM Type: Other
	Speed: Unknown
	Error Correction Type: Single-bit ECC
	System Type: Instruction
	Associativity: 8-way Set-associative

Handle 0x0007, DMI type 7, 19 bytes
Cache Information
	Socket Designation: L3-Cache
	Configuration: Disabled, Not Socketed, Level 3
	Operational Mode: Unknown
	Location: Internal
	Installed Size: 0 KB
	Maximum Size: 0 KB
	Supported SRAM Types:
		Unknown
	Installed SRAM Type: Unknown
	Speed: Unknown
	Error Correction Type: Unknown
	System Type: Unknown
	Associativity: Unknown

Handle 0x0008, DMI type 5, 24 bytes
Memory Controller Information
	Error Detecting Method: 64-bit ECC
	Error Correcting Capabilities:
		None
	Supported Interleave: One-way Interleave
	Current Interleave: One-way Interleave
	Maximum Memory Module Size: 4096 MB
	Maximum Total Memory Size: 16384 MB
	Supported Speeds:
		Other
	Supported Memory Types:
		DIMM
		SDRAM
	Memory Module Voltage: 3.3 V
	Associated Memory Slots: 4
		0x0009
		0x000A
		0x000B
		0x000C
	Enabled Error Correcting Capabilities:
		None

Handle 0x0009, DMI type 6, 12 bytes
Memory Module Information
	Socket Designation: DIMM0
	Bank Connections: 0 1
	Current Speed: Unknown
	Type: DIMM SDRAM
	Installed Size: 1024 MB (Double-bank Connection)
	Enabled Size: 1024 MB (Double-bank Connection)
	Error Status: OK

Handle 0x000A, DMI type 6, 12 bytes
Memory Module Information
	Socket Designation: DIMM1
	Bank Connections: 2 3
	Current Speed: Unknown
	Type: DIMM SDRAM
	Installed Size: Not Installed
	Enabled Size: Not Installed
	Error Status: OK

Handle 0x000B, DMI type 6, 12 bytes
Memory Module Information
	Socket Designation: DIMM2
	Bank Connections: 4 5
	Current Speed: Unknown
	Type: DIMM SDRAM
	Installed Size: 1024 MB (Double-bank Connection)
	Enabled Size: 1024 MB (Double-bank Connection)
	Error Status: OK

Handle 0x000C, DMI type 6, 12 bytes
Memory Module Information
	Socket Designation: DIMM3
	Bank Connections: 6 7
	Current Speed: Unknown
	Type: DIMM SDRAM
	Installed Size: Not Installed
	Enabled Size: Not Installed
	Error Status: OK

Handle 0x000D, DMI type 13, 22 bytes
BIOS Language Information
	Installable Languages: 1
		en|US|iso8859-1
	Currently Installed Language: en|US|iso8859-1

Handle 0x000E, DMI type 15, 35 bytes
System Event Log
	Area Length: 4 bytes
	Header Start Offset: 0x0000
	Header Length: 2 bytes
	Data Start Offset: 0x0002
	Access Method: Indexed I/O, one 16-bit index port, one 8-bit data port
	Access Address: Index 0x046A, Data 0x046C
	Status: Invalid, Not Full
	Change Token: 0x00000000
	Header Format: No Header
	Supported Log Type Descriptors: 6
	Descriptor 1: End of log
	Data Format 1: OEM-specific
	Descriptor 2: End of log
	Data Format 2: OEM-specific
	Descriptor 3: End of log
	Data Format 3: OEM-specific
	Descriptor 4: End of log
	Data Format 4: OEM-specific
	Descriptor 5: End of log
	Data Format 5: OEM-specific
	Descriptor 6: End of log
	Data Format 6: OEM-specific

Handle 0x000F, DMI type 16, 15 bytes
Physical Memory Array
	Location: System Board Or Motherboard
	Use: System Memory
	Error Correction Type: None
	Maximum Capacity: 4 GB
	Error Information Handle: 0x0010
	Number Of Devices: 4

Handle 0x0010, DMI type 18, 23 bytes
32-bit Memory Error Information
	Type: Unknown
	Granularity: Unknown
	Operation: Unknown
	Vendor Syndrome: Unknown
	Memory Array Address: Unknown
	Device Address: Unknown
	Resolution: Unknown

Handle 0x0011, DMI type 19, 15 bytes
Memory Array Mapped Address
	Starting Address: 0x00000000000
	Ending Address: 0x0007FFFFFFF
	Range Size: 2 GB
	Physical Array Handle: 0x000F
	Partition Width: 0

Handle 0x0012, DMI type 17, 27 bytes
Memory Device
	Array Handle: 0x000F
	Error Information Handle: 0x0013
	Total Width: 64 bits
	Data Width: 64 bits
	Size: 1024 MB
	Form Factor: DIMM
	Set: None
	Locator: DIMM0
	Bank Locator: BANK0
	Type: SDRAM
	Type Detail: Synchronous
	Speed: Unknown
	Manufacturer: Manufacturer0
	Serial Number: SerNum0
	Asset Tag: AssetTagNum0
	Part Number: PartNum0

Handle 0x0013, DMI type 18, 23 bytes
32-bit Memory Error Information
	Type: Unknown
	Granularity: Unknown
	Operation: Unknown
	Vendor Syndrome: Unknown
	Memory Array Address: Unknown
	Device Address: Unknown
	Resolution: Unknown

Handle 0x0014, DMI type 20, 19 bytes
Memory Device Mapped Address
	Starting Address: 0x00000000000
	Ending Address: 0x0003FFFFFFF
	Range Size: 1 GB
	Physical Device Handle: 0x0012
	Memory Array Mapped Address Handle: 0x0011
	Partition Row Position: 1
	Interleaved Data Depth: 1

Handle 0x0015, DMI type 17, 27 bytes
Memory Device
	Array Handle: 0x000F
	Error Information Handle: 0x0016
	Total Width: Unknown
	Data Width: Unknown
	Size: No Module Installed
	Form Factor: DIMM
	Set: None
	Locator: DIMM1
	Bank Locator: BANK1
	Type: Unknown
	Type Detail: Unknown
	Speed: Unknown
	Manufacturer: Manufacturer1
	Serial Number: SerNum1
	Asset Tag: AssetTagNum1
	Part Number: PartNum1

Handle 0x0016, DMI type 18, 23 bytes
32-bit Memory Error Information
	Type: Unknown
	Granularity: Unknown
	Operation: Unknown
	Vendor Syndrome: Unknown
	Memory Array Address: Unknown
	Device Address: Unknown
	Resolution: Unknown

Handle 0x0017, DMI type 20, 19 bytes
Memory Device Mapped Address
	Starting Address: 0x00000000000
	Ending Address: 0x000000003FF
	Range Size: 1 kB
	Physical Device Handle: 0x0015
	Memory Array Mapped Address Handle: 0x0011
	Partition Row Position: 1
	Interleaved Data Depth: 1

Handle 0x0018, DMI type 17, 27 bytes
Memory Device
	Array Handle: 0x000F
	Error Information Handle: 0x0019
	Total Width: 64 bits
	Data Width: 64 bits
	Size: 1024 MB
	Form Factor: DIMM
	Set: None
	Locator: DIMM2
	Bank Locator: BANK2
	Type: SDRAM
	Type Detail: Synchronous
	Speed: Unknown
	Manufacturer: Manufacturer2
	Serial Number: SerNum2
	Asset Tag: AssetTagNum2
	Part Number: PartNum2

Handle 0x0019, DMI type 18, 23 bytes
32-bit Memory Error Information
	Type: Unknown
	Granularity: Unknown
	Operation: Unknown
	Vendor Syndrome: Unknown
	Memory Array Address: Unknown
	Device Address: Unknown
	Resolution: Unknown

Handle 0x001A, DMI type 20, 19 bytes
Memory Device Mapped Address
	Starting Address: 0x00040000000
	Ending Address: 0x0007FFFFFFF
	Range Size: 1 GB
	Physical Device Handle: 0x0018
	Memory Array Mapped Address Handle: 0x0011
	Partition Row Position: 1
	Interleaved Data Depth: 1

Handle 0x001B, DMI type 17, 27 bytes
Memory Device
	Array Handle: 0x000F
	Error Information Handle: 0x001C
	Total Width: Unknown
	Data Width: Unknown
	Size: No Module Installed
	Form Factor: DIMM
	Set: None
	Locator: DIMM3
	Bank Locator: BANK3
	Type: Unknown
	Type Detail: Unknown
	Speed: Unknown
	Manufacturer: Manufacturer3
	Serial Number: SerNum3
	Asset Tag: AssetTagNum3
	Part Number: PartNum3

Handle 0x001C, DMI type 18, 23 bytes
32-bit Memory Error Information
	Type: Unknown
	Granularity: Unknown
	Operation: Unknown
	Vendor Syndrome: Unknown
	Memory Array Address: Unknown
	Device Address: Unknown
	Resolution: Unknown

Handle 0x001D, DMI type 20, 19 bytes
Memory Device Mapped Address
	Starting Address: 0x00000000000
	Ending Address: 0x000000003FF
	Range Size: 1 kB
	Physical Device Handle: 0x001B
	Memory Array Mapped Address Handle: 0x0011
	Partition Row Position: 1
	Interleaved Data Depth: 1

Handle 0x001E, DMI type 32, 20 bytes
System Boot Information
	Status: No errors detected

Handle 0x001F, DMI type 34, 11 bytes
Management Device
	Description: LM78-1
	Type: LM78
	Address: 0x00000000
	Address Type: I/O Port

Handle 0x0020, DMI type 26, 22 bytes
Voltage Probe
	Description: LM78A
	Location: <OUT OF SPEC>
	Status: <OUT OF SPEC>
	Maximum Value: Unknown
	Minimum Value: Unknown
	Resolution: Unknown
	Tolerance: Unknown
	Accuracy: Unknown
	OEM-specific Information: 0x00000000
	Nominal Value: Unknown

Handle 0x0021, DMI type 36, 16 bytes
Management Device Threshold Data
	Lower Non-critical Threshold: 1
	Upper Non-critical Threshold: 2
	Lower Critical Threshold: 3
	Upper Critical Threshold: 4
	Lower Non-recoverable Threshold: 5
	Upper Non-recoverable Threshold: 6

Handle 0x0022, DMI type 35, 11 bytes
Management Device Component
	Description: To Be Filled By O.E.M.
	Management Device Handle: 0x001F
	Component Handle: 0x001F
	Threshold Handle: 0x0020

Handle 0x0023, DMI type 28, 22 bytes
Temperature Probe
	Description: LM78A
	Location: <OUT OF SPEC>
	Status: <OUT OF SPEC>
	Maximum Value: Unknown
	Minimum Value Unknown
	Resolution: Unknown
	Tolerance: Unknown
	Accuracy: Unknown
	OEM-specific Information: 0x00000000
	Nominal Value: Unknown

Handle 0x0024, DMI type 36, 16 bytes
Management Device Threshold Data
	Lower Non-critical Threshold: 1
	Upper Non-critical Threshold: 2
	Lower Critical Threshold: 3
	Upper Critical Threshold: 4
	Lower Non-recoverable Threshold: 5
	Upper Non-recoverable Threshold: 6

Handle 0x0025, DMI type 35, 11 bytes
Management Device Component
	Description: To Be Filled By O.E.M.
	Management Device Handle: 0x001F
	Component Handle: 0x0022
	Threshold Handle: 0x0023

Handle 0x0026, DMI type 27, 14 bytes
Cooling Device
	Temperature Probe Handle: 0x0023
	Type: Fan
	Status: OK
	OEM-specific Information: 0x00000000
	Nominal Speed: 1200 rpm

Handle 0x0027, DMI type 36, 16 bytes
Management Device Threshold Data
	Lower Non-critical Threshold: 1
	Upper Non-critical Threshold: 2
	Lower Critical Threshold: 3
	Upper Critical Threshold: 4
	Lower Non-recoverable Threshold: 5
	Upper Non-recoverable Threshold: 6

Handle 0x0028, DMI type 35, 11 bytes
Management Device Component
	Description: To Be Filled By O.E.M.
	Management Device Handle: 0x001F
	Component Handle: 0x0025
	Threshold Handle: 0x0026

Handle 0x0029, DMI type 29, 22 bytes
Electrical Current Probe
	Description: ABC
	Location: <OUT OF SPEC>
	Status: <OUT OF SPEC>
	Maximum Value: Unknown
	Minimum Value: Unknown
	Resolution: Unknown
	Tolerance: Unknown
	Accuracy: Unknown
	OEM-specific Information: 0x00000000
	Nominal Value: Unknown

Handle 0x002A, DMI type 36, 16 bytes
Management Device Threshold Data

Handle 0x002B, DMI type 35, 11 bytes
Management Device Component
	Description: To Be Filled By O.E.M.
	Management Device Handle: 0x001F
	Component Handle: 0x0028
	Threshold Handle: 0x0026

Handle 0x002C, DMI type 39, 22 bytes
System Power Supply
	Location: In the Back
	Name: ENP-3330A
	Manufacturer: Enhance Electronics Co. LTD
	Serial Number: 0612 00214
	Asset Tag: System power supply
	Model Part Number: ENP-3330A
	Revision: 3.1
	Max Power Capacity: 0.300 W
	Status: Present, <OUT OF SPEC>
	Type: <OUT OF SPEC>
	Input Voltage Range Switching: <OUT OF SPEC>
	Plugged: No
	Hot Replaceable: Yes
	Input Voltage Probe Handle: 0x0020
	Cooling Device Handle: 0x0026
	Input Current Probe Handle: 0x0029

Handle 0x002D, DMI type 129, 8 bytes
OEM-specific Type
	Header and Data:
		81 08 2D 00 01 01 02 01
	Strings:
		Intel_ASF
		Intel_ASF_001

Handle 0x002E, DMI type 130, 20 bytes
OEM-specific Type
	Header and Data:
		82 14 2E 00 24 41 4D 54 01 00 00 00 01 00 00 00
		00 00 00 00

Handle 0x002F, DMI type 127, 4 bytes
End Of Table


[-- Attachment #1.2: S/MIME Cryptographic Signature --]
[-- Type: application/x-pkcs7-signature, Size: 3237 bytes --]

[-- Attachment #2: Type: text/plain, Size: 228 bytes --]

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/

[-- Attachment #3: Type: text/plain, Size: 186 bytes --]

_______________________________________________
kvm-devel mailing list
kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
https://lists.sourceforge.net/lists/listinfo/kvm-devel

Re: KVM-58 -- existing VM just hangs with black screen

[Richard W.M. Jones]

[-- Attachment #1.1: Type: text/plain, Size: 957 bytes --]

Avi Kivity wrote:
> Can you identify which version of kvm introduced the regression?

Some more data points:

   kvm-56 from [1]   ==> works OK

   kvm-57 from [2]   ==> works OK

   kvm-58 from [1]   ==> hangs with black screen at boot

   kvm-58 from [2]   ==> hangs with black screen at boot

In all cases, the command line I'm using to boot is:

   qemu-kvm -m 1024 -boot c -hda windows32kvm.img

In all cases the kernel is this Fedora 9 kernel:

   Linux intel 2.6.24-0.123.rc6.fc9 #1 SMP Fri Dec 21 16:12:46 EST 2007 
x86_64 x86_64 x86_64 GNU/Linux

Rich.

[1] http://koji.fedoraproject.org/koji/packageinfo?packageID=2261
[2] http://download.sourceforge.net/sourceforge/kvm/kvm-57.tar.gz

-- 
Emerging Technologies, Red Hat - http://et.redhat.com/~rjones/
Registered Address: Red Hat UK Ltd, Amberley Place, 107-111 Peascod
Street, Windsor, Berkshire, SL4 1TE, United Kingdom.  Registered in
England and Wales under Company Registration No. 03798903

[-- Attachment #1.2: S/MIME Cryptographic Signature --]
[-- Type: application/x-pkcs7-signature, Size: 3237 bytes --]

[-- Attachment #2: Type: text/plain, Size: 228 bytes --]

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/

[-- Attachment #3: Type: text/plain, Size: 186 bytes --]

_______________________________________________
kvm-devel mailing list
kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
https://lists.sourceforge.net/lists/listinfo/kvm-devel

Re: KVM-58 -- existing VM just hangs with black screen

[Avi Kivity]

[-- Attachment #1: Type: text/plain, Size: 569 bytes --]

Richard W.M. Jones wrote:
> Avi Kivity wrote:
>> Can you identify which version of kvm introduced the regression?
>
> Some more data points:
>
>   kvm-56 from [1]   ==> works OK
>
>   kvm-57 from [2]   ==> works OK
>
>   kvm-58 from [1]   ==> hangs with black screen at boot
>
>   kvm-58 from [2]   ==> hangs with black screen at boot
>

Please try reverting the attached patch (or applying it to a working 
version).

If that doesn't work, try bios.bin from a working version with a 
non-working qemu.

-- 
error compiling committee.c: too many arguments to function


[-- Attachment #2: chs.patch --]
[-- Type: text/x-patch, Size: 10307 bytes --]

commit 7c4f3ce4aad409377adc0389da1805152a30dafd
Author: Anthony Liguori <aliguori-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
Date:   Thu Dec 20 13:37:56 2007 +0200

    kvm: qemu: refactor disk CHS guessing for reuse in non-IDE drives
    
    Signed-off-by: Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org>

diff --git a/qemu/block.c b/qemu/block.c
index 24d78fc..b1650c0 100644
--- a/qemu/block.c
+++ b/qemu/block.c
@@ -738,6 +738,122 @@ void bdrv_set_boot_sector(BlockDriverState *bs, const uint8_t *data, int size)
     memset(bs->boot_sector_data + size, 0, 512 - size);
 }
 
+struct partition {
+	uint8_t boot_ind;		/* 0x80 - active */
+	uint8_t head;		/* starting head */
+	uint8_t sector;		/* starting sector */
+	uint8_t cyl;		/* starting cylinder */
+	uint8_t sys_ind;		/* What partition type */
+	uint8_t end_head;		/* end head */
+	uint8_t end_sector;	/* end sector */
+	uint8_t end_cyl;		/* end cylinder */
+	uint32_t start_sect;	/* starting sector counting from 0 */
+	uint32_t nr_sects;		/* nr of sectors in partition */
+} __attribute__((packed));
+
+/* try to guess the disk logical geometry from the MSDOS partition table. Return 0 if OK, -1 if could not guess */
+static int guess_disk_lchs(BlockDriverState *bs,
+                           int *pcylinders, int *pheads, int *psectors)
+{
+    uint8_t buf[512];
+    int ret, i, heads, sectors, cylinders;
+    struct partition *p;
+    uint32_t nr_sects;
+    int64_t nb_sectors;
+
+    bdrv_get_geometry(bs, &nb_sectors);
+
+    ret = bdrv_read(bs, 0, buf, 1);
+    if (ret < 0)
+        return -1;
+    /* test msdos magic */
+    if (buf[510] != 0x55 || buf[511] != 0xaa)
+        return -1;
+    for(i = 0; i < 4; i++) {
+        p = ((struct partition *)(buf + 0x1be)) + i;
+        nr_sects = le32_to_cpu(p->nr_sects);
+        if (nr_sects && p->end_head) {
+            /* We make the assumption that the partition terminates on
+               a cylinder boundary */
+            heads = p->end_head + 1;
+            sectors = p->end_sector & 63;
+            if (sectors == 0)
+                continue;
+            cylinders = nb_sectors / (heads * sectors);
+            if (cylinders < 1 || cylinders > 16383)
+                continue;
+            *pheads = heads;
+            *psectors = sectors;
+            *pcylinders = cylinders;
+#if 0
+            printf("guessed geometry: LCHS=%d %d %d\n",
+                   cylinders, heads, sectors);
+#endif
+            return 0;
+        }
+    }
+    return -1;
+}
+
+void bdrv_guess_geometry(BlockDriverState *bs, int *pcyls, int *pheads, int *psecs)
+{
+    int translation, lba_detected = 0;
+    int cylinders, heads, secs;
+    int64_t nb_sectors;
+
+    /* if a geometry hint is available, use it */
+    bdrv_get_geometry(bs, &nb_sectors);
+    bdrv_get_geometry_hint(bs, &cylinders, &heads, &secs);
+    translation = bdrv_get_translation_hint(bs);
+    if (cylinders != 0) {
+	*pcyls = cylinders;
+	*pheads = heads;
+	*psecs = secs;
+    } else {
+	if (guess_disk_lchs(bs, &cylinders, &heads, &secs) == 0) {
+	    if (heads > 16) {
+		/* if heads > 16, it means that a BIOS LBA
+		   translation was active, so the default
+		   hardware geometry is OK */
+		lba_detected = 1;
+		goto default_geometry;
+	    } else {
+		*pcyls = cylinders;
+		*pheads = heads;
+		*psecs = secs;
+		/* disable any translation to be in sync with
+		   the logical geometry */
+		if (translation == BIOS_ATA_TRANSLATION_AUTO) {
+		    bdrv_set_translation_hint(bs,
+					      BIOS_ATA_TRANSLATION_NONE);
+		}
+	    }
+	} else {
+	default_geometry:
+	    /* if no geometry, use a standard physical disk geometry */
+	    cylinders = nb_sectors / (16 * 63);
+
+	    if (cylinders > 16383)
+	        cylinders = 16383;
+	    else if (cylinders < 2)
+	        cylinders = 2;
+	    *pcyls = cylinders;
+	    *pheads = 16;
+	    *psecs = 63;
+	    if ((lba_detected == 1) && (translation == BIOS_ATA_TRANSLATION_AUTO)) {
+		if ((*pcyls * *pheads) <= 131072) {
+		    bdrv_set_translation_hint(bs,
+					      BIOS_ATA_TRANSLATION_LARGE);
+		} else {
+		    bdrv_set_translation_hint(bs,
+					      BIOS_ATA_TRANSLATION_LBA);
+		}
+	    }
+	}
+	bdrv_set_geometry_hint(bs, *pcyls, *pheads, *psecs);
+    }
+}
+
 void bdrv_set_geometry_hint(BlockDriverState *bs,
                             int cyls, int heads, int secs)
 {
diff --git a/qemu/block.h b/qemu/block.h
index f98639a..839be90 100644
--- a/qemu/block.h
+++ b/qemu/block.h
@@ -73,6 +73,7 @@ int bdrv_pwrite(BlockDriverState *bs, int64_t offset,
 int bdrv_truncate(BlockDriverState *bs, int64_t offset);
 int64_t bdrv_getlength(BlockDriverState *bs);
 void bdrv_get_geometry(BlockDriverState *bs, int64_t *nb_sectors_ptr);
+void bdrv_guess_geometry(BlockDriverState *bs, int *pcyls, int *pheads, int *psecs);
 int bdrv_commit(BlockDriverState *bs);
 void bdrv_set_boot_sector(BlockDriverState *bs, const uint8_t *data, int size);
 /* async block I/O */
diff --git a/qemu/hw/ide.c b/qemu/hw/ide.c
index bd579f8..f43e6f1 100644
--- a/qemu/hw/ide.c
+++ b/qemu/hw/ide.c
@@ -2367,67 +2367,13 @@ static void ide_reset(IDEState *s)
     s->media_changed = 0;
 }
 
-struct partition {
-	uint8_t boot_ind;		/* 0x80 - active */
-	uint8_t head;		/* starting head */
-	uint8_t sector;		/* starting sector */
-	uint8_t cyl;		/* starting cylinder */
-	uint8_t sys_ind;		/* What partition type */
-	uint8_t end_head;		/* end head */
-	uint8_t end_sector;	/* end sector */
-	uint8_t end_cyl;		/* end cylinder */
-	uint32_t start_sect;	/* starting sector counting from 0 */
-	uint32_t nr_sects;		/* nr of sectors in partition */
-} __attribute__((packed));
-
-/* try to guess the disk logical geometry from the MSDOS partition table. Return 0 if OK, -1 if could not guess */
-static int guess_disk_lchs(IDEState *s,
-                           int *pcylinders, int *pheads, int *psectors)
-{
-    uint8_t buf[512];
-    int ret, i, heads, sectors, cylinders;
-    struct partition *p;
-    uint32_t nr_sects;
-
-    ret = bdrv_read(s->bs, 0, buf, 1);
-    if (ret < 0)
-        return -1;
-    /* test msdos magic */
-    if (buf[510] != 0x55 || buf[511] != 0xaa)
-        return -1;
-    for(i = 0; i < 4; i++) {
-        p = ((struct partition *)(buf + 0x1be)) + i;
-        nr_sects = le32_to_cpu(p->nr_sects);
-        if (nr_sects && p->end_head) {
-            /* We make the assumption that the partition terminates on
-               a cylinder boundary */
-            heads = p->end_head + 1;
-            sectors = p->end_sector & 63;
-            if (sectors == 0)
-                continue;
-            cylinders = s->nb_sectors / (heads * sectors);
-            if (cylinders < 1 || cylinders > 16383)
-                continue;
-            *pheads = heads;
-            *psectors = sectors;
-            *pcylinders = cylinders;
-#if 0
-            printf("guessed geometry: LCHS=%d %d %d\n",
-                   cylinders, heads, sectors);
-#endif
-            return 0;
-        }
-    }
-    return -1;
-}
-
 static void ide_init2(IDEState *ide_state,
                       BlockDriverState *hd0, BlockDriverState *hd1,
                       qemu_irq irq)
 {
     IDEState *s;
     static int drive_serial = 1;
-    int i, cylinders, heads, secs, translation, lba_detected = 0;
+    int i, cylinders, heads, secs;
     int64_t nb_sectors;
 
     for(i = 0; i < 2; i++) {
@@ -2438,56 +2384,12 @@ static void ide_init2(IDEState *ide_state,
             s->bs = hd1;
         if (s->bs) {
             bdrv_get_geometry(s->bs, &nb_sectors);
+	    bdrv_guess_geometry(s->bs, &cylinders, &heads, &secs);
+	    s->cylinders = cylinders;
+	    s->heads = heads;
+	    s->sectors = secs;
             s->nb_sectors = nb_sectors;
-            /* if a geometry hint is available, use it */
-            bdrv_get_geometry_hint(s->bs, &cylinders, &heads, &secs);
-            translation = bdrv_get_translation_hint(s->bs);
-            if (cylinders != 0) {
-                s->cylinders = cylinders;
-                s->heads = heads;
-                s->sectors = secs;
-            } else {
-                if (guess_disk_lchs(s, &cylinders, &heads, &secs) == 0) {
-                    if (heads > 16) {
-                        /* if heads > 16, it means that a BIOS LBA
-                           translation was active, so the default
-                           hardware geometry is OK */
-                        lba_detected = 1;
-                        goto default_geometry;
-                    } else {
-                        s->cylinders = cylinders;
-                        s->heads = heads;
-                        s->sectors = secs;
-                        /* disable any translation to be in sync with
-                           the logical geometry */
-                        if (translation == BIOS_ATA_TRANSLATION_AUTO) {
-                            bdrv_set_translation_hint(s->bs,
-                                                      BIOS_ATA_TRANSLATION_NONE);
-                        }
-                    }
-                } else {
-                default_geometry:
-                    /* if no geometry, use a standard physical disk geometry */
-                    cylinders = nb_sectors / (16 * 63);
-                    if (cylinders > 16383)
-                        cylinders = 16383;
-                    else if (cylinders < 2)
-                        cylinders = 2;
-                    s->cylinders = cylinders;
-                    s->heads = 16;
-                    s->sectors = 63;
-                    if ((lba_detected == 1) && (translation == BIOS_ATA_TRANSLATION_AUTO)) {
-                      if ((s->cylinders * s->heads) <= 131072) {
-                        bdrv_set_translation_hint(s->bs,
-                                                  BIOS_ATA_TRANSLATION_LARGE);
-                      } else {
-                        bdrv_set_translation_hint(s->bs,
-                                                  BIOS_ATA_TRANSLATION_LBA);
-                      }
-                    }
-                }
-                bdrv_set_geometry_hint(s->bs, s->cylinders, s->heads, s->sectors);
-            }
+
             if (bdrv_get_type_hint(s->bs) == BDRV_TYPE_CDROM) {
                 s->is_cdrom = 1;
 		bdrv_set_change_cb(s->bs, cdrom_change_cb, s);

[-- Attachment #3: Type: text/plain, Size: 228 bytes --]

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/

[-- Attachment #4: Type: text/plain, Size: 186 bytes --]

_______________________________________________
kvm-devel mailing list
kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
https://lists.sourceforge.net/lists/listinfo/kvm-devel

Re: KVM-58 -- existing VM just hangs with black screen

[Richard W.M. Jones]

[-- Attachment #1.1: Type: text/plain, Size: 942 bytes --]

Avi Kivity wrote:
> Richard W.M. Jones wrote:
>> Avi Kivity wrote:
>>> Can you identify which version of kvm introduced the regression?
>>
>> Some more data points:
>>
>>   kvm-56 from [1]   ==> works OK
>>
>>   kvm-57 from [2]   ==> works OK
>>
>>   kvm-58 from [1]   ==> hangs with black screen at boot
>>
>>   kvm-58 from [2]   ==> hangs with black screen at boot
>>
> 
> Please try reverting the attached patch (or applying it to a working 
> version).
> 
> If that doesn't work, try bios.bin from a working version with a 
> non-working qemu.

No, I'm afraid that taking kvm-58 and applying that patch reversed (to 
remove it) does not work.  Same symptoms as before.

Rich.

-- 
Emerging Technologies, Red Hat - http://et.redhat.com/~rjones/
Registered Address: Red Hat UK Ltd, Amberley Place, 107-111 Peascod
Street, Windsor, Berkshire, SL4 1TE, United Kingdom.  Registered in
England and Wales under Company Registration No. 03798903

[-- Attachment #1.2: S/MIME Cryptographic Signature --]
[-- Type: application/x-pkcs7-signature, Size: 3237 bytes --]

[-- Attachment #2: Type: text/plain, Size: 228 bytes --]

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/

[-- Attachment #3: Type: text/plain, Size: 186 bytes --]

_______________________________________________
kvm-devel mailing list
kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
https://lists.sourceforge.net/lists/listinfo/kvm-devel

Re: KVM-58 -- existing VM just hangs with black screen

[Avi Kivity]

Richard W.M. Jones wrote:
>>
>> Please try reverting the attached patch (or applying it to a working 
>> version).
>>
>> If that doesn't work, try bios.bin from a working version with a 
>> non-working qemu.
>
> No, I'm afraid that taking kvm-58 and applying that patch reversed (to 
> remove it) does not work.  Same symptoms as before.
>

What about using an older bios?

-- 
error compiling committee.c: too many arguments to function


-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/

Re: KVM-58 -- existing VM just hangs with black screen

[Richard W.M. Jones]

[-- Attachment #1.1: Type: text/plain, Size: 574 bytes --]

Avi Kivity wrote:
> If that doesn't work, try bios.bin from a working version with a 
> non-working qemu.

I've just read the second part now ...

I took bios.bin, vgabios.bin and vgabios-cirrus.bin from KVM-57 and used 
them to overwrite the corresponding files in KVM-58, and that did not 
work either.

Rich.

-- 
Emerging Technologies, Red Hat - http://et.redhat.com/~rjones/
Registered Address: Red Hat UK Ltd, Amberley Place, 107-111 Peascod
Street, Windsor, Berkshire, SL4 1TE, United Kingdom.  Registered in
England and Wales under Company Registration No. 03798903

[-- Attachment #1.2: S/MIME Cryptographic Signature --]
[-- Type: application/x-pkcs7-signature, Size: 3237 bytes --]

[-- Attachment #2: Type: text/plain, Size: 228 bytes --]

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/

[-- Attachment #3: Type: text/plain, Size: 186 bytes --]

_______________________________________________
kvm-devel mailing list
kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
https://lists.sourceforge.net/lists/listinfo/kvm-devel

Re: KVM-58 -- existing VM just hangs with black screen

[Avi Kivity]

Richard W.M. Jones wrote:
> Avi Kivity wrote:
>> If that doesn't work, try bios.bin from a working version with a 
>> non-working qemu.
>
> I've just read the second part now ...
>
> I took bios.bin, vgabios.bin and vgabios-cirrus.bin from KVM-57 and 
> used them to overwrite the corresponding files in KVM-58, and that did 
> not work either.

Can you post the boot sector?  Also, what is the size of the disk?


-- 
error compiling committee.c: too many arguments to function


-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/

Re: KVM-58 -- existing VM just hangs with black screen

[Richard W.M. Jones]

[-- Attachment #1.1: Type: text/plain, Size: 912 bytes --]

Avi Kivity wrote:
> Richard W.M. Jones wrote:
>> Avi Kivity wrote:
>>> If that doesn't work, try bios.bin from a working version with a 
>>> non-working qemu.
>>
>> I've just read the second part now ...
>>
>> I took bios.bin, vgabios.bin and vgabios-cirrus.bin from KVM-57 and 
>> used them to overwrite the corresponding files in KVM-58, and that did 
>> not work either.
> 
> Can you post the boot sector?  Also, what is the size of the disk?

This is the boot sector: http://www.annexia.org/tmp/bootsect

and the size of the disk is 20,000 MB, originally created using this 
command:

dd if=/dev/zero of=windows32kvm.img bs=1M count=20000

Rich.

-- 
Emerging Technologies, Red Hat - http://et.redhat.com/~rjones/
Registered Address: Red Hat UK Ltd, Amberley Place, 107-111 Peascod
Street, Windsor, Berkshire, SL4 1TE, United Kingdom.  Registered in
England and Wales under Company Registration No. 03798903

[-- Attachment #1.2: S/MIME Cryptographic Signature --]
[-- Type: application/x-pkcs7-signature, Size: 3237 bytes --]

[-- Attachment #2: Type: text/plain, Size: 228 bytes --]

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/

[-- Attachment #3: Type: text/plain, Size: 186 bytes --]

_______________________________________________
kvm-devel mailing list
kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
https://lists.sourceforge.net/lists/listinfo/kvm-devel

Re: KVM-58 -- existing VM just hangs with black screen

[Avi Kivity]

Richard W.M. Jones wrote:
> Avi Kivity wrote:
>> Richard W.M. Jones wrote:
>>> Avi Kivity wrote:
>>>> If that doesn't work, try bios.bin from a working version with a 
>>>> non-working qemu.
>>>
>>> I've just read the second part now ...
>>>
>>> I took bios.bin, vgabios.bin and vgabios-cirrus.bin from KVM-57 and 
>>> used them to overwrite the corresponding files in KVM-58, and that 
>>> did not work either.
>>
>> Can you post the boot sector?  Also, what is the size of the disk?
>
> This is the boot sector: http://www.annexia.org/tmp/bootsect
>
> and the size of the disk is 20,000 MB, originally created using this 
> command:
>
> dd if=/dev/zero of=windows32kvm.img bs=1M count=20000

Booting the same boot sector shows three read operations here with 'info 
blockstats'.

Can you try the option '-no-kvm' both with kvm-57 and kvm-58?

-- 
error compiling committee.c: too many arguments to function


-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/

Re: KVM-58 -- existing VM just hangs with black screen

[Jeremy Katz]

On Wed, 2008-01-02 at 19:13 +0200, Avi Kivity wrote:
> Can you try the option '-no-kvm' both with kvm-57 and kvm-58?

-no-kvm works.  I can hit this just booting a live CD both on a 32bit
and a 64bit host.  It looks like compatibility with old kernels is
broken (the kvm package only contains the userspace bits, the kernel
bits come from the kernel which is currently 2.6.24-rc6).  Building an
updated kernel module makes things start to work on my laptop

Jeremy


-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/

Re: KVM-58 -- existing VM just hangs with black screen

[Avi Kivity]

[-- Attachment #1: Type: text/plain, Size: 629 bytes --]

Jeremy Katz wrote:
> On Wed, 2008-01-02 at 19:13 +0200, Avi Kivity wrote:
>   
>> Can you try the option '-no-kvm' both with kvm-57 and kvm-58?
>>     
>
> -no-kvm works.  I can hit this just booting a live CD both on a 32bit
> and a 64bit host.  It looks like compatibility with old kernels is
> broken (the kvm package only contains the userspace bits, the kernel
> bits come from the kernel which is currently 2.6.24-rc6).  Building an
> updated kernel module makes things start to work on my laptop
>   

Right.  I fixed this for kvm-60, see attached patch.


-- 
error compiling committee.c: too many arguments to function


[-- Attachment #2: fix-old-kernels.patch --]
[-- Type: text/x-patch, Size: 1126 bytes --]

commit 6b8bb99a9cde386d72b4b7c22b92f4bdec333dab
Author: Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
Date:   Thu Jan 3 12:20:21 2008 +0200

    kvm: qemu: restore IO_MEM_ROM mark to bios when registering the memory with kvm
    
    We removed the IO_MEM_ROM mark for qemu, since the tpr optimization needs to
    update the bios.  However, kvm_cpu_register_physical_memory() uses the mark
    for other purposes, so keep it.  The removal broke bootstrap on older kernels.
    
    Signed-off-by: Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org>

diff --git a/qemu/hw/pc.c b/qemu/hw/pc.c
index 5a1b7d4..179585f 100644
--- a/qemu/hw/pc.c
+++ b/qemu/hw/pc.c
@@ -865,8 +865,7 @@ static void pc_init1(ram_addr_t ram_size, int vga_ram_size,
     if (kvm_allowed)
         kvm_cpu_register_physical_memory(0x100000 - isa_bios_size,
                                          isa_bios_size,
-                                         (bios_offset + bios_size - isa_bios_size)
-					 /* | IO_MEM_ROM */);
+                                         (bios_offset + bios_size - isa_bios_size) | IO_MEM_ROM);
 #endif
 
 

[-- Attachment #3: Type: text/plain, Size: 228 bytes --]

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/

[-- Attachment #4: Type: text/plain, Size: 186 bytes --]

_______________________________________________
kvm-devel mailing list
kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
https://lists.sourceforge.net/lists/listinfo/kvm-devel