vmd console freeze and locked (?) qcow2 image

classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

vmd console freeze and locked (?) qcow2 image

Thomas L.
Hi,

I am running -current and installed Arch Linux on vmd.
Unfortunatly, after a while the vmd console freezes.
I tried stoping the vm with vmctl stop, but it keept hanging (maybe related to the console hanging?).
So I terminated the vm with vmctl stop -f.
Now, the vm won't start up complaining that it can't open the disk (log snippet below).
Is the qcow2 image somehow locked and can I unlock it?
Or is it corrupted? If so, is it recommanded using qcow2 images or are raw images more robust?

Kind regards,

Thomas


Jan  4 16:00:52 hilbert vmd[76370]: startup
Jan  4 16:00:52 hilbert vmd[76370]: archlinux: started vm 1 successfully, tty /dev/ttyp5
Jan  4 16:01:03 hilbert vmd[40912]: vcpu_process_com_data: guest reading com1 when not ready
Jan  4 16:01:03 hilbert last message repeated 2 times
Jan  4 16:01:04 hilbert vmd[40912]: vioblk_notifyq: unsupported command 0x8
Jan  4 16:01:04 hilbert vmd[40912]: vioblk_notifyq: unsupported command 0x8
Jan  4 16:04:53 hilbert vmd[40912]: vioblk_notifyq: unsupported command 0x8
Jan  4 16:04:53 hilbert vmd[40912]: vioblk_notifyq: unsupported command 0x8
Jan  4 16:04:55 hilbert vmd[40912]: vcpu_process_com_data: guest reading com1 when not ready
Jan  4 16:04:55 hilbert last message repeated 2 times
Jan  4 16:45:44 hilbert vmd[76370]: parent terminating
Jan  4 16:45:44 hilbert vmd[55480]: vmm exiting, pid 55480
Jan  4 16:45:44 hilbert vmd[76051]: control exiting, pid 76051
Jan  4 16:45:44 hilbert vmd[31650]: priv exiting, pid 31650
Jan  4 16:45:44 hilbert vmd[72119]: startup
Jan  4 16:45:44 hilbert vmd[72119]: can't open disk /var/vmd/archlinux.qcow2: Resource temporarily unavailable
Jan  4 16:45:44 hilbert vmd[72119]: failed to start vm archlinux
Jan  4 16:45:44 hilbert vmd[72119]: parent: configuration failed
Jan  4 16:45:44 hilbert vmd[12825]: vmm exiting, pid 12825
Jan  4 16:45:44 hilbert vmd[55512]: control exiting, pid 55512
Jan  4 16:45:44 hilbert vmd[1619]: priv exiting, pid 1619

Reply | Threaded
Open this post in threaded view
|

Re: Fwd: vmd console freeze and locked (?) qcow2 image

Mike Larkin
> From: Thomas L. <[hidden email]>
> Date: Fri, Jan 4, 2019 at 8:53 AM
> Subject: vmd console freeze and locked (?) qcow2 image
> To: <[hidden email]>
>
>
> Hi,
>
> I am running -current and installed Arch Linux on vmd.
> Unfortunatly, after a while the vmd console freezes.
> I tried stoping the vm with vmctl stop, but it keept hanging (maybe related
> to the console hanging?).
> So I terminated the vm with vmctl stop -f.
> Now, the vm won't start up complaining that it can't open the disk (log
> snippet below).
> Is the qcow2 image somehow locked and can I unlock it?
> Or is it corrupted? If so, is it recommanded using qcow2 images or are raw
> images more robust?
>
> Kind regards,
>
> Thomas
>
>
> Jan  4 16:00:52 hilbert vmd[76370]: startup
> Jan  4 16:00:52 hilbert vmd[76370]: archlinux: started vm 1 successfully,
> tty /dev/ttyp5
> Jan  4 16:01:03 hilbert vmd[40912]: vcpu_process_com_data: guest reading
> com1 when not ready
> Jan  4 16:01:03 hilbert last message repeated 2 times
> Jan  4 16:01:04 hilbert vmd[40912]: vioblk_notifyq: unsupported command 0x8
> Jan  4 16:01:04 hilbert vmd[40912]: vioblk_notifyq: unsupported command 0x8
> Jan  4 16:04:53 hilbert vmd[40912]: vioblk_notifyq: unsupported command 0x8
> Jan  4 16:04:53 hilbert vmd[40912]: vioblk_notifyq: unsupported command 0x8
> Jan  4 16:04:55 hilbert vmd[40912]: vcpu_process_com_data: guest reading
> com1 when not ready
> Jan  4 16:04:55 hilbert last message repeated 2 times
> Jan  4 16:45:44 hilbert vmd[76370]: parent terminating
> Jan  4 16:45:44 hilbert vmd[55480]: vmm exiting, pid 55480
> Jan  4 16:45:44 hilbert vmd[76051]: control exiting, pid 76051
> Jan  4 16:45:44 hilbert vmd[31650]: priv exiting, pid 31650
> Jan  4 16:45:44 hilbert vmd[72119]: startup
> Jan  4 16:45:44 hilbert vmd[72119]: can't open disk
> /var/vmd/archlinux.qcow2: Resource temporarily unavailable
> Jan  4 16:45:44 hilbert vmd[72119]: failed to start vm archlinux
> Jan  4 16:45:44 hilbert vmd[72119]: parent: configuration failed
> Jan  4 16:45:44 hilbert vmd[12825]: vmm exiting, pid 12825
> Jan  4 16:45:44 hilbert vmd[55512]: control exiting, pid 55512
> Jan  4 16:45:44 hilbert vmd[1619]: priv exiting, pid 1619

Did you kill all the old vmd processes?

-ml

Reply | Threaded
Open this post in threaded view
|

Re: vmd console freeze and locked (?) qcow2 image

Thomas L.
On Sat, 5 Jan 2019 17:56:01 -0800
Mike Larkin <[hidden email]> wrote:
> Did you kill all the old vmd processes?
>
> -ml
>

I tested again and it works now. There were restarts in between.
I will try killing vmd processes if this happens again, thanks.

Kind regards,

Thomas