similar to: virsh list shows no vm after downgrade

Displaying 20 results from an estimated 20000 matches similar to: "virsh list shows no vm after downgrade"

2014 Dec 18
1
virsh list shows no vm after downgrade
Hi, I was running libvirt 1.2.2 and qemu 2.0 which are from icehouse cloud archive repo on ubuntu 12.04, "virsh list --all" showed correct instances after launching several VMs, Then I just downgraded libvirt to 0.9.13 and qemu to 1.0, but kept the VMs running. However, when I run "virsh list --all" after downgrade, I can't see any VMs. Seems that the old version libvirt
2012 Aug 16
1
disappeared VM in virsh
Hi guys, one of my VM has disappeared in libvirtd. I still can see the process with ps and the configuration file is as well there. But it is not displayed or found with virt-manger/virsh. virsh list shows only 4 of 5, but there is no real error message. I restarted the daemon without solving the problem. Any idea what to do? Here some info: Compiled against library: libvir 0.9.13 Using
2014 Nov 05
1
old vm cannot be migrated, new vm can be migrated
scenario: i run a mix of libvirt 1.1.1 and 1.2.2 on the source hosts, 1.2.2 on the destination hosts qemu: 1.5.0+dfsg-3ubuntu5.3~cloud0 on all the hosts openstack havana and icehouse description: i have many compute nodes running libvirt+kvm, when i try to migrate guest that were created months ago it fails, if i create a vm and then migrate it works the problem is that libvirt cannot
2015 Jan 14
1
volume can't be attached after libvirt upgrade
Hi, My nova-compute nodes was running libvirt 0.9.13 and QEMU 1.0, after libvirt was upgraded to 1.2.2, the VMs launched by libvirt 0.9.13 can't attach volume any more, i.e. "nova volume-attach <vm-uuid> <volume-uuid>" doesn't work. But before the libvirt upgrade, the same VM can attach volume disk. I did some debuging and find that, it failed in QEMU when try to
2010 Jan 04
2
Downgrade TDB files?
Hi. I've tried Samba 3.4.3 and it upgraded my passdb.tdb file. After testing I concluded that I'm not going to upgrade to 3.4.3 yet, because 'getent passwd' was broken in recent BlastWave Solaris packages: http://wiki.blastwave.org/forum/viewtopic.php?f=5&t=447&start=0 Now, after I downgraded the Samba back to 3.0.32, client connections started to malfunction. I saw
2005 Feb 27
0
ATA 286 downgrade failure
Good day list, I have a problem with ATA Handy Tone 286. It has been unsuccessfully downgraded via HTTP. Seems like during downgrade there was a problem with connection, because now it's not responding at all. There is no way to get to it's voice menu via phone (by pressing button on it). The button is just flashing ... Could anyone suggest any way to bring that device back to life.
2015 Apr 21
1
Re: <qemu:commandline> domain XML tag is not working?
Hi Kashyap, Here I want to test and see how much I/O performance could be improved by virtio-blk data plane feature. Yes, this is a dirty way to enable it :-), You mentioned using newer libvirt, is there parameter similar "x-data-plane=on" in new version libvirt? Please let know me you if you have better solution. Regards, CY. On Mon, Apr 20, 2015 at 10:51 PM, Kashyap Chamarthy
2015 Apr 20
4
<qemu:commandline> domain XML tag is not working?
Hi, I tried to enable virtio-blk data plane feature for VMs in my openstack environment, the hypervisor is ubuntu 14.04, libvirt 1.2.2 and QEMU 2.0. As nova doesn't support that parameter yet, I did belows 1. nova boot a VM with raw disk image. 2. nova stop the VM. 3. run "virsh edit <instance-id>" on the hyprvisor node, and adding below into instance xml just before
2015 Apr 21
1
Re: <qemu:commandline> domain XML tag is not working?
Hi Eric, Thanks! You are right, I missed declaring namespace, now, the <qemu:commandline> is saved after virsh edit. However, both namespace and <qemu:commandline> tag are lost after I run "nova start" to launch the VM. Any idea that how could I make this qemu command take effect ? Regards, CY. On Mon, Apr 20, 2015 at 11:41 PM, Eric Blake <eblake@redhat.com> wrote:
2016 Apr 04
0
LXC don't support network type of ethernet
Hi All, Applied patch from below link in order to add ethernet network type support to LXC. https://www.redhat.com/archives/libvir-list/2016-January/msg00318.html Launching LXC based VM using openstack Icehouse release which uses libvirt in background fails with below error: LOG shows "*error : virNetDevVethCreate:196 : internal error: Failed to allocate free veth pair after 10
2017 Jan 26
2
samba rpm deps - with yum downgrade = kind of a mayhem
On 25/01/17 14:26, Jonathan Billings wrote: > On Wed, Jan 25, 2017 at 11:32:16AM +0000, lejeczek wrote: >> hi guys, gals >> >> do you see this: >> >> ~]$ yum downgrade samba >> Resolving Dependencies >> [...] >> --> Processing Dependency: libtevent.so.0(TEVENT_0.9.9) for package: >> samba-client-libs-4.4.4 >> >> ..and process
2017 Jan 26
0
samba rpm deps - with yum downgrade = kind of a mayhem
On Thu, Jan 26, 2017 at 11:44:06AM +0000, lejeczek wrote: > but Centos should, right? > Being able to downgrade can save you a day or a few. I know, for it did save > mine several times, eg. buggy samba new update and downgrade fixed it, etc. > We absolutely should be able to downgrade every rpm, if this is just a > matter of an opinion(I'd fail to see any other reasons to not
2017 Jun 01
0
yum install <olderversion> does not downgrade
Use the 'downgrade' option. https://access.redhat.com/solutions/29617 On Thu, Jun 1, 2017 at 1:46 PM, Anand Buddhdev <anandb at ripe.net> wrote: > We're using ansible to configure our CentOS 6 servers, and we have a > task to install a specific version of a package: > > - name: install thrift2 > yum: name=ripencc-thrift2-{{ version }} > > In this ansible
2006 Jun 16
2
[Slightly Off Topic]How to handle downgrades
Let''s say that there is a web application which comes in several different plans. Each plan has a different number of users and content items allowed for an account. Obviously we can allow the user to upgrade to a higher level plan by just increasing their limits but how do we handle downgrades? If the user is only allowed x items on the downgraded plan and they currently have
2017 Jun 02
0
yum install <olderversion> does not downgrade
Personally, I would do one of three things: 1. Use the -m command to run 'yum install <version>' which /might/ work. 2. Uninstall the newer package and install the version you want. (Check the 'state' directive to do this.) 3. Pin that package version when creating the server/VM so as not to be updated. #3 is useful to us as we kickstart all our servers and VMs, and
2017 Jan 25
0
samba rpm deps - with yum downgrade = kind of a mayhem
On Wed, Jan 25, 2017 at 11:32:16AM +0000, lejeczek wrote: > hi guys, gals > > do you see this: > > ~]$ yum downgrade samba > Resolving Dependencies > [...] > --> Processing Dependency: libtevent.so.0(TEVENT_0.9.9) for package: > samba-client-libs-4.4.4 > > ..and process fails. > chained are i686 arch? Is it only us(centos) or redhat's bugzilla should
2018 Oct 15
0
[Qemu-devel] virtio-console downgrade the virtio-pci-blk performance
On (Thu) 11 Oct 2018 [18:15:41], Feng Li wrote: > Add Amit Shah. > > After some tests, we found: > - the virtio serial port number is inversely proportional to the iSCSI > virtio-blk-pci performance. > If we set the virio-serial ports to 2("<controller > type='virtio-serial' index='0' ports='2'/>), the performance downgrade > is minimal.
2017 Jan 25
2
samba rpm deps - with yum downgrade = kind of a mayhem
hi guys, gals do you see this: ~]$ yum downgrade samba Resolving Dependencies --> Running transaction check ---> Package samba.x86_64 0:4.4.4-9.el7 will be a downgrade --> Processing Dependency: samba-libs = 4.4.4-9.el7 for package: samba-4.4.4-9.el7.x86_64 --> Processing Dependency: samba-common-tools = 4.4.4-9.el7 for package: samba-4.4.4-9.el7.x86_64 --> Processing
2015 Apr 20
0
Re: <qemu:commandline> domain XML tag is not working?
On 04/20/2015 08:37 AM, Chengyuan Li wrote: > Hi, > > I tried to enable virtio-blk data plane feature for VMs in my openstack > environment, the hypervisor is ubuntu 14.04, libvirt 1.2.2 and QEMU 2.0. > As nova doesn't support that parameter yet, I did belows > > 1. nova boot a VM with raw disk image. > 2. nova stop the VM. > 3. run "virsh edit
2014 Mar 14
1
libplasma - no downgrade
I tried, last night, to downgrade kdelibs, I think it is, to resolve the libplasma crash that we talked about yesterday... and yum told me there was no upgrade or downgrade. I'm sort of assuming that I'd have to go back to 6.4... unless I need to add a repo - the vault? wget it, and downgrade it locally? mark