Changes between Initial Version and Version 1 of Ticket #12567
- Timestamp:
- Jan 6, 2014 1:58:51 PM (10 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #12567 – Description
initial v1 1 1 Hello, 2 2 3 I used to have workstations running local VirtualBox VMs which base disk are connected to the same remote iSCSI read-only lun. It use to work because each VM also have a default snapshot to the base disk meaning disk writes are redirected to the local differential disk created by the snapshot.4 This worked correctly from version 4.0 to latest 4.2.20 and seems broken starting from 4.3.0, including latest 4.3.6 3 I used to have workstations running local !VirtualBox VMs which base disk are connected to the same remote iSCSI read-only lun. It use to work because each VM also have a default snapshot to the base disk meaning disk writes are redirected to the local differential disk created by the snapshot.[[BR]] 4 This worked correctly from version 4.0 to latest 4.2.20 and seems broken starting from 4.3.0, including latest 4.3.6.[[BR]] 5 5 I could verify this on a Mac host (OSX 10.9) and a Windows host (Windows 7 Prof.). I expect it to be the same on a Linux Host but didn't have a chance to verify. 6 6 7 How to reproduce: 8 machine 1: iSCSI server (I used ietd on SLES). IP address 192.168.0.19 9 machine 2: VirtualBox host (Windows or OSX using Virtualbox 4.3.6). IP address 192.168.0.237 How to reproduce:[[BR]] 8 machine 1: iSCSI server (I used ietd on SLES). IP address 192.168.0.19[[BR]] 9 machine 2: !VirtualBox host (Windows or OSX using Virtualbox 4.3.6). IP address 192.168.0.23 10 10 11 1. machine 1:12 - create an iSCSI target and a read-write 20GB Lun 13 target: iqn.1995-09.fr.univ-lr:storage.win7 14 lun: 2 11 1. machine 1: 12 - create an iSCSI target and a read-write 20GB Lun [[BR]] 13 target: iqn.1995-09.fr.univ-lr:storage.win7 [[BR]] 14 lun: 2 15 15 16 2. machine 2: 17 2.1 create a VB VM 'win7' without a hard disk 18 2.2 attach the iSCSI volume from machine 1 with VBoxManage: 19 VBoxManage storageattach "win7" --storagectl IDE --port 0 --device 1 --type hdd --medium iscsi --mtype normal --server "192.168.0.19" --target "iqn.1995-09.fr.univ-lr:storage.win7" --lun 2 20 2.3 install the guest OS (Windows 7 Pro.) 21 2.4 start the guest OS once after install to make sure booting read-write from the remote target works fine 22 2.5 poweroff the VM and create a snapshot 16 2. machine 2: 17 - create a VB VM 'win7' without a hard disk 18 - attach the iSCSI volume from machine 1 with VBoxManage: 19 {{{ 20 VBoxManage storageattach "win7" --storagectl IDE --port 0 --device 1 21 --type hdd --medium iscsi --mtype normal --server "192.168.0.19" 22 --target "iqn.1995-09.fr.univ-lr:storage.win7" --lun 2 23 }}} 24 - install the guest OS (Windows 7 Pro.) 25 - start the guest OS once after install to make sure booting read-write from the remote target works fine 26 - poweroff the VM and create a snapshot 23 27 24 3. machine 1:25 3.1make the previous Lun 2 read-only28 3. machine 1: 29 - make the previous Lun 2 read-only 26 30 27 4. machine 2:28 4.1start the VM31 4. machine 2: 32 - start the VM 29 33 30 31 - With VirtualBox 4.3.6, the VM hangs just after starting and the associated host process is using 100% CPU time. The diffential disk never grows and there isn't any iSCSI network traffic on machine 1. 34 With !VirtualBox 4.3.6, the VM hangs just after starting and the associated host process is using 100% CPU time. The diffential disk never grows and there isn't any iSCSI network traffic on machine 1. 32 35 Unfortunately, nothing interresting in the VM log file (Windows host or Mac host). 33 36 34 - withVirtualBox 4.2.20, the guest OS starts and differential disk of the snapshot starts to grow while block are written37 With !VirtualBox 4.2.20, the guest OS starts and differential disk of the snapshot starts to grow while block are written 35 38 36 39 If I downgrade from 4.3.6 to 4.2.20 everything works fine again.
