wrote:
-Original Message-
From: Marcus Sorensen [mailto:shadow...@gmail.com]
Sent: Monday, March 04, 2013 10:26 PM
To: cloudstack-dev@incubator.apache.org
Subject: Re: [DISCUSS] getting rid of KVM patchdisk
I've been thinking about how to tackle this, written a little concept
On Tue, Mar 05, 2013 at 11:58:55PM +0530, Edison Su wrote:
-Original Message-
From: Marcus Sorensen [mailto:shadow...@gmail.com]
Sent: Monday, March 04, 2013 10:26 PM
To: cloudstack-dev@incubator.apache.org
Subject: Re: [DISCUSS] getting rid of KVM patchdisk
I've been
-Original Message-
From: Marcus Sorensen [mailto:shadow...@gmail.com]
Sent: Monday, March 04, 2013 10:26 PM
To: cloudstack-dev@incubator.apache.org
Subject: Re: [DISCUSS] getting rid of KVM patchdisk
I've been thinking about how to tackle this, written a little concept code
On 03/05/2013 07:28 PM, Edison Su wrote:
-Original Message-
From: Marcus Sorensen [mailto:shadow...@gmail.com]
Sent: Monday, March 04, 2013 10:26 PM
To: cloudstack-dev@incubator.apache.org
Subject: Re: [DISCUSS] getting rid of KVM patchdisk
I've been thinking about how to tackle
To: cloudstack-dev@incubator.apache.org
Subject: Re: [DISCUSS] getting rid of KVM patchdisk
I've been thinking about how to tackle this, written a little concept
code, and
it seems fairly straightforward to include our own little python daemon
that
speaks JSON via this local character device
-Original Message-
From: Marcus Sorensen [mailto:shadow...@gmail.com]
Sent: Sunday, March 03, 2013 12:13 PM
To: cloudstack-dev@incubator.apache.org
Subject: [DISCUSS] getting rid of KVM patchdisk
For those who don't know (this probably doesn't matter, but...), when KVM
brings up
I think this just requires an updated system vm (the virtio-serial
portion). I've played a bit with the old debian 2.6.32-5-686-bigmem
one and can't get the device nodes to show up, even though the
/boot/config shows that it has CONFIG_VIRTIO_CONSOLE=y. However, if I
try this with a CentOS 6.3 VM,
I tested this with Rohit's systemvm from master. It works fine,
provided you install the qemu-guest-agent software and modify the
libvirt xml definition of the system vm to include something like:
channel type='unix'
source mode='bind' path='/var/lib/libvirt/qemu/v-2-VM.agent'/
I've been thinking about how to tackle this, written a little concept
code, and it seems fairly straightforward to include our own little
python daemon that speaks JSON via this local character device in the
system vm. I'm assuming we'd start it up at the beginning of
cloud-early-config.
What I'm
