#[repr(C)]pub struct VZDiskBlockDeviceStorageDeviceAttachment { /* private fields */ }
VZDiskBlockDeviceStorageDeviceAttachment
and VZStorageDeviceAttachment
only.Expand description
Storage device attachment using a disk block device to store data.
The disk block device implements a storage attachment by using an actual disk rather than a disk image on a file system.
For example, a disk block device on the disk at /dev/rdisk42
would execute the I/O operations directly on that disk
rather than through a file system.
Note that if the disk has a file system formatted on it, the guest is able to destroy data in a way that is not recoverable. The disk passed to this attachment needs to be handled with caution.
An example use of this API is:
NSFileHandle *fileHandle = [NSFileHandle fileHandleForReadingAtPath:
"
/dev/rdisk42"];
if (!fileHandle) {
// Handle errors.
}
NSError *error;
VZDiskBlockDeviceStorageDeviceAttachment *attachment =
[[VZDiskBlockDeviceStorageDeviceAttachment alloc] initWithFileHandle:fileHandle
readOnly:YES
synchronizationMode:VZDiskSynchronizationModeFull
error:error];
if (!attachment) {
// Handle errors.
}
Disk file handles are typically only accessible by the root
user unless permission is explicitly granted.
Running virtual machines as root is not recommended. If root
access is required to open the file descriptor, it is recommended to do that operation
in a separate process then pass the file descriptor to a less privileged process running Virtualization framework.
See: VZDiskImageStorageDeviceAttachment
See: VZNVMExpressControllerDeviceConfiguration
See: VZUSBMassStorageDeviceConfiguration
See: VZVirtioBlockDeviceConfiguration
See also Apple’s documentation
Implementations§
Source§impl VZDiskBlockDeviceStorageDeviceAttachment
impl VZDiskBlockDeviceStorageDeviceAttachment
Sourcepub unsafe fn initWithFileHandle_readOnly_synchronizationMode_error(
this: Allocated<Self>,
file_handle: &NSFileHandle,
read_only: bool,
synchronization_mode: VZDiskSynchronizationMode,
) -> Result<Retained<Self>, Retained<NSError>>
Available on crate feature VZDiskSynchronizationMode
only.
pub unsafe fn initWithFileHandle_readOnly_synchronizationMode_error( this: Allocated<Self>, file_handle: &NSFileHandle, read_only: bool, synchronization_mode: VZDiskSynchronizationMode, ) -> Result<Retained<Self>, Retained<NSError>>
VZDiskSynchronizationMode
only.Initialize the disk attachment from a file handle.
Parameter fileHandle
: File handle to a block device.
Parameter readOnly
: If YES, the disk attachment is read only, otherwise, if the file handle allows writes, the device can write data into it.
Parameter synchronizationMode
: Defines how the disk synchronizes with the underlying storage when the guest operating system flushes data.
Parameter error
: If not nil, assigned with the error if the initialization failed.
Returns: An initialized VZDiskBlockDeviceStorageDeviceAttachment
or nil if there was an error.
The file handle is retained by the disk attachment. The handle must be open when the virtual machine starts.
The readOnly
parameter affects how the disk is exposed to the guest operating system
by the storage controller. If the disk is intended to be used read-only, it is also recommended
to open the file handle as read-only.
Sourcepub unsafe fn fileHandle(&self) -> Retained<NSFileHandle>
pub unsafe fn fileHandle(&self) -> Retained<NSFileHandle>
File handle to the underlying disk used for storage by the attachment.
Sourcepub unsafe fn isReadOnly(&self) -> bool
pub unsafe fn isReadOnly(&self) -> bool
Whether the underlying disk attachment is read-only.
Sourcepub unsafe fn synchronizationMode(&self) -> VZDiskSynchronizationMode
Available on crate feature VZDiskSynchronizationMode
only.
pub unsafe fn synchronizationMode(&self) -> VZDiskSynchronizationMode
VZDiskSynchronizationMode
only.The mode in which the disk image synchronizes data with the underlying storage device.
Methods from Deref<Target = NSObject>§
Sourcepub fn doesNotRecognizeSelector(&self, sel: Sel) -> !
pub fn doesNotRecognizeSelector(&self, sel: Sel) -> !
Handle messages the object doesn’t recognize.
See Apple’s documentation for details.
Methods from Deref<Target = AnyObject>§
Sourcepub fn class(&self) -> &'static AnyClass
pub fn class(&self) -> &'static AnyClass
Dynamically find the class of this object.
§Panics
May panic if the object is invalid (which may be the case for objects
returned from unavailable init
/new
methods).
§Example
Check that an instance of NSObject
has the precise class NSObject
.
use objc2::ClassType;
use objc2::runtime::NSObject;
let obj = NSObject::new();
assert_eq!(obj.class(), NSObject::class());
Sourcepub unsafe fn get_ivar<T>(&self, name: &str) -> &Twhere
T: Encode,
👎Deprecated: this is difficult to use correctly, use Ivar::load
instead.
pub unsafe fn get_ivar<T>(&self, name: &str) -> &Twhere
T: Encode,
Ivar::load
instead.Use Ivar::load
instead.
§Safety
The object must have an instance variable with the given name, and it
must be of type T
.
See Ivar::load_ptr
for details surrounding this.
Sourcepub fn downcast_ref<T>(&self) -> Option<&T>where
T: DowncastTarget,
pub fn downcast_ref<T>(&self) -> Option<&T>where
T: DowncastTarget,
Attempt to downcast the object to a class of type T
.
This is the reference-variant. Use Retained::downcast
if you want
to convert a retained object to another type.
§Mutable classes
Some classes have immutable and mutable variants, such as NSString
and NSMutableString
.
When some Objective-C API signature says it gives you an immutable class, it generally expects you to not mutate that, even though it may technically be mutable “under the hood”.
So using this method to convert a NSString
to a NSMutableString
,
while not unsound, is generally frowned upon unless you created the
string yourself, or the API explicitly documents the string to be
mutable.
See Apple’s documentation on mutability and on
isKindOfClass:
for more details.
§Generic classes
Objective-C generics are called “lightweight generics”, and that’s because they aren’t exposed in the runtime. This makes it impossible to safely downcast to generic collections, so this is disallowed by this method.
You can, however, safely downcast to generic collections where all the
type-parameters are AnyObject
.
§Panics
This works internally by calling isKindOfClass:
. That means that the
object must have the instance method of that name, and an exception
will be thrown (if CoreFoundation is linked) or the process will abort
if that is not the case. In the vast majority of cases, you don’t need
to worry about this, since both root objects NSObject
and
NSProxy
implement this method.
§Examples
Cast an NSString
back and forth from NSObject
.
use objc2::rc::Retained;
use objc2_foundation::{NSObject, NSString};
let obj: Retained<NSObject> = NSString::new().into_super();
let string = obj.downcast_ref::<NSString>().unwrap();
// Or with `downcast`, if we do not need the object afterwards
let string = obj.downcast::<NSString>().unwrap();
Try (and fail) to cast an NSObject
to an NSString
.
use objc2_foundation::{NSObject, NSString};
let obj = NSObject::new();
assert!(obj.downcast_ref::<NSString>().is_none());
Try to cast to an array of strings.
use objc2_foundation::{NSArray, NSObject, NSString};
let arr = NSArray::from_retained_slice(&[NSObject::new()]);
// This is invalid and doesn't type check.
let arr = arr.downcast_ref::<NSArray<NSString>>();
This fails to compile, since it would require enumerating over the array to ensure that each element is of the desired type, which is a performance pitfall.
Downcast when processing each element instead.
use objc2_foundation::{NSArray, NSObject, NSString};
let arr = NSArray::from_retained_slice(&[NSObject::new()]);
for elem in arr {
if let Some(data) = elem.downcast_ref::<NSString>() {
// handle `data`
}
}
Trait Implementations§
Source§impl AsRef<VZDiskBlockDeviceStorageDeviceAttachment> for VZDiskBlockDeviceStorageDeviceAttachment
impl AsRef<VZDiskBlockDeviceStorageDeviceAttachment> for VZDiskBlockDeviceStorageDeviceAttachment
Source§impl AsRef<VZStorageDeviceAttachment> for VZDiskBlockDeviceStorageDeviceAttachment
impl AsRef<VZStorageDeviceAttachment> for VZDiskBlockDeviceStorageDeviceAttachment
Source§fn as_ref(&self) -> &VZStorageDeviceAttachment
fn as_ref(&self) -> &VZStorageDeviceAttachment
Source§impl Borrow<VZStorageDeviceAttachment> for VZDiskBlockDeviceStorageDeviceAttachment
impl Borrow<VZStorageDeviceAttachment> for VZDiskBlockDeviceStorageDeviceAttachment
Source§fn borrow(&self) -> &VZStorageDeviceAttachment
fn borrow(&self) -> &VZStorageDeviceAttachment
Source§impl ClassType for VZDiskBlockDeviceStorageDeviceAttachment
impl ClassType for VZDiskBlockDeviceStorageDeviceAttachment
Source§const NAME: &'static str = "VZDiskBlockDeviceStorageDeviceAttachment"
const NAME: &'static str = "VZDiskBlockDeviceStorageDeviceAttachment"
Source§type Super = VZStorageDeviceAttachment
type Super = VZStorageDeviceAttachment
Source§type ThreadKind = <<VZDiskBlockDeviceStorageDeviceAttachment as ClassType>::Super as ClassType>::ThreadKind
type ThreadKind = <<VZDiskBlockDeviceStorageDeviceAttachment as ClassType>::Super as ClassType>::ThreadKind
Source§impl NSObjectProtocol for VZDiskBlockDeviceStorageDeviceAttachment
impl NSObjectProtocol for VZDiskBlockDeviceStorageDeviceAttachment
Source§fn isEqual(&self, other: Option<&AnyObject>) -> bool
fn isEqual(&self, other: Option<&AnyObject>) -> bool
Source§fn hash(&self) -> usize
fn hash(&self) -> usize
Source§fn isKindOfClass(&self, cls: &AnyClass) -> bool
fn isKindOfClass(&self, cls: &AnyClass) -> bool
Source§fn is_kind_of<T>(&self) -> bool
fn is_kind_of<T>(&self) -> bool
isKindOfClass
directly, or cast your objects with AnyObject::downcast_ref