| Age | Commit message (Collapse) | Author | Files | Lines |
|
Fix what looks like an incomplete conversion to egg.mk (PLIST commited but
not Makefile?)
|
|
Untested because of
ld -N -T out/romlayout32flat.lds out/rom16.strip.o out/rom32seg.strip.o out/code32flat.o -o out/rom.o
ld: cannot find out/rom16.strip.o: No such file or directory
ld: cannot find out/rom32seg.strip.o: No such file or directory
on -current/amd64.
|
|
PR pkg/56411 also apply, so pretend that eventfd support is not there.
To be revisited after the freeze.
|
|
Changes since 4.13.2: inlcude security fixes for all XSA known to date
(up to XSA-369). Other minor bug fixes.
|
|
are not used in the file, even if not declared static.
Add __attribute__((externally_visible)) to memcpy() to force gcc to
include it.
Fixes build on -current (gcc 9)
This is a build fix so no PKGREVISION bump
|
|
Also, fix xenstored looping keeping the CPU 100% busy and leaking
file descriptors.
|
|
|
|
to xenstore permissions.
|
|
XSA up to XSA347, and an improved fix for XSA 286.
|
|
|
|
Roman Shaposhnik via xen-devel) as qemu-xen-traditional does.
Also set an XEN_DOMAIN_ID environnement variable, so that the xenstore can
be looked up from qemu scripts.
While there, check /usr/include/xen/xenio.h presense instead of relying
only on ONLY_FOR_PLATFORM. This way this package can be built on recent
9.0_STABLE.
Bump PKGREVISION.
|
|
include files.
Build seabios and ipxe, they're needed by qemu-xen (ipxe not strictly
needed but it's convenient to have)
Switch default device model from qemu-xen-traditional to qemu-xen
(the former being unmaintained)
Add upstream patch for XSA335 security issue.
Bump PKGREVISION.
|
|
At this time xentools413 will only build on a very recent -current (as of
an hour ago or do - with /usr/include/xen/xenio.h 1.12 or newer)
Xen is a hypervisor which supports running multiple guest operating
systems on a single machine. Guest OSes (also called "domains")
can be either paravirtualised (i.e. make hypercalls in order to
access hardware), run in HVM (Hardware Virtualisation Mode) where
they will be presented with virtual devices, or a combination where
they use hypercalls to access hardware but manage memory themselves.
At boot, the xen kernel is loaded along with the guest kernel for
the first domain (called domain0). domain0 has privileges to access
the physical hardware (PCI and ISA devices), administrate other
domains and provide virtual devices (disks and network) to other
domains.
|