On Tue, Oct 13, 2009 at 3:52 PM, Don Dutile <ddutile(a)redhat.com> wrote:
> Gianluca Cecchi wrote:
>> I don't remember if it is possible to connect to qemu monitor with
>> virt-manager/libvirtd managed guests.
>> If so, how can I accomplish this?
>> Thanks in advance,
> do you mean?:
> virsh console <guest-name>
No, not this.
Putting correct lines in guest kernel command line I'm able to see what you
wrote, directly from virt-manager through
View --> Consoles --> Serial 0
I mean qemu monitor itself. The one that you activate inside qemu guest when
you run qemu or qemu-kvm and then press Ctrl+ Alt + 2
and you get something like
QEMU 0.11.0 monitor - type 'help' for more information
I understand that it would be risky to make things from the qemu monitor
itself bypassing libvirt, and so I asked, just to know
According to https://fedoraproject.org/wiki/Features/VirtgPXE the switch
to gPXE should make PXE 'localboot' (which etherboot didn't support)
start working. I've tried setting up a network booting VM on a host
running F11 + virt-preview and while it uses gPXE, loading a pxelinux
configuration that tries to do localboot doesn't work - gPXE loops and
does DHCP again. The same config does work on real hardware, so am I
missing a detail somewhere, do I need a full F12 install, or is this not
supposed to be working yet?
 screenshot here:
On Sat, Oct 10, 2009 at 04:56:35PM +0300, Vitaliy Yermolenko wrote:
> I'm a big fun of Red Hat/Fedora distributives, and, have tried your
> febootstrap Fedora bootstrapping system, which seems very interesting for me
> in order to make own lightweighted Fedora-based Linux distributive.
> I'm currently using Fedora 11 with fresh 184.108.40.206 kernel on AMD Phenom II X4
> 945 CPU. But, unfortunately, I have got many segmentation faults during
> running ./minimal-filesystem.sh - see below.
You should ask questions on one of the proper mailing lists. I've
CC'd this to fedora-virt.
Segfaults are almost certainly because you're trying to install a
guest >= F12 on an F11 host. There's some ABI incompatibility in
glibc which causes fakeroot to segfault in this case.
Install an F11 guest if you have an F11 host, or upgrade to F12 host.
Richard Jones, Emerging Technologies, Red Hat http://et.redhat.com/~rjones
libguestfs lets you edit virtual machines. Supports shell scripting,
bindings from many languages. http://et.redhat.com/~rjones/libguestfs/
See what it can do: http://et.redhat.com/~rjones/libguestfs/recipes.html
I've started playing with libvirt and I have question?
What is proper way to make guest accessible from net.
I have mode=nat /var/lib/libvirt/network/default.xml.
libvirtd makes this rules in FORWARD chain
-A FORWARD -d 192.168.231.0/24 -o virbr0 -m state --state
RELATED,ESTABLISHED -j ACCEPT
-A FORWARD -s 192.168.231.0/24 -i virbr0 -j ACCEPT
-A FORWARD -i virbr0 -o virbr0 -j ACCEPT
-A FORWARD -o virbr0 -j REJECT --reject-with icmp-port-unreachable
-A FORWARD -i virbr0 -j REJECT --reject-with icmp-port-unreachable
-A FORWARD -j REJECT --reject-with icmp-host-prohibited
If I add
iptables -I FORWARD -i eth0 -o virbr0 -j ACCEPT
guests are accessible
My question is:
Is is possible write this somewhere to configuration?
I've tried to put it in /etc/sysconfig/iptables but it libvirtd put his
rules before mine.
I've found two directories
I suppose I can write my rules here but I haven't find any docs about
format. Can somebody help me with it?
I don't know if something is busted in my rawhide setup, or if this is just
a real problem with the new scheme of running as user qemu, but user qemu (on
my system at least), has no access to physical usb devices. I had to change
the qemu.conf file to tell it to run as root before it could attach a usb
device to my windows XP virtual machine.
I want to set up wo virtual WinXP machines to act as licence managers
for a couple of CAD/CAM programs.
With the first one, everything went well, but when I got the second one
to work, the virtual machines got confused, as if they didn't know which
was their dongle.
I think it is because in their definition files there is something like:
<hostdev mode='subsystem' type='usb'>
The vendor and product ids are the same in both cases.
I saw in the docs that I can't change it to:
<hostdev mode='subsystem' type='sub'>
<address bus='0x06' slot='0x02' function='0x0'/>
'bus' and 'slot' I can get with 'lsusb', but what does 'function' mean?
Quick question about virt package dependencies. The Rawhide Acceptance
Install Test (which does a virt install)  first installs the required
packages by doing:
# yum -y install qemu-kvm python-virtinst pax
It seems that installing python-virtinst used to also pull libvirt into
the transaction. However, this is no longer the case . Should the
deps chain when installing python-virtinst also install libvirt? Or is
it expected that if you wish to run your own virt daemon, you should
 rats_install test output - http://pastie.org/647021
I run something like this, for un-attended automated guest installs.
echo "Creating domain $domname"
echo "Image is here $vmimage"
echo "Location of the OS sources $location"
virt-install --connect=qemu:///system \
--name $domname \
--ram 1024 \
-- once the install is finished and guest reboots, a console does
/not/ show up. Because, as the
"console=tty0 console=ttyS0,9600" args from the script are not picked
by the anaconda of guest while booting.
-- A console shows up only when I manually edit the guest machine's
kernel args and append
"console=tty0 console=ttyS0,9600" , /then/ boot the guest - now
console shows up happily.
My question is : shouldn't the anaconda of the guest machine pick up
"console=tty0 console=ttyS0,9600" in the --extra-args mentioned in the
Is this the expected behaviour? or shall I file a bug.
is there a way to provide virt-viewer access to a single VM? After some
googling I can only find ways to provide access to a whole virt-manager
instance but I'd like to create VMs for users an only give them access to
their own virtual machines? Is this possible?