From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mga18.intel.com (mga18.intel.com [134.134.136.126]) by mx.groups.io with SMTP id smtpd.web11.6964.1570779902913434496 for ; Fri, 11 Oct 2019 00:45:03 -0700 Authentication-Results: mx.groups.io; dkim=missing; spf=pass (domain: intel.com, ip: 134.134.136.126, mailfrom: junhao.gao@intel.com) X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from fmsmga007.fm.intel.com ([10.253.24.52]) by orsmga106.jf.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 11 Oct 2019 00:45:02 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.67,283,1566889200"; d="scan'208";a="194257853" Received: from fmsmsx107.amr.corp.intel.com ([10.18.124.205]) by fmsmga007.fm.intel.com with ESMTP; 11 Oct 2019 00:45:01 -0700 Received: from fmsmsx112.amr.corp.intel.com (10.18.116.6) by fmsmsx107.amr.corp.intel.com (10.18.124.205) with Microsoft SMTP Server (TLS) id 14.3.439.0; Fri, 11 Oct 2019 00:45:01 -0700 Received: from shsmsx153.ccr.corp.intel.com (10.239.6.53) by FMSMSX112.amr.corp.intel.com (10.18.116.6) with Microsoft SMTP Server (TLS) id 14.3.439.0; Fri, 11 Oct 2019 00:45:00 -0700 Received: from shsmsx101.ccr.corp.intel.com ([169.254.1.96]) by SHSMSX153.ccr.corp.intel.com ([10.239.6.53]) with mapi id 14.03.0439.000; Fri, 11 Oct 2019 15:44:59 +0800 From: "Junhao Gao" To: "devel@edk2.groups.io" , "Gao, Junhao" , "lersek@redhat.com" CC: David Woodhouse Subject: Re: [edk2-devel] question about qemu+kvm+ovmf+winxp Thread-Topic: [edk2-devel] question about qemu+kvm+ovmf+winxp Thread-Index: AdV/d1Cgr1GFE2MpSZCiy3fhXb9THv//t0kA//7/spD//ZdNUA== Date: Fri, 11 Oct 2019 07:44:57 +0000 Message-ID: <50E163A92F208D4B8CEB452055E613EB0AFE8C2B@SHSMSX101.ccr.corp.intel.com> References: <50E163A92F208D4B8CEB452055E613EB0AFE85F7@SHSMSX101.ccr.corp.intel.com> <15CC73B09CF3FDD9.17220@groups.io> In-Reply-To: <15CC73B09CF3FDD9.17220@groups.io> Accept-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: dlp-product: dlpe-windows dlp-version: 11.2.0.6 dlp-reaction: no-action x-titus-metadata-40: eyJDYXRlZ29yeUxhYmVscyI6IiIsIk1ldGFkYXRhIjp7Im5zIjoiaHR0cDpcL1wvd3d3LnRpdHVzLmNvbVwvbnNcL0ludGVsMyIsImlkIjoiZmYxMjlhNzAtZThlYy00MzM0LWI4Y2ItMjE5OWJhNmU3MTUzIiwicHJvcHMiOlt7Im4iOiJDVFBDbGFzc2lmaWNhdGlvbiIsInZhbHMiOlt7InZhbHVlIjoiQ1RQX05UIn1dfV19LCJTdWJqZWN0TGFiZWxzIjpbXSwiVE1DVmVyc2lvbiI6IjE3LjEwLjE4MDQuNDkiLCJUcnVzdGVkTGFiZWxIYXNoIjoiWFpnZWp1a2xNZWc4UEozb0ZVR2tvQm1idTk0SEtzWmlUakJxaHFTeCt2SHhBTWdZaEozWjZnSzJkK0V4U05SXC8ifQ== x-ctpclassification: CTP_NT x-originating-ip: [10.239.127.40] MIME-Version: 1.0 Return-Path: junhao.gao@intel.com Content-Language: en-US Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Hi David=20 I have found this compiled OVMF-with-csm.fd can support winxp booting up. OVMF-with-csm.fd path: https://www.kraxel.org/repos/jenkins/seabios/seabi= os.git-csm-1.12.0-33.63.g43f5df7.x86_64.rpm Then could you help to provide me the compile method and base code to rep= roduce this OVMF-with-csm.fd? Thanks, Junhao=20 -----Original Message----- From: devel@edk2.groups.io On Behalf Of Junhao Gao Sent: Friday, October 11, 2019 9:33 AM To: devel@edk2.groups.io; lersek@redhat.com Cc: David Woodhouse Subject: Re: [edk2-devel] question about qemu+kvm+ovmf+winxp Hi Laszlo Thank you very much for your great support. Hi David Refer to http://www.linux-kvm.org/downloads/lersek/ovmf-whitepaper-c770f8= c.txt. Interested users and developers should look for OVMF's "-D CSM_ENABLE" build-time option, and check out the cont= inuous integration repository, which provides CSM-enabled OVMF builds. =09 Could you help me to choose which branch supporting CSM, and more details= , thanks very much. Thanks, Junhao -----Original Message----- From: devel@edk2.groups.io On Behalf Of Laszlo Erse= k Sent: Friday, October 11, 2019 2:11 AM To: Gao, Junhao Cc: devel@edk2.groups.io; David Woodhouse Subject: Re: [edk2-devel] question about qemu+kvm+ovmf+winxp On 10/10/19 16:37, Junhao Gao wrote: > Hi edk2 members > > I have a question for your help. > I want to enable qemu+kvm+ovmf to boot up windows xp, > then ovmf support winxp starting-up? To my understanding, the first Windows "family" with any kind of UEFI supp= ort is Windows 7. OvmfPkg/README has some comments on Windows support: > * UEFI Windows 8 boots > * UEFI Windows 7 & Windows 2008 Server boot (see important notes=20 > below!) and > =3D=3D=3D UEFI Windows 7 & Windows 2008 Server =3D=3D=3D > > * One of the '-vga std' and '-vga qxl' QEMU options should be used. > * Only one video mode, 1024x768x32, is supported at OS runtime. > * The '-vga qxl' QEMU option is recommended. After booting the installed > guest OS, select the video card in Device Manager, and upgrade its dri= ver > to the QXL XDDM one. Download location: > , Guest | Windows binaries. > This enables further resolutions at OS runtime, and provides S3 > (suspend/resume) capability. If you'd like to virtualize Windows XP on QEMU/KVM, please use SeaBIOS for= guest firmware. You can also try to build OVMF with -D CSM_ENABLE, but for that, you'll ha= ve to build SeaBIOS in CSM mode first, and embed that binary into OVMF at b= uild time. Please ask David for details (CC'd). Thanks Laszlo > qemu command: > qemu-system-x86_64 -hda winxp.img -boot c -enable-kvm -cp= u host -bios ./OVMF.fd -m 512 -vga cirrus -net nic,model=3Drtl8139 -net use= r -usbdevice tablet -localtime > Then if ovmf support, could you provide me the way to com= pile the OVMF.fd? > > Thanks, > Junhao > > >=20 > >