Re: Backing up Windows Guest

[Simon Becherer]

Am 27.07.21 um 18:08 schrieb Chris Moody:
> Hi all,
> 
> Thinking of doing a distrohop, one issue I've had in the past when doing this 
> is the Windows seems to know that its environment has changed causing issues 
> with its registration.
> 
> Is there a way to backup this file in such a way that Windows won't know its 
> running under a different Host OS?
> 
> Thanks in advance for your help,
> 
> Chris
> 
> 

Hi chris,

i asked 2 times at this list how to stuck the virtual hardware / environement 
to do not change
when qemu is updated. i get only one "+" but no other response for a solution.
if you find a solution or anybody who could answer, please tell me/us.


simoN




-- 
www.becherer.de



signature.asc
Description: OpenPGP digital signature

Backing up Windows Guest

[Chris Moody]

Hi all,

Thinking of doing a distrohop, one issue I've had in the past when doing 
this is the Windows seems to know that its environment has changed 
causing issues with its registration.


Is there a way to backup this file in such a way that Windows won't know 
its running under a different Host OS?


Thanks in advance for your help,

Chris

Re: Blank screen for hello world qemu-4.2.0

[abhijeet inamdar]

Hi,

I was trying to use gdbstub what does vmlinux mean here?

Then launch gdb on the ‘vmlinux’ executable:

> gdb vmlinux

Is it my executable file or ?

On Mon, Jul 26, 2021, 15:44 abhijeet inamdar 
wrote:

> Hi,
>
> Is there any particular Flash and RAM length for qemu to semihosting. I'm
> using q2-update-2017 tool chain and 16.04 Ubuntu.
>
> On Fri, Jul 23, 2021, 14:16 Peter Maydell 
> wrote:
>
>> On Fri, 23 Jul 2021 at 13:05, abhijeet inamdar
>>  wrote:
>> >
>> > Means the memory mapping is not done correctly.
>> >
>> > I have added '-d nochain' and '-singlestep' to the command line it
>> gives me never ending
>> >
>> >  Trace 0: 0x7ff207a5eac0 [/0572/0x312000c1]
>> HardFault_Handler
>> > R00=218c R01= R02=2264 R03=2264
>> > R04=23f4 R05=23f4 R06= R07=
>> > R08= R09= R10= R11=
>> > R12= R13=07e0 R14=fff9 R15=0572
>> > XPSR=6103 -ZC- T handler
>> >
>> > Until i kill it.
>>
>> Well, of course it does -- I already told you your guest code goes
>> into an infinite loop in its HardFault handler. The part of the trace
>> that will tell you what is going wrong is before that.
>>
>> -- PMM
>>
>

how to use smmuv3 for arm64?

[ckim]

Hello, all

I found by adding "iommu=smmuv3" in the 'virt' machine option the smmuv3 is
instantiated. Cool.

It looks like smmu is instantiated with PCIe bus. (maybe PCIe ATS is done by
smmuv3..).

But if I want to use smmuv3 for a device attached in the platform, how
should I use it?

I see in hw/arm/smmuv3.c, (version 5.1.0)

static void smmuv3_register_types(void)

{

type_register(_type_info);

type_register(_iommu_memory_region_info);

}

I couldn't find any example code using "smmuv3_iommu_memory_region_info".

Is it possible to set a memory region to use smmuv3? 

Thanks for any help.

Chan Kim