Re: Problems with 6.0-release inside vmware 5

From: João Carlos Mendes Luís (jonny_at_jonny.eng.br)
Date: 11/06/05

  • Next message: FreeBSD Tinderbox: "[releng_6 tinderbox] failure on amd64/amd64" 
    Date: Sun, 06 Nov 2005 03:28:38 -0200
To: Joao Barros <joao.barros@gmail.com>

    Joao Barros wrote:
    > On 11/6/05, João Carlos Mendes Luís <jonny@jonny.eng.br> wrote:
    >
    >>Hi,
    >>
    >> I tried to install a vmware 5 virtual machine with 6.0-RELEASE, using
    >>physical partitions. In this mode, even ATA disks appear as SCSI to the guest
    >>system. In VMWARE ghest, this also means a buslogic mpt controller.
    >>
    >> Up to 5.4-stable, this worked ok. But at 6.0-release, the mpt controller is
    >>detectd, but no disk is found. Any hints?
    >
    >
    > I have 6.0 working under VMWare 5.0 using physical partitions.
    > When you add a new disk you are given an advanced option where you can
    > specify IDE or SCSI. VMWare by default goes SCSI, so you must have
    > missed it as it's very common to happen.

        For me, it only asks for IDE or SCSI on logical disks. Maybe because I am
    not using the whole disk, but only some of its partitions.

        My main intent is to be able to dual boot Windows and FreeBSD, and keep both
    running, with Windows vmware hosting FreeBSD (I would prefer the other way, but
    vmware3 is a bit old). I need a secondary root partition, because of kernel and
    config changes, but the data partitions could be shared.

       BTW: Maybe this can help. I'll copy scsi@, maybe they can find this problem
    quicker.

        The only messages sent by the mpt driver are:

    mpt0: <LSILogic 1030 Ultra4 Adapter> port 0x1080-0x10ff mem
    0xec800000-0xec800fff irq 17 at device 16.0 on pci0
    mpt0: [GIANT-LOCKED]
    mpt0: MPI Version=1.2.0.0
    mpt0: Unhandled Event Notify Frame. Event 0xa.

       If I enable verbose booting, there are to many messages for me to understand
    each one.

        Also: In the install CD fixit shell, "camcontrol devlist" finds no device,
    but "camcontrol devlist -v" finds two VMware devices <VMware, Virtual S 1.0>, at
    scbus target 0 and 1. If I do a "camcontrol rescan all", and then another
    "camcontrol devlist -v", even these devices disappear.

        I did also try disabling ACPI during boot, but no luck.

    _______________________________________________
    freebsd-stable@freebsd.org mailing list
    http://lists.freebsd.org/mailman/listinfo/freebsd-stable
    To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org"

  • Next message: FreeBSD Tinderbox: "[releng_6 tinderbox] failure on amd64/amd64"

    Relevant Pages

    • Re: kernel-2.6.9-1.6_FC2 boot failure where kernel-2.6.9-1.3_FC2 works
      ... Partitions are also static. ... Disk device names in Solaris do not change, as long as you don't change ... SCSI ID of the disk, SCSI controller the disk is on, or PCI slot the ...
      (Fedora)
    • Re: [opensuse] vmware and fake scsi devs
      ... scsi disk x. ... One such application is vmware. ... I always boot VMware with physical SCSI drives and it works! ...
      (SuSE)
    • Re: FC2 and VMWare
      ... >> I can't help you fix it, but I can tell you that I am running VMWare ... > and another primary partition with several logical partitions: ... Samba support, and shared disk support, you should be able to get your ...
      (linux.redhat)
    • Re: [opensuse] vmware and fake scsi devs
      ... scsi disk x. ... One such application is vmware. ... I boot on a SATA disk, but you can choose to install the system on the IDE disk as well. ...
      (SuSE)
    • Re: Need to change disk number
      ... Is your scsi card the type that has its own bootable bios? ... Boot with your XP CD and delete all partitions. ... Install second IDE Hard Disk 1. ...
      (microsoft.public.windowsxp.hardware)
    Loading