similar to: Some more Virt-P2V CD results

I should post this here - I am trying to do a P2V migration for a Windows server and I want to use virt-p2v and virt-v2v. But I obviously don't know what I'm doing. The goal is to have this physical Windows server come alive as a RHEL libvirt guest virtual machine. I built a Virt-p2v-image-builder CD and successfully booted a source Windows server from the CD. It prompts me for a

Hello, I upgraded my kvm server from Fedora 14 to Fedora 16 and the only casualty was a Windows 2003 Server client that will no longer boot with and produces a BSOD. I admittedly know very little about Windows and this VM has been around - real hardware -> Parallels on a Mac -> linux kvm but it was working fine under Fedora 14. The client does boot fine under safe mode but anything higher

These are the current steps we followed to set up and run Windows P2V migrations. Note that development is proceeding rapidly and the versions of all pieces below will likely be obsolete soon. ************************************************************* Windows RHEV P2V Cookbook 2011-1122 1. Install 32 bit Fedora 14 as a virtual machine or physical host. You will use this system to build

I need to p2v migrate a Windows server and I am soooo confused! By now, I've done a few virt-v2v migrations, so I get how that works. I attended Richard and Matthew's Red Hat Summit talk about virt-p2v and just now downloaded the handouts. If I understand what's going on, virt-p2v is pretty much the same as virt-v2v, except that the physical system to migrate from needs to boot

I'm trying to impute data using the mi package, but after running through almost the entire first round of imputations (which takes quite a while), it throws this error (I'll include the whole output prior to the error for context). Does anyone know what is causing it, or how I can fix it? More specifically, how can I tell what is throwing the error so I know what to fix? Is

Hi, I installed F14 on release, but was diquieted to note that my symlinked GotoBLAS (http://cran.r-project.org/doc/manuals/R-admin.html#Shared-BLAS, foot of paragraph) prevented R (compiled from source, no special configure options) from loading - everything had been fine on F < 14. It seems that: cat /selinux/booleans/allow_execstack is 1 1 on my RHEL systems, but became (?) 0 0 in F14.

(oops accidentally sent to -owners) Hi, i'm trying to start a LXC guest on a F14 computer .. followed the examples in http://libvirt.org/drvlxc.html, but got stuck when starting it .. 03:07:23.706: debug : virCgroupNew:542 : New group / 03:07:23.707: debug : lxcControllerRun:563 : Setting up private /dev/pts 03:07:23.711: debug : lxcControllerRun:589 : Mouting 'devpts' on

On Fri, Sep 02, 2011 at 02:06:57AM -0500, Greg Scott wrote: > "This kernel requires an X86-64 CPU, but only detected an i686 CPU. > Unable to boot - please use a kernel appropriate for your CPU." That's strange because virt-p2v-image-builder is supposed to only build 32 bit images ... Please keep the replies on the list. Rich. -- Richard Jones, Virtualization Group, Red

I just now ran into some traceback messages and other errors running virt-p2v-image-builder 0.8.5.1. Anything to worry about? . . . Installing: passwd ##################### [305/307] Installing: syslinux ##################### [306/307] Installing: vim-minimal ##################### [307/307] Note: Forwarding request to

On my CentOS 6.3 machine, in /etc/idmapd.conf I've updated the "[Mapping]" section of the config file: Nobody-User = paulbsch Nobody-Group = paulbsch But the mapping is not working. Files still show up as being owned by "nobody". On my Fedora 14 machine, with the exact same changes to /etc/idmapd.conf, the mapping works perfectly and the files show up as being owned by

On Fri, 2015-03-06 at 21:59 +0000, Rowland Penny wrote: > try adding 'map to guest = Bad User' to smb.conf > > Rowland > IT WORKED!!! THANK YOU. Now the XP machine can see both the f14 and f20 shares. (It was not even necessary to restart nmbd or smbd on the f20 machines.) Now, if I'm not asking for too much, can you please explain why this worked. :-) Many thanks

Marc, et al, Thanks for your reply. Sorry, I didn't mean to be confusing. Summary of problem: 1) XP sees samba shares on fedora14/samba3 machine, but not on fedora20/samba4 machines. 2) all fedora machines see all shares including on XP machine. 3) clicking on f20 machine from XP tries to log in rather than showing the shares. Login is not successful. 4) all machines can ping each

Dear all, I'm using R function "glmmPQL" in "MASS" package for generalized linear mixed model considering the temporal correlations in random effect. There are 1825 observations in my data, in which the random effect is called "Date", and there are five levels in "Date", each repeats 365 times. When I tried

On Thursday 26 May 2016 16:40:16 Richard W.M. Jones wrote: > A convenience method instead of having to work out the right > qemu command line each time. > --- > .gitignore | 1 + > p2v/Makefile.am | 28 ++++++++++++++++++++++++++++ > 2 files changed, 29 insertions(+) > > diff --git a/.gitignore b/.gitignore > index 285b28d..8509a9d 100644 > --- a/.gitignore

virt-p2v-make-kiwi now forces the launch-virt-p2v mode to 0755 to ensure the executable bit it set for user. --- p2v/virt-p2v-make-kiwi.in | 1 + 1 file changed, 1 insertion(+) diff --git a/p2v/virt-p2v-make-kiwi.in b/p2v/virt-p2v-make-kiwi.in index e493bd4..3506e9b 100644 --- a/p2v/virt-p2v-make-kiwi.in +++ b/p2v/virt-p2v-make-kiwi.in @@ -190,6 +190,7 @@ cp $datadir/issue $output/root/etc/issue

Hi, this small series fixes the generation of Debian-based images using virt-p2v-make-disk. With this series, the image can boot fine, X is started, and the p2v interface appears. I haven't tried an actual conversion, but I don't think there are Debian-specific problems preventing that. Thanks, Pino Toscano (4): p2v: fix Gtk dependencies on Debian p2v: remove

It relied on the qemu libguestfs was configured with, which is no more available now. Since we already require libguestfs tools for some functional tests, make run-virt-p2v-in-a-vm depend on libguestfs too, and use the qemu configured in libguestfs. --- Makefile.am | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/Makefile.am b/Makefile.am index d27219d..d1b4bee 100644 ---

Set p2v.local as hostname for the p2v disk image, so it will be fixed, instead of whatever is set in the used templates. This is also somewhat important during the distribution update, and installation of our packages: there may be distribution packages actually using the hostname to initialize stuff (e.g. configuration values), and thus the unset value "(none)" triggers errors. The

Memory leak found by valgrind. --- p2v/main.c | 1 + 1 file changed, 1 insertion(+) diff --git a/p2v/main.c b/p2v/main.c index e1a7550..7f1e1c0 100644 --- a/p2v/main.c +++ b/p2v/main.c @@ -260,6 +260,7 @@ main (int argc, char *argv[]) } guestfs_int_free_string_list (cmdline); + free_config (config); exit (EXIT_SUCCESS); } -- 2.10.2

From: Alban Lecorps <alban.lecorps at ubisoft.com> The "-oo" option will be useful primarily for the openstack output mode (currently disabled, from commit b74c126629e3, "Ignore 'openstack' driver", 2020-03-16). Use a ConfigStringList knob for "-oo", and for each OPTION=VALUE element in that list, create a separate "-oo OPTION=VALUE" option.