Thank you very much.
I can launch L2 from L1 by directly using qemu-system-x86_64
name_of_image. L2 still hangs if I launch it using 'virsh' command;
libvirt shows this log:
warning : virAuditSend:135 : Failed to send audit message virt=kvm
resrc=net reason=start vm="L2"
uuid=e9549443-e63f-31b5-0692-1396736d06b4 old-net=?
new-net=52:54:00:75:c1:5b: Operation not permitted
I am using libvirt 1.1.1. Is it the above warning that causes the problem?
Best,
Hai
On Fri, Jan 17, 2014 at 6:40 AM, Jan Kiszka <jan.kiszka@xxxxxxxxxxx> wrote:
> On 2014-01-17 12:29, Kashyap Chamarthy wrote:
>> On Fri, Jan 17, 2014 at 2:51 AM, duy hai nguyen <haind93@xxxxxxxxx> wrote:
>>> Now I can run an L2 guest (nested guest) using the kvm kernel module
>>> of kernel 3.12
>>>
>>> However, I am facing a new problem when trying to build and use kvm
>>> kernel module from git://git.kiszka.org/kvm-kmod.git: L1 (nested
>>> hypervisor) cannot boot L2 and the graphic console of virt-manager
>>> hangs displaying 'Booting from Hard Disk...'. L1 still runs fine.
>>>
>>> Loading kvm_intel with 'emulate_invalid_guest_state=0' in L0 does not
>>> solve the problem. I have also tried with different kernel versions:
>>> 3.12.0, 3.12.8 and 3.13.0 without success.
>>>
>>> Can you give me some suggestions?
>>
>> Maybe you can try without graphical managers and enable serial console
>> ('console=ttyS0') to your Kernel command-line of L2 guest, so you can
>> see where it's stuck.
>
> Tracing can also be helpful, both in L1 and L0:
>
> http://www.linux-kvm.org/page/Tracing
>
> Jan
>
> --
> Siemens AG, Corporate Technology, CT RTC ITP SES-DE
> Corporate Competence Center Embedded Linux
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
