Hi,
Thanks for telling me. The point is that I can't see the vif0.0, peth0 that kinds of interface when I used the original driver.
Here is the original problem that I have and I posted it yesterday.
After I upgrade the driver, I don't have that issue.
I found that only one user has the same problem as me.
My network adapter is 80003ES2 and my OS is opensuse 10.3.
Any information is appreciated. Thank you.
Regards,
- Tommy
Hi,
I am still stuck with the network problem.
I searched the archive of maling list and found an user has the same problem.
http://lists.xensource.com/archives/html/xen-users/2007-08/msg00839.html
And the reply suggests to execute "ethtool -K eth0 tx off "
When I executed it, nothing happens. Should I execute this command at boot time?
How can I do that?
So I didn't get the answer from that thread.
Here is my output of ifconfig:
eth0 Link encap:Ethernet HWaddr 00:30:48:63:72:76
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:9624 errors:0 dropped:0 overruns:0 frame:0
TX packets:4042 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:3466249 (3.3 Mb) TX bytes:799201 (780.4 Kb)
Base address:0x2000 Memory:d8020000-d8040000
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:150 errors:0 dropped:0 overruns:0 frame:0
TX packets:150 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:10904 (10.6 Kb) TX bytes:10904 (10.6 Kb)
xenbr0 Link encap:Ethernet HWaddr 00:30:48:63:72:76
inet addr:143.215.206.12 Bcast:143.215.207.255 Mask:25Actually, I want to make domains can communicate with each other, suck like uploading files to another domain. I really don't know how to achieve this without bridging.5.255.252.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:5626 errors:0 dropped:0 overruns:0 frame:0
TX packets:2024 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0Actually, I want to make domains can communicate with each other, suck like uploading files to another domain. I really don't know how to achieve this without bridging.
RX bytes:1621821 (1.5 Mb) TX bytes:399985 (390.6 Kb)
As you can see, no peth0 and vif0.0.
The output of brctl show
bridge name bridge id STP enabled interfaces
xenbr0 8000.003048637276 no eth0
No vif interface.
Does anyone have the same problem?
This problem is quite annoying.
Actually, I want to make domains can communicate with each other, suck like uploading files from Dom 0 to Dom 1. I really don't know how to achieve this without bridging.
If you have any workaround solution, please kindly let me know.
I have to use opensuse 10.3 with xen. No other limitations.
Any response is appreciated. Thanks again.
From: lists@xxxxxxxxxxxxxxx
To: tommy24@xxxxxxxx
Subject: AW: [Xen-users] How to transfer files from DOM 0 to DOM U
Date: Wed, 24 Sep 2008 19:52:50 +0200
CC: xen-users@xxxxxxxxxxxxxxxxxxx
Hi
When using a notwork share within one Xen machine (domUs +
dom0), the “real” network driver is not involved.
Xen has it’s own virtual network cards and these should work
independent of the machines network driver.
Regards,
Steffen
Von:
xen-users-bounces@xxxxxxxxxxxxxxxxxxx
[mailto:xen-users-bounces@xxxxxxxxxxxxxxxxxxx] Im Auftrag von Tommy
Huang
Gesendet: Mittwoch, 24. September 2008 05:07
An: deshantm@xxxxxxxxx
Cc: xen-users@xxxxxxxxxxxxxxxxxxx
Betreff: RE: [Xen-users] How to transfer files from DOM 0 to DOM U
Hi,
Thanks for the answer. I will test it later.
The reason why I don't use networking way is because I have to use a customized
kernel.
The built-in e1000 driver seems not working on my network adapter when I tried
to use bridge.
And I found that I have to update it then it shoule be able to work
(I have another original kernel used for comparison, it happens to have
the same problem.
So I update the driver and it works.)
However, I really don't know how to update the driver on the customized kernel.
I cannot find the kernel-source package for that kernel (The kernel version of
the customized one and my original one are different).
So I cannot compile the latest e1000 package within the customized kernel
because of lacking kernel-source package.
I cannot use the kernel-source of my original kernel since the versions are
different and it will have "Invalid Module Format" error while
modprobe.
Anyway, I cannot correctly configure bridging correctly at this moment. That's
why I need another solution for it.
By the way, do you know any website that talks about how the answer that you
mentioned below?
That would help me set up all things more easier. Thanks again.
Regards,
- Tommy
> Date: Tue, 23 Sep 2008 22:49:22 -0400
> From: deshantm@xxxxxxxxx
> To: tommy24@xxxxxxxx
> Subject: Re: [Xen-users] How to transfer files from DOM 0 to DOM U
> CC: xen-users@xxxxxxxxxxxxxxxxxxx
>
> On Tue, Sep 23, 2008 at 8:48 PM, Tommy Huang <tommy24@xxxxxxxx>
wrote:
> > Hi,
> >
> > I am wondering if there is another way to do so besides using
bridging or
> > other network stuff.
> > Any information is appreciated.
>
> If the domU is shutdown, you can mount its file system and copy files into
it.
>
> The reason that everyone suggests networking is that if you tried to mount
> a file system twice (once in dom0 and once in the domU) you will cause
file
> system corruption. So using cluster and/or network file systems is really
your
> only real option for dealing with a running guest.
>
> If you have a partition that is available to dom0 and domU, and you only
> mount it in the one that you want to write in and the other leave it
> ummounted or
> mounted read-only, that could be a way, but you would have to implement it
> carefully and the potential for error is there.
>
> (when i say partition above, it could be a image file created with dd)
>
> It seems like learning the bridging and or basic network sharing is an
> easier route.
>
> Is there a reason not to use a internal private network with a bridge
> to accomplish
> your goal?
>
> Cheers,
> Todd
>
> --
> Todd Deshane
> http://todddeshane.net
> check out our book: http://runningxen.com
Get
more out of the Web. Learn 10 hidden secrets of Windows Live. Learn Now
Want to do more with Windows Live? Learn “10 hidden secrets” from Jamie. Learn Now
|
Home