From: Joerg Roedel <joro@8bytes.org>
To: Daniel Schwager <Daniel.Schwager@dtnet.de>
Cc: kvm@vger.kernel.org
Subject: Re: How to secret Dom0 against DomU .
Date: Fri, 20 Feb 2009 17:50:16 +0100 [thread overview]
Message-ID: <20090220165016.GJ2125@8bytes.org> (raw)
In-Reply-To: <EB31672367A401439CD5A4A10889D57B01297453@exchange.dtnet.de>
On Fri, Feb 20, 2009 at 05:26:22PM +0100, Daniel Schwager wrote:
> Hi,
>
> are there some known issues using kvm-84
> - to break in into the Dom0
> - to corrupt the Dom0
> - to ... Dom0
>
> Are there some thinks I have to configure in Dom0
> to safe Dom0 against DomU's ?
This is absolutly no risk in KVM just because there is no Dom0. I guess
you mean if there is any way to break out of a guest and hack the host.
As far as I know there are no known security issue.
>
> My kvm-call looks like this:
>
> 30743 ? Sl 85:36 /usr/kvm/bin/qemu-system-x86_64 -S -M pc -m
> 500 -smp 1 -name solidcam -uuid 85e73643-0f27-b995-8ecb-9042ea044dc5
> -monitor pty -pidfile /var/run/libvirt/qemu//solidcam.pid -boot c -drive
> file=/srv/winxp127.dsk,if=ide,index=0,boot=on -net
> nic,macaddr=ae:de:49:00:40:0e,vlan=0,model=e1000 -net
> tap,ifname=vif100,script=/opt/virtcontroller/bin/qemu-ifup,vlan=0
> -serial pty -parallel none -usb -usbdevice tablet -vnc 0.0.0.0:0
>
> I want to publish windows XP DomU's to (technical affine) people's - I
> do not want
> that they can hurt/hack our base-system.
>
> regards
> Danny
>
>
> --
> To unsubscribe from this list: send the line "unsubscribe kvm" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2009-02-20 16:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-20 16:26 How to secret Dom0 against DomU Daniel Schwager
2009-02-20 16:50 ` Joerg Roedel [this message]
2009-02-20 18:20 ` Tomasz Chmielewski
2009-02-20 18:25 ` Daniel Schwager
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20090220165016.GJ2125@8bytes.org \
--to=joro@8bytes.org \
--cc=Daniel.Schwager@dtnet.de \
--cc=kvm@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.