Juergen Gross:
> Commit 96edd61dcf44362d3ef0bed1a5361e0ac7886a63 ("xen/balloon: don't
> online new memory initially") introduced a regression when booting a
> HVM domain with memory less than mem-max: instead of ballooning down
> immediately the system would try to use the memory up to mem-max
> re
ally we have to trigger the ballooning process at once.
>>>>>
>>>>> Cc: # 4.13
>>>>> Fixes: 96edd61dcf44362d3ef0bed1a5361e0ac7886a63 ("xen/balloon: don't
>>>>>online new memory initially")
>>>>>
>>>&
Juergen Gross:
> When setting up the Xenstore watch for the memory target size the new
> watch will fire at once. Don't try to reach the configured target size
> by onlining new memory in this case, as the current memory size will
> be smaller in almost all cases due to e.g. BIOS reserved pages.
>
Hi,
when I try to attach a pci device to a running HVM the interrupt setup
inside the domain fails if the Linux has PV support:
kernel: xen:events: Failed to obtain physical IRQ 36
When I use [0] to get a more verbose output I get
kernel: xen:events: Failed to obtain physical IRQ 36 (error
Hi,
I'm currently debugging why hotplugging pci devices doesn't work with the
linux based stubdom used in the next Qubes release (based on Anthony's
and Eric's patches).
When attaching a pci device to a running domain qemu in the stubdom
throws the following error:
[00:06.0] xen_pt_region_upda
