On 2014-11-28 05:42, Ask Bjørn Hansen wrote:
> Hi everyone,
> 
> I’ve spent some time off this week upgrading my 
> build-my-personal-NanoBSD-image tool from a VMware virtual machine to a 
> physical box running a 32-bit build-box under bhyve.
> 
> So far so good — all that has been working really well.
> 
> My nanobsd image is only used on Soekris and PC Engines boxes and my 
> production images are really small (some <100MB storage and ~32MB memory), so 
> I have a crufty kernel config that excluded a bunch of stuff I (thought I) 
> don’t need.
> 
> Now I’d like to run my built image under bhyve for testing. It’s easier for 
> me if the disk comes up as an ada device, so I’m using ahci-hd instead of 
> virtio-blk. With virtio-blk the system boots but the device has the “wrong" 
> name.
> 
> With ahci-hd it can’t read my partition for some reason.
> 
> I’ve tried with both file and zvol backing store.
> 
> This is the error I’m getting:
> 
> ada0: <BHYVE SATA DISK 001> ATA-8 SATA 2.x device
> ada0: Serial Number 123456
> ada0: 300.000MB/s transfers (SATA 2.x, PIO4, PIO 8192bytes)
> ada0: Command Queueing enabled
> ada0: 260MB (532480 512 byte sectors: 16H 63S/T 528C)
> ada0: Previously was known as ad4
> Unsupported cmd:c4
>                   (ada0:ahcich0:0:0:0): READ_MUL. ACB: c4 00 c1 1f 08 40 00 
> 00 00 00 04 00
> (ada0:ahcich0:0:0:0): CAM status: ATA Status Error
> (ada0:ahcich0:0:0:0): ATA status: 41 (DRDY ERR), error: 04 (ABRT )
> (ada0:ahcich0:0:0:0): RES: 41 04 00 00 00 40 00 00 00 00 00
> (ada0:ahcich0:0:0:0): Retrying command
> Unsupported cmd:c4
> 
> 
> Any suggestion for what I’m doing wrong? Did I compile my kernel with some 
> idiotic set of not-working options?
> 
> 
> Ask
> 
> _______________________________________________
> freebsd-virtualization@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
> To unsubscribe, send any mail to 
> "freebsd-virtualization-unsubscr...@freebsd.org"
> 

When using zvols, you must set the 'volmode' to 'dev', otherwise GEOM on
the host locks the disk and causes all kinds of interesting things to
happen.

Note: the volmode property is only applied when the device is created,
so you might have to 'zfs rename' it to cause it to be recreated

-- 
Allan Jude

Attachment: signature.asc
Description: OpenPGP digital signature

Reply via email to