Re: [Qemu-devel] why -hda myimgfile can not work ??
On 5/4/07, tang peilei [EMAIL PROTECTED] wrote: I first create a img file using command qemu-img create myimgfile 10M then I use this img file in my qemu . (qemu -kernel ... -initrd ... -hda myimgfile). but when i am in linux shell , I can not find any hda info even in dmesg, and I can not fdisk or mount hda. who knows what is the problem ??? the problem might be in your guest linux kernel (no ATAPI/IDE modules or built-in). Could you send your kernel .config, and inform us on the revision of qemu you're using and the guest's arch you're using (x86, x86-64, arm...) ? That'd be a start... -- Christian
Re: [Qemu-devel] why -hda myimgfile can not work ??
thank you for your help. From: Christian MICHON [EMAIL PROTECTED] Reply-To: qemu-devel@nongnu.org To: qemu-devel@nongnu.org Subject: Re: [Qemu-devel] why -hda myimgfile can not work ?? Date: Fri, 4 May 2007 08:30:54 +0200 On 5/4/07, tang peilei [EMAIL PROTECTED] wrote: I first create a img file using command qemu-img create myimgfile 10M then I use this img file in my qemu . (qemu -kernel ... -initrd ... -hda myimgfile). but when i am in linux shell , I can not find any hda info even in dmesg, and I can not fdisk or mount hda. who knows what is the problem ??? the problem might be in your guest linux kernel (no ATAPI/IDE modules or built-in). Could you send your kernel .config, and inform us on the revision of qemu you're using and the guest's arch you're using (x86, x86-64, arm...) ? That'd be a start... the target arch is arm. and I was just use the download qemu arm-test kernel and initrd file to run. It has a config.gz in /proc, but I can not copy it out, becase the net can not work in my qemu, and the hda can not use .Is there any other way to copy data from qemu system to my phy system ? -- Christian _ 享用世界上最大的电子邮件系统― MSN Hotmail。 http://www.hotmail.com
Re: [Qemu-devel] why -hda myimgfile can not work ??
On 5/4/07, tang peilei [EMAIL PROTECTED] wrote: the target arch is arm. and I was just use the download qemu arm-test kernel and initrd file to run. It has a config.gz in /proc, but I can not copy it out, becase the net can not work in my qemu, and the hda can not use .Is there any other way to copy data from qemu system to my phy system ? are you using http://fabrice.bellard.free.fr/qemu/arm-test-0.2.tar.gz ? what is the exact cmd line you use ? -- Christian
Re: [Qemu-devel] why -hda myimgfile can not work ??
thank you very much. From: Paul Brook [EMAIL PROTECTED] Reply-To: qemu-devel@nongnu.org To: qemu-devel@nongnu.org CC: tang peilei [EMAIL PROTECTED] Subject: Re: [Qemu-devel] why -hda myimgfile can not work ?? Date: Fri, 4 May 2007 14:13:57 +0100 the target arch is arm. and I was just use the download qemu arm-test kernel and initrd file to run. It has a config.gz in /proc, but I can not copy it out, becase the net can not work in my qemu, and the hda can not use .Is there any other way to copy data from qemu system to my phy system The ARM boards do not support IDE. Some of them have a SCSI controller instead, as described in the documentation. As the ARM boards do not support IDE, and my net can not work. How can I copy files from QEMU system to my phy system ??? _ 与联机的朋友进行交流，请使用 MSN Messenger: http://messenger.msn.com/cn
Re: [Qemu-devel] why -hda myimgfile can not work ??
tang peilei wrote: The ARM boards do not support IDE. Some of them have a SCSI controller instead, as described in the documentation. As the ARM boards do not support IDE, and my net can not work. How can I copy files from QEMU system to my phy system ??? I don't really understand what your question is about. Are you running Linux on a physical ARM system or a virtual QEMU ARM platform? I run Armedslack and Debian in QEMU ARM emulation with a virtual SCSI hard drive and user mode networking and both work fine. You can use any network file system you want. I am using FUSE and SSHFS and it functions well. You can also use Samba, NFS or something else. I have attached my scripts for Armedslack (http://www.armedslack.org) and there are directions for Debian at http://www.aurel32.net. If it works for me it should also work for you. QEMU CVS as of 20070420 didn't work for me though, but 0.9.0 release does. Sunil #!/bin/sh # # Armedslack # # Running # # qemu-system-arm-orig \ qemu-system-arm \ -M versatilepb \ -m 256 \ -kernel vmlinuz-versatile-2.6.20 \ -append ro root=/dev/sda2 \ -hda ata01.dsk \ -redir tcp:10023::10022 \ -k en-us #!/bin/sh # # Armedslack # # Installation # qemu-system-arm \ -M versatilepb \ -m 256 \ -kernel vmlinuz-versatile-2.6.20 \ -initrd color.gz \ -append rw root=/dev/ram0 ramdisk_size=9900 \ -hda ata01.dsk \ -cdrom armedslack-current-dvd.iso \ -redir tcp:10023::10022 \ -k en-us
Re: [Qemu-devel] why -hda myimgfile can not work ??
From: Sunil Amitkumar Janki [EMAIL PROTECTED] Reply-To: qemu-devel@nongnu.org To: qemu-devel@nongnu.org Subject: Re: [Qemu-devel] why -hda myimgfile can not work ?? Date: Fri, 04 May 2007 16:01:40 +0200 tang peilei wrote: The ARM boards do not support IDE. Some of them have a SCSI controller instead, as described in the documentation. As the ARM boards do not support IDE, and my net can not work. How can I copy files from QEMU system to my phy system ??? I don't really understand what your question is about. Are you running Linux on a physical ARM system or a virtual QEMU ARM platform? My phy system is my PC, a computer with ubuntu. and qemu-system-arm is running in this PC . I run Armedslack and Debian in QEMU ARM emulation with a virtual SCSI hard drive and user mode networking and both work fine. You can use any network file system you want. I am using FUSE and SSHFS and it functions well. You can also use Samba, NFS or something else. I have attached my scripts for Armedslack (http://www.armedslack.org) and there are directions for Debian at http://www.aurel32.net. If it works for me it should also work for you. QEMU CVS as of 20070420 didn't work for me though, but 0.9.0 release does. Sunil I also use command like you, but I can not find any hard disk info in qemu's system.(in dmesg's output). Are you create your disk img with command qemu-img ??? #!/bin/sh # # Armedslack # # Running # # qemu-system-arm-orig \ qemu-system-arm \ -M versatilepb \ -m 256 \ -kernel vmlinuz-versatile-2.6.20 \ -append ro root=/dev/sda2 \ -hda ata01.dsk \ -redir tcp:10023::10022 \ -k en-us #!/bin/sh # # Armedslack # # Installation # qemu-system-arm \ -M versatilepb \ -m 256 \ -kernel vmlinuz-versatile-2.6.20 \ -initrd color.gz \ -append rw root=/dev/ram0 ramdisk_size=9900 \ -hda ata01.dsk \ -cdrom armedslack-current-dvd.iso \ -redir tcp:10023::10022 \ -k en-us _ 免费下载 MSN Explorer: http://explorer.msn.com/lccn/
Re: [Qemu-devel] why -hda myimgfile can not work ??
tang peilei wrote: My phy system is my PC, a computer with ubuntu. and qemu-system-arm is running in this PC . I also use command like you, but I can not find any hard disk info in qemu's system.(in dmesg's output). Are you create your disk img with command qemu-img ??? I create my image using qemu-img create -f qcow ata00.dsk 10G. You could substitute scsi00.dsk for a scsi hard drive though. Sunil Linux version 2.6.20-versatile ([EMAIL PROTECTED]) (gcc version 4.1.1) #1 Tue Feb 13 01:01:22 GMT 2007 CPU: ARM926EJ-S [41069265] revision 5 (ARMv5TEJ), cr=3137 Machine: ARM-Versatile PB Memory policy: ECC disabled, Data cache writeback On node 0 totalpages: 65536 DMA zone: 512 pages used for memmap DMA zone: 0 pages reserved DMA zone: 65024 pages, LIFO batch:15 Normal zone: 0 pages used for memmap CPU0: D VIVT write-through cache CPU0: I cache: 4096 bytes, associativity 4, 32 byte lines, 32 sets CPU0: D cache: 65536 bytes, associativity 4, 32 byte lines, 512 sets Built 1 zonelists. Total pages: 65024 Kernel command line: ro root=/dev/sda2 PID hash table entries: 1024 (order: 10, 4096 bytes) Console: colour dummy device 80x30 Dentry cache hash table entries: 32768 (order: 5, 131072 bytes) Inode-cache hash table entries: 16384 (order: 4, 65536 bytes) Memory: 256MB = 256MB total Memory: 254208KB available (5092K code, 406K data, 104K init) Calibrating delay loop... 153.19 BogoMIPS (lpj=765952) Security Framework v1.0.0 initialized Capability LSM initialized Mount-cache hash table entries: 512 CPU: Testing write buffer coherency: ok NET: Registered protocol family 16 PCI core found (slot 11) PCI: bus0: Fast back to back transfers disabled PCI map irq: slot 0, pin 1, devslot 12, irq: 27 SCSI subsystem initialized usbcore: registered new interface driver usbfs usbcore: registered new interface driver hub usbcore: registered new device driver usb NET: Registered protocol family 2 IP route cache hash table entries: 2048 (order: 1, 8192 bytes) TCP established hash table entries: 8192 (order: 3, 32768 bytes) TCP bind hash table entries: 4096 (order: 2, 16384 bytes) TCP: Hash tables configured (established 8192 bind 4096) TCP reno registered NetWinder Floating Point Emulator V0.97 (double precision) VFS: Disk quotas dquot_6.5.1 Dquot-cache hash table entries: 1024 (order 0, 4096 bytes) Installing knfsd (copyright (C) 1996 [EMAIL PROTECTED]). EFS: 1.0a - http://aeschi.ch.eu.org/efs/ QNX4 filesystem 0.2.3 registered. JFS: nTxBlock = 1986, nTxLock = 15890 SGI XFS with ACLs, security attributes, no debug enabled SGI XFS Quota Management subsystem BeFS version: 0.9.3 OCFS2 1.3.3 OCFS2 Node Manager 1.3.3 OCFS2 DLM 1.3.3 OCFS2 DLMFS 1.3.3 OCFS2 User DLM kernel interface loaded io scheduler noop registered io scheduler anticipatory registered (default) io scheduler deadline registered io scheduler cfq registered CLCD: unknown LCD panel ID 0x1000, using VGA CLCD: Versatile hardware, VGA display Clock CLCDCLK: setting VCO reg params: S=1 R=99 V=98 Console: switching to colour frame buffer device 80x30 Serial: AMBA PL011 UART driver dev:f1: ttyAMA0 at MMIO 0x101f1000 (irq = 12) is a AMBA/PL011 dev:f2: ttyAMA1 at MMIO 0x101f2000 (irq = 13) is a AMBA/PL011 dev:f3: ttyAMA2 at MMIO 0x101f3000 (irq = 14) is a AMBA/PL011 fpga:09: ttyAMA3 at MMIO 0x10009000 (irq = 38) is a AMBA/PL011 RAMDISK driver initialized: 16 RAM disks of 8192K size 1024 blocksize loop: loaded (max 8 devices) smc91x.c: v1.1, sep 22 2004 by Nicolas Pitre [EMAIL PROTECTED] eth0: SMC91C11xFD (rev 1) at d0946000 IRQ 25 [nowait] eth0: Ethernet addr: 52:54:00:12:34:56 eth0: No PHY found PCI: enabling device :00:0c.0 (0140 - 0143) sym0: 895a rev 0x0 at pci :00:0c.0 irq 27 sym0: No NVRAM, ID 7, Fast-40, LVD, parity checking sym0: SCSI BUS has been reset. scsi0 : sym-2.2.3 scsi 0:0:0:0: Direct-Access QEMU QEMU HARDDISK0.9. PQ: 0 ANSI: 3 target0:0:0: tagged command queuing enabled, command queue depth 16. target0:0:0: Beginning Domain Validation target0:0:0: Domain Validation skipping write tests target0:0:0: Ending Domain Validation scsi 0:0:2:0: CD-ROMQEMU QEMU CD-ROM 0.9. PQ: 0 ANSI: 3 target0:0:2: tagged command queuing enabled, command queue depth 16. target0:0:2: Beginning Domain Validation target0:0:2: Domain Validation skipping write tests target0:0:2: Ending Domain Validation SCSI device sda: 20971520 512-byte hdwr sectors (10737 MB) sda: Write Protect is off sda: Mode Sense: 13 00 00 00 SCSI device sda: write cache: enabled, read cache: enabled, doesn't support DPO or FUA SCSI device sda: 20971520 512-byte hdwr sectors (10737 MB) sda: Write Protect is off sda: Mode Sense: 13 00 00 00 SCSI device sda: write cache: enabled, read cache: enabled, doesn't support DPO or FUA sda: sda1 sda2 sda3 sda4 sd 0:0:0:0: Attached scsi disk sda sr0: scsi3-mmc drive: 16x/50x cd/rw xa/form2 cdda tray Uniform CD-ROM driver Revision: 3.20 sr 0:0:2:0: Attached scsi CD-ROM sr0 sd 0:0:0:0: Attached scsi generic
Re: [Qemu-devel] why -hda myimgfile can not work ??
yes, when I rebuild my kernel with scsi support ,the hard disk sda could be found, thank you very much . From: Sunil Amitkumar Janki [EMAIL PROTECTED] Reply-To: qemu-devel@nongnu.org To: qemu-devel@nongnu.org Subject: Re: [Qemu-devel] why -hda myimgfile can not work ?? Date: Fri, 04 May 2007 17:10:33 +0200 tang peilei wrote: My phy system is my PC, a computer with ubuntu. and qemu-system-arm is running in this PC . I also use command like you, but I can not find any hard disk info in qemu's system.(in dmesg's output). Are you create your disk img with command qemu-img ??? I create my image using qemu-img create -f qcow ata00.dsk 10G. You could substitute scsi00.dsk for a scsi hard drive though. Sunil Linux version 2.6.20-versatile ([EMAIL PROTECTED]) (gcc version 4.1.1) #1 Tue Feb 13 01:01:22 GMT 2007 CPU: ARM926EJ-S [41069265] revision 5 (ARMv5TEJ), cr=3137 Machine: ARM-Versatile PB Memory policy: ECC disabled, Data cache writeback On node 0 totalpages: 65536 DMA zone: 512 pages used for memmap DMA zone: 0 pages reserved DMA zone: 65024 pages, LIFO batch:15 Normal zone: 0 pages used for memmap CPU0: D VIVT write-through cache CPU0: I cache: 4096 bytes, associativity 4, 32 byte lines, 32 sets CPU0: D cache: 65536 bytes, associativity 4, 32 byte lines, 512 sets Built 1 zonelists. Total pages: 65024 Kernel command line: ro root=/dev/sda2 PID hash table entries: 1024 (order: 10, 4096 bytes) Console: colour dummy device 80x30 Dentry cache hash table entries: 32768 (order: 5, 131072 bytes) Inode-cache hash table entries: 16384 (order: 4, 65536 bytes) Memory: 256MB = 256MB total Memory: 254208KB available (5092K code, 406K data, 104K init) Calibrating delay loop... 153.19 BogoMIPS (lpj=765952) Security Framework v1.0.0 initialized Capability LSM initialized Mount-cache hash table entries: 512 CPU: Testing write buffer coherency: ok NET: Registered protocol family 16 PCI core found (slot 11) PCI: bus0: Fast back to back transfers disabled PCI map irq: slot 0, pin 1, devslot 12, irq: 27 SCSI subsystem initialized usbcore: registered new interface driver usbfs usbcore: registered new interface driver hub usbcore: registered new device driver usb NET: Registered protocol family 2 IP route cache hash table entries: 2048 (order: 1, 8192 bytes) TCP established hash table entries: 8192 (order: 3, 32768 bytes) TCP bind hash table entries: 4096 (order: 2, 16384 bytes) TCP: Hash tables configured (established 8192 bind 4096) TCP reno registered NetWinder Floating Point Emulator V0.97 (double precision) VFS: Disk quotas dquot_6.5.1 Dquot-cache hash table entries: 1024 (order 0, 4096 bytes) Installing knfsd (copyright (C) 1996 [EMAIL PROTECTED]). EFS: 1.0a - http://aeschi.ch.eu.org/efs/ QNX4 filesystem 0.2.3 registered. JFS: nTxBlock = 1986, nTxLock = 15890 SGI XFS with ACLs, security attributes, no debug enabled SGI XFS Quota Management subsystem BeFS version: 0.9.3 OCFS2 1.3.3 OCFS2 Node Manager 1.3.3 OCFS2 DLM 1.3.3 OCFS2 DLMFS 1.3.3 OCFS2 User DLM kernel interface loaded io scheduler noop registered io scheduler anticipatory registered (default) io scheduler deadline registered io scheduler cfq registered CLCD: unknown LCD panel ID 0x1000, using VGA CLCD: Versatile hardware, VGA display Clock CLCDCLK: setting VCO reg params: S=1 R=99 V=98 Console: switching to colour frame buffer device 80x30 Serial: AMBA PL011 UART driver dev:f1: ttyAMA0 at MMIO 0x101f1000 (irq = 12) is a AMBA/PL011 dev:f2: ttyAMA1 at MMIO 0x101f2000 (irq = 13) is a AMBA/PL011 dev:f3: ttyAMA2 at MMIO 0x101f3000 (irq = 14) is a AMBA/PL011 fpga:09: ttyAMA3 at MMIO 0x10009000 (irq = 38) is a AMBA/PL011 RAMDISK driver initialized: 16 RAM disks of 8192K size 1024 blocksize loop: loaded (max 8 devices) smc91x.c: v1.1, sep 22 2004 by Nicolas Pitre [EMAIL PROTECTED] eth0: SMC91C11xFD (rev 1) at d0946000 IRQ 25 [nowait] eth0: Ethernet addr: 52:54:00:12:34:56 eth0: No PHY found PCI: enabling device :00:0c.0 (0140 - 0143) sym0: 895a rev 0x0 at pci :00:0c.0 irq 27 sym0: No NVRAM, ID 7, Fast-40, LVD, parity checking sym0: SCSI BUS has been reset. scsi0 : sym-2.2.3 scsi 0:0:0:0: Direct-Access QEMU QEMU HARDDISK0.9. PQ: 0 ANSI: 3 target0:0:0: tagged command queuing enabled, command queue depth 16. target0:0:0: Beginning Domain Validation target0:0:0: Domain Validation skipping write tests target0:0:0: Ending Domain Validation scsi 0:0:2:0: CD-ROMQEMU QEMU CD-ROM 0.9. PQ: 0 ANSI: 3 target0:0:2: tagged command queuing enabled, command queue depth 16. target0:0:2: Beginning Domain Validation target0:0:2: Domain Validation skipping write tests target0:0:2: Ending Domain Validation SCSI device sda: 20971520 512-byte hdwr sectors (10737 MB) sda: Write Protect is off sda: Mode Sense: 13 00 00 00 SCSI device sda: write cache: enabled, read cache: enabled, doesn't support DPO or FUA SCSI device sda: 20971520 512-byte hdwr sectors (10737 MB) sda: Write Protect is off sda: Mode
