search for: msg00038

...is is as close to policy in the kernel as one can get. User land has all the information it needs to instantiate that bond/team automatically. In fact I'm trying to discuss this with NetworkManager folks and Red Hat right now: https://mail.gnome.org/archives/networkmanager-list/2017-November/msg00038.html Can we flip the argument and ask why is the kernel supposed to be responsible for this? It's not like we run DHCP out of the kernel on new interfaces...

...is is as close to policy in the kernel as one can get. User land has all the information it needs to instantiate that bond/team automatically. In fact I'm trying to discuss this with NetworkManager folks and Red Hat right now: https://mail.gnome.org/archives/networkmanager-list/2017-November/msg00038.html Can we flip the argument and ask why is the kernel supposed to be responsible for this? It's not like we run DHCP out of the kernel on new interfaces...

...epository failed to resolve or find a proper mirror. > > If those are not available are there any other locations, repositories or > proposed dates for the virt-v2* package family to become available for > centos. Please see here: https://www.redhat.com/archives/libguestfs/2015-April/msg00038.html https://www.redhat.com/archives/libguestfs/2015-April/msg00039.html Rich. -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones Read my programming and virtualization blog: http://rwmj.wordpress.com virt-p2v converts physical machines to virtual machines. Boot wi...

Hi, I am looking for the package, virt-v2v, for Redhat 7 to convert virtual machines under Xen in Redhat 5 to KVM. But, can't find it from the 7 and neither from the public websites. Why wasn’t virt-v2v included with 7 from the get-go? And, pls also advise for the downloading sites if possible. Regards, Philip Li

On Thu, Aug 06, 2015 at 05:52:57PM -0400, Chris Conn wrote: > Hello, > > I am following > https://www.redhat.com/archives/libguestfs/2015-April/msg00038.html > and have added this repo to my Centos7 server: > > [libguestfs-RHEL-7.1-preview] > name=libguestfs RHEL 7.1 preview - x86_64 > baseurl=http://people.redhat.com/~rjones/libguestfs-RHEL-7.2-preview/ > enabled=1 > gpgcheck=0 > > Is this the correct repo location as...

These are general updates to: https://www.redhat.com/archives/libguestfs/2009-October/msg00037.html [Libguestfs] [PATCH 4/5] New tool: virt-tar and: https://www.redhat.com/archives/libguestfs/2009-October/msg00038.html [Libguestfs] [PATCH 5/5] New tool: virt-ls The code uses die "prog: ...\n". The parameters to virt-tar are swapped so they always go in source -> destination order, ie: virt-tar -zx myguest /home home.tar.gz virt-tar -zu myguest uploadstuff.tar.gz /tmp and these parameters...

Hello everyone, I have recently installed libvirt 1.0.0 and am having a problem with my iSCSI storage pool's autostarting. They are just going to an inactive state right after a reboot of the host. However once the startup is complete I can manually start the pool without problem. I am getting the following errors in the libvirtd.log file but they don't really give me much as to what

...aining an > uninterrupted connection is not a policy - it's what networking is > about. > > > In fact I'm trying to discuss this with NetworkManager > > folks and Red Hat right now: > > > > https://mail.gnome.org/archives/networkmanager-list/2017-November/msg00038.html > > I thought we should do it too, for a while. > > But now, I think that the real issue is this: kernel exposes what looks > like two network devices to userspace, but in fact it is just one > backend device, just exposed by hypervisor in a weird way for > compatibili...

...aining an > uninterrupted connection is not a policy - it's what networking is > about. > > > In fact I'm trying to discuss this with NetworkManager > > folks and Red Hat right now: > > > > https://mail.gnome.org/archives/networkmanager-list/2017-November/msg00038.html > > I thought we should do it too, for a while. > > But now, I think that the real issue is this: kernel exposes what looks > like two network devices to userspace, but in fact it is just one > backend device, just exposed by hypervisor in a weird way for > compatibili...

...in the kernel as one can get. User > land has all the information it needs to instantiate that bond/team > automatically. In fact I'm trying to discuss this with NetworkManager > folks and Red Hat right now: > > https://mail.gnome.org/archives/networkmanager-list/2017-November/msg00038.html > > Can we flip the argument and ask why is the kernel supposed to be > responsible for this? It's not like we run DHCP out of the kernel > on new interfaces... Although "policy should not be in the kernel" is a a great mantra, it is not practical in the real worl...

...know SRIOV will will go away. Maintaining an uninterrupted connection is not a policy - it's what networking is about. > In fact I'm trying to discuss this with NetworkManager > folks and Red Hat right now: > > https://mail.gnome.org/archives/networkmanager-list/2017-November/msg00038.html I thought we should do it too, for a while. But now, I think that the real issue is this: kernel exposes what looks like two network devices to userspace, but in fact it is just one backend device, just exposed by hypervisor in a weird way for compatibility reasons. For example you will not...

There are significant components of the upstream 5.6 release which are stuck behind the CentOS 5.6 release process, but are now incorporated in EPEL 5 components. In particular, the "php53" package is now necessary for the "drupal6" EPEL components, due to the long out of date PHP 5.1 in the default upstream vendor's codebase. I see that some of these components are

I'm not sure which version we're up to now. Anyway I believe this addresses all the points that Eric raised in: https://www.redhat.com/archives/libguestfs/2019-March/msg00038.html https://www.redhat.com/archives/libguestfs/2019-March/msg00040.html In particular: - default state of extents_map is all allocated disk - support hole + non-zero - you can now iterate with bounds - removed the nbdkit_extents_clear function; the name is confusing and it doesn't...

Hi, I'd like to get some feedback on a proposal to enhance virtio-net to ease configuration of a VM and that would enable live migration of passthrough network SR-IOV devices. Today we have SR-IOV network devices (VFs) that can be passed into a VM in order to enable high performance networking direct within the VM. The problem I am trying to address is that this configuration is generally

Hi, I'd like to get some feedback on a proposal to enhance virtio-net to ease configuration of a VM and that would enable live migration of passthrough network SR-IOV devices. Today we have SR-IOV network devices (VFs) that can be passed into a VM in order to enable high performance networking direct within the VM. The problem I am trying to address is that this configuration is generally

Previously posted: https://www.redhat.com/archives/libguestfs/2015-December/msg00038.html Inspection now really succeeds on a small number of simple guests. To test it out: $ ./run guestfish -v -x -a /tmp/centos-6.img ><fs> run ><fs> debug sh "guestfs-inspection --verbose" Rich.

For background on this change, see: https://rwmj.wordpress.com/2015/12/06/inspection-now-with-added-prolog/ v2 was previously posted here: https://www.redhat.com/archives/libguestfs/2015-December/msg00038.html To test this patch series on a real guest, you can do: $ ./run guestfish -v -x -a /var/tmp/centos-6.img ><fs> run ><fs> debug sh "guestfs-inspection --verbose" v2 -> v3: - Rebase on top of upstream libguestfs. - Allow prologue and epilogue C code....