Re: [fedora-virt] F12 virtual screen resolution
by Brendan Whelan
The only options in the guest are 640x480 and 800x600.
I don't know where the list is stored where I could add another set of
values.
Brendan
Ján ONDREJ (SAL) wrote:
> Then I don't know. Have you tryed to change resolution in guest?
> Which choices are available?
>
> SAL
>
> On Fri, Dec 11, 2009 at 02:00:59PM +0000, Brendan Whelan wrote:
>
>> virsh edit MACHINE_NAME showed my video system to be the same as
>> yours. i.e. <model type='cirrus' vram='9216' heads='1'/>
>>
>> Is there any way that I can refine this or adjust other settings to improve the resolution?
>>
>> Brendan
>> Ján ONDREJ (SAL) wrote:
>>
>>
>>> I have this in virt-manager, but I am using Fedora 13 preview repository for
>>> Fedora 12. If you don't have this, use virsh edit:
>>>
>>> virsh edit MACHINE_NAME
>>>
>>> Try to search for video section and try to replace it with something like:
>>>
>>> <video> <model type='cirrus' vram='9216' heads='1'/>
>>> </video>
>>>
>>> SAL
>>>
>>> On Fri, Dec 11, 2009 at 01:30:35PM +0000, Brendan Whelan wrote:
>>>
>>>> Hi Sal, Thanks for the response.
>>>> The laptop is a Dell Latitude E5500 with an Intel GMA 4500MHD chip set.
>>>> I just created the Centos client using the GUI interface and wasn't
>>>> asked about the graphics chip.
>>>> How can I refine my settings?
>>>> Thanks, Brendan
>>>> ---------------------------------------------------------
>>>> Ján ONDREJ (SAL) wrote:
>>>>
>>>>> Hello,
>>>>>
>>>>> which video card model you selected in guest? With cirrus it's working
>>>>> well for me at 1024x768 and may be for more too.
>>>>>
>>>>> SAL
>>>>>
>>>>> On Fri, Dec 11, 2009 at 10:38:58AM +0000, Brendan Whelan wrote:
>>>>>
>>>>>> I have installed F12 on a laptop and created a Centos client. The
>>>>>> host, F12, system uses a screen resolution of 1280x800. Is there any
>>>>>> way to increase the resolution for the client beyond 800x600?
>>>>>> Thanks, Brendan
>>>>>>
>>>>>> _______________________________________________
>>>>>> Fedora-virt mailing list
>>>>>> Fedora-virt(a)redhat.com
>>>>>> https://www.redhat.com/mailman/listinfo/fedora-virt
>>>>>>
>
>
14 years, 4 months
[OT?] value of virtualization that comes with RHEL 5.4?
by Robert P. J. Day
i'm being offered the chance to teach an admin course based on RHEL
5.4, so i'll probably just do it under CentOS 5.4, but one of the
chapters deals with the virtualization facilities that come with 5.4.
even though that's the latest release of RHEL/CentOS, it's still
fairly far behind the curve in terms of recent virtualization
developments as compared to fedora 12. the client is currently using
vmware, so it's not clear they even *care* about the native
virtualization features of RHEL.
in any case, is there any real value in discussing the
virtualization in RHEL 5.4, since the other two options are:
1) blow off virt completely as explained in the manual, or
2) switch to perhaps f12 just for that to show what's available
*today*
thoughts? no matter what the decision is, i can't see covering old
virtualization technology being of much use.
rday
--
========================================================================
Robert P. J. Day Waterloo, Ontario, CANADA
Linux Consulting, Training and Kernel Pedantry.
Web page: http://crashcourse.ca
Twitter: http://twitter.com/rpjday
========================================================================
14 years, 4 months
re: [fedora-virt] DRBD and virtualization
by Gianluca Cecchi
> Does this have any implications for virtualization? It's just that I
> notice there's a whole section in the DRBD manual about using it to
> provide replicated block devices for virtual machines:
Currently I'm using it in primary/primary mode with two F12 x86_64
servers and it is working.
(I began to test in F11 + rawvirt repo days with drbd 8.3.3rc, now in 8.3.6)
For live migration too and it is working...
yet doing various testings/evalutations for configurations and mix
about keeping drbd part inside cluster infra or outside....
Gianluca
14 years, 4 months
hot add scsi disk supposed to work on f12 qemu/kvm host?
by Gianluca Cecchi
Hello,
F12 with qemu-kvm updated components.
Also installed virt-manager 0.8.1 from updates-testing repo.
I have a CentOS 5.4 guest x86_64.
If I remember well (probably from the kvm test day for which I don't
find the full log I found at time...), hot add of scsi disk should
work if there is already a scsi disk into the guest (and if the guest
supports it).
I presume CentOS 5.4 supports in general hot add of scsiu disks, as I
do this sometimes to SAN connected disks.
So I have this pre-condition with an sda device already configured and
used on a running guest.
I add a new scsi disk, but I don't see any new disk in guest.
I have acpihp kernel module loaded in guest.
>From posts in other mailing lists it seems that probably I should also
have pci_hotplug kernel module, but I don't find it under
2.6.18-164.6.1.el5 kernel ....
When I add the disk from virt-manager (it doesn't say that it will be
operational after next reboot, btw) I see a new controller in guest
and not a new disk attached to the same controller.... and in dmesg:
sym1: <895a> rev 0x0 at pci 0000:00:06.0 irq 11
sym1: No NVRAM, ID 7, Fast-40, LVD, parity checking
sym1: SCSI BUS has been reset.
scsi2 : sym-2.2.3
and in messages:
Dec 10 17:21:04 c54vm1 kernel: PCI: Ignore bogus resource 6 [0:0] of
0000:00:02.0
Dec 10 17:21:04 c54vm1 kernel: decode_hpp: Could not get hotplug
parameters. Use defaults
Dec 10 17:21:04 c54vm1 kernel: PCI: Enabling device 0000:00:06.0 (0000 -> 0003)
Dec 10 17:21:04 c54vm1 kernel: ACPI: PCI Interrupt 0000:00:06.0[A] ->
Link [LNKB] -> GSI 11 (level, high) -> IRQ 11
Dec 10 17:21:04 c54vm1 kernel: sym1: <895a> rev 0x0 at pci 0000:00:06.0 irq 11
Dec 10 17:21:04 c54vm1 kernel: sym1: No NVRAM, ID 7, Fast-40, LVD,
parity checking
Dec 10 17:21:04 c54vm1 kernel: sym1: SCSI BUS has been reset.
Dec 10 17:21:04 c54vm1 kernel: scsi2 : sym-2.2.3
But fdisk -l gives no added scsi disk.
tried also with:
[root@c54vm1 ~]# echo "- - -" > /sys/class/scsi_host/host2/scan
but nothing.
[root@c54vm1 ~]# find /sys -iname "*scan"
gives
/sys/class/scsi_host/host2/scan
/sys/class/scsi_host/host0/scan
/sys/devices/pci0000:00/0000:00:04.0/host0/target0:0:0/0:0:0:0/rescan
in /sys filesystem, this is the situation about the newly added controller
[root@c54vm1 ~]# ll /sys/devices/pci0000\:00/0000\:00\:06.0/host2/
total 0
drwxr-xr-x 2 root root 0 Dec 10 17:21 power
lrwxrwxrwx 1 root root 0 Dec 11 15:23 scsi_host:host2 ->
../../../../class/scsi_host/host2
lrwxrwxrwx 1 root root 0 Dec 11 15:23 spi_host:host2 ->
../../../../class/spi_host/host2
--w------- 1 root root 4096 Dec 11 15:23 uevent
while for the controller related to sda:
[root@c54vm1 ~]# ll /sys/devices/pci0000\:00/0000\:00\:04.0/host0/
total 0
drwxr-xr-x 2 root root 0 Dec 10 12:57 power
lrwxrwxrwx 1 root root 0 Dec 10 12:57 scsi_host:host0 ->
../../../../class/scsi_host/host0
lrwxrwxrwx 1 root root 0 Dec 10 12:57 spi_host:host0 ->
../../../../class/spi_host/host0
drwxr-xr-x 4 root root 0 Dec 10 12:57 target0:0:0
--w------- 1 root root 4096 Dec 10 12:57 uevent
any hint or clarification about current hot add of scsi (or virtio) disks?
And also about suggested disk type (ide vs scsi vs virtio) in case of
RHEL/CentOS 4 and 5 guests with F12 hosts.
Thanks in advance,
Gianluca
14 years, 4 months
F12 virtual screen resolution
by Brendan Whelan
I have installed F12 on a laptop and created a Centos client. The host,
F12, system uses a screen resolution of 1280x800. Is there any way to
increase the resolution for the client beyond 800x600? Thanks, Brendan
14 years, 4 months
Re: [Fedora-xen] Fedora xen-3.4.2 rpms
by Boris Derzhavets
I've met another problem . Upgrading libvirt via F13 rawhide, breaks virsh connection to
xen been built via the most recent xen-3.4.1-5.fc12.src.rpm . Once , this question was already posted by me to fedora-virt with no feedback. Working libvirt version for Xen
seems to be 0.7.1-15 as max.
Boris.
________________________________
From: Gerd Hoffmann <kraxel(a)redhat.com>
To: Pasi Kärkkäinen <pasik(a)iki.fi>
Cc: fedora-xen(a)redhat.com
Sent: Thu, December 10, 2009 4:40:25 PM
Subject: Re: [Fedora-xen] Fedora xen-3.4.2 rpms
On 12/10/09 09:47, Pasi Kärkkäinen wrote:
> On Thu, Nov 19, 2009 at 10:47:18AM +0200, Pasi Kärkkäinen wrote:
>> Hello again,
>>
>> Xen 3.4.2 was released last week with a lot of updates, so it would be
>> good to sync the Fedora rpm again.
>>
>
> Doesn't seem to require much changes to the .spec:
> http://bderzhavets.wordpress.com/2009/11/28/hot-hypervisor-upgrade-up-to-...
Committed and building for rawhide, F12 will follow.
What is the status of the fixes you've mailed a while back and I've
never came around committing? Are they in the 3.4.2 release and thus
obsolete now?
cheers,
Gerd
--
Fedora-xen mailing list
Fedora-xen(a)redhat.com
https://www.redhat.com/mailman/listinfo/fedora-xen
14 years, 4 months
Question about virt-manager devel for Fedora 13
by Scott Dowdle
Greetings,
I attended the RH Virtual Experience 2009 event today and got to talk with some RH RHEV guys... which led me to a few questions about what might be in the future for Fedora. I checked the upcoming features page for F13 and nothing is there yet for virt... but just probing to see if anyone has a clue.
Most of the SPICE stuff has been released at spice-space.org. Are there any plans to add the SPICE protocol to the virt-manager app in Fedora 13?
And a follow-up question... Anyone considering creating a general purpose remote desktop client / server app for Fedora 13 based on SPICE to be a much more performant remote access protocol than freenx and VNC?
I've got about $0.75 to offer as bounty. :)
TYL,
--
Scott Dowdle
704 Church Street
Belgrade, MT 59714
(406)388-0827 [home]
(406)994-3931 [work]
14 years, 4 months
fc12 virsh tap networking problem
by Chiradeep Vittal
Hi,
On a fresh FC12 system, I am able to create and run KVM-based vms with tap networking using the qemu-kvm command line but not using virsh.
I have user and group set to "root" in /etc/libvirt/qemu.conf. "user mode networking" works with virsh, but not tap! selinux is disabled.
I have this xml:
<domain type='kvm'>
<name>centos</name>
<uuid>22d9d573-d82c-c18d-36c0-d3ffef057468</uuid>
<memory>131072</memory>
<vcpu>1</vcpu>
<os>
<type arch='x86_64'>hvm</type>
</os>
<features>
<acpi/>
<pae/>
</features>
<clock offset='utc'/>
<devices>
<emulator>/usr/bin/qemu-kvm</emulator>
<disk type='file' device='disk'>
<source file='/var/lib/images/centos.5-4.x86-64/centos-small.img'/>
<target dev='hda' bus='ide'/>
</disk>
<interface type='user'>
<mac address='52:54:00:7e:5b:58'/>
</interface>
<interface type='ethernet'>
<mac address='52:54:00:2e:33:c8'/>
<script path='/var/lib/images/centos.5-4.x86-64/qemu-ifup'/>
</interface>
<graphics type='vnc' port='5910' autoport='no' listen=''/>
</devices>
</domain>
This won't start even when I execute virsh as root:
[root@fc12 centos.5-4.x86-64]# virsh -c qemu+unix:///system create domr.xml
error: Failed to create domain from domr.xml
error: monitor socket did not show up.: No such file or directory
[root@fc12 centos.5-4.x86-64]# tail -3 /var/log/libvirt/qemu/centos.log
LC_ALL=C
PATH=/sbin:/usr/sbin:/bin:/usr/bin QEMU_AUDIO_DRV=none
/usr/bin/qemu-kvm -S -M pc-0.11 -m 128 -smp 1 -name centos -uuid
22d9d573-d82c-c18d-36c0-d3ffef057468 -monitor
unix:/var/lib/libvirt/qemu/centos.monitor,server,nowait -boot c -drive
file=/var/lib/images/centos.5-4.x86-64/centos-small.img,if=ide,index=0,boot=on
-net nic,macaddr=52:54:00:7e:5b:58,vlan=0,name=nic.0 -net
user,vlan=0,name=user.0 -net
nic,macaddr=52:54:00:2e:33:c8,vlan=1,name=nic.1 -net
tap,script=/var/lib/images/centos.5-4.x86-64/qemu-ifup,vlan=1,name=tap.0
-serial none -parallel none -usb -vnc :10 -vga cirrus
warning: could not configure /dev/net/tun: no virtual network emulation
qemu: Could not initialize device 'tap'
'***** But I can execute the same command line and it works!!********
[root@fc12
centos.5-4.x86-64]# LC_ALL=C PATH=/sbin:/usr/sbin:/bin:/usr/bin
QEMU_AUDIO_DRV=none /usr/bin/qemu-kvm -S -M pc-0.11 -m 128 -smp 1 -name
centos -uuid 22d9d573-d82c-c18d-36c0-d3ffef057468 -monitor
unix:/var/lib/libvirt/qemu/centos.monitor,server,nowait -boot c -drive
file=/var/lib/images/centos.5-4.x86-64/centos-small.img,if=ide,index=0,boot=on
-net nic,macaddr=52:54:00:7e:5b:58,vlan=0,name=nic.0 -net
user,vlan=0,name=user.0 -net
nic,macaddr=52:54:00:2e:33:c8,vlan=1,name=nic.1 -net
tap,script=/var/lib/images/centos.5-4.x86-64/qemu-ifup,vlan=1,name=tap.0
-serial none -parallel none -usb -vnc :10 -vga cirrus &
[2] 4543
[root@fc12 centos.5-4.x86-64]# ps -ef | grep qemu
root 4543 3449 0 19:02 pts/12
00:00:00 /usr/bin/qemu-kvm -S -M pc-0.11 -m 128 -smp 1 -name centos
-uuid 22d9d573-d82c-c18d-36c0-d3ffef057468 -monitor
unix:/var/lib/libvirt/qemu/centos.monitor,server,nowait -boot c -drive
file=/var/lib/images/centos.5-4.x86-64/centos-small.img,if=ide,index=0,boot=on
-net nic,macaddr=52:54:00:7e:5b:58,vlan=0,name=nic.0 -net
user,vlan=0,name=user.0 -net
nic,macaddr=52:54:00:2e:33:c8,vlan=1,name=nic.1 -net
tap,script=/var/lib/images/centos.5-4.x86-64/qemu-ifup,vlan=1,name=tap.0
-serial none -parallel none -usb -vnc :10 -vga cirrus
14 years, 4 months
ANNOUNCE: Rawhide virt repo for F12 users
by Justin Forbes
As was done for Fedora 11 users, the tradition continues, only the
locations have changed.
We've set up a repository for people running Fedora 12 who would like
to test the rawhide/F13 virt packages. To use it, do e.g.
$> cat > /etc/yum.repos.d/fedora-virt-preview.repo << EOF
[rawvirt]
name=Virtualization Rawhide for Fedora 12
baseurl=http://jforbes.fedorapeople.org/virt-preview/f12/$basearch/
enabled=1
gpgcheck=0
EOF
$> yum update
At the moment, it contains the F-13 versions of libvirt and virt-manager, but
as F-13 development continues, it will contain more. I'll send periodic
mails to the list detailing the latest updates.
A couple of improvements have been made this time around. Namely
packages are build with mock instead of koji so that new packages can be
used a BuildRequires for other new packages. Also new builds are
triggered by successful koji builds of tracked packages against
dist-rawhide, so the process is a bit more automated.
Also, this is still a work-in-progress. The TODO list includes:
- include debuginfo packages in the repo (need more quota)
- find a better location than jforbes.fedorapeople.org
Comments most welcome. Help with the TODO list is even more welcome :-)
Thanks,
Justin M. Forbes
14 years, 4 months
