[Users] Change virtual disk interface
I have serveral "old" KVM virtual images, all off them using virtio for networking and disks. Trying to import these into my EXPORT datastore ends up with an error: virt-v2v -i libvirt -o rhev -os 10.0.0.3:/nfs/export -n br0 PXE5-test PXE5.img: 100% [=====================================================] virt-v2v: WARNING: Unable to convert this guest operating system. Its storage will be transfered and a domain created for it, but it may not operate correctly without manual reconfiguration. The domain will present all storage devices as ide, all network interfaces as rtl8139 and the host as x86_64. virt-v2v: PXE5-test configured without virtio drivers. How can I avoid these errors? How can I fix this error. After restoring the image, I am able to change the network interface from rtl8139 to Virtio. However; I cannot change the disk. In the admin console going to Virtual Machines --> <virtual machine> --> Virtual Disks --> <disk> --> Edit gives a menu, but the only option I can change is "is bootable". Options like "Interface" are grey and cannot be modified.
On 02/28/2012 10:26 AM, wdh@dds.nl wrote:
I have serveral "old" KVM virtual images, all off them using virtio for networking and disks. Trying to import these into my EXPORT datastore ends up with an error:
virt-v2v -i libvirt -o rhev -os 10.0.0.3:/nfs/export -n br0 PXE5-test PXE5.img: 100% [=====================================================]
virt-v2v: WARNING: Unable to convert this guest operating system. Its storage will be transfered and a domain created for it, but it may not operate correctly without manual reconfiguration. The domain will present all storage devices as ide, all network interfaces as rtl8139 and the host as x86_64. virt-v2v: PXE5-test configured without virtio drivers.
How can I avoid these errors? How can I fix this error.
matt/rich - thoughts?
After restoring the image, I am able to change the network interface from rtl8139 to Virtio. However; I cannot change the disk. In the admin console going to Virtual Machines --> <virtual machine> --> Virtual Disks --> <disk> --> Edit gives a menu, but the only option I can change is "is bootable". Options like "Interface" are grey and cannot be modified.
please try via the rest API/sdk/cli, iirc, this is just a UI limitation. (feel free to open a bug about this)
On Tue, Feb 28, 2012 at 03:56:19PM +0200, Itamar Heim wrote:
On 02/28/2012 10:26 AM, wdh@dds.nl wrote:
I have serveral "old" KVM virtual images, all off them using virtio for networking and disks. Trying to import these into my EXPORT datastore ends up with an error:
virt-v2v -i libvirt -o rhev -os 10.0.0.3:/nfs/export -n br0 PXE5-test PXE5.img: 100% [=====================================================]
virt-v2v: WARNING: Unable to convert this guest operating system. Its storage will be transfered and a domain created for it, but it may not operate correctly without manual reconfiguration. The domain will present all storage devices as ide, all network interfaces as rtl8139 and the host as x86_64. virt-v2v: PXE5-test configured without virtio drivers.
How can I avoid these errors? How can I fix this error.
matt/rich - thoughts?
Matt's actually off today, but I'm sure he'll answer in more detail tomorrow. However the reason for getting this error is that your guest isn't one of those supported by virt-v2v (which is roughly: RHEL 3/4/5/6 and clones, Windows XP and above, Fedora). If virt-v2v doesn't understand the guest, it tries only a very minimal and conservative form of conversion. It's not clear what this PXE5-test guest is. You can find out by using virt-inspector (on RHEL 6, replace 'virt-inspector' with 'virt-inspector2'): virt-inspector -a /path/to/PXE5-test.img For examples see: http://libguestfs.org/virt-inspector.1.html#xml_format Rich. -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones libguestfs lets you edit virtual machines. Supports shell scripting, bindings from many languages. http://libguestfs.org
Hi Richard, Centos 5.7 that is: virt-inspector -a /var/lib/libvirt/images/PXE5.img <?xml version="1.0"?> <operatingsystems> <operatingsystem> <root>/dev/VG_OS/LV_ROOT</root> <name>linux</name> <arch>x86_64</arch> <distro>centos</distro> <product_name>CentOS release 5.7 (Final)</product_name> <major_version>5</major_version> <minor_version>7</minor_version> <package_format>rpm</package_format> ~ Winfried "Richard W.M. Jones" <rjones@redhat.com> schreef:
On Tue, Feb 28, 2012 at 03:56:19PM +0200, Itamar Heim wrote: > On 02/28/2012 10:26 AM, wdh@dds.nl wrote:
I have serveral "old" KVM virtual images, all off them using virtio for networking and disks. Trying to import these into my EXPORT datastore ends up with an error:
virt-v2v -i libvirt -o rhev -os 10.0.0.3:/nfs/export -n br0 PXE5-test PXE5.img: 100% [=====================================================]
virt-v2v: WARNING: Unable to convert this guest operating system. Its storage will be transfered and a domain created for it, but it may not operate correctly without manual reconfiguration. The domain will present all storage devices as ide, all network interfaces as rtl8139 and the host as x86_64. virt-v2v: PXE5-test configured without virtio drivers.
How can I avoid these errors? How can I fix this error.
matt/rich - thoughts? Matt's actually off today, but I'm sure he'll answer in more detail tomorrow.
However the reason for getting this error is that your guest isn't one of those supported by virt-v2v (which is roughly: RHEL 3/4/5/6 and clones, Windows XP and above, Fedora). If virt-v2v doesn't understand the guest, it tries only a very minimal and conservative form of conversion.
It's not clear what this PXE5-test guest is. You can find out by using virt-inspector (on RHEL 6, replace 'virt-inspector' with 'virt-inspector2'):
virt-inspector -a /path/to/PXE5-test.img
For examples see:
http://libguestfs.org/virt-inspector.1.html#xml_format
Rich.
-- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones libguestfs lets you edit virtual machines. Supports shell scripting,bindings from many languages. http://libguestfs.org
Met vriendelijke groet, Winfried de Heiden
On Tue, Feb 28, 2012 at 03:30:03PM +0100, Winfried de Heiden wrote:
Hi Richard,
Centos 5.7 that is:
virt-inspector -a /var/lib/libvirt/images/PXE5.img <?xml version="1.0"?> <operatingsystems> <operatingsystem> <root>/dev/VG_OS/LV_ROOT</root> <name>linux</name> <arch>x86_64</arch> <distro>centos</distro> <product_name>CentOS release 5.7 (Final)</product_name> <major_version>5</major_version> <minor_version>7</minor_version> <package_format>rpm</package_format>
In the current RHEL 6 virt-v2v, CentOS support is either disabled or wasn't yet written, I can't remember which ... CentOS conversions, including virtio conversion, can be done by virt-v2v upstream. Rich. -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones Read my programming blog: http://rwmj.wordpress.com Fedora now supports 80 OCaml packages (the OPEN alternative to F#) http://cocan.org/getting_started_with_ocaml_on_red_hat_and_fedora
Hi Richard, Any chance for a workaround: changing /etc/redhat-release first...., modify some virt-v2v configuration file? Centos is just my poor men@home lab... Winfried "Richard W.M. Jones" <rjones@redhat.com> schreef:
On Tue, Feb 28, 2012 at 03:30:03PM +0100, Winfried de Heiden wrote:
Hi Richard,
Centos 5.7 that is:
virt-inspector -a /var/lib/libvirt/images/PXE5.img <?xml version="1.0"?> <operatingsystems> <operatingsystem> <root>/dev/VG_OS/LV_ROOT</root> <name>linux</name> <arch>x86_64</arch> <distro>centos</distro> <product_name>CentOS release 5.7 (Final)</product_name> <major_version>5</major_version> <minor_version>7</minor_version> <package_format>rpm</package_format> In the current RHEL 6 virt-v2v, CentOS support is either disabled or wasn't yet written, I can't remember which ... CentOS conversions, including virtio conversion, can be done by virt-v2v upstream.
Rich.
-- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones Read my programming blog: http://rwmj.wordpress.com Fedora now supports 80 OCaml packages (the OPEN alternative to F#)http://cocan.org/getting_started_with_ocaml_on_red_hat_and_fedora
Met vriendelijke groet, Winfried de Heiden
On 02/28/2012 02:51 PM, Winfried de Heiden wrote:
Hi Richard,
Any chance for a workaround: changing /etc/redhat-release first...., modify some virt-v2v configuration file?
There's a reasonable chance that would work. I couldn't say for sure, though.
Centos is just my poor men@home lab...
As Rich mentioned, we recently added CentOS support upstream. It should be in RHEL 6.3. Matt
Winfried
"Richard W.M. Jones" <rjones@redhat.com <mailto:rjones@redhat.com>> schreef:
On Tue, Feb 28, 2012 at 03:30:03PM +0100, Winfried de Heiden wrote:
Hi Richard,
Centos 5.7 that is:
virt-inspector -a /var/lib/libvirt/images/PXE5.img <?xml version="1.0"?> <operatingsystems> <operatingsystem> <root>/dev/VG_OS/LV_ROOT</root> <name>linux</name> <arch>x86_64</arch> <distro>centos</distro> <product_name>CentOS release 5.7 (Final)</product_name> <major_version>5</major_version> <minor_version>7</minor_version> <package_format>rpm</package_format> In the current RHEL 6 virt-v2v, CentOS support is either disabled or wasn't yet written, I can't remember which ... CentOS conversions, including virtio conversion, can be done by virt-v2v upstream.
Rich.
-- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones Read my programming blog: http://rwmj.wordpress.com Fedora now supports 80 OCaml packages (the OPEN alternative to F#)http://cocan.org/getting_started_with_ocaml_on_red_hat_and_fedora
Met vriendelijke groet,
Winfried de Heiden
-- Matthew Booth, RHCA, RHCSS Red Hat Engineering, Virtualisation Team GPG ID: D33C3490 GPG FPR: 3733 612D 2D05 5458 8A8A 1600 3441 EA19 D33C 3490
On 02/28/2012 10:26 AM, wdh@dds.nl wrote: > I have serveral "old" KVM virtual images, all off them using virtio for
networking and disks. Trying to import these into my EXPORT datastore ends up with an error:
virt-v2v -i libvirt -o rhev -os 10.0.0.3:/nfs/export -n br0 PXE5-test PXE5.img: 100% [=====================================================]
virt-v2v: WARNING: Unable to convert this guest operating system. Its storage will be transfered and a domain created for it, but it may not operate correctly without manual reconfiguration. The domain will
Bug created: https://bugzilla.redhat.com/show_bug.cgi?id=798277 Winfried Itamar Heim <iheim@redhat.com> schreef: present
all storage devices as ide, all network interfaces as rtl8139 and the host as x86_64. virt-v2v: PXE5-test configured without virtio drivers.
How can I avoid these errors? How can I fix this error. matt/rich - thoughts? After restoring the image, I am able to change the network interface from rtl8139 to Virtio. However; I cannot change the disk. In the admin console going to Virtual Machines --> <virtual machine> --> Virtual Disks --> <disk> --> Edit gives a menu, but the only option I can change is "is bootable". Options like "Interface" are grey and cannot be modified. please try via the rest API/sdk/cli, iirc, this is just a UI limitation.(feel free to open a bug about this)
Met vriendelijke groet, Winfried de Heiden
Hi, /"please try via the rest API/sdk/cli, iirc, this is just a UI limitation"/ Any sugestions for using the rest API? This is quite new for me.... :( Winfried Itamar Heim <iheim@redhat.com> schreef:
networking and disks. Trying to import these into my EXPORT datastore ends up with an error:
virt-v2v -i libvirt -o rhev -os 10.0.0.3:/nfs/export -n br0 PXE5-test PXE5.img: 100% [=====================================================]
virt-v2v: WARNING: Unable to convert this guest operating system. Its storage will be transfered and a domain created for it, but it may not operate correctly without manual reconfiguration. The domain will present all storage devices as ide, all network interfaces as rtl8139 and the host as x86_64. virt-v2v: PXE5-test configured without virtio drivers.
How can I avoid these errors? How can I fix this error. matt/rich - thoughts? After restoring the image, I am able to change the network interface from rtl8139 to Virtio. However; I cannot change the disk. In the admin console going to Virtual Machines --> <virtual machine> --> Virtual Disks --> <disk> --> Edit gives a menu, but the only option I can change is "is bootable". Options like "Interface" are grey and cannot be modified.
On 02/28/2012 10:26 AM, wdh@dds.nl wrote: > I have serveral "old" KVM virtual images, all off them using virtio for please try via the rest API/sdk/cli, iirc, this is just a UI limitation.(feel free to open a bug about this)
Met vriendelijke groet, Winfried de Heiden
participants (5)
-
Itamar Heim -
Matthew Booth -
Richard W.M. Jones -
wdh＠dds.nl -
Winfried de Heiden