Installed virt-manager,
target virtual machine is debian jessie with spice-vdagent installed
shared clipboard, and latency-free mouse input works
Display: Spice
Video: QXL
Channel spice: spicevmc, virtio, com.redhat.spice.0 (confirmed /dev devices exist in target vm)
Make sure guest resizing is enabled in virt-manager:
Menu View -> Scale Display ->
Auto resize VM with window (Checked)
Make sure your have a spice agent on your guest (the virtual machine)
https://www.spice-space.org/download.html#guest
'spice-vdagent' on linux
'spice-guest-tools' on windows
How I figured this out,
I found a setting in "spicy" that I assumed had an equivalent in virt-maanger. To connect with spicy from spice-client-gtk apt package, I found the port to connect to by checking sudo ss -nlp | grep qemu, and connected to that port on localhost. Spicy's toggle was much easier to find: Options -> Resize guest to match window size (Checked).
For XFCE, this is a known bug which does not appear to have been fixed yet (confirmed still broken in Xubuntu 20.04).
This issue is due to a change in spice-vdagent whereby instead of changing the resolution directly, it instead notifies the DE to make the change, and that functionality has not been implemented yet in XFCE.
One workaround is to run the following in the guest every time you resize your window:
$ xrandr --output Virtual-1 --auto
According to Installing Windows 10 in KVM + libvirt, visit Spice then scroll down to Windows binaries and then click the link spice guest tools. Proceed to install the spice tools after download completes. Once installation is complete, you should be able to get the guest VM resolution to match that of the resized VM window.
For me, "Auto resize VM with window" was greyed out until I installed the spice guest tools; I did not even have to reboot after installation - this feature was available immediately and it just worked - :).
Host machine: Ubuntu 16.04.6 LTS (Xenial Xerus)
Guest VM: Windows 10 Pro (Version 1809 build 17763.379)
#ThorSummoner's approach works, but if you have a high resolution monitor, the guest video driver may not have enough memory to draw the larger screen. In that case, you will need to increase the video memory, but unfortunately the virt-manager GUI doesn't provide a method to do so. So instead follow this procedure:
View -> Details -> copy the UUID.
sudo virsh edit <copied uuid>
Look for a line like the following: <model type='qxl' ram='65536' vram='65536' vgamem='16384' heads='1' primary='yes'/>. Your type and other parameters may be different, but as long as there's a vgamem, you can continue.
Change vgamem to 32768
Save & exit. The config file will automatically be checked for errors.
Then restart your VM, and try again.
Short answer that worked for me:
I also have Display set to Spice. If the VM's virtual Video hardware was set to VGA or QXL, I could not resize the desktop in the guest. When I changed Video to Virtio in virt-manager and restarted the VM, it worked.
Longer background in case it's useful to future visitors:
I ran into this problem in May 2020 and while the older answers here were of some help I thought I'd add some clarifications since the virt-manager UI and libvirt capabilities continuously evolve.
In my case, I have a Fedora 32 (KDE Spin) Linux host and the same OS in the guest. My virt-manager version is 2.2.1.
As with thorsummoner's original situation above I am using Display Spice so I can have goodies like the shared clipboard between host and guest.
The guest seemed stuck on 1024x768. xrandr in the guest showed lots of higher resolutions available, but when I tried to set the resolution to 1920x1080 -- whether with xrandr --output Virtual-1 --mode 1920x1080 or with Plasma's Display setting -- it would only momentarily change to the higher resolution. Then, clunk, it would change right back.
Explicitly setting a higher level VGA video memory did not work (although it did help for another problem long ago).
No matter what I set virt-manager's View -> Scale to display menu options to, this still happened.
The fix for me was in the virtual hardware Video settings. Note: not Display, but a separate entry further down in the left-hand-side Hardware list in virt-manager.
If video was set to VGA or QXL, I could not resize the guest.
Then I changed the video hardware to Virtio, and the problem went away. I could resize the desktop with either xrandr commands or the GUI Display preferences, and the changes would stick even after restarts.
Of course the guest VM should be cleanly shut down before making this change to its virtual hardware settings.
What worked for me is much simplified modified ThorSummoner's answer:
Step 1:
View > Scale Display > Always
Step 2:
View > Scale Display > Auto Resize VM with window
Step 3:
In the guest OS, set the desired resolution.
I tried everything I saw to make it work but the only thing that worked for me was to set video to QXL (didn't tried Virtio or VGA after that tho) and do a proper shutdown of the Windows 10 VM (from inside the VM, do a "shutdown"). If you use the reboot from virt-manager it seem's like it doesn't reboot entirely.
What worked for me (finally!):
Debian 11.6 on my host laptop.
Debian unstable as my guest VM.
In the guest, "apt install spice-vdagent".
In the guest details (View / Details):
Display Spice = Spice Server
Video = QXL
View / Scale Display = Always
When logged into KDE Plasma (X11) as my Desktop Environment, the View / Scale Display had the "Auto-resize window with VM" option selected, but it was grayed out and KDE's resolution would not resize as I changed the guest window size; it would scale to some degree, but it seemed to be using a magnification effect rather than actually changing the resolution.
When logged into Cinnamon or into Gnome (just plain "Gnome", not "Gnome Wayland" or "Gnome on Xorg" or any of the other Gnome options in my selection pull-down menu), the View / Scale / Auto-resize was not grayed out, and both DE's resized as I resized the guest window.
Note: the resizing was not instantaneous; it took a second or two after I finished resizing the guest window before the DE changed resolution to match.
In my case, I had manually set resolution to 1920x1080 prior to booting with SPICE vdagent. I just had to go to settings, display (will depend slightly between DE), and select the resolution corresponding to SPICE resize mode.
For those of you who still haven't got virt to auto-resize with suggested config (spice channel, spice guest tool, QXL), this is how I solved mine.
Background: I got it to auto resized before, but I got a clean install of ubuntu, and using the same config, same vm files (was actually physical partition), but I can't get it to resize again. I got spice channel in the config with QXL video, spice guest tools in windows guest, but still can get it to resize.
So finally, I just got a clean install of both windows and my distro (this is not the solution, just indicating that my config was clean). I tried again with the same config but nothing work, and I started to wonder if windows I the problem here, which it ultimately was. I checked the device manager to see that 2 virtio drivers were rejected by windows secure boot. So as an instinct I went in tiano bios (ovmf) and disable secure boot. It's working fine now.
Form me it was just a matter of going to the VM click Show virtual hardware details icon, resize that window, then click back on the Show the graphical window icon since they share the same window.
Resizing on Windows guest works if you install the virtio display driver.
Open "Device Manager", right click on "Display adapters", right click on the one entry you find, then "Update driver", browse for a driver, select the virtio ISO, and install the driver.
Notice the entry won't be displayed with a yellow warning sign, as Windows will use the Microsoft Basic Display Adapter drivers, and so it is all fine for it.
I installed GRUB and it only shows GRUB on the screen, I am unable to type anything. I am unable to get back into my bios to boot from usb.
Any help would be appreciated
If the only thing you see is GRUB printed on the screen, something is wrong with your grub installation.
You can follow these steps to correct:
Boot the PC from a livecd USB or CDROM (can be Ubuntu, for example)
Reinstall grub by typing grub-install /dev/<target block device>
Reboot and test
If you still have issues after these steps post what you're getting
I am really new to Windows Phone 8 App development. I would be grateful to you if you can answer my question. I have a machine with Intel(R) Core(TM) i3 processor and when checked I found out that my virtualization setting enabled.
I installed Windows Pro 8.1 in to my machine and then it indicates that my Hyper Visor is default switched off and I had to run it. But when I run it after making some of the changes by restarting the machine, suddenly for some unknown reason it undoes every change made finally leaving the machine with no Hyper Visor running.
I come across the same process when I am to run the Windows Phone emulator to test Windows Phone 8 Apps.
I hope my issue is clear to you all, can someone help me to fix this issue or tell me the exact reason behind this?
I would look at my Windows Event log and see if you perhaps there's a problem with Hyper-V being incompatible with a driver or something like that. It may be failing to reboot and the doing a system restore to get the machine back to a bootable state (by rolling back Hyper-V). I've had problems with Hyper-V and my HP laptop's blue tooth drivers:
Here's the thread where I found out about that:
HP Bluetooth / Hyper-V woes
Updating the driver to the newest version on HP's site fixed my computer for a while, but then I had problems with Windows Update hosing my machine with an update to the Bluetooth driver.
I seem to have fixed it for good by going to RA Link's website and downloading a version of the driver that's newer than the one on HP's website. I'm not at my personal computer right now, but if you'd like I can see if I can find the driver version that seems to have fixed my Bluetooth/hyper-v problems for good.
-Eric
I got a beaglebone black version and downloaded the starterware for example code. I can build .bin file but I have no idea how to make it work in the board. I put the MLO and modify 'gpioLedBlink.bin' name to 'app' and put them into SD card. Open the power, I know beaglebone didn't get into the original linux, but it only open USER LED 012, but there no led blink. I think the program didn't really work.
How should I solve this problem? And how can I use gdb to debug the program?
Another question is that there is no ttyUSB* when I plug the usb. How should I get the linux information when beagle black get into the original linux. THX.=)
Use Uboot and loady to load your binary over serial (default address is 0x8020 0000). Once it has loaded, go 0x80200000.
GL.
I have the same problem with this post: MSDN Post. It seems nobody answered with a working solution on that thread.
The symptoms:
Kinect SDK 1.5 installed.
The Kinect device is recognized and drivers seem to be loaded correctly.The speech demo works correctly.
Skeleton Viewer shows "Could not enable Skeleton Tracking".
Shape Game starts, but does not track anything.
Kinect Explorer starts the small windows only showing that it has connected to the Kinect, the black window does not open. If I close the white window, the kinect explorer is still running I have to quit it through the task manager.
When I unplug and plug the USB after I open Kinect explorer; it says insufficient bandwith.
I tried:
Updated BIOS.
Updated motherboard software. (ASUS Maximus IV Gene-Z, Gen3)
Removed all USB's and plugged them all.
Restarted windows. (several million times)
I uninstalled and re installed. Kinect SDK 1.0. (but everything is the same)
My OS: Windows 7 64 bit Ultimate.
I have been struggling with this for 1 complete day. Any suggestions will be greatly appreciated.
EDIT: I tried my Kinect device on another computer (laptop), and it works.
If the Kinect shares a USB Controller with other devices, a problem such as yours can happen easily.
Try the following: Unplug all USB devices, then connect only the Kinect to your computer. If you have USB mouse and/or keyboard, plug those into a different set of ports (for example front usb ports if you have the Kinect plugged into the back of the computer). Then, try running the SDK's sample applications.
Should this approach fail, something might be wrong with your USB controller(s).
One more option: Try running the sample applications on a different Windows computer, preferably a laptop of some type, since you won't need to plug in any additional USB devices.
If this approach fails, your Kinect is most likely defective. In which case you can get a replacement or refund from your retailer, if the purchase didn't happen too long ago.
Best of luck to you!
I finally was able to made my kinect work. This MSDN Discussion helped me to do that.
The solution:
Uninstall all Kinect Drivers from Control Panel.
Reinstall Kinect SDK.
(IMPORTANT) Make sure to skip getting drivers from windows update during driver installation.
And yay! It works beautifuly ..
The same happened with me; I noticed a windows update related to Kinect, installed it. Kinect stopped working. Installing SDK from May 2d 2012 didn't fix the problem. Rolling back to February 2010 SDK didn't fix it either. At first I guessed that Microsoft doesn't want us to use Kinect for Xbox any more, and this is their way of telling us to buy Kinect for Windows... well, may be - but in my case Kinect Camera driver was somehow updated to Version 1.5 (May 2, 2012), while everything else was on version 1.0. Installing original driver fixed the problem.