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
Fedora 12 Xen guests (domU) and hosts (dom0)
by Pasi Kärkkäinen
Hello,
I thought of writing some information about running Fedora 12 Xen guests
and also Fedora 12 Xen hosts/dom0.
Fedora 12 includes the upstream Linux pv_ops Xen domU support in the default kernel.
By using virt-install or virt-manager you can install Fedora 12 Xen PV
(paravirtual) guests directly from network, for example on RHEL 5.4,
CentOS 5.4, or Fedora Xen dom0/host.
If you want to run Fedora 12 Xen dom0 (host), there are some extra steps
needed. Fedora 12 ships with Xen hypervisor and management tools
(Xen 3.4.1, and Xen 3.4.2 in the F12 updates), but the required Xen dom0
capable host kernel is not included in Fedora atm/yet.
General information about Xen dom0 status in Fedora:
http://fedoraproject.org/wiki/Features/XenPvopsDom0
There are a couple of different ways to get and install a Xen dom0
capable kernel to Fedora 12 host:
- By using pre-packaged pv_ops xendom0 kernel rpms by M A Young. his repository:
http://fedorapeople.org/~myoung/dom0/
- Compiling and installing Xen dom0 capable kernel yourself/manually.
There are many options to choose from, full list of the available Xen
dom0 capable kernels is here:
http://wiki.xensource.com/xenwiki/XenDom0Kernels
The recommended dom0 kernel is the pv_ops kernel, which is in the
process of being cleaned up for upstream/mainline Linux inclusion.
More information about pv_ops dom0 kernel, including the status
reports:
http://wiki.xensource.com/xenwiki/XenParavirtOps
Xen developers are interested of both the success and failure reports
when using the Xen pv_ops dom0 kernel.
Tips for running Xen with Fedora 12:
- Make sure you install all the latest Fedora 12 updates, since they
have an updated Xen version (3.4.2), and also fix a bug in
python-virtinst tool to make Xen guest console keymaps work properly:
https://bugzilla.redhat.com/show_bug.cgi?id=533707
- Recent versions of Xen pv_ops dom0 kernel renamed some xen
backend driver modules to have "xen-" prefix in them, for
example evtchn module became xen-evtchn. Fedora Xen 3.4.2 init
scripts take care of this, and load the correct modules, but
Xen 3.4.1 doesn't do this automatically, causing xend fail to
start in dom0/host before the modules are loaded manually.
- There are some upcoming apic-related changes coming in pv_ops
dom0 kernel, which will require a patch to Xen hypervisor.
This patch is not yet included in the Fedora Xen rpms.
The patch will be added to Fedora Xen rpms when the upstream
pv_ops kernel starts to require/use it.
- pv_ops dom0 kernel currently lacks blktap2 support, so using
tap:aio: backend disk image files is not yet possible.
Xen file: backend image files work though.
At the moment it's recommended to use LVM volumes for guest
disks (Xen phy: backend).
- virt-manager seems to work OK on Fedora 12 Xen dom0.
- If you experience problems related to Fedora 12 guests (domU)
kernel crashing (especially related to save/restore/migration),
install the latest Fedora updates to the guest. There has been
a lot of Xen guest related fixes in the upstream Linux recently.
These fixes will appear in Fedora when the kernel gets updated
to include the latest stable upstream fixes.
Hopefully that helps :)
-- Pasi
13 years, 2 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
Fedora virt status
by Justin Forbes
Fedora 13
=========
Feature Submission deadline for F-13 was earlier this week, we have some
exciting new features submitted. As we move towards F-13, we are getting
really close to the Feature Freeze deadline.
F-13 schedule:
2010-02-09 Feature Freeze (12 days)
2010-02-16 Alpha Freeze (19 days)
2010-03-23 Beta (Final Development) Freeze (54 days)
2010-04-29 Compose Release Candidate (91 days)
F12 Virt Preview
================
As was announced before, the virt-preview repository for F12 users wishing
to test out the latest virtualization bits is available. Instructions for
using this repository can be found at:
https://fedoraproject.org/wiki/Virtualization_Preview_Repository
Recent updates in this repository include:
qemu-0.12.2-4:
- Update to 0.12.2 upstream
- Add virtio-console patches from upstream for the F13 VirtioSerial feature
- Remove build dependency on iasl now that we have seabios
Bugs
====
DOOM-O-METER: 216 bugs open 1 week ago, up to 230 now.
We have a lot of work to do!
= Important =
== kernel ==
https://bugzilla.redhat.com/show_bug.cgi?id=545851
KVM/networking-related crash
This is related to guests using IPV6
== kvm ==
https://bugzilla.redhat.com/show_bug.cgi?id=555788
SIGTRAP leakage between separate virtual machines
Patches have been posted for this, and a resolution is coming soon.
https://bugzilla.redhat.com/show_bug.cgi?id=478317
almost 9 thousand syscalls per second while idle
This is believed to be a result of the USB Tablet device, but several
users have noticed high host CPU usage while guests were idle.
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.
https://bugzilla.redhat.com/show_bug.cgi?id=544940
reattach virtio to rhel{5,6} guests will cause qemu-kvm crash
== libvirt ==
https://bugzilla.redhat.com/show_bug.cgi?id=547045
libvirt can generate bogus node device XML
libvirt has a function for escaping XML strings that we clearly forgot to
use here. In addition though we probably need to check where this garbage
is coming from, because in this particular case we probably shouldn't be
including the element at all.
13 years, 4 months
is libvirtd breaking iptables in Fedora 12?
by Daniel Sanabria
Hi All,
I noticed that if I turn on the libvirtd service via chkconfig it ends up
breaking my iptables by adding duplicated rules.
For you to have an idea here's the output of iptables-save -c after a reboot
with libvirtd off:
# Generated by iptables-save v1.4.5 on Mon Jan 25 19:34:39 2010
*nat
:PREROUTING ACCEPT [21:7584]
:POSTROUTING ACCEPT [21:1673]
:OUTPUT ACCEPT [21:1673]
[0:0] -A PREROUTING -d 192.168.0.6/32 -p tcp -m tcp --dport 80 -j DNAT
--to-destination 192.168.122.118
[0:0] -A POSTROUTING -s 192.168.122.0/24 ! -d 192.168.122.0/24 -j MASQUERADE
COMMIT
# Completed on Mon Jan 25 19:34:39 2010
# Generated by iptables-save v1.4.5 on Mon Jan 25 19:34:39 2010
*filter
:INPUT ACCEPT [0:0]
:FORWARD ACCEPT [0:0]
:OUTPUT ACCEPT [105:11066]
[0:0] -A INPUT -i virbr0 -p udp -m udp --dport 53 -j ACCEPT
[0:0] -A INPUT -i virbr0 -p tcp -m tcp --dport 53 -j ACCEPT
[0:0] -A INPUT -i virbr0 -p udp -m udp --dport 67 -j ACCEPT
[0:0] -A INPUT -i virbr0 -p tcp -m tcp --dport 67 -j ACCEPT
[0:0] -A INPUT -i virbr0 -p udp -m udp --dport 53 -j ACCEPT
[0:0] -A INPUT -i virbr0 -p tcp -m tcp --dport 53 -j ACCEPT
[0:0] -A INPUT -i virbr0 -p udp -m udp --dport 67 -j ACCEPT
[0:0] -A INPUT -i virbr0 -p tcp -m tcp --dport 67 -j ACCEPT
[0:0] -A INPUT -i virbr0 -p tcp -m tcp --dport 80 -j ACCEPT
[0:0] -A INPUT -i wlan0 -p tcp -m tcp --dport 80 -j ACCEPT
[41:23909] -A INPUT -m state --state RELATED,ESTABLISHED -j ACCEPT
[0:0] -A INPUT -p icmp -j ACCEPT
[2:120] -A INPUT -i lo -j ACCEPT
[0:0] -A INPUT -p tcp -m state --state NEW -m tcp --dport 22 -j ACCEPT
[0:0] -A INPUT -p tcp -m tcp --dport 11201 -j ACCEPT
[0:0] -A INPUT -p udp -m udp --dport 11201 -j ACCEPT
[36:6884] -A INPUT -j REJECT --reject-with icmp-host-prohibited
[0:0] -A FORWARD -d 192.168.122.0/24 -o virbr0 -m state --state
RELATED,ESTABLISHED -j ACCEPT
[0:0] -A FORWARD -s 192.168.122.0/24 -i virbr0 -j ACCEPT
[0:0] -A FORWARD -i virbr0 -o virbr0 -j ACCEPT
[0:0] -A FORWARD -i wlan0 -o virbr0 -p tcp -m tcp --dport 80 -j ACCEPT
[0:0] -A FORWARD -o virbr0 -j REJECT --reject-with icmp-port-unreachable
[0:0] -A FORWARD -i virbr0 -j REJECT --reject-with icmp-port-unreachable
[0:0] -A FORWARD -j REJECT --reject-with icmp-host-prohibited
COMMIT
# Completed on Mon Jan 25 19:34:39 2010
and this is the output of the same command after a reboot with libvirtd on:
# Generated by iptables-save v1.4.5 on Mon Jan 25 19:46:03 2010
*nat
:PREROUTING ACCEPT [6:965]
:POSTROUTING ACCEPT [50:3703]
:OUTPUT ACCEPT [52:4038]
[0:0] -A PREROUTING -d 192.168.0.6/32 -p tcp -m tcp --dport 80 -j DNAT
--to-destination 192.168.122.118
[1:295] -A POSTROUTING -s 192.168.122.0/24 ! -d 192.168.122.0/24 -j
MASQUERADE
[1:40] -A POSTROUTING -s 192.168.122.0/24 ! -d 192.168.122.0/24 -j
MASQUERADE
COMMIT
# Completed on Mon Jan 25 19:46:03 2010
# Generated by iptables-save v1.4.5 on Mon Jan 25 19:46:03 2010
*filter
:INPUT ACCEPT [0:0]
:FORWARD ACCEPT [0:0]
:OUTPUT ACCEPT [338:37036]
[1:74] -A INPUT -i virbr0 -p udp -m udp --dport 53 -j ACCEPT
[0:0] -A INPUT -i virbr0 -p tcp -m tcp --dport 53 -j ACCEPT
[1:328] -A INPUT -i virbr0 -p udp -m udp --dport 67 -j ACCEPT
[0:0] -A INPUT -i virbr0 -p tcp -m tcp --dport 67 -j ACCEPT
[0:0] -A INPUT -i virbr0 -p udp -m udp --dport 53 -j ACCEPT
[0:0] -A INPUT -i virbr0 -p tcp -m tcp --dport 53 -j ACCEPT
[0:0] -A INPUT -i virbr0 -p udp -m udp --dport 67 -j ACCEPT
[0:0] -A INPUT -i virbr0 -p tcp -m tcp --dport 67 -j ACCEPT
[0:0] -A INPUT -i virbr0 -p udp -m udp --dport 53 -j ACCEPT
[0:0] -A INPUT -i virbr0 -p tcp -m tcp --dport 53 -j ACCEPT
[0:0] -A INPUT -i virbr0 -p udp -m udp --dport 67 -j ACCEPT
[0:0] -A INPUT -i virbr0 -p tcp -m tcp --dport 67 -j ACCEPT
[0:0] -A INPUT -i virbr0 -p tcp -m tcp --dport 80 -j ACCEPT
[0:0] -A INPUT -i wlan0 -p tcp -m tcp --dport 80 -j ACCEPT
[190:99034] -A INPUT -m state --state RELATED,ESTABLISHED -j ACCEPT
[0:0] -A INPUT -p icmp -j ACCEPT
[2:120] -A INPUT -i lo -j ACCEPT
[0:0] -A INPUT -p tcp -m state --state NEW -m tcp --dport 22 -j ACCEPT
[0:0] -A INPUT -p tcp -m tcp --dport 11201 -j ACCEPT
[0:0] -A INPUT -p udp -m udp --dport 11201 -j ACCEPT
[78:13517] -A INPUT -j REJECT --reject-with icmp-host-prohibited
[0:0] -A FORWARD -d 192.168.122.0/24 -o virbr0 -m state --state
RELATED,ESTABLISHED -j ACCEPT
[0:0] -A FORWARD -s 192.168.122.0/24 -i virbr0 -j ACCEPT
[0:0] -A FORWARD -i virbr0 -o virbr0 -j ACCEPT
[0:0] -A FORWARD -o virbr0 -j REJECT --reject-with icmp-port-unreachable
[0:0] -A FORWARD -i virbr0 -j REJECT --reject-with icmp-port-unreachable
[0:0] -A FORWARD -d 192.168.122.0/24 -o virbr0 -m state --state
RELATED,ESTABLISHED -j ACCEPT
[0:0] -A FORWARD -s 192.168.122.0/24 -i virbr0 -j ACCEPT
[0:0] -A FORWARD -i virbr0 -o virbr0 -j ACCEPT
[0:0] -A FORWARD -i wlan0 -o virbr0 -p tcp -m tcp --dport 80 -j ACCEPT
[0:0] -A FORWARD -o virbr0 -j REJECT --reject-with icmp-port-unreachable
[0:0] -A FORWARD -i virbr0 -j REJECT --reject-with icmp-port-unreachable
[0:0] -A FORWARD -j REJECT --reject-with icmp-host-prohibited
COMMIT
# Completed on Mon Jan 25 19:46:03 2010
As you can see when the libvirtd daemon is up I end up with a number of
duplicated entries ...
this is then content of /etc/sysconfig/iptables in both cases:
# Generated by iptables-save v1.4.5 on Thu Jan 21 19:54:46 2010
*nat
:PREROUTING ACCEPT [24306:3491836]
:POSTROUTING ACCEPT [17614:1213585]
:OUTPUT ACCEPT [16779:1092505]
-A PREROUTING -d 192.168.0.6/32 -p tcp -m tcp --dport 80 -j DNAT
--to-destination 192.168.122.118
-A POSTROUTING -s 192.168.122.0/24 ! -d 192.168.122.0/24 -j MASQUERADE
COMMIT
# Completed on Thu Jan 21 19:54:46 2010
# Generated by iptables-save v1.4.5 on Thu Jan 21 19:54:46 2010
*filter
:INPUT ACCEPT [0:0]
:FORWARD ACCEPT [0:0]
:OUTPUT ACCEPT [544711:383016639]
-A INPUT -i virbr0 -p udp -m udp --dport 53 -j ACCEPT
-A INPUT -i virbr0 -p tcp -m tcp --dport 53 -j ACCEPT
-A INPUT -i virbr0 -p udp -m udp --dport 67 -j ACCEPT
-A INPUT -i virbr0 -p tcp -m tcp --dport 67 -j ACCEPT
-A INPUT -i virbr0 -p tcp -m tcp --dport 80 -j ACCEPT
-A INPUT -i wlan0 -p tcp -m tcp --dport 80 -j ACCEPT
-A INPUT -m state --state RELATED,ESTABLISHED -j ACCEPT
-A INPUT -p icmp -j ACCEPT
-A INPUT -i lo -j ACCEPT
-A INPUT -p tcp -m state --state NEW -m tcp --dport 22 -j ACCEPT
-A INPUT -p tcp -m tcp --dport 11201 -j ACCEPT
-A INPUT -p udp -m udp --dport 11201 -j ACCEPT
-A INPUT -j REJECT --reject-with icmp-host-prohibited
-A FORWARD -d 192.168.122.0/24 -o virbr0 -m state --state
RELATED,ESTABLISHED -j ACCEPT
-A FORWARD -s 192.168.122.0/24 -i virbr0 -j ACCEPT
-A FORWARD -i virbr0 -o virbr0 -j ACCEPT
-A FORWARD -i wlan0 -o virbr0 -p tcp -m tcp --dport 80 -j ACCEPT
-A FORWARD -o virbr0 -j REJECT --reject-with icmp-port-unreachable
-A FORWARD -i virbr0 -j REJECT --reject-with icmp-port-unreachable
-A FORWARD -j REJECT --reject-with icmp-host-prohibited
COMMIT
# Completed on Thu Jan 21 19:54:46 2010
Has anyone experienced this? Is there another file that libvirtd uses to
manipulate iptables?
Thanks in advance,
Daniel
13 years, 4 months
virt-manager needs finishing polish
by Valent Turkovic
After posting my initial blog post
(http://kernelreloaded.blog385.com/index.php/archives/fedora-virtualizatio...)
and through discussion in comments and also in reported bugs I saw the
great potential of virt-manager on Fedora as desktop virtualization
tool that could replace likes of VMWare and VirtualBox but it needed
some UI and usability polish.
Please take use case of installing Fedora or Ubuntu in virt-manager as
benchmarks or ease of use for new users. How easy/hard is it to
install Fedora/Ubuntu as virtual machines in virt-manager? Any install
issues? How well do they work? Etc...
I covered some of that in my previously mentioned blog post and came
to some later what would make virt-manager easier to use.
After looking more deeply in virt-manager it UI indeed looks a bit
clunky and assumes you are familiar with the way it works, not user
friendly for new users.
For new users of virt-manager it would be great if somehow more
emphasized in UI is done on explaining that there are these things
called "storage pools" and also that there are two storage pools by
default; one in /var and other in /home directory.
Fedora community has educated me to put any suggestions as
constructive as possible and I did that in two RFEs and hope they are
seeded in fertile soil and that developers see opportunity to improve
usability of virt-manager
Here are two RFEs, please comment on them:
https://bugzilla.redhat.com/show_bug.cgi?id=557103
https://bugzilla.redhat.com/show_bug.cgi?id=557107
Cheers!
--
pratite me na twitteru - www.twitter.com/valentt
http://kernelreloaded.blog385.com/
linux, blog, anime, spirituality, windsurf, wireless
registered as user #367004 with the Linux Counter, http://counter.li.org.
ICQ: 2125241, Skype: valent.turkovic, msn: valent.turkovic(a)hotmail.com
13 years, 4 months
Fedora virt status
by Justin Forbes
Fedora 13
=========
As we move towards F-13, we are getting really close to the Feature
Submission deadline. Planned F-13 features can be seen at
http://fedoraproject.org/wiki/Category:F13_Virt_Features
F-13 schedule:
2010-01-26 Feature Submission Deadline (8 days)
2010-02-09 Feature Freeze (22 days)
2010-02-16 Alpha Freeze (29 days)
2010-03-23 Beta (Final Development) Freeze (64 days)
2010-04-29 Compose Release Candidate (101 days)
Feature status should be updated to reflect current progress sooner rather
than later.
Now that qemu-0.12 has been added for F-13 we need as much testing as
possible. This can be tested by using rawhide, or for those who prefer an
F-12 base, the virt-preview repository will allow you to test.
F12 Virt Preview
================
As was announced before, the virt-preview repository for F12 users wishing
to test out the latest virtualization bits is available. Instructions for
using this repository can be found at:
https://fedoraproject.org/wiki/Virtualization_Preview_Repository
Recent updates in this repository include:
libvirt-0.7.5-3:
- Add new API virDomainMemoryStats
- Public API and domain extension for CPU flags
- vbox: Add support for version 3.1
- Support QEMU's virtual FAT block device driver
- a lot of fixes
libvirt-java-0.4.1-1:
- Better null checking around Scheduled Parameters
- Added error function callback
qemu-0.12.1.2-3:
- Point to seabios instead of bochs, and add a requires for seabios
- Update to 0.12.1.2 upstream
- Remove patches included in upstream
seabios-0.5.1-0.1.20100108git669c991:
- Initial seabios package
* Required for qemu-0.12 and newer.
virt-manager-0.8.2-2:
- Build with actual upstream tarball (not manually built dist)
virt-viewer-0.2.1-1:
- Update to 0.2.1 release
Bugs
====
DOOM-O-METER: 211 bugs open 4 weeks ago, up to 216 now.
We have a lot of work to do!
= Important =
== kernel ==
https://bugzilla.redhat.com/show_bug.cgi?id=545851
KVM/networking-related crash
This is related to guests using IPV6
== kvm ==
https://bugzilla.redhat.com/show_bug.cgi?id=555788
SIGTRAP leakage between separate virtual machines
https://bugzilla.redhat.com/show_bug.cgi?id=546483
buffer overflow in usb-linux.c
Patch included, this will require an updated 0.11 push for F-12.
https://bugzilla.redhat.com/show_bug.cgi?id=478317
almost 9 thousand syscalls per second while idle
This is believed to be a result of the USB Tablet device, but several
users have noticed high host CPU usage while guests were idle.
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.
https://bugzilla.redhat.com/show_bug.cgi?id=544940
reattach virtio to rhel{5,6} guests will cause qemu-kvm crash
Reattaching virtio storage to a guest is causing host crashes.
== libvirt ==
https://bugzilla.redhat.com/show_bug.cgi?id=547045
libvirt can generate bogus node device XML
libvirt has a function for escaping XML strings that we clearly forgot to
use here. In addition though we probably need to check where this garbage
is coming from, because in this particular case we probably shouldn't be
including the element at all.
13 years, 4 months
is there a best clock to use?
by Tom Horsley
Is there a HOWTO anywhere of the different ways to
make time of day clock work in virtual machines and different
ways to influence it from the qemu side of the world?
Time keeping is horrible in most of my virtual machines,
and I just wonder if there are settings I can change
in libvirt or kernel boot parameters I can apply in
the linux guest to make things slightly less horrible?
Sometimes I get the impression that the guest time is
already two or three minutes off as soon as it is
booted, and I can't imagine how that happens since I
would assume it gets a copy of the host machine time
for the emulated rtc clock in the guest. How can it
already be broken at boot time?
13 years, 4 months
Cloned machine has no network
by John Poelstra
I'm running virt-manager on Fedora 12. I selected the option to 'clone'
a machine from the menu. The clone process worked great (mostly) and
the cloned machine boots fine.
On the cloned machine the network card no longer works and trying to
start eth0 returns an error message about the device not being present.
I gave the virtual machine a new nic, hoping that might solve the
problem but I can't figure out how to configure it using command line
tools. 'lspci' shows that it is present. I tried setuptools, but the
changes didn't seem to take.
I'm running a really bare bones guest with no X.
Suggestions on how to move forward?
Thanks,
John
13 years, 4 months
libvirtd fails to start after upgrading to virt-preview
by Vinu Moses
Hello
After upgrading to the virt-preview repository yesterday, I am unable to get
libvirtd started. /var/log/messages gives the following errors:
Jan 16 14:25:26 vinu libvirtd: 14:25:26.816: error : udevSetupSystemDev:1409 :
Failed to get udev device for syspath '
/sys/devices/virtual/dmi/id'#012
Jan 16 14:25:26 vinu libvirtd: 14:25:26.816: error : virStateInitialize:890 :
Initialization of (null) state driver failed
Jan 16 14:25:26 vinu kernel: libvirtd[4321]: segfault at 38 ip
000000000047d1df sp 00007f76f5f18840 error 4 in libvirtd[400000+a6000]
Jan 16 14:25:26 vinu kernel: Process 4320(libvirtd) has RLIMIT_CORE set to 0
Jan 16 14:25:26 vinu kernel: Aborting core
I'm running f12 x86_64 with all updates applied to date, with a 2.6.32.3
kernel from kernel.org.
Would be grateful for any help to rectify this.
Thank you in advance.
--Vinu.
13 years, 4 months