All of lore.kernel.org
 help / color / mirror / Atom feed
* vm pxe fail
@ 2012-08-16 12:25 Andrew Holway
  2012-08-16 13:54 ` Stefan Hajnoczi
  2012-08-17  2:34 ` [libvirt-users] " Alex Jia
  0 siblings, 2 replies; 14+ messages in thread
From: Andrew Holway @ 2012-08-16 12:25 UTC (permalink / raw)
  To: kvm

Hallo

I have a kvm vm that I am attempting to boot from pxe. The dhcp works perfectly and I can see the VM in the pxe server arp. but the tftp just times out. I don't see any tftp traffic on either the physical host or on the pie server. I am using a bridged interface. I have tried using several virtual nic drivers, several different mac addresses and several different ips.  on the physical host I can get the pxelinux.0 file from the pxe server via tftp and can clearly see that traffic with tcpdump.

Ive tried using various virtual interfaces.

I can pxe boot my physical hosts with no problems.

I can tftp fine from the physical host and see the traffic with ethdump

Here is the terminal output from the VM: https://dl.dropbox.com/u/98200887/Screen%20Shot%202012-08-15%20at%206.41.12%20PM.png

Thanks,

Andrew

[root@node002 ~]# yum list | grep qemu
gpxe-roms-qemu.noarch                   0.9.7-6.9.el6               @base       
qemu-img.x86_64                         2:0.12.1.2-2.295.el6_3.1    @updates    
qemu-kvm.x86_64                         2:0.12.1.2-2.295.el6_3.1    @updates    
qemu-guest-agent.x86_64                 2:0.12.1.2-2.295.el6_3.1    updates     
qemu-kvm-tools.x86_64                   2:0.12.1.2-2.295.el6_3.1    updates 

[root@node002 ~]# ethtool eth0
Settings for eth0:
	Supported ports: [ TP ]
	Supported link modes:   10000baseT/Full 
	Supports auto-negotiation: No
	Advertised link modes:  10000baseT/Full 
	Advertised pause frame use: No
	Advertised auto-negotiation: No
	Speed: Unknown!
	Duplex: Unknown! (255)
	Port: Twisted Pair
	PHYAD: 0
	Transceiver: internal
	Auto-negotiation: off
	MDI-X: Unknown
	Supports Wake-on: g
	Wake-on: g
	Current message level: 0x00000014 (20)
	Link detected: no

[root@node002 ~]# brctl show
bridge name	bridge id		STP enabled	interfaces
br0		8000.009c02241ae0	no		eth1
							vnet0
virbr0		8000.525400a6d5aa	yes		virbr0-nic

[root@node002 ~]# ethtool vnet0
Settings for vnet0:
	Supported ports: [ ]
	Supported link modes:   
	Supports auto-negotiation: No
	Advertised link modes:  Not reported
	Advertised pause frame use: No
	Advertised auto-negotiation: No
	Speed: 10Mb/s
	Duplex: Full
	Port: Twisted Pair
	PHYAD: 0
	Transceiver: internal
	Auto-negotiation: off
	MDI-X: Unknown
	Current message level: 0xffffffa1 (-95)
	Link detected: yes

<domain type='kvm'>
  <name>vm004</name>
  <uuid>4f03b09b-e834-bbf3-a6c2-1689f3156ef2</uuid>
  <memory unit='KiB'>2097152</memory>
  <currentMemory unit='KiB'>2097152</currentMemory>
  <vcpu placement='static'>2</vcpu>
  <os>
    <type arch='x86_64' machine='rhel6.3.0'>hvm</type>
    <boot dev='hd'/>
  </os>
  <features>
    <acpi/>
    <apic/>
    <pae/>
  </features>
  <clock offset='utc'/>
  <on_poweroff>destroy</on_poweroff>
  <on_reboot>restart</on_reboot>
  <on_crash>restart</on_crash>
  <devices>
    <emulator>/usr/libexec/qemu-kvm</emulator>
    <disk type='file' device='disk'>
      <driver name='qemu' type='raw' cache='none'/>
      <source file='/cm/shared/vm/vm004.img'/>
      <target dev='hda' bus='ide'/>
      <address type='drive' controller='0' bus='0' target='0' unit='0'/>
    </disk>
    <disk type='block' device='cdrom'>
      <driver name='qemu' type='raw'/>
      <target dev='hdc' bus='ide'/>
      <readonly/>
      <address type='drive' controller='0' bus='1' target='0' unit='0'/>
    </disk>
    <controller type='usb' index='0'>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x2'/>
    </controller>
    <controller type='ide' index='0'>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x1'/>
    </controller>
    <interface type='bridge'>
      <mac address='00:00:00:00:00:0d'/>
      <source bridge='br0'/>
      <model type='rtl8139'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/>
    </interface>
    <serial type='pty'>
      <target port='0'/>
    </serial>
    <console type='pty'>
      <target type='serial' port='0'/>
    </console>
    <input type='mouse' bus='ps2'/>
    <graphics type='vnc' port='-1' autoport='yes'/>
    <video>
      <model type='cirrus' vram='9216' heads='1'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0'/>
    </video>
    <memballoon model='virtio'>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x04' function='0x0'/>
    </memballoon>
  </devices>
</domain>



^ permalink raw reply	[flat|nested] 14+ messages in thread

* Re: vm pxe fail
  2012-08-16 12:25 vm pxe fail Andrew Holway
@ 2012-08-16 13:54 ` Stefan Hajnoczi
  2012-08-16 15:09   ` Andrew Holway
  2012-08-17  2:34 ` [libvirt-users] " Alex Jia
  1 sibling, 1 reply; 14+ messages in thread
From: Stefan Hajnoczi @ 2012-08-16 13:54 UTC (permalink / raw)
  To: Andrew Holway; +Cc: kvm

On Thu, Aug 16, 2012 at 1:25 PM, Andrew Holway <a.holway@syseleven.de> wrote:
> I have a kvm vm that I am attempting to boot from pxe. The dhcp works perfectly and I can see the VM in the pxe server arp. but the tftp just times out. I don't see any tftp traffic on either the physical host or on the pie server. I am using a bridged interface. I have tried using several virtual nic drivers, several different mac addresses and several different ips.  on the physical host I can get the pxelinux.0 file from the pxe server via tftp and can clearly see that traffic with tcpdump.
>
> Ive tried using various virtual interfaces.
>
> I can pxe boot my physical hosts with no problems.
>
> I can tftp fine from the physical host and see the traffic with ethdump

Have you run tcpdump on the tap interface?  (This is different from
running tcpdump on host eth0 because it is earlier in the network path
and happens before the software bridge.)

What do iptables -L -n and ebtables -L say?

Stefan

^ permalink raw reply	[flat|nested] 14+ messages in thread

* Re: vm pxe fail
  2012-08-16 13:54 ` Stefan Hajnoczi
@ 2012-08-16 15:09   ` Andrew Holway
  2012-08-16 15:35     ` Stefan Hajnoczi
  0 siblings, 1 reply; 14+ messages in thread
From: Andrew Holway @ 2012-08-16 15:09 UTC (permalink / raw)
  To: Stefan Hajnoczi; +Cc: kvm


On Aug 16, 2012, at 3:54 PM, Stefan Hajnoczi wrote:

> On Thu, Aug 16, 2012 at 1:25 PM, Andrew Holway <a.holway@syseleven.de> wrote:
>> I have a kvm vm that I am attempting to boot from pxe. The dhcp works perfectly and I can see the VM in the pxe server arp. but the tftp just times out. I don't see any tftp traffic on either the physical host or on the pie server. I am using a bridged interface. I have tried using several virtual nic drivers, several different mac addresses and several different ips.  on the physical host I can get the pxelinux.0 file from the pxe server via tftp and can clearly see that traffic with tcpdump.
>> 
>> Ive tried using various virtual interfaces.
>> 
>> I can pxe boot my physical hosts with no problems.
>> 
>> I can tftp fine from the physical host and see the traffic with ethdump
> 
> Have you run tcpdump on the tap interface?  (This is different from
> running tcpdump on host eth0 because it is earlier in the network path
> and happens before the software bridge.)

Yes. I can just see DHCP traffic.

> 
> What do iptables -L -n and ebtables -L say?
> 

[root@node002 ~]# iptables -L -n 
Chain INPUT (policy ACCEPT)
target     prot opt source               destination         
ACCEPT     udp  --  0.0.0.0/0            0.0.0.0/0           udp dpt:53 
ACCEPT     tcp  --  0.0.0.0/0            0.0.0.0/0           tcp dpt:53 
ACCEPT     udp  --  0.0.0.0/0            0.0.0.0/0           udp dpt:67 
ACCEPT     tcp  --  0.0.0.0/0            0.0.0.0/0           tcp dpt:67 

Chain FORWARD (policy ACCEPT)
target     prot opt source               destination         
ACCEPT     all  --  0.0.0.0/0            192.168.122.0/24    state RELATED,ESTABLISHED 
ACCEPT     all  --  192.168.122.0/24     0.0.0.0/0           
ACCEPT     all  --  0.0.0.0/0            0.0.0.0/0           
REJECT     all  --  0.0.0.0/0            0.0.0.0/0           reject-with icmp-port-unreachable 
REJECT     all  --  0.0.0.0/0            0.0.0.0/0           reject-with icmp-port-unreachable 

Chain OUTPUT (policy ACCEPT)
target     prot opt source               destination  


[root@node002 ~]# ebtables -L
Bridge table: filter

Bridge chain: INPUT, entries: 0, policy: ACCEPT

Bridge chain: FORWARD, entries: 0, policy: ACCEPT

Bridge chain: OUTPUT, entries: 0, policy: ACCEPT

[root@node002 ~]# tcpdump -i vnet0 udp
tcpdump: WARNING: vnet0: no IPv4 address assigned
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on vnet0, link-type EN10MB (Ethernet), capture size 65535 bytes
17:08:08.849344 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 00:00:00:00:00:0d (oui Ethernet), length 387
17:08:08.849413 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 00:00:00:00:00:0d (oui Ethernet), length 387
17:08:08.849661 IP master.cm.cluster.bootps > 255.255.255.255.bootpc: BOOTP/DHCP, Reply, length 360
17:08:09.812645 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 00:00:00:00:00:0d (oui Ethernet), length 387
17:08:09.812709 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 00:00:00:00:00:0d (oui Ethernet), length 387
17:08:09.812903 IP master.cm.cluster.bootps > 255.255.255.255.bootpc: BOOTP/DHCP, Reply, length 360
17:08:11.789993 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 00:00:00:00:00:0d (oui Ethernet), length 399
17:08:11.790107 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 00:00:00:00:00:0d (oui Ethernet), length 399
17:08:11.790294 IP master.cm.cluster.bootps > 255.255.255.255.bootpc: BOOTP/DHCP, Reply, length 360


And then…….silence!



> Stefan



^ permalink raw reply	[flat|nested] 14+ messages in thread

* Re: vm pxe fail
  2012-08-16 15:09   ` Andrew Holway
@ 2012-08-16 15:35     ` Stefan Hajnoczi
  0 siblings, 0 replies; 14+ messages in thread
From: Stefan Hajnoczi @ 2012-08-16 15:35 UTC (permalink / raw)
  To: Andrew Holway; +Cc: kvm

On Thu, Aug 16, 2012 at 4:09 PM, Andrew Holway <a.holway@syseleven.de> wrote:
>
> On Aug 16, 2012, at 3:54 PM, Stefan Hajnoczi wrote:
>
>> On Thu, Aug 16, 2012 at 1:25 PM, Andrew Holway <a.holway@syseleven.de> wrote:
>>> I have a kvm vm that I am attempting to boot from pxe. The dhcp works perfectly and I can see the VM in the pxe server arp. but the tftp just times out. I don't see any tftp traffic on either the physical host or on the pie server. I am using a bridged interface. I have tried using several virtual nic drivers, several different mac addresses and several different ips.  on the physical host I can get the pxelinux.0 file from the pxe server via tftp and can clearly see that traffic with tcpdump.
>>>
>>> Ive tried using various virtual interfaces.
>>>
>>> I can pxe boot my physical hosts with no problems.
>>>
>>> I can tftp fine from the physical host and see the traffic with ethdump
>>
>> Have you run tcpdump on the tap interface?  (This is different from
>> running tcpdump on host eth0 because it is earlier in the network path
>> and happens before the software bridge.)
>
> Yes. I can just see DHCP traffic.
>
>>
>> What do iptables -L -n and ebtables -L say?
>>
>
> [root@node002 ~]# iptables -L -n
> Chain INPUT (policy ACCEPT)
> target     prot opt source               destination
> ACCEPT     udp  --  0.0.0.0/0            0.0.0.0/0           udp dpt:53
> ACCEPT     tcp  --  0.0.0.0/0            0.0.0.0/0           tcp dpt:53
> ACCEPT     udp  --  0.0.0.0/0            0.0.0.0/0           udp dpt:67
> ACCEPT     tcp  --  0.0.0.0/0            0.0.0.0/0           tcp dpt:67
>
> Chain FORWARD (policy ACCEPT)
> target     prot opt source               destination
> ACCEPT     all  --  0.0.0.0/0            192.168.122.0/24    state RELATED,ESTABLISHED
> ACCEPT     all  --  192.168.122.0/24     0.0.0.0/0
> ACCEPT     all  --  0.0.0.0/0            0.0.0.0/0
> REJECT     all  --  0.0.0.0/0            0.0.0.0/0           reject-with icmp-port-unreachable
> REJECT     all  --  0.0.0.0/0            0.0.0.0/0           reject-with icmp-port-unreachable
>
> Chain OUTPUT (policy ACCEPT)
> target     prot opt source               destination
>
>
> [root@node002 ~]# ebtables -L
> Bridge table: filter
>
> Bridge chain: INPUT, entries: 0, policy: ACCEPT
>
> Bridge chain: FORWARD, entries: 0, policy: ACCEPT
>
> Bridge chain: OUTPUT, entries: 0, policy: ACCEPT
>
> [root@node002 ~]# tcpdump -i vnet0 udp
> tcpdump: WARNING: vnet0: no IPv4 address assigned
> tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
> listening on vnet0, link-type EN10MB (Ethernet), capture size 65535 bytes
> 17:08:08.849344 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 00:00:00:00:00:0d (oui Ethernet), length 387
> 17:08:08.849413 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 00:00:00:00:00:0d (oui Ethernet), length 387
> 17:08:08.849661 IP master.cm.cluster.bootps > 255.255.255.255.bootpc: BOOTP/DHCP, Reply, length 360
> 17:08:09.812645 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 00:00:00:00:00:0d (oui Ethernet), length 387
> 17:08:09.812709 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 00:00:00:00:00:0d (oui Ethernet), length 387
> 17:08:09.812903 IP master.cm.cluster.bootps > 255.255.255.255.bootpc: BOOTP/DHCP, Reply, length 360
> 17:08:11.789993 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 00:00:00:00:00:0d (oui Ethernet), length 399
> 17:08:11.790107 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 00:00:00:00:00:0d (oui Ethernet), length 399
> 17:08:11.790294 IP master.cm.cluster.bootps > 255.255.255.255.bootpc: BOOTP/DHCP, Reply, length 360

Strange how the VM gets 3 DHCP Replies.  That makes it seem like the
VM isn't receiving/processing the DHCP Replies.

Your screenshot shows that the IP address and other network details
from DHCP are being received though...

Stefan

^ permalink raw reply	[flat|nested] 14+ messages in thread

* Re: [libvirt-users] vm pxe fail
  2012-08-16 12:25 vm pxe fail Andrew Holway
  2012-08-16 13:54 ` Stefan Hajnoczi
@ 2012-08-17  2:34 ` Alex Jia
  2012-08-17  8:24   ` Andrew Holway
                     ` (2 more replies)
  1 sibling, 3 replies; 14+ messages in thread
From: Alex Jia @ 2012-08-17  2:34 UTC (permalink / raw)
  To: Andrew Holway; +Cc: kvm

Hi Andrew,
I can't confirm a root reason based on your information, perhaps you may
try to find a reason by yourself via the following docs:

http://wiki.libvirt.org/page/PXE_boot_%28or_dhcp%29_on_guest_failed  (Troubleshooting)
http://docs.fedoraproject.org/en-US/Fedora/13/html/Virtualization_Guide/sect-Virtualization-Virtualized_guest_installation_overview-Installing_guests_with_PXE.html  (User Guide)

If can't, please provide your version of kvm, libvirt, tftp, etc, and run 'virsh net-dumpxml br0' to dump your
network bridge XML configuration, and run 'cat pxelinux.cfg' to show your pxelinux configuration, thanks.

-- 
Regards,     
Alex


----- Original Message -----
From: "Andrew Holway" <a.holway@syseleven.de>
To: kvm@vger.kernel.org
Sent: Thursday, August 16, 2012 8:25:35 PM
Subject: [libvirt-users] vm pxe fail

Hallo

I have a kvm vm that I am attempting to boot from pxe. The dhcp works perfectly and I can see the VM in the pxe server arp. but the tftp just times out. I don't see any tftp traffic on either the physical host or on the pie server. I am using a bridged interface. I have tried using several virtual nic drivers, several different mac addresses and several different ips.  on the physical host I can get the pxelinux.0 file from the pxe server via tftp and can clearly see that traffic with tcpdump.

Ive tried using various virtual interfaces.

I can pxe boot my physical hosts with no problems.

I can tftp fine from the physical host and see the traffic with ethdump

Here is the terminal output from the VM: https://dl.dropbox.com/u/98200887/Screen%20Shot%202012-08-15%20at%206.41.12%20PM.png

Thanks,

Andrew

[root@node002 ~]# yum list | grep qemu
gpxe-roms-qemu.noarch                   0.9.7-6.9.el6               @base       
qemu-img.x86_64                         2:0.12.1.2-2.295.el6_3.1    @updates    
qemu-kvm.x86_64                         2:0.12.1.2-2.295.el6_3.1    @updates    
qemu-guest-agent.x86_64                 2:0.12.1.2-2.295.el6_3.1    updates     
qemu-kvm-tools.x86_64                   2:0.12.1.2-2.295.el6_3.1    updates 

[root@node002 ~]# ethtool eth0
Settings for eth0:
	Supported ports: [ TP ]
	Supported link modes:   10000baseT/Full 
	Supports auto-negotiation: No
	Advertised link modes:  10000baseT/Full 
	Advertised pause frame use: No
	Advertised auto-negotiation: No
	Speed: Unknown!
	Duplex: Unknown! (255)
	Port: Twisted Pair
	PHYAD: 0
	Transceiver: internal
	Auto-negotiation: off
	MDI-X: Unknown
	Supports Wake-on: g
	Wake-on: g
	Current message level: 0x00000014 (20)
	Link detected: no

[root@node002 ~]# brctl show
bridge name	bridge id		STP enabled	interfaces
br0		8000.009c02241ae0	no		eth1
							vnet0
virbr0		8000.525400a6d5aa	yes		virbr0-nic

[root@node002 ~]# ethtool vnet0
Settings for vnet0:
	Supported ports: [ ]
	Supported link modes:   
	Supports auto-negotiation: No
	Advertised link modes:  Not reported
	Advertised pause frame use: No
	Advertised auto-negotiation: No
	Speed: 10Mb/s
	Duplex: Full
	Port: Twisted Pair
	PHYAD: 0
	Transceiver: internal
	Auto-negotiation: off
	MDI-X: Unknown
	Current message level: 0xffffffa1 (-95)
	Link detected: yes

<domain type='kvm'>
 <name>vm004</name>
 <uuid>4f03b09b-e834-bbf3-a6c2-1689f3156ef2</uuid>
 <memory unit='KiB'>2097152</memory>
 <currentMemory unit='KiB'>2097152</currentMemory>
 <vcpu placement='static'>2</vcpu>
 <os>
   <type arch='x86_64' machine='rhel6.3.0'>hvm</type>
   <boot dev='hd'/>
 </os>
 <features>
   <acpi/>
   <apic/>
   <pae/>
 </features>
 <clock offset='utc'/>
 <on_poweroff>destroy</on_poweroff>
 <on_reboot>restart</on_reboot>
 <on_crash>restart</on_crash>
 <devices>
   <emulator>/usr/libexec/qemu-kvm</emulator>
   <disk type='file' device='disk'>
     <driver name='qemu' type='raw' cache='none'/>
     <source file='/cm/shared/vm/vm004.img'/>
     <target dev='hda' bus='ide'/>
     <address type='drive' controller='0' bus='0' target='0' unit='0'/>
   </disk>
   <disk type='block' device='cdrom'>
     <driver name='qemu' type='raw'/>
     <target dev='hdc' bus='ide'/>
     <readonly/>
     <address type='drive' controller='0' bus='1' target='0' unit='0'/>
   </disk>
   <controller type='usb' index='0'>
     <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x2'/>
   </controller>
   <controller type='ide' index='0'>
     <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x1'/>
   </controller>
   <interface type='bridge'>
     <mac address='00:00:00:00:00:0d'/>
     <source bridge='br0'/>
     <model type='rtl8139'/>
     <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/>
   </interface>
   <serial type='pty'>
     <target port='0'/>
   </serial>
   <console type='pty'>
     <target type='serial' port='0'/>
   </console>
   <input type='mouse' bus='ps2'/>
   <graphics type='vnc' port='-1' autoport='yes'/>
   <video>
     <model type='cirrus' vram='9216' heads='1'/>
     <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0'/>
   </video>
   <memballoon model='virtio'>
     <address type='pci' domain='0x0000' bus='0x00' slot='0x04' function='0x0'/>
   </memballoon>
 </devices>
</domain>



_______________________________________________
libvirt-users mailing list
libvirt-users@redhat.com
https://www.redhat.com/mailman/listinfo/libvirt-users

^ permalink raw reply	[flat|nested] 14+ messages in thread

* Re: [libvirt-users] vm pxe fail
  2012-08-17  2:34 ` [libvirt-users] " Alex Jia
@ 2012-08-17  8:24   ` Andrew Holway
  2012-08-17  8:45     ` Fwd: " Alex Jia
  2012-08-20 17:47   ` Andrew Holway
  2012-08-31 13:32   ` Andrew Holway
  2 siblings, 1 reply; 14+ messages in thread
From: Andrew Holway @ 2012-08-17  8:24 UTC (permalink / raw)
  To: Alex Jia; +Cc: kvm

[-- Attachment #1: Type: text/plain, Size: 2535 bytes --]

Hello,

On Aug 17, 2012, at 4:34 AM, Alex Jia wrote:

> Hi Andrew,
> I can't confirm a root reason based on your information, perhaps you may
> try to find a reason by yourself via the following docs:
> 
> http://wiki.libvirt.org/page/PXE_boot_%28or_dhcp%29_on_guest_failed  (Troubleshooting)
> http://docs.fedoraproject.org/en-US/Fedora/13/html/Virtualization_Guide/sect-Virtualization-Virtualized_guest_installation_overview-Installing_guests_with_PXE.html  (User Guide)

Everything seems quite normal.

> 
> If can't, please provide your version of kvm, libvirt, tftp, etc, and run 'virsh net-dumpxml br0' to dump your
> network bridge XML configuration, and run 'cat pxelinux.cfg' to show your pxelinux configuration, thanks.

default is my pxelinux configuration but I'm not sure is this is what your after.

dhcp is a protocol decode of the DHCP traffic. You see that the VM is sending each request twice which is a bit odd.

[root@node002 ~]# yum list | grep qemu
gpxe-roms-qemu.noarch                   0.9.7-6.9.el6               @base       
qemu-img.x86_64                         2:0.12.1.2-2.295.el6_3.1    @updates    
qemu-kvm.x86_64                         2:0.12.1.2-2.295.el6_3.1    @updates    
qemu-guest-agent.x86_64                 2:0.12.1.2-2.295.el6_3.1    updates     
qemu-kvm-tools.x86_64                   2:0.12.1.2-2.295.el6_3.1    updates    

br0 is created by brctl. There is not XML config as far as I am aware.

[root@node002 ~]# ifconfig br0
br0       Link encap:Ethernet  HWaddr 00:9C:02:24:1A:E0  
          inet addr:10.141.80.2  Bcast:10.141.255.255  Mask:255.255.0.0
          inet6 addr: fe80::29c:2ff:fe24:1ae0/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:185129 errors:0 dropped:0 overruns:0 frame:0
          TX packets:2094 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:8820359 (8.4 MiB)  TX bytes:123842 (120.9 KiB)

[root@node002 ~]# ifconfig eth0
eth0      Link encap:Ethernet  HWaddr 00:02:C9:36:21:A1  
          BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)

[root@node002 ~]# brctl show
bridge name	bridge id		STP enabled	interfaces
br0		8000.009c02241ae0	no		eth1
							vnet0
virbr0		8000.525400a6d5aa	yes		virbr0-nic

[-- Attachment #2: default.txt --]
[-- Type: text/plain, Size: 2807 bytes --]

# This is the Cluster Manager PXE configuration file.
#
# Note that every boot option should specify 'IPAPPEND 3', otherwise the
# ramdisk will fail.
#
# An optional kernel parameter 'INSTALLMODE' can be used to force a certain
# installmode.
#
# The CMDaemon will generate additional kernel parameters (if configured)
# and insert them between the CMDS rdblacklist=nouveau CMDE markers.
#
# There is also a possibility to try and boot the next device in the BIOS
# boot order. It can be specified as:
#
# LABEL disk
#   localboot 0
#   MENU LABEL ^BOOT     - Boot next device in BIOS boot order.
#
# End of documentation, configuration follows:

LABEL linux
  KERNEL vmlinuz
  IPAPPEND 3
  APPEND initrd=initrd CMDS rdblacklist=nouveau CMDE
  MENU LABEL ^AUTO       - Normal node boot
  MENU DEFAULT

LABEL full
  KERNEL vmlinuz
  IPAPPEND 3
  APPEND initrd=initrd CMDS rdblacklist=nouveau CMDE INSTALLMODE=FULL CANCELBURN=1
  MENU LABEL ^FULL       - Force FULL install (cancels burn)
  MENU HIDE

LABEL main
  KERNEL vmlinuz
  IPAPPEND 3
  APPEND initrd=initrd CMDS rdblacklist=nouveau CMDE INSTALLMODE=MAIN CANCELBURN=1
  MENU LABEL MA^IN       - Drop to maintenance shell

LABEL newburn
  KERNEL vmlinuz
  IPAPPEND 3
  APPEND initrd=initrd CMDS rdblacklist=nouveau CMDE NEWBURN=1
  MENU LABEL NEW^BURN    - Force a new burn
  MENU HIDE

LABEL manburn
  KERNEL vmlinuz
  IPAPPEND 3
  APPEND initrd=initrd CMDS rdblacklist=nouveau CMDE NEWBURN=1 BURNMENUPAUSE=1 
  MENU LABEL ^MANBURN    - Force a new burn (no menu timeout)
  MENU HIDE

LABEL cancelburn
  KERNEL vmlinuz
  IPAPPEND 3
  APPEND initrd=initrd CMDS rdblacklist=nouveau CMDE CANCELBURN=1
  MENU LABEL ^CANCELBURN - Cancel the current burn
  MENU HIDE

LABEL RESCUE
  KERNEL kernel.rescue
  MENU LABEL ^RESCUE     - Start rescue environment
  APPEND vga=normal initrd=rescue.rootfs.cgz root=/dev/ram0 rw nokeymap

LABEL localdrive
  MENU LABEL ^DRIVE      - Boot from first hard drive
  KERNEL chain.c32
  APPEND hd0

LABEL MEMTEST
  KERNEL memtest
  MENU LABEL MEM^TEST    - Start Memtest86

LABEL MEMPLUS
  KERNEL memtestplus
  MENU LABEL MEM^PLUS    - Start Memtest86+

INCLUDE bios/menu.conf
INCLUDE mpxe/minstall.conf

DEFAULT menu.c32
PROMPT 0
TIMEOUT 50
MENU TITLE Cluster Manager PXE Environment
MENU BACKGROUND bootlogo.png
MENU COLOR sel          7;37;40    #ff94cc31 #ff303030 all
MENU COLOR hotsel       1;7;37;40  #ff94cc31 #ff303030 all
MENU COLOR unsel        37;44      #ff78af00 #00000000 std
MENU COLOR hotkey       1;37;44    #ff94cc31 #00000000 std
MENU COLOR border       30;44      #ff78af00 #00000000 std
MENU COLOR title        1;36;44    #ff78af00 #00000000 std
MENU COLOR tabmsg       31;40      #ff78af00 #00000000 std


[-- Attachment #3: Type: text/plain, Size: 1 bytes --]



[-- Attachment #4: dhcp.txt --]
[-- Type: text/plain, Size: 10181 bytes --]

[root@node002 ~]# tcpdump -vv -i br0 udp
tcpdump: listening on br0, link-type EN10MB (Ethernet), capture size 65535 bytes
17:39:24.212593 IP (tos 0x0, ttl 64, id 1, offset 0, flags [none], proto UDP (17), length 415)
    0.0.0.0.bootpc > 255.255.255.255.bootps: [udp sum ok] BOOTP/DHCP, Request from 00:00:00:00:00:0d (oui Ethernet), length 387, xid 0xd, Flags [none] (0x0000)
	  Client-Ethernet-Address 00:00:00:00:00:0d (oui Ethernet)
	  Vendor-rfc1048 Extensions
	    Magic Cookie 0x63825363
	    GUID Option 97, length 17: 0.79.3.176.155.232.52.187.243.166.194.22.137.243.21.110.242
	    Client-ID Option 61, length 7: ether 00:00:00:00:00:0d
	    T175 Option 175, length 45: 177.5.1.16.236.129.57.19.1.1.23.1.1.21.1.1.24.1.1.35.1.1.34.1.1.25.1.1.33.1.1.16.1.2.18.1.1.17.1.1.235.3.0.9.7
	    DHCP-Message Option 53, length 1: Discover
	    MSZ Option 57, length 2: 1472
	    ARCH Option 93, length 2: 0
	    NDI Option 94, length 3: 1.2.1
	    Vendor-Class Option 60, length 32: "PXEClient:Arch:00000:UNDI:002001"
	    CLASS Option 77, length 4: "gPXE"
	    Parameter-Request Option 55, length 13: 
	      Subnet-Mask, Default-Gateway, Domain-Name-Server, LOG
	      Hostname, Domain-Name, RP, Vendor-Option
	      Vendor-Class, TFTP, BF, Option 175
	      Option 203
17:39:24.212659 IP (tos 0x0, ttl 64, id 1, offset 0, flags [none], proto UDP (17), length 415)
    0.0.0.0.bootpc > 255.255.255.255.bootps: [udp sum ok] BOOTP/DHCP, Request from 00:00:00:00:00:0d (oui Ethernet), length 387, xid 0xd, Flags [none] (0x0000)
	  Client-Ethernet-Address 00:00:00:00:00:0d (oui Ethernet)
	  Vendor-rfc1048 Extensions
	    Magic Cookie 0x63825363
	    GUID Option 97, length 17: 0.79.3.176.155.232.52.187.243.166.194.22.137.243.21.110.242
	    Client-ID Option 61, length 7: ether 00:00:00:00:00:0d
	    T175 Option 175, length 45: 177.5.1.16.236.129.57.19.1.1.23.1.1.21.1.1.24.1.1.35.1.1.34.1.1.25.1.1.33.1.1.16.1.2.18.1.1.17.1.1.235.3.0.9.7
	    DHCP-Message Option 53, length 1: Discover
	    MSZ Option 57, length 2: 1472
	    ARCH Option 93, length 2: 0
	    NDI Option 94, length 3: 1.2.1
	    Vendor-Class Option 60, length 32: "PXEClient:Arch:00000:UNDI:002001"
	    CLASS Option 77, length 4: "gPXE"
	    Parameter-Request Option 55, length 13: 
	      Subnet-Mask, Default-Gateway, Domain-Name-Server, LOG
	      Hostname, Domain-Name, RP, Vendor-Option
	      Vendor-Class, TFTP, BF, Option 175
	      Option 203
17:39:24.212913 IP (tos 0x0, ttl 64, id 0, offset 0, flags [DF], proto UDP (17), length 388)
    master.cm.cluster.bootps > 255.255.255.255.bootpc: [udp sum ok] BOOTP/DHCP, Reply, length 360, xid 0xd, Flags [none] (0x0000)
	  Your-IP vm001.cm.cluster
	  Server-IP master.cm.cluster
	  Client-Ethernet-Address 00:00:00:00:00:0d (oui Ethernet)
	  file "cm-images/default-image/boot/pxelinux.0"
	  Vendor-rfc1048 Extensions
	    Magic Cookie 0x63825363
	    DHCP-Message Option 53, length 1: Offer
	    Server-ID Option 54, length 4: master.cm.cluster
	    Lease-Time Option 51, length 4: 86400
	    Subnet-Mask Option 1, length 4: 255.255.0.0
	    Default-Gateway Option 3, length 4: master.cm.cluster
	    Domain-Name-Server Option 6, length 4: master.cm.cluster
	    Hostname Option 12, length 17: "vm001.internalnet"
	    Domain-Name Option 15, length 65: "eth.cluster brightcomputing.com ib.cluster ilo.cluster cm.cluster"
17:39:25.178728 IP (tos 0x0, ttl 64, id 2, offset 0, flags [none], proto UDP (17), length 415)
    0.0.0.0.bootpc > 255.255.255.255.bootps: [udp sum ok] BOOTP/DHCP, Request from 00:00:00:00:00:0d (oui Ethernet), length 387, xid 0xd, Flags [none] (0x0000)
	  Client-Ethernet-Address 00:00:00:00:00:0d (oui Ethernet)
	  Vendor-rfc1048 Extensions
	    Magic Cookie 0x63825363
	    GUID Option 97, length 17: 0.79.3.176.155.232.52.187.243.166.194.22.137.243.21.110.242
	    Client-ID Option 61, length 7: ether 00:00:00:00:00:0d
	    T175 Option 175, length 45: 177.5.1.16.236.129.57.19.1.1.23.1.1.21.1.1.24.1.1.35.1.1.34.1.1.25.1.1.33.1.1.16.1.2.18.1.1.17.1.1.235.3.0.9.7
	    DHCP-Message Option 53, length 1: Discover
	    MSZ Option 57, length 2: 1472
	    ARCH Option 93, length 2: 0
	    NDI Option 94, length 3: 1.2.1
	    Vendor-Class Option 60, length 32: "PXEClient:Arch:00000:UNDI:002001"
	    CLASS Option 77, length 4: "gPXE"
	    Parameter-Request Option 55, length 13: 
	      Subnet-Mask, Default-Gateway, Domain-Name-Server, LOG
	      Hostname, Domain-Name, RP, Vendor-Option
	      Vendor-Class, TFTP, BF, Option 175
	      Option 203
17:39:25.178784 IP (tos 0x0, ttl 64, id 2, offset 0, flags [none], proto UDP (17), length 415)
    0.0.0.0.bootpc > 255.255.255.255.bootps: [udp sum ok] BOOTP/DHCP, Request from 00:00:00:00:00:0d (oui Ethernet), length 387, xid 0xd, Flags [none] (0x0000)
	  Client-Ethernet-Address 00:00:00:00:00:0d (oui Ethernet)
	  Vendor-rfc1048 Extensions
	    Magic Cookie 0x63825363
	    GUID Option 97, length 17: 0.79.3.176.155.232.52.187.243.166.194.22.137.243.21.110.242
	    Client-ID Option 61, length 7: ether 00:00:00:00:00:0d
	    T175 Option 175, length 45: 177.5.1.16.236.129.57.19.1.1.23.1.1.21.1.1.24.1.1.35.1.1.34.1.1.25.1.1.33.1.1.16.1.2.18.1.1.17.1.1.235.3.0.9.7
	    DHCP-Message Option 53, length 1: Discover
	    MSZ Option 57, length 2: 1472
	    ARCH Option 93, length 2: 0
	    NDI Option 94, length 3: 1.2.1
	    Vendor-Class Option 60, length 32: "PXEClient:Arch:00000:UNDI:002001"
	    CLASS Option 77, length 4: "gPXE"
	    Parameter-Request Option 55, length 13: 
	      Subnet-Mask, Default-Gateway, Domain-Name-Server, LOG
	      Hostname, Domain-Name, RP, Vendor-Option
	      Vendor-Class, TFTP, BF, Option 175
	      Option 203
17:39:25.179009 IP (tos 0x0, ttl 64, id 0, offset 0, flags [DF], proto UDP (17), length 388)
    master.cm.cluster.bootps > 255.255.255.255.bootpc: [udp sum ok] BOOTP/DHCP, Reply, length 360, xid 0xd, Flags [none] (0x0000)
	  Your-IP vm001.cm.cluster
	  Server-IP master.cm.cluster
	  Client-Ethernet-Address 00:00:00:00:00:0d (oui Ethernet)
	  file "cm-images/default-image/boot/pxelinux.0"
	  Vendor-rfc1048 Extensions
	    Magic Cookie 0x63825363
	    DHCP-Message Option 53, length 1: Offer
	    Server-ID Option 54, length 4: master.cm.cluster
	    Lease-Time Option 51, length 4: 86400
	    Subnet-Mask Option 1, length 4: 255.255.0.0
	    Default-Gateway Option 3, length 4: master.cm.cluster
	    Domain-Name-Server Option 6, length 4: master.cm.cluster
	    Hostname Option 12, length 17: "vm001.internalnet"
	    Domain-Name Option 15, length 65: "eth.cluster brightcomputing.com ib.cluster ilo.cluster cm.cluster"
17:39:27.156065 IP (tos 0x0, ttl 64, id 3, offset 0, flags [none], proto UDP (17), length 427)
    0.0.0.0.bootpc > 255.255.255.255.bootps: [udp sum ok] BOOTP/DHCP, Request from 00:00:00:00:00:0d (oui Ethernet), length 399, xid 0xd, Flags [none] (0x0000)
	  Client-Ethernet-Address 00:00:00:00:00:0d (oui Ethernet)
	  Vendor-rfc1048 Extensions
	    Magic Cookie 0x63825363
	    Requested-IP Option 50, length 4: vm001.cm.cluster
	    Server-ID Option 54, length 4: master.cm.cluster
	    GUID Option 97, length 17: 0.79.3.176.155.232.52.187.243.166.194.22.137.243.21.110.242
	    Client-ID Option 61, length 7: ether 00:00:00:00:00:0d
	    T175 Option 175, length 45: 177.5.1.16.236.129.57.19.1.1.23.1.1.21.1.1.24.1.1.35.1.1.34.1.1.25.1.1.33.1.1.16.1.2.18.1.1.17.1.1.235.3.0.9.7
	    DHCP-Message Option 53, length 1: Request
	    MSZ Option 57, length 2: 1472
	    ARCH Option 93, length 2: 0
	    NDI Option 94, length 3: 1.2.1
	    Vendor-Class Option 60, length 32: "PXEClient:Arch:00000:UNDI:002001"
	    CLASS Option 77, length 4: "gPXE"
	    Parameter-Request Option 55, length 13: 
	      Subnet-Mask, Default-Gateway, Domain-Name-Server, LOG
	      Hostname, Domain-Name, RP, Vendor-Option
	      Vendor-Class, TFTP, BF, Option 175
	      Option 203
17:39:27.156121 IP (tos 0x0, ttl 64, id 3, offset 0, flags [none], proto UDP (17), length 427)
    0.0.0.0.bootpc > 255.255.255.255.bootps: [udp sum ok] BOOTP/DHCP, Request from 00:00:00:00:00:0d (oui Ethernet), length 399, xid 0xd, Flags [none] (0x0000)
	  Client-Ethernet-Address 00:00:00:00:00:0d (oui Ethernet)
	  Vendor-rfc1048 Extensions
	    Magic Cookie 0x63825363
	    Requested-IP Option 50, length 4: vm001.cm.cluster
	    Server-ID Option 54, length 4: master.cm.cluster
	    GUID Option 97, length 17: 0.79.3.176.155.232.52.187.243.166.194.22.137.243.21.110.242
	    Client-ID Option 61, length 7: ether 00:00:00:00:00:0d
	    T175 Option 175, length 45: 177.5.1.16.236.129.57.19.1.1.23.1.1.21.1.1.24.1.1.35.1.1.34.1.1.25.1.1.33.1.1.16.1.2.18.1.1.17.1.1.235.3.0.9.7
	    DHCP-Message Option 53, length 1: Request
	    MSZ Option 57, length 2: 1472
	    ARCH Option 93, length 2: 0
	    NDI Option 94, length 3: 1.2.1
	    Vendor-Class Option 60, length 32: "PXEClient:Arch:00000:UNDI:002001"
	    CLASS Option 77, length 4: "gPXE"
	    Parameter-Request Option 55, length 13: 
	      Subnet-Mask, Default-Gateway, Domain-Name-Server, LOG
	      Hostname, Domain-Name, RP, Vendor-Option
	      Vendor-Class, TFTP, BF, Option 175
	      Option 203
17:39:27.156373 IP (tos 0x0, ttl 64, id 0, offset 0, flags [DF], proto UDP (17), length 388)
    master.cm.cluster.bootps > 255.255.255.255.bootpc: [udp sum ok] BOOTP/DHCP, Reply, length 360, xid 0xd, Flags [none] (0x0000)
	  Your-IP vm001.cm.cluster
	  Server-IP master.cm.cluster
	  Client-Ethernet-Address 00:00:00:00:00:0d (oui Ethernet)
	  file "cm-images/default-image/boot/pxelinux.0"
	  Vendor-rfc1048 Extensions
	    Magic Cookie 0x63825363
	    DHCP-Message Option 53, length 1: ACK
	    Server-ID Option 54, length 4: master.cm.cluster
	    Lease-Time Option 51, length 4: 86400
	    Subnet-Mask Option 1, length 4: 255.255.0.0
	    Default-Gateway Option 3, length 4: master.cm.cluster
	    Domain-Name-Server Option 6, length 4: master.cm.cluster
	    Hostname Option 12, length 17: "vm001.internalnet"
	    Domain-Name Option 15, length 65: "eth.cluster brightcomputing.com ib.cluster ilo.cluster cm.cluster"

[-- Attachment #5: Type: text/plain, Size: 5092 bytes --]


> 
> -- 
> Regards,     
> Alex
> 
> 
> ----- Original Message -----
> From: "Andrew Holway" <a.holway@syseleven.de>
> To: kvm@vger.kernel.org
> Sent: Thursday, August 16, 2012 8:25:35 PM
> Subject: [libvirt-users] vm pxe fail
> 
> Hallo
> 
> I have a kvm vm that I am attempting to boot from pxe. The dhcp works perfectly and I can see the VM in the pxe server arp. but the tftp just times out. I don't see any tftp traffic on either the physical host or on the pie server. I am using a bridged interface. I have tried using several virtual nic drivers, several different mac addresses and several different ips.  on the physical host I can get the pxelinux.0 file from the pxe server via tftp and can clearly see that traffic with tcpdump.
> 
> Ive tried using various virtual interfaces.
> 
> I can pxe boot my physical hosts with no problems.
> 
> I can tftp fine from the physical host and see the traffic with ethdump
> 
> Here is the terminal output from the VM: https://dl.dropbox.com/u/98200887/Screen%20Shot%202012-08-15%20at%206.41.12%20PM.png
> 
> Thanks,
> 
> Andrew
> 
> [root@node002 ~]# yum list | grep qemu
> gpxe-roms-qemu.noarch                   0.9.7-6.9.el6               @base       
> qemu-img.x86_64                         2:0.12.1.2-2.295.el6_3.1    @updates    
> qemu-kvm.x86_64                         2:0.12.1.2-2.295.el6_3.1    @updates    
> qemu-guest-agent.x86_64                 2:0.12.1.2-2.295.el6_3.1    updates     
> qemu-kvm-tools.x86_64                   2:0.12.1.2-2.295.el6_3.1    updates 
> 
> [root@node002 ~]# ethtool eth0
> Settings for eth0:
> 	Supported ports: [ TP ]
> 	Supported link modes:   10000baseT/Full 
> 	Supports auto-negotiation: No
> 	Advertised link modes:  10000baseT/Full 
> 	Advertised pause frame use: No
> 	Advertised auto-negotiation: No
> 	Speed: Unknown!
> 	Duplex: Unknown! (255)
> 	Port: Twisted Pair
> 	PHYAD: 0
> 	Transceiver: internal
> 	Auto-negotiation: off
> 	MDI-X: Unknown
> 	Supports Wake-on: g
> 	Wake-on: g
> 	Current message level: 0x00000014 (20)
> 	Link detected: no
> 
> [root@node002 ~]# brctl show
> bridge name	bridge id		STP enabled	interfaces
> br0		8000.009c02241ae0	no		eth1
> 							vnet0
> virbr0		8000.525400a6d5aa	yes		virbr0-nic
> 
> [root@node002 ~]# ethtool vnet0
> Settings for vnet0:
> 	Supported ports: [ ]
> 	Supported link modes:   
> 	Supports auto-negotiation: No
> 	Advertised link modes:  Not reported
> 	Advertised pause frame use: No
> 	Advertised auto-negotiation: No
> 	Speed: 10Mb/s
> 	Duplex: Full
> 	Port: Twisted Pair
> 	PHYAD: 0
> 	Transceiver: internal
> 	Auto-negotiation: off
> 	MDI-X: Unknown
> 	Current message level: 0xffffffa1 (-95)
> 	Link detected: yes
> 
> <domain type='kvm'>
> <name>vm004</name>
> <uuid>4f03b09b-e834-bbf3-a6c2-1689f3156ef2</uuid>
> <memory unit='KiB'>2097152</memory>
> <currentMemory unit='KiB'>2097152</currentMemory>
> <vcpu placement='static'>2</vcpu>
> <os>
>   <type arch='x86_64' machine='rhel6.3.0'>hvm</type>
>   <boot dev='hd'/>
> </os>
> <features>
>   <acpi/>
>   <apic/>
>   <pae/>
> </features>
> <clock offset='utc'/>
> <on_poweroff>destroy</on_poweroff>
> <on_reboot>restart</on_reboot>
> <on_crash>restart</on_crash>
> <devices>
>   <emulator>/usr/libexec/qemu-kvm</emulator>
>   <disk type='file' device='disk'>
>     <driver name='qemu' type='raw' cache='none'/>
>     <source file='/cm/shared/vm/vm004.img'/>
>     <target dev='hda' bus='ide'/>
>     <address type='drive' controller='0' bus='0' target='0' unit='0'/>
>   </disk>
>   <disk type='block' device='cdrom'>
>     <driver name='qemu' type='raw'/>
>     <target dev='hdc' bus='ide'/>
>     <readonly/>
>     <address type='drive' controller='0' bus='1' target='0' unit='0'/>
>   </disk>
>   <controller type='usb' index='0'>
>     <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x2'/>
>   </controller>
>   <controller type='ide' index='0'>
>     <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x1'/>
>   </controller>
>   <interface type='bridge'>
>     <mac address='00:00:00:00:00:0d'/>
>     <source bridge='br0'/>
>     <model type='rtl8139'/>
>     <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/>
>   </interface>
>   <serial type='pty'>
>     <target port='0'/>
>   </serial>
>   <console type='pty'>
>     <target type='serial' port='0'/>
>   </console>
>   <input type='mouse' bus='ps2'/>
>   <graphics type='vnc' port='-1' autoport='yes'/>
>   <video>
>     <model type='cirrus' vram='9216' heads='1'/>
>     <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0'/>
>   </video>
>   <memballoon model='virtio'>
>     <address type='pci' domain='0x0000' bus='0x00' slot='0x04' function='0x0'/>
>   </memballoon>
> </devices>
> </domain>
> 
> 
> 
> _______________________________________________
> libvirt-users mailing list
> libvirt-users@redhat.com
> https://www.redhat.com/mailman/listinfo/libvirt-users


^ permalink raw reply	[flat|nested] 14+ messages in thread

* Fwd: [libvirt-users] vm pxe fail
  2012-08-17  8:24   ` Andrew Holway
@ 2012-08-17  8:45     ` Alex Jia
  0 siblings, 0 replies; 14+ messages in thread
From: Alex Jia @ 2012-08-17  8:45 UTC (permalink / raw)
  To: libvirt-users; +Cc: KVM devel mailing list

[-- Attachment #1: Type: text/plain, Size: 7643 bytes --]

----- Forwarded Message -----
From: "Andrew Holway" <a.holway@syseleven.de>
To: "Alex Jia" <ajia@redhat.com>
Cc: kvm@vger.kernel.org
Sent: Friday, August 17, 2012 4:24:33 PM
Subject: Re: [libvirt-users] vm pxe fail

Hello,

On Aug 17, 2012, at 4:34 AM, Alex Jia wrote:

> Hi Andrew,
> I can't confirm a root reason based on your information, perhaps you may
> try to find a reason by yourself via the following docs:
> 
> http://wiki.libvirt.org/page/PXE_boot_%28or_dhcp%29_on_guest_failed  (Troubleshooting)
> http://docs.fedoraproject.org/en-US/Fedora/13/html/Virtualization_Guide/sect-Virtualization-Virtualized_guest_installation_overview-Installing_guests_with_PXE.html  (User Guide)

Everything seems quite normal.

> 
> If can't, please provide your version of kvm, libvirt, tftp, etc, and run 'virsh net-dumpxml br0' to dump your
> network bridge XML configuration, and run 'cat pxelinux.cfg' to show your pxelinux configuration, thanks.

default is my pxelinux configuration but I'm not sure is this is what your after.

dhcp is a protocol decode of the DHCP traffic. You see that the VM is sending each request twice which is a bit odd.

[root@node002 ~]# yum list | grep qemu
gpxe-roms-qemu.noarch                   0.9.7-6.9.el6               @base       
qemu-img.x86_64                         2:0.12.1.2-2.295.el6_3.1    @updates    
qemu-kvm.x86_64                         2:0.12.1.2-2.295.el6_3.1    @updates    
qemu-guest-agent.x86_64                 2:0.12.1.2-2.295.el6_3.1    updates     
qemu-kvm-tools.x86_64                   2:0.12.1.2-2.295.el6_3.1    updates    

br0 is created by brctl. There is not XML config as far as I am aware.

[root@node002 ~]# ifconfig br0
br0       Link encap:Ethernet  HWaddr 00:9C:02:24:1A:E0  
          inet addr:10.141.80.2  Bcast:10.141.255.255  Mask:255.255.0.0
          inet6 addr: fe80::29c:2ff:fe24:1ae0/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:185129 errors:0 dropped:0 overruns:0 frame:0
          TX packets:2094 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:8820359 (8.4 MiB)  TX bytes:123842 (120.9 KiB)

[root@node002 ~]# ifconfig eth0
eth0      Link encap:Ethernet  HWaddr 00:02:C9:36:21:A1  
          BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)

[root@node002 ~]# brctl show
bridge name	bridge id		STP enabled	interfaces
br0		8000.009c02241ae0	no		eth1
							vnet0
virbr0		8000.525400a6d5aa	yes		virbr0-nic




> 
> -- 
> Regards,     
> Alex
> 
> 
> ----- Original Message -----
> From: "Andrew Holway" <a.holway@syseleven.de>
> To: kvm@vger.kernel.org
> Sent: Thursday, August 16, 2012 8:25:35 PM
> Subject: [libvirt-users] vm pxe fail
> 
> Hallo
> 
> I have a kvm vm that I am attempting to boot from pxe. The dhcp works perfectly and I can see the VM in the pxe server arp. but the tftp just times out. I don't see any tftp traffic on either the physical host or on the pie server. I am using a bridged interface. I have tried using several virtual nic drivers, several different mac addresses and several different ips.  on the physical host I can get the pxelinux.0 file from the pxe server via tftp and can clearly see that traffic with tcpdump.
> 
> Ive tried using various virtual interfaces.
> 
> I can pxe boot my physical hosts with no problems.
> 
> I can tftp fine from the physical host and see the traffic with ethdump
> 
> Here is the terminal output from the VM: https://dl.dropbox.com/u/98200887/Screen%20Shot%202012-08-15%20at%206.41.12%20PM.png
> 
> Thanks,
> 
> Andrew
> 
> [root@node002 ~]# yum list | grep qemu
> gpxe-roms-qemu.noarch                   0.9.7-6.9.el6               @base       
> qemu-img.x86_64                         2:0.12.1.2-2.295.el6_3.1    @updates    
> qemu-kvm.x86_64                         2:0.12.1.2-2.295.el6_3.1    @updates    
> qemu-guest-agent.x86_64                 2:0.12.1.2-2.295.el6_3.1    updates     
> qemu-kvm-tools.x86_64                   2:0.12.1.2-2.295.el6_3.1    updates 
> 
> [root@node002 ~]# ethtool eth0
> Settings for eth0:
> 	Supported ports: [ TP ]
> 	Supported link modes:   10000baseT/Full 
> 	Supports auto-negotiation: No
> 	Advertised link modes:  10000baseT/Full 
> 	Advertised pause frame use: No
> 	Advertised auto-negotiation: No
> 	Speed: Unknown!
> 	Duplex: Unknown! (255)
> 	Port: Twisted Pair
> 	PHYAD: 0
> 	Transceiver: internal
> 	Auto-negotiation: off
> 	MDI-X: Unknown
> 	Supports Wake-on: g
> 	Wake-on: g
> 	Current message level: 0x00000014 (20)
> 	Link detected: no
> 
> [root@node002 ~]# brctl show
> bridge name	bridge id		STP enabled	interfaces
> br0		8000.009c02241ae0	no		eth1
> 							vnet0
> virbr0		8000.525400a6d5aa	yes		virbr0-nic
> 
> [root@node002 ~]# ethtool vnet0
> Settings for vnet0:
> 	Supported ports: [ ]
> 	Supported link modes:   
> 	Supports auto-negotiation: No
> 	Advertised link modes:  Not reported
> 	Advertised pause frame use: No
> 	Advertised auto-negotiation: No
> 	Speed: 10Mb/s
> 	Duplex: Full
> 	Port: Twisted Pair
> 	PHYAD: 0
> 	Transceiver: internal
> 	Auto-negotiation: off
> 	MDI-X: Unknown
> 	Current message level: 0xffffffa1 (-95)
> 	Link detected: yes
> 
> <domain type='kvm'>
> <name>vm004</name>
> <uuid>4f03b09b-e834-bbf3-a6c2-1689f3156ef2</uuid>
> <memory unit='KiB'>2097152</memory>
> <currentMemory unit='KiB'>2097152</currentMemory>
> <vcpu placement='static'>2</vcpu>
> <os>
>   <type arch='x86_64' machine='rhel6.3.0'>hvm</type>
>   <boot dev='hd'/>
> </os>
> <features>
>   <acpi/>
>   <apic/>
>   <pae/>
> </features>
> <clock offset='utc'/>
> <on_poweroff>destroy</on_poweroff>
> <on_reboot>restart</on_reboot>
> <on_crash>restart</on_crash>
> <devices>
>   <emulator>/usr/libexec/qemu-kvm</emulator>
>   <disk type='file' device='disk'>
>     <driver name='qemu' type='raw' cache='none'/>
>     <source file='/cm/shared/vm/vm004.img'/>
>     <target dev='hda' bus='ide'/>
>     <address type='drive' controller='0' bus='0' target='0' unit='0'/>
>   </disk>
>   <disk type='block' device='cdrom'>
>     <driver name='qemu' type='raw'/>
>     <target dev='hdc' bus='ide'/>
>     <readonly/>
>     <address type='drive' controller='0' bus='1' target='0' unit='0'/>
>   </disk>
>   <controller type='usb' index='0'>
>     <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x2'/>
>   </controller>
>   <controller type='ide' index='0'>
>     <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x1'/>
>   </controller>
>   <interface type='bridge'>
>     <mac address='00:00:00:00:00:0d'/>
>     <source bridge='br0'/>
>     <model type='rtl8139'/>
>     <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/>
>   </interface>
>   <serial type='pty'>
>     <target port='0'/>
>   </serial>
>   <console type='pty'>
>     <target type='serial' port='0'/>
>   </console>
>   <input type='mouse' bus='ps2'/>
>   <graphics type='vnc' port='-1' autoport='yes'/>
>   <video>
>     <model type='cirrus' vram='9216' heads='1'/>
>     <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0'/>
>   </video>
>   <memballoon model='virtio'>
>     <address type='pci' domain='0x0000' bus='0x00' slot='0x04' function='0x0'/>
>   </memballoon>
> </devices>
> </domain>
> 
> 
> 
> _______________________________________________
> libvirt-users mailing list
> libvirt-users@redhat.com
> https://www.redhat.com/mailman/listinfo/libvirt-users


[-- Attachment #2: default.txt --]
[-- Type: text/plain, Size: 2807 bytes --]

# This is the Cluster Manager PXE configuration file.
#
# Note that every boot option should specify 'IPAPPEND 3', otherwise the
# ramdisk will fail.
#
# An optional kernel parameter 'INSTALLMODE' can be used to force a certain
# installmode.
#
# The CMDaemon will generate additional kernel parameters (if configured)
# and insert them between the CMDS rdblacklist=nouveau CMDE markers.
#
# There is also a possibility to try and boot the next device in the BIOS
# boot order. It can be specified as:
#
# LABEL disk
#   localboot 0
#   MENU LABEL ^BOOT     - Boot next device in BIOS boot order.
#
# End of documentation, configuration follows:

LABEL linux
  KERNEL vmlinuz
  IPAPPEND 3
  APPEND initrd=initrd CMDS rdblacklist=nouveau CMDE
  MENU LABEL ^AUTO       - Normal node boot
  MENU DEFAULT

LABEL full
  KERNEL vmlinuz
  IPAPPEND 3
  APPEND initrd=initrd CMDS rdblacklist=nouveau CMDE INSTALLMODE=FULL CANCELBURN=1
  MENU LABEL ^FULL       - Force FULL install (cancels burn)
  MENU HIDE

LABEL main
  KERNEL vmlinuz
  IPAPPEND 3
  APPEND initrd=initrd CMDS rdblacklist=nouveau CMDE INSTALLMODE=MAIN CANCELBURN=1
  MENU LABEL MA^IN       - Drop to maintenance shell

LABEL newburn
  KERNEL vmlinuz
  IPAPPEND 3
  APPEND initrd=initrd CMDS rdblacklist=nouveau CMDE NEWBURN=1
  MENU LABEL NEW^BURN    - Force a new burn
  MENU HIDE

LABEL manburn
  KERNEL vmlinuz
  IPAPPEND 3
  APPEND initrd=initrd CMDS rdblacklist=nouveau CMDE NEWBURN=1 BURNMENUPAUSE=1 
  MENU LABEL ^MANBURN    - Force a new burn (no menu timeout)
  MENU HIDE

LABEL cancelburn
  KERNEL vmlinuz
  IPAPPEND 3
  APPEND initrd=initrd CMDS rdblacklist=nouveau CMDE CANCELBURN=1
  MENU LABEL ^CANCELBURN - Cancel the current burn
  MENU HIDE

LABEL RESCUE
  KERNEL kernel.rescue
  MENU LABEL ^RESCUE     - Start rescue environment
  APPEND vga=normal initrd=rescue.rootfs.cgz root=/dev/ram0 rw nokeymap

LABEL localdrive
  MENU LABEL ^DRIVE      - Boot from first hard drive
  KERNEL chain.c32
  APPEND hd0

LABEL MEMTEST
  KERNEL memtest
  MENU LABEL MEM^TEST    - Start Memtest86

LABEL MEMPLUS
  KERNEL memtestplus
  MENU LABEL MEM^PLUS    - Start Memtest86+

INCLUDE bios/menu.conf
INCLUDE mpxe/minstall.conf

DEFAULT menu.c32
PROMPT 0
TIMEOUT 50
MENU TITLE Cluster Manager PXE Environment
MENU BACKGROUND bootlogo.png
MENU COLOR sel          7;37;40    #ff94cc31 #ff303030 all
MENU COLOR hotsel       1;7;37;40  #ff94cc31 #ff303030 all
MENU COLOR unsel        37;44      #ff78af00 #00000000 std
MENU COLOR hotkey       1;37;44    #ff94cc31 #00000000 std
MENU COLOR border       30;44      #ff78af00 #00000000 std
MENU COLOR title        1;36;44    #ff78af00 #00000000 std
MENU COLOR tabmsg       31;40      #ff78af00 #00000000 std


[-- Attachment #3: dhcp.txt --]
[-- Type: text/plain, Size: 10181 bytes --]

[root@node002 ~]# tcpdump -vv -i br0 udp
tcpdump: listening on br0, link-type EN10MB (Ethernet), capture size 65535 bytes
17:39:24.212593 IP (tos 0x0, ttl 64, id 1, offset 0, flags [none], proto UDP (17), length 415)
    0.0.0.0.bootpc > 255.255.255.255.bootps: [udp sum ok] BOOTP/DHCP, Request from 00:00:00:00:00:0d (oui Ethernet), length 387, xid 0xd, Flags [none] (0x0000)
	  Client-Ethernet-Address 00:00:00:00:00:0d (oui Ethernet)
	  Vendor-rfc1048 Extensions
	    Magic Cookie 0x63825363
	    GUID Option 97, length 17: 0.79.3.176.155.232.52.187.243.166.194.22.137.243.21.110.242
	    Client-ID Option 61, length 7: ether 00:00:00:00:00:0d
	    T175 Option 175, length 45: 177.5.1.16.236.129.57.19.1.1.23.1.1.21.1.1.24.1.1.35.1.1.34.1.1.25.1.1.33.1.1.16.1.2.18.1.1.17.1.1.235.3.0.9.7
	    DHCP-Message Option 53, length 1: Discover
	    MSZ Option 57, length 2: 1472
	    ARCH Option 93, length 2: 0
	    NDI Option 94, length 3: 1.2.1
	    Vendor-Class Option 60, length 32: "PXEClient:Arch:00000:UNDI:002001"
	    CLASS Option 77, length 4: "gPXE"
	    Parameter-Request Option 55, length 13: 
	      Subnet-Mask, Default-Gateway, Domain-Name-Server, LOG
	      Hostname, Domain-Name, RP, Vendor-Option
	      Vendor-Class, TFTP, BF, Option 175
	      Option 203
17:39:24.212659 IP (tos 0x0, ttl 64, id 1, offset 0, flags [none], proto UDP (17), length 415)
    0.0.0.0.bootpc > 255.255.255.255.bootps: [udp sum ok] BOOTP/DHCP, Request from 00:00:00:00:00:0d (oui Ethernet), length 387, xid 0xd, Flags [none] (0x0000)
	  Client-Ethernet-Address 00:00:00:00:00:0d (oui Ethernet)
	  Vendor-rfc1048 Extensions
	    Magic Cookie 0x63825363
	    GUID Option 97, length 17: 0.79.3.176.155.232.52.187.243.166.194.22.137.243.21.110.242
	    Client-ID Option 61, length 7: ether 00:00:00:00:00:0d
	    T175 Option 175, length 45: 177.5.1.16.236.129.57.19.1.1.23.1.1.21.1.1.24.1.1.35.1.1.34.1.1.25.1.1.33.1.1.16.1.2.18.1.1.17.1.1.235.3.0.9.7
	    DHCP-Message Option 53, length 1: Discover
	    MSZ Option 57, length 2: 1472
	    ARCH Option 93, length 2: 0
	    NDI Option 94, length 3: 1.2.1
	    Vendor-Class Option 60, length 32: "PXEClient:Arch:00000:UNDI:002001"
	    CLASS Option 77, length 4: "gPXE"
	    Parameter-Request Option 55, length 13: 
	      Subnet-Mask, Default-Gateway, Domain-Name-Server, LOG
	      Hostname, Domain-Name, RP, Vendor-Option
	      Vendor-Class, TFTP, BF, Option 175
	      Option 203
17:39:24.212913 IP (tos 0x0, ttl 64, id 0, offset 0, flags [DF], proto UDP (17), length 388)
    master.cm.cluster.bootps > 255.255.255.255.bootpc: [udp sum ok] BOOTP/DHCP, Reply, length 360, xid 0xd, Flags [none] (0x0000)
	  Your-IP vm001.cm.cluster
	  Server-IP master.cm.cluster
	  Client-Ethernet-Address 00:00:00:00:00:0d (oui Ethernet)
	  file "cm-images/default-image/boot/pxelinux.0"
	  Vendor-rfc1048 Extensions
	    Magic Cookie 0x63825363
	    DHCP-Message Option 53, length 1: Offer
	    Server-ID Option 54, length 4: master.cm.cluster
	    Lease-Time Option 51, length 4: 86400
	    Subnet-Mask Option 1, length 4: 255.255.0.0
	    Default-Gateway Option 3, length 4: master.cm.cluster
	    Domain-Name-Server Option 6, length 4: master.cm.cluster
	    Hostname Option 12, length 17: "vm001.internalnet"
	    Domain-Name Option 15, length 65: "eth.cluster brightcomputing.com ib.cluster ilo.cluster cm.cluster"
17:39:25.178728 IP (tos 0x0, ttl 64, id 2, offset 0, flags [none], proto UDP (17), length 415)
    0.0.0.0.bootpc > 255.255.255.255.bootps: [udp sum ok] BOOTP/DHCP, Request from 00:00:00:00:00:0d (oui Ethernet), length 387, xid 0xd, Flags [none] (0x0000)
	  Client-Ethernet-Address 00:00:00:00:00:0d (oui Ethernet)
	  Vendor-rfc1048 Extensions
	    Magic Cookie 0x63825363
	    GUID Option 97, length 17: 0.79.3.176.155.232.52.187.243.166.194.22.137.243.21.110.242
	    Client-ID Option 61, length 7: ether 00:00:00:00:00:0d
	    T175 Option 175, length 45: 177.5.1.16.236.129.57.19.1.1.23.1.1.21.1.1.24.1.1.35.1.1.34.1.1.25.1.1.33.1.1.16.1.2.18.1.1.17.1.1.235.3.0.9.7
	    DHCP-Message Option 53, length 1: Discover
	    MSZ Option 57, length 2: 1472
	    ARCH Option 93, length 2: 0
	    NDI Option 94, length 3: 1.2.1
	    Vendor-Class Option 60, length 32: "PXEClient:Arch:00000:UNDI:002001"
	    CLASS Option 77, length 4: "gPXE"
	    Parameter-Request Option 55, length 13: 
	      Subnet-Mask, Default-Gateway, Domain-Name-Server, LOG
	      Hostname, Domain-Name, RP, Vendor-Option
	      Vendor-Class, TFTP, BF, Option 175
	      Option 203
17:39:25.178784 IP (tos 0x0, ttl 64, id 2, offset 0, flags [none], proto UDP (17), length 415)
    0.0.0.0.bootpc > 255.255.255.255.bootps: [udp sum ok] BOOTP/DHCP, Request from 00:00:00:00:00:0d (oui Ethernet), length 387, xid 0xd, Flags [none] (0x0000)
	  Client-Ethernet-Address 00:00:00:00:00:0d (oui Ethernet)
	  Vendor-rfc1048 Extensions
	    Magic Cookie 0x63825363
	    GUID Option 97, length 17: 0.79.3.176.155.232.52.187.243.166.194.22.137.243.21.110.242
	    Client-ID Option 61, length 7: ether 00:00:00:00:00:0d
	    T175 Option 175, length 45: 177.5.1.16.236.129.57.19.1.1.23.1.1.21.1.1.24.1.1.35.1.1.34.1.1.25.1.1.33.1.1.16.1.2.18.1.1.17.1.1.235.3.0.9.7
	    DHCP-Message Option 53, length 1: Discover
	    MSZ Option 57, length 2: 1472
	    ARCH Option 93, length 2: 0
	    NDI Option 94, length 3: 1.2.1
	    Vendor-Class Option 60, length 32: "PXEClient:Arch:00000:UNDI:002001"
	    CLASS Option 77, length 4: "gPXE"
	    Parameter-Request Option 55, length 13: 
	      Subnet-Mask, Default-Gateway, Domain-Name-Server, LOG
	      Hostname, Domain-Name, RP, Vendor-Option
	      Vendor-Class, TFTP, BF, Option 175
	      Option 203
17:39:25.179009 IP (tos 0x0, ttl 64, id 0, offset 0, flags [DF], proto UDP (17), length 388)
    master.cm.cluster.bootps > 255.255.255.255.bootpc: [udp sum ok] BOOTP/DHCP, Reply, length 360, xid 0xd, Flags [none] (0x0000)
	  Your-IP vm001.cm.cluster
	  Server-IP master.cm.cluster
	  Client-Ethernet-Address 00:00:00:00:00:0d (oui Ethernet)
	  file "cm-images/default-image/boot/pxelinux.0"
	  Vendor-rfc1048 Extensions
	    Magic Cookie 0x63825363
	    DHCP-Message Option 53, length 1: Offer
	    Server-ID Option 54, length 4: master.cm.cluster
	    Lease-Time Option 51, length 4: 86400
	    Subnet-Mask Option 1, length 4: 255.255.0.0
	    Default-Gateway Option 3, length 4: master.cm.cluster
	    Domain-Name-Server Option 6, length 4: master.cm.cluster
	    Hostname Option 12, length 17: "vm001.internalnet"
	    Domain-Name Option 15, length 65: "eth.cluster brightcomputing.com ib.cluster ilo.cluster cm.cluster"
17:39:27.156065 IP (tos 0x0, ttl 64, id 3, offset 0, flags [none], proto UDP (17), length 427)
    0.0.0.0.bootpc > 255.255.255.255.bootps: [udp sum ok] BOOTP/DHCP, Request from 00:00:00:00:00:0d (oui Ethernet), length 399, xid 0xd, Flags [none] (0x0000)
	  Client-Ethernet-Address 00:00:00:00:00:0d (oui Ethernet)
	  Vendor-rfc1048 Extensions
	    Magic Cookie 0x63825363
	    Requested-IP Option 50, length 4: vm001.cm.cluster
	    Server-ID Option 54, length 4: master.cm.cluster
	    GUID Option 97, length 17: 0.79.3.176.155.232.52.187.243.166.194.22.137.243.21.110.242
	    Client-ID Option 61, length 7: ether 00:00:00:00:00:0d
	    T175 Option 175, length 45: 177.5.1.16.236.129.57.19.1.1.23.1.1.21.1.1.24.1.1.35.1.1.34.1.1.25.1.1.33.1.1.16.1.2.18.1.1.17.1.1.235.3.0.9.7
	    DHCP-Message Option 53, length 1: Request
	    MSZ Option 57, length 2: 1472
	    ARCH Option 93, length 2: 0
	    NDI Option 94, length 3: 1.2.1
	    Vendor-Class Option 60, length 32: "PXEClient:Arch:00000:UNDI:002001"
	    CLASS Option 77, length 4: "gPXE"
	    Parameter-Request Option 55, length 13: 
	      Subnet-Mask, Default-Gateway, Domain-Name-Server, LOG
	      Hostname, Domain-Name, RP, Vendor-Option
	      Vendor-Class, TFTP, BF, Option 175
	      Option 203
17:39:27.156121 IP (tos 0x0, ttl 64, id 3, offset 0, flags [none], proto UDP (17), length 427)
    0.0.0.0.bootpc > 255.255.255.255.bootps: [udp sum ok] BOOTP/DHCP, Request from 00:00:00:00:00:0d (oui Ethernet), length 399, xid 0xd, Flags [none] (0x0000)
	  Client-Ethernet-Address 00:00:00:00:00:0d (oui Ethernet)
	  Vendor-rfc1048 Extensions
	    Magic Cookie 0x63825363
	    Requested-IP Option 50, length 4: vm001.cm.cluster
	    Server-ID Option 54, length 4: master.cm.cluster
	    GUID Option 97, length 17: 0.79.3.176.155.232.52.187.243.166.194.22.137.243.21.110.242
	    Client-ID Option 61, length 7: ether 00:00:00:00:00:0d
	    T175 Option 175, length 45: 177.5.1.16.236.129.57.19.1.1.23.1.1.21.1.1.24.1.1.35.1.1.34.1.1.25.1.1.33.1.1.16.1.2.18.1.1.17.1.1.235.3.0.9.7
	    DHCP-Message Option 53, length 1: Request
	    MSZ Option 57, length 2: 1472
	    ARCH Option 93, length 2: 0
	    NDI Option 94, length 3: 1.2.1
	    Vendor-Class Option 60, length 32: "PXEClient:Arch:00000:UNDI:002001"
	    CLASS Option 77, length 4: "gPXE"
	    Parameter-Request Option 55, length 13: 
	      Subnet-Mask, Default-Gateway, Domain-Name-Server, LOG
	      Hostname, Domain-Name, RP, Vendor-Option
	      Vendor-Class, TFTP, BF, Option 175
	      Option 203
17:39:27.156373 IP (tos 0x0, ttl 64, id 0, offset 0, flags [DF], proto UDP (17), length 388)
    master.cm.cluster.bootps > 255.255.255.255.bootpc: [udp sum ok] BOOTP/DHCP, Reply, length 360, xid 0xd, Flags [none] (0x0000)
	  Your-IP vm001.cm.cluster
	  Server-IP master.cm.cluster
	  Client-Ethernet-Address 00:00:00:00:00:0d (oui Ethernet)
	  file "cm-images/default-image/boot/pxelinux.0"
	  Vendor-rfc1048 Extensions
	    Magic Cookie 0x63825363
	    DHCP-Message Option 53, length 1: ACK
	    Server-ID Option 54, length 4: master.cm.cluster
	    Lease-Time Option 51, length 4: 86400
	    Subnet-Mask Option 1, length 4: 255.255.0.0
	    Default-Gateway Option 3, length 4: master.cm.cluster
	    Domain-Name-Server Option 6, length 4: master.cm.cluster
	    Hostname Option 12, length 17: "vm001.internalnet"
	    Domain-Name Option 15, length 65: "eth.cluster brightcomputing.com ib.cluster ilo.cluster cm.cluster"

^ permalink raw reply	[flat|nested] 14+ messages in thread

* Re: [libvirt-users] vm pxe fail
  2012-08-17  2:34 ` [libvirt-users] " Alex Jia
  2012-08-17  8:24   ` Andrew Holway
@ 2012-08-20 17:47   ` Andrew Holway
  2012-08-31 13:32   ` Andrew Holway
  2 siblings, 0 replies; 14+ messages in thread
From: Andrew Holway @ 2012-08-20 17:47 UTC (permalink / raw)
  To: kvm

I had SR-IOV enabled on the interface card. This was breaking it.

The card is a:   Ethernet controller: Emulex Corporation OneConnect 10Gb NIC (be3) (rev 01)

On Aug 17, 2012, at 4:34 AM, Alex Jia wrote:

> Hi Andrew,
> I can't confirm a root reason based on your information, perhaps you may
> try to find a reason by yourself via the following docs:
> 
> http://wiki.libvirt.org/page/PXE_boot_%28or_dhcp%29_on_guest_failed  (Troubleshooting)
> http://docs.fedoraproject.org/en-US/Fedora/13/html/Virtualization_Guide/sect-Virtualization-Virtualized_guest_installation_overview-Installing_guests_with_PXE.html  (User Guide)
> 
> If can't, please provide your version of kvm, libvirt, tftp, etc, and run 'virsh net-dumpxml br0' to dump your
> network bridge XML configuration, and run 'cat pxelinux.cfg' to show your pxelinux configuration, thanks.
> 
> -- 
> Regards,     
> Alex
> 
> 
> ----- Original Message -----
> From: "Andrew Holway" <a.holway@syseleven.de>
> To: kvm@vger.kernel.org
> Sent: Thursday, August 16, 2012 8:25:35 PM
> Subject: [libvirt-users] vm pxe fail
> 
> Hallo
> 
> I have a kvm vm that I am attempting to boot from pxe. The dhcp works perfectly and I can see the VM in the pxe server arp. but the tftp just times out. I don't see any tftp traffic on either the physical host or on the pie server. I am using a bridged interface. I have tried using several virtual nic drivers, several different mac addresses and several different ips.  on the physical host I can get the pxelinux.0 file from the pxe server via tftp and can clearly see that traffic with tcpdump.
> 
> Ive tried using various virtual interfaces.
> 
> I can pxe boot my physical hosts with no problems.
> 
> I can tftp fine from the physical host and see the traffic with ethdump
> 
> Here is the terminal output from the VM: https://dl.dropbox.com/u/98200887/Screen%20Shot%202012-08-15%20at%206.41.12%20PM.png
> 
> Thanks,
> 
> Andrew
> 
> [root@node002 ~]# yum list | grep qemu
> gpxe-roms-qemu.noarch                   0.9.7-6.9.el6               @base       
> qemu-img.x86_64                         2:0.12.1.2-2.295.el6_3.1    @updates    
> qemu-kvm.x86_64                         2:0.12.1.2-2.295.el6_3.1    @updates    
> qemu-guest-agent.x86_64                 2:0.12.1.2-2.295.el6_3.1    updates     
> qemu-kvm-tools.x86_64                   2:0.12.1.2-2.295.el6_3.1    updates 
> 
> [root@node002 ~]# ethtool eth0
> Settings for eth0:
> 	Supported ports: [ TP ]
> 	Supported link modes:   10000baseT/Full 
> 	Supports auto-negotiation: No
> 	Advertised link modes:  10000baseT/Full 
> 	Advertised pause frame use: No
> 	Advertised auto-negotiation: No
> 	Speed: Unknown!
> 	Duplex: Unknown! (255)
> 	Port: Twisted Pair
> 	PHYAD: 0
> 	Transceiver: internal
> 	Auto-negotiation: off
> 	MDI-X: Unknown
> 	Supports Wake-on: g
> 	Wake-on: g
> 	Current message level: 0x00000014 (20)
> 	Link detected: no
> 
> [root@node002 ~]# brctl show
> bridge name	bridge id		STP enabled	interfaces
> br0		8000.009c02241ae0	no		eth1
> 							vnet0
> virbr0		8000.525400a6d5aa	yes		virbr0-nic
> 
> [root@node002 ~]# ethtool vnet0
> Settings for vnet0:
> 	Supported ports: [ ]
> 	Supported link modes:   
> 	Supports auto-negotiation: No
> 	Advertised link modes:  Not reported
> 	Advertised pause frame use: No
> 	Advertised auto-negotiation: No
> 	Speed: 10Mb/s
> 	Duplex: Full
> 	Port: Twisted Pair
> 	PHYAD: 0
> 	Transceiver: internal
> 	Auto-negotiation: off
> 	MDI-X: Unknown
> 	Current message level: 0xffffffa1 (-95)
> 	Link detected: yes
> 
> <domain type='kvm'>
> <name>vm004</name>
> <uuid>4f03b09b-e834-bbf3-a6c2-1689f3156ef2</uuid>
> <memory unit='KiB'>2097152</memory>
> <currentMemory unit='KiB'>2097152</currentMemory>
> <vcpu placement='static'>2</vcpu>
> <os>
>   <type arch='x86_64' machine='rhel6.3.0'>hvm</type>
>   <boot dev='hd'/>
> </os>
> <features>
>   <acpi/>
>   <apic/>
>   <pae/>
> </features>
> <clock offset='utc'/>
> <on_poweroff>destroy</on_poweroff>
> <on_reboot>restart</on_reboot>
> <on_crash>restart</on_crash>
> <devices>
>   <emulator>/usr/libexec/qemu-kvm</emulator>
>   <disk type='file' device='disk'>
>     <driver name='qemu' type='raw' cache='none'/>
>     <source file='/cm/shared/vm/vm004.img'/>
>     <target dev='hda' bus='ide'/>
>     <address type='drive' controller='0' bus='0' target='0' unit='0'/>
>   </disk>
>   <disk type='block' device='cdrom'>
>     <driver name='qemu' type='raw'/>
>     <target dev='hdc' bus='ide'/>
>     <readonly/>
>     <address type='drive' controller='0' bus='1' target='0' unit='0'/>
>   </disk>
>   <controller type='usb' index='0'>
>     <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x2'/>
>   </controller>
>   <controller type='ide' index='0'>
>     <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x1'/>
>   </controller>
>   <interface type='bridge'>
>     <mac address='00:00:00:00:00:0d'/>
>     <source bridge='br0'/>
>     <model type='rtl8139'/>
>     <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/>
>   </interface>
>   <serial type='pty'>
>     <target port='0'/>
>   </serial>
>   <console type='pty'>
>     <target type='serial' port='0'/>
>   </console>
>   <input type='mouse' bus='ps2'/>
>   <graphics type='vnc' port='-1' autoport='yes'/>
>   <video>
>     <model type='cirrus' vram='9216' heads='1'/>
>     <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0'/>
>   </video>
>   <memballoon model='virtio'>
>     <address type='pci' domain='0x0000' bus='0x00' slot='0x04' function='0x0'/>
>   </memballoon>
> </devices>
> </domain>
> 
> 
> 
> _______________________________________________
> libvirt-users mailing list
> libvirt-users@redhat.com
> https://www.redhat.com/mailman/listinfo/libvirt-users



^ permalink raw reply	[flat|nested] 14+ messages in thread

* Re: [libvirt-users] vm pxe fail
  2012-08-17  2:34 ` [libvirt-users] " Alex Jia
  2012-08-17  8:24   ` Andrew Holway
  2012-08-20 17:47   ` Andrew Holway
@ 2012-08-31 13:32   ` Andrew Holway
  2012-08-31 14:37     ` Alex Jia
  2 siblings, 1 reply; 14+ messages in thread
From: Andrew Holway @ 2012-08-31 13:32 UTC (permalink / raw)
  To: Alex Jia; +Cc: kvm

Hi,

In the end the problem was SR-IOV enabled on the cards. I turned this off and everything worked ok.

Im using HP 10G cards which are rebranded emulex.

0a:00.0 Ethernet controller: Emulex Corporation OneConnect 10Gb NIC (be3) (rev 01)

Thanks,

Andrew

On Aug 17, 2012, at 4:34 AM, Alex Jia wrote:

> Hi Andrew,
> I can't confirm a root reason based on your information, perhaps you may
> try to find a reason by yourself via the following docs:
> 
> http://wiki.libvirt.org/page/PXE_boot_%28or_dhcp%29_on_guest_failed  (Troubleshooting)
> http://docs.fedoraproject.org/en-US/Fedora/13/html/Virtualization_Guide/sect-Virtualization-Virtualized_guest_installation_overview-Installing_guests_with_PXE.html  (User Guide)
> 
> If can't, please provide your version of kvm, libvirt, tftp, etc, and run 'virsh net-dumpxml br0' to dump your
> network bridge XML configuration, and run 'cat pxelinux.cfg' to show your pxelinux configuration, thanks.
> 
> -- 
> Regards,     
> Alex
> 
> 
> ----- Original Message -----
> From: "Andrew Holway" <a.holway@syseleven.de>
> To: kvm@vger.kernel.org
> Sent: Thursday, August 16, 2012 8:25:35 PM
> Subject: [libvirt-users] vm pxe fail
> 
> Hallo
> 
> I have a kvm vm that I am attempting to boot from pxe. The dhcp works perfectly and I can see the VM in the pxe server arp. but the tftp just times out. I don't see any tftp traffic on either the physical host or on the pie server. I am using a bridged interface. I have tried using several virtual nic drivers, several different mac addresses and several different ips.  on the physical host I can get the pxelinux.0 file from the pxe server via tftp and can clearly see that traffic with tcpdump.
> 
> Ive tried using various virtual interfaces.
> 
> I can pxe boot my physical hosts with no problems.
> 
> I can tftp fine from the physical host and see the traffic with ethdump
> 
> Here is the terminal output from the VM: https://dl.dropbox.com/u/98200887/Screen%20Shot%202012-08-15%20at%206.41.12%20PM.png
> 
> Thanks,
> 
> Andrew
> 
> [root@node002 ~]# yum list | grep qemu
> gpxe-roms-qemu.noarch                   0.9.7-6.9.el6               @base       
> qemu-img.x86_64                         2:0.12.1.2-2.295.el6_3.1    @updates    
> qemu-kvm.x86_64                         2:0.12.1.2-2.295.el6_3.1    @updates    
> qemu-guest-agent.x86_64                 2:0.12.1.2-2.295.el6_3.1    updates     
> qemu-kvm-tools.x86_64                   2:0.12.1.2-2.295.el6_3.1    updates 
> 
> [root@node002 ~]# ethtool eth0
> Settings for eth0:
> 	Supported ports: [ TP ]
> 	Supported link modes:   10000baseT/Full 
> 	Supports auto-negotiation: No
> 	Advertised link modes:  10000baseT/Full 
> 	Advertised pause frame use: No
> 	Advertised auto-negotiation: No
> 	Speed: Unknown!
> 	Duplex: Unknown! (255)
> 	Port: Twisted Pair
> 	PHYAD: 0
> 	Transceiver: internal
> 	Auto-negotiation: off
> 	MDI-X: Unknown
> 	Supports Wake-on: g
> 	Wake-on: g
> 	Current message level: 0x00000014 (20)
> 	Link detected: no
> 
> [root@node002 ~]# brctl show
> bridge name	bridge id		STP enabled	interfaces
> br0		8000.009c02241ae0	no		eth1
> 							vnet0
> virbr0		8000.525400a6d5aa	yes		virbr0-nic
> 
> [root@node002 ~]# ethtool vnet0
> Settings for vnet0:
> 	Supported ports: [ ]
> 	Supported link modes:   
> 	Supports auto-negotiation: No
> 	Advertised link modes:  Not reported
> 	Advertised pause frame use: No
> 	Advertised auto-negotiation: No
> 	Speed: 10Mb/s
> 	Duplex: Full
> 	Port: Twisted Pair
> 	PHYAD: 0
> 	Transceiver: internal
> 	Auto-negotiation: off
> 	MDI-X: Unknown
> 	Current message level: 0xffffffa1 (-95)
> 	Link detected: yes
> 
> <domain type='kvm'>
> <name>vm004</name>
> <uuid>4f03b09b-e834-bbf3-a6c2-1689f3156ef2</uuid>
> <memory unit='KiB'>2097152</memory>
> <currentMemory unit='KiB'>2097152</currentMemory>
> <vcpu placement='static'>2</vcpu>
> <os>
>   <type arch='x86_64' machine='rhel6.3.0'>hvm</type>
>   <boot dev='hd'/>
> </os>
> <features>
>   <acpi/>
>   <apic/>
>   <pae/>
> </features>
> <clock offset='utc'/>
> <on_poweroff>destroy</on_poweroff>
> <on_reboot>restart</on_reboot>
> <on_crash>restart</on_crash>
> <devices>
>   <emulator>/usr/libexec/qemu-kvm</emulator>
>   <disk type='file' device='disk'>
>     <driver name='qemu' type='raw' cache='none'/>
>     <source file='/cm/shared/vm/vm004.img'/>
>     <target dev='hda' bus='ide'/>
>     <address type='drive' controller='0' bus='0' target='0' unit='0'/>
>   </disk>
>   <disk type='block' device='cdrom'>
>     <driver name='qemu' type='raw'/>
>     <target dev='hdc' bus='ide'/>
>     <readonly/>
>     <address type='drive' controller='0' bus='1' target='0' unit='0'/>
>   </disk>
>   <controller type='usb' index='0'>
>     <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x2'/>
>   </controller>
>   <controller type='ide' index='0'>
>     <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x1'/>
>   </controller>
>   <interface type='bridge'>
>     <mac address='00:00:00:00:00:0d'/>
>     <source bridge='br0'/>
>     <model type='rtl8139'/>
>     <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/>
>   </interface>
>   <serial type='pty'>
>     <target port='0'/>
>   </serial>
>   <console type='pty'>
>     <target type='serial' port='0'/>
>   </console>
>   <input type='mouse' bus='ps2'/>
>   <graphics type='vnc' port='-1' autoport='yes'/>
>   <video>
>     <model type='cirrus' vram='9216' heads='1'/>
>     <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0'/>
>   </video>
>   <memballoon model='virtio'>
>     <address type='pci' domain='0x0000' bus='0x00' slot='0x04' function='0x0'/>
>   </memballoon>
> </devices>
> </domain>
> 
> 
> 
> _______________________________________________
> libvirt-users mailing list
> libvirt-users@redhat.com
> https://www.redhat.com/mailman/listinfo/libvirt-users



^ permalink raw reply	[flat|nested] 14+ messages in thread

* Re: [libvirt-users] vm pxe fail
  2012-08-31 13:32   ` Andrew Holway
@ 2012-08-31 14:37     ` Alex Jia
  2012-09-03 13:27       ` Avi Kivity
  0 siblings, 1 reply; 14+ messages in thread
From: Alex Jia @ 2012-08-31 14:37 UTC (permalink / raw)
  To: Andrew Holway; +Cc: kvm

Hi Andrew,
Great, BTW, in fact, you may pxe boot via VF of Intel82576, however, Intel82576 SR-IOV network adapters 
don't provide a ROM BIOS for the cards virtual functions (VF), but an image of such a ROM is available, 
and with this ROM visible to the guest, it can PXE boot.

In libvirt's xml, you need to configure guest XML like this:

          <hostdev mode='subsystem' type='pci' managed='yes'>
            <source>
              <address bus='XX' slot='XX' function='XX'/>
            </source>         
            <boot order='1'/>         
           <rom bar='on' file='/xxxx/ipxe-808610ca.rom'/>
          </hostdev>

You need to build a ipxe-808610ca.rom by yourself, if you're interested in this,
please refer to http://ipxe.org/.
 

-- 
Regards,     
Alex


----- Original Message -----
From: "Andrew Holway" <a.holway@syseleven.de>
To: "Alex Jia" <ajia@redhat.com>
Cc: kvm@vger.kernel.org
Sent: Friday, August 31, 2012 9:32:24 PM
Subject: Re: [libvirt-users] vm pxe fail

Hi,

In the end the problem was SR-IOV enabled on the cards. I turned this off and everything worked ok.

Im using HP 10G cards which are rebranded emulex.

0a:00.0 Ethernet controller: Emulex Corporation OneConnect 10Gb NIC (be3) (rev 01)

Thanks,

Andrew

On Aug 17, 2012, at 4:34 AM, Alex Jia wrote:

> Hi Andrew,
> I can't confirm a root reason based on your information, perhaps you may
> try to find a reason by yourself via the following docs:
> 
> http://wiki.libvirt.org/page/PXE_boot_%28or_dhcp%29_on_guest_failed  (Troubleshooting)
> http://docs.fedoraproject.org/en-US/Fedora/13/html/Virtualization_Guide/sect-Virtualization-Virtualized_guest_installation_overview-Installing_guests_with_PXE.html  (User Guide)
> 
> If can't, please provide your version of kvm, libvirt, tftp, etc, and run 'virsh net-dumpxml br0' to dump your
> network bridge XML configuration, and run 'cat pxelinux.cfg' to show your pxelinux configuration, thanks.
> 
> -- 
> Regards,     
> Alex
> 
> 
> ----- Original Message -----
> From: "Andrew Holway" <a.holway@syseleven.de>
> To: kvm@vger.kernel.org
> Sent: Thursday, August 16, 2012 8:25:35 PM
> Subject: [libvirt-users] vm pxe fail
> 
> Hallo
> 
> I have a kvm vm that I am attempting to boot from pxe. The dhcp works perfectly and I can see the VM in the pxe server arp. but the tftp just times out. I don't see any tftp traffic on either the physical host or on the pie server. I am using a bridged interface. I have tried using several virtual nic drivers, several different mac addresses and several different ips.  on the physical host I can get the pxelinux.0 file from the pxe server via tftp and can clearly see that traffic with tcpdump.
> 
> Ive tried using various virtual interfaces.
> 
> I can pxe boot my physical hosts with no problems.
> 
> I can tftp fine from the physical host and see the traffic with ethdump
> 
> Here is the terminal output from the VM: https://dl.dropbox.com/u/98200887/Screen%20Shot%202012-08-15%20at%206.41.12%20PM.png
> 
> Thanks,
> 
> Andrew
> 
> [root@node002 ~]# yum list | grep qemu
> gpxe-roms-qemu.noarch                   0.9.7-6.9.el6               @base       
> qemu-img.x86_64                         2:0.12.1.2-2.295.el6_3.1    @updates    
> qemu-kvm.x86_64                         2:0.12.1.2-2.295.el6_3.1    @updates    
> qemu-guest-agent.x86_64                 2:0.12.1.2-2.295.el6_3.1    updates     
> qemu-kvm-tools.x86_64                   2:0.12.1.2-2.295.el6_3.1    updates 
> 
> [root@node002 ~]# ethtool eth0
> Settings for eth0:
> 	Supported ports: [ TP ]
> 	Supported link modes:   10000baseT/Full 
> 	Supports auto-negotiation: No
> 	Advertised link modes:  10000baseT/Full 
> 	Advertised pause frame use: No
> 	Advertised auto-negotiation: No
> 	Speed: Unknown!
> 	Duplex: Unknown! (255)
> 	Port: Twisted Pair
> 	PHYAD: 0
> 	Transceiver: internal
> 	Auto-negotiation: off
> 	MDI-X: Unknown
> 	Supports Wake-on: g
> 	Wake-on: g
> 	Current message level: 0x00000014 (20)
> 	Link detected: no
> 
> [root@node002 ~]# brctl show
> bridge name	bridge id		STP enabled	interfaces
> br0		8000.009c02241ae0	no		eth1
> 							vnet0
> virbr0		8000.525400a6d5aa	yes		virbr0-nic
> 
> [root@node002 ~]# ethtool vnet0
> Settings for vnet0:
> 	Supported ports: [ ]
> 	Supported link modes:   
> 	Supports auto-negotiation: No
> 	Advertised link modes:  Not reported
> 	Advertised pause frame use: No
> 	Advertised auto-negotiation: No
> 	Speed: 10Mb/s
> 	Duplex: Full
> 	Port: Twisted Pair
> 	PHYAD: 0
> 	Transceiver: internal
> 	Auto-negotiation: off
> 	MDI-X: Unknown
> 	Current message level: 0xffffffa1 (-95)
> 	Link detected: yes
> 
> <domain type='kvm'>
> <name>vm004</name>
> <uuid>4f03b09b-e834-bbf3-a6c2-1689f3156ef2</uuid>
> <memory unit='KiB'>2097152</memory>
> <currentMemory unit='KiB'>2097152</currentMemory>
> <vcpu placement='static'>2</vcpu>
> <os>
>   <type arch='x86_64' machine='rhel6.3.0'>hvm</type>
>   <boot dev='hd'/>
> </os>
> <features>
>   <acpi/>
>   <apic/>
>   <pae/>
> </features>
> <clock offset='utc'/>
> <on_poweroff>destroy</on_poweroff>
> <on_reboot>restart</on_reboot>
> <on_crash>restart</on_crash>
> <devices>
>   <emulator>/usr/libexec/qemu-kvm</emulator>
>   <disk type='file' device='disk'>
>     <driver name='qemu' type='raw' cache='none'/>
>     <source file='/cm/shared/vm/vm004.img'/>
>     <target dev='hda' bus='ide'/>
>     <address type='drive' controller='0' bus='0' target='0' unit='0'/>
>   </disk>
>   <disk type='block' device='cdrom'>
>     <driver name='qemu' type='raw'/>
>     <target dev='hdc' bus='ide'/>
>     <readonly/>
>     <address type='drive' controller='0' bus='1' target='0' unit='0'/>
>   </disk>
>   <controller type='usb' index='0'>
>     <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x2'/>
>   </controller>
>   <controller type='ide' index='0'>
>     <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x1'/>
>   </controller>
>   <interface type='bridge'>
>     <mac address='00:00:00:00:00:0d'/>
>     <source bridge='br0'/>
>     <model type='rtl8139'/>
>     <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/>
>   </interface>
>   <serial type='pty'>
>     <target port='0'/>
>   </serial>
>   <console type='pty'>
>     <target type='serial' port='0'/>
>   </console>
>   <input type='mouse' bus='ps2'/>
>   <graphics type='vnc' port='-1' autoport='yes'/>
>   <video>
>     <model type='cirrus' vram='9216' heads='1'/>
>     <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0'/>
>   </video>
>   <memballoon model='virtio'>
>     <address type='pci' domain='0x0000' bus='0x00' slot='0x04' function='0x0'/>
>   </memballoon>
> </devices>
> </domain>
> 
> 
> 
> _______________________________________________
> libvirt-users mailing list
> libvirt-users@redhat.com
> https://www.redhat.com/mailman/listinfo/libvirt-users



^ permalink raw reply	[flat|nested] 14+ messages in thread

* Re: [libvirt-users] vm pxe fail
  2012-08-31 14:37     ` Alex Jia
@ 2012-09-03 13:27       ` Avi Kivity
  2012-09-04 11:31         ` Alex Jia
  0 siblings, 1 reply; 14+ messages in thread
From: Avi Kivity @ 2012-09-03 13:27 UTC (permalink / raw)
  To: Alex Jia; +Cc: Andrew Holway, kvm

On 08/31/2012 05:37 PM, Alex Jia wrote:
> Hi Andrew,
> Great, BTW, in fact, you may pxe boot via VF of Intel82576, however, Intel82576 SR-IOV network adapters 
> don't provide a ROM BIOS for the cards virtual functions (VF), but an image of such a ROM is available, 
> and with this ROM visible to the guest, it can PXE boot.
> 
> In libvirt's xml, you need to configure guest XML like this:
> 
>           <hostdev mode='subsystem' type='pci' managed='yes'>
>             <source>
>               <address bus='XX' slot='XX' function='XX'/>
>             </source>         
>             <boot order='1'/>         
>            <rom bar='on' file='/xxxx/ipxe-808610ca.rom'/>
>           </hostdev>
> 
> You need to build a ipxe-808610ca.rom by yourself, if you're interested in this,
> please refer to http://ipxe.org/.

Is there a way to automate this?  Perhaps a database matching PCI IDs
and ipxe .roms, which qemu could consult?


-- 
error compiling committee.c: too many arguments to function

^ permalink raw reply	[flat|nested] 14+ messages in thread

* Re: [libvirt-users] vm pxe fail
  2012-09-03 13:27       ` Avi Kivity
@ 2012-09-04 11:31         ` Alex Jia
  2012-09-04 11:44           ` Avi Kivity
  0 siblings, 1 reply; 14+ messages in thread
From: Alex Jia @ 2012-09-04 11:31 UTC (permalink / raw)
  To: Avi Kivity; +Cc: Andrew Holway, kvm

----- Original Message -----
From: "Avi Kivity" <avi@redhat.com>
To: "Alex Jia" <ajia@redhat.com>
Cc: "Andrew Holway" <a.holway@syseleven.de>, kvm@vger.kernel.org
Sent: Monday, September 3, 2012 9:27:08 PM
Subject: Re: [libvirt-users] vm pxe fail

On 08/31/2012 05:37 PM, Alex Jia wrote:
> Hi Andrew,
> Great, BTW, in fact, you may pxe boot via VF of Intel82576, however, Intel82576 SR-IOV network adapters 
> don't provide a ROM BIOS for the cards virtual functions (VF), but an image of such a ROM is available, 
> and with this ROM visible to the guest, it can PXE boot.
> 
> In libvirt's xml, you need to configure guest XML like this:
> 
>           <hostdev mode='subsystem' type='pci' managed='yes'>
>             <source>
>               <address bus='XX' slot='XX' function='XX'/>
>             </source>         
>             <boot order='1'/>         
>            <rom bar='on' file='/xxxx/ipxe-808610ca.rom'/>
>           </hostdev>
> 
> You need to build a ipxe-808610ca.rom by yourself, if you're interested in this,
> please refer to http://ipxe.org/.

Is there a way to automate this?  Perhaps a database matching PCI IDs
and ipxe .roms, which qemu could consult?

   Hi Avi,
   Good question, I haven't try this via qemu yet, from libvirt POV, basically, we may filter and parse 'lspci'
   or 'virsh nodedev-list --tree' output to get a bus, slot and function number then add them into above guest
   XML, WRT above 'ipxe-808610ca.rom' file, we may directly 'git clone git://git.ipxe.org/ipxe.git' then compile
   it and generate a .rom file such as 82576.rom or use a vendor+product id as a rom name if you like.

   Regards,
   Alex

-- 
error compiling committee.c: too many arguments to function

^ permalink raw reply	[flat|nested] 14+ messages in thread

* Re: [libvirt-users] vm pxe fail
  2012-09-04 11:31         ` Alex Jia
@ 2012-09-04 11:44           ` Avi Kivity
  2012-09-04 14:47             ` Alex Jia
  0 siblings, 1 reply; 14+ messages in thread
From: Avi Kivity @ 2012-09-04 11:44 UTC (permalink / raw)
  To: Alex Jia; +Cc: Andrew Holway, kvm

On 09/04/2012 02:31 PM, Alex Jia wrote:
> ----- Original Message -----
> From: "Avi Kivity" <avi@redhat.com>
> To: "Alex Jia" <ajia@redhat.com>
> Cc: "Andrew Holway" <a.holway@syseleven.de>, kvm@vger.kernel.org
> Sent: Monday, September 3, 2012 9:27:08 PM
> Subject: Re: [libvirt-users] vm pxe fail
> 
> On 08/31/2012 05:37 PM, Alex Jia wrote:
>> Hi Andrew,
>> Great, BTW, in fact, you may pxe boot via VF of Intel82576, however, Intel82576 SR-IOV network adapters 
>> don't provide a ROM BIOS for the cards virtual functions (VF), but an image of such a ROM is available, 
>> and with this ROM visible to the guest, it can PXE boot.
>> 
>> In libvirt's xml, you need to configure guest XML like this:
>> 
>>           <hostdev mode='subsystem' type='pci' managed='yes'>
>>             <source>
>>               <address bus='XX' slot='XX' function='XX'/>
>>             </source>         
>>             <boot order='1'/>         
>>            <rom bar='on' file='/xxxx/ipxe-808610ca.rom'/>
>>           </hostdev>
>> 
>> You need to build a ipxe-808610ca.rom by yourself, if you're interested in this,
>> please refer to http://ipxe.org/.
> 
> Is there a way to automate this?  Perhaps a database matching PCI IDs
> and ipxe .roms, which qemu could consult?
> 
>    Hi Avi,
>    Good question, I haven't try this via qemu yet, from libvirt POV, basically, we may filter and parse 'lspci'
>    or 'virsh nodedev-list --tree' output to get a bus, slot and function number then add them into above guest
>    XML, WRT above 'ipxe-808610ca.rom' file, we may directly 'git clone git://git.ipxe.org/ipxe.git' then compile
>    it and generate a .rom file such as 82576.rom or use a vendor+product id as a rom name if you like.

We could have qemu autoload /usr/share/qemu/roms/vendor-device.rom, and
symlink /usr/share/qemu/roms to /usr/share/ipxe/roms or something.

-- 
error compiling committee.c: too many arguments to function

^ permalink raw reply	[flat|nested] 14+ messages in thread

* Re: [libvirt-users] vm pxe fail
  2012-09-04 11:44           ` Avi Kivity
@ 2012-09-04 14:47             ` Alex Jia
  0 siblings, 0 replies; 14+ messages in thread
From: Alex Jia @ 2012-09-04 14:47 UTC (permalink / raw)
  To: Avi Kivity; +Cc: Andrew Holway, kvm

----- Original Message -----
From: "Avi Kivity" <avi@redhat.com>
To: "Alex Jia" <ajia@redhat.com>
Cc: "Andrew Holway" <a.holway@syseleven.de>, kvm@vger.kernel.org
Sent: Tuesday, September 4, 2012 7:44:36 PM
Subject: Re: [libvirt-users] vm pxe fail

On 09/04/2012 02:31 PM, Alex Jia wrote:
> ----- Original Message -----
> From: "Avi Kivity" <avi@redhat.com>
> To: "Alex Jia" <ajia@redhat.com>
> Cc: "Andrew Holway" <a.holway@syseleven.de>, kvm@vger.kernel.org
> Sent: Monday, September 3, 2012 9:27:08 PM
> Subject: Re: [libvirt-users] vm pxe fail
> 
> On 08/31/2012 05:37 PM, Alex Jia wrote:
>> Hi Andrew,
>> Great, BTW, in fact, you may pxe boot via VF of Intel82576, however, Intel82576 SR-IOV network adapters 
>> don't provide a ROM BIOS for the cards virtual functions (VF), but an image of such a ROM is available, 
>> and with this ROM visible to the guest, it can PXE boot.
>> 
>> In libvirt's xml, you need to configure guest XML like this:
>> 
>>           <hostdev mode='subsystem' type='pci' managed='yes'>
>>             <source>
>>               <address bus='XX' slot='XX' function='XX'/>
>>             </source>         
>>             <boot order='1'/>         
>>            <rom bar='on' file='/xxxx/ipxe-808610ca.rom'/>
>>           </hostdev>
>> 
>> You need to build a ipxe-808610ca.rom by yourself, if you're interested in this,
>> please refer to http://ipxe.org/.
> 
> Is there a way to automate this?  Perhaps a database matching PCI IDs
> and ipxe .roms, which qemu could consult?
> 
>    Hi Avi,
>    Good question, I haven't try this via qemu yet, from libvirt POV, basically, we may filter and parse 'lspci'
>    or 'virsh nodedev-list --tree' output to get a bus, slot and function number then add them into above guest
>    XML, WRT above 'ipxe-808610ca.rom' file, we may directly 'git clone git://git.ipxe.org/ipxe.git' then compile
>    it and generate a .rom file such as 82576.rom or use a vendor+product id as a rom name if you like.

We could have qemu autoload /usr/share/qemu/roms/vendor-device.rom, and
symlink /usr/share/qemu/roms to /usr/share/ipxe/roms or something.

     Avi, good to know these, thanks :)
     

-- 
error compiling committee.c: too many arguments to function

^ permalink raw reply	[flat|nested] 14+ messages in thread

end of thread, other threads:[~2012-09-04 14:47 UTC | newest]

Thread overview: 14+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2012-08-16 12:25 vm pxe fail Andrew Holway
2012-08-16 13:54 ` Stefan Hajnoczi
2012-08-16 15:09   ` Andrew Holway
2012-08-16 15:35     ` Stefan Hajnoczi
2012-08-17  2:34 ` [libvirt-users] " Alex Jia
2012-08-17  8:24   ` Andrew Holway
2012-08-17  8:45     ` Fwd: " Alex Jia
2012-08-20 17:47   ` Andrew Holway
2012-08-31 13:32   ` Andrew Holway
2012-08-31 14:37     ` Alex Jia
2012-09-03 13:27       ` Avi Kivity
2012-09-04 11:31         ` Alex Jia
2012-09-04 11:44           ` Avi Kivity
2012-09-04 14:47             ` Alex Jia

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.