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

Re: [Xen-devel] Linux kernel initialization using Xen.

  • To: Ian Campbell <Ian.Campbell@xxxxxxxxxx>
  • From: jack nemati <hn_nemati1985@xxxxxxxxx>
  • Date: Wed, 1 Feb 2012 02:51:06 -0800 (PST)
  • Cc: "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>
  • Delivery-date: Wed, 01 Feb 2012 10:51:23 +0000
  • Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=X-YMail-OSG:Received:X-Mailer:Message-ID:Date:From:Subject:To:Cc:MIME-Version:Content-Type; b=Fe8cNsygnC8MFt1wlT0wB3RmO4pBQwkNOvmHWqyvq3IvXMvwMaER0rgw5Zyq8N+lIzealW9slwNymSkvXZQK39J+icddrtwBw8DhPKAFIJuRHYDOJEVwHVdRencBtfRVjE76FgRe57b5HisSgheAeQyAllINUBTWmjqCd6qb4NQ=;
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>

is there any solution for it? Thanks

I want to do this in the hypervisor level, because I'm going to prevent illegal  modifications in the bootloader. as an instance, I want to prevent users from passing parameters such as noexec=off in boot time to the kernel.

Xen-devel mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.