hi All,
I have :
Host: N54L + Windows 2008R2 + VB 4.3.22
NIC1: Intel Gigabit to LAN
NIC2: Broadcom NetXtreme to WAN
PFsense running as VM with 4vNIC. 3 are attached to the LAN, 1 is attached to the WAN.
The issue I have is after a random period the WAN side becomes unresponsive which the VM is unaware of. Disable re-enable of phys adapter does nothing, as does detach and re-attach of the "cable connected". In trying to "forward-fix" (instead of reboot) today I found that changing the vNIC 2 from one pNIC to the other fixed the issue, however I see in the logs this triggers an instantaneous suspend/resume operation which would appear to be the 'fix'.
Has anyone seen such behaviour before?
thanks, Dave.
NB. Pls ignore the fact I shutdown the VM shortly after, it was fixed at this point
Network Death on 1 VNIC
-
- Posts: 4
- Joined: 20. Feb 2015, 11:24
Network Death on 1 VNIC
- Attachments
-
- PfSense-2015-02-20-08-30-05.log
- (94.91 KiB) Downloaded 6 times
-
- Volunteer
- Posts: 8851
- Joined: 30. Apr 2009, 09:45
- Primary OS: Mac OS X other
- VBox Version: PUEL
- Guest OSses: just about all that run
Re: Network Death on 1 VNIC
This might help... viewtopic.php?f=1&t=66067#p312593
OSX, Linux and Windows Hosts & Guests
There are three groups of people. Those that can count and those that can't.
There are three groups of people. Those that can count and those that can't.
-
- Posts: 4
- Joined: 20. Feb 2015, 11:24
Re: Network Death on 1 VNIC
thanks for that. I've gone to r98406 - let's see if it's still an issue (probably will be as it's bridge rather than NAT, but you never know!).
cheers.
cheers.
-
- Posts: 4
- Joined: 20. Feb 2015, 11:24
Re: Network Death on 1 VNIC
Issue had occurred again by this morning.
Anyone able to indicate what I might need to do to capture the 'issue in the logs?
the issue has occured between these two timespans:
00:00:37.574992 PIIX3 ATA: Ctl#0: RESET, DevSel=0 AIOIf=0 CmdIf0=0xc4 (-1 usec ago) CmdIf1=0x00 (-1 usec ago)
00:00:37.587970 PIIX3 ATA: Ctl#0: finished processing RESET
00:00:37.688042 PIIX3 ATA: Ctl#1: RESET, DevSel=0 AIOIf=0 CmdIf0=0xa0 (-1 usec ago) CmdIf1=0x00 (-1 usec ago)
00:00:37.698754 PIIX3 ATA: Ctl#1: finished processing RESET
15:30:44.933866 UIMachineLogic: Host-screen geometry changed.
15:30:45.351660 UIMachineLogic: Host-screen available-area changed.
15:31:42.324122 Entering S5 power state (power down)
15:31:42.378884 Changing the VM state from 'RUNNING' to 'POWERING_OFF'
thanks a lot.
Anyone able to indicate what I might need to do to capture the 'issue in the logs?
the issue has occured between these two timespans:
00:00:37.574992 PIIX3 ATA: Ctl#0: RESET, DevSel=0 AIOIf=0 CmdIf0=0xc4 (-1 usec ago) CmdIf1=0x00 (-1 usec ago)
00:00:37.587970 PIIX3 ATA: Ctl#0: finished processing RESET
00:00:37.688042 PIIX3 ATA: Ctl#1: RESET, DevSel=0 AIOIf=0 CmdIf0=0xa0 (-1 usec ago) CmdIf1=0x00 (-1 usec ago)
00:00:37.698754 PIIX3 ATA: Ctl#1: finished processing RESET
15:30:44.933866 UIMachineLogic: Host-screen geometry changed.
15:30:45.351660 UIMachineLogic: Host-screen available-area changed.
15:31:42.324122 Entering S5 power state (power down)
15:31:42.378884 Changing the VM state from 'RUNNING' to 'POWERING_OFF'
thanks a lot.
- Attachments
-
- PfSense-2015-02-21-07-53-01.log
- (89.52 KiB) Downloaded 7 times