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
F12 and ksm/ksmtuned: info required...
by Gianluca Cecchi
Hello,
F12 x86_64 with Qemu/KVM booted yesterday evening.
It has two guests with CentOS 5.3 x86_64 configured to auto-start and
now they are running...
I see this morning, some minutes ago:
[root@virtfed ~]# service ksm status
ksm is not running
My config:
[root@virtfed ~]# chkconfig --list|grep ksm
ksm 0:off 1:off 2:on 3:on 4:on 5:on 6:off
ksmtuned 0:off 1:off 2:on 3:on 4:on 5:on 6:off
[root@virtfed ~]# cat /sys/kernel/mm/ksm/pages_shared
3786
Then I start two other guests, both with CentOS 5.4 x86_64.
After a while:
[root@virtfed ~]# cat /sys/kernel/mm/ksm/pages_shared
4752
[root@virtfed ~]# cat /sys/kernel/mm/ksm/pages_shared
5219
...
[root@virtfed ~]# cat /sys/kernel/mm/ksm/pages_shared
90895
and now, without any action at my side:
[root@virtfed ~]# service ksm status
ksm is running
Is this normal/expected?
Any deeper doc/link about ksm/ksmtuned logic?
Is it ksmtuned that spins ksm as it is needed? Any log file to check/configure?
I read https://fedoraproject.org/wiki/Features/KSM but probably I'm
missing something...
Thanks,
Gianluca
13 years, 3 months
libvirtd crashes host when autostarting
by Rich Mahn
Summary:
My host crashes when I use the autostart function in
libvirtd.
This command sequence works fine:
service libvirtd stop
virsh autostart mydomain --disable
service lib virtd start
virsh start mydomain
This command sequence will crash the host:
service libvirtd stop
virsh autostart mydomain
service libvirtd start
I can't find any error messages related to this. The host system
freezes, the keyboard starts blinking the caps-lock and scroll-lock,
and as best I can tell, the kernel has stopped running.
If I starting up the host system with the VM autostarted, I sometimes
get messages that look like kernel errors on the screen, but I don't
find them in any log files so far. They seem to be related to networking.
Here's some configuration information--I don't know really what all is
needed, but this, I guess is a start:
Host and VM both Fedora 11 with the lastest updates.
Host machine in Intel based with the virtual support turned on.
In the /var/log/libvirtd/qemu directory, the command line to start
the virtual machine is different when started from autostart. The
difference is in this portion:
-net tap,fd=11,vlan=0 for failure (autostart) and
-net tap,fd=18,vlan=0 for success
I am using a bridged connection.
Here's the command line that's used, split over
lines for some degree of readability:
LC_ALL=C PATH=/sbin:/usr/sbin:/bin:/usr/bin /usr/bin/qemu-kvm -S -M pc
-m 1024 -smp 1 -name mydomain
-uuid 5cde5a23-2abe-fcdd-04dc-5ae3a46ab51c
-monitor pty -pidfile /var/run/libvirt/qemu//mydomain.pid
-boot c -drive file=,if=ide,media=cdrom,index=2
-drive file=/dev/mapper/vg_host-lv_mydomain,if=virtio,index=0,boot=on
-drive file=/dev/mapper/vg_host-lv_mydomain_data,if=virtio,index=1
-net nic,macaddr=54:52:00:67:91:e9,vlan=0,model=virtio
-net tap,fd=11,vlan=0 -serial pty -parallel none
-usb -usbdevice tablet -vnc 127.0.0.1:0
13 years, 4 months
ANNOUNCE: Rawhide virt repo for F12 users
by Justin Forbes
As was done for Fedora 11 users, the tradition continues, only the
locations have changed.
We've set up a repository for people running Fedora 12 who would like
to test the rawhide/F13 virt packages. To use it, do e.g.
$> cat > /etc/yum.repos.d/fedora-virt-preview.repo << EOF
[rawvirt]
name=Virtualization Rawhide for Fedora 12
baseurl=http://jforbes.fedorapeople.org/virt-preview/f12/$basearch/
enabled=1
gpgcheck=0
EOF
$> yum update
At the moment, it contains the F-13 versions of libvirt and virt-manager, but
as F-13 development continues, it will contain more. I'll send periodic
mails to the list detailing the latest updates.
A couple of improvements have been made this time around. Namely
packages are build with mock instead of koji so that new packages can be
used a BuildRequires for other new packages. Also new builds are
triggered by successful koji builds of tracked packages against
dist-rawhide, so the process is a bit more automated.
Also, this is still a work-in-progress. The TODO list includes:
- include debuginfo packages in the repo (need more quota)
- find a better location than jforbes.fedorapeople.org
Comments most welcome. Help with the TODO list is even more welcome :-)
Thanks,
Justin M. Forbes
13 years, 5 months
some vm die in F12
by Gianluca Cecchi
Hello,
I had an F11 host with virt-preview repo configured and I have used it
a lot without particular problems.
Now I'm on F12 on the same host after upgrade and I'm experiencing
guests' death caused by oom killer.
Example.
- all VM (4) are qemu/kvm and x86_64
- boot of host on 26/11 about 19:20.
- two centos 5.3 guests are configured to startup automatically and
they indeed start
In messages I see this on their startup:
Nov 26 19:23:01 virtfed kernel: kvm: 3458: cpu0 unimplemented perfctr
wrmsr: 0x186 data 0x130079
Nov 26 19:23:01 virtfed kernel: kvm: 3458: cpu0 unimplemented perfctr
wrmsr: 0xc1 data 0xffcfadc8
Nov 26 19:23:01 virtfed kernel: kvm: 3458: cpu0 unimplemented perfctr
wrmsr: 0x186 data 0x530079
Nov 26 19:23:01 virtfed kernel: kvm: 3458: cpu1 unimplemented perfctr
wrmsr: 0x186 data 0x130079
Nov 26 19:23:01 virtfed kernel: kvm: 3458: cpu1 unimplemented perfctr
wrmsr: 0xc1 data 0xffcfadc8
Nov 26 19:23:01 virtfed kernel: kvm: 3458: cpu1 unimplemented perfctr
wrmsr: 0x186 data 0x530079
Nov 26 19:23:01 virtfed kernel: kvm: 3501: cpu0 unimplemented perfctr
wrmsr: 0x186 data 0x130079
Nov 26 19:23:01 virtfed kernel: kvm: 3501: cpu0 unimplemented perfctr
wrmsr: 0xc1 data 0xffcfadc8
Nov 26 19:23:01 virtfed kernel: kvm: 3501: cpu0 unimplemented perfctr
wrmsr: 0x186 data 0x530079
Nov 26 19:23:01 virtfed kernel: kvm: 3501: cpu1 unimplemented perfctr
wrmsr: 0x186 data 0x130079
Nov 26 19:23:36 virtfed kernel: kvm: emulating exchange as write
- On 27/11 at 12:03 I start other two guests in centos 5.4
Again I get rows similar to the above ones plus:
Nov 27 12:03:19 virtfed kernel: __ratelimit: 2 callbacks suppressed
The day after at 06:55
Nov 28 03:27:06 virtfed logrotate: ALERT exited abnormally with [1]
Nov 28 06:55:01 virtfed kernel: qemu-kvm invoked oom-killer:
gfp_mask=0x201da, order=0, oomkilladj=0
Nov 28 06:55:01 virtfed kernel: qemu-kvm cpuset=/ mems_allowed=0
Nov 28 06:55:01 virtfed kernel: Pid: 405, comm: qemu-kvm Tainted: G
W 2.6.31.5-127.fc12.x86_64 #1
Nov 28 06:55:01 virtfed kernel: Call Trace:
Nov 28 06:55:01 virtfed kernel: [<ffffffff8108a7d7>] ?
cpuset_print_task_mems_allowed+0x91/0x9d
Nov 28 06:55:01 virtfed kernel: [<ffffffff810c38e9>] oom_kill_process+0x98/0x256
Nov 28 06:55:01 virtfed kernel: [<ffffffff810c3d6a>] ?
select_bad_process+0xa3/0x102
Nov 28 06:55:01 virtfed kernel: [<ffffffff810c3e53>] __out_of_memory+0x8a/0x99
Nov 28 06:55:01 virtfed kernel: [<ffffffff810c3fc5>] out_of_memory+0x163/0x195
Nov 28 06:55:01 virtfed kernel: [<ffffffff810c75c1>]
__alloc_pages_nodemask+0x491/0x584
Nov 28 06:55:01 virtfed kernel: [<ffffffff810eb1c4>]
alloc_pages_current+0x95/0x9e
Nov 28 06:55:01 virtfed kernel: [<ffffffff810c15c1>]
__page_cache_alloc+0x5f/0x61
Nov 28 06:55:01 virtfed kernel: [<ffffffff810c9235>]
__do_page_cache_readahead+0x98/0x176
Nov 28 06:55:01 virtfed kernel: [<ffffffff810c9334>] ra_submit+0x21/0x25
Nov 28 06:55:01 virtfed kernel: [<ffffffff810c1abd>] filemap_fault+0x193/0x317
Nov 28 06:55:01 virtfed kernel: [<ffffffff810d6641>] __do_fault+0x54/0x3c4
Nov 28 06:55:01 virtfed kernel: [<ffffffff81017bc1>] ? read_tsc+0x9/0x1b
Nov 28 06:55:01 virtfed kernel: [<ffffffff810d881a>] handle_mm_fault+0x2f6/0x705
Nov 28 06:55:01 virtfed kernel: [<ffffffff8106a9ff>] ?
__hrtimer_start_range_ns+0x2bb/0x2cd
Nov 28 06:55:01 virtfed kernel: [<ffffffff8141cfe1>] do_page_fault+0x281/0x299
Nov 28 06:55:01 virtfed kernel: [<ffffffff8141af75>] page_fault+0x25/0x30
Nov 28 06:55:01 virtfed kernel: Mem-Info:
Nov 28 06:55:01 virtfed kernel: Node 0 DMA per-cpu:
Nov 28 06:55:01 virtfed kernel: CPU 0: hi: 0, btch: 1 usd: 0
Nov 28 06:55:01 virtfed kernel: CPU 1: hi: 0, btch: 1 usd: 0
Nov 28 06:55:01 virtfed kernel: CPU 2: hi: 0, btch: 1 usd: 0
Nov 28 06:55:01 virtfed kernel: CPU 3: hi: 0, btch: 1 usd: 0
Nov 28 06:55:01 virtfed kernel: CPU 4: hi: 0, btch: 1 usd: 0
Nov 28 06:55:01 virtfed kernel: CPU 5: hi: 0, btch: 1 usd: 0
Nov 28 06:55:01 virtfed kernel: CPU 6: hi: 0, btch: 1 usd: 0
Nov 28 06:55:01 virtfed kernel: CPU 7: hi: 0, btch: 1 usd: 0
Nov 28 06:55:01 virtfed kernel: Node 0 DMA32 per-cpu:
Nov 28 06:55:01 virtfed kernel: CPU 0: hi: 186, btch: 31 usd: 86
Nov 28 06:55:01 virtfed kernel: CPU 1: hi: 186, btch: 31 usd: 136
Nov 28 06:55:01 virtfed kernel: CPU 2: hi: 186, btch: 31 usd: 51
Nov 28 06:55:01 virtfed kernel: CPU 3: hi: 186, btch: 31 usd: 126
Nov 28 06:55:01 virtfed kernel: CPU 4: hi: 186, btch: 31 usd: 86
Nov 28 06:55:01 virtfed kernel: CPU 5: hi: 186, btch: 31 usd: 34
Nov 28 06:55:01 virtfed kernel: CPU 6: hi: 186, btch: 31 usd: 171
Nov 28 06:55:01 virtfed kernel: CPU 7: hi: 186, btch: 31 usd: 169
Nov 28 06:55:01 virtfed kernel: Node 0 Normal per-cpu:
Nov 28 06:55:01 virtfed kernel: CPU 0: hi: 186, btch: 31 usd: 173
Nov 28 06:55:01 virtfed kernel: CPU 1: hi: 186, btch: 31 usd: 42
Nov 28 06:55:01 virtfed kernel: CPU 2: hi: 186, btch: 31 usd: 160
Nov 28 06:55:01 virtfed kernel: CPU 3: hi: 186, btch: 31 usd: 109
Nov 28 06:55:01 virtfed kernel: CPU 4: hi: 186, btch: 31 usd: 112
Nov 28 06:55:01 virtfed kernel: CPU 5: hi: 186, btch: 31 usd: 112
Nov 28 06:55:01 virtfed kernel: CPU 6: hi: 186, btch: 31 usd: 174
Nov 28 06:55:01 virtfed kernel: CPU 7: hi: 186, btch: 31 usd: 118
Nov 28 06:55:01 virtfed kernel: Active_anon:2537459 active_file:3
inactive_anon:364350
Nov 28 06:55:01 virtfed kernel: inactive_file:160 unevictable:12562
dirty:0 writeback:0 unstable:0
Nov 28 06:55:01 virtfed kernel: free:16256 slab:29833 mapped:7872
pagetables:10697 bounce:0
Nov 28 06:55:01 virtfed kernel: Node 0 DMA free:15824kB min:16kB
low:20kB high:24kB active_anon:0kB inactive_anon:0kB active_file:0kB
inactive_file:0kB unevictable:0kB present:15320kB pages_scanned:0
all_unreclaimable? yes
Nov 28 06:55:01 virtfed kernel: lowmem_reserve[]: 0 3254 12092 12092
Nov 28 06:55:01 virtfed kernel: Node 0 DMA32 free:39060kB min:3784kB
low:4728kB high:5676kB active_anon:2510452kB inactive_anon:502304kB
active_file:12kB inactive_file:244kB unevictable:520kB
present:3332660kB pages_scanned:120 all_unreclaimable? no
Nov 28 06:55:01 virtfed kernel: lowmem_reserve[]: 0 0 8837 8837
Nov 28 06:55:01 virtfed kernel: Node 0 Normal free:10140kB min:10280kB
low:12848kB high:15420kB active_anon:7639384kB inactive_anon:955096kB
active_file:0kB inactive_file:396kB unevictable:49728kB
present:9049596kB pages_scanned:0 all_unreclaimable? no
Nov 28 06:55:01 virtfed kernel: lowmem_reserve[]: 0 0 0 0
Nov 28 06:55:01 virtfed kernel: Node 0 DMA: 2*4kB 1*8kB 2*16kB 1*32kB
2*64kB 0*128kB 1*256kB 0*512kB 1*1024kB 1*2048kB 3*4096kB = 15824kB
Nov 28 06:55:01 virtfed kernel: Node 0 DMA32: 3793*4kB 2168*8kB
68*16kB 11*32kB 4*64kB 6*128kB 3*256kB 2*512kB 2*1024kB 0*2048kB
0*4096kB = 38820kB
Nov 28 06:55:01 virtfed kernel: Node 0 Normal: 1948*4kB 5*8kB 0*16kB
0*32kB 2*64kB 0*128kB 1*256kB 0*512kB 0*1024kB 1*2048kB 0*4096kB =
10264kB
Nov 28 06:55:01 virtfed kernel: 26703 total pagecache pages
Nov 28 06:55:01 virtfed kernel: 18747 pages in swap cache
Nov 28 06:55:01 virtfed kernel: Swap cache stats: add 1236041, delete
1217294, find 52896/69574
Nov 28 06:55:01 virtfed kernel: Free swap = 0kB
Nov 28 06:55:01 virtfed kernel: Total swap = 4194296kB
Nov 28 06:55:01 virtfed kernel: 3145727 pages RAM
Nov 28 06:55:01 virtfed kernel: 63020 pages reserved
Nov 28 06:55:01 virtfed kernel: 76044 pages shared
Nov 28 06:55:01 virtfed kernel: 3053641 pages non-shared
Nov 28 06:55:01 virtfed kernel: virbr0: port 3(vnet4) entering disabled state
Nov 28 06:55:01 virtfed kernel: device vnet4 left promiscuous mode
Nov 28 06:55:01 virtfed kernel: virbr0: port 3(vnet4) entering disabled state
About 1 hour and a half after, at 08:14 I get the same for the other 5.4 vm.
The same happens for other processes
Any hints on this and on how to debug? Any other one?
I don't know if it can be related, but I also tried to reboot
disabling ksm and ksmtuned:
[root@virtfed ~]# chkconfig --list ksmtuned
ksmtuned 0:off 1:off 2:off 3:off 4:off 5:off 6:off
[root@virtfed ~]# chkconfig --list ksm
ksm 0:off 1:off 2:off 3:off 4:off 5:off 6:off
getting the same problem...
strangely, I get anyway this:
[root@virtfed ~]# service ksm status
ksm is running
Why ksm is running? How can I configure a VM to be or not to be
managed with ksm?
Or is it an overall feature to enable/disable?
13 years, 6 months
wireless network connectivity
by Paul Lambert
I need some feedback as to what could be the source of my wireless
connectivity for FE-12. Previously, there were some serious problems with
the wireless network software as well as the user interface using FE-12. In
general, these issues have been corrected.
The problem I now see is dropped connections. This could be due to failure
to re-authenticate or something in the driver. I mostly see this problem
when connecting to a Linksys WRT160N. However, once the problem is observed
the FE-12 will not reconnect to any wireless router unless I logoff and then
log back on. Or, simply reboot the computer.
It should be noted that the WRT160N has been plagued by software problems.
In fact, you can buy an entire new OS for these and many problems go away.
I using v3 the latest from Linksys for this device. For the most part when
I connect to a WRT54G I do not see these problems.
Scenario:
After bootup the computer will connect to the WRT160N and communicate as
expected. The longer I stayed connected the slower the response gets.
Eventually, when executing an "arp -a" command the system will return the
MAC address with a <incomplete> instead of the IP address for the router.
The computer's IP address 192.168.1.100 and the router is 10.10.10.1. At
this point attempting to connect to a different router (WRT54G) does not
work either. Only a logout or reboot corrects the problem.
I am using WPA & WPA2 Personal authentication whereas the WRT54G uses WEP.
I am hesitant to file a bug report due to the possibility the root problem
is not in FE-12. However, the fact that the FE-12 network drive does not
recover indicates something is not quite right.
Thanks
PJAL
13 years, 6 months
Working sound in KVM with SDL display on Fedora 12 ?
by Daniel P. Berrange
I've been working on GTK-VNC to make it able to receive the audio stream
from the remote VNC server, and decided to compare the quality against
the current KVM host audio support. At which point I discovered that,
AFAICT, the latter does not work in the slightest.
I know that when running KVM guests with VNC under libvirt, you will not
get any sound because I disabled that bit of code :-) It is guests using
SDL graphics I'm interested in. eg, running a really simple guest like
/usr/bin/qemu-kvm -m 700 -smp 1 -boot c
-drive file=/home/berrange/f11i686.img,if=virtio,index=0,boot=on
-vga cirrus -soundhw ac97 -sdl
I have tested both ac97, and es1370 sound cards. I have tested with the
default QEMU host audio backend (pulseaudio), and with also tested with
each of the following settings on the host
<no env set>
QEMU_AUDIO_DRV=pa
QEMU_AUDIO_DRV=alsa
QEMU_AUDIO_DRV=sdl
QEMU_AUDIO_DRV=sdl SDL_AUDIODRIVER=pa
QEMU_AUDIO_DRV=sdl SDL_AUDIODRIVER=alsa
NB, they all ultimately go to pulseaudio on the host since it has its
alsa proxy installed
All of them appear to be more or less just as bad as each other. Inside the
guest I'm running a boring old F11 i686 guest. I removed pulseaudio inside
the guest and run 'mpg321' on the native alsa drivers. If you include the
'-v' flag to mpg321, it shows its playback progress. What I'm seeing is
that for the first 10 seconds or so its timer runs at 1/2 the actual
speed, and then it speeds up exponentially taking a mere 10 seconds for the
remaining 2 minutes of the mp3.
Does anyone successfully have KVM on Fedora 12 playing audio when using
the SDL display ? AFAICT, audio is just totally & utterly fubar, with
SDL and any of the host audio drivers. So if anyone has it working
reliably please tell me what, if any, QEMU_AUDIO_DRV / SDL_AUDIODRIVER
env variables you have set, what guest OS you use, and what program you
are using for playback in the guest. Also on the host, whether you have
pulse audio (the default for F12), or are using native ALSA directly.
On the plus side, by comparison, my code for streaming audio to GTK-VNC is
managing to playback at pretty much native speed, with only a few dropouts
in buffering
Daniel
--
|: Red Hat, Engineering, London -o- http://people.redhat.com/berrange/ :|
|: http://libvirt.org -o- http://virt-manager.org -o- http://ovirt.org :|
|: http://autobuild.org -o- http://search.cpan.org/~danberr/ :|
|: GnuPG: 7D3B9505 -o- F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 :|
13 years, 6 months
Routing to guests
by Philip Rhoades
People,
I have an ADSL router:
192.168.0.1
a 64bit F12 host:
eth0: 192.168.0.10
virbr0: 192.168.122.1
a F11 guest:
eth0: 192.168.122.68
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" -
I have "route add" things with no success.
- I had a look at:
http://docs.fedoraproject.org/virtualization-guide/f12/en-US/html/ but
the problem does not seem to be covered there.
Thanks,
Phil.
--
Philip Rhoades
GPO Box 3411
Sydney NSW 2001
Australia
E-mail: phil(a)pricom.com.au
13 years, 6 months
Re: [fedora-virt] release notes virt passage seems overly pessimistic
by Dale Bewley
----- "Robert P. J. Day" <rpjday(a)crashcourse.ca> wrote:
> On Sun, 22 Nov 2009, Dale Bewley wrote:
> > ----- "Robert P. J. Day" <rpjday(a)crashcourse.ca> wrote:
> > > reading here:
> > >
> > >
> http://docs.fedoraproject.org/release-notes/f12/en-US/html/sect-Release_N...
> > >
> > > down at the bottom:
> > >
> > > "KVM requires hardware virtualization features in the host
> system.
> > >
> > > Systems lacking hardware virtualization do not support Xen guests
> > > at this time."
> > >
> > > if one is new to virt, that could be read as, "without HW virt,
> > > you're pretty much screwed." or could that be worded a bit
> > > differently?
> >
> > This is the same text carried over from 10 and 11.
> >
> >
> http://docs.fedoraproject.org/release-notes/f10/en_US/What_Do_System_Admi...
> >
> > While Xen does not require hardware support, KVM still (always
> > will?) does. Xen guests on Fedora still require KVM-based xenner.
> > There has been success with Xen dom0 on experimental 3rd party
> > kernels, but that may be beyond the scope of the release notes. We
> > wouldn't want it to be inferred as a recommendation.
> >
> > Hopefully the F13 release notes will be able to describe native
> > support for Xen dom0 hosts.
> >
> >
> http://fedoraproject.org/wiki/FWN/Issue202#No_Xen_dom0_in_Fedora_12_Hopef...
> >
> > If you have any suggestions for further improvement to the release
> > notes, please keep them coming.
>
> for people new to virtualization, i was simply suggesting that that
> wording still leaves some doubt as to what's possible.
>
> what about a slightly longer explanation which describes what you
> can support based on the capabilities of your system, as in:
>
> 1) if your system supports H/W virtualization, you can do the
> following:
>
> ... list of things ...
>
> 2) if your system does *not* support H/W virtualization, you are
> limited to the following:
>
> ... much shorter list ...
>
> that should be written for the newbie since the most frustrating
> experience for beginners is to invest considerable time trying to do
> something, only to eventually learn that it wasn't possible all
> along.
>
> i'm thinking a page entitled something like "So, you have a
> computer
> and you want to get into virtualization." does such a page exist?
>
> rday
Under
http://fedoraproject.org/wiki/Category:Virtualization
We do have
http://fedoraproject.org/wiki/Getting_started_with_virtualization
--
Dale Bewley - Unix Administrator - Shields Library - UC Davis
GPG: 0xB098A0F3 0D5A 9AEB 43F4 F84C 7EFD 1753 064D 2583 B098 A0F3
13 years, 6 months
