works.
From: "Wei ZHOU"
Sent: 11/24/21 4:29 PM
To: [email protected]
Subject: Re: Libvirt exception on live migrate
Hi Peter,
I see. The qemu hook replaces the device name only if the old device name does
not exist. But in your case, the old device name exists.
If you mak
uot;
Sent: 11/24/21 3:14 PM
To: [email protected]
Subject: Re: Libvirt exception on live migrate
Hi Peter,
I checked /etc/libvirt/hooks/qemu on hosts once again. I think it is able to
handle migrations between hosts with different device names. My questions are
(1) Do the hosts have /e
4/21 2:23 PM
To: [email protected]
Subject: Re: Libvirt exception on live migrate
Hi Peter,
Virtual routers have nics on Public and Guest network(both on cloudbr0), but
not on Management network, therefore it is expected that VR does not connect
cloudbr1 (management).
Currently cloud
/f540d08baa16a6d0d8e4b5dbe9dbe01a
~Peter
(Thanks for your help, by the way; I doubt I would have found this in the
script on my own.)
From: "Wei ZHOU"
Sent: 11/24/21 4:29 PM
To: [email protected]
Subject: Re: Libvirt exception on live m
udbr0
From: "Wei ZHOU"
Sent: 11/24/21 9:26 AM
To: [email protected]
Subject: Re: Libvirt exception on live migrate
Hi Peter,
You need to set the correct network label for traffic types (Public/Guest) in
zone-> physical networks
(destination of migration):
https://gist.github.com/PeterS-gd/d250c240f63538a6bd541b7870dffe0d
From: "Wei ZHOU"
Sent: 11/24/21 4:56 AM
To: users , [email protected]
Subject: Re: Libvirt exception on live migrate
Hi Peter,
The information you provi
Hi Peter,
The information you provided is not enough to find out the root cause.
Could you share more information ?
cloudstack version
os distribution and version
network device name on source host and destination host
output of `brctl show` or `bridge link` on source host and destination host
lo
Good afternoon everyone,
I have gotten my cloudstack running, but I am unable to live migrate any of my
VMs. I get an error like this: "Exception during migrate:
org.libvirt.LibvirtException: Cannot get interface MTU on 'brenp3s0f0-3128': No
such device"
I have tried using an L2, isolated, and
Hi Everybody,
I just fixed the issue :) As per mentioned in the link below, the issue was
systemd-machined daemon which tracks locally running virtual machines. I
just restarted it as well as restarted libvirtd and cloudstack-agent and it
started to work fine.
https://www.softaculous.com/board/i
Hello,
I'm running 4.15.0.0
On Thu, Apr 22, 2021 at 9:05 PM Gabriel Bräscher
wrote:
> Hi Fariborz,
>
> What version of CloudStack are you running?
>
> Em qui., 22 de abr. de 2021 às 13:14, Fariborz Navidan <
> [email protected]> escreveu:
>
> > Hello All,
> >
> > I am not able to start any
Hi Fariborz,
What version of CloudStack are you running?
Em qui., 22 de abr. de 2021 às 13:14, Fariborz Navidan <
[email protected]> escreveu:
> Hello All,
>
> I am not able to start any stopped VM. Agent and Libvirtd are both running.
> However, I see the following exception in agent.log:
>
Hello All,
I am not able to start any stopped VM. Agent and Libvirtd are both running.
However, I see the following exception in agent.log:
This is the exception I found in the agent.log:
2021-04-22 12:21:29,045 WARN [kvm.resource.LibvirtKvmAgentHook]
(agentRequest-Handler-1:null) (logid:4d875f
Hi,
has anybody an update on that Issue?
Does a libvirt upgrade solve the problem?
BR
Alexander
-Ursprüngliche Nachricht-
Von: Cloud List
Gesendet: Donnerstag, 20. September 2018 07:00
An: [email protected]
Betreff: Re: Unable to resize down data disk: libvirt exception
rom: Cloud List
> Sent: Tuesday, September 18, 2018 11:34 PM
> To: [email protected]
> Subject: Re: Unable to resize down data disk: libvirt exception - invalid
> argument: can't shrink capacity below existing allocation
>
> Hi,
>
> Anyone can advise on
This looks like a libvirt limitation/bug. What OS are you using?
From: Cloud List
Sent: Tuesday, September 18, 2018 11:34 PM
To: [email protected]
Subject: Re: Unable to resize down data disk: libvirt exception - invalid
argument: can't s
Hi,
Anyone can advise on below? Or is it confirmed that resizing down
(shrinking) the data-disk is no longer supported on CloudStack with KVM,
libvirt and Ceph RBD storage?
Looking forward to your reply, thank you.
Cheers.
On Thu, Aug 16, 2018 at 6:07 PM, Cloud List wrote:
> Hi,
>
> We are
Hi,
We are using CloudStack 4.8.1.1 with QEMU/KVM hypervisor, libvirt and Ceph
RBD storage.
We just realised that we are not able to resize down any of our data-disks,
and we are sure that we were able to do that before. Not too sure since
when the problem started to happen.
When we tried to res
H Mike, good to hear. I will have a look at it later this week end
On Fri, 8 May 2015 16:02 Mike C wrote:
> On 2015-05-07 16:41, Daan Hoogland wrote:
> > But if your patient I'll get there.
> I'm here to see it through to the end ;) The good news is Remi's note
> worked. I've included output bel
On 2015-05-07 16:41, Daan Hoogland wrote:
But if your patient I'll get there.
I'm here to see it through to the end ;) The good news is Remi's note
worked. I've included output below.
On 2015-05-07 16:42, Remi Bergsma wrote:
Hi Mike,
Can you check if the agent has debug logging enabled in lo
Hi Mike,
Can you check if the agent has debug logging enabled in log4j.xml? If not, this
enables it:
sed -i 's/INFO/DEBUG/g' /etc/cloudstack/agent/log4j-cloud.xml
Restart agent, then try again and we should see more logs.
Regards,
Remi
Sent from my iPhone
> On 07 May 2015, at 22:30, Mike C
I am not familiar with the deployment model on the kvm agent but there must
be a way to up the logging level. I am looking for the message in the 4.4.3
source now (long search). If the deployment model is anything like the ms
you should be editing some cloud log4j.xml under /etc. You may have to
re
On 2015-05-07 16:23, Daan Hoogland wrote:
To bad the agent didn't log a stack trace because the ms stacktrace is
really only telling us that the agent failed to do the migration.
Yeah, the following is what I have on the agent. There are a number of
records as I've tried doing the migration mo
To bad the agent didn't log a stack trace because the ms stacktrace is
really only telling us that the agent failed to do the migration.
Op do 7 mei 2015 om 22:04 schreef Mike C :
> On 2015-05-07 15:21, Daan Hoogland wrote:
> > Guess you are the first victim. Can you send me the full stack trace
On 2015-05-07 15:21, Daan Hoogland wrote:
Guess you are the first victim. Can you send me the full stack trace?
Preferably the first related one, so a bit of log digging might be
desired.
This is the full stack trace on the management server, I don't see
anything in the logs on the agent mac
Guess you are the first victim. Can you send me the full stack trace?
Preferably the first related one, so a bit of log digging might be desired.
On Thu, 7 May 2015 20:57 Mike C wrote:
> I recently upgraded to 4.4.3 and when trying to migrate a virtual router
> to a new host I get the following
I recently upgraded to 4.4.3 and when trying to migrate a virtual router
to a new host I get the following exception:
job origin:4121
com.cloud.utils.exception.CloudRuntimeException: Unable to migrate due
to org.libvirt.LibvirtException: Cannot get interface MTU on '
breth0-1214': No such devic
26 matches
Mail list logo
