similar to: Floppy controller

Hi, Is it possible add a floppy image to a paravirtualized domain? I have the following lines in the config file: <devices> <disk type=''file'' device=''disk''> <driver name=''tap'' type=''aio''/> <source file=''/var/lib/xen/images/proba1.img''/> <target

Trying to be not long, on x86 I have 3 floppies images boot, root-1, root-2 Booting from boot image with no problem, I try reading root-1 and root-2 image in raw format. Reading root-1 and root-2 is made from boot init script, using klibc-1.5.9 or klibc-1.5.10 with debian insmod patch, and a vanilia linux-2.6.24.7 root-1 and 2 images are smaller than 1440 kB and are made the same way with cd

Hello, I successfuly run Centos 5.1 domU in Centos 5.1 dom0. But I still have some minor issues/errors/warnings while booting I'd like to fix and here are my questions: 1. How to disable loading usb host controler module: [...from dmesg... ] Loading uhci-hcd.ko module USB Universal Host Controller Interface driver v3.0 insmod: error inserting '/lib/uhci-hcd.ko': -1 No such

Hi - daft one for Friday morning coffee break: I have been trying to mount floppies on a couple of CentOS5 servers - the usual "mount /dev/fd0 /mnt/floppy" (yes, /mnt/floppy exists!). On both servers, the mount command just doesn't come back and I have to hit CTRL-C. I have tried different media and also changed the floppy drive on one server, /dev/fd0 is seen as present on both

Hi all, i need to use openbsd 3.9 as domU. So I downloaded an image and used my standard config file: kernel = "/boot/vmlinuz-2.6.16.18-xenU" memory = 128 name = "openbsd.3-9" disk = [''file:/xen/openbsd/disk,sda1,w''] root = "/dev/sda1 ro" but when I start the domU and attach the console I only see following lines befor it crashs. Any

Hi, when i try to set up a DomU with the following configuration: dir = /home/xen debootstrap = 1 size = 4Gb memory = 128Mb swap = 128Mb fs = ext3 dist = dapper image = sparse dhcp = 1 kernel = /boot/xen0-linux-2.6.16-11.1-generic initrd = /boot/xen-modules-2.6.16-11.1-generic mirror = http://archive.ubuntu.com/ubuntu/ and try to start it with: root@ubuntu:/etc/xen# xm create dapperDomU.cfg -c

It is now possible to build a bootable floppy image which contains HDT, with my patch applied to Erwans HDT branch: http://git.zytor.com/?p=users/erwan/hdt.git;a=commit;h=16b37fe2266c920087f88cdec94243b71218d871 Unpack the Syslinux archive and build whole Syslinux first, then cd to ./com32/hdt/ and make hdt.img $ make $ cd ./com32/hdt/ $ make hdt.img Now you have a 2.88 MB floppy image which

Hello, I am trying to boot a FC6 domU on Xen 3.2 (compiled on a FC6 system). After compiling Xen 3.2 successfully on FC6 and making the ramdisk, I modified the conf.grub as shown below. With this, I was able to boot xen. ------------------------------ --------------------------------------------------------------------------------- # grub.conf generated by anaconda # # Note that you do not have

Thanks for your response, and how would you suggest that one would fix that? It hangs in the boot process! woody ==================== From: Christopher Clark <christopher.w.clark@gmail.com> [Add to Address Book] [View Source] To: "tarawa1943@comcast.net" <tarawa1943@comcast.net> Cc: xen-devel@lists.xensource.com Subject: Re: [Xen-devel] xen-unstable dom0 boot "Floppy

Dear All, I now have my Dom0 working nicely running Ubuntu Jaunty. I am now trying to boot Images I had been using without problem under my previous Xen installation (Gentoo). For the Dom0 host kernel I am using the debian package linux-image-2.6.26-2-xen-686_2.6.26-15_i386.deb. The DomU kernel is one I compiled myself a while ago (sometime last year and has always worked on Gentoo and I think

Hi, I am still trying to get kick-start centos in my vmware5 because pxe cannot find the pxe server. I do not control the dhcp or pxe server. I have both my kickstart file and my iso image for centos6.5 on my vmware datastore, but am trying to run my kickstart file from VMware guest. Can I tell the command line to run from the datastore in VMWare? Or must I convert my kickstart file to a

Hello everybody, I''am trying to make an installation of a sles9 based system. In order to install this system after booting a floppy disk (or usb) should be "inserted" with a auto configuration file. My problem is what ever I try I can not attach a floppy image to the sles9. the command I tried is xm block-attach <dom nr> file://path/to/floppy.img /dev/fd0 w After

has anyone received from the build/boot of dom0 "Floppy drive(s): fd0 is 1.44M" when put on a thinkpad without a floppy drive? woody _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

After formatting a floppy to MSDOS format and using syslinux /dev/fd0, I successfully installed ldlinux.sys to the root directory of the floppy. Then I created a syslinux.cfg under the root directtory of this floppy to load the linux kernel in my first hard disk, 3rd partition, boot folder. The file system of this partition is ext3. The floppy has a FAT file system. This config file is listed

Thanks for responses. I use GRUB as my bootloader in my hard disk now. I have a Windows in sda1, Ubuntu in sda3. If I want to install extlinux to boot Ubuntu, should I follow the steps below? 1. in Ubuntu, go to extlinux folder, run command ./extlinux --install /boot 2. create an extlinux.conf in/boot 3. cd ../mbr 4. cat mbr.bin > /dev/sda (or use dd if=mbr.bin of=/dev/sda bs=404 count=1)

Hi All, I am trying to attach floppy virtual image to Windows domU. Either it is not attaching or domU is not showing floppy drive? domU config: 1. disk = [ ''file:/root/xenwin.img,hda,w'', ''file:/opt/Windows-Xp.iso,hdc:cdrom,r'', ''file:/root/win-boot.img,fd:floppy,r'' ] boot = "cda" In above format the window domU is booting but

Dear Sir, I have everything set up on my red hat Linux 7.1 linux box. For sometime I could mount cd's and floppies automatically, but now something seems to have gone wrong. I can't mount my floppy(/dev/fd0) and cdrom(/dev/cdrom) manually or automatically. At startup it says ... /dev/fd0 is not a valid block device. /dev/cdrom is write protected...mounting read only! mount: No

Hi, I suspect this bug has already been reported, but here it is just in case: the bootable floppies I produced with syslinux 2.10 (just by running 'syslinux /dev/fd0') are not able to 'remember' the parameters I pass at the boot prompt. Namely, to boot a USB pen from one of my floppies I pass something like boot: MoviX MEDIA=usb (where MoviX is the boot label) but the usb boot

Hi as described on the syslinux pxe webpage: A multi-hardware boot floppy is included with Windows Server 2000 and 2003. A company called Argon Technology used to offer a free-as-in-beer updated version, but is seems to have gone fully commercial. This floppy (which can also be burned to a CD using El Torito in floppy-emulation mode), is known to work with PXELINUX 2.03 or later only I'm

Hi there, http://www.seagate.com/support/disc/download/seatoold_en.exe Seagate offers a Windows executable (needs Win98 or better, 1,9MB) that should create 2 bootable floppy disks that contain a harddrive check program. Invoking "wine seatoold_en.exe" works, but when the floppy should be written, an error occurs "insert 1.44 MB...click retry". I tried to mount a DOS