similar to: isolinux failing to boot on SCSI system

Attached patch allows isolinux to boot from a CDROM attached to a NCR/Symbios/LSIlogic SCSI controller (bios version 4.19). It appears this bios can't read more than 1 sector at the time using the ah=42h int13 call. The isolinux boot was failing early on when 4 sector are read. (bios returned error 0 !) I'm not sure if the same 'getlinsec' routine is called upon later to load

Hello, This afternoon I wanted to upgrade to 7.1 two good old dell PowerEdge servers which were running FreeBSD 6.x. It went fine and quickly on the poweredge 1950, but it failed completely on the poweredge 1850. Facts: - boot cd and setup / operation of freebsd 6.x or 7.0 is fine Message log abstract: $ uname -v FreeBSD 7.0-RELEASE-p7 #0: Sun Dec 21 08:31:52 UTC 2008

On Mon, Aug 12, 2013 at 06:17:51PM +0800, Timon Wang wrote: > Yes, SCSI bus likes pass through a shared LUN to the vm, and I am > using a shared LUN for 'share' purpose. > > I found a post that vmware use lsilogic bus for the shared disk, but > my qemu/kvm version can't support lsilogic bus. > > I'm tring to update qemu/kvm version for lsilogic bus support.

I want to install CentOS 5.1 with hardware RAID on an HP DL140 G3 server that I have here for testing. It prompts me for a storage controller. According to this readme page for the latest driver at ftp://ftp.hp.com/pub/softlib2/software1/pubsw-linux/p1463703615/v44436/mpt linux-4.00.13.01-2.rhel5.i686.dd.gz.txt CentOS 5 should already contain a "default driver version contained in the Red

Dear Sirs. It seems to me a never ending story. We run a box with a TYAN Thunder 2500 Dual SMP mainboard, 2GB ECC Tyan certified memory, AMI Enterprise 1600 RAID adapter and additional Intel 1000/Pro server type (64 bit) GBit LAN NIC. With FreeBSD 4.8 this was stable, but to achive this state was really hard! It is a story similar to that what happend when we changed towards FreeBSD

Just curious but how long has ESX support been in libvirt? Also I noticed this error when accessing one of my windows vms: error: internal error Expecting VMX entry 'scsi0.virtualDev' to be 'buslogic' or 'lsilogic' but found 'lsisas1068' Not sure whether this is an enhancement, defect, or not supported at this time. Thanks. -Jon

Dual Opteron system running ext3 atop drbd (network RAID) devices, which, in turn, are atop LVM logical volumes. The underlying device is hardware SCSI RAID via a LSILogic HBA. The kernel is vanilla 2.6.13 on a Gentoo-based system. A panic occurred, which contains references to ext3 code. I'm not sure how others manage to get these typed out, but I'm manually typing it from

Hello, We're getting around to upgrading our mail server and here are the quick specs: MegaRAID SCSI 320-2X http://www.lsilogic.com/products/megaraid/scsi_320_2x.html TYAN Transport TA26 B2882T26U8H 2U Barebone Server-Rackmount - Retail http://www.newegg.com/Product/Product.asp?item=N82E16856152007 plus RAM, CPU and 4 SCSI drives setup in a RAID-5 Is that MegaRAID controller supported in

Many people seem to wait for the announcement of CentOS 6.0, so I want to share some test results I did with SL 6.0.. The actual 6.0 kernel can NOT allocate tape buffers when the server is heavily loaded at least on some LSILogic hardware. There is a big problem of slab buffer increase that can cause reboot/freeze of the server under load. Reported by many and verified by me :-( So perhaps

On Sat, Aug 10, 2013 at 11:14:39AM +0800, Timon Wang wrote: > I have tryied change the disk bus to SCSI, add a SCSI controller whose > model is virtio-scsi, still can't setup the RAC instance. > > I tried to use windows 2008 Failover Cluster feature to setup a a > Failover Cluster instead, and I can't find any cluster disk to share > between two nodes. So when Failover

Hi, Dear Mr/Mrs. I have two questions ask for help: my virt-manager and libvirt version is : linux-vaan:~ # rpm -q libvirt libvirt-0.8.5-1.2.i586 linux-vaan:~ # uname -a Linux linux-vaan 2.6.34-12-desktop #1 SMP PREEMPT 2010-06-29 02:39:08 +0200 i686 i386 GNU/Linux linux-vaan:~ # rpm -q virt-manager virt-manager-0.8.5-3.1.i586 linux-vaan:~ # cat /etc/SuSE-release openSUSE 11.3 (i586) VERSION =

Hello, While shopping for another 3Ware card, I found that this market has gotten much larger since I bought my 6500. So I started looking at the various cards while browsing the hardware notes for FreeBSD 4.8 and 5.1. So I'm wondering if anyone can provide some insight here. -3Ware has a whole new series of cards. The twe(4) manpage states that only 5xxx and 6xxx series cards are

In fact, I discovered that the bug is caused when there is no primary hard disk image (no hard disk 0). When an HD image is created and attached, ISOLINUX works well: ISOLINUX 1.75 2002-06-14 Copyright (C) 1994-2002 H. Peter Anvin isolinux: Starting up, DL = 99 isolinux: Loaded spec packet OK, drive = 99 isolinux: Sector size appears to be 0800 isolinux: Loading main image from LBA = 0000001C

Hello friends! HAXM is a hardware-assisted virtualization engine (hypervisor) that uses Intel Virtualization Technology to speed up IA (x86/ x86_64) emulation on a host machine running Windows or macOS. Latest Isolinux 6.03 hangs under VM after "Main image LBA =...". Please, help us investigate the root of the problem. Bug on github: https://github.com/intel/haxm/issues/15 Thank you!

Hello List, I have a problem with an Onborad scsci, that won't boot a isolinux-cd: anyone got a clue? Mainboard is ASUS-CUV4X-DLS with onboard LSI 35c1010-33 Controller. Board-Bios is Award Medaillion 6.0 and Controller Bios is Symbios SDMS v4.0 (4.18.02) The CDRW device to boot from is a Yamaha CRW2100S Rev1.0H I tried Isolinux 1.63 and 1.66 with similar "success": here's

I have tried to use isolinux 2.05, and I am running into a problem where it will not boot. I have previously used version 1.66, and the older version works just fine. Changing nothing except dropping the new version in does not work. Below is all of the relevant info, I believe. This occurs on multiple machines with different BIOS. I am currently in process of doing a binary search to find the

Hi, Ady wrote: > If a specific BIOS' CHS/LBA translations cannot cope with the above, it > is no surprise that we get some mess, somewhere. Currently my suspicion is that the isohdpfx.S code simply mishandles the two conversion factors which it correctly got from BIOS call INT 13H AH 8. > Boot System ID : First : Last : Relative : Number of: > Flag

Hi, funny or enlightening observation: With my qemu-system-i386 it would work if the detected Heads/Cylinder and Sectors/Head factors would change positions ! The effective read operation seems to use H/C = 32 , S/H = 63. The correct LBA would be addressed by H/C = 63 , S/H = 32. -------------------------------------------------------------------------- Reasoning: I have transplanted the

Yes, SCSI bus likes pass through a shared LUN to the vm, and I am using a shared LUN for 'share' purpose. I found a post that vmware use lsilogic bus for the shared disk, but my qemu/kvm version can't support lsilogic bus. I'm tring to update qemu/kvm version for lsilogic bus support. On 8/12/13, Stefan Hajnoczi <stefanha@gmail.com> wrote: > On Sat, Aug 10, 2013 at

Thanks, i have tried virtio-scsi and LSI SCSI controller, by using a local file or a LUN as disk. Both raw and qcow2 disk format are be verified, but no way to make windows Failover Cluster and Oracle RAC work correctly. Actually, Oracle RAC and Windows Failover Cluster needs "share" storage like iscsi disk and fc disk to work correctly. In iscsi situation, we can use ip network for