On 08.05.2013 01:50, Edison Su wrote:
Need to modify KVM code to enable this feature. If you want to hack
the code, welcome:)
I believe this is or should be supported by SPICE - currently pretty
stable in EL6, maybe we'll have the feature whenever SPICE makes it in
Cloudstack (fingers crossed
Hi, you can try this with nested paging. Activate nested and install a "all in
one" Ovirt Server.
Then you have a VDI Platform with Spice native. Maybe it works with your Server
Hardware. (It's only a idea)
Regards Andreas
- Ursprüngliche Mail -
Von: "Nux!"
An: users@cloudstack
Yes, ovirt is the project you need for a vdi with usb passthru.
The usb redirection is available on fedora kvm and ovirt is based on fedora.
But ovirt is not a cloud Infrasctructure As A Service (IaaS).
I do not think that the last version o redhat supports usb redirection in
spice channel.
Infact
Thanks - I ended up using cloudmonkey. I was able to create a physical
network but can't attach it to a VM. Do I have to add something else? Is
there a network interface workflow that ties offerings, physical networks,
etc?
On Tue, May 7, 2013 at 3:20 PM, Sebastien Goasguen wrote:
>
> On May
There are multiple tickets filed for this, I'd quickly ask on dev to see if
there is a workaround to the issue youre facing.
On Mon, May 6, 2013 at 12:44 AM, wrote:
> Hi,
>
> I have upgraded cloudstack from 3.0.2 to 4.0.2 but still xenserver host
> is in disconnected status for few hours.
>
>
I had this same issue when I attempted to upgrade my production environment
from 3.0.2 to 4.0.2. I could not get the XenServer hosts to connect back, so I
had to end up rolling back to 3.0.2. I haven't been able to get around it.
John Skinner
---
Looping in dev;
Hey guys, are there any documented workarounds for the 4.0-4.02 upgrade
issues people are facing?
On Wed, May 8, 2013 at 11:10 AM, John Skinner wrote:
> I had this same issue when I attempted to upgrade my production
> environment from 3.0.2 to 4.0.2. I could not get the XenServ
Hi everyone,
On our cloudstack setup (4.0.2), I noticed that after a reboot of the
management server, I was no longer able to start new instances. A
secondary problem was that the management-server.log file filled up
extremely fast (gigabytes in a few hours), with messages like these:
2013-
Hi everyone,
On our cloudstack setup (4.0.2), I noticed that after a reboot of the
management server, I was no longer able to start new instances. A
secondary problem was that the management-server.log file filled up
extremely fast (gigabytes in a few hours), with messages like these:
2013-
On Wed, May 08, 2013 at 09:11:43PM +0200, Jori Liesenborgs wrote:
>
> Hi everyone,
>
> On our cloudstack setup (4.0.2), I noticed that after a reboot of
> the management server, I was no longer able to start new instances.
> A secondary problem was that the management-server.log file filled
> up
This is a known issue when you are running management server together with
a KVM host. After KVM host is added to the running management server, it
creates a bridge that can cause management server ID to be changed after
reboot, but only for once.
A similar issue can happen when you run management
Hi Kelven,
We have never used KVM in our cloud setup and the management server is a
separate machine, not a VM. I'm not sure what the code logic is supposed
to do, but in our case the problem did prevent the management server
from functioning: no new instances could be started.
Cheers,
Jori
Then this is slight different than the case with
management-server-and-KVM-in-one-box issue that I'm aware of.
When a management server is restarted with a new ID, it appears to the
cluster as a new management server instance, we have some code logic to
handle that. From what you described, the lo
13 matches
Mail list logo
