All of lore.kernel.org
 help / color / mirror / Atom feed
* [Qemu-devel] [Bug 1798434] [NEW] [Feature Request] Automatic device configuration discovery
@ 2018-10-17 18:21 Ryan Govostes
  2018-10-17 18:44 ` [Qemu-devel] [Bug 1798434] " Peter Maydell
  2018-10-18  5:31 ` Thomas Huth
  0 siblings, 2 replies; 3+ messages in thread
From: Ryan Govostes @ 2018-10-17 18:21 UTC (permalink / raw)
  To: qemu-devel

Public bug reported:

Would it be possible to have a script that enumerates the device tree of
a Linux host and generates a qemu command line that would recreate it
under emulation? The user would have to customize the arguments (for
instance to point to disk image files), but it would take a lot of the
guesswork out.

Similarly, there could be information that can be gleaned from the
kernel build config that would help with configuration.

** Affects: qemu
     Importance: Undecided
         Status: New

** Description changed:

  Would it be possible to have a script that enumerates the device tree of
  a Linux host and generates a qemu command line that would recreate it
  under emulation? The user would have to customize the arguments (for
  instance to point to disk image files), but it would take a lot of the
  guesswork out.
  
- Similarly, is there information that can be gleaned from the kernel
- build config that would help with configuration?
+ Similarly, there could be information that can be gleaned from the
+ kernel build config that would help with configuration.

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

Title:
  [Feature Request] Automatic device configuration discovery

Status in QEMU:
  New

Bug description:
  Would it be possible to have a script that enumerates the device tree
  of a Linux host and generates a qemu command line that would recreate
  it under emulation? The user would have to customize the arguments
  (for instance to point to disk image files), but it would take a lot
  of the guesswork out.

  Similarly, there could be information that can be gleaned from the
  kernel build config that would help with configuration.

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

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

* [Qemu-devel] [Bug 1798434] Re: [Feature Request] Automatic device configuration discovery
  2018-10-17 18:21 [Qemu-devel] [Bug 1798434] [NEW] [Feature Request] Automatic device configuration discovery Ryan Govostes
@ 2018-10-17 18:44 ` Peter Maydell
  2018-10-18  5:31 ` Thomas Huth
  1 sibling, 0 replies; 3+ messages in thread
From: Peter Maydell @ 2018-10-17 18:44 UTC (permalink / raw)
  To: qemu-devel

This is occasionally asked for but unfortunately not in the general case
possible. Device trees contain enough information for a guest OS to use
the hardware; they do not contain a full description of how the hardware
is actually configured and connected together, and they don't say
anything about parts of the hardware that are "discoverable" (ie
probeable, like PCI). So there isn't enough information to produce a
full board model, and the parts that correspond to QEMU command line
options (like pluggable devices such as ethernet cards) aren't usually
in the DT at all.

The expected workflow goes the other way around -- you start by picking
a machine type that QEMU models, and then configure the kernel and use
the device tree that is intended for it, in the same way you would if
you wanted to get Linux running on a real hardware board.

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

Title:
  [Feature Request] Automatic device configuration discovery

Status in QEMU:
  New

Bug description:
  Would it be possible to have a script that enumerates the device tree
  of a Linux host and generates a qemu command line that would recreate
  it under emulation? The user would have to customize the arguments
  (for instance to point to disk image files), but it would take a lot
  of the guesswork out.

  Similarly, there could be information that can be gleaned from the
  kernel build config that would help with configuration.

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

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

* [Qemu-devel] [Bug 1798434] Re: [Feature Request] Automatic device configuration discovery
  2018-10-17 18:21 [Qemu-devel] [Bug 1798434] [NEW] [Feature Request] Automatic device configuration discovery Ryan Govostes
  2018-10-17 18:44 ` [Qemu-devel] [Bug 1798434] " Peter Maydell
@ 2018-10-18  5:31 ` Thomas Huth
  1 sibling, 0 replies; 3+ messages in thread
From: Thomas Huth @ 2018-10-18  5:31 UTC (permalink / raw)
  To: qemu-devel

Right, and since QEMU also only supports a limited set of devices, there
is no chance that you can mirror an arbitrary host this way. But if you
want to convert a host into a VM and do not care whether each and every
detail can be mirrored, have a look at http://libguestfs.org/virt-
p2v.1.html - that's likely the best solution so far.

** Changed in: qemu
       Status: New => Won't Fix

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

Title:
  [Feature Request] Automatic device configuration discovery

Status in QEMU:
  Won't Fix

Bug description:
  Would it be possible to have a script that enumerates the device tree
  of a Linux host and generates a qemu command line that would recreate
  it under emulation? The user would have to customize the arguments
  (for instance to point to disk image files), but it would take a lot
  of the guesswork out.

  Similarly, there could be information that can be gleaned from the
  kernel build config that would help with configuration.

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

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

end of thread, other threads:[~2018-10-18  5:40 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2018-10-17 18:21 [Qemu-devel] [Bug 1798434] [NEW] [Feature Request] Automatic device configuration discovery Ryan Govostes
2018-10-17 18:44 ` [Qemu-devel] [Bug 1798434] " Peter Maydell
2018-10-18  5:31 ` Thomas Huth

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.