Access to individual VMs
by Dennis Jacobfeuerborn
Hi,
Is it possible to provide access to individual VMs using virsh or
virt-manager? What I'm specifically trying to do is to give users the
ability to shutdown/destroy/start their own virtual machines in case the VM
hangs. Is this possible?
Regards,
Dennis
14 years, 2 months
burning spice question :-).
by Tom Horsley
Has anyone played with spice enough to answer the burning question:
Does it provide high enough performance video for the espn360
viewer app to be willing to install and run? :-).
14 years, 2 months
Re: [fedora-virt] Guest resolution notabug?
by Scott Dowdle
Paul,
----- "Paul Lambert" <eb30750(a)gmail.com> wrote:
> The host is FE-12 x86_64 and the guest is x86_32 (i386). Why would the
> same software not recognize the same hardware running as a guest? Most
> likely because the virt manager software simply restricts the
> resolution choices. The goal of virtualization is to make all guest
> runs as "pass through" operating systems where the guest can do what
> the host can do.
KVM has some PCI pass-thru features but I'm not that familiar with them. I believe that when used the device has to be dedicated to the VM... but I'm not sure.
Yes, I understand that some other virtualization products do give you much more flexibility with video options including some offering accelerated 3D video in the VM (under certain conditions) but that isn't something built in with virt-manager and the VNC connector it offers. Of course a SPICE video option in virt-manager will be much different once it makes it into Fedora in a usable way but we aren't there yet.
One work around is to run vncserver, freenx or whatever similar client/server app you'd like in the VM specifying the desired resolution and then connect to it with a client app. For example I sometimes simulate a netbook resolution for people who want to try out 1024x600 before commiting to that resolution with netbook hardware. I think getting a real (or virtualized) video card to do 1024x600 is problematic but VNC handles it just fine. One of the drawbacks of doing it that way though is you don't get access to the virtual consoles like you do using virt-manager/VNC.
So while it feels like a bug to you, it is really just missing functionality in the virtual video cards offered by KVM/qemu today. To the best of my knowledge it isn't specific to Fedora and applies to all distros using KVM.
TYL,
--
Scott Dowdle
704 Church Street
Belgrade, MT 59714
(406)388-0827 [home]
(406)994-3931 [work]
14 years, 2 months
Re: [fedora-virt] Guest resolution notabug?
by Kenni Lund
2010/2/16 Paul Lambert <eb30750(a)gmail.com>:
> Kenni,
>
> My graphics card is an ATI Radeon that might be contributing to the problem
> somewhat. My point is regardless of the resolution why does the VM cpu
> display "unknown" for the graphics while the host recognizes the monitor as
> 17" and gives me a choice of resolutions.
No, your ATI Radeon card has nothing to do with the "problem". You
need to understand that your host has access to your real hardware:
graphics card, monitor, HDDs, RAM, CPU, etc. while your VM has NO
ACCESS to your real hardware. Therefore it doesn't know your monitor,
your graphics card, your HDDs, your CPU, etc. etc.
It's a VIRTUAL machine, the hardware in the VM is virtual as well (eg.
the hardware is not physical, you'll never be able to touch the
hardware of your VM - it doesn't exist in real life, only in software
on your computer).
Best Regards
Kenni Lund
14 years, 2 months
Guest resolution notabug?
by Paul Lambert
I submitted bug 548626 regarding the fact that the guest VM does not
recognize the fullest screen resolution of the host monitor. My bug report
was closed as being "notabug." This was also identified as a bug in report
479792 previously. In addition bug reports 474831 and 509117 document
screen resolution issues related to the guest. These bug reports were also
closed with no corrective action.
This is a bug and needs to be addressed.
Paul
14 years, 2 months
Re: [fedora-virt] Guest resolution notabug?
by Scott Dowdle
Paul,
So far as I know the max resolution of a KVM VM from VNC in virt-manager is 1024x768 with the cirrus adaptor type and that was added in Fedora 11. See:
http://fedoraproject.org/wiki/Features/VirtImprovedConsole
I think if you use another adaptor type your resolution options might differ.
----- "Paul Lambert" <eb30750(a)gmail.com> wrote:
> I submitted bug 548626 regarding the fact that the guest VM does not
> recognize the fullest screen resolution of the host monitor. My bug
> report was closed as being "notabug." This was also identified as a
> bug in report 479792 previously. In addition bug reports 474831 and
> 509117 document screen resolution issues related to the guest. These
> bug reports were also closed with no corrective action.
>
> This is a bug and needs to be addressed.
>
> Paul
>
>
>
> _______________________________________________
> virt mailing list
> virt(a)lists.fedoraproject.org
> https://admin.fedoraproject.org/mailman/listinfo/virt
--
Scott Dowdle
704 Church Street
Belgrade, MT 59714
(406)388-0827 [home]
(406)994-3931 [work]
14 years, 2 months
Fedora virt status
by Justin Forbes
Fedora 13
=========
Feature Freeze deadline for F-13 was earlier this week, and all packages
should be feature complete. Now it is time to widdle down the bug list
and get F13 as clean as possible.
F-13 schedule:
2010-02-16 Alpha Freeze (4 days)
2010-03-23 Beta (Final Development) Freeze (39 days)
2010-04-29 Compose Release Candidate (76 days)
Fedora Cloud SIG
================
Progressis being made towards updated Fedora in the EC2 cloud, and
There is some interest in supporting the IBM Cloud. More details
can be found at https://fedoraproject.org/wiki/Cloud_SIG
F12 Virt Preview
================
As was announced before, the virt-preview repository for F12 users wishing
to test out the latest virtualization bits is available. Instructions for
using this repository can be found at:
https://fedoraproject.org/wiki/Virtualization_Preview_Repository
Recent updates in this repository include:
python-virtinst-0.500.2-1:
- Update to version 0.500.2
- virt-install --autostart option for setting domain autostart flag
- virt-install --host-device now supports values via lsusb and lspci
qemu-0.12.2-6:
- Add vhost net support
virt-manager-0.8.3-1:
- Update to 0.8.3 release
- Manage network interfaces: start, stop, view, provision bridges, bonds, etc.
- Option to 'customize VM before install'.
Bugs
====
DOOM-O-METER: 238 bugs open 1 week ago, up to 244 now.
Feature Freeze has happened, so it is time to really start attacking
this bug list! Anyone wishing to help can find more information at:
http://fedoraproject.org/wiki/Virtualization_bugs
= Important =
== kernel ==
https://bugzilla.redhat.com/show_bug.cgi?id=545851
KVM/networking-related crash
A patch has been submitted upstream, and this should be fixed with
the next kernel update.
== kvm ==
https://bugzilla.redhat.com/show_bug.cgi?id=555788
SIGTRAP leakage between separate virtual machines
Patches have been posted for this, and a resolution is coming soon.
This requires kernel patches, so timeframe coinsides with the 2.6.32
update for F12.
https://bugzilla.redhat.com/show_bug.cgi?id=478317
almost 9 thousand syscalls per second while idle
This is believed to be a result of the USB Tablet device, but several
users have noticed high host CPU usage while guests were idle.
https://bugzilla.redhat.com/show_bug.cgi?id=544339
Segfaults logged from kvm (qemu-kvm) resulting in guest sudden crash
and data loss
A number of users complaining of guests crashing and sometimes taking
the host with them. This appears to be related to sound emulation.
We are waiting for feedback from virt-preview users.
https://bugzilla.redhat.com/show_bug.cgi?id=544940
reattach virtio to rhel{5,6} guests will cause qemu-kvm crash
14 years, 2 months
ANNOUNCE: New releases virt-manager 0.8.3 and virtinst 0.500.2
by Cole Robinson
I'm happy to announce two new releases:
virt-manager 0.8.3: virt-manager is a desktop application for managing
KVM and Xen virtual machines via libvirt.
virtinst 0.500.2: virtinst is a collection of command line tools for
provisioning libvirt virtual machines, including virt-install and
virt-clone.
The releases can be downloaded from:
http://virt-manager.org/download.html
The direct download links are:
http://virt-manager.org/download/sources/virt-manager/virt-manager-0.8.3....
http://virt-manager.org/download/sources/virtinst/virtinst-0.500.2.tar.gz
The virt-manager release includes:
- New ability to manage network interfaces: start, stop, and view
existing interfaces. Provision new bridge, bond, and vlan devices.
- New option to 'customize VM before install', which allows adjusting
most VM options from the install wizard.
The virtinst release includes:
- virt-install: --autostart option for setting domain autostart flag
- virt-install: Allow specifying --host-device with lsusb and lspci
format (0x1234:0x5678 for USB, etc)
- virtinst: New 'Interface' module for building libvirt interface XML
Thanks to everyone who has contributed to this release through testing,
bug reporting, submitting patches, and otherwise sending in feedback!
Thanks,
Cole
14 years, 2 months
