[Bug 732693] New: hv_vmbus: Unable to intialize the hypervisor on first boot after install

bugzilla_noreply＠novell.com

24 Nov 2011 24 Nov '11

22:36

https://bugzilla.novell.com/show_bug.cgi?id=732693 https://bugzilla.novell.com/show_bug.cgi?id=732693#c0 Summary: hv_vmbus: Unable to intialize the hypervisor on first boot after install Classification: openSUSE Product: openSUSE 12.1 Version: Final Platform: Other OS/Version: SuSE Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel AssignedTo: kernel-maintainers@forge.provo.novell.com ReportedBy: mike@surcouf.co.uk QAContact: qa@suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_7_2) AppleWebKit/534.51.22 (KHTML, like Gecko) Version/5.1.1 Safari/534.51.22 Installing 12.1 text server mode on hyper-v after the first reboot I get doing fast boot FATAL: Module ata_piix not found FATAL: Error running install command for ata_Piix Creating device nodes with udev [ 11.057946] hv_vmbus: Unable to intialize the hypervisor - 0xfffffdf4 udev[157]: failed to execute '/etc/sysconfig/network/scripts/ifup-sysctl' '/etc/sysconfig/network/scripts/ifup-sysctl lo -o hotplug': No such file or directory Then of course the disk can't be seen as the hypervisor disables the ata_piix drivers. Turning the vm off and then on resumes the install ok and hypervisor loads and the disks are seen I always get the '/etc/sysconfig/network/scripts/ifup-sysctl' error on each reboot though Tried it a few times and always fails on first reboot after install so it is repo in my environment. Doesnt seem to have any adverse effects after the first failed reboot. Any ideas. What category of bugzilla should this go in. Many Thanks Mike Reproducible: Always Steps to Reproduce: 1.do minimal install of openSUSE 12.1 on hyper 2.during first reboot get message above and no access to disk so boot fails 3.Turn off virtual machine and turn back on 4.hv_vmbus loads this time and installation continues ok. Actual Results: error message hv_vmbus: Unable to intialize the hypervisor message followed by failed detection of root partition and thus boot failure Expected Results: installation reboot should not fail and should not require a forced power cycle to resolve -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

Show replies by date

bugzilla_noreply＠novell.com

24 Nov 24 Nov

22:39

New subject: [Bug 732693] hv_vmbus: Unable to intialize the hypervisor on first reboot during install

https://bugzilla.novell.com/show_bug.cgi?id=732693 https://bugzilla.novell.com/show_bug.cgi?id=732693#c Mike Surcouf changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|hv_vmbus: Unable to |hv_vmbus: Unable to |intialize the hypervisor on |intialize the hypervisor on |first boot after install |first reboot during install -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

bugzilla_noreply＠novell.com

25 Nov 25 Nov

16:14

New subject: [Bug 732693] hv_vmbus: Unable to intialize the hypervisor on first reboot during install

https://bugzilla.novell.com/show_bug.cgi?id=732693 https://bugzilla.novell.com/show_bug.cgi?id=732693#c Greg Kroah-Hartman changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|kernel-maintainers@forge.pr |ohering@suse.com |ovo.novell.com | -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

bugzilla_noreply＠novell.com

16:39

New subject: [Bug 732693] hv_vmbus: Unable to intialize the hypervisor on first reboot during install

https://bugzilla.novell.com/show_bug.cgi?id=732693 https://bugzilla.novell.com/show_bug.cgi?id=732693#c1 Olaf Hering changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO InfoProvider| |mike@surcouf.co.uk --- Comment #1 from Olaf Hering 2011-11-25 17:39:07 CET --- What host is this? Is the guest 32bit? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

bugzilla_noreply＠novell.com

16:42

New subject: [Bug 732693] hv_vmbus: Unable to intialize the hypervisor on first reboot during install

https://bugzilla.novell.com/show_bug.cgi?id=732693 https://bugzilla.novell.com/show_bug.cgi?id=732693#c2 Mike Surcouf changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW InfoProvider|mike@surcouf.co.uk | --- Comment #2 from Mike Surcouf 2011-11-25 16:42:08 UTC --- Hi Olaf openSUSE 32bit uname -a Linux aestest 3.1.0-1.2-desktop #1 SMP PREEMPT Thu Nov 3 14:45:45 UTC 2011 (187dde0) i686 i686 i386 GNU/Linux host is 2008 R2 sp1 Thanks anything else let me know -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

bugzilla_noreply＠novell.com

17:07

New subject: [Bug 732693] hv_vmbus: Unable to intialize the hypervisor on first reboot during install

https://bugzilla.novell.com/show_bug.cgi?id=732693 https://bugzilla.novell.com/show_bug.cgi?id=732693#c3 --- Comment #3 from Mike Surcouf 2011-11-25 17:07:52 UTC --- Just had a thought noticed the install routine uses kexec to reboot kernel just before this error rather than a full reboot. COuld be irrelavent but thought I'd mention it -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

bugzilla_noreply＠novell.com

17:47

New subject: [Bug 732693] hv_vmbus: Unable to intialize the hypervisor on first reboot during install

https://bugzilla.novell.com/show_bug.cgi?id=732693 https://bugzilla.novell.com/show_bug.cgi?id=732693#c4 Olaf Hering changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |ohering@suse.com AssignedTo|ohering@suse.com |kys@microsoft.com --- Comment #4 from Olaf Hering 2011-11-25 18:47:29 CET --- Yes, thats the cause. Currently the hv drivers have no kexec nor kdump support. This is something for KY to implement at some point. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

bugzilla_noreply＠novell.com

4 Dec 4 Dec

22:51

New subject: [Bug 732693] hv_vmbus: Unable to intialize the hypervisor on first reboot during install

https://bugzilla.novell.com/show_bug.cgi?id=732693 https://bugzilla.novell.com/show_bug.cgi?id=732693#c5 --- Comment #5 from Kattiganehalli srinivasan 2011-12-04 22:51:30 UTC --- Olaf is right; we do have an issue with kexec. Once we exit staging, I am going to look into this. Olaf is there a workaround here. If not, I will have to mark it won't fix for sometime. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

bugzilla_noreply＠novell.com

5 Dec 5 Dec

07:50

New subject: [Bug 732693] hv_vmbus: Unable to intialize the hypervisor on first reboot during install

https://bugzilla.novell.com/show_bug.cgi?id=732693 https://bugzilla.novell.com/show_bug.cgi?id=732693#c6 --- Comment #6 from Olaf Hering 2011-12-05 08:50:09 CET --- Booting the installer with the "kexec=0" kernel cmdline option is supposed to avoid using kexec for the very first reboot. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

bugzilla_noreply＠novell.com

09:27

New subject: [Bug 732693] hv_vmbus: Unable to intialize the hypervisor on first reboot during install

https://bugzilla.novell.com/show_bug.cgi?id=732693 https://bugzilla.novell.com/show_bug.cgi?id=732693#c7 --- Comment #7 from Mike Surcouf 2011-12-05 09:27:34 UTC --- Hi Olaf Sorry to sound a bit dim but how excactly do I do that. Currently I am mounting the iso to a virtual machine and booting from that so all the files are read only. I dont have a commandline before booting from the isao. Thanks Mike -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

bugzilla_noreply＠novell.com

10:50

New subject: [Bug 732693] hv_vmbus: Unable to intialize the hypervisor on first reboot during install

https://bugzilla.novell.com/show_bug.cgi?id=732693 https://bugzilla.novell.com/show_bug.cgi?id=732693#c8 --- Comment #8 from Olaf Hering 2011-12-05 11:50:15 CET --- Its the graphical boot screen with 'boot from hard disk', 'Installation', 'rescue' etc. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

bugzilla_noreply＠novell.com

11:00

New subject: [Bug 732693] hv_vmbus: Unable to intialize the hypervisor on first reboot during install

https://bugzilla.novell.com/show_bug.cgi?id=732693 https://bugzilla.novell.com/show_bug.cgi?id=732693#c9 --- Comment #9 from Kattiganehalli srinivasan 2011-12-05 11:00:03 UTC --- Ok. I have on my plate to deal with kexec properly once other higher priority issues are dealt with. Also, if I recall correctly, there were some host side issues that made re-loading of the vmbus driver impossible (don't recall all the details). Now that there is a work around, Olaf, perhaps you can close this bug with documentation. If and when I deal with Kexec issues, this bug and other bugs (kdump etc.) will be addressed. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

bugzilla_noreply＠novell.com

8 Jan 8 Jan

18:56

New subject: [Bug 732693] hv_vmbus: Unable to intialize the hypervisor on first reboot during install

https://bugzilla.novell.com/show_bug.cgi?id=732693 https://bugzilla.novell.com/show_bug.cgi?id=732693#c10 Kattiganehalli srinivasan changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |WONTFIX --- Comment #10 from Kattiganehalli srinivasan 2012-01-08 18:56:47 UTC --- kexec cannot be supported anytime soon. I have notified the Hyper-V team about the need to be able to reset the vmbus connection which is required for kexec. I am going to close this bug as it cannot be fixed now. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

bugzilla_noreply＠novell.com

9 Jan 9 Jan

15:34

New subject: [Bug 732693] hv_vmbus: Unable to intialize the hypervisor on first reboot during install

https://bugzilla.novell.com/show_bug.cgi?id=732693 https://bugzilla.novell.com/show_bug.cgi?id=732693#c11 --- Comment #11 from Mike Surcouf 2012-01-09 15:34:35 UTC --- Prehaps openSUSE could drop the kexec from the install routine. I am sure there are other drivers out there that can't/are not supporting kexec and it seems to only save a small ammount of time vs full reboot. After all problems with install always give a negative first impression. Thanks Mike -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

bugzilla_noreply＠novell.com

15:52

New subject: [Bug 732693] hv_vmbus: Unable to intialize the hypervisor on first reboot during install

https://bugzilla.novell.com/show_bug.cgi?id=732693 https://bugzilla.novell.com/show_bug.cgi?id=732693#c12 Olaf Hering changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|WONTFIX | AssignedTo|kys@microsoft.com |yast2-maintainers@suse.de --- Comment #12 from Olaf Hering 2012-01-09 16:52:04 CET --- (In reply to comment #11)

...

Prehaps openSUSE could drop the kexec from the install routine. I am sure there are other drivers out there that can't/are not supporting kexec and it seems to only save a small ammount of time vs full reboot. After all problems with install always give a negative first impression.

I think VirtualBox has a similar issue, and yast has code to detect this and not use kexec for reboot. Perhaps that part of yast should be extended to recognize also a hyper-v guest. Therefor I reopen that bug and assign it to the yast2 maintainers. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

bugzilla_noreply＠novell.com

15:53

New subject: [Bug 732693] hv_vmbus: Unable to intialize the hypervisor on first reboot during install

https://bugzilla.novell.com/show_bug.cgi?id=732693 https://bugzilla.novell.com/show_bug.cgi?id=732693#c13 --- Comment #13 from Olaf Hering 2012-01-09 16:53:50 CET --- And the workaround for 12.1 installation would be to boot the installation with kexec_reboot=0, according to http://en.opensuse.org/SDB:Linuxrc -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

bugzilla_noreply＠novell.com

17:16

New subject: [Bug 732693] hv_vmbus: Unable to intialize the hypervisor on first reboot during install

https://bugzilla.novell.com/show_bug.cgi?id=732693 https://bugzilla.novell.com/show_bug.cgi?id=732693#c Arvin Schnell changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|yast2-maintainers@suse.de |jsuchome@suse.com -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

bugzilla_noreply＠novell.com

10 Jan 10 Jan

10:23

New subject: [Bug 732693] hv_vmbus: Unable to intialize the hypervisor on first reboot during install

https://bugzilla.novell.com/show_bug.cgi?id=732693 https://bugzilla.novell.com/show_bug.cgi?id=732693#c Jiří Suchomel changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|jsuchome@suse.com |mvidner@suse.com -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

bugzilla_noreply＠novell.com

10 Apr 10 Apr

12:09

New subject: [Bug 732693] hv_vmbus: Unable to intialize the hypervisor on first reboot during install

https://bugzilla.novell.com/show_bug.cgi?id=732693 https://bugzilla.novell.com/show_bug.cgi?id=732693#c14 --- Comment #14 from Mike Surcouf 2012-04-10 12:09:38 UTC --- On Hyper-V openSUSE 12.1 install hwinfo --bios |grep Product gives output Product Product id: "HYPERV" Product: "Virtual Machine" Product: "Virtual Machine" I have never contributed to factory and did have a look at the process but not confident enought to submit this in the right way The following code inserted just after the Virtualbox check code in Bootloader.ycp should resolve the issue. Hopefully someone more experienced could submit this for me. Thanks Mike code below.... // checking if installation run on Hyper-V string cmd = sformat("hwinfo --bios |grep Product"); y2milestone("Checking if installation run on Hyper-V command: %1", cmd); map out = (map)WFM::Execute(.local.bash_output, cmd); if (search(out["stdout"]:"", "HYPERV") != nil) { y2milestone ("Installation run on Hyper-V, skip kexec loading: %1", out); return false; } -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

bugzilla_noreply＠novell.com

17 Apr 17 Apr

14:27

New subject: [Bug 732693] hv_vmbus: Unable to intialize the hypervisor on first reboot during install

https://bugzilla.novell.com/show_bug.cgi?id=732693 https://bugzilla.novell.com/show_bug.cgi?id=732693#c15 --- Comment #15 from Mike Surcouf 2012-04-17 14:27:23 UTC --- OK I think I did it right Code submitted under Request 114180 -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

bugzilla_noreply＠novell.com

21:34

New subject: [Bug 732693] hv_vmbus: Unable to intialize the hypervisor on first reboot during install

https://bugzilla.novell.com/show_bug.cgi?id=732693 https://bugzilla.novell.com/show_bug.cgi?id=732693#c16 --- Comment #16 from Mike Surcouf 2012-04-17 21:34:00 UTC --- Now submitted under Request 114237 -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

bugzilla_noreply＠novell.com

23 Apr 23 Apr

13:02

New subject: [Bug 732693] hv_vmbus: Unable to intialize the hypervisor on first reboot during install

https://bugzilla.novell.com/show_bug.cgi?id=732693 https://bugzilla.novell.com/show_bug.cgi?id=732693#c17 Steffen Winterfeldt changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |NEEDINFO InfoProvider| |mike@surcouf.co.uk AssignedTo|mvidner@suse.com |snwint@suse.com --- Comment #17 from Steffen Winterfeldt 2012-04-23 15:02:14 CEST --- Mike, could you please attach the complete output of 'hwinfo --bios' from a hyperv machine? I don't like running external programs just for this (and also not for the vbox check). -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

bugzilla_noreply＠novell.com

14:35

New subject: [Bug 732693] hv_vmbus: Unable to intialize the hypervisor on first reboot during install

https://bugzilla.novell.com/show_bug.cgi?id=732693 https://bugzilla.novell.com/show_bug.cgi?id=732693#c18 Mike Surcouf changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |REOPENED InfoProvider|mike@surcouf.co.uk | Severity|Normal |Major --- Comment #18 from Mike Surcouf 2012-04-23 14:32:02 UTC --- Hi Steffen Tried to attach but couldn't (browser issue?) so here is the output in-line sorry Thanks Mike # hwinfo --bios 01: None 00.0: 10105 BIOS [Created at bios.189] Unique ID: rdCR.lZF+r4EgHp4 Hardware Class: bios BIOS Keyboard LED Status: Scroll Lock: off Num Lock: off Caps Lock: off Serial Port 0: 0x3f8 Serial Port 1: 0x2f8 Base Memory: 639 kB PnP BIOS: @@@0000 BIOS: extended read supported MP spec rev 1.4 info: OEM id: "MICROSFT" Product id: "HYPERV" 8 CPUs (7 disabled) SMBIOS Version: 2.3 BIOS Info: #0 Vendor: "American Megatrends Inc." Version: "090004" Date: "03/19/2009" Start Address: 0xf0000 ROM Size: 256 kB Features: 0x0134000000007fcbda90 ISA supported PCI supported PnP supported BIOS flashable BIOS shadowing allowed ESCD supported CD boot supported Selectable boot supported BIOS ROM socketed EDD spec supported 360kB Floppy supported 1.2MB Floppy supported 720kB Floppy supported 2.88MB Floppy supported Print Screen supported 8042 Keyboard Services supported Serial Services supported Printer Services supported CGA/Mono Video supported AGP supported LS-120 boot supported ATAPI ZIP boot supported BIOS Boot Spec supported System Info: #1 Manufacturer: "Microsoft Corporation" Product: "Virtual Machine" Version: "7.0" Serial: "5168-1304-2189-7471-5217-3250-94" UUID: undefined, but settable Wake-up: 0x06 (Power Switch) Board Info: #2 Manufacturer: "Microsoft Corporation" Product: "Virtual Machine" Version: "7.0" Serial: "5168-1304-2189-7471-5217-3250-94" Chassis Info: #3 Manufacturer: "Microsoft Corporation" Version: "7.0" Serial: "5168-1304-2189-7471-5217-3250-94" Asset Tag: "2969-6757-6186-1721-9832-4613-99" Type: 0x03 (Desktop) Bootup State: 0x03 (Safe) Power Supply State: 0x03 (Safe) Thermal State: 0x01 (Other) Security Status: 0x01 (Other) OEM Strings: #4 [MS_VM_CERT/SHA1/9b80ca0d5dd061ec9da4e494f4c3fd1196270c22] 00000000000000000000000000000000 To be filed by MSFT Processor Info: #5 Socket: "None" Socket Type: 0x06 (None) Socket Status: Populated Type: 0x03 (CPU) Family: 0xb3 (Xeon) Manufacturer: "Intel" Version: "Intel(R) Xeon(R) CPU E5520 @ 2.27GHz" Serial: "None" Asset Tag: "None" Part Number: "None" Processor ID: 0x1f8bfbff000106a5 Status: 0x01 (Enabled) Voltage: 1.2 V External Clock: 5860 MHz Max. Speed: 3600 MHz Current Speed: 2266 MHz Processor Info: #6 Socket: "None" Socket Type: 0x06 (None) Socket Status: Empty Type: 0x03 (CPU) Family: 0x02 (Unknown) Manufacturer: "None" Version: "None" Serial: "None" Asset Tag: "None" Part Number: "None" Status: 0x00 (Unknown) Voltage: 2.9 V Processor Info: #7 Socket: "None" Socket Type: 0x06 (None) Socket Status: Empty Type: 0x03 (CPU) Family: 0x02 (Unknown) Manufacturer: "None" Version: "None" Serial: "None" Asset Tag: "None" Part Number: "None" Status: 0x00 (Unknown) Voltage: 2.9 V Processor Info: #8 Socket: "None" Socket Type: 0x06 (None) Socket Status: Empty Type: 0x03 (CPU) Family: 0x02 (Unknown) Manufacturer: "None" Version: "None" Serial: "None" Asset Tag: "None" Part Number: "None" Status: 0x00 (Unknown) Voltage: 2.9 V Processor Info: #9 Socket: "None" Socket Type: 0x06 (None) Socket Status: Empty Type: 0x03 (CPU) Family: 0x02 (Unknown) Manufacturer: "None" Version: "None" Serial: "None" Asset Tag: "None" Part Number: "None" Status: 0x00 (Unknown) Voltage: 2.9 V Processor Info: #10 Socket: "None" Socket Type: 0x06 (None) Socket Status: Empty Type: 0x03 (CPU) Family: 0x02 (Unknown) Manufacturer: "None" Version: "None" Serial: "None" Asset Tag: "None" Part Number: "None" Status: 0x00 (Unknown) Voltage: 2.9 V Processor Info: #11 Socket: "None" Socket Type: 0x06 (None) Socket Status: Empty Type: 0x03 (CPU) Family: 0x02 (Unknown) Manufacturer: "None" Version: "None" Serial: "None" Asset Tag: "None" Part Number: "None" Status: 0x00 (Unknown) Voltage: 2.9 V Processor Info: #12 Socket: "None" Socket Type: 0x06 (None) Socket Status: Empty Type: 0x03 (CPU) Family: 0x02 (Unknown) Manufacturer: "None" Version: "None" Serial: "None" Asset Tag: "None" Part Number: "None" Status: 0x00 (Unknown) Voltage: 2.9 V Port Connector: #13 Type: 0x10 (USB) Internal Designator: "USB" Internal Connector: 0x01 (Centronics) External Designator: "USB1" External Connector: 0x01 (Centronics) Port Connector: #14 Type: 0x10 (USB) Internal Designator: "USB" Internal Connector: 0x01 (Centronics) External Designator: "USB2" External Connector: 0x01 (Centronics) Port Connector: #15 Type: 0x09 (Serial Port 16550A Compatible) Internal Designator: "COM1" Internal Connector: 0x09 (DB-9 pin female) External Designator: "COM1" External Connector: 0x09 (DB-9 pin female) Port Connector: #16 Type: 0x09 (Serial Port 16550A Compatible) Internal Designator: "COM2" Internal Connector: 0x09 (DB-9 pin female) External Designator: "COM2" External Connector: 0x09 (DB-9 pin female) Port Connector: #17 Type: 0x05 (Parallel Port ECP/EPP) Internal Designator: "Printer" Internal Connector: 0x04 (DB-25 pin male) External Designator: "Lpt1" External Connector: 0x04 (DB-25 pin male) Port Connector: #18 Type: 0x1c (Video Port) Internal Designator: "Video" Internal Connector: 0x06 (DB-15 pin male) External Designator: "Video" External Connector: 0x07 (DB-15 pin female) Port Connector: #19 Type: 0x0d (Keyboard Port) Internal Designator: "Keyboard" Internal Connector: 0x0f (PS/2) External Designator: "Keyboard" External Connector: 0x0f (PS/2) Port Connector: #20 Type: 0x0e (Mouse Port) Internal Designator: "Mouse" Internal Connector: 0x0f (PS/2) External Designator: "Mouse" External Connector: 0x0f (PS/2) On Board Devices: #21 Video: "To Be filled by O.E.M." System Config Options (Jumpers & Switches) #22: To Be Filled By O.E.M. To Be Filled By O.E.M. To Be Filled By O.E.M. Language Info: #23 Languages: enUS Current: enUS 32bit-Memory Error Info: #24 Type: 0x03 (OK) Granularity: 0x02 (Unknown) Operation: 0x02 (Unknown) Physical Memory Array: #25 Use: 0x03 (System memory) Location: 0x02 (Unknown) Slots: 64 ECC: 0x03 (None) Error Info: #24 Memory Array Mapping: #26 Memory Array: #25 Partition Width: 1 Start Address: 0x00000000 End Address: 0x40000400 Inactive Record: #27 Data 00: 7e 0f 1b 00 00 00 00 00 00 00 00 00 19 00 ff Memory Device: #28 Location: "M0" Bank: "None" Manufacturer: "Microsoft" Serial: "None" Asset Tag: "None" Part Number: "None" Memory Array: #25 Error Info: #24 Form Factor: 0x02 (Unknown) Type: 0x01 (Other) Type Detail: 0x0004 (Unknown) Data Width: 0 bits Size: 1 GB Memory Device Mapping: #29 Memory Device: #28 Array Mapping: #26 Row: 0 Interleave Pos: 0 Interleaved Depth: 0 Start Address: 0x00000000 End Address: 0x40000400 Memory Device: #30 Location: "M1" Bank: "None" Manufacturer: "Microsoft" Serial: "None" Asset Tag: "None" Part Number: "None" Memory Array: #25 Error Info: #24 Form Factor: 0x02 (Unknown) Type: 0x01 (Other) Type Detail: 0x0004 (Unknown) Data Width: 0 bits Size: No Memory Installed Inactive Record: #31 Data 00: 7e 13 1f 00 00 00 00 00 00 00 00 00 1e 00 1b 00 Data 10: 00 00 00 Memory Device: #32 Location: "M2" Bank: "None" Manufacturer: "Microsoft" Serial: "None" Asset Tag: "None" Part Number: "None" Memory Array: #25 Error Info: #24 Form Factor: 0x02 (Unknown) Type: 0x01 (Other) Type Detail: 0x0004 (Unknown) Data Width: 0 bits Size: No Memory Installed Inactive Record: #33 Data 00: 7e 13 21 00 00 00 00 00 00 00 00 00 20 00 1b 00 Data 10: 00 00 00 Memory Device: #34 Location: "M3" Bank: "None" Manufacturer: "Microsoft" Serial: "None" Asset Tag: "None" Part Number: "None" Memory Array: #25 Error Info: #24 Form Factor: 0x02 (Unknown) Type: 0x01 (Other) Type Detail: 0x0004 (Unknown) Data Width: 0 bits Size: No Memory Installed Inactive Record: #35 Data 00: 7e 13 23 00 00 00 00 00 00 00 00 00 22 00 1b 00 Data 10: 00 00 00 Memory Device: #36 Location: "M4" Bank: "None" Manufacturer: "Microsoft" Serial: "None" Asset Tag: "None" Part Number: "None" Memory Array: #25 Error Info: #24 Form Factor: 0x02 (Unknown) Type: 0x01 (Other) Type Detail: 0x0004 (Unknown) Data Width: 0 bits Size: No Memory Installed Inactive Record: #37 Data 00: 7e 13 25 00 00 00 00 00 00 00 00 00 24 00 1b 00 Data 10: 00 00 00 Memory Device: #38 Location: "M5" Bank: "None" Manufacturer: "Microsoft" Serial: "None" Asset Tag: "None" Part Number: "None" Memory Array: #25 Error Info: #24 Form Factor: 0x02 (Unknown) Type: 0x01 (Other) Type Detail: 0x0004 (Unknown) Data Width: 0 bits Size: No Memory Installed Inactive Record: #39 Data 00: 7e 13 27 00 00 00 00 00 00 00 00 00 26 00 1b 00 Data 10: 00 00 00 Memory Device: #40 Location: "M6" Bank: "None" Manufacturer: "Microsoft" Serial: "None" Asset Tag: "None" Part Number: "None" Memory Array: #25 Error Info: #24 Form Factor: 0x02 (Unknown) Type: 0x01 (Other) Type Detail: 0x0004 (Unknown) Data Width: 0 bits Size: No Memory Installed Inactive Record: #41 Data 00: 7e 13 29 00 00 00 00 00 00 00 00 00 28 00 1b 00 Data 10: 00 00 00 Memory Device: #42 Location: "M7" Bank: "None" Manufacturer: "Microsoft" Serial: "None" Asset Tag: "None" Part Number: "None" Memory Array: #25 Error Info: #24 Form Factor: 0x02 (Unknown) Type: 0x01 (Other) Type Detail: 0x0004 (Unknown) Data Width: 0 bits Size: No Memory Installed Inactive Record: #43 Data 00: 7e 13 2b 00 00 00 00 00 00 00 00 00 2a 00 1b 00 Data 10: 00 00 00 Memory Device: #44 Location: "M8" Bank: "None" Manufacturer: "Microsoft" Serial: "None" Asset Tag: "None" Part Number: "None" Memory Array: #25 Error Info: #24 Form Factor: 0x02 (Unknown) Type: 0x01 (Other) Type Detail: 0x0004 (Unknown) Data Width: 0 bits Size: No Memory Installed Inactive Record: #45 Data 00: 7e 13 2d 00 00 00 00 00 00 00 00 00 2c 00 1b 00 Data 10: 00 00 00 Memory Device: #46 Location: "M9" Bank: "None" Manufacturer: "Microsoft" Serial: "None" Asset Tag: "None" Part Number: "None" Memory Array: #25 Error Info: #24 Form Factor: 0x02 (Unknown) Type: 0x01 (Other) Type Detail: 0x0004 (Unknown) Data Width: 0 bits Size: No Memory Installed Inactive Record: #47 Data 00: 7e 13 2f 00 00 00 00 00 00 00 00 00 2e 00 1b 00 Data 10: 00 00 00 Memory Device: #48 Location: "M10" Bank: "None" Manufacturer: "Microsoft" Serial: "None" Asset Tag: "None" Part Number: "None" Memory Array: #25 Error Info: #24 Form Factor: 0x02 (Unknown) Type: 0x01 (Other) Type Detail: 0x0004 (Unknown) Data Width: 0 bits Size: No Memory Installed Inactive Record: #49 Data 00: 7e 13 31 00 00 00 00 00 00 00 00 00 30 00 1b 00 Data 10: 00 00 00 Memory Device: #50 Location: "M11" Bank: "None" Manufacturer: "Microsoft" Serial: "None" Asset Tag: "None" Part Number: "None" Memory Array: #25 Error Info: #24 Form Factor: 0x02 (Unknown) Type: 0x01 (Other) Type Detail: 0x0004 (Unknown) Data Width: 0 bits Size: No Memory Installed Inactive Record: #51 Data 00: 7e 13 33 00 00 00 00 00 00 00 00 00 32 00 1b 00 Data 10: 00 00 00 Memory Device: #52 Location: "M12" Bank: "None" Manufacturer: "Microsoft" Serial: "None" Asset Tag: "None" Part Number: "None" Memory Array: #25 Error Info: #24 Form Factor: 0x02 (Unknown) Type: 0x01 (Other) Type Detail: 0x0004 (Unknown) Data Width: 0 bits Size: No Memory Installed Inactive Record: #53 Data 00: 7e 13 35 00 00 00 00 00 00 00 00 00 34 00 1b 00 Data 10: 00 00 00 Memory Device: #54 Location: "M13" Bank: "None" Manufacturer: "Microsoft" Serial: "None" Asset Tag: "None" Part Number: "None" Memory Array: #25 Error Info: #24 Form Factor: 0x02 (Unknown) Type: 0x01 (Other) Type Detail: 0x0004 (Unknown) Data Width: 0 bits Size: No Memory Installed Inactive Record: #55 Data 00: 7e 13 37 00 00 00 00 00 00 00 00 00 36 00 1b 00 Data 10: 00 00 00 Memory Device: #56 Location: "M14" Bank: "None" Manufacturer: "Microsoft" Serial: "None" Asset Tag: "None" Part Number: "None" Memory Array: #25 Error Info: #24 Form Factor: 0x02 (Unknown) Type: 0x01 (Other) Type Detail: 0x0004 (Unknown) Data Width: 0 bits Size: No Memory Installed Inactive Record: #57 Data 00: 7e 13 39 00 00 00 00 00 00 00 00 00 38 00 1b 00 Data 10: 00 00 00 Memory Device: #58 Location: "M15" Bank: "None" Manufacturer: "Microsoft" Serial: "None" Asset Tag: "None" Part Number: "None" Memory Array: #25 Error Info: #24 Form Factor: 0x02 (Unknown) Type: 0x01 (Other) Type Detail: 0x0004 (Unknown) Data Width: 0 bits Size: No Memory Installed Inactive Record: #59 Data 00: 7e 13 3b 00 00 00 00 00 00 00 00 00 3a 00 1b 00 Data 10: 00 00 00 Memory Device: #60 Location: "M16" Bank: "None" Manufacturer: "Microsoft" Serial: "None" Asset Tag: "None" Part Number: "None" Memory Array: #25 Error Info: #24 Form Factor: 0x02 (Unknown) Type: 0x01 (Other) Type Detail: 0x0004 (Unknown) Data Width: 0 bits Size: No Memory Installed Inactive Record: #61 Data 00: 7e 13 3d 00 00 00 00 00 00 00 00 00 3c 00 1b 00 Data 10: 00 00 00 Memory Device: #62 Location: "M17" Bank: "None" Manufacturer: "Microsoft" Serial: "None" Asset Tag: "None" Part Number: "None" Memory Array: #25 Error Info: #24 Form Factor: 0x02 (Unknown) Type: 0x01 (Other) Type Detail: 0x0004 (Unknown) Data Width: 0 bits Size: No Memory Installed Inactive Record: #63 Data 00: 7e 13 3f 00 00 00 00 00 00 00 00 00 3e 00 1b 00 Data 10: 00 00 00 Memory Device: #64 Location: "M18" Bank: "None" Manufacturer: "Microsoft" Serial: "None" Asset Tag: "None" Part Number: "None" Memory Array: #25 Error Info: #24 Form Factor: 0x02 (Unknown) Type: 0x01 (Other) Type Detail: 0x0004 (Unknown) Data Width: 0 bits Size: No Memory Installed Inactive Record: #65 Data 00: 7e 13 41 00 00 00 00 00 00 00 00 00 40 00 1b 00 Data 10: 00 00 00 Memory Device: #66 Location: "M19" Bank: "None" Manufacturer: "Microsoft" Serial: "None" Asset Tag: "None" Part Number: "None" Memory Array: #25 Error Info: #24 Form Factor: 0x02 (Unknown) Type: 0x01 (Other) Type Detail: 0x0004 (Unknown) Data Width: 0 bits Size: No Memory Installed Inactive Record: #67 Data 00: 7e 13 43 00 00 00 00 00 00 00 00 00 42 00 1b 00 Data 10: 00 00 00 Memory Device: #68 Location: "M20" Bank: "None" Manufacturer: "Microsoft" Serial: "None" Asset Tag: "None" Part Number: "None" Memory Array: #25 Error Info: #24 Form Factor: 0x02 (Unknown) Type: 0x01 (Other) Type Detail: 0x0004 (Unknown) Data Width: 0 bits Size: No Memory Installed Inactive Record: #69 Data 00: 7e 13 45 00 00 00 00 00 00 00 00 00 44 00 1b 00 Data 10: 00 00 00 Memory Device: #70 Location: "M21" Bank: "None" Manufacturer: "Microsoft" Serial: "None" Asset Tag: "None" Part Number: "None" Memory Array: #25 Error Info: #24 Form Factor: 0x02 (Unknown) Type: 0x01 (Other) Type Detail: 0x0004 (Unknown) Data Width: 0 bits Size: No Memory Installed Inactive Record: #71 Data 00: 7e 13 47 00 00 00 00 00 00 00 00 00 46 00 1b 00 Data 10: 00 00 00 Memory Device: #72 Location: "M22" Bank: "None" Manufacturer: "Microsoft" Serial: "None" Asset Tag: "None" Part Number: "None" Memory Array: #25 Error Info: #24 Form Factor: 0x02 (Unknown) Type: 0x01 (Other) Type Detail: 0x0004 (Unknown) Data Width: 0 bits Size: No Memory Installed Inactive Record: #73 Data 00: 7e 13 49 00 00 00 00 00 00 00 00 00 48 00 1b 00 Data 10: 00 00 00 Memory Device: #74 Location: "M23" Bank: "None" Manufacturer: "Microsoft" Serial: "None" Asset Tag: "None" Part Number: "None" Memory Array: #25 Error Info: #24 Form Factor: 0x02 (Unknown) Type: 0x01 (Other) Type Detail: 0x0004 (Unknown) Data Width: 0 bits Size: No Memory Installed Inactive Record: #75 Data 00: 7e 13 4b 00 00 00 00 00 00 00 00 00 4a 00 1b 00 Data 10: 00 00 00 Memory Device: #76 Location: "M24" Bank: "None" Manufacturer: "Microsoft" Serial: "None" Asset Tag: "None" Part Number: "None" Memory Array: #25 Error Info: #24 Form Factor: 0x02 (Unknown) Type: 0x01 (Other) Type Detail: 0x0004 (Unknown) Data Width: 0 bits Size: No Memory Installed Inactive Record: #77 Data 00: 7e 13 4d 00 00 00 00 00 00 00 00 00 4c 00 1b 00 Data 10: 00 00 00 Memory Device: #78 Location: "M25" Bank: "None" Manufacturer: "Microsoft" Serial: "None" Asset Tag: "None" Part Number: "None" Memory Array: #25 Error Info: #24 Form Factor: 0x02 (Unknown) Type: 0x01 (Other) Type Detail: 0x0004 (Unknown) Data Width: 0 bits Size: No Memory Installed Inactive Record: #79 Data 00: 7e 13 4f 00 00 00 00 00 00 00 00 00 4e 00 1b 00 Data 10: 00 00 00 Memory Device: #80 Location: "M26" Bank: "None" Manufacturer: "Microsoft" Serial: "None" Asset Tag: "None" Part Number: "None" Memory Array: #25 Error Info: #24 Form Factor: 0x02 (Unknown) Type: 0x01 (Other) Type Detail: 0x0004 (Unknown) Data Width: 0 bits Size: No Memory Installed Inactive Record: #81 Data 00: 7e 13 51 00 00 00 00 00 00 00 00 00 50 00 1b 00 Data 10: 00 00 00 Memory Device: #82 Location: "M27" Bank: "None" Manufacturer: "Microsoft" Serial: "None" Asset Tag: "None" Part Number: "None" Memory Array: #25 Error Info: #24 Form Factor: 0x02 (Unknown) Type: 0x01 (Other) Type Detail: 0x0004 (Unknown) Data Width: 0 bits Size: No Memory Installed Inactive Record: #83 Data 00: 7e 13 53 00 00 00 00 00 00 00 00 00 52 00 1b 00 Data 10: 00 00 00 Memory Device: #84 Location: "M28" Bank: "None" Manufacturer: "Microsoft" Serial: "None" Asset Tag: "None" Part Number: "None" Memory Array: #25 Error Info: #24 Form Factor: 0x02 (Unknown) Type: 0x01 (Other) Type Detail: 0x0004 (Unknown) Data Width: 0 bits Size: No Memory Installed Inactive Record: #85 Data 00: 7e 13 55 00 00 00 00 00 00 00 00 00 54 00 1b 00 Data 10: 00 00 00 Memory Device: #86 Location: "M29" Bank: "None" Manufacturer: "Microsoft" Serial: "None" Asset Tag: "None" Part Number: "None" Memory Array: #25 Error Info: #24 Form Factor: 0x02 (Unknown) Type: 0x01 (Other) Type Detail: 0x0004 (Unknown) Data Width: 0 bits Size: No Memory Installed Inactive Record: #87 Data 00: 7e 13 57 00 00 00 00 00 00 00 00 00 56 00 1b 00 Data 10: 00 00 00 Memory Device: #88 Location: "M30" Bank: "None" Manufacturer: "Microsoft" Serial: "None" Asset Tag: "None" Part Number: "None" Memory Array: #25 Error Info: #24 Form Factor: 0x02 (Unknown) Type: 0x01 (Other) Type Detail: 0x0004 (Unknown) Data Width: 0 bits Size: No Memory Installed Inactive Record: #89 Data 00: 7e 13 59 00 00 00 00 00 00 00 00 00 58 00 1b 00 Data 10: 00 00 00 Memory Device: #90 Location: "M31" Bank: "None" Manufacturer: "Microsoft" Serial: "None" Asset Tag: "None" Part Number: "None" Memory Array: #25 Error Info: #24 Form Factor: 0x02 (Unknown) Type: 0x01 (Other) Type Detail: 0x0004 (Unknown) Data Width: 0 bits Size: No Memory Installed Inactive Record: #91 Data 00: 7e 13 5b 00 00 00 00 00 00 00 00 00 5a 00 1b 00 Data 10: 00 00 00 Memory Device: #92 Location: "M32" Bank: "None" Manufacturer: "Microsoft" Serial: "None" Asset Tag: "None" Part Number: "None" Memory Array: #25 Error Info: #24 Form Factor: 0x02 (Unknown) Type: 0x01 (Other) Type Detail: 0x0004 (Unknown) Data Width: 0 bits Size: No Memory Installed Inactive Record: #93 Data 00: 7e 13 5d 00 00 00 00 00 00 00 00 00 5c 00 1b 00 Data 10: 00 00 00 Memory Device: #94 Location: "M33" Bank: "None" Manufacturer: "Microsoft" Serial: "None" Asset Tag: "None" Part Number: "None" Memory Array: #25 Error Info: #24 Form Factor: 0x02 (Unknown) Type: 0x01 (Other) Type Detail: 0x0004 (Unknown) Data Width: 0 bits Size: No Memory Installed Inactive Record: #95 Data 00: 7e 13 5f 00 00 00 00 00 00 00 00 00 5e 00 1b 00 Data 10: 00 00 00 Memory Device: #96 Location: "M34" Bank: "None" Manufacturer: "Microsoft" Serial: "None" Asset Tag: "None" Part Number: "None" Memory Array: #25 Error Info: #24 Form Factor: 0x02 (Unknown) Type: 0x01 (Other) Type Detail: 0x0004 (Unknown) Data Width: 0 bits Size: No Memory Installed Inactive Record: #97 Data 00: 7e 13 61 00 00 00 00 00 00 00 00 00 60 00 1b 00 Data 10: 00 00 00 Memory Device: #98 Location: "M35" Bank: "None" Manufacturer: "Microsoft" Serial: "None" Asset Tag: "None" Part Number: "None" Memory Array: #25 Error Info: #24 Form Factor: 0x02 (Unknown) Type: 0x01 (Other) Type Detail: 0x0004 (Unknown) Data Width: 0 bits Size: No Memory Installed Inactive Record: #99 Data 00: 7e 13 63 00 00 00 00 00 00 00 00 00 62 00 1b 00 Data 10: 00 00 00 Memory Device: #100 Location: "M36" Bank: "None" Manufacturer: "Microsoft" Serial: "None" Asset Tag: "None" Part Number: "None" Memory Array: #25 Error Info: #24 Form Factor: 0x02 (Unknown) Type: 0x01 (Other) Type Detail: 0x0004 (Unknown) Data Width: 0 bits Size: No Memory Installed Inactive Record: #101 Data 00: 7e 13 65 00 00 00 00 00 00 00 00 00 64 00 1b 00 Data 10: 00 00 00 Memory Device: #102 Location: "M37" Bank: "None" Manufacturer: "Microsoft" Serial: "None" Asset Tag: "None" Part Number: "None" Memory Array: #25 Error Info: #24 Form Factor: 0x02 (Unknown) Type: 0x01 (Other) Type Detail: 0x0004 (Unknown) Data Width: 0 bits Size: No Memory Installed Inactive Record: #103 Data 00: 7e 13 67 00 00 00 00 00 00 00 00 00 66 00 1b 00 Data 10: 00 00 00 Memory Device: #104 Location: "M38" Bank: "None" Manufacturer: "Microsoft" Serial: "None" Asset Tag: "None" Part Number: "None" Memory Array: #25 Error Info: #24 Form Factor: 0x02 (Unknown) Type: 0x01 (Other) Type Detail: 0x0004 (Unknown) Data Width: 0 bits Size: No Memory Installed Inactive Record: #105 Data 00: 7e 13 69 00 00 00 00 00 00 00 00 00 68 00 1b 00 Data 10: 00 00 00 Memory Device: #106 Location: "M39" Bank: "None" Manufacturer: "Microsoft" Serial: "None" Asset Tag: "None" Part Number: "None" Memory Array: #25 Error Info: #24 Form Factor: 0x02 (Unknown) Type: 0x01 (Other) Type Detail: 0x0004 (Unknown) Data Width: 0 bits Size: No Memory Installed Inactive Record: #107 Data 00: 7e 13 6b 00 00 00 00 00 00 00 00 00 6a 00 1b 00 Data 10: 00 00 00 Memory Device: #108 Location: "M40" Bank: "None" Manufacturer: "Microsoft" Serial: "None" Asset Tag: "None" Part Number: "None" Memory Array: #25 Error Info: #24 Form Factor: 0x02 (Unknown) Type: 0x01 (Other) Type Detail: 0x0004 (Unknown) Data Width: 0 bits Size: No Memory Installed Inactive Record: #109 Data 00: 7e 13 6d 00 00 00 00 00 00 00 00 00 6c 00 1b 00 Data 10: 00 00 00 Memory Device: #110 Location: "M41" Bank: "None" Manufacturer: "Microsoft" Serial: "None" Asset Tag: "None" Part Number: "None" Memory Array: #25 Error Info: #24 Form Factor: 0x02 (Unknown) Type: 0x01 (Other) Type Detail: 0x0004 (Unknown) Data Width: 0 bits Size: No Memory Installed Inactive Record: #111 Data 00: 7e 13 6f 00 00 00 00 00 00 00 00 00 6e 00 1b 00 Data 10: 00 00 00 Memory Device: #112 Location: "M42" Bank: "None" Manufacturer: "Microsoft" Serial: "None" Asset Tag: "None" Part Number: "None" Memory Array: #25 Error Info: #24 Form Factor: 0x02 (Unknown) Type: 0x01 (Other) Type Detail: 0x0004 (Unknown) Data Width: 0 bits Size: No Memory Installed Inactive Record: #113 Data 00: 7e 13 71 00 00 00 00 00 00 00 00 00 70 00 1b 00 Data 10: 00 00 00 Memory Device: #114 Location: "M43" Bank: "None" Manufacturer: "Microsoft" Serial: "None" Asset Tag: "None" Part Number: "None" Memory Array: #25 Error Info: #24 Form Factor: 0x02 (Unknown) Type: 0x01 (Other) Type Detail: 0x0004 (Unknown) Data Width: 0 bits Size: No Memory Installed Inactive Record: #115 Data 00: 7e 13 73 00 00 00 00 00 00 00 00 00 72 00 1b 00 Data 10: 00 00 00 Memory Device: #116 Location: "M44" Bank: "None" Manufacturer: "Microsoft" Serial: "None" Asset Tag: "None" Part Number: "None" Memory Array: #25 Error Info: #24 Form Factor: 0x02 (Unknown) Type: 0x01 (Other) Type Detail: 0x0004 (Unknown) Data Width: 0 bits Size: No Memory Installed Inactive Record: #117 Data 00: 7e 13 75 00 00 00 00 00 00 00 00 00 74 00 1b 00 Data 10: 00 00 00 Memory Device: #118 Location: "M45" Bank: "None" Manufacturer: "Microsoft" Serial: "None" Asset Tag: "None" Part Number: "None" Memory Array: #25 Error Info: #24 Form Factor: 0x02 (Unknown) Type: 0x01 (Other) Type Detail: 0x0004 (Unknown) Data Width: 0 bits Size: No Memory Installed Inactive Record: #119 Data 00: 7e 13 77 00 00 00 00 00 00 00 00 00 76 00 1b 00 Data 10: 00 00 00 Memory Device: #120 Location: "M46" Bank: "None" Manufacturer: "Microsoft" Serial: "None" Asset Tag: "None" Part Number: "None" Memory Array: #25 Error Info: #24 Form Factor: 0x02 (Unknown) Type: 0x01 (Other) Type Detail: 0x0004 (Unknown) Data Width: 0 bits Size: No Memory Installed Inactive Record: #121 Data 00: 7e 13 79 00 00 00 00 00 00 00 00 00 78 00 1b 00 Data 10: 00 00 00 Memory Device: #122 Location: "M47" Bank: "None" Manufacturer: "Microsoft" Serial: "None" Asset Tag: "None" Part Number: "None" Memory Array: #25 Error Info: #24 Form Factor: 0x02 (Unknown) Type: 0x01 (Other) Type Detail: 0x0004 (Unknown) Data Width: 0 bits Size: No Memory Installed Inactive Record: #123 Data 00: 7e 13 7b 00 00 00 00 00 00 00 00 00 7a 00 1b 00 Data 10: 00 00 00 Memory Device: #124 Location: "M48" Bank: "None" Manufacturer: "Microsoft" Serial: "None" Asset Tag: "None" Part Number: "None" Memory Array: #25 Error Info: #24 Form Factor: 0x02 (Unknown) Type: 0x01 (Other) Type Detail: 0x0004 (Unknown) Data Width: 0 bits Size: No Memory Installed Inactive Record: #125 Data 00: 7e 13 7d 00 00 00 00 00 00 00 00 00 7c 00 1b 00 Data 10: 00 00 00 Memory Device: #126 Location: "M49" Bank: "None" Manufacturer: "Microsoft" Serial: "None" Asset Tag: "None" Part Number: "None" Memory Array: #25 Error Info: #24 Form Factor: 0x02 (Unknown) Type: 0x01 (Other) Type Detail: 0x0004 (Unknown) Data Width: 0 bits Size: No Memory Installed Inactive Record: #127 Data 00: 7e 13 7f 00 00 00 00 00 00 00 00 00 7e 00 1b 00 Data 10: 00 00 00 Memory Device: #128 Location: "M50" Bank: "None" Manufacturer: "Microsoft" Serial: "None" Asset Tag: "None" Part Number: "None" Memory Array: #25 Error Info: #24 Form Factor: 0x02 (Unknown) Type: 0x01 (Other) Type Detail: 0x0004 (Unknown) Data Width: 0 bits Size: No Memory Installed Inactive Record: #129 Data 00: 7e 13 81 00 00 00 00 00 00 00 00 00 80 00 1b 00 Data 10: 00 00 00 Memory Device: #130 Location: "M51" Bank: "None" Manufacturer: "Microsoft" Serial: "None" Asset Tag: "None" Part Number: "None" Memory Array: #25 Error Info: #24 Form Factor: 0x02 (Unknown) Type: 0x01 (Other) Type Detail: 0x0004 (Unknown) Data Width: 0 bits Size: No Memory Installed Inactive Record: #131 Data 00: 7e 13 83 00 00 00 00 00 00 00 00 00 82 00 1b 00 Data 10: 00 00 00 Memory Device: #132 Location: "M52" Bank: "None" Manufacturer: "Microsoft" Serial: "None" Asset Tag: "None" Part Number: "None" Memory Array: #25 Error Info: #24 Form Factor: 0x02 (Unknown) Type: 0x01 (Other) Type Detail: 0x0004 (Unknown) Data Width: 0 bits Size: No Memory Installed Inactive Record: #133 Data 00: 7e 13 85 00 00 00 00 00 00 00 00 00 84 00 1b 00 Data 10: 00 00 00 Memory Device: #134 Location: "M53" Bank: "None" Manufacturer: "Microsoft" Serial: "None" Asset Tag: "None" Part Number: "None" Memory Array: #25 Error Info: #24 Form Factor: 0x02 (Unknown) Type: 0x01 (Other) Type Detail: 0x0004 (Unknown) Data Width: 0 bits Size: No Memory Installed Inactive Record: #135 Data 00: 7e 13 87 00 00 00 00 00 00 00 00 00 86 00 1b 00 Data 10: 00 00 00 Memory Device: #136 Location: "M54" Bank: "None" Manufacturer: "Microsoft" Serial: "None" Asset Tag: "None" Part Number: "None" Memory Array: #25 Error Info: #24 Form Factor: 0x02 (Unknown) Type: 0x01 (Other) Type Detail: 0x0004 (Unknown) Data Width: 0 bits Size: No Memory Installed Inactive Record: #137 Data 00: 7e 13 89 00 00 00 00 00 00 00 00 00 88 00 1b 00 Data 10: 00 00 00 Memory Device: #138 Location: "M55" Bank: "None" Manufacturer: "Microsoft" Serial: "None" Asset Tag: "None" Part Number: "None" Memory Array: #25 Error Info: #24 Form Factor: 0x02 (Unknown) Type: 0x01 (Other) Type Detail: 0x0004 (Unknown) Data Width: 0 bits Size: No Memory Installed Inactive Record: #139 Data 00: 7e 13 8b 00 00 00 00 00 00 00 00 00 8a 00 1b 00 Data 10: 00 00 00 Memory Device: #140 Location: "M56" Bank: "None" Manufacturer: "Microsoft" Serial: "None" Asset Tag: "None" Part Number: "None" Memory Array: #25 Error Info: #24 Form Factor: 0x02 (Unknown) Type: 0x01 (Other) Type Detail: 0x0004 (Unknown) Data Width: 0 bits Size: No Memory Installed Inactive Record: #141 Data 00: 7e 13 8d 00 00 00 00 00 00 00 00 00 8c 00 1b 00 Data 10: 00 00 00 Memory Device: #142 Location: "M57" Bank: "None" Manufacturer: "Microsoft" Serial: "None" Asset Tag: "None" Part Number: "None" Memory Array: #25 Error Info: #24 Form Factor: 0x02 (Unknown) Type: 0x01 (Other) Type Detail: 0x0004 (Unknown) Data Width: 0 bits Size: No Memory Installed Inactive Record: #143 Data 00: 7e 13 8f 00 00 00 00 00 00 00 00 00 8e 00 1b 00 Data 10: 00 00 00 Memory Device: #144 Location: "M58" Bank: "None" Manufacturer: "Microsoft" Serial: "None" Asset Tag: "None" Part Number: "None" Memory Array: #25 Error Info: #24 Form Factor: 0x02 (Unknown) Type: 0x01 (Other) Type Detail: 0x0004 (Unknown) Data Width: 0 bits Size: No Memory Installed Inactive Record: #145 Data 00: 7e 13 91 00 00 00 00 00 00 00 00 00 90 00 1b 00 Data 10: 00 00 00 Memory Device: #146 Location: "M59" Bank: "None" Manufacturer: "Microsoft" Serial: "None" Asset Tag: "None" Part Number: "None" Memory Array: #25 Error Info: #24 Form Factor: 0x02 (Unknown) Type: 0x01 (Other) Type Detail: 0x0004 (Unknown) Data Width: 0 bits Size: No Memory Installed Inactive Record: #147 Data 00: 7e 13 93 00 00 00 00 00 00 00 00 00 92 00 1b 00 Data 10: 00 00 00 Memory Device: #148 Location: "M60" Bank: "None" Manufacturer: "Microsoft" Serial: "None" Asset Tag: "None" Part Number: "None" Memory Array: #25 Error Info: #24 Form Factor: 0x02 (Unknown) Type: 0x01 (Other) Type Detail: 0x0004 (Unknown) Data Width: 0 bits Size: No Memory Installed Inactive Record: #149 Data 00: 7e 13 95 00 00 00 00 00 00 00 00 00 94 00 1b 00 Data 10: 00 00 00 Memory Device: #150 Location: "M61" Bank: "None" Manufacturer: "Microsoft" Serial: "None" Asset Tag: "None" Part Number: "None" Memory Array: #25 Error Info: #24 Form Factor: 0x02 (Unknown) Type: 0x01 (Other) Type Detail: 0x0004 (Unknown) Data Width: 0 bits Size: No Memory Installed Inactive Record: #151 Data 00: 7e 13 97 00 00 00 00 00 00 00 00 00 96 00 1b 00 Data 10: 00 00 00 Memory Device: #152 Location: "M62" Bank: "None" Manufacturer: "Microsoft" Serial: "None" Asset Tag: "None" Part Number: "None" Memory Array: #25 Error Info: #24 Form Factor: 0x02 (Unknown) Type: 0x01 (Other) Type Detail: 0x0004 (Unknown) Data Width: 0 bits Size: No Memory Installed Inactive Record: #153 Data 00: 7e 13 99 00 00 00 00 00 00 00 00 00 98 00 1b 00 Data 10: 00 00 00 Memory Device: #154 Location: "M63" Bank: "None" Manufacturer: "Microsoft" Serial: "None" Asset Tag: "None" Part Number: "None" Memory Array: #25 Error Info: #24 Form Factor: 0x02 (Unknown) Type: 0x01 (Other) Type Detail: 0x0004 (Unknown) Data Width: 0 bits Size: No Memory Installed Inactive Record: #155 Data 00: 7e 13 9b 00 00 00 00 00 00 00 00 00 9a 00 1b 00 Data 10: 00 00 00 Type 23 Record: #156 Data 00: 17 0d 9c 00 00 ff ff ff ff ff ff ff ff Type 32 Record: #157 Data 00: 20 14 9d 00 00 00 00 00 00 00 00 00 00 00 00 00 Data 10: 00 00 00 00 Config Status: cfg=new, avail=yes, need=no, active=unknown -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

bugzilla_noreply＠novell.com

20:46

New subject: [Bug 732693] hv_vmbus: Unable to intialize the hypervisor on first reboot during install

https://bugzilla.novell.com/show_bug.cgi?id=732693 https://bugzilla.novell.com/show_bug.cgi?id=732693#c19 --- Comment #19 from Mike Surcouf 2012-04-23 20:46:12 UTC --- I am no expert but maybe arch/x86/kernel/cpu/mshyperv.c has the answer it contains a kernel export but Iam afraid its a bit out of my league. gregkh helped KY Srinivasan with this code so maybe he can help? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

bugzilla_noreply＠novell.com

24 Apr 24 Apr

13:39

New subject: [Bug 732693] hv_vmbus: Unable to intialize the hypervisor on first reboot during install

https://bugzilla.novell.com/show_bug.cgi?id=732693 https://bugzilla.novell.com/show_bug.cgi?id=732693#c20 --- Comment #20 from Steffen Winterfeldt 2012-04-24 15:39:12 CEST --- Created an attachment (id=487743) --> (http://bugzilla.novell.com/attachment.cgi?id=487743) yast2-bootloader fix Could you test the attached driverupdate for Factory? To use it, add something like dud=http://foo/driver_update.img to the install boot options (or dud=disk:/driver_update.img if you store it on a local disk). If it doesn't work, please attach /var/log/YaST2/y2log*. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

bugzilla_noreply＠novell.com

13:50

New subject: [Bug 732693] hv_vmbus: Unable to intialize the hypervisor on first reboot during install

https://bugzilla.novell.com/show_bug.cgi?id=732693 https://bugzilla.novell.com/show_bug.cgi?id=732693#c21 --- Comment #21 from Mike Surcouf 2012-04-24 13:50:41 UTC --- Sorry I only see an attachment named bl90 (no extension). Not sure what to do with it. Assume minimal knowledge of Factory development. Thanks for you patience. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

bugzilla_noreply＠novell.com

14:00

New subject: [Bug 732693] hv_vmbus: Unable to intialize the hypervisor on first reboot during install

https://bugzilla.novell.com/show_bug.cgi?id=732693 https://bugzilla.novell.com/show_bug.cgi?id=732693#c22 --- Comment #22 from Steffen Winterfeldt 2012-04-24 16:00:41 CEST --- Never mind the name. Just use it. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

bugzilla_noreply＠novell.com

25 Apr 25 Apr

22:25

New subject: [Bug 732693] hv_vmbus: Unable to intialize the hypervisor on first reboot during install

https://bugzilla.novell.com/show_bug.cgi?id=732693 https://bugzilla.novell.com/show_bug.cgi?id=732693#c23 --- Comment #23 from Mike Surcouf 2012-04-25 22:25:29 UTC --- Anyone else have the patience to explain how to test this driver update disk? Do I do a new install and press F6? If so what do I do after I pressed F6? If non of the above a simple 1. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

bugzilla_noreply＠novell.com

22:27

New subject: [Bug 732693] hv_vmbus: Unable to intialize the hypervisor on first reboot during install

https://bugzilla.novell.com/show_bug.cgi?id=732693 https://bugzilla.novell.com/show_bug.cgi?id=732693#c24 --- Comment #24 from Mike Surcouf 2012-04-25 22:27:30 UTC --- A simple step by step procedure would be good as I never used a driver upodate before. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

bugzilla_noreply＠novell.com

26 Apr 26 Apr

05:59

New subject: [Bug 732693] hv_vmbus: Unable to intialize the hypervisor on first reboot during install

https://bugzilla.novell.com/show_bug.cgi?id=732693 https://bugzilla.novell.com/show_bug.cgi?id=732693#c25 --- Comment #25 from Steffen Winterfeldt 2012-04-26 07:59:12 CEST --- Copy the attached file somewhere where you can access it from the vm. Boot from install dvd, at the boot screen add dud=url_pointing_to_the_file (see examples in comment 20). That's it. There will be some messages on the screen later on saying it found a driver update etc. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

bugzilla_noreply＠novell.com

27 Apr 27 Apr

13:15

New subject: [Bug 732693] hv_vmbus: Unable to intialize the hypervisor on first reboot during install

https://bugzilla.novell.com/show_bug.cgi?id=732693 https://bugzilla.novell.com/show_bug.cgi?id=732693#c26 --- Comment #26 from Mike Surcouf 2012-04-27 13:15:17 UTC --- Created an attachment (id=488593) --> (http://bugzilla.novell.com/attachment.cgi?id=488593) y2log files -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

bugzilla_noreply＠novell.com

13:20

New subject: [Bug 732693] hv_vmbus: Unable to intialize the hypervisor on first reboot during install

https://bugzilla.novell.com/show_bug.cgi?id=732693 https://bugzilla.novell.com/show_bug.cgi?id=732693#c27 --- Comment #27 from Mike Surcouf 2012-04-27 13:20:48 UTC --- Using factory install (without patch) I no longer see a kexec call in the install routine. I think someone has removed it? So in that respect the original bug of a kexec causing a hang at install on hyper-v seems to be moot. Applying the patch I see the dud you posted loading and succeeding. I don't know if it worked though as I am not sure how to test if kexec is disabled by your patch so I attached the y2log files as requested. Sorry for the delay it took a while to set up my test. I will have a much faster response time if you need to test further. Thanks Mike -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

bugzilla_noreply＠novell.com

30 Apr 30 Apr

09:18

New subject: [Bug 732693] hv_vmbus: Unable to intialize the hypervisor on first reboot during install

https://bugzilla.novell.com/show_bug.cgi?id=732693 https://bugzilla.novell.com/show_bug.cgi?id=732693#c28 Steffen Winterfeldt changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |RESOLVED Resolution| |FIXED --- Comment #28 from Steffen Winterfeldt 2012-04-30 11:18:41 CEST --- The attached archive is broken. I can't read the log. Anyway, I've submitted the patch to Factory now (in yast2-bootloader-2.23.3). Please reopen this bug if you see any issues. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

bugzilla_noreply＠novell.com

10:00

New subject: [Bug 732693] hv_vmbus: Unable to intialize the hypervisor on first reboot during install

https://bugzilla.novell.com/show_bug.cgi?id=732693 https://bugzilla.novell.com/show_bug.cgi?id=732693#c29 --- Comment #29 from Bernhard Wiedemann 2012-04-30 12:00:08 CEST --- This is an autogenerated message for OBS integration: This bug (732693) was mentioned in https://build.opensuse.org/request/show/116005 Factory / yast2-bootloader -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

bugzilla_noreply＠novell.com

10:02

New subject: [Bug 732693] hv_vmbus: Unable to intialize the hypervisor on first reboot during install

https://bugzilla.novell.com/show_bug.cgi?id=732693 https://bugzilla.novell.com/show_bug.cgi?id=732693#c30 --- Comment #30 from Mike Surcouf 2012-04-30 10:02:12 UTC --- Created an attachment (id=488797) --> (http://bugzilla.novell.com/attachment.cgi?id=488797) resend of y2logs Apologies fixed attachment -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

bugzilla_noreply＠novell.com

10:03

New subject: [Bug 732693] hv_vmbus: Unable to intialize the hypervisor on first reboot during install

https://bugzilla.novell.com/show_bug.cgi?id=732693 https://bugzilla.novell.com/show_bug.cgi?id=732693#c31 --- Comment #31 from Mike Surcouf 2012-04-30 10:03:15 UTC --- Thanks for all your help. I resent the fixed tar if you are still interested in the contents -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

4386

Age (days ago)

4544

Last active (days ago)

List overview

Download

35 comments

1 participants

participants (1)

bugzilla_noreply＠novell.com

[Bug 732693] New: hv_vmbus: Unable to intialize the hypervisor on first boot after install

tags

participants (1)