All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stefan Hajnoczi <stefanha@gmail.com>
To: Antonio Raffaele <windowsnotfound@gmail.com>
Cc: Julia Suvorova <jusual@redhat.com>, qemu-devel@nongnu.org
Subject: Re: Overriding PCI Vendor/Device IDs
Date: Tue, 23 Jun 2020 16:02:53 +0100	[thread overview]
Message-ID: <20200623150253.GT36568@stefanha-x1.localdomain> (raw)
In-Reply-To: <CAFES52nPcmpF9dB175J4xdAqsJO+GK2614OOoKDArt+=cX2mhA@mail.gmail.com>

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

On Sun, Jun 21, 2020 at 09:31:30AM +0200, Antonio Raffaele wrote:
> Hi I'm trying to create a qemu virtual machine that runs windows 10. I
> would like to try to make it almost indistinguishable from a real computer
> (I know it's impossible, but at least I get close). I have already changed
> any suspicious identifiers (smbios, hard disk, card network and so on,
> host-passthroug cpu etc.) But now checking the various components that the
> guest computer recognizes, I realized (through the hwinfo64 program) that
> in the bus section, then pcibus there are devices called "Red Hat , Device
> ID "and with the same devicename, as device class have:" PCI-to-PCI Bridge
> ". Is there a way to change the devicename of these virtual compontents
> (maybe even changing the qemu source)?

As far as I know there is no command-line parameter for overriding PCI
Vendor/Device IDs.

If you are able to modify the QEMU source code you can change the
PCIDeviceClass fields. For example, in hw/pci-bridge/pci_bridge_dev.c:

  k->vendor_id = PCI_VENDOR_ID_REDHAT;
  k->device_id = PCI_DEVICE_ID_REDHAT_BRIDGE;

Stefan

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

      reply	other threads:[~2020-06-23 15:04 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-21  7:31 Antonio Raffaele
2020-06-23 15:02 ` Stefan Hajnoczi [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20200623150253.GT36568@stefanha-x1.localdomain \
    --to=stefanha@gmail.com \
    --cc=jusual@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=windowsnotfound@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.