FreeBSD-current/Xen and block device enumeration
This config: disk = [ 'phy:/dev/hosting2_data2/XEN_freebsd_root,0x01,w', 'phy:/dev/hosting2_data2/XEN_freebsd_swap,0x02,w' ] Gives this output in dmesg: xbd0: 10240MB at device/vbd/1 on xenbus0 GEOM: new disk xbd0 xbd1: 512MB at device/vbd/2 on xenbus0 WARNING: WITNESS option enabled, expect reduced performance. GEOM: new disk xbd0 and then ls -l /dev/xbd* : freebsd_domu# ls -l /dev/xbd* crw-r- 1 root operator0, 41 May 18 02:51 /dev/xbd0 crw-r- 1 root operator0, 41 May 18 02:51 /dev/xbd0 Hm, I wonder whats busted! Adrian ___ freebsd-xen@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-xen To unsubscribe, send any mail to "freebsd-xen-unsubscr...@freebsd.org"
Re: FreeBSD-current/Xen and block device enumeration
(Cross-posting to -current because of the way a badly confused Xen DomU confuses GEOM and populates invalid stuff.) 2009/5/19 Adrian Chadd : > This config: > > disk = [ > 'phy:/dev/hosting2_data2/XEN_freebsd_root,0x01,w', > 'phy:/dev/hosting2_data2/XEN_freebsd_swap,0x02,w' > ] Confuses some "linux" device unit naming type magic in the blkfront device code. Anyway. To get xbd0 and xbd1 I need to use 0xCA00 and 0xCA10. The code matches on major 202 (0xca) and shifts the minor bits right to get partition ids (which I'm not using here.) This outlines some sanity checking and debugging which should be improved a little. > Gives this output in dmesg: > > xbd0: 10240MB at device/vbd/1 on xenbus0 > GEOM: new disk xbd0 > xbd1: 512MB at device/vbd/2 on xenbus0 > WARNING: WITNESS option enabled, expect reduced performance. > GEOM: new disk xbd0 .. since I shouldn't be able to do that. > > and then ls -l /dev/xbd* : > > freebsd_domu# ls -l /dev/xbd* > crw-r- 1 root operator 0, 41 May 18 02:51 /dev/xbd0 > crw-r- 1 root operator 0, 41 May 18 02:51 /dev/xbd0 .. or that. Adrian ___ freebsd-xen@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-xen To unsubscribe, send any mail to "freebsd-xen-unsubscr...@freebsd.org"
[Fwd: Re: FreeBSD-current/Xen and block device enumeration]
Forwarded Message > From: Mister Olli > Reply-to: mister.o...@googlemail.com > To: Adrian Chadd > Subject: Re: FreeBSD-current/Xen and block device enumeration > Date: Mon, 18 May 2009 19:07:16 +0200 > > hi, > > I had a similar setup with up to 4 block devices connected to a domU, > but my config looked a little bit different. Instead of 0x01/0x02/... > I've used hda/hdb/... and it worked quite well. > > Btw, I've never seen a 0x.. configuration before ;-)) > > Regards, > --- > Mr. Olli > > On Tue, 2009-05-19 at 01:00 +0800, Adrian Chadd wrote: > > This config: > > > > disk = [ > > 'phy:/dev/hosting2_data2/XEN_freebsd_root,0x01,w', > > 'phy:/dev/hosting2_data2/XEN_freebsd_swap,0x02,w' > > ] > > > > > > Gives this output in dmesg: > > > > xbd0: 10240MB at device/vbd/1 on xenbus0 > > GEOM: new disk xbd0 > > xbd1: 512MB at device/vbd/2 on xenbus0 > > WARNING: WITNESS option enabled, expect reduced performance. > > GEOM: new disk xbd0 > > > > and then ls -l /dev/xbd* : > > > > freebsd_domu# ls -l /dev/xbd* > > crw-r- 1 root operator0, 41 May 18 02:51 /dev/xbd0 > > crw-r- 1 root operator0, 41 May 18 02:51 /dev/xbd0 > > > > Hm, I wonder whats busted! > > > > > > > > Adrian > > ___ > > freebsd-xen@freebsd.org mailing list > > http://lists.freebsd.org/mailman/listinfo/freebsd-xen > > To unsubscribe, send any mail to "freebsd-xen-unsubscr...@freebsd.org" ___ freebsd-xen@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-xen To unsubscribe, send any mail to "freebsd-xen-unsubscr...@freebsd.org"
