4:21 p.m.
I'm working on getting QEMU running with libvirt and virt-manager and have thus far
had no success. I chose QEMU because it didn't require CPU support for
full-virtualization (I got a bit older CPUs).
Now I'm at a stand-still trying to get it running. My libvirt is compiled with QEMU
support, but I'm getting a "virConnectOpenReadOnly() failed error when it tries
to connect the the hypervisor. A couple questions:
1) How do I start qemu as a service? I actually have 6 guests running.
2) How do I connect from libvirt to qemu? (either running or not).
Could someone who's already been there give me a little libvirt/qemu tutorial?
Thanks, smoyer
--
Steven W. Moyer
Principle Architect, Assurance Applications
C-COR Solutions, LLC
60 Decibel Road
State College, PA 16801
Office Phone: 814-231-4408
Front Desk: 814-238-2461
Cell Phone: 814-883-0391
Fax: 814-278-6540
E-mail: smoyer(a)c-cor.com
AIM: StevenWMoyer
ICQ: 349680381
Jabber: smoyer1(a)jabber.jcware.org
MSN: smoyer64
Yahoo: smoyer64
4:48 a.m.
Steven W. Moyer wrote:
I'm working on getting QEMU running with libvirt and virt-manager
and have thus far had no success. I chose QEMU because it didn't require CPU support
for full-virtualization (I got a bit older CPUs).
Now I'm at a stand-still trying to get it running. My libvirt is compiled with QEMU
support, but I'm getting a "virConnectOpenReadOnly() failed error when it tries
to connect the the hypervisor. A couple questions:
1) How do I start qemu as a service? I actually have 6 guests running.
2) How do I connect from libvirt to qemu? (either running or not).
Is there a process called libvirt_qemud running?
Rich.
--
Emerging Technologies, Red Hat - http://et.redhat.com/~rjones/
Registered Address: Red Hat UK Ltd, Amberley Place, 107-111 Peascod
Street, Windsor, Berkshire, SL4 1TE, United Kingdom. Registered in
England and Wales under Company Registration No. 03798903
7:56 a.m.
Thanks Rich!
It was running, but not as a system daemon (I'm not even really sure how it started).
Now I can manage QEMU guests with virt-manager ... I'm still working on the network
(seem to be missing a package that allows virtual bridging).
I'm also working on a end-to-end full virtualization how-to (since in total, I believe
this to be much better than VMware). Would anyone be interested in providing feedback for
it?
ciao, smoyer
On Wednesday 16 May 2007 05:48, Richard W.M. Jones wrote:
Is there a process called libvirt_qemud running?
Rich.
--
Steven W. Moyer
Principle Architect, Assurance Applications
C-COR Solutions, LLC
60 Decibel Road
State College, PA 16801
Office Phone: 814-231-4408
Front Desk: 814-238-2461
Cell Phone: 814-883-0391
Fax: 814-278-6540
E-mail: smoyer(a)c-cor.com
AIM: StevenWMoyer
ICQ: 349680381
Jabber: smoyer1(a)jabber.jcware.org
MSN: smoyer64
Yahoo: smoyer64
8:01 a.m.
Steven W. Moyer wrote:
Thanks Rich!
It was running, but not as a system daemon (I'm not
even really sure how it started).
If you are using the CVS version then there is much more help given in
the output of libvirt_qemud --help, including paths to where it thinks
all the communication sockets should be.
Now I can manage QEMU
guests with virt-manager ... I'm still working on
the network (seem to be missing a package that allows
virtual bridging).
Do you get an error message?
I'm also working on a end-to-end full virtualization
how-to (since in total, I believe this to be much better
than VMware). Would anyone be interested in providing
feedback for it?
Yes, if you send it here I'll be happy to give you feedback.
Rich.
--
Emerging Technologies, Red Hat - http://et.redhat.com/~rjones/
Registered Address: Red Hat UK Ltd, Amberley Place, 107-111 Peascod
Street, Windsor, Berkshire, SL4 1TE, United Kingdom. Registered in
England and Wales under Company Registration No. 03798903
8:11 a.m.
Thanks Rich!
Do you get an error message?
Yes ... it's "Failed to autostart network 'default': cannot create bridge
'virbr0' : Package not installed"
With "libvirt_qemud --help" I do see that the sockets should be in
"/var/lib/run/libvirt/". They appear to be in place (and the permissions are
what I would expect for system-daemon mode):
smoyernew images # ls -al /var/lib/run/libvirt/
total 0
drwxr-xr-x 2 root root 112 May 16 08:54 .
drwxr-xr-x 3 root root 72 May 14 16:39 ..
srw------- 1 root root 0 May 16 08:54 qemud-sock
srw-rw-rw- 1 root root 0 May 16 08:54 qemud-sock-ro
smoyernew images #
Rich.
--
Steven W. Moyer
Principle Architect, Assurance Applications
C-COR Solutions, LLC
60 Decibel Road
State College, PA 16801
Office Phone: 814-231-4408
Front Desk: 814-238-2461
Cell Phone: 814-883-0391
Fax: 814-278-6540
E-mail: smoyer(a)c-cor.com
AIM: StevenWMoyer
ICQ: 349680381
Jabber: smoyer1(a)jabber.jcware.org
MSN: smoyer64
Yahoo: smoyer64
8:28 a.m.
Steven W. Moyer wrote:
Thanks Rich!
> Do you get an error message?
>
Yes ... it's "Failed to autostart network 'default': cannot create
bridge 'virbr0' : Package not installed"
That's an odd one.
It seems to come from here in the qemud code:
if ((err = brAddBridge(server->brctl, name, network->bridge,
sizeof(network-
bridge)))) {
qemudReportError(server,
VIR_ERR_INTERNAL_ERROR,
"cannot create bridge '%s' : %s", name,
strerror(err));
return -1;
}
Can you please strace the process and post it?
Something like:
strace -o /tmp/log -s 1024 -f libvirt_qemud [any usual flags]
Rich.
--
Emerging Technologies, Red Hat - http://et.redhat.com/~rjones/
Registered Address: Red Hat UK Ltd, Amberley Place, 107-111 Peascod
Street, Windsor, Berkshire, SL4 1TE, United Kingdom. Registered in
England and Wales under Company Registration No. 03798903
8:43 a.m.
Richard W.M. Jones wrote:
Steven W. Moyer wrote:
> Thanks Rich!
>
>> Do you get an error message?
>>
>
> Yes ... it's "Failed to autostart network 'default': cannot create
> bridge 'virbr0' : Package not installed"
That's an odd one.
So the particular error (Package not install / ENOPKG) seems to happen
when the kernel cannot request the bridge.ko kernel module to be loaded.
It seems like that either you don't have this module, or else
something in your /etc/modprobe.conf or /etc/modprobe.d/* is confusing
or preventing the module from being loaded.
You might try: modprobe bridge.ko and see if it gives any errors.
Rich.
--
Emerging Technologies, Red Hat - http://et.redhat.com/~rjones/
Registered Address: Red Hat UK Ltd, Amberley Place, 107-111 Peascod
Street, Windsor, Berkshire, SL4 1TE, United Kingdom. Registered in
England and Wales under Company Registration No. 03798903
9:19 a.m.
Yep ... I was headed that direction too. It turns out that I don't have a bridging
kernel module at all (that might do it). The word package threw me and I ran around
making sure that I had the bridge-utils package installed (I did), but there's nothing
for it to work with:)
Thanks again for the help!
smoyer
On Wednesday 16 May 2007 09:43, Richard W.M. Jones wrote:
Richard W.M. Jones wrote:
> Steven W. Moyer wrote:
>> Thanks Rich!
>>
>>> Do you get an error message?
>>>
>>
>> Yes ... it's "Failed to autostart network 'default': cannot
create
>> bridge 'virbr0' : Package not installed"
>
> That's an odd one.
So the particular error (Package not install / ENOPKG) seems to happen
when the kernel cannot request the bridge.ko kernel module to be loaded.
It seems like that either you don't have this module, or else
something in your /etc/modprobe.conf or /etc/modprobe.d/* is confusing
or preventing the module from being loaded.
You might try: modprobe bridge.ko and see if it gives any errors.
Rich.
--
Steven W. Moyer
Principle Architect, Assurance Applications
C-COR Solutions, LLC
60 Decibel Road
State College, PA 16801
Office Phone: 814-231-4408
Front Desk: 814-238-2461
Cell Phone: 814-883-0391
Fax: 814-278-6540
E-mail: smoyer(a)c-cor.com
AIM: StevenWMoyer
ICQ: 349680381
Jabber: smoyer1(a)jabber.jcware.org
MSN: smoyer64
Yahoo: smoyer64
12:15 p.m.
Rich:
It was definitely missing bridge ... now that it's loaded, I'm still getting and
error related to iptables (I've also loaded the ebtables kernel module). Which kernel
modules are required for bridged networking?
thanks again, smoyer
BTW: Here's the error I'm getting now ...
FATAL: Module ip_tables not found.
iptables v1.3.5: can't initialize iptables table `filter': iptables who? (do you
need to insmod?)
Perhaps iptables or your kernel needs to be upgraded.
Failed to autostart network 'default': failed to add iptables rule to allow DHCP
requests from 'virbr0' : Invalid argument
You might try: modprobe bridge.ko and see if it gives any errors.
Rich.
--
Steven W. Moyer
Principle Architect, Assurance Applications
C-COR Solutions, LLC
60 Decibel Road
State College, PA 16801
Office Phone: 814-231-4408
Front Desk: 814-238-2461
Cell Phone: 814-883-0391
Fax: 814-278-6540
E-mail: smoyer(a)c-cor.com
AIM: StevenWMoyer
ICQ: 349680381
Jabber: smoyer1(a)jabber.jcware.org
MSN: smoyer64
Yahoo: smoyer64
12:21 p.m.
On Wed, May 16, 2007 at 01:15:50PM -0400, Steven W. Moyer wrote:
Rich:
It was definitely missing bridge ... now that it's loaded, I'm still getting and
error related to iptables (I've also loaded the ebtables kernel module). Which kernel
modules are required for bridged networking?
thanks again, smoyer
BTW: Here's the error I'm getting now ...
FATAL: Module ip_tables not found.
^^^^^^^^^^^^^^^^
Make sure you have the iptables modules for your kernel. At the very
least we use the filter & nat tables, and the state module for
connection tracking.
Dan.
--
|=- Red Hat, Engineering, Emerging Technologies, Boston. +1 978 392 2496 -=|
|=- Perl modules: http://search.cpan.org/~danberr/ -=|
|=- Projects: http://freshmeat.net/~danielpb/ -=|
|=- GnuPG: 7D3B9505 F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 -=|
8:39 a.m.
Thanks Dan! I was indeed missing some modules (I just switched to the 2.6.20 kernel
series and didn't find a couple of the necessary switches in menuconfig). I'm
still having problems with the networking.
If I try to start libvirt_qemud without have the bridge defined, I get this error:
smoyernew images # libvirt_qemud --system
iptables: Invalid argument
Failed to autostart network 'default': failed to add iptables rule to allow
forwarding to 'virbr0' : Invalid argument
If I create virbr0 and then start libvirt_qemud, I get this error:
smoyernew images # libvirt_qemud --system
Failed to autostart network 'default': cannot create bridge 'virbr0' :
File exists
In any case, the guest domains don't end up with connectivity through the bridge. I
think I'm missing something basic, but it's been a while since I used iptables for
anything.
I also have one error that I'm trying to track down from virt-manager's GUI. I
seem to have something misconfigured with GTK and dbus:
(virt-manager.py:5482): Gdk-WARNING **: Connection to display localhost:10.0 appears to be
untrusted. Pointer and keyboard grabs and inter-client communication may not work as
expected.
libvir: QEMU error : internal error cannot create bridge 'virbr0' : File exists
Traceback (most recent call last):
File "/usr/share/virt-manager/virtManager/host.py", line 117, in
start_network
net.start()
File "/usr/share/virt-manager/virtManager/network.py", line 64, in start
self.net.create()
File "/usr/lib/python2.4/site-packages/libvirt.py", line 402, in create
if ret == -1: raise libvirtError ('virNetworkCreate() failed', net=self)
libvirt.libvirtError: virNetworkCreate() failed internal error cannot create bridge
'virbr0' : File exists
/usr/share/virt-manager/virt-manager.py:242: GtkWarning: Coercing GDK_INPUT_ONLY toplevel
window to GDK_INPUT_OUTPUT to work around bug in Xorg server
gtk.main()
process 5482: D-Bus library appears to be incorrectly set up; failed to read machine uuid:
Failed to open "/var/lib/dbus/machine-id": No such file or directory
See the manual page for dbus-uuidgen to correct this issue.
D-Bus not built with -rdynamic so unable to print a backtrace
Thanks again for all the help!
smoyer
Make sure you have the iptables modules for your kernel. At the very
least we use the filter & nat tables, and the state module for
connection tracking.
--
Steven W. Moyer
Principle Architect, Assurance Applications
C-COR Solutions, LLC
60 Decibel Road
State College, PA 16801
Office Phone: 814-231-4408
Front Desk: 814-238-2461
Cell Phone: 814-883-0391
Fax: 814-278-6540
E-mail: smoyer(a)c-cor.com
AIM: StevenWMoyer
ICQ: 349680381
Jabber: smoyer1(a)jabber.jcware.org
MSN: smoyer64
Yahoo: smoyer64
11:02 a.m.
Steven W. Moyer wrote:
In any case, the guest domains don't end up with connectivity
through the bridge. I think I'm missing something basic, but it's been a while
since I used iptables for anything.
What does 'brctl show' say?
I also have one error that I'm trying to track down from
virt-manager's GUI. I seem to have something misconfigured with GTK and dbus:
(virt-manager.py:5482): Gdk-WARNING **: Connection to display localhost:10.0 appears to
be untrusted. Pointer and keyboard grabs and inter-client communication may not work as
expected.
Try 'ssh -Y' instead of 'ssh -X'
libvir: QEMU error : internal error cannot create bridge
'virbr0' : File exists
This is probably non-fatal.
process 5482: D-Bus library appears to be incorrectly set up; failed
to read machine uuid: Failed to open "/var/lib/dbus/machine-id": No such file or
directory
See the manual page for dbus-uuidgen to correct this issue.
D-Bus not built with -rdynamic so unable to print a backtrace
DBus is only used (I think) if you do things like inserting a new CD
during the create dialogs. In any case DBus also fails here without any
apparent ill-effects.
Rich.
--
Emerging Technologies, Red Hat - http://et.redhat.com/~rjones/
Registered Address: Red Hat UK Ltd, Amberley Place, 107-111 Peascod
Street, Windsor, Berkshire, SL4 1TE, United Kingdom. Registered in
England and Wales under Company Registration No. 03798903
11:47 a.m.
Rich:
What does 'brctl show' say?
In the normal case, I believe that libvirt_qemud should create virbr0 and then add a rule
to iptables that forwards through the bridge. In this case, brctl show does not list any
bridges.
Try 'ssh -Y' instead of 'ssh -X'
This did eliminate the warning on virt-manager startup but...
This is probably non-fatal.
If I create virbr0 with brctl, then I can actually start a guest domain. If I click on
anything in that window, virt-manager and all child windows crash with this error.
Thanks for tolerating my long barrage of problems:)
ciao, smoyer
--
Steven W. Moyer
Principle Architect, Assurance Applications
C-COR Solutions, LLC
60 Decibel Road
State College, PA 16801
Office Phone: 814-231-4408
Front Desk: 814-238-2461
Cell Phone: 814-883-0391
Fax: 814-278-6540
E-mail: smoyer(a)c-cor.com
AIM: StevenWMoyer
ICQ: 349680381
Jabber: smoyer1(a)jabber.jcware.org
MSN: smoyer64
Yahoo: smoyer64
11:56 a.m.
On Thu, May 17, 2007 at 12:47:11PM -0400, Steven W. Moyer wrote:
Rich:
> What does 'brctl show' say?
In the normal case, I believe that libvirt_qemud should create virbr0 and then add a rule
to iptables that forwards through the bridge. In this case, brctl show does not list any
bridges.
Yes, libvirt_qemud should be the only one creating the virbr0 device,
since it needs to track the device state & iptables state wrt to the
guest networking setup.
> Try 'ssh -Y' instead of 'ssh -X'
This did eliminate the warning on virt-manager startup but...
> This is probably non-fatal.
If I create virbr0 with brctl, then I can actually start a guest
domain. If I click on anything in that window, virt-manager and
all child windows crash with this error.
What is the error ? Is there anything in /root/.virt-manager/virt-manager.log
after the crash.
Regards,
Dan.
--
|=- Red Hat, Engineering, Emerging Technologies, Boston. +1 978 392 2496 -=|
|=- Perl modules: http://search.cpan.org/~danberr/ -=|
|=- Projects: http://freshmeat.net/~danielpb/ -=|
|=- GnuPG: 7D3B9505 F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 -=|
2:19 p.m.
Gents:
I finally got the networking figured out (had to add a couple more modules to satisfy
libvirt_qemud). Here's a list of the modules I'm loading for virtualization -
Does it look about right?:
smoyernew images # lsmod
Module Size Used by
ipt_MASQUERADE 2176 1
iptable_nat 4228 1
nf_nat 9516 2 ipt_MASQUERADE,iptable_nat
nf_conntrack_ipv4 7436 3 iptable_nat
xt_state 1920 1
nf_conntrack 28040 5
ipt_MASQUERADE,iptable_nat,nf_nat,nf_conntrack_ipv4,xt_state
ipt_REJECT 3072 2
xt_tcpudp 2816 4
rtc 7216 1
iptable_filter 2048 1
ip_tables 7652 2 iptable_nat,iptable_filter
x_tables 6660 6
ipt_MASQUERADE,iptable_nat,xt_state,ipt_REJECT,xt_tcpudp,ip_tables
bridge 29720 0
kqemu 119460 1
tun 5376 1
What is the error ? Is there anything in
/root/.virt-manager/virt-manager.log
after the crash.
This hasn't solved the problem with virt-manager (and children) crashing when I click
in a child window (just DSL for now). The error messages are a bit cleaner now that the
networking issue if fixed (and I guess we know they're not related). Here's what
shows up on the console:
smoyernew images # virt-manager
process 5225: D-Bus library appears to be incorrectly set up; failed to read machine uuid:
Failed to open "/var/lib/dbus/machine-id": No such file or directory
See the manual page for dbus-uuidgen to correct this issue.
D-Bus not built with -rdynamic so unable to print a backtrace
Aborted
and here's what's in the log file:
Thu, 17 May 2007 15:14:11 WARNING No support for gnome-keyring
Thu, 17 May 2007 15:14:11 ERROR Unable to connect to HAL to list network devi
ces: '%s'dbus.DBusException org.freedesktop.DBus.Error.FileNotFound: Failed to c
onnect to socket /var/run/dbus/system_bus_socket: No such file or directory
Traceback (most recent call last):
File "/usr/share/virt-manager/virtManager/connection.py", line 93, in
detect_n
etwork_devices
self.bus = dbus.SystemBus()
File "//usr/lib/python2.4/site-packages/dbus/_dbus.py", line 652, in __new__
private=private)
File "//usr/lib/python2.4/site-packages/dbus/_dbus.py", line 293, in __new__
mainloop=mainloop)
DBusException: org.freedesktop.DBus.Error.FileNotFound: Failed to connect to soc
ket /var/run/dbus/system_bus_socket: No such file or directory
Thu, 17 May 2007 15:14:11 WARNING Unable to resolve local hostname for machine
Thu, 17 May 2007 15:14:19 DEBUG Graphics console configured at vnc://127.0.0.
1:5900
Thu, 17 May 2007 15:14:19 DEBUG Graphics console configured at vnc://127.0.0.
1:5900
Since I don't have hal on this machine, I think I'll install it and then retry.
Thanks again for all the help!
smoyer
--
Steven W. Moyer
Principle Architect, Assurance Applications
C-COR Solutions, LLC
60 Decibel Road
State College, PA 16801
Office Phone: 814-231-4408
Front Desk: 814-238-2461
Cell Phone: 814-883-0391
Fax: 814-278-6540
E-mail: smoyer(a)c-cor.com
AIM: StevenWMoyer
ICQ: 349680381
Jabber: smoyer1(a)jabber.jcware.org
MSN: smoyer64
Yahoo: smoyer64
2:25 p.m.
On Thu, May 17, 2007 at 03:19:33PM -0400, Steven W. Moyer wrote:
> What is the error ? Is there anything in
/root/.virt-manager/virt-manager.log
> after the crash.
This hasn't solved the problem with virt-manager (and children) crashing when I click
in a child window (just DSL for now). The error messages are a bit cleaner now that the
networking issue if fixed (and I guess we know they're not related). Here's what
shows up on the console:
smoyernew images # virt-manager
process 5225: D-Bus library appears to be incorrectly set up; failed to read machine
uuid: Failed to open "/var/lib/dbus/machine-id": No such file or directory
See the manual page for dbus-uuidgen to correct this issue.
D-Bus not built with -rdynamic so unable to print a backtrace
Aborted
The word 'Aborted' is the key there. We call the DBus library, but it
is hitting a fatal error during its initialization & aborting the entire
process. That's not something we can work around in virt-manager :-(
Really need to figure out why dbus isn't setup correctly on this
machine. On Fedora systems that directory is created automatically by
the RPM install
$ rpm -qf /var/lib/dbus/
dbus-1.0.1-12.fc6
Dan.
--
|=- Red Hat, Engineering, Emerging Technologies, Boston. +1 978 392 2496 -=|
|=- Perl modules: http://search.cpan.org/~danberr/ -=|
|=- Projects: http://freshmeat.net/~danielpb/ -=|
|=- GnuPG: 7D3B9505 F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 -=|
3:28 p.m.
It didn't abort during initialization ... it aborted when I clicked on the VNC
(I'm assuming) window. In the log file, the error first occurs with the call to hald
(which wasn't installed on this system).
Once I installed hal, this problem cleared up (I guess that's one to put in the
troubleshooting guide huh?). The screen grabs work perfectly:)
Now I just need to finish my networking on the host side and I'll be all set (any
hints?).
BTW: My target is RHEL5, but I'm using a lot of software that doesn't have RPMs
yet, so I'm working this all out on Gentoo. As I mentioned before, I'm also going
to write up a comprehensive how-to.
I'm using the system to test installation scripts. One of the things that would be
very handy is the ability to copy a guest (image file, configuration, etc.). It could use
the same wizard that's used to create a new guest, with everything already filled in
(except a couple obvious fields).
Once I have some of this running, I'll dig into the Python code for virt-manager a bit
... I should be able to add a few enhancements myself.
Thanks again, smoyer
On Thursday 17 May 2007 15:25, Daniel P. Berrange wrote:
On Thu, May 17, 2007 at 03:19:33PM -0400, Steven W. Moyer wrote:
> > What is the error ? Is there anything in /root/.virt-manager/virt-manager.log
> > after the crash.
>
> This hasn't solved the problem with virt-manager (and children) crashing when I
click in a child window (just DSL for now). The error messages are a bit cleaner now that
the networking issue if fixed (and I guess we know they're not related). Here's
what shows up on the console:
>
> smoyernew images # virt-manager
> process 5225: D-Bus library appears to be incorrectly set up; failed to read machine
uuid: Failed to open "/var/lib/dbus/machine-id": No such file or directory
> See the manual page for dbus-uuidgen to correct this issue.
> D-Bus not built with -rdynamic so unable to print a backtrace
> Aborted
The word 'Aborted' is the key there. We call the DBus library, but it
is hitting a fatal error during its initialization & aborting the entire
process. That's not something we can work around in virt-manager :-(
Really need to figure out why dbus isn't setup correctly on this
machine. On Fedora systems that directory is created automatically by
the RPM install
$ rpm -qf /var/lib/dbus/
dbus-1.0.1-12.fc6
Dan.
--
Steven W. Moyer
Principle Architect, Assurance Applications
C-COR Solutions, LLC
60 Decibel Road
State College, PA 16801
Office Phone: 814-231-4408
Front Desk: 814-238-2461
Cell Phone: 814-883-0391
Fax: 814-278-6540
E-mail: smoyer(a)c-cor.com
AIM: StevenWMoyer
ICQ: 349680381
Jabber: smoyer1(a)jabber.jcware.org
MSN: smoyer64
Yahoo: smoyer64
4:30 p.m.
On Thu, May 17, 2007 at 04:28:10PM -0400, Steven W. Moyer wrote:
It didn't abort during initialization ... it aborted when I
clicked on
the VNC (I'm assuming) window. In the log file, the error first occurs
with the call to hald (which wasn't installed on this system).
Once I installed hal, this problem cleared up (I guess that's one to
put in the troubleshooting guide huh?). The screen grabs work perfectly:)
I think HAL/dbus is already listed in the pre-requisites for install, but
I'll check.
Now I just need to finish my networking on the host side and I'll
be all
set (any hints?).
Well there are two ways to do networking
- Virtual networking - this is the libvirt virbr0 device. It set up
a bridge device to which guests attach. It provides DNS & DHCP and
does NAT to whatever your real LAN is. This is nice if you using
laptops (or other machines with dynamic networking / NetworkManager)
since it 'just works' if you switch between LAN / WLAN.
- Shared physical device - this case you have a bridge which has your
real physical device also enslaved. If a guest connects to this
bridge, then it has full connectivity to the LAN. Disadvantage is
that this doesn't play nice with many Wifi cards, or if you switch
between active devices.
I'm using the system to test installation scripts. One of the
things
that would be very handy is the ability to copy a guest (image file,
configuration, etc.). It could use the same wizard that's used to
create a new guest, with everything already filled in (except a couple
obvious fields).
Two ideas which may be of interest there...
- Fujitsu just contributed a additional tool called 'virt-clone'
which lets you clone a pre-installed system - its config and
disks, automatically changing things which need to be kept unique
like UUID, MAC addr, etc.
- The virt-install tool provides identical capabilities to the
virt-manager wizard, in a command line tool, so you can easily
script the kick off of 'from scratch' distro installs.
Regards,
Dan.
--
|=- Red Hat, Engineering, Emerging Technologies, Boston. +1 978 392 2496 -=|
|=- Perl modules: http://search.cpan.org/~danberr/ -=|
|=- Projects: http://freshmeat.net/~danielpb/ -=|
|=- GnuPG: 7D3B9505 F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 -=|
11:54 a.m.
On Thu, May 17, 2007 at 09:39:01AM -0400, Steven W. Moyer wrote:
Thanks Dan! I was indeed missing some modules (I just switched to
the 2.6.20 kernel series and didn't find a couple of the necessary switches in
menuconfig). I'm still having problems with the networking.
If I try to start libvirt_qemud without have the bridge defined, I get this error:
smoyernew images # libvirt_qemud --system
iptables: Invalid argument
Failed to autostart network 'default': failed to add iptables rule to allow
forwarding to 'virbr0' : Invalid argument
This indicates that iptables failed to add the stateful forwarding
rules, eg this rule
Chain FORWARD (policy ACCEPT 0 packets, 0 bytes)
pkts bytes target prot opt in out source destination
0 0 ACCEPT all -- * virbr0 0.0.0.0/0 192.168.122.0/24
state RELATED,ESTABLISHED
This says you're still missing some iptables kernel moodules.
nf_conntrack_ipv4
nf_conntrack
Are the relevant ones i believe.
If I create virbr0 and then start libvirt_qemud, I get this error:
smoyernew images # libvirt_qemud --system
Failed to autostart network 'default': cannot create bridge 'virbr0' :
File exists
Yep, manually creating virbr0 is a really bad idea & will ultimately
not work, because you still need the iptables rules which were failing
above.
Dan.
--
|=- Red Hat, Engineering, Emerging Technologies, Boston. +1 978 392 2496 -=|
|=- Perl modules: http://search.cpan.org/~danberr/ -=|
|=- Projects: http://freshmeat.net/~danielpb/ -=|
|=- GnuPG: 7D3B9505 F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 -=|
12:09 p.m.
Dan:
This says you're still missing some iptables kernel moodules.
nf_conntrack_ipv4
nf_conntrack
Yep ... nf_conntrack wasn't loaded and nf_conntrack_ipv4 wasn't built. I'll
rebuild the kernel modules and make another go at it!
Thanks again, smoyer
--
Steven W. Moyer
Principle Architect, Assurance Applications
C-COR Solutions, LLC
60 Decibel Road
State College, PA 16801
Office Phone: 814-231-4408
Front Desk: 814-238-2461
Cell Phone: 814-883-0391
Fax: 814-278-6540
E-mail: smoyer(a)c-cor.com
AIM: StevenWMoyer
ICQ: 349680381
Jabber: smoyer1(a)jabber.jcware.org
MSN: smoyer64
Yahoo: smoyer64
6399
days inactive
6402
days old
19 comments
3 participants
participants (3)
-
Daniel P. Berrange -
Richard W.M. Jones -
Steven W. Moyer