Re: [Users] Migration issues with ovirt 3.3

On Wed, Oct 09, 2013 at 02:27:16PM +0200, Gianluca Cecchi wrote: > On Tue, Oct 8, 2013 at 12:27 PM, Omer Frenkel wrote: > > >> > > >> > so now I'm able to start VM without having to select run once and > >> > attaching a cd iso > >> > (note that is only valid for newly created VMs though) > >> > >> Yes. Old VMs are trashed with the bogus address reproted by the buggy > >> Vdsm. Can someone from engine supply a script to clear all device > >> addresses from the VM database table? > >> > > > > > > you can use this line (assuming engine as db and user), make sure

> > psql -U engine -d engine -c "select distinct vm_name from vm_static,

> > > > if so, you can run this to clear the address field for them, so they

> > psql -U engine -d engine -c "update vm_device set address='' where

> > > > I wanted to test this but for some reason it seems actually it solved

> I first ran the query and already had no value: > engine=# select distinct vm_name from vm_static, vm_device where > vm_guid=vm_id and device='cdrom' and address ilike '%pci%'; > vm_name > --------- > (0 rows) > > (overall my VMs are > engine=# select distinct vm_name from vm_static; > vm_name > ----------- > Blank > c6s > c8again32 > (3 rows) Which of these 3 is the one that was started up with an empty cdrom on a vanilla ovirt-3.3.0 vdsm? The script is expect to show only those.