I've been running VBox with VM's on iSCSI for a couple of
weeks now, and have had problems with VM's being paused
automatically.

Today, I took some time to check a log of one of them and
got this:

00:25:02.234 iSCSI: disconnect from initiator 
iqn.2009-08.com.sun.virtualbox.initiator:01:192.168.69.3 with source port 35951
00:25:02.234 iSCSI: connect from initiator 
iqn.2009-08.com.sun.virtualbox.initiator:01:192.168.69.3 with source port 35953
00:25:12.284 iSCSI: disconnect from initiator 
iqn.2009-08.com.sun.virtualbox.initiator:01:192.168.69.3 with source port 35953
00:25:12.285 iSCSI: login to target 
iqn.2012-02.com.bayour:share.VirtualMachines.Squeeze64 failed
00:25:12.285 AHCI#0: Read at offset 7994322944 (24576 bytes left) returned 
rc=VERR_BROKEN_PIPE
00:25:12.285 AHCI: iSCSI target unavailable
00:25:12.285 VM: Raising runtime error 'DevAHCI_ISCSIDOWN' (fFlags=0x6)
00:25:12.285 Changing the VM state from 'RUNNING' to 'SUSPENDING'.
00:25:12.285 PDMR3Suspend: 75 171 ns run time
00:25:12.285 Changing the VM state from 'SUSPENDING' to 'SUSPENDED'.
00:25:12.288 Console: VM runtime error: fatal=false, errorID=DevAHCI_ISCSIDOWN 
message="The iSCSI target has stopped responding. VM execution is suspended. 
You can resume when it is available again"


This keep happening with a few minutes intervals (I'm copying a lot
of data inside my VM). Anyone got an idea where I should start looking?
I.e., is this a iSCSI or VBox problem? What's this 'broken pipe' mentioned?

Running resume directly after this happens works. For a while, until
it happens again...


------------------------------------------------------------------------------
Virtualization & Cloud Management Using Capacity Planning
Cloud computing makes use of virtualization - but cloud computing 
also focuses on allowing computing to be delivered as a service.
http://www.accelacomm.com/jaw/sfnl/114/51521223/
_______________________________________________
VBox-users-community mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/vbox-users-community

Reply via email to