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
12 years, 3 months
f15 guest with spice and gnome 3
by Gianluca Cecchi
Hello,
I'm testing an F15 beta guest running on an F14+virt-preview host.
Is it correct to say that as right now spice doesn't support 3d
acceleration, then my guest will only be able to run gnome 3 in
fallback mode?
In this case is there any emulated video adapter to configure with
which I can test f15 and gnome 3 in its new desktop layout?
Thanks in advance,
Gianluca
12 years, 12 months
info on resize support for virtio disk
by Gianluca Cecchi
hello,
I'm using F14+virt-preview repo and I have an f15 guest configured
with a virtio disk.
I'm trying online resize support for guest disk if in place.
So my disk is vda in guest and in guest xml I have:
<disk type='file' device='disk'>
<driver name='qemu' type='raw'/>
<source file='/var/lib/libvirt/images/f15_001.img'/>
<target dev='vda' bus='virtio'/>
<address type='pci' domain='0x0000' bus='0x00' slot='0x06' function='0x0'/>
</disk>
I extend the disk with qemu-img at host side:
qemu-img resize /var/lib/libvirt/images/f15_001.img +1G
In guest neither partprobe nor kpartx show any change...
I put the xml definition in disk.xml and try to update device from
libvirt point of view (my domain id is 4):
[root ~]# virsh update-device 4 disk.xml
error: Failed to update device from disk.xml
error: unsupported configuration: disk bus 'virtio' cannot be updated.
Any confirmation of this?
Teorically qemu/monitor should support block_resize command for virtio
devices too in qemu 0.14....
Is this true but functionality not ported to virsh command yet or
other kind of things?
Thanks for clarifications
Gianluca
12 years, 12 months
fedora virt versus RHEV - libvirt tools availability
by Dale Bewley
I hope this doesn't seem too far off topic.
In my current position we are a vmware shop. With a few dozen machines
in a handful of clusters, multipath fibrechannel storage, lots of live
migrations, etc.
In my past position, I did everything on Fedora with the help of virsh,
guestfish and all their friends, and life was very good. I could
provision machines with virt-install and koan. I could tweak the machine
definitions in XML. I could login and get a vm console very easy.
That environment was much smaller and all storage was essentially direct
attached and there was no live migration. Moving to vmware has a few
niceties, but feels encumbered.
I now want to evaluate RHEV against vmware, but I'm immediately taken
aback to see the need for a windows mgt console, and troubled by an
apparent burying of the libvirt API with a user push towards a REST API.
Maybe my perception is off. I'm going to RH Summit and will get some
more education next week.
Tools like guestfish and virsh are some of the drivers causing me to
explore vmware alternatives. If RHEV occludes those tools I'm left
wondering what do I get that I can't get from Fedora with an apparently
more open toolset. Other than the long term support.
What are others doing out there? How large have you scaled up a Fedora
solution (libvirt, virt-manager, virsh, kvm)? Are you performing live
migrations reliably? How do you feel about RHEV?
Anyone coming to RH Summit?
12 years, 12 months
Fedora Virt Status
by Justin Forbes
Fedora 14
- We have 95 open bugs, 5 of which have fixes in awaiting updates.
- 17 bugs have been closed in the last week
Fedora 15
- We have 22 open bugs.
- 9 bugs have been closed in the last week
- Beta is released, go test!
- Upcoming Dates of importance:
2011-05-09 Final Change Deadline
2011-05-10 Compose 'Final' RC
2011-05-24 Fedora 15 Final Release
== Updates Needing review ==
The following packages are in updates-testing and need review and karma as
appropriate:
F14:
- libguestfs-1.8.6-1.fc14
New stable version 1.8.6
- spice-protocol-0.8.0-1.fc14
Add support for copy and paste using the primary selection, to use this you
need a spice-gtk widget based client and the latest spice-gtk code
Various small bug fixes
F15:
- libguestfs-1.10.2-1.fc15
New upstream stable version 1.10.2.
== Virt Preview Repository ==
The virt-preview repository is now active for F14 users wishing to run the
latest F15 virt packages on their stable F14 systems. F13 virt-preview users
will still get the latest F14 packages. For details on how to run enable
virt-preview, please see:
https://fedoraproject.org/wiki/Virtualization_Preview_Repository
== Bugs of importance: ==
- 674530 Change CDROM of guest, new CD is truncated to the size of the old
Installing a very old guest which requires several CDs, the CD size is
truncated to the size of the first CD. This could be a bug in the guest
kernel, but needs to be investigated to ensure that it is not a hypervisor
issue.
- 693530 Qemu does the wrong thing with Cache=None and looks like corruption
btrfs complains about corruption when Windows guests do certain types of
writes with cache=none.
13 years
Testcase Virtualization Attach/Detach a SCSI device to guest
by Gianluca Cecchi
Hello,
with my F14+virt-preview repo and a CentOS 5.5 vm currently using
virtio devices, I'm not able to attach a scsi disk with virsh:
[root ~]# virsh attach-device c55ms /tmp/disk.xml
error: Failed to attach device from /tmp/disk.xml
error: internal error unable to execute QEMU command 'drive_add': The
command drive_add has not been found
Is this expected because the features between my system and current
rawhide are different?
I have qemu-kvm-0.14.0-7.fc14.x86_64
Or do I have to open a bug for this if not already open?
The same error trying to add from virt-manager:
Are you sure you want to add this device?
This device could not be attached to the running machine. Would you
like to make the device available after the next VM shutdown?
internal error unable to execute QEMU command 'drive_add': The command
drive_add has not been found
Traceback (most recent call last):
File "/usr/share/virt-manager/virtManager/addhardware.py", line 927,
in add_device
self.vm.attach_device(self._dev)
File "/usr/share/virt-manager/virtManager/domain.py", line 1240, in
attach_device
self._backend.attachDevice(devxml)
File "/usr/lib64/python2.7/site-packages/libvirt.py", line 263, in
attachDevice
if ret == -1: raise libvirtError ('virDomainAttachDevice()
failed', dom=self)
libvirtError: internal error unable to execute QEMU command
'drive_add': The command drive_add has not been found
BTW:
I know that in RH EL 6 it's not possible to define and use scsi disks
for Qemu/KVM guests (because related source parts not kept much in
sync with upstream patches and poor performance generally, if I
understood correctly)
I see now that between testcases for Fedora Virt test day there is
this one for scsi disks.
The question is: what is the expected situation in F15 for scsi disks
for guests in terms of performance and reliability? Does it matter the
format to be used with them?
Thanks,
Gianluca
13 years
Fwd: virt-preview: libguestfs requires glibc not in F14
by sean darcy
---------- Forwarded message ----------
From: sean darcy <seandarcy2(a)gmail.com>
Date: Thu, Apr 14, 2011 at 9:46 PM
Subject: Re: [fedora-virt] virt-preview: libguestfs requires glibc not in F14
To: "Richard W.M. Jones" <rjones(a)redhat.com>
On Thu, Apr 14, 2011 at 4:42 AM, Richard W.M. Jones <rjones(a)redhat.com> wrote:
> On Wed, Apr 13, 2011 at 07:19:21PM -0400, sean darcy wrote:
>> From the spec file:
>>
>> # Because many previously unreadable binaries have been made readable
>> # (because of RHBZ#646469) they will be included in the hostfiles
>> # list, which means that this libguestfs won't work with versions of
>> # glibc built before the change.
>> Requires: glibc >= 2.13.90-4
>>
>> This implies that even if I build it with glibc-2.13.0, it still won't work.
>
> Maybe the comment is badly worded, but the problem is not that you
> can't build against particular glibc. It is that if you build with
> glibc < 2.13.90-4 then you must install with glibc < 2.13.90-4, and
> conversely if you build with glibc >= 2.13.90-4 then you must install
> with glibc >= 2.13.90-4. There is no way to express this using RPM
> dependencies.
>
> Rich.
>
> --
> Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
> virt-df lists disk usage of guests without needing to install any
> software inside the virtual machine. Supports Linux and Windows.
> http://et.redhat.com/~rjones/virt-df/
>
Gotcha. OK, I'll get the src.rpm, build it against the F14 glibc, and,
hopefully, Bob's your uncle.
Not that I know anything about the Fedora/Red Hat infrastructure, if
you're doing a koji F14 build, wouldn't it be built against F14 glibc?
Thanks,
Sean
13 years
Fedora 15 Virtualization Test Day -- Thu. April 14th
by Justin Forbes
This is just a reminder that today, April 14 is Fedora Virtualization
test day. Test plans and more information for the event can be found on
the Fedora Project Wiki at:
https://fedoraproject.org/wiki/Test_Day:2011-04-14_Virtualization
IRC for the event on freenode in #fedora-test-day. Please come lend a
hand, we can use as many testers as possible. If you cannot make it
on Thursday, please feel free to run through test plans as you have
time,the feedback is still relevant and helps to make Fedora a better
platform for virtualization.
Thanks,
Justin
13 years
virt-preview: libguestfs requires glibc not in F14
by sean darcy
yum upgrade
...........
Error: Package: 1:libguestfs-1.9.14-1.fc14.x86_64 (fedora-virt-preview)
Requires: glibc >= 2.13.90-4
Installed: glibc-2.13-1.i686 (@updates)
glibc = 2.13-1
Available: glibc-2.12.90-17.i686 (fedora)
glibc = 2.12.90-17
rpm -q glibc
glibc-2.13-1.x86_64
glibc-2.13-1.i686
sean
13 years
Fedora Virt Test day is coming up in 2 days!
by Justin Forbes
This is just a reminder that Thursday, April 14 is Fedora Virtualization
test day. Test plans and more information for the event can be found on
the Fedora Project Wiki at:
https://fedoraproject.org/wiki/Test_Day:2011-04-14_Virtualization
IRC for the event on freenode in #fedora-test-day. Please come lend a
hand, we can use as many testers as possible. If you cannot make it
on Thursday, please feel free to run through test plans as you have
time,the feedback is still relevant and helps to make Fedora a better
platform for virtualization.
Thanks,
Justin
13 years