Re: [Qemu-discuss] DMAR errors with iommu emulation enabled

2017-02-07 Thread Jintack Lim 
On Tue, Feb 7, 2017 at 1:03 PM, Alex Williamson
 wrote:
> On Tue, 7 Feb 2017 12:53:04 -0500
> Jintack Lim  wrote:
>
>> Thanks Alex, I appreciate your help.
>>
>> On Tue, Feb 7, 2017 at 12:09 PM, Alex Williamson
>>  wrote:
>> > On Tue, 7 Feb 2017 11:46:57 -0500
>> > Jintack Lim  wrote:
>> >
>> >> Adding CC and some more information.
>> >
>> > $ ./scripts/get_maintainer.pl -f ./hw/i386/intel_iommu.c
>> > get_maintainer.pl: No maintainers found, printing recent contributors.
>> > get_maintainer.pl: Do not blindly cc: them on patches!  Use common sense.
>>
>> Oh, I got it. Thanks!
>>
>> >
>> > "Michael S. Tsirkin"  (commit_signer:54/35=100%)
>> > Peter Xu  (commit_signer:28/35=80%)
>> > Paolo Bonzini  (commit_signer:6/35=17%)
>> > Jason Wang  (commit_signer:5/35=14%)
>> > "Radim Krčmář"  (commit_signer:5/35=14%)
>> > qemu-de...@nongnu.org (open list:All patches CC here)
>> >
>> >> On Tue, Feb 7, 2017 at 5:07 AM, Jintack Lim  
>> >> wrote:
>> >> > Hi,
>> >> >
>> >> > I'm getting DMAR errors during VM booting when I enable the iommu
>> >> > emulation for the VM. I was not able to complete booting since the VM
>> >> > gets really slow and just keep printing the error message (sym0:
>> >> > unexpected disconnect) at a speed of one character per second.
>> >> >
>> >> > I have enabled the iommu emulation, but didn't assign any device to the 
>> >> > VM.
>> >> >
>> >> > This is the kernel log from the VM
>> >>
>> >> I'm using 4.6.0-rc5+ kernel for the host and the VM.
>> >>
>> >> Here's the full kernel log from the VM.
>> >> https://paste.ubuntu.com/23948597/
>> >>
>> >> >
>> >> > [6.087794] sym0: SCSI BUS has been reset.
>> >> > [6.087960] DMAR: DRHD: handling fault status reg 2
>> >> > [6.088001] DMAR: DMAR:[DMA Read] Request device [04:03.0] fault
>> >> > addr fe281000
>> >> > [6.088001] DMAR:[fault reason 06] PTE Read access is not set
>> >> > [6.090513] scsi host1: sym-2.2.3
>> >> > [6.090567] sym0: unexpected disconnect
>> >> > [8.814929] sym0: unexpected disconnect
>> >> > [   11.670251] sym0: unexpected disconnect
>> >> >
>> >> > I enabled iommu in the host (intel_iommu=on). I also enabled iommu in
>> >> > the guest AND gave this option to the qemu (-device intel-iommu). I'm
>> >> > using qemu 2.8.0 and libvirt 3.0.0.
>> >> > I used  in libvirt xml to enable iommu emulation.
>> >> > Here's the full libvirt xml.
>> >> > http://paste.ubuntu.com/23946803/
>> >> >
>> >> > I did lspci -vvv and 04:03:0 is scsi device. Unfortunately, I lost
>> >> > that information, and can't boot the VM now. I'll add this information
>> >> > later if necessary.
>> >>
>> >> This is information about 04:03:0
>> >> I got this from the another identical VM but not with the iommu emulation.
>> >>
>> >> root@guest0:~# lspci -vvs 04:03.0
>> >> 04:03.0 SCSI storage controller: LSI Logic / Symbios Logic 53c895a
>> >> Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
>> >> Stepping- SERR+ FastB2B- DisINTx-
>> >> Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort-
>> >> SERR- > >> Latency: 255, Cache Line Size: 64 bytes
>> >> Interrupt: pin A routed to IRQ 23
>> >> Region 0: I/O ports at c000 [size=256]
>> >> Region 1: Memory at fe284000 (32-bit, non-prefetchable) [size=1K]
>> >> Region 2: Memory at fe28 (32-bit, non-prefetchable) [size=8K]
>> >> Kernel driver in use: sym53c8xx
>> >>
>> >> >
>> >> > Any thoughts why this happens and how to fix?
>> >
>> > Try a different disk controller in the VM?  Running virtual VT-d can't
>> > automatically fix guest drivers that don't handle devices behind an
>> > IOMMU correctly.  I don't know if that's the case, but I imagine 53c895a
>> > has probably never been tested w/ VT-d emulation.
>>
>> Ok, I'll try another disk controller. If someone can suggest other
>> disk controller which is working well with the iommu emulation, then
>> it would be great. I guess I got the controller by using this option
>> in virsh-install (--disk=/temp-space/guest50.img,size=10,bus=scsi),
>> but not 100% sure.
>>
>> > Note that when you
>> > do get to the point off assigning a device to the VM, you're going to
>> > need to build your own QEMU with patches from the mailing list, or
>> > maybe wait a few days and they might make it to the git tree.  Thanks,
>>
>> I'm afraid I understand this.
>
> lol ;)
>
>> I was able to assign a network device to
>> the VM without the iommu emulation. If I want to assign a network
>> device to the VM with the iommu emulation, then I need to apply
>> patches from the mailing list?
>
> Yes, the version of intel-iommu in QEMU 2.8 does not work correctly
> with assigned devices.  This is the latest posting:
>
> https://lists.gnu.org/archive/html/qemu-devel/2017-02/msg01331.html

This is really helpful!

Re: [Qemu-discuss] DMAR errors with iommu emulation enabled

2017-02-07 Thread Alex Williamson 
On Tue, 7 Feb 2017 12:53:04 -0500
Jintack Lim  wrote:

> Thanks Alex, I appreciate your help.
> 
> On Tue, Feb 7, 2017 at 12:09 PM, Alex Williamson
>  wrote:
> > On Tue, 7 Feb 2017 11:46:57 -0500
> > Jintack Lim  wrote:
> >  
> >> Adding CC and some more information.  
> >
> > $ ./scripts/get_maintainer.pl -f ./hw/i386/intel_iommu.c
> > get_maintainer.pl: No maintainers found, printing recent contributors.
> > get_maintainer.pl: Do not blindly cc: them on patches!  Use common sense.  
> 
> Oh, I got it. Thanks!
> 
> >
> > "Michael S. Tsirkin"  (commit_signer:54/35=100%)
> > Peter Xu  (commit_signer:28/35=80%)
> > Paolo Bonzini  (commit_signer:6/35=17%)
> > Jason Wang  (commit_signer:5/35=14%)
> > "Radim Krčmář"  (commit_signer:5/35=14%)
> > qemu-de...@nongnu.org (open list:All patches CC here)
> >  
> >> On Tue, Feb 7, 2017 at 5:07 AM, Jintack Lim  
> >> wrote:  
> >> > Hi,
> >> >
> >> > I'm getting DMAR errors during VM booting when I enable the iommu
> >> > emulation for the VM. I was not able to complete booting since the VM
> >> > gets really slow and just keep printing the error message (sym0:
> >> > unexpected disconnect) at a speed of one character per second.
> >> >
> >> > I have enabled the iommu emulation, but didn't assign any device to the 
> >> > VM.
> >> >
> >> > This is the kernel log from the VM  
> >>
> >> I'm using 4.6.0-rc5+ kernel for the host and the VM.
> >>
> >> Here's the full kernel log from the VM.
> >> https://paste.ubuntu.com/23948597/
> >>  
> >> >
> >> > [6.087794] sym0: SCSI BUS has been reset.
> >> > [6.087960] DMAR: DRHD: handling fault status reg 2
> >> > [6.088001] DMAR: DMAR:[DMA Read] Request device [04:03.0] fault
> >> > addr fe281000
> >> > [6.088001] DMAR:[fault reason 06] PTE Read access is not set
> >> > [6.090513] scsi host1: sym-2.2.3
> >> > [6.090567] sym0: unexpected disconnect
> >> > [8.814929] sym0: unexpected disconnect
> >> > [   11.670251] sym0: unexpected disconnect
> >> >
> >> > I enabled iommu in the host (intel_iommu=on). I also enabled iommu in
> >> > the guest AND gave this option to the qemu (-device intel-iommu). I'm
> >> > using qemu 2.8.0 and libvirt 3.0.0.
> >> > I used  in libvirt xml to enable iommu emulation.
> >> > Here's the full libvirt xml.
> >> > http://paste.ubuntu.com/23946803/
> >> >
> >> > I did lspci -vvv and 04:03:0 is scsi device. Unfortunately, I lost
> >> > that information, and can't boot the VM now. I'll add this information
> >> > later if necessary.  
> >>
> >> This is information about 04:03:0
> >> I got this from the another identical VM but not with the iommu emulation.
> >>
> >> root@guest0:~# lspci -vvs 04:03.0
> >> 04:03.0 SCSI storage controller: LSI Logic / Symbios Logic 53c895a
> >> Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
> >> Stepping- SERR+ FastB2B- DisINTx-
> >> Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort-
> >> SERR-  >> Latency: 255, Cache Line Size: 64 bytes
> >> Interrupt: pin A routed to IRQ 23
> >> Region 0: I/O ports at c000 [size=256]
> >> Region 1: Memory at fe284000 (32-bit, non-prefetchable) [size=1K]
> >> Region 2: Memory at fe28 (32-bit, non-prefetchable) [size=8K]
> >> Kernel driver in use: sym53c8xx
> >>  
> >> >
> >> > Any thoughts why this happens and how to fix?  
> >
> > Try a different disk controller in the VM?  Running virtual VT-d can't
> > automatically fix guest drivers that don't handle devices behind an
> > IOMMU correctly.  I don't know if that's the case, but I imagine 53c895a
> > has probably never been tested w/ VT-d emulation.  
> 
> Ok, I'll try another disk controller. If someone can suggest other
> disk controller which is working well with the iommu emulation, then
> it would be great. I guess I got the controller by using this option
> in virsh-install (--disk=/temp-space/guest50.img,size=10,bus=scsi),
> but not 100% sure.
> 
> > Note that when you
> > do get to the point off assigning a device to the VM, you're going to
> > need to build your own QEMU with patches from the mailing list, or
> > maybe wait a few days and they might make it to the git tree.  Thanks,  
> 
> I'm afraid I understand this.

lol ;)

> I was able to assign a network device to
> the VM without the iommu emulation. If I want to assign a network
> device to the VM with the iommu emulation, then I need to apply
> patches from the mailing list?

Yes, the version of intel-iommu in QEMU 2.8 does not work correctly
with assigned devices.  This is the latest posting:

https://lists.gnu.org/archive/html/qemu-devel/2017-02/msg01331.html

Re: [Qemu-discuss] DMAR errors with iommu emulation enabled

2017-02-07 Thread Jintack Lim 
Thanks Alex, I appreciate your help.

On Tue, Feb 7, 2017 at 12:09 PM, Alex Williamson
 wrote:
> On Tue, 7 Feb 2017 11:46:57 -0500
> Jintack Lim  wrote:
>
>> Adding CC and some more information.
>
> $ ./scripts/get_maintainer.pl -f ./hw/i386/intel_iommu.c
> get_maintainer.pl: No maintainers found, printing recent contributors.
> get_maintainer.pl: Do not blindly cc: them on patches!  Use common sense.

Oh, I got it. Thanks!

>
> "Michael S. Tsirkin"  (commit_signer:54/35=100%)
> Peter Xu  (commit_signer:28/35=80%)
> Paolo Bonzini  (commit_signer:6/35=17%)
> Jason Wang  (commit_signer:5/35=14%)
> "Radim Krčmář"  (commit_signer:5/35=14%)
> qemu-de...@nongnu.org (open list:All patches CC here)
>
>> On Tue, Feb 7, 2017 at 5:07 AM, Jintack Lim  wrote:
>> > Hi,
>> >
>> > I'm getting DMAR errors during VM booting when I enable the iommu
>> > emulation for the VM. I was not able to complete booting since the VM
>> > gets really slow and just keep printing the error message (sym0:
>> > unexpected disconnect) at a speed of one character per second.
>> >
>> > I have enabled the iommu emulation, but didn't assign any device to the VM.
>> >
>> > This is the kernel log from the VM
>>
>> I'm using 4.6.0-rc5+ kernel for the host and the VM.
>>
>> Here's the full kernel log from the VM.
>> https://paste.ubuntu.com/23948597/
>>
>> >
>> > [6.087794] sym0: SCSI BUS has been reset.
>> > [6.087960] DMAR: DRHD: handling fault status reg 2
>> > [6.088001] DMAR: DMAR:[DMA Read] Request device [04:03.0] fault
>> > addr fe281000
>> > [6.088001] DMAR:[fault reason 06] PTE Read access is not set
>> > [6.090513] scsi host1: sym-2.2.3
>> > [6.090567] sym0: unexpected disconnect
>> > [8.814929] sym0: unexpected disconnect
>> > [   11.670251] sym0: unexpected disconnect
>> >
>> > I enabled iommu in the host (intel_iommu=on). I also enabled iommu in
>> > the guest AND gave this option to the qemu (-device intel-iommu). I'm
>> > using qemu 2.8.0 and libvirt 3.0.0.
>> > I used  in libvirt xml to enable iommu emulation.
>> > Here's the full libvirt xml.
>> > http://paste.ubuntu.com/23946803/
>> >
>> > I did lspci -vvv and 04:03:0 is scsi device. Unfortunately, I lost
>> > that information, and can't boot the VM now. I'll add this information
>> > later if necessary.
>>
>> This is information about 04:03:0
>> I got this from the another identical VM but not with the iommu emulation.
>>
>> root@guest0:~# lspci -vvs 04:03.0
>> 04:03.0 SCSI storage controller: LSI Logic / Symbios Logic 53c895a
>> Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
>> Stepping- SERR+ FastB2B- DisINTx-
>> Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort-
>> SERR- > Latency: 255, Cache Line Size: 64 bytes
>> Interrupt: pin A routed to IRQ 23
>> Region 0: I/O ports at c000 [size=256]
>> Region 1: Memory at fe284000 (32-bit, non-prefetchable) [size=1K]
>> Region 2: Memory at fe28 (32-bit, non-prefetchable) [size=8K]
>> Kernel driver in use: sym53c8xx
>>
>> >
>> > Any thoughts why this happens and how to fix?
>
> Try a different disk controller in the VM?  Running virtual VT-d can't
> automatically fix guest drivers that don't handle devices behind an
> IOMMU correctly.  I don't know if that's the case, but I imagine 53c895a
> has probably never been tested w/ VT-d emulation.

Ok, I'll try another disk controller. If someone can suggest other
disk controller which is working well with the iommu emulation, then
it would be great. I guess I got the controller by using this option
in virsh-install (--disk=/temp-space/guest50.img,size=10,bus=scsi),
but not 100% sure.

> Note that when you
> do get to the point off assigning a device to the VM, you're going to
> need to build your own QEMU with patches from the mailing list, or
> maybe wait a few days and they might make it to the git tree.  Thanks,

I'm afraid I understand this. I was able to assign a network device to
the VM without the iommu emulation. If I want to assign a network
device to the VM with the iommu emulation, then I need to apply
patches from the mailing list?

Thanks,
Jintack

>
> Alex
>

Re: [Qemu-discuss] Qemu ARM64 command line parameters

2017-02-07 Thread Peter Maydell 
On 5 February 2017 at 14:27, Hrishikesh Murukkathampoondi
 wrote:
> * a flash device at 0x0
> * RAM starting at 0x4000

You can also get away with hardcoding the UART being at
0x0900 (since UEFI hardcodes that too).

> He mentioned that all other values like -machine gic-version=  etc
>
> I dont know what values can be provided for gic-version. Are the
> possible values documented somewhere?

Not documented, I'm afraid, but the usage message if you get them
wrong will tell you:

$ ./build/x86/aarch64-softmmu/qemu-system-aarch64 -M virt -machine
gic-version=help
qemu-system-aarch64: Invalid gic-version value
Valid values are 3, 2, host.

"host" is for KVM use only (and means "whatever this host machine
can provide"). You probably want 3 unless you know you'd rather
have a GICv2. Default is 2 (for back-compatibility reasons).

> I am unsure what else I should specify besides GIC. Are all
> -machine options documented somewhere ?

The other useful options you want will be
 -cpu cortex-a57# default cpu is 32-bit
 -m 1024# 1GB of RAM (more possible; default is 128MB)

and maybe
 -machine virtualization=on# if you want to enable EL2
 -machine secure=on# if you want to enable EL3
...but for your use case I would suggest leaving both these disabled
unless your intention is to play with these parts of the ARM
architecture.
(secure=on in particular will enable split secure and nonsecure
address spaces and put some devices only in secure, like a
second UART.)

You can also use -device options to add virtio PCI devices if you want
networking, disk, etc. (They won't affect the device tree,
though.)

I would also suggest
 -semihosting

which will enable the semihosting ABI. Semihosting is documented
here: https://developer.arm.com/docs/100863/0200
but basically it's a mechanism for allowing you to do things
like "debug print to console" via a simple "load values into
registers and execute magic HLT 0xf000 instruction" interface.
That's likely to be easier than talking to the serial port.
For instance you can print a message with something like
ldr x1, =string
mov x0, 4// SYS_WRITE0
hlt 0xf000   // semihosting call
[...]
string: asciz "hello world\n"

Note that the semihosting ABI contains functions like
"write to a host file" so don't enable it if the guest
code is not trustworthy. Also it will only work in QEMU
if the guest code is at EL1 (system), not at EL0 (user).

> What is the first memory address fetched by the processor in
> the virt machine? (ie where should I place the first instruction
> of my bare metal code)

As on real hardware, we start at address zero (the reset
vector in the vector table), which is in the flash.
Use -bios to specify a binary blob to put in the flash.
Note that the flash is not writeable memory :-)

(This assumes you aren't passing -kernel to QEMU: if
you ask us to load a linux kernel then we'll start
execution at the start of the kernel. For your use case
you should stick with -bios and not -kernel.)

thanks
-- PMM

Re: [Qemu-discuss] DMAR errors with iommu emulation enabled

2017-02-07 Thread Alex Williamson 
On Tue, 7 Feb 2017 11:46:57 -0500
Jintack Lim  wrote:

> Adding CC and some more information.

$ ./scripts/get_maintainer.pl -f ./hw/i386/intel_iommu.c
get_maintainer.pl: No maintainers found, printing recent contributors.
get_maintainer.pl: Do not blindly cc: them on patches!  Use common sense.

"Michael S. Tsirkin"  (commit_signer:54/35=100%)
Peter Xu  (commit_signer:28/35=80%)
Paolo Bonzini  (commit_signer:6/35=17%)
Jason Wang  (commit_signer:5/35=14%)
"Radim Krčmář"  (commit_signer:5/35=14%)
qemu-de...@nongnu.org (open list:All patches CC here)
 
> On Tue, Feb 7, 2017 at 5:07 AM, Jintack Lim  wrote:
> > Hi,
> >
> > I'm getting DMAR errors during VM booting when I enable the iommu
> > emulation for the VM. I was not able to complete booting since the VM
> > gets really slow and just keep printing the error message (sym0:
> > unexpected disconnect) at a speed of one character per second.
> >
> > I have enabled the iommu emulation, but didn't assign any device to the VM.
> >
> > This is the kernel log from the VM  
> 
> I'm using 4.6.0-rc5+ kernel for the host and the VM.
> 
> Here's the full kernel log from the VM.
> https://paste.ubuntu.com/23948597/
> 
> >
> > [6.087794] sym0: SCSI BUS has been reset.
> > [6.087960] DMAR: DRHD: handling fault status reg 2
> > [6.088001] DMAR: DMAR:[DMA Read] Request device [04:03.0] fault
> > addr fe281000
> > [6.088001] DMAR:[fault reason 06] PTE Read access is not set
> > [6.090513] scsi host1: sym-2.2.3
> > [6.090567] sym0: unexpected disconnect
> > [8.814929] sym0: unexpected disconnect
> > [   11.670251] sym0: unexpected disconnect
> >
> > I enabled iommu in the host (intel_iommu=on). I also enabled iommu in
> > the guest AND gave this option to the qemu (-device intel-iommu). I'm
> > using qemu 2.8.0 and libvirt 3.0.0.
> > I used  in libvirt xml to enable iommu emulation.
> > Here's the full libvirt xml.
> > http://paste.ubuntu.com/23946803/
> >
> > I did lspci -vvv and 04:03:0 is scsi device. Unfortunately, I lost
> > that information, and can't boot the VM now. I'll add this information
> > later if necessary.  
> 
> This is information about 04:03:0
> I got this from the another identical VM but not with the iommu emulation.
> 
> root@guest0:~# lspci -vvs 04:03.0
> 04:03.0 SCSI storage controller: LSI Logic / Symbios Logic 53c895a
> Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
> Stepping- SERR+ FastB2B- DisINTx-
> Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort-
> SERR-  Latency: 255, Cache Line Size: 64 bytes
> Interrupt: pin A routed to IRQ 23
> Region 0: I/O ports at c000 [size=256]
> Region 1: Memory at fe284000 (32-bit, non-prefetchable) [size=1K]
> Region 2: Memory at fe28 (32-bit, non-prefetchable) [size=8K]
> Kernel driver in use: sym53c8xx
> 
> >
> > Any thoughts why this happens and how to fix?

Try a different disk controller in the VM?  Running virtual VT-d can't
automatically fix guest drivers that don't handle devices behind an
IOMMU correctly.  I don't know if that's the case, but I imagine 53c895a
has probably never been tested w/ VT-d emulation.  Note that when you
do get to the point off assigning a device to the VM, you're going to
need to build your own QEMU with patches from the mailing list, or
maybe wait a few days and they might make it to the git tree.  Thanks,

Alex

Re: [Qemu-discuss] New web site!

2017-02-07 Thread Peter Maydell 
On 7 February 2017 at 15:26, Thomas Huth  wrote:
> On 07.02.2017 11:06, James Hanley wrote:
>> Why the new domain?
>
> It's not new, it's the official domain of the QEMU project.

Yes, we've always had both domains in parallel. The recent
change is that qemu.org now redirects to qemu-project.org
rather than them being separate-but-equivalent. (We're
currently discussing whether we should do it the other
way round instead.)

thanks
-- PMM

Re: [Qemu-discuss] info iso sparc64

2017-02-07 Thread sacarde 
>Alle domenica 15 gennaio 2017, hai scritto:

I try with debian-7.11.0-sparc-DVD-1.iso (as the suggested guide)

qemu-system-sparc64 -L pc-bios -m 
384 -nographic -kernel /.../sparc64 -initrd /.../initrd+virtio.gz -drive 
file=/.../sparc64.img,if=virtio,index=0 -drive 
file=/.../debian-7.11.0-sparc-DVD-1.iso,if=virtio,readonly=on,index=1 -net 
nic,model=virtio -net user -append 'modprobe.blacklist=pata_cmd64x'

but after insert "/dev/vdb" and "scanning cdrom"

I have error: 
 
 Failed to load installer component
 Loading apt-cdrom-setup failed for unknown reasons. Aborting


You have any suggestions?

p.s.
check disc is OK

thank you

saca...@tiscali.it

> no idea - but why dont't just follow:
> http://tyom.blogspot.de/2013/03/debiansparc64-wheezy-under-qemu-how-to.html
> i've got it working using exact this tutorial - using the dvd image (as
> stated in the tutorial) - not the netinstall like you
>
> beware: you can't update the security stuff - there seems to be a bug
> with 7.8 - maybe its already fixed in 7.11
>
> after it works for the first time you can start tricking around with
> other settings
>
> Am 15.01.2017 um 12:02 schrieb sacarde:
> > Alle martedì 10 gennaio 2017, Dennis Luehring ha scritto:
> > > you can find several install tutorials on
> >
> > I download: debian-7.8.0-sparc-netinst.iso
> >
> > and I run:
> >
> > qemu-system-sparc64 -L pc-bios -m
> > 384 -nographic -kernel /.../sparc64 -initrd /.../initrd+virtio.gz -hda
> > /.../sparc64.img -drive
> > file=/.../debian-7.8.0-sparc-netinst.iso,if=virtio,readonly=on,index=1
> > -net nic,vlan=0,model=virtio -net tap,vlan=0,ifname=tap0 -net
> > user -append 'modprobe.blacklist=pata_cmd64x'
> >
> >
> > after I insert cdrom device: "/dev/vdb" I have error:
> >
> > Installation step failed  │
> >   │ An installation step failed. You can try to run the failing
> > item  │ │ again from the menu, or skip it and choose something else.
> > The│ │ failing step is: Detect and mount CD-ROM
> >
> >
> >
> >
> > thanks
> >
> >
> > saca...@tiscali.it
> >
> > > Artyom Tarasenko's blog: http://tyom.blogspot.de/
> > >
> > > i've successfully installed debian 7.8 on former qemu versions - 7.11
> > > should work
> > >
> > > http://tyom.blogspot.de/2013/03/debiansparc64-wheezy-under-qemu-how-to.
> > >html
> > >
> > > Am 09.01.2017 um 09:32 schrieb sacarde:
> > > > Hi,
> > > > I try to use qemu-system-sparc64 (qemu 2.8.0) in my archlinux64
> > > > I tried some isos , with command:
> > > >
> > > > "qemu-system-sparc64 -cdrom /...iso"
> > > >
> > > >
> > > > but I have error:
> > > >
> > > > with iso: gentoo-2004.3 sparc, I have:
> > > > http://sacarde.altervista.org/np/gentoo-2004.3.jpg
> > > >
> > > >
> > > > with iso: ubuntu-alternate-10.4 sparc, I have
> > > > http://sacarde.altervista.org/np/ubuntu-10.4.jpg
> > > >
> > > >
> > > > have you some iso to suggest me, that work OK ?
> > > >
> > > >
> > > >
> > > > thank you
> > > >
> > > > saca...@tiscali.it

Re: [Qemu-discuss] New web site!

2017-02-07 Thread Thomas Huth 
On 07.02.2017 11:06, James Hanley wrote:
> Why the new domain?

It's not new, it's the official domain of the QEMU project.
For some historical details see:
http://git.qemu-project.org/?p=qemu.git;a=commitdiff;h=859389810910
(though the situation has improved nowadays, as far as I know)

 Thomas

>> On Feb 7, 2017, at 1:38 AM, Vincenzo Romano  
>> wrote:
>>
>> When going to the qemu.org with your brwoser, you'll be redirected to
>> the new website qemu-project.org!
>>
>> You're all invited! Bring your (virtual) glass to toast it!
>>
>> --
>> Vincenzo Romano - NotOrAnd.IT
>> Information Technologies
>> --
>> NON QVIETIS MARIBVS NAVTA PERITVS
>>
>

[Qemu-discuss] Tracing the execution flow when using qemu user mode

2017-02-07 Thread Prashast Srivastava 
When doing full system emulation, QEMU provides us with an option to trace
events which can then be analysed(for eg. the simple trace backend). I
wanted to know if it's possible for me to trace the execution
flow(tb_exec,translate_block etc) when using the user mode emulation to run
a 32 bits MIPS binary in x86_64 environment(qemu-mips-static).

The ubuntu distro provides me with black box binaries to perform user mode
emulation(qemu-user-static) but I couldn't find a way to build these
binaries from source so that I can have the tracing backend enabled. I
tried to build qemu statically from the source code but that ended up
giving me the qemu-system-mips binary statically linked.

Re: [Qemu-discuss] New web site!

2017-02-07 Thread James Hanley 
Why the new domain?

-Jim

> On Feb 7, 2017, at 1:38 AM, Vincenzo Romano  
> wrote:
> 
> When going to the qemu.org with your brwoser, you'll be redirected to
> the new website qemu-project.org!
> 
> You're all invited! Bring your (virtual) glass to toast it!
> 
> --
> Vincenzo Romano - NotOrAnd.IT
> Information Technologies
> --
> NON QVIETIS MARIBVS NAVTA PERITVS
>