search for: xen_guest

...o-local.pod b/v2v/virt-v2v-copy-to-local.pod index e06391757..4703aee2f 100644 --- a/v2v/virt-v2v-copy-to-local.pod +++ b/v2v/virt-v2v-copy-to-local.pod @@ -8,8 +8,6 @@ virt-v2v-copy-to-local - Copy a remote guest to the local machine virt-v2v-copy-to-local -ic xen+ssh://root at xen.example.com xen_guest - virt-v2v-copy-to-local -ic esx://root at esxi.example.com vmware_guest - =head1 DESCRIPTION C<virt-v2v-copy-to-local> copies a guest from a remote hypervisor to @@ -35,17 +33,6 @@ convert such guests directly. See L<virt-v2v(1)/XEN OR SSH CONVERSIONS FROM BLOCK DEVICES>. -=...

It turns out that RHEL 5 Xen conversions don't work if the source disk is located on a block device. See patch 1/4 for the gory details. This patch series proposes a new tool called virt-v2v-copy-to-local which essentially is a way to make new virt-v2v work like the old virt-v2v, ie. copy first, convert after. Of course this is very slow and would only be used as a last resort, but I

Folks, Regarding the Virtualization BoF, Ted Tso clarified that the remaining BoF sessons would just be scheduled on paper at OLS. We only need to use a scheduled BoF slot if we want to use a room there, I guess, else we can schedule at any free time and use a corridor or pub. Available BoF slots are only Friday evening, note. Since I don't believe the Xen team is available Friday evening,

Hi Rusty, I had a look over your 011-paravirt-head.S.patch. I'm struggling to come up with a list of any benefits over having separate entrypoints for each hypervisor. Multiple entry pros: * allows maximum startup flexibility for any given hypervisor * for Xen at least, it's pretty simple * the "what hypervisor am I under" question is answered trivially cons:

Last year we had a discussion[1] about how the hypercall ABI unfortunately contains fields that change width between 32- and 64-bit builds. This is a huge problem as we come up on the python management stack for ppc64, since the distributions ship 32-bit python. A 32-bit python/libxc cannot currently manage a 64-bit hypervisor. I had a patch but was unable to test it, and some other things were

Previously posted: https://www.redhat.com/archives/libguestfs/2018-November/msg00000.html https://www.redhat.com/archives/libguestfs/2018-November/msg00001.html This completes the split and rewrite of the virt-v2v manual to make it much simpler to understand and digest. Rich.

Hello, When I install guest OS on xen using "xm create /path/of/file/ubuntu.cfg -c" , I am getting an error message *"Error*: Device 0 (*vif*) could not be connected. Hotplug scripts not working <http://markmail.org/message/24aj3qs6ddrtwdks>" . I also saw that hotplugs and udev are prerequisites to be installed before compiling xen. I could not find hotplugs in Yast.

Hello, When I install guest OS on xen using "xm create /path/of/file/ubuntu.cfg -c" , I am getting an error message *"Error*: Device 0 (*vif*) could not be connected. Hotplug scripts not working <http://markmail.org/message/24aj3qs6ddrtwdks>" . I also saw that hotplugs and udev are prerequisites to be installed before compiling xen. I could not find hotplugs in Yast.

...se too much overhead. Each single diff --git a/arch/x86/platform/pvh/enlighten.c b/arch/x86/platform/pvh/enlighten.c index c0a502f7e3a7..15a74dbc9b00 100644 --- a/arch/x86/platform/pvh/enlighten.c +++ b/arch/x86/platform/pvh/enlighten.c @@ -86,7 +86,7 @@ static void __init init_pvh_bootparams(bool xen_guest) } /* - * See Documentation/x86/boot.rst. + * See Documentation/arch/x86/boot.rst. * * Version 2.12 supports Xen entry point but we will use default x86/PC * environment (i.e. hardware_subarch 0). diff --git a/drivers/vhost/vhost.c b/drivers/vhost/vhost.c index ff8892c38666..f5c186...

...se too much overhead. Each single diff --git a/arch/x86/platform/pvh/enlighten.c b/arch/x86/platform/pvh/enlighten.c index 1861a2ba0f2b..c0a502f7e3a7 100644 --- a/arch/x86/platform/pvh/enlighten.c +++ b/arch/x86/platform/pvh/enlighten.c @@ -86,7 +86,7 @@ static void __init init_pvh_bootparams(bool xen_guest) } /* - * See Documentation/x86/boot.txt. + * See Documentation/x86/boot.rst. * * Version 2.12 supports Xen entry point but we will use default x86/PC * environment (i.e. hardware_subarch 0). diff --git a/drivers/acpi/Kconfig b/drivers/acpi/Kconfig index 283ee94224c6..2438f37f2ca1...

...se too much overhead. Each single diff --git a/arch/x86/platform/pvh/enlighten.c b/arch/x86/platform/pvh/enlighten.c index 1861a2ba0f2b..c0a502f7e3a7 100644 --- a/arch/x86/platform/pvh/enlighten.c +++ b/arch/x86/platform/pvh/enlighten.c @@ -86,7 +86,7 @@ static void __init init_pvh_bootparams(bool xen_guest) } /* - * See Documentation/x86/boot.txt. + * See Documentation/x86/boot.rst. * * Version 2.12 supports Xen entry point but we will use default x86/PC * environment (i.e. hardware_subarch 0). diff --git a/drivers/acpi/Kconfig b/drivers/acpi/Kconfig index 283ee94224c6..2438f37f2ca1...

...ch single > diff --git a/arch/x86/platform/pvh/enlighten.c > b/arch/x86/platform/pvh/enlighten.c index 1861a2ba0f2b..c0a502f7e3a7 100644 > --- a/arch/x86/platform/pvh/enlighten.c > +++ b/arch/x86/platform/pvh/enlighten.c > @@ -86,7 +86,7 @@ static void __init init_pvh_bootparams(bool xen_guest) > } > > /* > - * See Documentation/x86/boot.txt. > + * See Documentation/x86/boot.rst. > * > * Version 2.12 supports Xen entry point but we will use default x86/PC > * environment (i.e. hardware_subarch 0). > diff --git a/drivers/acpi/Kconfig b/drivers/a...

...ch single > diff --git a/arch/x86/platform/pvh/enlighten.c > b/arch/x86/platform/pvh/enlighten.c index 1861a2ba0f2b..c0a502f7e3a7 100644 > --- a/arch/x86/platform/pvh/enlighten.c > +++ b/arch/x86/platform/pvh/enlighten.c > @@ -86,7 +86,7 @@ static void __init init_pvh_bootparams(bool xen_guest) > } > > /* > - * See Documentation/x86/boot.txt. > + * See Documentation/x86/boot.rst. > * > * Version 2.12 supports Xen entry point but we will use default x86/PC > * environment (i.e. hardware_subarch 0). > diff --git a/drivers/acpi/Kconfig b/drivers/a...

...se too much overhead. Each single diff --git a/arch/x86/platform/pvh/enlighten.c b/arch/x86/platform/pvh/enlighten.c index 1861a2ba0f2b..c0a502f7e3a7 100644 --- a/arch/x86/platform/pvh/enlighten.c +++ b/arch/x86/platform/pvh/enlighten.c @@ -86,7 +86,7 @@ static void __init init_pvh_bootparams(bool xen_guest) } /* - * See Documentation/x86/boot.txt. + * See Documentation/x86/boot.rst. * * Version 2.12 supports Xen entry point but we will use default x86/PC * environment (i.e. hardware_subarch 0). diff --git a/drivers/acpi/Kconfig b/drivers/acpi/Kconfig index 283ee94224c6..2438f37f2ca1...

...se too much overhead. Each single diff --git a/arch/x86/platform/pvh/enlighten.c b/arch/x86/platform/pvh/enlighten.c index 1861a2ba0f2b..c0a502f7e3a7 100644 --- a/arch/x86/platform/pvh/enlighten.c +++ b/arch/x86/platform/pvh/enlighten.c @@ -86,7 +86,7 @@ static void __init init_pvh_bootparams(bool xen_guest) } /* - * See Documentation/x86/boot.txt. + * See Documentation/x86/boot.rst. * * Version 2.12 supports Xen entry point but we will use default x86/PC * environment (i.e. hardware_subarch 0). diff --git a/drivers/acpi/Kconfig b/drivers/acpi/Kconfig index 283ee94224c6..2438f37f2ca1...

...--git a/arch/x86/platform/pvh/enlighten.c > > b/arch/x86/platform/pvh/enlighten.c index 1861a2ba0f2b..c0a502f7e3a7 100644 > > --- a/arch/x86/platform/pvh/enlighten.c > > +++ b/arch/x86/platform/pvh/enlighten.c > > @@ -86,7 +86,7 @@ static void __init init_pvh_bootparams(bool xen_guest) > > } > > > > /* > > - * See Documentation/x86/boot.txt. > > + * See Documentation/x86/boot.rst. > > * > > * Version 2.12 supports Xen entry point but we will use default > x86/PC > > * environment (i.e. hardware_subarch 0). >...

This patch is incomplete, but early feedback would be welcome. Rich.

Fix several warnings and broken links. This series was generated against linux-next, but was rebased to be applied at docs-next. It should apply cleanly on either tree. There's a git tree with all of them applied on the top of docs/docs-next at: https://git.linuxtv.org/mchehab/experimental.git/log/?h=fix_doc_links_v2 Mauro Carvalho Chehab (21): ABI: sysfs-devices-system-cpu: point to