Manually upgraded QEMU 3.1 does not support qxl video device












0















I want to use the latest version of QEMU (3.1) with my installation of Ubuntu Server 18.04.2. I have managed to install it, but it seems that the new installation is not correctly connected to all the dependencies (or perhaps I need to manually upgrade other packages to get them in sync with my upgraded QEMU?)



the error I got was:



ERROR    unsupported configuration: this QEMU does not support 'qxl' video device
Removing disk 'WINVM.img' | 0 B 00:00
Domain installation does not appear to have been successful.
If it was, you can restart your domain by running:
virsh --connect qemu:///system start myWINVM
otherwise, please restart your installation.


Do my suspicions about the cause of the problem seem reasonable? What should I try to get QXL working again (it was working before the QEMU upgrade).










share|improve this question


















  • 1





    You're on the cutting edge! The documentation for 3.1.50 indicates that it does support qxl, but it's unclear which version you are running. You could try being on the bleeding edge by compiling from the git source. Another alternative would be to load Ubuntu 19.04, which uses qemu 3.1 - but I think that this has more to do with development versions of the programs...

    – Charles Green
    Feb 20 at 16:09











  • I am using 3.1.0, which I downloaded and compiled from here: download.qemu.org/qemu-3.1.0.tar.xz

    – Thoughtcraft
    Feb 20 at 16:16








  • 1





    The webpage for qemu has instructions for downloading the very latest development version, downloading and building from git.

    – Charles Green
    Feb 20 at 16:26











  • OK that didn't work, I think next I will step back to 3.0 and see if that works.

    – Thoughtcraft
    Feb 21 at 0:37
















0















I want to use the latest version of QEMU (3.1) with my installation of Ubuntu Server 18.04.2. I have managed to install it, but it seems that the new installation is not correctly connected to all the dependencies (or perhaps I need to manually upgrade other packages to get them in sync with my upgraded QEMU?)



the error I got was:



ERROR    unsupported configuration: this QEMU does not support 'qxl' video device
Removing disk 'WINVM.img' | 0 B 00:00
Domain installation does not appear to have been successful.
If it was, you can restart your domain by running:
virsh --connect qemu:///system start myWINVM
otherwise, please restart your installation.


Do my suspicions about the cause of the problem seem reasonable? What should I try to get QXL working again (it was working before the QEMU upgrade).










share|improve this question


















  • 1





    You're on the cutting edge! The documentation for 3.1.50 indicates that it does support qxl, but it's unclear which version you are running. You could try being on the bleeding edge by compiling from the git source. Another alternative would be to load Ubuntu 19.04, which uses qemu 3.1 - but I think that this has more to do with development versions of the programs...

    – Charles Green
    Feb 20 at 16:09











  • I am using 3.1.0, which I downloaded and compiled from here: download.qemu.org/qemu-3.1.0.tar.xz

    – Thoughtcraft
    Feb 20 at 16:16








  • 1





    The webpage for qemu has instructions for downloading the very latest development version, downloading and building from git.

    – Charles Green
    Feb 20 at 16:26











  • OK that didn't work, I think next I will step back to 3.0 and see if that works.

    – Thoughtcraft
    Feb 21 at 0:37














0












0








0








I want to use the latest version of QEMU (3.1) with my installation of Ubuntu Server 18.04.2. I have managed to install it, but it seems that the new installation is not correctly connected to all the dependencies (or perhaps I need to manually upgrade other packages to get them in sync with my upgraded QEMU?)



the error I got was:



ERROR    unsupported configuration: this QEMU does not support 'qxl' video device
Removing disk 'WINVM.img' | 0 B 00:00
Domain installation does not appear to have been successful.
If it was, you can restart your domain by running:
virsh --connect qemu:///system start myWINVM
otherwise, please restart your installation.


Do my suspicions about the cause of the problem seem reasonable? What should I try to get QXL working again (it was working before the QEMU upgrade).










share|improve this question














I want to use the latest version of QEMU (3.1) with my installation of Ubuntu Server 18.04.2. I have managed to install it, but it seems that the new installation is not correctly connected to all the dependencies (or perhaps I need to manually upgrade other packages to get them in sync with my upgraded QEMU?)



the error I got was:



ERROR    unsupported configuration: this QEMU does not support 'qxl' video device
Removing disk 'WINVM.img' | 0 B 00:00
Domain installation does not appear to have been successful.
If it was, you can restart your domain by running:
virsh --connect qemu:///system start myWINVM
otherwise, please restart your installation.


Do my suspicions about the cause of the problem seem reasonable? What should I try to get QXL working again (it was working before the QEMU upgrade).







graphics virtualization kvm qemu






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked Feb 20 at 15:51









ThoughtcraftThoughtcraft

1095




1095








  • 1





    You're on the cutting edge! The documentation for 3.1.50 indicates that it does support qxl, but it's unclear which version you are running. You could try being on the bleeding edge by compiling from the git source. Another alternative would be to load Ubuntu 19.04, which uses qemu 3.1 - but I think that this has more to do with development versions of the programs...

    – Charles Green
    Feb 20 at 16:09











  • I am using 3.1.0, which I downloaded and compiled from here: download.qemu.org/qemu-3.1.0.tar.xz

    – Thoughtcraft
    Feb 20 at 16:16








  • 1





    The webpage for qemu has instructions for downloading the very latest development version, downloading and building from git.

    – Charles Green
    Feb 20 at 16:26











  • OK that didn't work, I think next I will step back to 3.0 and see if that works.

    – Thoughtcraft
    Feb 21 at 0:37














  • 1





    You're on the cutting edge! The documentation for 3.1.50 indicates that it does support qxl, but it's unclear which version you are running. You could try being on the bleeding edge by compiling from the git source. Another alternative would be to load Ubuntu 19.04, which uses qemu 3.1 - but I think that this has more to do with development versions of the programs...

    – Charles Green
    Feb 20 at 16:09











  • I am using 3.1.0, which I downloaded and compiled from here: download.qemu.org/qemu-3.1.0.tar.xz

    – Thoughtcraft
    Feb 20 at 16:16








  • 1





    The webpage for qemu has instructions for downloading the very latest development version, downloading and building from git.

    – Charles Green
    Feb 20 at 16:26











  • OK that didn't work, I think next I will step back to 3.0 and see if that works.

    – Thoughtcraft
    Feb 21 at 0:37








1




1





You're on the cutting edge! The documentation for 3.1.50 indicates that it does support qxl, but it's unclear which version you are running. You could try being on the bleeding edge by compiling from the git source. Another alternative would be to load Ubuntu 19.04, which uses qemu 3.1 - but I think that this has more to do with development versions of the programs...

– Charles Green
Feb 20 at 16:09





You're on the cutting edge! The documentation for 3.1.50 indicates that it does support qxl, but it's unclear which version you are running. You could try being on the bleeding edge by compiling from the git source. Another alternative would be to load Ubuntu 19.04, which uses qemu 3.1 - but I think that this has more to do with development versions of the programs...

– Charles Green
Feb 20 at 16:09













I am using 3.1.0, which I downloaded and compiled from here: download.qemu.org/qemu-3.1.0.tar.xz

– Thoughtcraft
Feb 20 at 16:16







I am using 3.1.0, which I downloaded and compiled from here: download.qemu.org/qemu-3.1.0.tar.xz

– Thoughtcraft
Feb 20 at 16:16






1




1





The webpage for qemu has instructions for downloading the very latest development version, downloading and building from git.

– Charles Green
Feb 20 at 16:26





The webpage for qemu has instructions for downloading the very latest development version, downloading and building from git.

– Charles Green
Feb 20 at 16:26













OK that didn't work, I think next I will step back to 3.0 and see if that works.

– Thoughtcraft
Feb 21 at 0:37





OK that didn't work, I think next I will step back to 3.0 and see if that works.

– Thoughtcraft
Feb 21 at 0:37










0






active

oldest

votes











Your Answer








StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "89"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});

function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});


}
});














draft saved

draft discarded


















StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1119882%2fmanually-upgraded-qemu-3-1-does-not-support-qxl-video-device%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown

























0






active

oldest

votes








0






active

oldest

votes









active

oldest

votes






active

oldest

votes
















draft saved

draft discarded




















































Thanks for contributing an answer to Ask Ubuntu!


  • Please be sure to answer the question. Provide details and share your research!

But avoid



  • Asking for help, clarification, or responding to other answers.

  • Making statements based on opinion; back them up with references or personal experience.


To learn more, see our tips on writing great answers.




draft saved


draft discarded














StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1119882%2fmanually-upgraded-qemu-3-1-does-not-support-qxl-video-device%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown





















































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown

































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown







Popular posts from this blog

Mouse cursor on multiple screens with different PPI

Agildo Ribeiro

Sometime when accessing a menu: “Ubuntu 16.04 has experienced an internal error”