public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
* Kernel panic when loading kvm-amd
@ 2007-05-28  1:29 Pär Andersson
       [not found] ` <200705280330.19290.paran-SamgB31n2u5IcsJQ0EH25Q@public.gmane.org>
  0 siblings, 1 reply; 9+ messages in thread
From: Pär Andersson @ 2007-05-28  1:29 UTC (permalink / raw)
  To: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f


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

Hi.

I am getting a kernel panic when loading the kvm-amd module. I have talked a 
little about this with aliguori on IRC and according to him the panic occurs 
when KVM enables EFER.SVME.

Computer information:
AMD Athlon64 X2 4400+, 65nm, Brisbane.
Abit KN9 motherboard (nforce4)
Ubuntu 7.04 x86_64
Kernel version 2.6.20-15-generic (latest Ubuntu kernel for 7.04)

Unfortunately my motherboard does not have rs232 so I can't attach a serial 
console to get the text of the panic. Instead I have taken a photo of the 
screen, not very good but it is the best I can do. This "screenshot" together 
with some more hardware information (output from dmesg, /proc/cpuinfo etc) is 
here:

http://www-und.ida.liu.se/~paran213/kvm/2007-05-27/

The screenshot is when using KVM-25, I get the same result using KVM-16(from 
ubuntu packages) and KVM-24.

regards
Pär Andersson

[-- Attachment #1.2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

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

-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/

[-- 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

^ permalink raw reply	[flat|nested] 9+ messages in thread

* Re: Kernel panic when loading kvm-amd
       [not found] ` <200705280330.19290.paran-SamgB31n2u5IcsJQ0EH25Q@public.gmane.org>
@ 2007-05-28 20:16   ` Anthony Liguori
       [not found]     ` <465B3885.2070401-rdkfGonbjUSkNkDKm+mE6A@public.gmane.org>
  0 siblings, 1 reply; 9+ messages in thread
From: Anthony Liguori @ 2007-05-28 20:16 UTC (permalink / raw)
  To: Pär Andersson; +Cc: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f

Pär Andersson wrote:
> Hi.
>
> I am getting a kernel panic when loading the kvm-amd module. I have talked a 
> little about this with aliguori on IRC and according to him the panic occurs 
> when KVM enables EFER.SVME.
>   

I find this very odd.  Setting EFER.SVME shouldn't do any harm even if 
it's already set.  The only thing I can think of would be that SVM 
wasn't available but this is an X2 so it really ought to be.

Anyone have any clue why setting EFER.SVME would cause an OOPS?

Regards,

Anthony Liguori

> Computer information:
> AMD Athlon64 X2 4400+, 65nm, Brisbane.
> Abit KN9 motherboard (nforce4)
> Ubuntu 7.04 x86_64
> Kernel version 2.6.20-15-generic (latest Ubuntu kernel for 7.04)
>
> Unfortunately my motherboard does not have rs232 so I can't attach a serial 
> console to get the text of the panic. Instead I have taken a photo of the 
> screen, not very good but it is the best I can do. This "screenshot" together 
> with some more hardware information (output from dmesg, /proc/cpuinfo etc) is 
> here:
>
> http://www-und.ida.liu.se/~paran213/kvm/2007-05-27/
>
> The screenshot is when using KVM-25, I get the same result using KVM-16(from 
> ubuntu packages) and KVM-24.
>
> regards
> Pär Andersson
>   
> ------------------------------------------------------------------------
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by DB2 Express
> Download DB2 Express C - the FREE version of DB2 express and take
> control of your XML. No limits. Just data. Click to get it now.
> http://sourceforge.net/powerbar/db2/
> ------------------------------------------------------------------------
>
> _______________________________________________
> kvm-devel mailing list
> kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
> https://lists.sourceforge.net/lists/listinfo/kvm-devel
>   


-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/

^ permalink raw reply	[flat|nested] 9+ messages in thread

* Re: Kernel panic when loading kvm-amd
       [not found]     ` <465B3885.2070401-rdkfGonbjUSkNkDKm+mE6A@public.gmane.org>
@ 2007-05-29  8:20       ` Avi Kivity
       [not found]         ` <465BE236.4020805-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
  0 siblings, 1 reply; 9+ messages in thread
From: Avi Kivity @ 2007-05-29  8:20 UTC (permalink / raw)
  To: Anthony Liguori
  Cc: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f, Pär Andersson

Anthony Liguori wrote:
> Pär Andersson wrote:
>   
>> Hi.
>>
>> I am getting a kernel panic when loading the kvm-amd module. I have talked a 
>> little about this with aliguori on IRC and according to him the panic occurs 
>> when KVM enables EFER.SVME.
>>   
>>     
>
> I find this very odd.  Setting EFER.SVME shouldn't do any harm even if 
> it's already set.  The only thing I can think of would be that SVM 
> wasn't available but this is an X2 so it really ought to be.
>
> Anyone have any clue why setting EFER.SVME would cause an OOPS?
>   

Blue Pill?

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


-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/

^ permalink raw reply	[flat|nested] 9+ messages in thread

* Re: Kernel panic when loading kvm-amd
       [not found]         ` <465BE236.4020805-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
@ 2007-05-29 16:13           ` Huang2, Wei
       [not found]             ` <7D748C767B7FA541A8AC5504A4C89A2302FEBD35-SXV0rU3j2e+jL8BtgrxzBQC/G2K4zDHf@public.gmane.org>
  0 siblings, 1 reply; 9+ messages in thread
From: Huang2, Wei @ 2007-05-29 16:13 UTC (permalink / raw)
  To: Avi Kivity, Anthony Liguori
  Cc: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f, Pär Andersson

SVM looks available on your machine. If possible, could you provide dmidecode information (type "dmidecode") for further verification? I know that some vendors disabled SVM feature in BIOS last year. But this was pretty rare. Maybe you can check whether BIOS has an option for SVM.

-Wei


Avi Kivity wrote:
> Anthony Liguori wrote:
>> Pär Andersson wrote:
>> 
>>> Hi.
>>> 
>>> I am getting a kernel panic when loading the kvm-amd module. I have
>>> talked a little about this with aliguori on IRC and according to him
>>> the panic occurs when KVM enables EFER.SVME.
>>> 
>>> 
>> 
>> I find this very odd.  Setting EFER.SVME shouldn't do any harm even
>> if it's already set.  The only thing I can think of would be that SVM
>> wasn't available but this is an X2 so it really ought to be.
>> 
>> Anyone have any clue why setting EFER.SVME would cause an OOPS?
>> 
> 
> Blue Pill?



-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/

^ permalink raw reply	[flat|nested] 9+ messages in thread

* Re: Kernel panic when loading kvm-amd
       [not found]             ` <7D748C767B7FA541A8AC5504A4C89A2302FEBD35-SXV0rU3j2e+jL8BtgrxzBQC/G2K4zDHf@public.gmane.org>
@ 2007-05-29 18:16               ` Avi Kivity
       [not found]                 ` <465C6E0A.6030008-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
  0 siblings, 1 reply; 9+ messages in thread
From: Avi Kivity @ 2007-05-29 18:16 UTC (permalink / raw)
  To: Huang2, Wei
  Cc: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f, Pär Andersson

Huang2, Wei wrote:
> SVM looks available on your machine. If possible, could you provide dmidecode information (type "dmidecode") for further verification? I know that some vendors disabled SVM feature in BIOS last year. But this was pretty rare. Maybe you can check whether BIOS has an option for SVM.
>   

Is there a way to detect whether the bios has disabled svm?  If not, is
trapping the #GP on wrmsr(EFER) a good way to do it?

-- 
Do not meddle in the internals of kernels, for they are subtle and quick to panic.


-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/

^ permalink raw reply	[flat|nested] 9+ messages in thread

* Re: Kernel panic when loading kvm-amd
       [not found]                 ` <465C6E0A.6030008-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
@ 2007-05-29 18:55                   ` Huang2, Wei
       [not found]                     ` <7D748C767B7FA541A8AC5504A4C89A2302FEBE97-SXV0rU3j2e+jL8BtgrxzBQC/G2K4zDHf@public.gmane.org>
  0 siblings, 1 reply; 9+ messages in thread
From: Huang2, Wei @ 2007-05-29 18:55 UTC (permalink / raw)
  To: Avi Kivity; +Cc: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f, Pär Andersson

As far as I know, there is no special way to detect BIOS-disabled SVM. BIOS should always trap #GP on writing SVME bit. So the way you suggested should work.

Pär, are you sure that EFER.SVME bit has been set when the error happened? Our architecture design team confirmed that enabling EFER.SVME twice won't cause any problem (There will be some performance loss though). 

Regards,

-Wei


Avi Kivity wrote:
> Huang2, Wei wrote:
>> SVM looks available on your machine. If possible, could you provide
>> dmidecode information (type "dmidecode") for further verification? I
>> know that some vendors disabled SVM feature in BIOS last year. But
>> this was pretty rare. Maybe you can check whether BIOS has an option
>> for SVM.    
>> 
> 
> Is there a way to detect whether the bios has disabled svm?  If not,
> is trapping the #GP on wrmsr(EFER) a good way to do it? 



-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/

^ permalink raw reply	[flat|nested] 9+ messages in thread

* Re: Kernel panic when loading kvm-amd
       [not found]                     ` <7D748C767B7FA541A8AC5504A4C89A2302FEBE97-SXV0rU3j2e+jL8BtgrxzBQC/G2K4zDHf@public.gmane.org>
@ 2007-05-30  4:56                       ` Avi Kivity
  2007-05-31 12:21                       ` Pär Andersson
  1 sibling, 0 replies; 9+ messages in thread
From: Avi Kivity @ 2007-05-30  4:56 UTC (permalink / raw)
  To: Huang2, Wei
  Cc: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f, Pär Andersson

Huang2, Wei wrote:
> As far as I know, there is no special way to detect BIOS-disabled SVM. BIOS should always trap #GP on writing SVME bit. So the way you suggested should work.
>
>   

Okay.  How does the bios disable svm?

-- 
Do not meddle in the internals of kernels, for they are subtle and quick to panic.


-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/

^ permalink raw reply	[flat|nested] 9+ messages in thread

* Re: Kernel panic when loading kvm-amd
       [not found]                     ` <7D748C767B7FA541A8AC5504A4C89A2302FEBE97-SXV0rU3j2e+jL8BtgrxzBQC/G2K4zDHf@public.gmane.org>
  2007-05-30  4:56                       ` Avi Kivity
@ 2007-05-31 12:21                       ` Pär Andersson
       [not found]                         ` <465FB4D4.6030509@amd.com>
  1 sibling, 1 reply; 9+ messages in thread
From: Pär Andersson @ 2007-05-31 12:21 UTC (permalink / raw)
  To: Huang2, Wei; +Cc: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f

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

On Tuesday 29 May 2007 20:55:03 you wrote:
> Pär, are you sure that EFER.SVME bit has been set when the error happened?
> Our architecture design team confirmed that enabling EFER.SVME twice won't
> cause any problem (There will be some performance loss though).

No, I am not sure, this is a bit above my level of knowledge. The EFER.SVME 
interpretation was from Anthony when he looked at the panic output.

Output from dmidecode is attached. Please tell me if there is anything else 
you need.

I will take a look in the BIOS again, but I don't remember any virtualization 
options. I am also planning on doing some tests with some other linux 
distribution to rule out the possibility of this being a bug in Ubuntus 
kernel.

regards
Pär

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

# dmidecode 2.8
SMBIOS 2.2 present.
46 structures occupying 1804 bytes.
Table at 0x000F0000.

Handle 0x0000, DMI type 0, 19 bytes
BIOS Information
	Vendor: Phoenix Technologies, LTD
	Version: 6.00 PG
	Release Date: 03/26/2007
	Address: 0xE0000
	Runtime Size: 128 kB
	ROM Size: 512 kB
	Characteristics:
		ISA is supported
		PCI is supported
		PNP is supported
		APM is supported
		BIOS is upgradeable
		BIOS shadowing is allowed
		Boot from CD is supported
		Selectable boot is supported
		BIOS ROM is socketed
		EDD is supported
		5.25"/360 KB floppy services are supported (int 13h)
		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

Handle 0x0001, DMI type 1, 25 bytes
System Information
	Manufacturer: Unknow
	Product Name: Unknow
	Version: Unknow
	Serial Number: Unknow
	UUID: 00000000-0000-0000-0000-00508D97FBDB
	Wake-up Type: Power Switch

Handle 0x0002, DMI type 2, 8 bytes
Base Board Information
	Manufacturer: http://www.abit.com.tw/
	Product Name: KN9 Series(NF-CK804)
	Version: 1.x  
	Serial Number:  

Handle 0x0003, DMI type 3, 13 bytes
Chassis Information
	Manufacturer: Unknow
	Type: Desktop
	Lock: Not Present
	Version: Not Specified
	Serial Number: Not Specified
	Asset Tag: Not Specified
	Boot-up State: Unknown
	Power Supply State: Unknown
	Thermal State: Unknown
	Security Status: Unknown

Handle 0x0004, DMI type 4, 32 bytes
Processor Information
	Socket Designation: Socket AM2 
	Type: Central Processor
	Family: <OUT OF SPEC>
	Manufacturer: AMD
	ID: B1 0F 06 00 FF FB 8B 17
	Version: AMD Athlon(tm) 64 X2 Dual Core Processor 4400+
	Voltage: 1.3 V
	External Clock: 200 MHz
	Max Speed: 3000 MHz
	Current Speed: 2300 MHz
	Status: Populated, Enabled
	Upgrade: Socket 940
	L1 Cache Handle: 0x000B
	L2 Cache Handle: 0x000D
	L3 Cache Handle: No L3 Cache

Handle 0x0005, DMI type 4, 32 bytes
Processor Information
	Socket Designation: Socket AM2 
	Type: Central Processor
	Family: <OUT OF SPEC>
	Manufacturer: AMD
	ID: B1 0F 06 00 FF FB 8B 17
	Version: AMD Athlon(tm) 64 X2 Dual Core Processor 4400+
	Voltage: 1.3 V
	External Clock: 200 MHz
	Max Speed: 3000 MHz
	Current Speed: 2300 MHz
	Status: Populated, Enabled
	Upgrade: Socket 940
	L1 Cache Handle: 0x000C
	L2 Cache Handle: 0x000E
	L3 Cache Handle: No L3 Cache

Handle 0x0006, 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:
		70 ns
		60 ns
		50 ns
	Supported Memory Types:
		Standard
		DIMM
	Memory Module Voltage: 2.9 V
	Associated Memory Slots: 4
		0x0007
		0x0008
		0x0009
		0x000A
	Enabled Error Correcting Capabilities: None

Handle 0x0007, DMI type 6, 12 bytes
Memory Module Information
	Socket Designation: A0
	Bank Connections: 0 1
	Current Speed: 5 ns
	Type: Other Unknown EDO
	Installed Size: 1024 MB (Double-bank Connection)
	Enabled Size: 1024 MB (Double-bank Connection)
	Error Status: OK

Handle 0x0008, DMI type 6, 12 bytes
Memory Module Information
	Socket Designation: A1
	Bank Connections: 2 3
	Current Speed: 5 ns
	Type: Other Unknown EDO
	Installed Size: 1024 MB (Double-bank Connection)
	Enabled Size: 1024 MB (Double-bank Connection)
	Error Status: OK

Handle 0x0009, DMI type 6, 12 bytes
Memory Module Information
	Socket Designation: A2
	Bank Connections: 4 5
	Current Speed: 5 ns
	Type: Other Unknown EDO
	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: A3
	Bank Connections: 6 7
	Current Speed: 5 ns
	Type: Other Unknown EDO
	Installed Size: 1024 MB (Double-bank Connection)
	Enabled Size: 1024 MB (Double-bank Connection)
	Error Status: OK

Handle 0x000B, DMI type 7, 19 bytes
Cache Information
	Socket Designation: Internal Cache
	Configuration: Enabled, Not Socketed, Level 1
	Operational Mode: Write Back
	Location: Internal
	Installed Size: 128 KB
	Maximum Size: 128 KB
	Supported SRAM Types:
		Synchronous
	Installed SRAM Type: Synchronous
	Speed: Unknown
	Error Correction Type: Unknown
	System Type: Unknown
	Associativity: Unknown

Handle 0x000C, DMI type 7, 19 bytes
Cache Information
	Socket Designation: Internal Cache
	Configuration: Enabled, Not Socketed, Level 1
	Operational Mode: Write Back
	Location: Internal
	Installed Size: 128 KB
	Maximum Size: 128 KB
	Supported SRAM Types:
		Synchronous
	Installed SRAM Type: Synchronous
	Speed: Unknown
	Error Correction Type: Unknown
	System Type: Unknown
	Associativity: Unknown

Handle 0x000D, DMI type 7, 19 bytes
Cache Information
	Socket Designation: External Cache
	Configuration: Enabled, Not Socketed, Level 2
	Operational Mode: Write Back
	Location: Internal
	Installed Size: 512 KB
	Maximum Size: 512 KB
	Supported SRAM Types:
		Synchronous
	Installed SRAM Type: Synchronous
	Speed: Unknown
	Error Correction Type: Unknown
	System Type: Unknown
	Associativity: Unknown

Handle 0x000E, DMI type 7, 19 bytes
Cache Information
	Socket Designation: External Cache
	Configuration: Enabled, Not Socketed, Level 2
	Operational Mode: Write Back
	Location: Internal
	Installed Size: 512 KB
	Maximum Size: 512 KB
	Supported SRAM Types:
		Synchronous
	Installed SRAM Type: Synchronous
	Speed: Unknown
	Error Correction Type: Unknown
	System Type: Unknown
	Associativity: Unknown

Handle 0x000F, DMI type 8, 9 bytes
Port Connector Information
	Internal Reference Designator: PRIMARY IDE
	Internal Connector Type: On Board IDE
	External Reference Designator: Not Specified
	External Connector Type: None
	Port Type: Other

Handle 0x0010, DMI type 8, 9 bytes
Port Connector Information
	Internal Reference Designator: SECONDARY IDE
	Internal Connector Type: On Board IDE
	External Reference Designator: Not Specified
	External Connector Type: None
	Port Type: Other

Handle 0x0011, DMI type 8, 9 bytes
Port Connector Information
	Internal Reference Designator: FDD
	Internal Connector Type: On Board Floppy
	External Reference Designator: Not Specified
	External Connector Type: None
	Port Type: 8251 FIFO Compatible

Handle 0x0012, DMI type 8, 9 bytes
Port Connector Information
	Internal Reference Designator: COM1
	Internal Connector Type: 9 Pin Dual Inline (pin 10 cut)
	External Reference Designator:  
	External Connector Type: DB-9 male
	Port Type: Serial Port 16450 Compatible

Handle 0x0013, DMI type 8, 9 bytes
Port Connector Information
	Internal Reference Designator: COM2
	Internal Connector Type: 9 Pin Dual Inline (pin 10 cut)
	External Reference Designator:  
	External Connector Type: DB-9 male
	Port Type: Serial Port 16450 Compatible

Handle 0x0014, DMI type 8, 9 bytes
Port Connector Information
	Internal Reference Designator: LPT1
	Internal Connector Type: DB-25 female
	External Reference Designator:  
	External Connector Type: DB-25 female
	Port Type: Parallel Port ECP/EPP

Handle 0x0015, DMI type 8, 9 bytes
Port Connector Information
	Internal Reference Designator: Keyboard
	Internal Connector Type: PS/2
	External Reference Designator:  
	External Connector Type: PS/2
	Port Type: Keyboard Port

Handle 0x0016, DMI type 8, 9 bytes
Port Connector Information
	Internal Reference Designator: PS/2 Mouse
	Internal Connector Type: PS/2
	External Reference Designator:  
	External Connector Type: PS/2
	Port Type: Mouse Port

Handle 0x0017, DMI type 8, 9 bytes
Port Connector Information
	Internal Reference Designator: Not Specified
	Internal Connector Type: None
	External Reference Designator: USB0
	External Connector Type: Other
	Port Type: USB

Handle 0x0018, DMI type 9, 13 bytes
System Slot Information
	Designation: PCI0
	Type: 32-bit PCI
	Current Usage: In Use
	Length: Long
	ID: 1
	Characteristics:
		5.0 V is provided
		PME signal is supported

Handle 0x0019, DMI type 9, 13 bytes
System Slot Information
	Designation: PCI1
	Type: 32-bit PCI
	Current Usage: In Use
	Length: Long
	ID: 2
	Characteristics:
		5.0 V is provided
		PME signal is supported

Handle 0x001A, DMI type 9, 13 bytes
System Slot Information
	Designation: PCI2
	Type: 32-bit PCI
	Current Usage: In Use
	Length: Long
	ID: 3
	Characteristics:
		5.0 V is provided
		PME signal is supported

Handle 0x001B, DMI type 9, 13 bytes
System Slot Information
	Designation: PCI3
	Type: 32-bit PCI
	Current Usage: Available
	Length: Long
	ID: 4
	Characteristics:
		5.0 V is provided
		PME signal is supported

Handle 0x001C, DMI type 9, 13 bytes
System Slot Information
	Designation: PCI4
	Type: 32-bit PCI Express
	Current Usage: In Use
	Length: Long
	Characteristics:
		5.0 V is provided
		PME signal is supported

Handle 0x001D, DMI type 9, 13 bytes
System Slot Information
	Designation: PCI5
	Type: 32-bit PCI Express
	Current Usage: In Use
	Length: Long
	Characteristics:
		5.0 V is provided
		PME signal is supported

Handle 0x001E, DMI type 9, 13 bytes
System Slot Information
	Designation: PCI6
	Type: 32-bit PCI Express
	Current Usage: In Use
	Length: Long
	Characteristics:
		5.0 V is provided
		PME signal is supported

Handle 0x001F, DMI type 13, 22 bytes
BIOS Language Information
	Installable Languages: 3
		n|US|iso8859-1
		n|US|iso8859-1
		r|CA|iso8859-1
	Currently Installed Language: n|US|iso8859-1

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

Handle 0x0021, DMI type 17, 21 bytes
Memory Device
	Array Handle: 0x0020
	Error Information Handle: Not Provided
	Total Width: 64 bits
	Data Width: 64 bits
	Size: 1024 MB
	Form Factor: DIMM
	Set: None
	Locator: A0
	Bank Locator: Bank0/1
	Type: Unknown
	Type Detail: None

Handle 0x0022, DMI type 17, 21 bytes
Memory Device
	Array Handle: 0x0020
	Error Information Handle: Not Provided
	Total Width: 64 bits
	Data Width: 64 bits
	Size: 1024 MB
	Form Factor: DIMM
	Set: None
	Locator: A1
	Bank Locator: Bank2/3
	Type: Unknown
	Type Detail: None

Handle 0x0023, DMI type 17, 21 bytes
Memory Device
	Array Handle: 0x0020
	Error Information Handle: Not Provided
	Total Width: 64 bits
	Data Width: 64 bits
	Size: 1024 MB
	Form Factor: DIMM
	Set: None
	Locator: A2
	Bank Locator: Bank4/5
	Type: Unknown
	Type Detail: None

Handle 0x0024, DMI type 17, 21 bytes
Memory Device
	Array Handle: 0x0020
	Error Information Handle: Not Provided
	Total Width: 64 bits
	Data Width: 64 bits
	Size: 1024 MB
	Form Factor: DIMM
	Set: None
	Locator: A3
	Bank Locator: Bank6/7
	Type: Unknown
	Type Detail: None

Handle 0x0025, DMI type 19, 15 bytes
Memory Array Mapped Address
	Starting Address: 0x00000000000
	Ending Address: 0x000FFFFFFFF
	Range Size: 4 GB
	Physical Array Handle: 0x0020
	Partition Width: 0

Handle 0x0026, DMI type 20, 19 bytes
Memory Device Mapped Address
	Starting Address: 0x00000000000
	Ending Address: 0x0003FFFFFFF
	Range Size: 1 GB
	Physical Device Handle: 0x0021
	Memory Array Mapped Address Handle: 0x0025
	Partition Row Position: 1

Handle 0x0027, DMI type 20, 19 bytes
Memory Device Mapped Address
	Starting Address: 0x00040000000
	Ending Address: 0x0007FFFFFFF
	Range Size: 1 GB
	Physical Device Handle: 0x0022
	Memory Array Mapped Address Handle: 0x0025
	Partition Row Position: 1

Handle 0x0028, DMI type 20, 19 bytes
Memory Device Mapped Address
	Starting Address: 0x00080000000
	Ending Address: 0x000BFFFFFFF
	Range Size: 1 GB
	Physical Device Handle: 0x0023
	Memory Array Mapped Address Handle: 0x0025
	Partition Row Position: 1

Handle 0x0029, DMI type 20, 19 bytes
Memory Device Mapped Address
	Starting Address: 0x000C0000000
	Ending Address: 0x000FFFFFFFF
	Range Size: 1 GB
	Physical Device Handle: 0x0024
	Memory Array Mapped Address Handle: 0x0025
	Partition Row Position: 1

Handle 0x002A, DMI type 32, 11 bytes
System Boot Information
	Status: No errors detected

Handle 0x002B, DMI type 188, 255 bytes
OEM-specific Type
	Header and Data:
		BC FF 2B 00 4B 38 4E 50 54 44 52 41 4D 30 03 00
		00 00 00 00 3F 01 00 00 00 00 01 00 00 00 00 00
		00 00 02 00 00 00 00 00 00 00 03 00 00 00 00 00
		00 00 04 00 00 00 00 00 00 00 05 00 00 00 00 00
		00 00 06 00 00 00 00 00 00 00 07 00 00 00 01 40
		00 C0 40 00 10 0A 00 00 00 00 00 00 05 00 EB 02
		00 0C 01 00 00 00 01 01 00 00 01 02 00 00 01 03
		00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
		00 00 E0 3C F8 00 E0 3C F8 00 00 00 00 00 00 00
		00 00 46 00 00 00 00 00 00 00 22 00 00 00 00 00
		00 00 24 D2 7A 0C 20 13 92 00 30 08 01 00 6B 80
		10 74 88 88 FF FE 15 14 15 15 14 15 17 17 15 00
		00 00 17 17 16 16 17 17 17 17 17 00 00 00 2F 35
		00 00 15 14 14 14 15 15 14 14 15 16 18 18 17 16
		15 16 15 16 30 36 00 00 22 33 11 10 20 25 20 00
		22 33 11 10 20 25 20 00 00 00 00 00 00 00 00
	Strings:
		 

Handle 0x002C, DMI type 190, 255 bytes
OEM-specific Type
	Header and Data:
		BE FF 2C 00 00 00 00 C0 00 00 00 00 00 00 00 40
		01 00 00 00 01 06 76 00 00 00 00 00 00 00 00 00
		00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
		00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
		00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
		00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
		00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
		00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
		00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
		00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
		00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
		00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
		00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
		00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
		00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
		00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
	Strings:
		 

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


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

-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/

[-- 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

^ permalink raw reply	[flat|nested] 9+ messages in thread

* Re: Kernel panic when loading kvm-amd
       [not found]                           ` <465FB4D4.6030509-5C7GfCeVMHo@public.gmane.org>
@ 2007-06-01 12:59                             ` Pär Andersson
  0 siblings, 0 replies; 9+ messages in thread
From: Pär Andersson @ 2007-06-01 12:59 UTC (permalink / raw)
  To: Wei Huang; +Cc: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f

On Friday 01 June 2007 07:55:32 you wrote:
> Pär,
>
> Your CPU is AMD Athlon Rev G, which should support SVM. I happened to
> have a Rev G CPU at hand. I will install Ubuntu 64 myself tomorrow and
> see whether I can re-produce the problem.
>
> By any chance, could you can try the following tests?
>
> 1. Try other Linux distributions.
> 2. Try Ubuntu 32Bit instead of 64Bit. My laptop has Turion x2, which
> runs KVM 24 on Ubuntu 32bit without any problem.
>
> Thanks,
>
> -Wei

Testing with other Linux distributions was already on my TODO list as I 
mentioned before. However this won't be necessary any more as I yesterday got 
KVM to work with my normal kernel. :-)

I went through my BIOS settings and found:
"Advanced BIOS Features" -> "CPU Feature" -> Virtualization

However this was already set to "Enabled". I tried changing the value 
to "Disabled" and now KVM works fine. Stupid ABIT...


If you try to change KVM to detect BIOS disabled SVM (or Enabled, in ABITs 
case...) instead of panicing I will be glad to help test that.

regards
Pär Andersson

-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/

^ permalink raw reply	[flat|nested] 9+ messages in thread

end of thread, other threads:[~2007-06-01 12:59 UTC | newest]

Thread overview: 9+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2007-05-28  1:29 Kernel panic when loading kvm-amd Pär Andersson
     [not found] ` <200705280330.19290.paran-SamgB31n2u5IcsJQ0EH25Q@public.gmane.org>
2007-05-28 20:16   ` Anthony Liguori
     [not found]     ` <465B3885.2070401-rdkfGonbjUSkNkDKm+mE6A@public.gmane.org>
2007-05-29  8:20       ` Avi Kivity
     [not found]         ` <465BE236.4020805-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-05-29 16:13           ` Huang2, Wei
     [not found]             ` <7D748C767B7FA541A8AC5504A4C89A2302FEBD35-SXV0rU3j2e+jL8BtgrxzBQC/G2K4zDHf@public.gmane.org>
2007-05-29 18:16               ` Avi Kivity
     [not found]                 ` <465C6E0A.6030008-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-05-29 18:55                   ` Huang2, Wei
     [not found]                     ` <7D748C767B7FA541A8AC5504A4C89A2302FEBE97-SXV0rU3j2e+jL8BtgrxzBQC/G2K4zDHf@public.gmane.org>
2007-05-30  4:56                       ` Avi Kivity
2007-05-31 12:21                       ` Pär Andersson
     [not found]                         ` <465FB4D4.6030509@amd.com>
     [not found]                           ` <465FB4D4.6030509-5C7GfCeVMHo@public.gmane.org>
2007-06-01 12:59                             ` Pär Andersson

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox