How recreate cdrom?
by John W. Himpel
Good evening,
I am using the latest version of software from Rawhide and Justin's yum
repo.
Using virt-manager, I inadvertently removed the cdrom from the VM
configuration. Unfortunately, I can't figure out how to add a cdrom
back. Any hints would be greatly appreciated.
13 years, 3 months
Lorax F15 composes - buildinstall rewrite
by James Laska
Sent on behalf of mgracik(a)redhat.com (not subscribed to virt@).
-------- Forwarded Message --------
> From: Martin Gracik <mgracik(a)redhat.com>
> Reply-to: mgracik(a)redhat.com
> To: virt(a)lists.fedoraproject.org
> Cc: James Laska <jlaska(a)redhat.com>
> Subject: [Fwd: Re: Lorax F15 composes - buildinstall rewrite]
> Date: Tue, 11 Jan 2011 13:05:23 +0100
>
> Hello,
>
> I'm working on the buildinstall scripts rewrite, called lorax, and I
> have one issue. The buildinstall scripts generate the .treeinfo file,
> which is used by python-virtinst, and that it looks for the [images-xen]
> section.
>
> What I'd like to do in lorax, is that the section name will depend on
> the kernel name. If the kernel is a PAE kernel, it's filename will be
> kernel-PAE and initrd filename will be initrd-PAE.img (this is the same
> in buildinstall), but the section would be [images-PAE] as opposed to
> buildinstall's [images-xen].
>
> And if a XEN kernel is installed, the filename will be vmlinuz-XEN
> (initrd-XEN.img) and corresponding section will be [images-XEN].
>
> Will this change cause you any difficulties?
>
> --
> Martin Gracik <mgracik(a)redhat.com>
> email message attachment, "Forwarded message - Re: Lorax F15 composes
> - buildinstall rewrite"
> > -------- Forwarded Message --------
> > From: James Laska <jlaska(a)redhat.com>
> > To: Martin Gracik <mgracik(a)redhat.com>
> > Cc: Jesse Keating <jkeating(a)redhat.com>, Adam Williamson
> > <awilliam(a)redhat.com>, Dennis Gilmore <dgilmore(a)redhat.com>,
> > Christopher Lumens <clumens(a)redhat.com>, David Cantrell
> > <dcantrel(a)redhat.com>
> > Subject: Re: Lorax F15 composes - buildinstall rewrite
> > Date: Mon, 10 Jan 2011 08:58:20 -0500
> >
> > On Mon, 2011-01-10 at 08:51 -0500, Martin Gracik wrote:
> > >
> > > --
> > >
> > > Martin Gracik
> > >
> > > ----- Original Message -----
> > > > On Sun, Jan 09, 2011 at 06:53:38AM -0500, Martin Gracik wrote:
> > > > > ----- Original Message -----
> > > > > > On Tue, 2011-01-04 at 16:24 -0500, Martin Gracik wrote:
> > > > > > >
> > > > > > > --
> > > > > > >
> > > > > > > Martin Gracik
> > > > > > >
> > > > > > > ----- Original Message -----
> > > > > > > > Hi Martin,
> > > > > > > >
> > > > > > > > Thanks for reaching out on the topic. Exciting to see the
> > > > > > > > lorax
> > > > > > > > work
> > > > > > > > coming into Fedora.
> > > > > > > >
> > > > > > > > On Tue, 2011-01-04 at 14:29 -0500, Martin Gracik wrote:
> > > > > > > > > Hello,
> > > > > > > > >
> > > > > > > > > I'm working on the Lorax project, which is a rewrite of
> > > > > > > > > anaconda's
> > > > > > > > > buildinstall scripts. It is now in a state ready for
> > > > > > > > > thorough
> > > > > > > > > testing.
> > > > > > > > > The lorax package was already added to fedora and the build
> > > > > > > > > is
> > > > > > > > > in
> > > > > > > > > koji. I have a patch for pungi, and from the tests I did
> > > > > > > > > myself,
> > > > > > > > > I'm
> > > > > > > > > able to create the install images using patched pungi +
> > > > > > > > > lorax,
> > > > > > > > > and
> > > > > > > > > do
> > > > > > > > > a successful install with them. I would like lorax to be
> > > > > > > > > used
> > > > > > > > > for
> > > > > > > > > F15
> > > > > > > > > composes if it will be possible.
> > > > > > > > >
> > > > > > > > > Lorax as of now only supports i386 and x86_64 architectures,
> > > > > > > > > so
> > > > > > > > > there's a problem with all the secondary archs. I don't know
> > > > > > > > > which
> > > > > > > > > solution would be better, if the secondary archs should use
> > > > > > > > > unpatched
> > > > > > > > > pungi, which will still be running buildinstall, or if the
> > > > > > > > > patched
> > > > > > > > > pungi should run lorax only if the buildarch is supported,
> > > > > > > > > otherwise
> > > > > > > > > run buildinstall.
> > > > > > > > >
> > > > > > > > > After we'll have the patched pungi build, we can get the
> > > > > > > > > lorax
> > > > > > > > > enabled
> > > > > > > > > composes to QA and get more testing.
> > > > > > > > >
> > > > > > > > > I would like to hear your thoughts and comments, if this
> > > > > > > > > stuff
> > > > > > > > > is
> > > > > > > > > your
> > > > > > > > > concern.
> > > > > > > >
> > > > > > > > Has lorax been used to generate and compare F-14 install
> > > > > > > > images?
> > > > > > > > If
> > > > > > > > possible, I think comparing the resulting images might be
> > > > > > > > interesting.
> > > > > > > >
> > > > > > > > Clumens & I just finished up a new autoqa test that runs pungi
> > > > > > > > whenever
> > > > > > > > a new anaconda koji build is available. The test runs pungi
> > > > > > > > inside
> > > > > > > > a
> > > > > > > > mock chroot and is intended to capture potential compose
> > > > > > > > issues
> > > > > > > > ahead
> > > > > > > > of
> > > > > > > > time. Would any changes be needed for this test? Do we want to
> > > > > > > > run
> > > > > > > > both lorax and buildinstall versions of pungi at the same
> > > > > > > > time?
> > > > > > >
> > > > > > > We're doing rawhide composes with buildinstall and lorax every
> > > > > > > day,
> > > > > > > and doing diffs between the initrds. I'm trying to get the lorax
> > > > > > > composes as close as possible to the buildinstall ones. I don't
> > > > > > > know
> > > > > > > if you can access this server, but they are here
> > > > > > > http://10.34.39.2/trees/lorax/ and
> > > > > > > http://10.34.39.2/trees/rawhide/
> > > > > >
> > > > > > Ah perfect, thanks for the links.
> > > > > >
> > > > > > > The diffs are in the lorax directories. I know the format is
> > > > > > > strange, I didn't give a lot of thought to the formatting. It
> > > > > > > basically has 3 parts:
> > > > > > >
> > > > > > > 1. missing files from the lorax compose, that are in
> > > > > > > buildinstall
> > > > > > > 2. diff of text files that are in both composes
> > > > > > > 3. files that are in lorax compose, and NOT in the buildinstall
> > > > > > > (leftovers), sorted by size and package they belong to (I used
> > > > > > > this
> > > > > > > part to remove leftover files, so the image is smaller, the ones
> > > > > > > that are left now don't take much space, so I'm getting to the
> > > > > > > part,
> > > > > > > that removing them is not very effective for the maintainability
> > > > > > > of
> > > > > > > code, so they are still left there)
> > > > > >
> > > > > > Careful with some of the tree metadata that several tools rely on
> > > > > > (virt-install, cobbler/koan to some degree, snake, beaker ...).
> > > > > >
> > > > > > * lorax - http://10.34.39.2/trees/lorax/20110105/i386/os/.treeinfo
> > > > > > * buildinstall -
> > > > > > http://10.34.39.2/trees/rawhide/20110105/i386/os/.treeinfo
> > > > > >
> > > > > > Two issues jump out from comparing the two ...
> > > > > > 1. The [images-*] sections appear to be missing from the lorax
> > > > > > generated .treeinfo
> > > > > > 2. Also, possibly related, the [general] boot.iso option should be
> > > > > > moved to [images-$arch] boot.iso
> > > > >
> > > > > Yes, thanks for catching this, it must have slipped somehow,
> > > > > should be fixed now.
> > > >
> > > > Looking good. One more comment, the lorax generated treeinfo includes
> > > > a
> > > > section [images-PAE], while the rawhide treeinfo used [images-xen].
> > > > Should
> > > > they match, or do we need to inform consumers that the xen images can
> > > > be found
> > > > under [images-PAE]? Now that I think of it, is xen-guest support in
> > > > the
> > > > regular [images-$basearch] anyway?
> > >
> > > Yeah well, what I did in lorax is that, I take the images-<suffix> from the actual kernel name.
> > > If the kernel name ends with PAE, we rename it to vmlinuz-PAE, and corresponding initrd to initrd-PAE,
> > > so I put it to images-PAE. If the kernel would end with XEN, it would be all XEN instead of PAE.
> > > This looks more elegant to me, but I can change it easily to images-xen if it's a problem.
> >
> > Looking at the source code of python-virtinst, it does rely on the
> > presence of [images-xen]. I'd recommend reaching out to
> > virt(a)lists.fedoraproject.org to let them know of the change.
> >
> > Thanks,
> > James
13 years, 3 months
KVM high available
by iarly selbir
Hi there,
Hi I'm joining today an would like to share my knowledge with virtualization
and get more = )
I'm setting up two kvm hosts to work together in cluster using RHCS, but I'm
looking for a solution how to configure it to failover guests in case of any
host fail, for example, assuming that I have two nodes...
KVM-HOST-001
guest1
guest2
guest3
KVM-HOST-002
guest4
guest5
guest6
when KVM-HOST-001 fail, the KVM-HOST-002 take over all machines from other
host, I'm sharing a storage volume between two nodes (gfs2), so all hosts
can see the guest images, but how to configure the clusters resources to
migrate the guests? this is my question and any suggestions will be
appreciated.
Thanks in advance.
- -
iarlyy selbir
:wq!
13 years, 3 months
Status of Snapshots
by Jorge Fábregas
Hi again,
I noticed no "snapshot" functionality in virt-manager :( What I found
while doing a search is that it is planned but couldn't find anything
recent. What's the current status on snapshots? Any plans to include it
with virt-manager for F15? F16?
Also, is it to shut down the VM, and just copy the *.img files
somewhere else the closest thing we have now ? or place the *.img files
on a logical-volume and then perform the snapshot there (LVM wise)?
Thanks,
Jorge
13 years, 3 months
libvirt & VirtualBox (get some experience)
by Jorge Fábregas
Hello everyone,
I'm on Fedora 14 and I'm totally new to libvirt. I have experience with
vSphere on servers and VirtualBox on the desktop. I'm looking forward
to KVM but my desktop CPU doesn't have the virtualization extensions so
I can't play with KVM at the moment.
However, I would like to get some hands-on experience with the
management tools (command line virsh and the GUI virt-manager).
Can I really use these mgmt tools with VirtualBox as the back-end
virtualization engine? That is, can I totally control my VirtualBox VMs
(with libvirt) without needing to use the VirtualBox GUI at all?
Thanks,
Jorge
13 years, 3 months
bug 579348 when are we going to see it fixed for Fedora 13?
by KC8LDO
As far as I can see this issue is being ignored. See the link below.
http://www.mail-archive.com/package-announce@lists.fedoraproject.org/msg1...
Apparently this has been fixed since last October and the person this has
been assigned to did the package update for Fedora-14.
https://bugzilla.redhat.com/show_bug.cgi?format=multiple&id=579348
Cole Robinson said it should be fixed for Fedora-13. See comment 45. The
current packages date from August 2010 so they definitely have not been
updated.
http://download.fedora.redhat.com/pub/fedora/linux/updates/13/x86_64/
qemu-0.12.5-1.fc13.x86_64.rpm12-Aug-2010 11:04 23K
qemu-common-0.12.5-1.fc13.x86_64.rpm12-Aug-2010 11:04 242K
qemu-img-0.12.5-1.fc13.x86_64.rpm12-Aug-2010 11:04 146K
qemu-kvm-0.12.5-1.fc13.x86_64.rpm12-Aug-2010 11:04 22K
qemu-kvm-tools-0.12.5-1.fc13.x86_64.rpm12-Aug-2010 11:04 33K
qemu-system-arm-0.12.5-1.fc13.x86_64.rpm12-Aug-2010 11:04 880K
qemu-system-cris-0.12.5-1.fc13.x86_64.rpm12-Aug-2010 11:04 560K
qemu-system-m68k-0.12.5-1.fc13.x86_64.rpm12-Aug-2010 11:04 601K
qemu-system-mips-0.12.5-1.fc13.x86_64.rpm12-Aug-2010 11:04 2.9M
qemu-system-ppc-0.12.5-1.fc13.x86_64.rpm12-Aug-2010 11:04 2.6M
qemu-system-sh4-0.12.5-1.fc13.x86_64.rpm12-Aug-2010 11:04 1.1M
qemu-system-sparc-0.12.5-1.fc13.x86_64.rpm12-Aug-2010 11:04 623K
qemu-system-x86-0.12.5-1.fc13.x86_64.rpm12-Aug-2010 11:04 2.3M
qemu-user-0.12.5-1.fc13.x86_64.rpm12-Aug-2010 11:04 4.0M
13 years, 3 months
