-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 12/27/18 9:30 PM, Zrubi wrote:
> And according to the mentioned links, the resulted file can be
> injected, and then your windows VM wold be happy and activated just
> as your original hardware :)
here is te relevant part from the libvirt xml:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 12/27/18 9:03 PM, Marek Marczykowski-Górecki wrote:
> AFAIU, you try to provide licence key to Windows directly, right?
> Is that about the key extracted from the same machine, or arbitrary
> one?
Yes, from the same one. As (nearly) all the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Thu, Dec 27, 2018 at 08:30:48PM +0100, Zrubi wrote:
> On 12/27/18 6:10 PM, Marek Marczykowski-Górecki wrote:
>
> > It think libvirt Xen (libxl) driver does not support smbios
> > options. Quick grep on the sources says its supported only in
> >
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 12/27/18 6:10 PM, Marek Marczykowski-Górecki wrote:
> It think libvirt Xen (libxl) driver does not support smbios
> options. Quick grep on the sources says its supported only in
> qemu/kvm... xl.cfg man page says something about
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Thu, Dec 27, 2018 at 04:53:57PM +0100, Zrubi wrote:
> On 12/27/18 2:32 PM, Wojtek Porczyk wrote:
>
> > 1) and lines are not inside any {% block %} 2)
> > there is no "sysinfo" block in parent template
> >
> > For a quick-and-dirty hack, if
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 12/27/18 2:32 PM, Wojtek Porczyk wrote:
> 1) and lines are not inside any {% block %} 2)
> there is no "sysinfo" block in parent template
>
> For a quick-and-dirty hack, if you intend this node to be
> a child of , just append it to some
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Thu, Dec 27, 2018 at 01:49:14PM +0100, Zrubi wrote:
> I need to "play" with custom xml configs, in order to get hardware
> info via dmidecode inside a VM.
(...)
> Am I missed something?
That's not how jinja template inheritance works. After {%
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi,
I need to "play" with custom xml configs, in order to get hardware
info via dmidecode inside a VM.
According to these - it should be possible.:
https://github.com/QubesOS/qubes-issues/issues/1798
