[PATCH 1/2] Create an MD variant of the dummy Fedora image
by Matthew Booth
This change involves rewriting make-fedora-img.sh in perl. This allows the
flexibility to write mdadm.conf containing whichever uuids where randomly
generated when the md devices were created.
---
.gitignore | 2 +
images/Makefile.am | 18 +++-
images/guest-aux/make-fedora-img.pl | 194 +++++++++++++++++++++++++++++++++++
images/guest-aux/make-fedora-img.sh | 110 --------------------
4 files changed, 210 insertions(+), 114 deletions(-)
create mode 100755 images/guest-aux/make-fedora-img.pl
delete mode 100755 images/guest-aux/make-fedora-img.sh
13 years
[PATCH] inspection: Handle MD devices in fstab
by Matthew Booth
This patch fixes inspection when fstab contains devices md devices
specified as /dev/mdN. The appliance creates these devices without reference to
the guest's mdadm.conf so, for e.g. /dev/md0 in the guest will often be created
as /dev/md127 in the appliance. With this patch, we match the uuids of detected
md devices against uuids specified in mdadm.conf, and map them appropriately
when we encounter them in fstab.
The test in this patch also checks that devices specified by their md name, e.g.
/dev/md/boot, work correctly, although the patch isn't required for devices
specified this way.
---
regressions/Makefile.am | 1 +
regressions/test-inspect-fstab-md.sh | 65 ++++++
src/inspect.c | 22 ++-
src/inspect_fs_unix.c | 411 ++++++++++++++++++++++++++++++----
4 files changed, 456 insertions(+), 43 deletions(-)
create mode 100755 regressions/test-inspect-fstab-md.sh
13 years
Virtio-win RPM?
by Greg Scott
I should have this in my head by now...
I tried migrating a physical Windows host last night using virt-p2v CD.
It ran for 3 hours and then died. I'll get details later from the log
but as I think about it, I'll bet it died because I never installed
virtio-win in my Fedora migration server.
The documentation says do "yum install virtio-win" - but this is RHEL
documentation and my migration server is a Fedora 14 VM and yum doesn't
find it from there. Where do I grab virtio-win and how do I set it up
on that Fedora system such that virt-p2v-server will find it and use it
during a Windows P2V migration?
Thanks
- Greg Scott
13 years
[PATCH] Don't test r5t2 in mdadm test
by Matthew Booth
test-mdadm.sh was failing when mdadm-detail tried to examine r5t2, which is
missing a member. This patch simply skips testing the problematic array.
---
regressions/test-mdadm.sh | 9 ++-------
1 files changed, 2 insertions(+), 7 deletions(-)
13 years
[PATCH] Create an addition MD variant of the dummy Fedora image
by Matthew Booth
This change involves rewriting make-fedora-img.sh in perl. This allows the
flexibility to write mdadm.conf containing whichever uuids where randomly
generated when the md devices were created.
---
images/Makefile.am | 18 +++-
images/guest-aux/make-fedora-img.pl | 194 +++++++++++++++++++++++++++++++++++
images/guest-aux/make-fedora-img.sh | 110 --------------------
3 files changed, 208 insertions(+), 114 deletions(-)
create mode 100755 images/guest-aux/make-fedora-img.pl
delete mode 100755 images/guest-aux/make-fedora-img.sh
13 years
Re: [Libguestfs] Virtio-win RPM?
by Greg Scott
Update -
I built up a 64 bit F16 system and installed virtio-win-1.3.3-0.el6.noarch.rpm without hassle. However, trying to install libguestfs-winsupport-1.0-7.el6.x86_64.rpm blew up with some failed dependencies. It needs 2 packages named libgcrypt-devel and libgpg-error-devel. I can go get these, but I'm afraid these will have their own dependencies and none will get along well with Fedora.
So I think I am close - where do I find the equivalent of libguestfs-winsupport to run on a flavor of Fedora?
Also, how do I turn on that TRACE info with virt-p2v-server in case I need it? Those lines Matt said to uncomment do not exist in the copy from yum install virt-v2v.
On a RHEL6.1 system, I just tried a yum install libguestfs-winsupport. This brought in 3 dependencies and placed copies of the files my earlier P2V was looking for in /var/lib/virt-v2v/software/windows. In my Fedora conversion server, those files are nowhere to be found and there is no equivalent windows subdirectory.
So the libguestfs-winsupport stuff may be the final missing piece.
- Greg
13 years
Re: [Libguestfs] Virtio-win RPM?
by Greg Scott
I know I am adding a bazillion posts, but the more layers peeled from the onion, the more new layers I find. When we finally put it all together, I will post a step by step guide so others can get there with less trouble than me.
I found an installable RPM for virtio-win. It's in the RHN RHEL 6 Supplementary channel, so anyone with a RHEL subscription should be able to grab it. For others, I'll bet there are flavors of this floating around. The current RPM version is virtio-win-1.3.3-0.el6.noarch.rpm. This sets up the virtio-win ISO and vfd files in /usr/share/virtio-win, and it sets up a drivers subdirectory with the unpacked paravirtualized drivers for various versions of Windows.
Wonderful. But we're not out of the woods yet.
The error message below refers to programs/files we still don't have, such as firstboot.bat, rhev-apt.exe, and rhsrvany.exe. My hunch is, these are in libguestfs-winsupport-1.0-7.el6.x86_64.rpm, in the RHEL V2V Tools Server 6 RHN channel. But this package needs 64 bits and I'm running a 32 bit flavor of Fedora 14 because that's the variant needed for virt-p2v-image-builder.
Well, wonderful - Assuming my hunch is right, I can build a 64 bit F14 or F16 and install the packages I think I need, but what do folks without a RHEL subscription do? (Spend some money and buy one?) Apparently, there is no libguestfs-winsupport package for Fedora - word is, all of libguestfs is included. But if so, then where are the missing files in the error message below?
Is there a flavor of libguestfs_winsupport for Fedora I should be looking for?
- Greg
-----Original Message-----
From: libguestfs-bounces(a)redhat.com [mailto:libguestfs-bounces@redhat.com] On Behalf Of Greg Scott
Sent: Monday, November 21, 2011 7:38 PM
To: Matthew Booth; Richard W.M. Jones
Cc: Fredy Hernández; libguestfs(a)redhat.com
Subject: Re: [Libguestfs] Virtio-win RPM?
Finally some usable diagnostic info. Some of the earlier issues documented in this thread may have been network related. We redid some cabling and just tried another P2V test. Looking at /var/log/messages:
Nov 21 17:13:57 FedoraP2V virt-v2v[14428]: p2v-server started.
Nov 21 18:56:35 FedoraP2V virt-v2v[14428]: FATAL: Installation failed because the fo
llowing files referenced in the configuration file are required, but missing: /usr/s
hare/virtio-win/drivers/i386/WinXP windows/firstboot.bat windows/rhev-apt.exe window
s/rhsrvany.exe
Nov 21 18:56:35 FedoraP2V virt-v2v[14428]: p2v-server exited.
[root@FedoraP2V ~]#
The Fedora documentation says we need to do yum install virtio-win, but no such package apparently exists.
[root@FedoraP2V ~]#
[root@FedoraP2V ~]# yum install virtio-win
Loaded plugins: langpacks, presto, refresh-packagekit
Adding en_US to language list
Setting up Install Process
No package virtio-win available.
Error: Nothing to do
[root@FedoraP2V ~]#
[root@FedoraP2V ~]# rpm -qa | grep virtio
[root@FedoraP2V ~]#
I remember a version of virtio-win RPM buried on a web/ftp site somewhere a couple years ago. Where would the most recent version reside?
- Greg
_______________________________________________
Libguestfs mailing list
Libguestfs(a)redhat.com
https://www.redhat.com/mailman/listinfo/libguestfs
13 years
Re: [Libguestfs] Virtio-win RPM?
by Greg Scott
Does anyone have an idea what this error message means? This was waiting on the console this morning after running a conversion last night using the virt-p2v CD 0.8.3.1:
Inspect_os: cannot resolve Windows %SYSTEMROOT% at /usr/share/perl5/sys/VirtConvert/GuestfsHandle.pm line 187, <> line 7.
Thanks
- Greg Scott
From: Fredy Hernández [mailto:hernandez@stylmark.com]
Sent: Friday, November 18, 2011 9:12 AM
To: Greg Scott
Subject: RE: Virtio-win RPM?
Yes,
Fredy Hernández
Systems Administrator
763-574-8734 Office
hernandez(a)stylmark.com <mailto:hernandez@stylmark.com>
:
From: Greg Scott [mailto:GregScott@Infrasupport.com]
Sent: Friday, November 18, 2011 9:08 AM
To: Fredy Hernández
Subject: RE: Virtio-win RPM?
Is there a reference to a log file on that console?
From: Fredy Hernández [mailto:hernandez@stylmark.com]
Sent: Friday, November 18, 2011 9:08 AM
To: Greg Scott
Subject: RE: Virtio-win RPM?
Good morning Greg, So it died, is there something I need to do?
Fredy Hernández
Systems Administrator
763-574-8734 Office
hernandez(a)stylmark.com <mailto:hernandez@stylmark.com>
:
From: Greg Scott [mailto:GregScott@Infrasupport.com]
Sent: Friday, November 18, 2011 7:17 AM
To: libguestfs(a)redhat.com
Cc: Fredy Hernández
Subject: Virtio-win RPM?
I should have this in my head by now...
I tried migrating a physical Windows host last night using virt-p2v CD. It ran for 3 hours and then died. I'll get details later from the log but as I think about it, I'll bet it died because I never installed virtio-win in my Fedora migration server.
The documentation says do "yum install virtio-win" - but this is RHEL documentation and my migration server is a Fedora 14 VM and yum doesn't find it from there. Where do I grab virtio-win and how do I set it up on that Fedora system such that virt-p2v-server will find it and use it during a Windows P2V migration?
Thanks
- Greg Scott
13 years
Virt-resize error (ntfs) : Fatal error: exception Guestfs.Error("ntfsresize_opts: /dev/vda2)
by Morgan Cox
Hi.
(sorry I replyed in last email rather than posting to the list..)
Thanks - after issuing the commands it has correctly resized.. So it is
possible to resize (with the extra steps..)
Here is the output from the ntfsresize command:-
I have attached the complete output in a txt file
(virt-resize2.txt<https://mail.google.com/mail/?ui=2&ik=ed29735425&view=att&th=133c6f043b2c...>
*)*
Regards
----------------------------
Welcome to virt-rescue, the libguestfs rescue shell.
Note: The contents of / are the rescue appliance.
You have to mount the guest's partitions under /sysroot
before you can examine them.
bash: cannot set terminal process group (-1): Inappropriate ioctl for device
bash: no job control in this shell
groups: cannot find name for group ID 0
I have no name!@(none):/# ntfsresize /dev/vda2
ntfsresize v2011.4.12AR.4 (libntfs-3g)
Device name : /dev/vda2
NTFS volume version: 3.1
Cluster size : 4096 bytes
Current volume size: 14925427200 bytes (14926 MB)
Current device size: 32105103360 bytes (32106 MB)
New volume size : 32105099776 bytes (32106 MB)
Checking filesystem consistency ...
100.00 percent completed
Accounting clusters ...
Space in use : 7860 MB (52.7%)
Collecting resizing constraints ...
WARNING: Every sanity check passed and only the dangerous operations left.
Make sure that important data has been backed up! Power outage or computer
crash may result major data loss!
Are you sure you want to proceed (y/[n])? y
Schedule chkdsk for NTFS consistency check at Windows boot time ...
Resetting $LogFile ... (this might take a while)
Updating $BadClust file ...
Updating $Bitmap file ...
Updating Boot record ...
Syncing device ...
Successfully resized NTFS on device '/dev/vda2'.
----------------------------
13 years
