search for: pvpanic

On Wed, Apr 05, 2017 at 02:43:11PM +0100, Richard W.M. Jones wrote: > When outputting libvirt XML, create virtio-rng, a memory balloon > device, and a pvpanic device, if the guest supports it. > --- > v2v/create_libvirt_xml.ml | 19 +++++++++++++++++++ > 1 file changed, 19 insertions(+) > > diff --git a/v2v/create_libvirt_xml.ml b/v2v/create_libvirt_xml.ml > index fc7196595..58f720ac3 100644 > --- a/v2v/create_libvirt_xml.ml > +...

When outputting libvirt XML, create virtio-rng, a memory balloon device, and a pvpanic device, if the guest supports it. --- v2v/create_libvirt_xml.ml | 19 +++++++++++++++++++ 1 file changed, 19 insertions(+) diff --git a/v2v/create_libvirt_xml.ml b/v2v/create_libvirt_xml.ml index fc7196595..58f720ac3 100644 --- a/v2v/create_libvirt_xml.ml +++ b/v2v/create_libvirt_xml.ml @@ -338,6...

...ce in the output metadata. Patch 1-5 add this modelling, and support for -o libvirt. I didn't (yet?) add support for -o rhv, because I couldn't see from the oVirt Engine source how to describe that in the OVF. As part of the same set of changes, I also added support for virtio-balloon and pvpanic, which work in basically the same way as virtio-rng, so it was convenient to add all three at the same time. Rich.

v1 was posted here: https://www.redhat.com/archives/libguestfs/2017-April/msg00031.html v1 -> v2: - Add support for -o glance. - Add support for -o qemu. - Fix the -o libvirt support for balloon as pointed out by Dan. - Fix a test failure caused by changing libvirt XML output. Rich.

v1: https://www.redhat.com/archives/libguestfs/2017-April/msg00031.html v2: https://www.redhat.com/archives/libguestfs/2017-April/msg00040.html v2 -> v3: - Fix Xen PV-only kernel detection. Rich.

v1: https://www.redhat.com/archives/libguestfs/2017-April/msg00031.html v2: https://www.redhat.com/archives/libguestfs/2017-April/msg00040.html v3: https://www.redhat.com/archives/libguestfs/2017-April/msg00051.html v3 -> v4: - Properly fix Xen PV-only kernel detection, and test it. Rich.

...quot; in - let supports_virtio_rng = - kernel_supports "virtio-rng" "HW_RANDOM_VIRTIO" in - let supports_virtio_balloon = - kernel_supports "virtio_balloon" "VIRTIO_BALLOON" in - let supports_isa_pvpanic = - kernel_supports "pvpanic" "PVPANIC" in - let is_xen_pv_only_kernel = - check_config "X86_XEN" config_file || - check_config "X86_64_XEN" config_file in + let supports_virtio_blk = +...

...S); - (* The first disk, assumed to be the system disk, will be called * "guestname". Subsequent disks, assumed to be data disks, * will be called "guestname-disk2" etc. The manual strongly @@ -143,6 +140,11 @@ object (* XXX Neither memory balloon nor pvpanic are supported by * Glance at this time. *) + (match target_firmware with + | TargetBIOS -> () + | TargetUEFI -> + push_back properties ("hw_firmware_type", "uefi") + ); let properties = List...

...d Play ACPI [ 2.200079] ------------[ cut here ]------------ [ 2.200661] kernel BUG at include/linux/virtio_config.h:125! [ 2.201004] invalid opcode: 0000 [#1] SMP [ 2.201004] Modules linked in: snd_timer snd virtio_balloon virtio_console serio_raw parport_pc parport i2c_piix4 soundcore pvpanic btrfs qxl xor raid6_pq drm_kms_helper ttm drm 8139too virtio_pci virtio_rini [ 2.201004] CPU: 0 PID: 71 Comm: kworker/0:2 Not tainted 3.18.0-0.rc1.git0.1.fc22.x86_64 #1 [ 2.201004] Hardware name: Bochs Bochs, BIOS Bochs 01/01/2011 [ 2.201004] Workqueue: events control_work_handler [virtio_...

...d Play ACPI [ 2.200079] ------------[ cut here ]------------ [ 2.200661] kernel BUG at include/linux/virtio_config.h:125! [ 2.201004] invalid opcode: 0000 [#1] SMP [ 2.201004] Modules linked in: snd_timer snd virtio_balloon virtio_console serio_raw parport_pc parport i2c_piix4 soundcore pvpanic btrfs qxl xor raid6_pq drm_kms_helper ttm drm 8139too virtio_pci virtio_rini [ 2.201004] CPU: 0 PID: 71 Comm: kworker/0:2 Not tainted 3.18.0-0.rc1.git0.1.fc22.x86_64 #1 [ 2.201004] Hardware name: Bochs Bochs, BIOS Bochs 01/01/2011 [ 2.201004] Workqueue: events control_work_handler [virtio_...

Metapackages are valid packages with no files, used to easily install something without manually installing bits. This is the case of the "kernel" package in Fedora/RHEL/etc in the last couple of years. --- v2v/linux_kernels.ml | 1 - 1 file changed, 1 deletion(-) diff --git a/v2v/linux_kernels.ml b/v2v/linux_kernels.ml index 9a41225a..78c1ee59 100644 --- a/v2v/linux_kernels.ml +++

...ersion", string_of_int x) + | x, y -> push_back properties ("os_version", sprintf "%d.%d" x y) + ); + if guestcaps.gcaps_virtio_rng then + push_back properties ("hw_rng_model", "virtio"); + (* XXX Neither memory balloon nor pvpanic are supported by + * Glance at this time. + *) + (match target_firmware with + | TargetBIOS -> () + | TargetUEFI -> + push_back properties ("hw_firmware_type", "uefi") + ); + + !properties in + (* The first disk, assumed...

...low. +static const struct acpi_device_id virtio_mmio_acpi_match[] = { + { "QEMU0005", }, + { "1AF4103F", }, + { } +}; +MODULE_DEVICE_TABLE(acpi, virtio_mmio_acpi_match); > It's just playing nice with others. > > We could have done something similar to pvpanic as well, except we > didn't and guests using the QEMU prefix have been released, > so we have to keep using that. > >>> Since we have one for virtio, it seems neater to use that >>> rather than LNRO. For the device ID, use 103F which is a legacy ID that >>>...

...low. +static const struct acpi_device_id virtio_mmio_acpi_match[] = { + { "QEMU0005", }, + { "1AF4103F", }, + { } +}; +MODULE_DEVICE_TABLE(acpi, virtio_mmio_acpi_match); > It's just playing nice with others. > > We could have done something similar to pvpanic as well, except we > didn't and guests using the QEMU prefix have been released, > so we have to keep using that. > >>> Since we have one for virtio, it seems neater to use that >>> rather than LNRO. For the device ID, use 103F which is a legacy ID that >>>...

...iver bug that caused the error, as the guest continues to run. To > address that, we could probably add a new error action option to virtio > devices, similar to the "read/write werror" in block layer, so the vm could be > paused and the management will get an event in QMP like pvpanic. This work can > be done on top. At the architectural level, that's only one concern. Others would be - workloads such as openstack handle guest crash better than a guest that's e.g. slow because of a memory leak - it's easier for guests to probe host for security issues if gue...

...iver bug that caused the error, as the guest continues to run. To > address that, we could probably add a new error action option to virtio > devices, similar to the "read/write werror" in block layer, so the vm could be > paused and the management will get an event in QMP like pvpanic. This work can > be done on top. At the architectural level, that's only one concern. Others would be - workloads such as openstack handle guest crash better than a guest that's e.g. slow because of a memory leak - it's easier for guests to probe host for security issues if gue...

..., as the guest continues to run. To > > > address that, we could probably add a new error action option to virtio > > > devices, similar to the "read/write werror" in block layer, so the vm could be > > > paused and the management will get an event in QMP like pvpanic. This work can > > > be done on top. > > > > At the architectural level, that's only one concern. Others would be > > - workloads such as openstack handle guest crash better than > > a guest that's e.g. slow because of a memory leak > > What memor...

..., as the guest continues to run. To > > > address that, we could probably add a new error action option to virtio > > > devices, similar to the "read/write werror" in block layer, so the vm could be > > > paused and the management will get an event in QMP like pvpanic. This work can > > > be done on top. > > > > At the architectural level, that's only one concern. Others would be > > - workloads such as openstack handle guest crash better than > > a guest that's e.g. slow because of a memory leak > > What memor...

...0508] BUG: unable to handle kernel NULL pointer dereference at (null) [ 165.631027] IP: [<ffffffff817b1035>] __mutex_lock_slowpath+0x75/0x100 [ 165.631219] PGD 368a2067 PUD 797d3067 PMD 0 [ 165.631454] Oops: 0002 [#1] SMP [ 165.631632] Modules linked in: parport_pc 8250_fintek pvpanic parport snd_pcm snd_timer snd soundcore i2c_piix4 joydev pcspkr psmouse serio_raw evbug mac_hid hid_generic usbhid hid floppy [ 165.632010] CPU: 0 PID: 22838 Comm: dd Not tainted 3.18.0-031800-generic #201412071935 [ 165.632010] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS Bochs 01...

...0508] BUG: unable to handle kernel NULL pointer dereference at (null) [ 165.631027] IP: [<ffffffff817b1035>] __mutex_lock_slowpath+0x75/0x100 [ 165.631219] PGD 368a2067 PUD 797d3067 PMD 0 [ 165.631454] Oops: 0002 [#1] SMP [ 165.631632] Modules linked in: parport_pc 8250_fintek pvpanic parport snd_pcm snd_timer snd soundcore i2c_piix4 joydev pcspkr psmouse serio_raw evbug mac_hid hid_generic usbhid hid floppy [ 165.632010] CPU: 0 PID: 22838 Comm: dd Not tainted 3.18.0-031800-generic #201412071935 [ 165.632010] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS Bochs 01...