3:16 p.m.
Hi all,
I am trying to set up an `isolated virtual network' with two or more
MS-DOS guests, all on one single Linux box.
The aim is for them to share a disk (or just one directory on one
disk).
As I could not get it to work with IPX, am now trying TCP/IP. However,
I suspect the MS tools are still attempting to use IPX as well.
Is there some simple solution that I am missing?
Does libvirt support IPX at all?
Any other easy way to do DOS file sharing?
(I believe I can use any version of DOS, and any sort of tool as long
as I get a `remote' directory available as some drive letter.)
/Tomas
3:33 p.m.
On Wed, 02 Nov 2022 08:16:01 +0100, Tomas By wrote:
As I could not get it to work with IPX, am now trying TCP/IP.
However,
I suspect the MS tools are still attempting to use IPX as well.
In fact, it seems that DHCP does not even work.
In virt-manager/Connection details, it says "DHCP range..." for that
network, and virsh net-list says it is active.
DOS says, after a while, "No DHCP server found".
Anything else I can try?
/Tomas
4:15 p.m.
On Wed, Nov 02, 2022 at 08:33:52 +0100, Tomas By wrote:
On Wed, 02 Nov 2022 08:16:01 +0100, Tomas By wrote:
> As I could not get it to work with IPX, am now trying TCP/IP. However,
> I suspect the MS tools are still attempting to use IPX as well.
In fact, it seems that DHCP does not even work.
In virt-manager/Connection details, it says "DHCP range..." for that
network, and virsh net-list says it is active.
DOS says, after a while, "No DHCP server found".
Anything else I can try?
Please post the full XML definition of the network you use for the VMs.
It can be obtained by running 'virsh net-dumpxml $NETWORKNAME'
4:29 p.m.
On Wed, 02 Nov 2022 09:15:19 +0100, Peter Krempa wrote:
Please post the full XML definition of the network you use for the
VMs.
Well, I did not write any XML, but here it is.
|<network>
| <name>isolated</name>
| <uuid>17dca0c1-8bc6-4c6b-89b6-71259492315b</uuid>
| <bridge name='virbr1' stp='on' delay='0'/>
| <mac address='52:54:00:a0:26:52'/>
| <domain name='isolated'/>
| <ip address='192.168.100.1' netmask='255.255.255.0'>
| <dhcp>
| <range start='192.168.100.128' end='192.168.100.254'/>
| </dhcp>
| </ip>
|</network>
Libvirt's network definition creates a bridge (switch), so it
shouldn't
really matter which protocol you run across it. Obviously libvirt
does not configure IPX on the host facing side of the bridge because we
don't support it, but if VMs talk IPX they should be able to.
Is there some way to confirm that one guest VM sees the traffic from
another?
With IPX I get no errors in DOS but they do not see each other.
/Tomas
4:17 p.m.
On Wed, Nov 02, 2022 at 08:16:01 +0100, Tomas By wrote:
Hi all,
I am trying to set up an `isolated virtual network' with two or more
MS-DOS guests, all on one single Linux box.
The aim is for them to share a disk (or just one directory on one
disk).
As I could not get it to work with IPX, am now trying TCP/IP. However,
I suspect the MS tools are still attempting to use IPX as well.
Is there some simple solution that I am missing?
Does libvirt support IPX at all?
Libvirt's network definition creates a bridge (switch), so it shouldn't
really matter which protocol you run across it. Obviously libvirt
does not configure IPX on the host facing side of the bridge because we
don't support it, but if VMs talk IPX they should be able to.
675
days inactive
675
days old
4 comments
2 participants
participants (2)
-
Peter Krempa -
Tomas By