Re: [fedora-virt] Routing to guests
by Robert Thiem
> From: Philip Rhoades
> I can ssh from/to the host/guest OK but how do I set up a route (or
> whatever is necessary) so that another machine:
> eth0: 192.168.0.12
> can ssh to the guest? - "ssh 192.168.122.68" gives "no route to host" -
> http://docs.fedoraproject.org/virtualization-guide/f12/en-US/html/ but
> the problem does not seem to be covered there.
Alexander is correct in saying that bridging would allow you to do that.
There are two networking discussed in the guide.
The first is a NAT (network address translation), in which the guests are
given "private" ip addresses and any outbound traffic appears to be coming
from the host machine's IP address. This is the same as the setup on your
ADSL router where the internal network machines get addresses of
192.168.x.x but the internet sees your requests as coming from the IP
address of your router.
There should be lots of documentation in linux firewalling guides under
sections on NAT (or possibly called IP Masquerading in some). Have a look
at these for information on port forwarding to reveal services
inside the virtual (such as ssh).
The other option is bridging. This shares the physical network interface
of the host with the guest. In this case the VM acts as though it's a
machine plugged into the same subnet as the host, its services are
accessible like those of the host and it's as vulnerable to attack as the
host.
Robert
11 years, 4 months
porting a disk from lvm to file
by Gianluca Cecchi
Hello,
I have a virtio disk for a vm that consists of an lvm.
I would like to port this vm disk to another virtualization host that has vm
disks on file, instead.
Can I port this lvm vm-disk to file, for example with something like:
dd if=/dev/vgname/lvname of=/directory_tree/filename
and then copy "filename" to the other host and use it as a backing storage
for a vm on it?
Do I have perhaps to consider some heading for lvm metadata and skip
anything form the dd command?
Anyone already done/considered?
Thanks,
Gianluca
12 years, 9 months
Suddenly KVM/virt-manager is failing on qcow2 images
by Richard Chan
Hi, today all my KVMs based on qcow2 images have failed with "not a bootable
hard disk" message.
I am running F13 x64 fully yum updated on AMD Phenom II X4.
All these VMs were working fine (linux,freebsd,winxp).
When I booted a VM from an ISO image and looked at the /dev/vda - there was
a "corrupt" partition table.
When I converted the qcow2 image to raw, and looked at the partition table,
it was fine.
When I switched the VM to use the raw image, it booted and ran fine.
Any known issues with recent KVM/qcow2 interfaction?
Packages:
kernel-2.6.33.6-147.fc13.x86_64
gpxe-roms-qemu-1.0.0-1.fc13.noarch
qemu-common-0.12.3-8.fc13.x86_64
qemu-img-0.12.3-8.fc13.x86_64
qemu-system-x86-0.12.3-8.fc13.x86_64
qemu-kvm-0.12.3-8.fc13.x86_64
Help!? Tks.
12 years, 10 months
Re: [fedora-virt] Fedora Virt Status
by Scott Dowdle
Greetings,
----- Original Message -----
> > I'm wondering if there will be a test repo for Fedora 13 because it
> > would be nice to get SPICE going in Fedora 13 too!
>
> Actually there is one, which works quite well for me with F13 :
>
> $ cat /etc/yum.repos.d/spice-unstable.repo
> [spice-unstable]
> name=spice development bits for fedora $releasever
> baseurl=http://kraxel.fedorapeople.org/spice/fedora$releasever
> enabled=1
> gpgcheck=0
>
> In particular, the "qemu-spice" package provides a new
> "/usr/bin/qemu-spice" binary (since it's not fully merged with
> upstream qemu, both qemu and qemu-spice can be installed side by side
> this way).
Hmm, thanks for the info. I gave it a try but so far I'm stumped. I've not really used qemu/kvm from the command line much and mostly use virt-manager. I read the instructions here:
http://kraxel.fedorapeople.org/spice/README
I got the following packages installed (from my /var/log/yum.log)
Jul 16 11:37:25 Installed: celt051-0.5.1.3-2.fc13.x86_64
Jul 16 11:37:26 Installed: spice-server-0.5.2-2.fc13.x86_64
Jul 16 11:37:29 Installed: qemu-spice-0.12.50-0.git.20100708.fc13.x86_64
Jul 16 11:37:30 Installed: spice-client-0.5.2-2.fc13.x86_64
Then I ran a VM from virt-manager and did a "ps auxwww | grep kvm" to see what the full command virt-manager uses. I took that command and modified it for qemu-spice and here is what I came up with:
/usr/bin/qemu-spice \
-spice port=1234,password=mypassword \
-device qxl \
-vga qxl \
-S \
-M pc \
-cpu core2duo,+x2apic \
-enable-kvm \
-m 2048 \
-smp 2,sockets=2,cores=1,threads=1 \
-name montanalinux32 \
-uuid 9cf9479c-3476-9aa5-bdd3-dccf5d8af015 \
-nodefaults \
-chardev socket,id=monitor,path=/var/lib/libvirt/qemu/montanalinux32.monitor,server,nowait \
-mon chardev=monitor,mode=readline \
-rtc base=utc \
-boot c \
-drive file=/vm/montanalinux32.img,if=none,id=drive-virtio-disk0,boot=on,format=raw \
-device virtio-blk-pci,bus=pci.0,addr=0x4,drive=drive-virtio-disk0,id=virtio-disk0 \
-drive if=none,media=cdrom,id=drive-ide0-1-0 \
-device ide-drive,bus=ide.1,unit=0,drive=drive-ide0-1-0,id=ide0-1-0 \
-device virtio-net-pci,vlan=0,id=net0,mac=52:54:00:3a:0d:08,bus=pci.0,addr=0x5 \
-net tap,fd=49,vlan=0,name=hostnet0 \
-chardev pty,id=serial0 \
-device isa-serial,chardev=serial0 \
-usb \
-device usb-tablet,id=input0 \
-k en-us \
-device AC97,id=sound0,bus=pci.0,addr=0x6
That seems to start up (at least it shows in ps output) BUT when I try to connect to it with the spice client via...
spicec -h localhost -p 1234 -w mypassword
...all I get is a black display in the window and it doesn't connect.
Please note that I used an existing Fedora 13 KVM VM. If I understand correctly the VM needs to have the qxl driver installed in it so maybe that is why it isn't working. Or do the command line options given above inject the qxl driver into the VM magically?
I'm very new to this so I have little idea what I'm doing much less what I'm doing wrong. Any help would be appreciated.
Thanks,
--
Scott Dowdle
704 Church Street
Belgrade, MT 59714
(406)388-0827 [home]
(406)994-3931 [work]
12 years, 10 months
Fullscreen keep permanent
by Frank Murphy
How can I keep fullscreen on the guests permanent.
I tick the check boxes on each console, but on reboot of the host,
the tick marks are gone.
This is mainly an eyesight issue for me.
virt-manager-0.8.4-2.fc13.noarch
--
Regards,
Frank Murphy
UTF_8 Encoded
Friend of Fedora
12 years, 10 months
Re: [fedora-virt] FYI: Major version rebase of libvirt in F12, F13 in updates-testing
by Boris Derzhavets
Via my experience block :-
/*
if (!(caps = xenHypervisorMakeCapabilitiesInternal(NULL, hostmachine, fp1, fp2)))
goto fail;
if (!(actualxml = virCapabilitiesFormatXML(caps)))
goto fail;
if (STRNEQ(expectxml, actualxml)) {
virtTestDifference(stderr, expectxml, actualxml);
goto fail;
}
*/
in file /usr/src/libvirt-0.8.2/tests/xencaptest.c been commented out causes libvirt build to crash under 2.6.32.16 pvops been built either via JF's Git Repo or via kernel built via dom0.src.rpm. Been commented it allows to build libvirt 0.8.2 :-
.....
Wrote: /root/rpmbuild/SRPMS/libvirt-0.8.2-1.fc13.src.rpm
Wrote:
/root/rpmbuild/RPMS/x86_64/libvirt-0.8.2-1.fc13.x86_64.rpm
Wrote: /root/rpmbuild/RPMS/x86_64/libvirt-client-0.8.2-1.fc13.x86_64.rpm
Wrote: /root/rpmbuild/RPMS/x86_64/libvirt-devel-0.8.2-1.fc13.x86_64.rpm
Wrote: /root/rpmbuild/RPMS/x86_64/libvirt-python-0.8.2-1.fc13.x86_64.rpm
Wrote: /root/rpmbuild/RPMS/x86_64/libvirt-debuginfo-0.8.2-1.fc13.x86_64.rpm
Completely functional after rpms install with at Xen 4.0.1-rc4 Hypervisor & 2.6.32.16 Dom0 on top of F13.
Boris.
--- On Thu, 7/22/10, Pasi Kärkkäinen <pasik(a)iki.fi> wrote:
From: Pasi Kärkkäinen <pasik(a)iki.fi>
Subject: Re: [fedora-virt] FYI: Major version rebase of libvirt in F12, F13 in updates-testing
To: "M A Young" <m.a.young(a)durham.ac.uk>
Cc: virt(a)lists.fedoraproject.org
Date: Thursday, July 22, 2010, 5:41
AM
On Wed, Jul 21, 2010 at 09:12:36PM +0100, M A Young wrote:
> I tried rebuilding libvirt-0.8.2-1.fc13 against xen-4.0.1-rc4 (from the
> same SRPM as http://koji.fedoraproject.org/koji/taskinfo?taskID=2324778 )
> and it worked for me, both on a standard Fedora kernel and a dom0 one
> under xen.
>
Ok, no problems with that then.
Thanks!
-- Pasi
_______________________________________________
virt mailing list
virt(a)lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/virt
12 years, 10 months
Re: [fedora-virt] vm from fc13 ro rhel/CentOS 5
by Gianluca Cecchi
On Thu, Jul 22, 2010 at 11:54 AM, Kashyap Chamarthy <kchamart(a)redhat.com>wrote:
>
> FWIW, the below worked for me while trying to migrate vms from one host to
> another(in my case,both RHEL5.5). I used 'virsh' (from libvirt)
>
> 1) 'virsh dumpxml <domain (or) id>'--this will dump the guest machine
> info. into XML.
> 2) copy your qcow2 image disk from host1 to host2.
> 3) 'virsh define <xml file>' for the dumped xml files from step 1)
>
> Now you should be good to start/run the above guest on your host2 (running
> kvm..)
>
> /kashyap
>
>
yes, the vm was a CentOS 5.5 os.
It worked like a charm.
I made a dump from a previous rh el 5 vm already existent on the rh el 5.5
host, using it as baseline for differences.
And this is diff output between xml dump in FC13 and the modified version to
have it imported by rh el 5.5
(btw I changed memory size from 1Gb to 2Gb as I passed from my laptop to an
enterprise 16Gb based server...)
#diff f13out.xml rhel55in.xml
< <name>op</name>
< <memory>2097152</memory>
< <currentMemory>2097152</currentMemory>
---
> <name>o11p</name>
> <uuid>8030a286-d41c-d692-648a-4d0aad122bdd</uuid>
> <memory>1048576</memory>
> <currentMemory>1048576</currentMemory>
7c8
< <type arch='x86_64' machine='pc'>hvm</type>
---
> <type arch='x86_64' machine='fedora-13'>hvm</type>
8a10
> <boot dev='cdrom'/>
14a17,20
> <cpu match='exact'>
> <model>core2duo</model>
> <feature policy='force' name='x2apic'/>
> </cpu>
20c26
< <emulator>/usr/libexec/qemu-kvm</emulator>
---
> <emulator>/usr/bin/qemu-kvm</emulator>
23c29
< <source file='/VMDATA/o11p.img'/>
---
> <source file='/var/lib/libvirt/images/c55.img'/>
I only had to change then network parameters in vm os.
In virt-manager I also removed the audio card.
I was then also able to apply "yum update" to this new vm and it runs quite
good.
Thanks,
Gianluca
12 years, 10 months
Re: [fedora-virt] FYI: Major version rebase of libvirt in F12, F13 in updates-testing
by Boris Derzhavets
rpmbuild -ba ./libvirt.spec |tee build.log
..........
PASS: virsh-all
PASS: virsh-schedinfo
PASS: virsh-synopsis
PASS: xml2sexprtest
PASS: sexpr2xmltest
PASS: xmconfigtest
-> FAIL: xencapstest
PASS: qemuxml2argvtest
PASS: qemuxml2xmltest
PASS: qemuargv2xmltest
PASS: qemuhelptest
PASS: nwfilterxml2xmltest
PASS: esxutilstest
PASS: vmx2xmltest
PASS: xml2vmxtest
PASS: seclabeltest
PASS: eventtest
PASS: networkxml2xmltest
PASS: storagevolxml2xmltest
PASS: storagepoolxml2xmltest
PASS: nodedevxml2xmltest
PASS: interfacexml2xmltest
====================
1 of 47 tests failed
====================
make[2]: Leaving directory `/root/rpmbuild/BUILD/libvirt-0.8.2/tests'
make[1]: Leaving directory `/root/rpmbuild/BUILD/libvirt-0.8.2/tests'
--- On Tue, 7/13/10, Daniel P. Berrange <berrange(a)redhat.com> wrote:
From: Daniel P. Berrange <berrange(a)redhat.com>
Subject: Re: [fedora-virt] FYI: Major version rebase of libvirt in F12, F13 in updates-testing
To: "Boris Derzhavets" <bderzhavets(a)yahoo.com>
Cc: virt(a)lists.fedoraproject.org
Date: Tuesday, July 13, 2010, 8:52 AM
On Tue, Jul 13, 2010 at 05:45:18AM -0700, Boris Derzhavets wrote:
> Attempt to build rpms via src.rpm at Xen 4.0.1-rc3 (2.6.32.16) Dom0 on top of F13 :-
>
> PASS: xmconfigtest
> TEST: xencapstest
> !!!!!!!!!! 10 FAIL
> FAIL: xencapstest
Edit the libvirt.spec file and change
make check
to
VIR_TEST_DEBUG=1 make check
then it should show what failed.
Xen isn't a supported platform in Fedora anymore though, so we can't hold
up the updates for this.
Regards,
Daniel
--
|: Red Hat, Engineering, London -o- http://people.redhat.com/berrange/ :|
|: http://libvirt.org -o- http://virt-manager.org -o- http://deltacloud.org :|
|: http://autobuild.org -o- http://search.cpan.org/~danberr/ :|
|: GnuPG: 7D3B9505 -o- F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 :|
12 years, 10 months
