To be honest, RH will probably never get to work on it as XP is past End Of Life, and there exists a workaround.
I don't know if anybody else would like to take it, so we will leave it open for a while.

(In reply to Giuseppe Scrivano from comment #4)
> if it can help: it seems a similar problem was fixed for RHEL-7:
> 
> https://bugzilla.redhat.com/show_bug.cgi?id=1040315
> 
> Can it be the same bug?

Might be.

So it would be interesting to try it without the E1000.

(In reply to Ronen Hod from comment #5)
> (In reply to Giuseppe Scrivano from comment #4)
> > if it can help: it seems a similar problem was fixed for RHEL-7:
> > 
> > https://bugzilla.redhat.com/show_bug.cgi?id=1040315
> > 
> > Can it be the same bug?
> 
> Might be.
> 
> So it would be interesting to try it without the E1000.

Do you mean try it on the host do not have e1000 physical nic card?h

(In reply to sazhufa from comment #0)
> Description of problem:
> Two VM(via virt-manager create kvm vm).
> No.1  WinXP x86 (using virtio net eth0:macvtap, Spice-guest-tools-0.74)
> No.2  NAS4Free 9.2.0.1-r943 (FreeBSD 9.2, using e1000 net eth0:macvtap)
> 
> after installtion, setting IP: 
> nas: 192.168.9.39/24
> win: 192.168.9.100/24
> In windows could not open NAS console(http://192.168.9.39/)
> in nas console, enter shell, type: netstat -na | grep 80, resule is:
> tcp4  0 0 192.168.9.39.80  192.168.9.100.1033 SYN_RCVD !!!
> 
> 
> Version-Release number of selected component (if applicable):
> kernel - 3.13.7-200.fc20.x86_64
> qemu-kvm-1.6.2-1.fc20.x86_64
> libvirt-daemon-driver-qemu-1.1.3.4-3.fc20.x86_64
> qemu-system-x86-1.6.2-1.fc20.x86_64
> libvirt-1.1.3.4-3.fc20.x86_64
> virt-manager-1.0.1-1.fc20.noarch
> 
> 
> 
> How reproducible:
> 
> Steps to Reproduce:
> 1. run virt-manager, create two VM(1.winxp x86, 2.NAS4Free x64)
> 2. winxp VM: virtio net eth0:macvtap, install spice-guest-tools
> 3. nas VM: e1000 net eth0:macvtap
> 4. setting ip addr, and ping each other.
> 5. in winxpvm run: telnet nas-ip 80  (tcp connect to nas 80 port)
> 6. in nas console, enter shell, run: netstat -na | grep 80
> 
> Actual results:
> the TCP state is SYN_RCVD.
> 
> Expected results:
> the TCP state is ESTABLISHED.
> 
> 
> Additional info:
> 
> when I change the winxp VM net type as an emu hardware(such as pci_net,
> rtl8139), the problom is not occur. all is OK.

sazhufa ,Can you attach  lspci -vvv on this bug ?

(In reply to Mike Cao from comment #7)
> (In reply to sazhufa from comment #0)
> > Description of problem:
> > Two VM(via virt-manager create kvm vm).
> > No.1  WinXP x86 (using virtio net eth0:macvtap, Spice-guest-tools-0.74)
> > No.2  NAS4Free 9.2.0.1-r943 (FreeBSD 9.2, using e1000 net eth0:macvtap)
> > 
> > after installtion, setting IP: 
> > nas: 192.168.9.39/24
> > win: 192.168.9.100/24
> > In windows could not open NAS console(http://192.168.9.39/)
> > in nas console, enter shell, type: netstat -na | grep 80, resule is:
> > tcp4  0 0 192.168.9.39.80  192.168.9.100.1033 SYN_RCVD !!!
> > 
> > 
> > Version-Release number of selected component (if applicable):
> > kernel - 3.13.7-200.fc20.x86_64
> > qemu-kvm-1.6.2-1.fc20.x86_64
> > libvirt-daemon-driver-qemu-1.1.3.4-3.fc20.x86_64
> > qemu-system-x86-1.6.2-1.fc20.x86_64
> > libvirt-1.1.3.4-3.fc20.x86_64
> > virt-manager-1.0.1-1.fc20.noarch
> > 
> > 
> > 
> > How reproducible:
> > 
> > Steps to Reproduce:
> > 1. run virt-manager, create two VM(1.winxp x86, 2.NAS4Free x64)
> > 2. winxp VM: virtio net eth0:macvtap, install spice-guest-tools
> > 3. nas VM: e1000 net eth0:macvtap
> > 4. setting ip addr, and ping each other.
> > 5. in winxpvm run: telnet nas-ip 80  (tcp connect to nas 80 port)
> > 6. in nas console, enter shell, run: netstat -na | grep 80
> > 
> > Actual results:
> > the TCP state is SYN_RCVD.
> > 
> > Expected results:
> > the TCP state is ESTABLISHED.
> > 
> > 
> > Additional info:
> > 
> > when I change the winxp VM net type as an emu hardware(such as pci_net,
> > rtl8139), the problom is not occur. all is OK.
> 
> sazhufa ,Can you attach  lspci -vvv on this bug ?

HI, run lspci on which machine? Host or VMs ?
the VMs is FreeBSD or Windows, havn't lspci. so, I can startup it using a linux livecd, all right?

(In reply to Mike Cao from comment #6)
> (In reply to Ronen Hod from comment #5)
> > (In reply to Giuseppe Scrivano from comment #4)
> > > if it can help: it seems a similar problem was fixed for RHEL-7:
> > > 
> > > https://bugzilla.redhat.com/show_bug.cgi?id=1040315
> > > 
> > > Can it be the same bug?
> > 
> > Might be.
> > 
> > So it would be interesting to try it without the E1000.
> 
> Do you mean try it on the host do not have e1000 physical nic card?h

no, my main-board is MSI 870A-G54, on-board NIC is Realtek 8111DL.
AMD Phenom II 720 (three-cores) 16G MEM.

(In reply to sazhufa from comment #8)
> (In reply to Mike Cao from comment #7)
> > (In reply to sazhufa from comment #0)
> > > Description of problem:
> > > Two VM(via virt-manager create kvm vm).
> > > No.1  WinXP x86 (using virtio net eth0:macvtap, Spice-guest-tools-0.74)
> > > No.2  NAS4Free 9.2.0.1-r943 (FreeBSD 9.2, using e1000 net eth0:macvtap)
> > > 
> > > after installtion, setting IP: 
> > > nas: 192.168.9.39/24
> > > win: 192.168.9.100/24
> > > In windows could not open NAS console(http://192.168.9.39/)
> > > in nas console, enter shell, type: netstat -na | grep 80, resule is:
> > > tcp4  0 0 192.168.9.39.80  192.168.9.100.1033 SYN_RCVD !!!
> > > 
> > > 
> > > Version-Release number of selected component (if applicable):
> > > kernel - 3.13.7-200.fc20.x86_64
> > > qemu-kvm-1.6.2-1.fc20.x86_64
> > > libvirt-daemon-driver-qemu-1.1.3.4-3.fc20.x86_64
> > > qemu-system-x86-1.6.2-1.fc20.x86_64
> > > libvirt-1.1.3.4-3.fc20.x86_64
> > > virt-manager-1.0.1-1.fc20.noarch
> > > 
> > > 
> > > 
> > > How reproducible:
> > > 
> > > Steps to Reproduce:
> > > 1. run virt-manager, create two VM(1.winxp x86, 2.NAS4Free x64)
> > > 2. winxp VM: virtio net eth0:macvtap, install spice-guest-tools
> > > 3. nas VM: e1000 net eth0:macvtap
> > > 4. setting ip addr, and ping each other.
> > > 5. in winxpvm run: telnet nas-ip 80  (tcp connect to nas 80 port)
> > > 6. in nas console, enter shell, run: netstat -na | grep 80
> > > 
> > > Actual results:
> > > the TCP state is SYN_RCVD.
> > > 
> > > Expected results:
> > > the TCP state is ESTABLISHED.
> > > 
> > > 
> > > Additional info:
> > > 
> > > when I change the winxp VM net type as an emu hardware(such as pci_net,
> > > rtl8139), the problom is not occur. all is OK.
> > 
> > sazhufa ,Can you attach  lspci -vvv on this bug ?
> 
> HI, run lspci on which machine? Host or VMs ?

Yes I mean host 
> the VMs is FreeBSD or Windows, havn't lspci. so, I can startup it using a
> linux livecd, all right?

Created attachment 884391 [details]
lspci -vvv on host

post at 20140409

Closing this bug. XP is past end-of-life, and we will only work on XP urgent and selected customer bugs.