similar to: Question about local migration between containers

Displaying 20 results from an estimated 600 matches similar to: "Question about local migration between containers"

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
2020 Mar 26
0
Re: Question about local migration between containers
On Thu, Mar 26, 2020 at 04:47:50PM +0200, Or Shoval wrote: > 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
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
0
Re: Question about local migration between containers
On Thu, Mar 26, 2020 at 05:25:59PM +0200, Or Shoval wrote: > 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 > This machine-id
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
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 Sep 22
2
consuming pre-created tap - with multiqueue
Hello, On KubeVirt, we are trying to pre-create a tap device, then instruct libvirt to consume it (via the type=ethernet , managed='no' attributes). It works as expected, **unless** when we create a multi-queue tap device. The difference when creating the tap device is that we set the multi-queue flag; libvirt throws the following error when consuming it: ``` LibvirtError(Code=38,
2019 Nov 21
2
Getting "Unable to set XATTR" on libvirt 5.6.0 inside containers
Hi, We are updating KubeVirt to libvirt 5.6.0. Before that we were running on 5.0.0. It seems like something regarding setting xattrs on files has changed, because with libvirt 5.6.0 we are getting the following error: ``` Unable to set XATTR trusted.libvirt.security.dac on /var/lib/libvirt/qemu/domain-410-default_vmi-fedora: Operation not permitted') ``` The main problem is for us is that
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 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 Sep 23
1
Re: consuming pre-created tap - with multiqueue
On Wed, Sep 23, 2020 at 05:44:28PM +0100, Daniel P. Berrangé wrote: > On Tue, Sep 22, 2020 at 01:48:08PM +0200, Miguel Duarte de Mora Barroso wrote: > > Hello, > > > > On KubeVirt, we are trying to pre-create a tap device, then instruct > > libvirt to consume it (via the type=ethernet , managed='no' > > attributes). > > > > It works as
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
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 >
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 Apr 06
2
plug pre-created tap devices to libvirt guests
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 pre-created tap devices into libvirt guests - that would be a requirement to allow kubevirt to run with less capabilities in the pods that encapsulate the VMs. I took a look at the libvirt code
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 Nov 17
1
Openshift Kubevirt lab?
Is there an RHPDS lab for Kubevirt? -- Luis Gonzalez Consultant, Container Infrastructure Red Hat <https://www.redhat.com/> lgonzal@redhat.com M: 404.784.7166 IM: luisgonzalez GPG: 2800156E8386EA133D4F10AC3381C1457F69FF84 <https://www.redhat.com/>
2013 Apr 09
2
fail to convert qemu xml to args with libvirt-1.0.4: An error occurred, but the cause is unknown
Hi, I used to convert qemu XML to args with libvirt-1.0.3. But it failed to convert with libvirt-1.0.4. # virsh domxml-to-native qemu-argv test.xml >test.sh error: An error occurred, but the cause is unknown Comparing the debug file as below: 1) lbvirt-1.0.3 <cut> 2013-04-09 03:23:47.296+0000: 2669: debug : virEventPollInterruptLocked:716 : Interrupting 2013-04-09 03:23:47.296+0000:
2019 Aug 22
2
Re: RLIMIT_MEMLOCK in container environment
On Thu, Aug 22, 2019 at 2:24 AM Daniel P. Berrangé <berrange@redhat.com> wrote: > > On Wed, Aug 21, 2019 at 01:37:21PM -0700, Ihar Hrachyshka wrote: > > 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