qemu-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Qemu-devel] USB-Mass-Storage and OpenBSD 4.7 problem


From: Sebastian Schuetz
Subject: [Qemu-devel] USB-Mass-Storage and OpenBSD 4.7 problem
Date: Mon, 16 Aug 2010 10:07:18 +0200
User-agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1.11) Gecko/20100713 Thunderbird/3.0.6

Hello list,


I am trying to write to an usb image file using OpenBSD 4.7 as guest and a fresh "QEMU emulator version 0.12.90". While trying to access the device I got the following error messages:


~~~~~~~~snip~~~~~~~~~~~
umass0 at uhub0 port 1 configuration 1 interface 0 "QEMU 0.12.90 QEMU USB HARDDRIVE" rev 1.00/0.00 addr 2
umass0: using SCSI over Bulk-Only
scsibus2 at umass0: 2 targets, initiator 0
sd0 at scsibus2 targ 1 lun 0: <QEMU, QEMU HARDDISK, 0.12> SCSI3 0/direct fixed
sd0: 1024MB, 512 bytes/sec, 2097152 sec total
umass0: Invalid CSW: sig 0x00000000 should be 0x53425355
umass0: Invalid CSW: sig 0x00000000 should be 0x53425355

# newfs /dev/rsd0a
/dev/rsd0a: 1024.0MB in 2097088 sectors of 512 bytes
6 cylinder groups of 202.47MB, 12958 blocks, 25984 inodes each
super-block backups (for fsck -b #) at:
umass0: Invalid CSW: sig 0x00000000 should be 0x53425355
newfs: wtfs: write error on block 192: Input/output error
# disklabel sd0
# /dev/rsd0c:
type: SCSI
disk: SCSI disk
label: QEMU HARDDISK
flags:
bytes/sector: 512
sectors/track: 63
tracks/cylinder: 255
sectors/cylinder: 16065
cylinders: 130
total sectors: 2097152
rpm: 3600
interleave: 1
boundstart: 0
boundend: 2097152
drivedata: 0

16 partitions:
#                size           offset  fstype [fsize bsize  cpg]
  a:          2097089               63  4.2BSD   2048 16384    1
  c:          2097152                0  unused
#
~~~~~~~~~~~snip~~~~~~~~~~~~


Using some hardware USB-Stick (plugged into the host and forward it to the guest) works fine. Anyone have a clue about it? Please cc me in your replies because I am not subscribed to the list.




Cheers,


Sebastian



reply via email to

[Prev in Thread] Current Thread [Next in Thread]