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, 4 months
Cloning very slow?
by Tom Hughes
Yesterday I cloned one of my VMs and, somewhat implausibly, it took
virt-clone something like 8-9 hours to clone the 8Gb disk image...
Copying it from the command line took a mere 6.5 minutes.
I assume this is a bug, and it's not expected to take this long ;-)
This was using virt-clone from python-virtinst-0.500.2-1.fc12.noarch in
the virt-preview repository.
Tom
--
Tom Hughes (tom(a)compton.nu)
http://compton.nu/
14 years, 1 month
Re: [fedora-virt] Cloning very slow?
by Tom Hughes
On 29/04/10 12:33, jimmyb(a)jgbiii.com wrote:
> Can you update libvirt from updates-testing repo. It should be 0.7.7-3, this should fix the time to clone.
Well I was using the one from virt-preview which I assumed would be at
least as new as anything in updates or updates-testing ;-) It only
appears to be 0.7.7-2 however.
Tom
--
Tom Hughes (tom(a)compton.nu)
http://compton.nu/
14 years, 1 month
fedora 13 and Bugs 508317 & 477955
by Daniel Sanabria
Does anybody knows is the above bugs will be fixed in Fedora 13? I can see
that they are blocking F13Target which makes me think that that fixes will
be in the next version of fedora, but how can I track the progress made on
these fixes and how can I contribute with testing?
Cheers,
Daniel
14 years, 1 month
Any guesses for spice in fedora?
by Tom Horsley
I haven't quite worked up the energy to try building spice
by hand or digging up an experimental repo, but I'm wondering
if there are any guesses about when it might show up in
a fedora release.
Is fedora 14 too soon? (I might try to gather more energy
to try it manually if I'll have to wait longer than that :-).
14 years, 1 month
Fedora virt status
by Justin Forbes
Fedora 13
=========
The Fedora 13 beta is released now. Testing of virt features is
appreciated. We are down to the wire, with less than two weeks before
the release candidate is composed.
It should be noted that non frozen rawhide means that changes for F-13
now need to happen in the F-13 branch, as well as devel.
F-13 schedule:
2010-05-06 Compose Release Candidate (12 days)
Fedora Cloud SIG
================
Progress is being made towards updated Fedora in the EC2 cloud, and
There is some interest in supporting other cloude nvironemnets. More
details can be found at https://fedoraproject.org/wiki/Cloud_SIG
F12 Qemu
========
Fedora 12 has a qemu update in updates-testing which is should fix a
number of issues. Please test and provide karma as appropriate.
Virt Preview
================
As was announced before, the virt-preview repository for F12 users wishing
to test out the latest F13 virtualization bits is available. Additionally we
have created a virt-preview repository for F13 users wishing to test out
packages destined for F14 virtualization. Instructions for using these
repositories can be found at:
https://fedoraproject.org/wiki/Virtualization_Preview_Repository
Recent updates in this repository include:
F-12:
====
qemu-0.12.3-8:
- Change requires to the noarch seabios-bin
- Add ownership of docdir to qemu-common (#572110)
- Fix "Cannot boot from non-existent NIC" error when using virt-install (#577851)
- Update virtio console patches from upstream
virt-manager-0.8.3-3:
- Fix volume creation from 'New VM' wizard (bz 579039)
- Fix firstrun app lock up when calling PackageKit
- Fix File->Add Connection (bz 580578)
F-13:
====
libvirt-0.8.0-1:
- Upstream release 0.8.0
- Snapshotting support (QEmu/VBox/ESX)
- Network filtering API
- XenAPI driver
- new APIs for domain events
- Libvirt managed save API
- timer subselection for domain clock
- synchronous hooks
- API to update guest CPU to host CPU
- virDomainUpdateDeviceFlags new API
- migrate max downtime API
- volume wiping API
- and many bug fixe
python-virtinst-0.500.3-1:
- Update to version 0.500.3
- virt-install: New --watchdog option: configure a virtual watchdog device
- virt-install: New --soundhw option: More flexible sound configuration
deprecates --sound, though back compat is maintained
- virt-install: New --security option: configure VM security driver settings
- virt-install: New --description option: set a human readable description
- Better OS defaults: Use <video> VGA and <sound> AC97 if supported
- Enable x2apic for new KVM guests
virt-manager-0.8.4-1:
- Update to version 0.8.4
- 'Import' install option, to create a VM around an existing OS image
- Support multiple boot devices and boot order
- Watchdog device support
- Enable setting a human readable VM description.
- Option to manually specifying a bridge name, if bridge isn't detected
F13 Bugs
========
DOOM-O-METER: 76 bugs remain open against F13 virtualization packages,
60 are not fixed with pending releases.
The beta release has provided new testers, which found new bugs.
We have a lot of work to do before release. Anyone wishing to help can
find more information at:
http://fedoraproject.org/wiki/Virtualization_bugs
= Blockers =
== kernel ==
https://bugzilla.redhat.com/show_bug.cgi?id=577059
Failure while swapping install discs on KVM guest (F12 virt host)
Work is in progress to get this blocker resolved quickly.
= Important =
== kvm ==
https://bugzilla.redhat.com/show_bug.cgi?id=478317
almost 9 thousand syscalls per second while idle
A patch has been posted which may resolve the issue. Look for an update
after further testing.
https://bugzilla.redhat.com/show_bug.cgi?id=544339
Segfaults logged from kvm (qemu-kvm) resulting in guest sudden crash
and data loss
A number of users complaining of guests crashing and sometimes taking
the host with them. This appears to be related to sound emulation.
Feedback suggests that this is no longer an issue in the 0.12.x qemu
packages. These packages are available in F-12 updates-testing will be
updates to F-12 soon.
https://bugzilla.redhat.com/show_bug.cgi?id=544940
reattach virtio to rhel{5,6} guests will cause qemu-kvm crash
14 years, 1 month
Guest networking problem
by Adam Huffman
Yesterday I setup a Windows XP guest on a new F12 machine. Everything
proceeded normally.
This afternoon, the guest has lost network connectivity and has given
itself a 169.254. address as a result.
No DHCP requests are now being logged from the guest, whereas the
dnsmasq log showed them coming in all morning.
I would be grateful for any suggestions on how to investigate this.
Adam
14 years, 1 month
possible memory leak ?
by Razvan Radu
hello,
after running an stress program in the guest for 6 to 24 hours the
qemu-kvm process uses up all the available memory and gets killed by
oom, is this an bug or an configuration problem ?
host:
arch: intel i7 12gb ram
fedora 12 updated as of 2010-04-19 with fedora-virt packages
kernel: 2.6.32.11-99.fc12.x86_64
qemu: qemu*0.12.3-7.fc12.x86_64, also tested with qemu*0.12.3-6.fc12.x86_64
libvirt: libvirt*0.7.7-2.fc12.x86_64
qemu command: /usr/bin/qemu-kvm -S -M pc-0.11 -enable-kvm -m 3072 -smp
4,sockets=4,cores=1,threads=1 -name guest-00574 -uuid
3f26c499-b029-3e1c-2410-fd197b262057 -nodefaults -chardev
socket,id=monitor,path=/var/lib/libvirt/qemu/guest-00574.monitor,server,nowait
-mon chardev=monitor,mode=readline -rtc base=utc -boot dc -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 -drive
file=/dev/hdd.img/guest-00574-1,if=none,id=drive-virtio-disk0,boot=on,cache=none
-device
virtio-blk-pci,bus=pci.0,addr=0x4,drive=drive-virtio-disk0,id=virtio-disk0
-device
virtio-net-pci,vlan=0,id=net0,mac=54:52:00:00:00:49,bus=pci.0,addr=0x5
-net tap,fd=21,vlan=0,name=hostnet0 -usb -device usb-tablet,id=input0
-vnc 0.0.0.0:2 -vga cirrus -device
virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x3
guest:
CentOS release 5.4
kernel: 2.6.18-164.15.1.el5
stress program:
http://weather.ou.edu/~apw/projects/stress/
comman line: ./stress -v -c 4 -m 4 --vm-bytes 800M -d 4 --hdd-bytes 100M
-t 100000
the qemu process is constantly using more and more memory and after a
while it get killed
I have tested with:
- no hugepages
- hugepages
- lvm
- qcow2 image files
- cache=writeback
- cache=none
all resulted in the same memory usage pattern (slowly growing)
do you know of an formula for calculating the memory overhead for
qemu-kvm (without an potential memory leak ...) ?
I have noticed an 20% overhead with and without hugepages (pmap reported
a total of 1.2G for an 1G guest and 3.6G total for an 3G guest)
is 20% an correct assumption (it seems a little high) ?
I have observed the same overhead with hugepages, is this normal ?
thanks,
--
Razvan RADU
+40 (72) 7772218 / mobile
14 years, 1 month
Install XP without CD/DVD Rom
by Manish S Runwal
Right now I am using fedora 12. I want to install WinXP virtually. so I copied all its setup files on specific folder.
Then started virtual machine manager -> new virtual machine -> name given "WinXP"
->selected local install media (ISO image or CD Rom) -> then select the path. and when I make it next I get the attached error.
"Fatal : No Boot device."
though its bootable disk's files.
With Regards,
Manish S Runwal
Runwalsoft.com
14 years, 1 month
ANNOUNCE: Rawhide virt-preview repo for F13 users
by Justin Forbes
With no frozen rawhide, we find ourselves in the situation that rawhide
is already diverged from Fedora 13. Don't worry, we are not going to
kill virt-preview as you know and love it. The idea here is to keep the
current F12 virt-preview as it is, tracking F13 packages. A new
repository has been created, built against F13 that will track devel
packages until the F-14 split, and then follow the F-14 packages. To
use this repository simply:
$> cat > /etc/yum.repos.d/fedora-virt-preview.repo << EOF
[virt-preview]
name=Virtualization Rawhide for Fedora 13
baseurl=http://jforbes.fedorapeople.org/virt-preview/f13/\$basearch/
enabled=1
gpgcheck=0
EOF
$> yum update
Thanks,
Justin
14 years, 1 month
