From phil at pricom.com.au Sat Jan 2 15:45:36 2010 From: phil at pricom.com.au (Philip Rhoades) Date: Sun, 03 Jan 2010 02:45:36 +1100 Subject: [fedora-virt] Using NAT networking - can't ssh FROM the guest to the host Message-ID: <4B3F6A20.1040509@pricom.com.au> People, I am using F12 x86_64 as a host and have created a F12 i686 guest from the Live CD - I can successfully ssh from the host TO the guest (192.168.0.10 => 192.168.122.212) but not the other way around. It did actually work for a little while just after creating the guest but after trying stuff to get sound working on the guest and a couple of reboots, it no longer works (I can't think what has changed). http://www.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/5.4/html/Virtualization_Guide/chap-Virtualization-Network_Configuration.html says that the lines: "can be used in the guest" - but what file do they go in? The only appropriate file mentioned above those comments is regarding the host: /usr/share/libvirt/networks/default.xml - /usr/share/libvirt does not even exist on the guest . . I would like to get NAT networking going satisfactorily before having to look at bridged networking. Any suggestions appreciated. Thanks, Phil. -- Philip Rhoades GPO Box 3411 Sydney NSW 2001 Australia E-mail: phil at pricom.com.au From d.lesca at solinos.it Mon Jan 4 21:52:01 2010 From: d.lesca at solinos.it (Dario Lesca) Date: Mon, 04 Jan 2010 22:52:01 +0100 Subject: [fedora-virt] how to active XEN on Fedora 12 In-Reply-To: <20091230122156.GB23633@amd.home.annexia.org> References: <1261498240.2572.5.camel@localhost> <731380.66670.qm@web56105.mail.re3.yahoo.com> <1261571611.7526.434.camel@localhost> <715970.62563.qm@web56107.mail.re3.yahoo.com> <1261574617.7526.489.camel@localhost> <20091230122156.GB23633@amd.home.annexia.org> Message-ID: <1262612540.2349.6.camel@localhost> Il giorno mer, 30/12/2009 alle 12.21 +0000, Richard W.M. Jones ha scritto: > > Is KVM enabled? > > $ /sbin/lsmod | grep kvm > kvm_intel 48184 6 > kvm 163952 1 kvm_intel > > You should see a kvm_* module. Does your laptop support hardware > virtualization? Recent hardware has much better support than the > first generation of hardware. Is it enabled in the laptop BIOS? Thanks Richard, this is the problem: My laptop not have KVM support! It's my new laptop (HP Pavillon dv5) and I have discover now witch it non have KVM support in the bios. Now I'm looking for a buyer to sell and change it for use KVM. Thanks -- Dario Lesca From ondrejj at salstar.sk Tue Jan 5 07:29:52 2010 From: ondrejj at salstar.sk (=?utf-8?B?SsOhbiBPTkRSRUogKFNBTCk=?=) Date: Tue, 5 Jan 2010 08:29:52 +0100 Subject: [fedora-virt] how to active XEN on Fedora 12 In-Reply-To: <1262612540.2349.6.camel@localhost> References: <1261498240.2572.5.camel@localhost> <731380.66670.qm@web56105.mail.re3.yahoo.com> <1261571611.7526.434.camel@localhost> <715970.62563.qm@web56107.mail.re3.yahoo.com> <1261574617.7526.489.camel@localhost> <20091230122156.GB23633@amd.home.annexia.org> <1262612540.2349.6.camel@localhost> Message-ID: <20100105072952.GS27179@salstar.sk> On Mon, Jan 04, 2010 at 10:52:01PM +0100, Dario Lesca wrote: > Il giorno mer, 30/12/2009 alle 12.21 +0000, Richard W.M. Jones ha > scritto: > > > > Is KVM enabled? > > > > $ /sbin/lsmod | grep kvm > > kvm_intel 48184 6 > > kvm 163952 1 kvm_intel > > > > You should see a kvm_* module. Does your laptop support hardware > > virtualization? Recent hardware has much better support than the > > first generation of hardware. Is it enabled in the laptop BIOS? > > Thanks Richard, this is the problem: My laptop not have KVM support! > It's my new laptop (HP Pavillon dv5) and I have discover now witch it > non have KVM support in the bios. > > Now I'm looking for a buyer to sell and change it for use KVM. It's not neccessary to have switch in bios. Some laptops (like my one) has nothing about virtualization in BIOS, but KVM works well with full speed. You should check for virtualization flags for your CPU. More info here: http://fedoraproject.org/wiki/Virtualization_Quick_Start# Additional_requirements_for_fully_virtualized_guests SAL PS: Why I can't simply reply (or group reply) to this mail? Mailinglist is not included in To or Cc when replying. From adam.huffman at gmail.com Wed Jan 6 10:23:16 2010 From: adam.huffman at gmail.com (Adam Huffman) Date: Wed, 6 Jan 2010 10:23:16 +0000 Subject: [fedora-virt] libvirtd crashes host when autostarting In-Reply-To: <608c44bf0912150704u50ba97cby5ec09b40eea69750@mail.gmail.com> References: <200910091439.n99EdbJr009341@raspberry.lat.com> <1260756272.2100.91.camel@seitan.home.bewley.net> <608c44bf0912150704u50ba97cby5ec09b40eea69750@mail.gmail.com> Message-ID: <608c44bf1001060223l4286cddfrb28b62945be004a8@mail.gmail.com> On Tue, Dec 15, 2009 at 3:04 PM, Adam Huffman wrote: > On Mon, Dec 14, 2009 at 2:04 AM, Dale Bewley wrote: >> On Fri, 2009-10-09 at 10:39 -0400, Rich Mahn wrote: >>> > On Fri, 2009-10-09 at 09:45 -0400, Rich Mahn wrote: >>> > > Summary: >>> > > ? ?My host crashes when I use the autostart function in >>> > > libvirtd. >>> > > >>> > > This command sequence works fine: >>> > > >>> > > service libvirtd stop >>> > > virsh autostart mydomain --disable >>> > > service lib virtd start >>> > > virsh start mydomain >>> > > >>> > > This command sequence will crash the host: >>> > > >>> > > service libvirtd stop >>> > > virsh autostart mydomain >>> > > service libvirtd start >>> > > >>> > > >>> > > I can't find any error messages related to this. ?The host system >>> > > freezes, the keyboard starts blinking the caps-lock and scroll-lock, >>> > > and as best I can tell, the kernel has stopped running. >>> >>> > Ouch, that's really bad. This is a 2.6.30 kernel, right? Is it still >>> > reproducible with an older 2.6.29 kernel or a 2.6.31 kernel from >>> > rawhide? >>> >>> okay, it works correctly on 2.6.29. ?I'm trying to figure out how to >>> install 2.6.31 from rawhide without having dozens/hundreds of other >>> packages modified as well. ?Is there some option to 'yum' that will do >>> what I need? >> >> I am seeing a kernel oops and panic on a host running >> 2.6.31.6-166.fc12.x86_64 (and also at least 2.6.31.6-145) when I >> autostart a f12-x86_64 qemu-kvm guest. >> >> If I flag a guest as autoboot and reboot the host then the host starts, >> the guest starts, and some seconds later (presumably when the guest is >> fully up or just before) the host OOPs and hangs. The full error log is >> attached, it begins as: >> >> BUG: unable to handle kernel paging request at 0000000000200200 >> IP: [] destroy_conntrack+0x82/0x11f >> PGD 209d9d067 PUD 214dfa067 PMD 0 >> Oops: 0002 [#1] SMP >> last sysfs >> file: /sys/devices/pci0000:00/0000:00:09.0/0000:01:00.0/0000:02:02.0/0000:05:00.0/0000:06:00.0/irq >> CPU 0 >> Modules linked in: tun bridge stp llc xt_physdev ipt_LOG xt_limit >> xt_comment xt_multiport ip6t_REJECT nf_conntrack_ipv6 ip6table_filter >> ip6_tables ipv6 dm_multipath kvm_amd kvm bnx2 amd64_edac_mod shpchp >> edac_core i2c_piix4 serio_raw dcdbas raid1 raid10 mptsas mptscsih >> mptbase sata_svw scsi_transport_sas radeon ttm drm_kms_helper drm >> i2c_algo_bit i2c_core [last unloaded: freq_table] >> Pid: 1962, comm: qemu-kvm Not tainted 2.6.31.6-166.fc12.x86_64 #1 >> PowerEdge 2970 >> RIP: 0010:[] ?[] destroy_conntrack >> +0x82/0x11f >> >> I'm running on a quad core AMD with: >> >> qemu-kvm-0.11.0-12.fc12.x86_64 >> kernel-2.6.31.6-166.fc12.x86_64 >> libvirt-0.7.1-15.fc12.x86_64 >> >> What can I do to help further diagnose this problem? >> >> _______________________________________________ >> Fedora-virt mailing list >> Fedora-virt at redhat.com >> https://www.redhat.com/mailman/listinfo/fedora-virt >> > > For what it's worth I've been seeing very similar crashes. ?I reported it as: > > https://bugzilla.redhat.com/show_bug.cgi?id=545851 > > and on the KVM list. ?They thought it was a fault in the networking > stack, so people are now looking into it there. > > On my hardware, if I disable VT-d in the BIOS, the crashes don't happen. > > Adam > As I've noted in the bug report, if I disable IPv6, the system is stable. Adam From ondrejj at salstar.sk Wed Jan 6 10:37:40 2010 From: ondrejj at salstar.sk (=?utf-8?B?SsOhbiBPTkRSRUogKFNBTCk=?=) Date: Wed, 6 Jan 2010 11:37:40 +0100 Subject: [fedora-virt] libvirtd crashes host when autostarting In-Reply-To: <608c44bf1001060223l4286cddfrb28b62945be004a8@mail.gmail.com> References: <200910091439.n99EdbJr009341@raspberry.lat.com> <1260756272.2100.91.camel@seitan.home.bewley.net> <608c44bf0912150704u50ba97cby5ec09b40eea69750@mail.gmail.com> <608c44bf1001060223l4286cddfrb28b62945be004a8@mail.gmail.com> Message-ID: <20100106103740.GD27179@salstar.sk> On Wed, Jan 06, 2010 at 10:23:16AM +0000, Adam Huffman wrote: > On Tue, Dec 15, 2009 at 3:04 PM, Adam Huffman wrote: > > On Mon, Dec 14, 2009 at 2:04 AM, Dale Bewley wrote: > >> On Fri, 2009-10-09 at 10:39 -0400, Rich Mahn wrote: > >>> > On Fri, 2009-10-09 at 09:45 -0400, Rich Mahn wrote: > >>> > > Summary: > >>> > > ? ?My host crashes when I use the autostart function in > >>> > > libvirtd. > >>> > > > >>> > > This command sequence works fine: > >>> > > > >>> > > service libvirtd stop > >>> > > virsh autostart mydomain --disable > >>> > > service lib virtd start > >>> > > virsh start mydomain > >>> > > > >>> > > This command sequence will crash the host: > >>> > > > >>> > > service libvirtd stop > >>> > > virsh autostart mydomain > >>> > > service libvirtd start > >>> > > > >>> > > > >>> > > I can't find any error messages related to this. ?The host system > >>> > > freezes, the keyboard starts blinking the caps-lock and scroll-lock, > >>> > > and as best I can tell, the kernel has stopped running. > >>> > >>> > Ouch, that's really bad. This is a 2.6.30 kernel, right? Is it still > >>> > reproducible with an older 2.6.29 kernel or a 2.6.31 kernel from > >>> > rawhide? > >>> > >>> okay, it works correctly on 2.6.29. ?I'm trying to figure out how to > >>> install 2.6.31 from rawhide without having dozens/hundreds of other > >>> packages modified as well. ?Is there some option to 'yum' that will do > >>> what I need? > >> > >> I am seeing a kernel oops and panic on a host running > >> 2.6.31.6-166.fc12.x86_64 (and also at least 2.6.31.6-145) when I > >> autostart a f12-x86_64 qemu-kvm guest. > >> > >> If I flag a guest as autoboot and reboot the host then the host starts, > >> the guest starts, and some seconds later (presumably when the guest is > >> fully up or just before) the host OOPs and hangs. The full error log is > >> attached, it begins as: > >> > >> BUG: unable to handle kernel paging request at 0000000000200200 > >> IP: [] destroy_conntrack+0x82/0x11f > >> PGD 209d9d067 PUD 214dfa067 PMD 0 > >> Oops: 0002 [#1] SMP > >> last sysfs > >> file: /sys/devices/pci0000:00/0000:00:09.0/0000:01:00.0/0000:02:02.0/0000:05:00.0/0000:06:00.0/irq > >> CPU 0 > >> Modules linked in: tun bridge stp llc xt_physdev ipt_LOG xt_limit > >> xt_comment xt_multiport ip6t_REJECT nf_conntrack_ipv6 ip6table_filter > >> ip6_tables ipv6 dm_multipath kvm_amd kvm bnx2 amd64_edac_mod shpchp > >> edac_core i2c_piix4 serio_raw dcdbas raid1 raid10 mptsas mptscsih > >> mptbase sata_svw scsi_transport_sas radeon ttm drm_kms_helper drm > >> i2c_algo_bit i2c_core [last unloaded: freq_table] > >> Pid: 1962, comm: qemu-kvm Not tainted 2.6.31.6-166.fc12.x86_64 #1 > >> PowerEdge 2970 > >> RIP: 0010:[] ?[] destroy_conntrack > >> +0x82/0x11f > >> > >> I'm running on a quad core AMD with: > >> > >> qemu-kvm-0.11.0-12.fc12.x86_64 > >> kernel-2.6.31.6-166.fc12.x86_64 > >> libvirt-0.7.1-15.fc12.x86_64 > >> > >> What can I do to help further diagnose this problem? > >> > >> _______________________________________________ > >> Fedora-virt mailing list > >> Fedora-virt at redhat.com > >> https://www.redhat.com/mailman/listinfo/fedora-virt > >> > > > > For what it's worth I've been seeing very similar crashes. ?I reported it as: > > > > https://bugzilla.redhat.com/show_bug.cgi?id=545851 > > > > and on the KVM list. ?They thought it was a fault in the networking > > stack, so people are now looking into it there. > > > > On my hardware, if I disable VT-d in the BIOS, the crashes don't happen. > > > > Adam > > > > As I've noted in the bug report, if I disable IPv6, the system is stable. For me it's enough to disable iptables for bridge by adding: net.bridge.bridge-nf-call-ip6tables = 0 to /etc/sysctl.conf SAL From crobinso at redhat.com Wed Jan 6 15:03:00 2010 From: crobinso at redhat.com (Cole Robinson) Date: Wed, 06 Jan 2010 10:03:00 -0500 Subject: [fedora-virt] Fedora 12 host and windowsXP guest - No Sound from guest In-Reply-To: References: <4B3B0513.1040103@redhat.com> Message-ID: <4B44A624.50802@redhat.com> On 12/30/2009 05:58 AM, Daniel Sanabria wrote: > thanks Dor, > > looking at the logs you seem to have a point: > > LC_ALL=C PATH=/sbin:/usr/sbin:/bin:/usr/bin QEMU_AUDIO_DRV=none > /usr/bin/qemu-kvm -S -M pc-0.11 -m 1024 -smp 1 -name winxp -uuid 8 > 8b53573-a3c1-3e12-8703-ea3fc8580493 -monitor > unix:/var/lib/libvirt/qemu/winxp.monitor,server,nowait -localtime -boot c > -drive file > =/var/lib/libvirt/images/winxp.img,if=ide,index=0,boot=on,format=raw -drive > file=/home/daniel/ISO/WINXP_SP2_PRO.iso,if=ide,media=c > drom,index=2 -net nic,macaddr=52:54:00:62:66:ed,vlan=0,name=nic.0 -net > tap,fd=18,vlan=0,name=tap.0 -serial pty -parallel none -usb > -usbdevice tablet -vnc 127.0.0.1:1 -k en-gb -vga cirrus -soundhw es1370 > > I noticed the QEMU_AUDIO_DRV=none variable here which is how virt-manager is > trying to start the vm. Shouldn't that be QEMU_AUDIO_DRV=pa in the case of > Fedora 12? How can I change that value, so virt-manager starts the vm > correctly? > There is some more info here: https://bugzilla.redhat.com/show_bug.cgi?id=508317 Basically, trying to use the 'pa' backend can upset selinux, and doesn't easily work if the qemu binary isn't running under the user acct (which it likely isn't if you are using virt-manager). So, if you are using VNC, we set QEMU_AUDIO_DRV=none, which will attempt to route audio over VNC. However the gtk-vnc version in F12 doesn't support the audio extension yet, so you won't hear anything :( - Cole From sanabria.d at gmail.com Wed Jan 6 15:40:13 2010 From: sanabria.d at gmail.com (Daniel Sanabria) Date: Wed, 6 Jan 2010 15:40:13 +0000 Subject: [fedora-virt] Fedora 12 host and windowsXP guest - No Sound from guest In-Reply-To: <4B44A624.50802@redhat.com> References: <4B3B0513.1040103@redhat.com> <4B44A624.50802@redhat.com> Message-ID: Thanks Cole, with your comments things are starting to make a bit more of sense to me. So I now see 2 options: 1. start qemu with the user account which will potentially mean to stop using virt-manager 2. Install/compile the gtk-vnc version that support the audio extension (only if it's already available) Could you provide some guidance on how to approach any of these options? i.e. How can I start qemu and the guest manually without using virt-manager? or is there gtk-vnc version available that supports the audio extension? Cheers, Daniel 2010/1/6 Cole Robinson > On 12/30/2009 05:58 AM, Daniel Sanabria wrote: > > thanks Dor, > > > > looking at the logs you seem to have a point: > > > > LC_ALL=C PATH=/sbin:/usr/sbin:/bin:/usr/bin QEMU_AUDIO_DRV=none > > /usr/bin/qemu-kvm -S -M pc-0.11 -m 1024 -smp 1 -name winxp -uuid 8 > > 8b53573-a3c1-3e12-8703-ea3fc8580493 -monitor > > unix:/var/lib/libvirt/qemu/winxp.monitor,server,nowait -localtime -boot c > > -drive file > > =/var/lib/libvirt/images/winxp.img,if=ide,index=0,boot=on,format=raw > -drive > > file=/home/daniel/ISO/WINXP_SP2_PRO.iso,if=ide,media=c > > drom,index=2 -net nic,macaddr=52:54:00:62:66:ed,vlan=0,name=nic.0 -net > > tap,fd=18,vlan=0,name=tap.0 -serial pty -parallel none -usb > > -usbdevice tablet -vnc 127.0.0.1:1 -k en-gb -vga cirrus -soundhw es1370 > > > > I noticed the QEMU_AUDIO_DRV=none variable here which is how virt-manager > is > > trying to start the vm. Shouldn't that be QEMU_AUDIO_DRV=pa in the case > of > > Fedora 12? How can I change that value, so virt-manager starts the vm > > correctly? > > > > There is some more info here: > > https://bugzilla.redhat.com/show_bug.cgi?id=508317 > > Basically, trying to use the 'pa' backend can upset selinux, and doesn't > easily work if the qemu binary isn't running under the user acct (which > it likely isn't if you are using virt-manager). So, if you are using > VNC, we set QEMU_AUDIO_DRV=none, which will attempt to route audio over > VNC. However the gtk-vnc version in F12 doesn't support the audio > extension yet, so you won't hear anything :( > > - Cole > -------------- next part -------------- An HTML attachment was scrubbed... URL: From crobinso at redhat.com Wed Jan 6 21:39:07 2010 From: crobinso at redhat.com (Cole Robinson) Date: Wed, 06 Jan 2010 16:39:07 -0500 Subject: [fedora-virt] Fedora 12 host and windowsXP guest - No Sound from guest In-Reply-To: References: <4B3B0513.1040103@redhat.com> <4B44A624.50802@redhat.com> Message-ID: <4B4502FB.9060403@redhat.com> On 01/06/2010 10:40 AM, Daniel Sanabria wrote: > Thanks Cole, > > with your comments things are starting to make a bit more of sense to me. > > So I now see 2 options: > > 1. start qemu with the user account which will potentially mean to stop > using virt-manager This has networking caveats. If you run the qemu binary directly as a regular user, the easiest setup is -net user, which doesn't actually have full networking capabilities. You'll want to study up before you take this route. > 2. Install/compile the gtk-vnc version that support the audio extension > (only if it's already available) > Unfortunately that code isn't upstream yet. I know Dan Berrange has something working to a degree, but it hasn't been posted yet. > Could you provide some guidance on how to approach any of these options? > i.e. How can I start qemu and the guest manually without using virt-manager? > or is there gtk-vnc version available that supports the audio extension? > You can also try to use SDL for graphics rather than VNC. This has some caveats: no remote access via libvirt, the SDL console will pop up outside of virt-manager, and when the SDL window closes the guest will be forcibly powered off. I haven't tried this, but AFAIK sound should work. You can try changing the sdl audio backend in /etc/sysconfig/libvirtd from 'pa' (pulseaudio) to something else if you have issues. Hope that helps, Cole From eb30750 at gmail.com Thu Jan 7 02:13:33 2010 From: eb30750 at gmail.com (Paul Lambert) Date: Wed, 6 Jan 2010 21:13:33 -0500 Subject: [fedora-virt] FE-12 i686 config files shows x86_64 Message-ID: Is this correct? Yum results on guest show kernel.i686 version 2.6.31.9-174.fc12 yet KVM config file shows arch is x86_64 Fedora-11-Home 714133c3-eda0-eeb8-632c-bd37c7e66ddd 786432 786432 2 hvm Please advise if this should be reported as a bug. Paul -------------- next part -------------- An HTML attachment was scrubbed... URL: From tom at compton.nu Thu Jan 7 10:52:31 2010 From: tom at compton.nu (Tom Hughes) Date: Thu, 07 Jan 2010 10:52:31 +0000 Subject: [fedora-virt] virt-preview missing bios package Message-ID: <4B45BCEF.3000308@compton.nu> The new QEMU packages added to the F12 virt-preview repository in the last few days apparently require a new BIOS but that doesn't seem to be present in the repository. As it stands any attempt to start QEMU after updating just gives me a black screen. Tom -- Tom Hughes (tom at compton.nu) http://www.compton.nu/ From crobinso at redhat.com Thu Jan 7 14:23:31 2010 From: crobinso at redhat.com (Cole Robinson) Date: Thu, 07 Jan 2010 09:23:31 -0500 Subject: [fedora-virt] FE-12 i686 config files shows x86_64 In-Reply-To: References: Message-ID: <4B45EE63.5080501@redhat.com> On 01/06/2010 09:13 PM, Paul Lambert wrote: > Is this correct? > > Yum results on guest show kernel.i686 version 2.6.31.9-174.fc12 yet KVM > config file shows arch is x86_64 > > > Fedora-11-Home > 714133c3-eda0-eeb8-632c-bd37c7e66ddd > 786432 > 786432 > 2 > > hvm > > > > Please advise if this should be reported as a bug. > The XML is likely correct. The config file represents a 64 bit virtual CPU, but it looks like you installed the 32 bit F12 version, which is perfectly valid. Same as installing 32 bit OS on a real 64 bit machine. - Cole From fredericg_99 at yahoo.fr Thu Jan 7 15:25:21 2010 From: fredericg_99 at yahoo.fr (=?utf-8?Q?Fr=C3=A9d=C3=A9ric_Grelot?=) Date: Thu, 7 Jan 2010 16:25:21 +0100 (CET) Subject: [fedora-virt] virt-preview missing bios package In-Reply-To: <4B45BCEF.3000308@compton.nu> Message-ID: <27387611.51.1262877920905.JavaMail.root@server.grelot.net> I can confirm this (with few linux-32b images created before this update). I can't even ssh to my images, so they don't seem to have really started (while virt-manager shows they have). Frederic. ----- "Tom Hughes" a ?crit : > The new QEMU packages added to the F12 virt-preview repository in the > > last few days apparently require a new BIOS but that doesn't seem to > be > present in the repository. > > As it stands any attempt to start QEMU after updating just gives me a > > black screen. > > Tom > > -- > Tom Hughes (tom at compton.nu) > http://www.compton.nu/ > > _______________________________________________ > Fedora-virt mailing list > Fedora-virt at redhat.com > https://www.redhat.com/mailman/listinfo/fedora-virt From crobinso at redhat.com Thu Jan 7 15:41:51 2010 From: crobinso at redhat.com (Cole Robinson) Date: Thu, 07 Jan 2010 10:41:51 -0500 Subject: [fedora-virt] virt-preview missing bios package In-Reply-To: <27387611.51.1262877920905.JavaMail.root@server.grelot.net> References: <27387611.51.1262877920905.JavaMail.root@server.grelot.net> Message-ID: <4B4600BF.4080109@redhat.com> On 01/07/2010 10:25 AM, Fr?d?ric Grelot wrote: > I can confirm this (with few linux-32b images created before this update). > I can't even ssh to my images, so they don't seem to have really started (while virt-manager shows they have). > > Frederic. > Seems like seabios is missing, which is the new default bios for qemu (replacing bochs). We probably need to package it up as was done with the bochs-bios package. Maybe we can just patch it in qemu CVS until the new package is available? - Cole > > ----- "Tom Hughes" a ??crit : > >> The new QEMU packages added to the F12 virt-preview repository in the >> >> last few days apparently require a new BIOS but that doesn't seem to >> be >> present in the repository. >> >> As it stands any attempt to start QEMU after updating just gives me a >> >> black screen. >> >> Tom >> >> -- >> Tom Hughes (tom at compton.nu) >> http://www.compton.nu/ >> From adam.huffman at gmail.com Thu Jan 7 16:33:41 2010 From: adam.huffman at gmail.com (Adam Huffman) Date: Thu, 7 Jan 2010 16:33:41 +0000 Subject: [fedora-virt] Networking failure on F12 Message-ID: <608c44bf1001070833w1de5aabahd8954551d94519c8@mail.gmail.com> I've setup a Windows 7 guest on a new F12 box. Initially, it was fine. However, a couple of times now the guest's networking has been lost and it has allocate itself a 169.254. address. When I tried installing a Centos 5.4 guest for comparison, that wasn't able to pick up an IP via DHCP either. Here are the current iptables rules: *filter :INPUT ACCEPT [0:0] :FORWARD ACCEPT [0:0] :OUTPUT ACCEPT [0:0] -A INPUT -m state --state ESTABLISHED,RELATED -j ACCEPT -A INPUT -p icmp -j ACCEPT -A INPUT -i lo -j ACCEPT -A INPUT -m state --state NEW -m tcp -p tcp --dport 22 -j ACCEPT -A INPUT -s 192.168.122.0/24 -m tcp -p tcp --dport 445 -j ACCEPT -A INPUT -s 192.168.122.0/24 -i vnet0 -m udp -p udp --dport 137:139 -j ACCEPT -A INPUT -s 192.168.122.0/24 -i vnet0 -m tcp -p tcp --dport 137:139 -j ACCEPT -I FORWARD -m physdev --physdev-is-bridged -j ACCEPT -A INPUT -j REJECT --reject-with icmp-host-prohibited -A FORWARD -j REJECT --reject-with icmp-host-prohibited COMMIT dnsmasq is running. Adam From jmforbes at linuxtx.org Thu Jan 7 19:29:53 2010 From: jmforbes at linuxtx.org (Justin M. Forbes) Date: Thu, 7 Jan 2010 13:29:53 -0600 Subject: [fedora-virt] virt-preview missing bios package In-Reply-To: <4B45BCEF.3000308@compton.nu> References: <4B45BCEF.3000308@compton.nu> Message-ID: <20100107192953.GA13581@linuxtx.org> On Thu, Jan 07, 2010 at 10:52:31AM +0000, Tom Hughes wrote: > The new QEMU packages added to the F12 virt-preview repository in the last > few days apparently require a new BIOS but that doesn't seem to be present > in the repository. > They are indeed missing seabios. I am working on getting it packaged now. In the meantime you can always: git clone git://git.linuxtogo.org/home/kevin/seabios.git cd seabios make sudo cp out/bios.bin /usr/share/qemu/bios.bin And things will work again. Justin