Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1142247

Summary: activating vm's bootable disk after deactivating it, will cause remounting the disk file system as RO
Product: Red Hat Enterprise Virtualization Manager Reporter: lkuchlan <lkuchlan>
Component: ovirt-engineAssignee: Nobody <nobody>
Status: CLOSED NOTABUG QA Contact: Aharon Canan <acanan>
Severity: high Docs Contact:
Priority: unspecified    
Version: 3.5.0CC: amureini, derez, ecohen, gklein, iheim, lkuchlan, lpeer, michal.skrivanek, rbalakri, Rhev-m-bugs, scohen, tnisan, yeylon
Target Milestone: ---   
Target Release: 3.5.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: virt
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-11-10 09:50:42 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
Engine and vdsm logs none

Description lkuchlan 2014-09-16 12:45:30 UTC 
Description of problem:
vm with 1 disk with OS
after deactivating the disk, I activating it again and the disk remount as read only.



Version-Release number of selected component (if applicable):
rhevm-3.5.0-0.10.master.el6ev.noarch
vdsm-4.16.3-2.el7.x86_64

How reproducible:
100%

Steps to Reproduce:
1 vm + 1 disk (bootable) OS installed
1. run the vm
2. deactivate the bootable disk
3. activate the disk

Actual results:
explained above


Expected results:
the disk file system should mount a RW

Additional info:
Comment 1 Allon Mureinik 2014-09-17 08:19:52 UTC 
Please attach vdsm and engine logs.
Comment 2 lkuchlan 2014-09-21 10:40:12 UTC 
Created attachment 939729 [details]
Engine and vdsm logs
Comment 4 Daniel Erez 2014-10-05 08:10:21 UTC 
According to the vdsm log [1], 'readonly' tag hasn't been sent as part of hotplug xml - i.e. the disk isn't defined as read-only by engine. However, mounting is guest's responsibility and limited by OS support; hence, seems like not a bug of management.

@Michal - is there anything else we can do here from virt side?

[1]
Thread-213::DEBUG::2014-09-21 13:32:47,517::vm::3844::vm.Vm::(hotplugDisk) vmId=`fe73d29d-c7c1-4c3d-878b-5d19edb66df9`::Hotplug disk xml:
<disk device="disk" snapshot="no" type="block">
	<source dev="/rhev/data-center/00000002-0002-0002-0002-0000000002b1/8043365c-1522-4ebb-aa26-c08dce08f501/images/a74059e2-a399-4c1d-8f30-36fb037aaad6/6b6c5f3a-3809-4045-b528-9b698441151c"/>
	<target bus="virtio" dev="vdd"/>
	<serial>a74059e2-a399-4c1d-8f30-36fb037aaad6</serial>
	<driver cache="none" error_policy="stop" io="native" name="qemu" type="raw"/>
</disk>
Comment 5 Michal Skrivanek 2014-10-08 13:24:31 UTC 
well, is it remounted ro by the guest? It seems so. Then it should be like that at the time of deactivation already.
Please observe and confirm guest behavior

Daniel, I'm not sure what is deactive supposed to actually do? Does it try to hot remove the disk?
Comment 6 Daniel Erez 2014-10-12 07:37:57 UTC 
(In reply to Michal Skrivanek from comment #5)
> well, is it remounted ro by the guest? It seems so. Then it should be like
> that at the time of deactivation already.
> Please observe and confirm guest behavior
> 
> Daniel, I'm not sure what is deactive supposed to actually do? Does it try
> to hot remove the disk?

Yes, on a running VM, deactivate just invokes 'hotunplugDisk'.
Comment 7 Michal Skrivanek 2014-10-30 15:08:14 UTC 
so you have one disk, you booted from it
you eject it
and you plug it back

and you expect what exactly?
Comment 8 lkuchlan 2014-11-02 08:06:15 UTC 
After activate the disk, i expect that the disk also remount for write
Comment 9 Michal Skrivanek 2014-11-10 09:50:42 UTC 
what the guest does with the disk is a responsibility of the guest.