Displaying 20 results from an estimated 1000 matches similar to: "Openshift Kubevirt lab?"
2018 Mar 29
1
Re: [PATCH FOR DISCUSSION ONLY v2] v2v: Add -o kubevirt output mode.
On Thu, Mar 29, 2018 at 05:26:13PM +0200, Piotr Kliczewski wrote:
> Richard,
>
> Great progress. I really like it!!!
>
> Here is what I noticed:
>
> I see that in the yaml file we provide short-id as:
>
> os:
> osinfo: 'rhel7.2'
>
> whereas kubevirt expects it in metadata:
>
> metadata:
> labels:
> kubevirt.io/os: win10
>
2018 Mar 27
1
[PATCH FOR DISCUSSION ONLY] v2v: Add -o kubevirt output mode.
XXX
No documentation.
Only handles one disk.
Network cards?
Do we need to escape YAML format?
What firmware types does kubevirt support.
---
v2v/Makefile.am | 2 +
v2v/cmdline.ml | 21 ++++++++++
v2v/output_kubevirt.ml | 103 ++++++++++++++++++++++++++++++++++++++++++++++++
v2v/output_kubevirt.mli | 24 +++++++++++
4 files changed, 150 insertions(+)
diff --git
2020 Apr 06
1
Wiki edit: HowTos/Virtualization
Hello everyone,
First time contributor ... long time listener!
Your /FirstnameLastname/ username: ChrisCallegari
I am working with Open Source project called KubeVirt. Part of our mission
is to ensure that the project can easily be deployed ... this includes host
os and Kubernetes. We dev and test on Fedora, CentOS, and RHEL and several
Debian derivatives for OS's and minikube for
2018 Mar 27
6
[PATCH FOR DISCUSSION ONLY v2] v2v: Add -o kubevirt output mode.
Fixes some of the more egregious problems with v1, and also
applies properly to the head of git without needing any other
patches.
Rich.
2018 Mar 29
0
Re: [PATCH FOR DISCUSSION ONLY v2] v2v: Add -o kubevirt output mode.
Richard,
Great progress. I really like it!!!
Here is what I noticed:
I see that in the yaml file we provide short-id as:
os:
osinfo: 'rhel7.2'
whereas kubevirt expects it in metadata:
metadata:
labels:
kubevirt.io/os: win10
For windows vms we need to create perset like this one [1]. We can add
separator
---
between the objects.
Thanks,
Piotr
[1]
2020 Jul 13
1
Re: nbdkit / exposing disk images in containers
On Sun, Jul 12, 2020 at 11:16:01PM +0300, Nir Soffer wrote:
> On Sat, Jul 11, 2020 at 11:18 AM Richard W.M. Jones <rjones@redhat.com> wrote:
> >
> > KubeVirt is a custom resource (a kind of plugin) for Kubernetes which
> > adds support for running virtual machines. As part of this they have
> > the same problems as everyone else of how to import large disk images
2020 Mar 27
2
Create VM w/ cache=none on tmpfs
Hi,
I've seen that in the past, libvirt couldn't start VMs when the disk
image was stored on a file system that doesn't support direct I/O
having the 'cache=none' configuration [0].
On the KubeVirt project, we have some storage tests on a particular
provider which does just that - try to create / start a VM whose disk
is on tmpfs and whose definition features
2019 Oct 17
2
Transient permission denied errors when sending audit logs
Hi,
In kubevirt we are running into a strange permission problem on
libvirt-5.0. We see transient "Permission Denied" errors when "virAuditSend"
wants to send an audit log. [1] shows the logs of one of these containers.
Here an example:
{"component":"virt-launcher","level":"warning","msg":"Failed to send audit
message
2020 Mar 26
2
Re: Question about local migration between containers
Hi Daniel,
thanks for the quick reply
we did try to override SMBIOS
host_uuid_source = "machine-id"
and it didn't work even that nodes have different
[root@modi01 kubevirt]# ./cluster-up/ssh.sh kind-1.17.0-worker
root@kind-1:/# cat /etc/machine-id
[root@modi01 kubevirt]# ./cluster-up/ssh.sh kind-1.17.0-control-plane
root@kind-1:/# cat /etc/machine-id
2018 May 10
6
e1000 network interface takes a long time to set the link ready
Hi,
In kubevirt, we discovered [1] that whenever e1000 is used for vNIC,
link on the interface becomes ready several seconds after 'ifup' is
executed, which for some buggy images like cirros may slow down boot
process for up to 1 minute [2]. If we switch from e1000 to virtio, the
link is brought up and ready almost immediately.
For the record, I am using the following versions:
- L0
2020 Jul 11
2
nbdkit / exposing disk images in containers
KubeVirt is a custom resource (a kind of plugin) for Kubernetes which
adds support for running virtual machines. As part of this they have
the same problems as everyone else of how to import large disk images
into the system for pets, templates, etc.
As part of the project they've defined a format for embedding a disk
image into a container (unclear why? perhaps so these can be
distributed
2019 Aug 21
2
RLIMIT_MEMLOCK in container environment
Hi all,
KubeVirt uses libvirtd to manage qemu VMs represented as Kubernetes
API resources. In this case, libvirtd is running inside an
unprivileged pod, with some host mounts / capabilities added to the
pod, needed by libvirtd and other services.
One of the capabilities libvirtd requires for successful startup
inside a pod is SYS_RESOURCE. This capability is used to adjust
RLIMIT_MEMLOCK ulimit
2020 Apr 06
4
Re: plug pre-created tap devices to libvirt guests
On 4/6/20 9:54 AM, Daniel P. Berrangé wrote:
> On Mon, Apr 06, 2020 at 03:47:01PM +0200, Miguel Duarte de Mora Barroso wrote:
>> Hi all,
>>
>> I'm aware that it is possible to plug pre-created macvtap devices to
>> libvirt guests - tracked in RFE [0].
>>
>> My interpretation of the wording in [1] and [2] is that it is also
>> possible to plug
2020 Jul 16
1
Re: SELinux labels change in libvirt
On Tue, Jul 14, 2020 at 6:03 PM Daniel P. Berrangé <berrange@redhat.com>
wrote:
> On Tue, Jul 14, 2020 at 04:02:17PM +0300, Ram Lavi wrote:
> > On Tue, Jul 14, 2020 at 3:33 PM Daniel P. Berrangé <berrange@redhat.com>
> > wrote:
> >
> > > On Tue, Jul 14, 2020 at 03:21:17PM +0300, Ram Lavi wrote:
> > > > Hello all,
> > > >
> >
2020 Jun 30
1
Re: plug pre-created tap devices to libvirt guests
On Tue, Jun 30, 2020 at 12:59:03PM +0200, Miguel Duarte de Mora Barroso wrote:
> On Mon, Apr 6, 2020 at 4:03 PM Laine Stump <lstump@redhat.com> wrote:
> >
> > On 4/6/20 9:54 AM, Daniel P. Berrangé wrote:
> > > On Mon, Apr 06, 2020 at 03:47:01PM +0200, Miguel Duarte de Mora Barroso wrote:
> > >> Hi all,
> > >>
> > >> I'm aware
2023 Feb 27
2
Checksums and other verification
https://github.com/kubevirt/containerized-data-importer/issues/1520
Hi Eric,
We had a question from the Kubevirt team related to the above issue.
The question is roughly if it's possible to calculate the checksum of
an image as an nbdkit filter and/or in the qemu block layer.
Supplemental #1: could qemu-img convert calculate a checksum as it goes
along?
Supplemental #2: could we detect
2020 Jul 14
2
Re: SELinux labels change in libvirt
On Tue, Jul 14, 2020 at 3:33 PM Daniel P. Berrangé <berrange@redhat.com>
wrote:
> On Tue, Jul 14, 2020 at 03:21:17PM +0300, Ram Lavi wrote:
> > Hello all,
> >
> > tl;dr, can you point me to the point in the libvirt repo where it's
> trying
> > to change a tap-device's SELinux label?
> >
> > I am trying to create a tap device with libvirt on
2020 Aug 30
1
Re: plug pre-created tap devices to libvirt guests
> On Tue, Jun 30, 2020 at 04:02:05PM +0100, Daniel P. Berrangé wrote:
> > On Tue, Jun 30, 2020 at 12:59:03PM +0200, Miguel Duarte de Mora Barroso wrote:
> > > On Mon, Apr 6, 2020 at 4:03 PM Laine Stump <lstump redhat com> wrote:
> > > >
> > > > On 4/6/20 9:54 AM, Daniel P. Berrangé wrote:
> > > > > On Mon, Apr 06, 2020 at 03:47:01PM
2020 Mar 26
2
Question about local migration between containers
Hello
On kubevirt project we are using IpV6 Kind cluster,
and trying to support migration,
but since both of the containers are on the same host
we get this error
{"component":"virt-launcher","level":"error","msg":"internal error: Attempt
to migrate guest to the same host
2020 Nov 04
1
consume existing tap device when libvirt / qemu run as different users
Hello,
I'm having some doubts about consuming an existing - already
configured - tap device from libvirt (with `managed='no' ` attribute
set).
In KubeVirt, we want to have the consumer side of the tap device run
without the NET_ADMIN capability, which requires the UID / GID of the
tap creator / opener to match, as per the kernel code in [0]. As such,
we create the tap device (with