have searched in the Internet can't answer my question.
If anyone have done that before, let me know it will not be a dead end.
Thanks
Sangfor VT
On 2015/4/15 9:08, Rob Landley wrote:
> On Mon, Apr 13, 2015 at 6:29 AM, vt wrote:
>> Hi, guys
>>
>> I saw the architecture code about mips in the qemu and kvm modules, so it is
>> no doubt that mips cpu can be supported.
>
> It looks like the 32 bit one should
centos 5.5 2.6.18 jiffies/kvm-clock no panic
fedora 13 2.6.33 kvm-clockno panic
I am curious why redhat 5.5 have the different result ? Anything I missed?
Should the guest panic because of the stuck in qemu main thread?
Thanks
vt
ow2 is from [C] of base.qcow2, assuming the new.qcow2 has
not been write to since created.
What I want is that the data of new.qcow2 is from [B] of base.qcow2, like this:
qemu-img create -f qcow2 -o backing_file=/path/base.qcow2,backing_snapshot=B
new.qcow2
Can the qemu support it now?
Thanks
vt
On 2015/7/6 20:09, Max Reitz wrote:
> On 06.07.2015 10:20, vt wrote:
>> Hi.
>> If a base qcow2 image snapshot chain like this:
>> base.qcow2: [A] -> [B] -> [C]
>> [C] is the current image where guest read/write to,usually we create a
>> new image base on the
