| |
|
 |
|
 |
|
|
|
| |
|
|
xen-users
Re: [Xen-users] Xen Installation without virtualization enabled in Bios
Two things come to mind:
1. I'm not sure that the script you wrote will work correctly as-is.
Perhaps someone else would like to chime in on this, since my bash
skills aren't great, but here's the usage info from the default
network-bridge script:
# Usage:
#
# network-bridge (start|stop|status) {VAR=VAL}*
#
# Vars:
#
# bridge The bridge to use (default ${netdev}).
# netdev The interface to add to the bridge (default gateway
device).
# antispoof Whether to use iptables to prevent spoofing (default no).
#
# Internal Vars:
# pdev="p${netdev}"
# tdev=tmpbridge
#
# start:
# Creates the bridge as tdev
# Copies the IP and MAC addresses from pdev to bridge
# Renames netdev to be pdev
# Renames tdev to bridge
# Enslaves pdev to bridge
#
# stop:
# Removes pdev from the bridge
# Transfers addresses, routes from bridge to pdev
# Renames bridge to tdev
# Renames pdev to netdev
# Deletes tdev
#
# status:
# Print addresses, interfaces, routes
Based on the description above, I don't think that you're passing the
correct variables to the script.
2. You mentioned that the DomU was able to ping the Dom0, but not the
outside world. You might want to check a few basic network things,
such as:
- running
brctl show to make sure that the bridges
are being created correctly.
- running
route from within the DomU to make sure
that it's gateway and subnet are set up correctly.
HTH
|
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
|
|
|
| |
|
Home