Re: vmm issues - vioblk_notifyq: unsupported command 0x8

2018-01-12 Thread Mike Larkin
On Fri, Oct 13, 2017 at 04:14:09PM -0500, Andrew Daugherity wrote: > On Thu, Oct 12, 2017 at 6:42 PM, Mike Larkin wrote: > >> oh. I didn't know that is how it was finding things. > >> > > > > When booting it this way in qemu, qemu just reports the ID as "". > > > > So are

Re: vmm issues - vioblk_notifyq: unsupported command 0x8

2017-10-13 Thread Andrew Daugherity
On Thu, Oct 12, 2017 at 6:42 PM, Mike Larkin wrote: >> oh. I didn't know that is how it was finding things. >> > > When booting it this way in qemu, qemu just reports the ID as "". > > So are you sure this is the way it is supposed to work? Yes... with some caveats. The

Re: vmm issues - vioblk_notifyq: unsupported command 0x8

2017-10-12 Thread Mike Larkin
On Thu, Oct 12, 2017 at 03:15:45PM -0700, Mike Larkin wrote: > On Thu, Oct 12, 2017 at 05:07:24PM -0500, Andrew Daugherity wrote: > > On Tue, Oct 3, 2017 at 3:49 AM, Jiri B wrote: > > >> > I was able to boot opensuse from that dvd, although later on I got an > > >> > error in the

Re: vmm issues - vioblk_notifyq: unsupported command 0x8

2017-10-12 Thread Mike Larkin
On Thu, Oct 12, 2017 at 05:07:24PM -0500, Andrew Daugherity wrote: > On Tue, Oct 3, 2017 at 3:49 AM, Jiri B wrote: > >> > I was able to boot opensuse from that dvd, although later on I got an > >> > error in the installer :/ > >> > >> This was because the installer couldn't locate

Re: vmm issues - vioblk_notifyq: unsupported command 0x8

2017-10-12 Thread Andrew Daugherity
On Tue, Oct 3, 2017 at 3:49 AM, Jiri B wrote: >> > I was able to boot opensuse from that dvd, although later on I got an >> > error in the installer :/ >> >> This was because the installer couldn't locate the "dvd", correct? > > Unable to create repository > from URL

Re: vmm issues - vioblk_notifyq: unsupported command 0x8

2017-10-03 Thread Mike Larkin
On Mon, Oct 02, 2017 at 02:34:58PM -0400, Jiri B wrote: > Hello, > > I'm playing with vmm and I got these in daemon log: > > Oct 2 20:12:14 t440s vmd[13344]: startup > Oct 2 20:12:14 t440s vmd[53680]: SIOCBRDGADD: No such file or directory > Oct 2 20:12:24 t440s vmd[13344]: suse01: started vm

Re: vmm issues - vioblk_notifyq: unsupported command 0x8

2017-10-03 Thread Mike Larkin
On Tue, Oct 03, 2017 at 04:49:30AM -0400, Jiri B wrote: > > > I was able to boot opensuse from that dvd, although later on I got an > > > error in the installer :/ > > > > This was because the installer couldn't locate the "dvd", correct? > > It so seems so. > > ~~~ > Unable to create

Re: vmm issues - vioblk_notifyq: unsupported command 0x8

2017-10-03 Thread Jiri B
> > I was able to boot opensuse from that dvd, although later on I got an > > error in the installer :/ > > This was because the installer couldn't locate the "dvd", correct? It so seems so. ~~~ Unable to create repository from URL 'hd:/?device=/dev/disk/by-id/virtio-_U_2_-part2'.

Re: vmm issues - vioblk_notifyq: unsupported command 0x8

2017-10-02 Thread Carlos Cardenas
On 2017-10-02 11:57, Jiri B wrote: > On Mon, Oct 02, 2017 at 02:56:18PM -0400, Josh Grosse wrote: >> Hey Jiri. >> >>> I started this vm with: >>> >>> vmctl start suse01 -c -d $iso -d $disk -L >>> >>> where iso is openSUSE-Leap-42.3-DVD-x86_64.iso[1]. >>> >>> Any idea what's going on? >> >> I'll

Re: vmm issues - vioblk_notifyq: unsupported command 0x8

2017-10-02 Thread Carlos Cardenas
On 2017-10-02 11:34, Jiri B wrote: > Hello, > > I'm playing with vmm and I got these in daemon log: > > Oct 2 20:12:14 t440s vmd[13344]: startup > Oct 2 20:12:14 t440s vmd[53680]: SIOCBRDGADD: No such file or directory > Oct 2 20:12:24 t440s vmd[13344]: suse01: started vm 1 successfully, tty

Re: vmm issues - vioblk_notifyq: unsupported command 0x8

2017-10-02 Thread Jiri B
On Mon, Oct 02, 2017 at 02:56:18PM -0400, Josh Grosse wrote: > Hey Jiri. > > >I started this vm with: > > > >vmctl start suse01 -c -d $iso -d $disk -L > > > >where iso is openSUSE-Leap-42.3-DVD-x86_64.iso[1]. > > > >Any idea what's going on? > > I'll bet it's because you are attempting to boot a

vmm issues - vioblk_notifyq: unsupported command 0x8

2017-10-02 Thread Jiri B
Hello, I'm playing with vmm and I got these in daemon log: Oct 2 20:12:14 t440s vmd[13344]: startup Oct 2 20:12:14 t440s vmd[53680]: SIOCBRDGADD: No such file or directory Oct 2 20:12:24 t440s vmd[13344]: suse01: started vm 1 successfully, tty /dev/ttyp3 Oct 2 20:13:12 t440s vmd[98531]: