Re: dev/virtio stuff
On 29/10/2012 21:49, Sean Bruno wrote: So ... I see we have virtio nowish. I've started my hackery to make some man(4) pages for this, but have some questions. Doing some raw QEMU things, I can't quite see how to get the virtio blk and net devices working. I've loaded the virtio drivers as modules. Is this not going to work in this case? I don't see the virtio versions of disk devices in /dev so I'm not sure what the problem here is. Modules work for me. [root@fbsd ~]# grep v /boot/loader.conf virtio_load=YES virtio_pci_load=YES virtio_blk_load=YES if_vtnet_load=YES virtio_balloon_load=YES [root@fbsd ~]# mount /dev/vtbd0s1a on / (ufs, local) devfs on /dev (devfs, local, multilabel) /dev/vtbd0s1e on /tmp (ufs, local, soft-updates) /dev/vtbd0s1f on /usr (ufs, NFS exported, local, soft-updates) /dev/vtbd0s1d on /var (ufs, local, soft-updates) devfs on /var/named/dev (devfs, local, multilabel) [root@fbsd ~]# ifconfig vtnet0 vtnet0: flags=8943UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST metric 0 mtu 1500 options=c07bbRXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,JUMBO_MTU,VLAN_HWCSUM,TSO4,TSO6,LRO,VLAN_HWTSO,LINKSTATE ether 54:52:00:2a:63:af inet 213.xxx.xxx.13 netmask 0xfc00 broadcast 213.xxx.xxx.255 inet6 fe80::5652:ff:fe2a:63af%vtnet0 prefixlen 64 scopeid 0x1 inet6 2001:470:xxx:xxx::1 prefixlen 64 inet 10.10.24.1 netmask 0xff00 broadcast 10.10.24.255 nd6 options=21PERFORMNUD,AUTO_LINKLOCAL media: Ethernet 1000baseT full-duplex status: active [root@fbsd ~]# uname -a FreeBSD fbsd.bmk.namesco.net 10.0-CURRENT FreeBSD 10.0-CURRENT #33 r241491M: Sat Oct 13 01:34:48 BST 2012 t...@fbsd.bmk.namesco.net:/usr/obj/usr/src/sys/unsane-vm amd64 Relevent bits in libvirt config (kvm running on centos5) disk type='block' device='disk' driver name='qemu' type='raw'/ source dev='/dev/vg_data/vm.unsane.co.uk'/ target dev='vda' bus='virtio'/ alias name='virtio0'/ address type='drive' controller='0' bus='0' unit='0'/ /disk controller type='ide' index='0' address type='pci' domain='0x' bus='0x00' slot='0x01' function='0x1'/ /controller interface type='bridge' mac address='54:52:00:2a:63:af'/ source bridge='br0'/ target dev='vnet0'/ model type='virtio'/ address type='pci' domain='0x' bus='0x00' slot='0x03' function='0x0'/ /interface Not sure if thats useful to you or not? Vince http://people.freebsd.org/~sbruno/virtio.txt Sean ___ 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 ___ 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
Re: dev/virtio stuff
On Mon, 2012-10-29 at 16:58 -0700, Vincent Hoffman wrote: On 29/10/2012 21:49, Sean Bruno wrote: So ... I see we have virtio nowish. I've started my hackery to make some man(4) pages for this, but have some questions. Doing some raw QEMU things, I can't quite see how to get the virtio blk and net devices working. I've loaded the virtio drivers as modules. Is this not going to work in this case? I don't see the virtio versions of disk devices in /dev so I'm not sure what the problem here is. Modules work for me. [root@fbsd ~]# grep v /boot/loader.conf virtio_load=YES virtio_pci_load=YES virtio_blk_load=YES if_vtnet_load=YES virtio_balloon_load=YES [root@fbsd ~]# mount /dev/vtbd0s1a on / (ufs, local) devfs on /dev (devfs, local, multilabel) /dev/vtbd0s1e on /tmp (ufs, local, soft-updates) /dev/vtbd0s1f on /usr (ufs, NFS exported, local, soft-updates) /dev/vtbd0s1d on /var (ufs, local, soft-updates) devfs on /var/named/dev (devfs, local, multilabel) [root@fbsd ~]# ifconfig vtnet0 vtnet0: flags=8943UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST metric 0 mtu 1500 options=c07bbRXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,JUMBO_MTU,VLAN_HWCSUM,TSO4,TSO6,LRO,VLAN_HWTSO,LINKSTATE ether 54:52:00:2a:63:af inet 213.xxx.xxx.13 netmask 0xfc00 broadcast 213.xxx.xxx.255 inet6 fe80::5652:ff:fe2a:63af%vtnet0 prefixlen 64 scopeid 0x1 inet6 2001:470:xxx:xxx::1 prefixlen 64 inet 10.10.24.1 netmask 0xff00 broadcast 10.10.24.255 nd6 options=21PERFORMNUD,AUTO_LINKLOCAL media: Ethernet 1000baseT full-duplex status: active [root@fbsd ~]# uname -a FreeBSD fbsd.bmk.namesco.net 10.0-CURRENT FreeBSD 10.0-CURRENT #33 r241491M: Sat Oct 13 01:34:48 BST 2012 t...@fbsd.bmk.namesco.net:/usr/obj/usr/src/sys/unsane-vm amd64 Relevent bits in libvirt config (kvm running on centos5) disk type='block' device='disk' driver name='qemu' type='raw'/ source dev='/dev/vg_data/vm.unsane.co.uk'/ target dev='vda' bus='virtio'/ alias name='virtio0'/ address type='drive' controller='0' bus='0' unit='0'/ /disk controller type='ide' index='0' address type='pci' domain='0x' bus='0x00' slot='0x01' function='0x1'/ /controller interface type='bridge' mac address='54:52:00:2a:63:af'/ source bridge='br0'/ target dev='vnet0'/ model type='virtio'/ address type='pci' domain='0x' bus='0x00' slot='0x03' function='0x0'/ /interface Not sure if thats useful to you or not? totally and very useful. thank you. Sean ___ 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
Re: dev/virtio stuff
On Mon, 2012-10-29 at 17:00 -0700, Sean Bruno wrote: [root@fbsd ~]# ifconfig vtnet0 vtnet0: flags=8943UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST metric 0 mtu 1500 options=c07bbRXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,JUMBO_MTU,VLAN_HWCSUM,TSO4,TSO6,LRO,VLAN_HWTSO,LINKSTATE ether 54:52:00:2a:63:af inet 213.xxx.xxx.13 netmask 0xfc00 broadcast 213.xxx.xxx.255 inet6 fe80::5652:ff:fe2a:63af%vtnet0 prefixlen 64 scopeid 0x1 inet6 2001:470:xxx:xxx::1 prefixlen 64 inet 10.10.24.1 netmask 0xff00 broadcast 10.10.24.255 nd6 options=21PERFORMNUD,AUTO_LINKLOCAL media: Ethernet 1000baseT full-duplex status: active Some google foo landed me on an IBM site that hinted at me that the virsh commands of RHEL 5 don't know how to setup virtio on the network. However, you can add it to the RHEL 5 config manually. http://publib.boulder.ibm.com/infocenter/lnxinfo/v3r0m0/index.jsp?topic= %2Fliaat%2Fliaatkvmfaq.htm Sean ___ 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
Re: dev/virtio stuff
Hi, - Original Message - From: Sean Bruno sean...@yahoo-inc.com To: freebsd-virtualization@freebsd.org Sent: Monday, October 29, 2012 4:49:42 PM Subject: dev/virtio stuff So ... I see we have virtio nowish. I've started my hackery to make some man(4) pages for this, but have some questions. Doing some raw QEMU things, I can't quite see how to get the virtio blk and net devices working. There are already virtio(4) man pages, but it looks like they didn't get MFC to 9. I've loaded the virtio drivers as modules. Is this not going to work in this case? I don't see the virtio versions of disk devices in /dev so I'm not sure what the problem here is. http://people.freebsd.org/~sbruno/virtio.txt FreeBSD 7.5-YAHOO-20121028 #0 ybsd_9@324991: Sun Oct 28 22:08:46 UTC 2012 ker...@yahoo-inc.com:/sys/amd64/compile/YAHOO amd64 I assume this is 9-STABLE'ish? virtio_pci0: VirtIO PCI Block adapter port 0xc200-0xc23f irq 11 at device 4.0 on pci0 vtblk0: VirtIO Block Adapter on virtio_pci0 virtio_pci0: host features: 0x4114 NotifyOnEmpty,DiskGeometry,MaxNumSegs virtio_pci0: negotiated features: 0x14 DiskGeometry,MaxNumSegs vtblk0: 4096MB (8388608 512 byte sectors) The VirtIO block gets probed and attached correctly, and right after the last printf, hands off to disk_create(9) to create the GEOM plumbing and device. VirtIO block devices get created as vtbdX, not as ad, ada, or da. Can you see if g_disk_create() gets called (with flag==EV_CANCEL)? What does a verbose boot show? Bryan Sean ___ 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 ___ 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
