[Qemu-devel] [Bug 1078892] [NEW] qemu doesn't general protection fault if there are reserved bits set in page-directory-pointer table entries

[Qemu-devel] [Bug 1078892] [NEW] qemu doesn't general protection fault if there are reserved bits set in page-directory-pointer table entries

[Alexander Chernyakhovsky]

Public bug reported:

While working on implementing 32-bit PAE mode in a custom operating
system, which I was testing in QEMU, I noticed that my OS worked
correctly, but resulted in a general protection fault when booted on
VMware, VirtualBox, or bochs.

According to the Intel Architecture Manual, Volume 3A, Section 4.4.1
"PDPTE Registers", "If any of the PDPTEs sets both the P flag (bit 0)
and any reserved bit, the MOV to CR instruction causes a general-
protection exception (#GP(0)) and the PDPTEs are not loaded." QEMU does
not emulate this behavior.

** Affects: qemu
     Importance: Undecided
         Status: New

-- 
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1078892

Title:
  qemu doesn't general protection fault if there are reserved bits set
  in page-directory-pointer table entries

Status in QEMU:
  New

Bug description:
  While working on implementing 32-bit PAE mode in a custom operating
  system, which I was testing in QEMU, I noticed that my OS worked
  correctly, but resulted in a general protection fault when booted on
  VMware, VirtualBox, or bochs.

  According to the Intel Architecture Manual, Volume 3A, Section 4.4.1
  "PDPTE Registers", "If any of the PDPTEs sets both the P flag (bit 0)
  and any reserved bit, the MOV to CR instruction causes a general-
  protection exception (#GP(0)) and the PDPTEs are not loaded." QEMU
  does not emulate this behavior.

To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1078892/+subscriptions

[Qemu-devel] [Bug 1078892] Re: qemu doesn't general protection fault if there are reserved bits set in page-directory-pointer table entries

[Thomas Huth]

Triaging old bug tickets ... can you still reproduce this issue with the
latest version of QEMU (version 2.9)?

** Changed in: qemu
       Status: New => Incomplete

-- 
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1078892

Title:
  qemu doesn't general protection fault if there are reserved bits set
  in page-directory-pointer table entries

Status in QEMU:
  Incomplete

Bug description:
  While working on implementing 32-bit PAE mode in a custom operating
  system, which I was testing in QEMU, I noticed that my OS worked
  correctly, but resulted in a general protection fault when booted on
  VMware, VirtualBox, or bochs.

  According to the Intel Architecture Manual, Volume 3A, Section 4.4.1
  "PDPTE Registers", "If any of the PDPTEs sets both the P flag (bit 0)
  and any reserved bit, the MOV to CR instruction causes a general-
  protection exception (#GP(0)) and the PDPTEs are not loaded." QEMU
  does not emulate this behavior.

To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1078892/+subscriptions

[Qemu-devel] [Bug 1078892] Re: qemu doesn't general protection fault if there are reserved bits set in page-directory-pointer table entries

[Launchpad Bug Tracker]

[Expired for QEMU because there has been no activity for 60 days.]

** Changed in: qemu
       Status: Incomplete => Expired

-- 
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1078892

Title:
  qemu doesn't general protection fault if there are reserved bits set
  in page-directory-pointer table entries

Status in QEMU:
  Expired

Bug description:
  While working on implementing 32-bit PAE mode in a custom operating
  system, which I was testing in QEMU, I noticed that my OS worked
  correctly, but resulted in a general protection fault when booted on
  VMware, VirtualBox, or bochs.

  According to the Intel Architecture Manual, Volume 3A, Section 4.4.1
  "PDPTE Registers", "If any of the PDPTEs sets both the P flag (bit 0)
  and any reserved bit, the MOV to CR instruction causes a general-
  protection exception (#GP(0)) and the PDPTEs are not loaded." QEMU
  does not emulate this behavior.

To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1078892/+subscriptions