virtualization
Here are 519 public repositories matching this topic...
Hi there! I wanted to propose adding the following badge to the README to indicate how many TODO comments are in this codebase:
The badge links to tickgit.com which is a free service that indexes and displays TODO comme
The seccomp filters are tailored for the Firecracker musl build. We should specify how to run Firecracker when building it with gnu as well.
Requested by @rbrasga in firecracker-microvm/firecracker#1515 (comment)
Can you automatically build libv86.js on Travis CI at every commit and publish it to some server or GitHub Pages? This would be very good because users then won't need to install and configure Closure Compiler and other build dependencies.
Can you also configure Makefile to also build sourcemap file for libv86.js?
Also, the version on your website is very old (f
please refer react native issue template: facebook/react-native#19799 we can make a new issue template like this:
have you search the existing issue list?
have you use the latest DroidPlugin release?
1,Environment: os version. DroidPlugin version
2, Description
3,reproduce step.
.......
if we describe the issue much detail we can get more info to fix problem
Kata shimv2 does not have any tracing yet. Will be useful to add this.
Is this a BUG REPORT or FEATURE REQUEST?:
Uncomment only one, leave it on its own line:
/kind bug
/kind enhancement
What happened:
A virt-launcher pod is being deleted because the QEMU crashed. This happens fast and if "spec
-
Updated
May 6, 2020 - Ruby
-
Updated
May 26, 2020 - Ruby
-
Updated
May 21, 2020 - JavaScript
I am using a custom prop to force my list to re-render, as recommended in the readme. However, doing so causes me this warning:
Warning: React does not recognize the
isScrollingprop on a DOM element. If you intentionally want it to appear in the DOM as a custom attribute, spell it as lowercase `isscrol
Describe the bug
While playing videos, there's a general jerkiness every few seconds.
To Reproduce
Steps to reproduce the behavior:
- Configure a CPU-optimized Digital Ocean droplet with 8Gb of RAM in your closests datacentre
- Install Neko as per instructions
- Log in, go to this trailer, play it, full
-
Updated
May 6, 2020 - Shell
When using the box built with osx-vm-templates, there is always some setting to tune in upper Vagrantfile.
Can we built those common settings into box with vagrantfile_template
There is a good [reference here](https://github.com/blueimp/boot2docker/blob/b33c71d07f2cfdc94e6f9150793bbb47a78f6b70/packer.jso
-
Updated
May 18, 2020 - JavaScript
Right now when a container exits you get some confusing error logs like this:
time="2019-12-11T20:03:38.436612731Z" level=error msg="error copying io" ExecID= TaskID=container-80-3 error="read unix @->firecracker.vsock: use of closed network connection" runtime=aws.firecracker stream=stdout vmID=80
or this:
time="2019-12-11T20:03:38.443037999Z" level=debug msg="[ 81.326403] a
-
Updated
May 17, 2020 - HTML
I'm currently testing the 1.0.1 release and discovered that the --wq-threads options isn't documented anywhere.
The only information I was able to find is in the commit log (c84b4fc1021df87bba161b758fb068a4333b9ad6).
"If the option isn't passed, sheep uses unlimited queues but it is highly dicouraged for stable and high IOPS."
It would be great to add something about this option. Moreover t
VFIO testing with NEMU is manual. The initial cut of the documentation on how to perform the same using a GPU is described here. Please review. We will add additional devices which have simpler VFIO setup.
Documentation
-
Updated
Apr 7, 2020 - Python
-
Updated
May 25, 2020 - C
Document that seccomp is on and how to disable it along with a pointer on how to identify missing syscalls during development.
I don't need no help with that of course, but this template better be fixed.
Context:
Often people at the forum got very confused about terms in XCP-ng universe, which software does what and so on. Sometimes the language is the biggest problem and you have to explain the same stuff many times and with many missunderstandings on both sides.
Idea:
We should draw a picture where one can easily see "what does what" and how the pieces interact with each other.
-
Updated
May 25, 2020
-
Updated
Jan 19, 2019 - C
-
Updated
Apr 16, 2019 - Go
Story
As a VIC developer I want an easy way to determine how a package functions and how it should be used.
As a VIC developer I want to easily see the call logic of code that I'm changing or reviewing
Details
We currently have a significant lack of good package documentation, at least in part because review inline doc is hard without generated output available. This documentation is
Improve this page
Add a description, image, and links to the virtualization topic page so that developers can more easily learn about it.
Add this topic to your repo
To associate your repository with the virtualization topic, visit your repo's landing page and select "manage topics."
Actual results
The content of the output indicates that the tool is not aware of the input command, as illustrated:
vagrant global-status --prune.