Re: [Libguestfs] translating CD-ROM device paths from i440fx to Q35 in virt-v2v (was: test-v2v-cdrom: update the CD-ROM's bus to SATA in the converted domain)

On Thu, Sep 30, 2021 at 12:53:51PM +0100, Richard W.M. Jones wrote: > On Thu, Sep 30, 2021 at 01:12:39PM +0200, Laszlo Ersek wrote: > > All this requires virt-v2v to parse complete elements from the > > original domain XML, and to generate complete elements in the > > destination domain XML. Is

Re: translating CD-ROM device paths from i440fx to Q35 in virt-v2v (was: test-v2v-cdrom: update the CD-ROM's bus to SATA in the converted domain)

On Thu, Sep 30, 2021 at 01:12:39PM +0200, Laszlo Ersek wrote: > On 09/29/21 21:22, Richard W.M. Jones wrote: > Please correct me if I'm wrong: at the moment, I believe virt-v2v parses > and manipulates the following elements and attributes in the domain XML: > > > > >

Re: translating CD-ROM device paths from i440fx to Q35 in virt-v2v (was: test-v2v-cdrom: update the CD-ROM's bus to SATA in the converted domain)

On Thu, Sep 30, 2021 at 01:12:39PM +0200, Laszlo Ersek wrote: > All this requires virt-v2v to parse complete elements from the > original domain XML, and to generate complete elements in the > destination domain XML. Is that feasible? The input is not always (in fact, hardly ever) full libvirt

translating CD-ROM device paths from i440fx to Q35 in virt-v2v (was: test-v2v-cdrom: update the CD-ROM's bus to SATA in the converted domain)

(+libvirt-devel) On 09/29/21 21:22, Richard W.M. Jones wrote: > We currently partially install the virtio block drivers in the Windows > guest (just enough to get the guest to boot on the target), and > Windows itself re-installs the virtio block driver and other drivers > it needs, and that's