ATA controller and Hyper-V "synthetic storage driver" handle the IDE disks devices ( but not for the CD-ROM) Re: Hyper-V on FreeBSD
Hi! prevent default OS driver from attaching to emulated ATA controller when Hyper-V Disable both primary and secondary ATA controller prevent use CD-ROM device in VM ( guest) Because "synthetic storage driver" not handle CD-ROM devices ( IMHO, even more: Hyper-V host work with CD-ROM only as "PCI bus" device) Best regards, Victor Miasnikov Blog: http://vvm.blog.tut.by/ P.S. http://lists.freebsd.org/pipermail/freebsd-virtualization/2013-April/001180.html == . . . On 23.04.2013 17:07, Larry Melia wrote: . . . Removing our ATA patches, on the other hand, results in a huge performance loss. This is because the root file system is managed by the ATA driver, which is emulated under Hyper-V. == Place on IDE disk only "\boot" ( and bootloader), other on SCSI . P.P.S. Larry, I'm found Youre 3 e-mail accounts, You use all 3 ? ___ 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: ATA controller and Hyper-V "synthetic storage driver" handle the IDE disks devices ( but not for the CD-ROM) Re: Hyper-V on FreeBSD
On 07.05.2013 10:40, Victor Miasnikov wrote: prevent default OS driver from attaching to emulated ATA controller when Hyper-V Disable both primary and secondary ATA controller prevent use CD-ROM device in VM ( guest) Because "synthetic storage driver" not handle CD-ROM devices ( IMHO, even more: Hyper-V host work with CD-ROM only as "PCI bus" device) Then may be possibility of blocking/hiding specific ATA channels or devices could be investigated. http://lists.freebsd.org/pipermail/freebsd-virtualization/2013-April/001180.html == . . . On 23.04.2013 17:07, Larry Melia wrote: . . . Removing our ATA patches, on the other hand, results in a huge performance loss. This is because the root file system is managed by the ATA driver, which is emulated under Hyper-V. == Place on IDE disk only "\boot" ( and bootloader), other on SCSI . May be instead of splitting filesystem it could be better to boot from "SCSI" completely and forget about "ATA"? Or there is no option ROM for SCSI boot in Hyper-V? -- Alexander Motin ___ 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: ATA controller and Hyper-V "synthetic storage driver" handle the IDE disks devices ( but not for the CD-ROM) Re: Hyper-V on FreeBSD
Hi! On 07.05.2013 10:40, Victor Miasnikov wrote: prevent default OS driver from attaching to emulated ATA controller when Hyper-V Disable both primary and secondary ATA controller prevent use CD-ROM device in VM ( guest) Because "synthetic storage driver" not handle CD-ROM devices ( IMHO, even more: Hyper-V host work with CD-ROM only as "PCI bus" device) A.M.> Then may be possibility of blocking/hiding specific ATA channels or A.M.> devices could be investigated. IMHO, this ( or some like this) must be investigated In any case, need carefully testing work CD-ROM ( primary for LiveCD and (or) .ISO for setup FreeBSD) in Hyper-V enviroment http://lists.freebsd.org/pipermail/freebsd-virtualization/2013-April/001180.html == . . . On 23.04.2013 17:07, Larry Melia wrote: . . . L.M.>>> Removing our ATA patches, on the other hand, results in a huge L.M.>>> performance loss. This is because the root file system is managed by the L.M.>>> ATA driver, which is emulated under Hyper-V. == VVM>> VVM>> Place on IDE disk only "\boot" ( and bootloader), other on SCSI . VVM>> A.M.> A.M.> May be instead of splitting filesystem it could be better to boot from A.M.> "SCSI" completely and forget about "ATA"? A.M.> Or there is no option ROM for SCSI boot in Hyper-V? A.M.> Yes, boot from SCSI disk in Hyper-V VM ( "guest") is impossible Best regards, Victor Miasnikov Blog: http://vvm.blog.tut.by/ ___ 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: VirtualBox + FreeBSD 9-STABLE == Frozen Ethernet
On 2013-05-06 2:49 PM, Norbert Beckmann wrote: To Marc G. Fournier I do not think it's an issue with VirtualBox. I am running VirtualBox under Solaris. And I never had problems with it. Guests: ubuntu, Windows 7, Linux Mint, FreeBSD, Chrome OS. But the people of VirtualBox themselves state that Windows is somewhat delicate (don't remember whether they meant as guest or as host, I think both). Which would be comprehensible, because Windows has never become a real multi user / multi process system as Unix was by birth (nearly). I can neither help concerning the freezing Ethernet nor did I encounter similar things (as far as I remember). My first thought is that its something in the vboxnet kernel module when using a bridge ... I think the problem has been getting progressively worse, with each upgrade, but since I upgrade both vBox and the kernel in tandem, I'm currently working on going 'back in time' with the code, see if I can find some 'stable point' ... If anyone with more knowledge can suggest any commands I can run to provide debug info, or such ... ? I don't mind debugging, just dont' know what to provide that is useful ... ___ 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"
