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
Is this an F12 or Virt Problem
by Frank Murphy
F13 x86_64 host. core 2 quad
Virt-manager:
Trying to boot F12 x86_64 LiveCD (2 cores, 2gb ram allowed)
Should this be bugged?
--
Regards,
Frank Murphy
UTF_8 Encoded
Friend of Fedora
13 years, 10 months
Mock Building
by Frank Murphy
Would you place a mock setup on the host or within one of the guests?
--
Regards,
Frank Murphy
UTF_8 Encoded
Friend of Fedora
13 years, 10 months
Need Pointers for Setting up Virt Host + Guests
by Frank Murphy
Have a box with a 320GB and a 500gm sata hds'
What is the best method to set this up.
It's a core 2 quad 64bit, with currently 4gb ram (max 8)
I would like it to run Fedora12 32+64 && Fedora13 32+64 && Rawhide.
For trying to reproduce certain bugs on current Releases.
I can add extra drives to box as necessary.
Best base F12,F13, Rawhide?
XFCE is my preferred DE.
--
Regards,
Frank Murphy
UTF_8 Encoded
Friend of Fedora
13 years, 10 months
pxe boot again
by Farkas Levente
hi,
i already wrote a thread about it a long time ago:
https://www.redhat.com/archives/et-mgmt-tools/2008-May/msg00139.html
now i try it again. we've got a working pxe server and use it to install
all of our system. now i like to test it, but it still (or again) not
working.
with virtualbox 3.2 if i choose bridged networking and switch off
VT-x/AMD-V support as described in:
http://www.virtualbox.org/ticket/2536
than it's working. but with kvm not.
so is there anybody who can tell me:
- is the pxe boot working in virt-manager kvm?
- if yes, which kind of setup? ie:
- which kind of networking to choose?
- nat or bridged?
- what else should i've to configure to get it working?
thanks in advance.
regards.
--
Levente "Si vis pacem para bellum!"
13 years, 11 months
boot.fedoraproject.org?
by Tom Horsley
I'm experimenting with boot.fedoraproject.org again, trying to
install a KVM booted from the bfo.iso boot CD image, and I'm
noticing some wacky behavior.
When I let the image file boot normally the DHCP step
always prints dots for several seconds then fails.
If I send a Ctrl-Alt-Del to the KVM after the initial network
failure, it reboots and the 2nd DHCP attempt prints one
dot then immediately says "Here we go!" (There was a mention
of this same behavior for PXE here:
http://lists.fedoraproject.org/pipermail/virt/2010-June/002108.html
and the Ctrl-Alt-Del thing worked for gPXE as well).
I'm now trying to install f13, and it is downloading the
install.img file. Looking at my network stats, it is only
managing a data rate of about 15K (occasionally hitting
a peak of 20K). Meanwhile, the cpu is running at 99%.
Is the gPXE ethernet running one byte at a time polled
transfers or something?
I'll see if the transfer rate improves once it starts running
the anaconda kernel (but it may take a while to get that
far :-).
13 years, 11 months
Re: [fedora-virt] Losing sound in Win XP qemu-kvm guest
by jah
Thanks for the reply Gilboa. I had given up on getting a response to my
email and almost didn't spot it. It's disappointing that nobody from
Red Hat feels like it's worth responding to. The only thing I could
find in Bugzilla was 520228, a very similar problem with F11 from Aug
2009. Though this pertains to my Fedora desktop at home, possibly my
Red Hat rep at work can find a resource who would share some insight on
the problem.
Anyway, I switched QEMU_AUDIO_DRV from "alsa" to "pa" and that made the
problem worse, sound went out a few minutes after starting the guest. I
don't have any experience running KVM under F12 but I am running
Virtualbox under F12 at work (no hardware virtual extentions) and sound
works great in my XP guest. What exactly are the "connection refused"
messages you're getting from qemu? The only unusual messages I'm
getting are occasional bursts of this message:
Jun 11 23:52:51 host pulseaudio[2651]: ratelimit.c: 676 events suppressed
Jun 12 10:10:06 host pulseaudio[2651]: ratelimit.c: 676 events suppressed
Jun 12 11:02:53 host pulseaudio[2651]: ratelimit.c: 685 events suppressed
In Gentoo I only had this problem when I ran KVM as a module, not when
it was compiled into the kernel. Unfortunately nowdays compiling a
custom kernel in Red Hat/Fedora is a little more involved and not really
worth re-doing every time a new kernel update comes out.
-jah
> Seeing the same.
> My script defaults to PA.
>
> Looking at the console, I see that qemu is getting connection refused.
> I'd imagine that the problem is that my scripts runs as root (I use only
> bridged networks), and PA (per-user) is getting rejected.
>
> What I don't understand is - why it worked just fine under F12, and why
> it doesn't work now? Though, I have a feeling that this a PA issue - not
> qemu.
>
> - Gilboa
>
13 years, 11 months
StablePCI and Windows 7 guests
by Adam Huffman
Is the Stable PCI Address feature in Fedora 13 supposed to fix the
problem of Windows 7 guests detecting a new network interface at each
boot?
Adam
13 years, 11 months
Fedora 13 and Win XP Guest - Boot anomaly
by Ken Smith
Hi, New to the list but not to Linux.
There has been a discussion on the "Fedora Users" list about an anomaly
that's been seen with FC13 64bit and installing XP as a guest.
It's a standard FC13 installation on a machine with an Intel i7 and 4G Ram.
When the XP installation finishes the initial text style part of its
install process and reboots to run the GUI part of the install process
the virtual machine fails to boot it from the virtualised hard disk.
But if its set to boot from the CD or, in my case, the iso image of a XP
install CD and its allowed to time out its initial question "Press any
key to boot from CD....." then the virtual machine starts up and
completes the XP installation.
One the installation is finished, similar behaviour is seen to get the
XP virtual system to start up. If I change the setting in virt-manager
to boot from the Hard Disk image the boot of the VM fails but leaving it
set to boot from the install CD allows it to start normally after
allowing the initial question to timeout
I have cc'd Suvayu Ali on this posting as he has also observed similar
behaviour.
The thread on the Fedora Users list is here ->
http://lists.fedoraproject.org/pipermail/users/2010-June/374730.html
Any suggestions.
Thanks
Ken
--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
13 years, 11 months
virtio-win on Fedora 13
by Patricio A. Bruna
Hi,
>From where i can download the virtio-win package for Fedora 13?
Thanks.
------------------------------------
Patricio Bruna V.
IT Linux Ltda.
www.it-linux.cl
Fono : (+56-2) 333 0578
Móvil: (+56-9) 7776 2899
13 years, 11 months
