Question on Windows HVM Domain
by Robert Locke
Bit of a n00b question....
I am currently running F8-Dom0 with an HVM-based Windows XP DomU. I
tend to run it from virt-manager the occasional times I use it.
Given that F9-Dom0 support is still a work-in-progress, I started
reading about KVM existing in the "regular" kernel.
Since the Dom0 is my main "work" platform, I am considering upgrading to
F9, but, losing Xen.
The question becomes, can I run the existing Windows XP instance under
virt-manager via KVM? BTW, the disk for Windows XP is an LV, and I
would prefer to continue NAT'ing it to the outside, if that matters....
Some of the doc's on fedoraproject.org started identifying parity
between KVM and Qemu (which I thought is what is used for HVM)....
Am I totally insane, or on to a potential solution that lets me move my
Dom0 to F9?
Thanks for any pointers/help,
--Rob
15 years, 11 months
[ANNOUNCE] virt-df 2.1.0 - a 'df' tool for virtual guests
by Richard W.M. Jones
I'm pleased to announce the most recent release of virt-df (2.1.0).
Virt-df is 'df' for virtual guests. Run the program on the host / dom0
to display disk space used and available on all partitions on all
guests. You don't need to run any sort of program/agent within the
guest.
Home page: http://et.redhat.com/~rjones/virt-df/
Source/binaries: http://et.redhat.com/~rjones/virt-df/files/
Developer repository:
http://hg.et.redhat.com/virt/applications/virt-df--devel
This version supports most common filesystems and partitioning
schemes, including:
- Linux ext2/3
- DOS FAT32
- Windows NTFS
- Linux LVM2 (volume groups and logical volumes)
- Primary and extended disk partitions
- Linux swap
- Linux suspend partition
You can run it in your host / dom0 to display guest filesystems:
# virt-df -c qemu:///system -h
Filesystem Size Used Available Type
rhel51x32kvm:hda1 96.8 MiB 14.6 MiB 82.2 MiB Linux ext2/3
rhel51x32kvm:VolGroup00/LogVol00 6.4 GiB 3.6 GiB 2.8 GiB Linux ext2/3
rhel51x32kvm:VolGroup00/LogVol01 992.0 MiB Linux swap
You can also run it on general disk images, or disk devices:
# virt-df -t /dev/sda
Filesystem 1K-blocks Used Available Type
/dev/sda:hda1 25599996 11309448 14290552 Windows NTFS
/dev/sda:hda2 992016 93772 898244 Linux ext2/3
/dev/sda:F9VG/F9Root 23316072 7818164 15497908 Linux ext2/3
/dev/sda:F9VG/F9Swap 1015808 Linux swap
/dev/sda:RHEL51VG/RHEL51Root 22382184 7796640 14585544 Linux ext2/3
/dev/sda:RHEL51VG/RHEL51Swap 2031616 Linux swap
/dev/sda:VolGroup/FAT32Test 916736 4 914676 DOS/Windows
You can write the output to a CSV file (use --csv option) in order to
import the data easily into spreadsheets and databases.
Included also is an experimental command line tool called 'diskzip'
which intelligently compresses disk images by leaving out the bits
which aren't actually used in the filesystems / partitions / volume
groups contained within.
Rich.
--
Richard Jones, Emerging Technologies, Red Hat http://et.redhat.com/~rjones
virt-p2v converts physical machines to virtual machines. Boot with a
live CD or over the network (PXE) and turn machines into Xen guests.
http://et.redhat.com/~rjones/virt-p2v
15 years, 11 months
Paravirtualization with Fedora 7 in Pentium IV
by Gastón Keller
Hello, everybody. I'm planning to play with Xen (version 3.1.2) in a
machine with a Pentium IV and 2 GB of memory. Fedora 7 is the
installed OS (kernel 2.6.21-7.fc7xen), so I guess I'm going to use
Fedora 7 for guests as well (can I use Fedora 8 for guests?).
I'm considering using a second disk of 140 GB with LVM, in order to
change the disk space allocated to the guests in case I need to.
My next consideration is how to deal with the installation tree. I
think that downloading the files from a repository each time I want to
create a new guest would be kind of silly, so I'm considering the
suggestion in the Fedora7VirtQuickStart [0] of downloading it once and
making it available from the host OS through NFS... or maybe through
HTTP using a web server (this last option is just a sudden thought
without much evaluation of its value =P ).
Any suggestion or comment? I mean. I might be doing something stupid
due to my lack of experience. :)
Thanks,
Gaston
PS: I'm trying to give all the info possible, not that is actually needed.
[0] http://fedoraproject.org/wiki/Docs/Fedora7VirtQuickStart#head-546553e2f5a...
--
La única verdad es la realidad.
15 years, 11 months
Custom bridge script; upgrade from Fedora 6 to Fedora 8
by Ask Bjørn Hansen
Hi,
Since upgrading from Fedora 6 to Fedora 8 my custom bridge script
stopped working. I need to have both eth0 and eth1 bridged into each
XM. My xen machines are just defined in old-style /etc/xen/foo
configuration files, like
vif = [ 'mac=00:16:3e:42:08:1d, bridge=xenbr0', 'mac=00:16:3e:
42:08:1e, bridge=xenbr1' ]
I've changed that to
vif = [ 'mac=00:16:3e:42:08:1d, bridge=eth0', 'mac=00:16:3e:42:08:1e,
bridge=eth1' ]
but when I do a "xm create foo" I still end up with the new interfaces
on the wrong bridge!
# brctl show
bridge name bridge id STP enabled interfaces
eth0 8000.0030488c8a26 no peth0
eth1 8000.0030488c8a27 no peth1
xenbr0 8000.feffffffffff no vif1.0
xenbr1 8000.feffffffffff no vif1.1
If I manually move the vifX.X interfaces to the eth0/eth1 bridges then
everything works.
This is my custom bridge script:
#!/bin/sh
dir=$(dirname "$0")
"$dir/network-bridge" "$@" netdev=eth1 bridge=eth1
"$dir/network-bridge" "$@" netdev=eth0 bridge=eth0
Any ideas?
- ask
--
http://develooper.com/ - http://askask.com/
15 years, 11 months
Guest boots OK with ATA disk (hdX) but not SCSI (sdX).
by Friedrich Clausen
Hi All,
(please feel free to refer me to the official Xen list if need be)
I am still using the same dom0 as outlined in :
https://www.redhat.com/archives/fedora-xen/2008-March/msg00006.html
I can successfully boot a domU using /dev/hda1 as rootfs but when I boot
using a scsi device it is unable to find its rootfs. I created an initrd,
preloading the sd_mod, in the hopes that that will fix it. The initrd was
created like so:
# mkinitrd -v --preload=sd_mod --preload=xenblk --with=xennet
--with=xenblktap --with=xenbus_be /tmp/test `uname -r`
# cp /tmp/test /boot/initrd-2.6.21.7-2.fc8xen.img
And the config of the guest is:
kernel = "/boot/vmlinuz-2.6.21.7-2.fc8xen"
ramdisk = "/boot/initrd-2.6.21.7-2.fc8xen.img"
extra = "ro enforcing=0"
root = "/dev/sda1"
memory = 256
name = "centos.5-1.64"
vif = [ '' ]
disk = ['phy:VolGroup00/LogVol00,sda1,w']
But is fails to boot, here are some possibly relevant messages with the
complete output at the end of this email :
Creating /dev
Creating initial device nodes
Setting up hotplug.
Creating block device nodes.
Loading scsi_mod.ko module
SCSI subsystem initialized
Loading sd_mod.ko module
Loading xenblk.ko module
register_blkdev: cannot get major 8 for sd
vbd vbd-2049: 19 xlvbd_add at /local/domain/0/backend/vbd/22/2049
register_blkdev: cannot get major 8 for sd
vbd vbd-2049: 19 xlvbd_add at /local/domain/0/backend/vbd/22/2049
XENBUS: Timeout connecting to device: device/vbd/2049 (state 6)
[ lines removed ]
unmounting old /dev
unmounting old /proc
unmounting old /sys
switchroot: mount failed: No such file or directory
Booting has failed.
Kernel panic - not syncing: Attempted to kill init!
I am glad I can successfully boot a guest but I would still like to get to
the bottom of this problem.
Thanks!
Fred.
--------------------------
Complete output
--------------------------
Using config file "./centos.conf.sda".
Started domain centos.5-1.64
Linux version 2.6.21.7-2.fc8xen (mockbuild(a)xenbuilder4.fedora.phx.redhat.com)
(gcc version 4.1.2 20070925 (Red Hat 4.1.2-33)) #1 SMP Fri Feb 15 12:34:28
EST 2008
Command line: root=/dev/sda1 ro enforcing=0
BIOS-provided physical RAM map:
Xen: 0000000000000000 - 0000000010800000 (usable)
end_pfn_map = 67584
Zone PFN ranges:
DMA 0 -> 67584
DMA32 67584 -> 67584
Normal 67584 -> 67584
early_node_map[1] active PFN ranges
0: 0 -> 67584
No mptable found.
PERCPU: Allocating 26496 bytes of per cpu data
Built 1 zonelists. Total pages: 63160
Kernel command line: root=/dev/sda1 ro enforcing=0
Initializing CPU#0
PID hash table entries: 1024 (order: 10, 8192 bytes)
Xen reported: 2327.484 MHz processor.
Console: colour dummy device 80x25
Dentry cache hash table entries: 32768 (order: 6, 262144 bytes)
Inode-cache hash table entries: 16384 (order: 5, 131072 bytes)
Software IO TLB disabled
Memory: 243620k/270336k available (2265k kernel code, 18172k reserved, 1351k
data, 200k init)
Calibrating delay using timer specific routine.. 4658.18 BogoMIPS
(lpj=2329090)
Security Framework v1.0.0 initialized
SELinux: Initializing.
selinux_register_security: Registering secondary module capability
Capability LSM initialized as secondary
Mount-cache hash table entries: 256
CPU: L1 I cache: 32K, L1 D cache: 32K
CPU: L2 cache: 4096K
CPU: Physical Processor ID: 0
CPU: Processor Core ID: 0
SMP alternatives: switching to UP code
Freeing SMP alternatives: 28k freed
Brought up 1 CPUs
NET: Registered protocol family 16
Brought up 1 CPUs
PCI: Fatal: No config space access function found
PCI: setting up Xen PCI frontend stub
ACPI: Interpreter disabled.
Linux Plug and Play Support v0.97 (c) Adam Belay
pnp: PnP ACPI: disabled
xen_mem: Initialising balloon driver.
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
PCI: System does not support PCI
PCI: System does not support PCI
NetLabel: Initializing
NetLabel: domain hash size = 128
NetLabel: protocols = UNLABELED CIPSOv4
NetLabel: unlabeled traffic allowed by default
NET: Registered protocol family 2
IP route cache hash table entries: 2048 (order: 2, 16384 bytes)
TCP established hash table entries: 8192 (order: 5, 196608 bytes)
TCP bind hash table entries: 8192 (order: 5, 131072 bytes)
TCP: Hash tables configured (established 8192 bind 8192)
TCP reno registered
checking if image is initramfs... it is
Freeing initrd memory: 8336k freed
audit: initializing netlink socket (disabled)
audit(1204798687.726:1): initialized
VFS: Disk quotas dquot_6.5.1
Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
ksign: Installing public key data
Loading keyring
io scheduler noop registered
io scheduler anticipatory registered
io scheduler deadline registered
io scheduler cfq registered (default)
pci_hotplug: PCI Hot Plug PCI Core version: 0.5
rtc: IRQ 8 is not free.
Non-volatile memory driver v1.2
Linux agpgart interface v0.102 (c) Dave Jones
RAMDISK driver initialized: 16 RAM disks of 16384K size 4096 blocksize
input: Macintosh mouse button emulation as /class/input/input0
Xen virtual console successfully installed as xvc0
Linux version 2.6.21.7-2.fc8xen (mockbuild(a)xenbuilder4.fedora.phx.redhat.com)
(gcc version 4.1.2 20070925 (Red Hat 4.1.2-33)) #1 SMP Fri Feb 15 12:34:28
EST 2008
Command line: root=/dev/sda1 ro enforcing=0
BIOS-provided physical RAM map:
Xen: 0000000000000000 - 0000000010800000 (usable)
end_pfn_map = 67584
Zone PFN ranges:
DMA 0 -> 67584
DMA32 67584 -> 67584
Normal 67584 -> 67584
early_node_map[1] active PFN ranges
0: 0 -> 67584
No mptable found.
PERCPU: Allocating 26496 bytes of per cpu data
Built 1 zonelists. Total pages: 63160
Kernel command line: root=/dev/sda1 ro enforcing=0
Initializing CPU#0
PID hash table entries: 1024 (order: 10, 8192 bytes)
Xen reported: 2327.484 MHz processor.
Console: colour dummy device 80x25
Dentry cache hash table entries: 32768 (order: 6, 262144 bytes)
Inode-cache hash table entries: 16384 (order: 5, 131072 bytes)
Software IO TLB disabled
Memory: 243620k/270336k available (2265k kernel code, 18172k reserved, 1351k
data, 200k init)
Calibrating delay using timer specific routine.. 4658.18 BogoMIPS
(lpj=2329090)
Security Framework v1.0.0 initialized
SELinux: Initializing.
selinux_register_security: Registering secondary module capability
Capability LSM initialized as secondary
Mount-cache hash table entries: 256
CPU: L1 I cache: 32K, L1 D cache: 32K
CPU: L2 cache: 4096K
CPU: Physical Processor ID: 0
CPU: Processor Core ID: 0
SMP alternatives: switching to UP code
Freeing SMP alternatives: 28k freed
Brought up 1 CPUs
NET: Registered protocol family 16
Brought up 1 CPUs
PCI: Fatal: No config space access function found
PCI: setting up Xen PCI frontend stub
ACPI: Interpreter disabled.
Linux Plug and Play Support v0.97 (c) Adam Belay
pnp: PnP ACPI: disabled
xen_mem: Initialising balloon driver.
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
PCI: System does not support PCI
PCI: System does not support PCI
NetLabel: Initializing
NetLabel: domain hash size = 128
NetLabel: protocols = UNLABELED CIPSOv4
NetLabel: unlabeled traffic allowed by default
NET: Registered protocol family 2
IP route cache hash table entries: 2048 (order: 2, 16384 bytes)
TCP established hash table entries: 8192 (order: 5, 196608 bytes)
TCP bind hash table entries: 8192 (order: 5, 131072 bytes)
TCP: Hash tables configured (established 8192 bind 8192)
TCP reno registered
checking if image is initramfs... it is
Freeing initrd memory: 8336k freed
audit: initializing netlink socket (disabled)
audit(1204798687.726:1): initialized
VFS: Disk quotas dquot_6.5.1
Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
ksign: Installing public key data
Loading keyring
io scheduler noop registered
io scheduler anticipatory registered
io scheduler deadline registered
io scheduler cfq registered (default)
pci_hotplug: PCI Hot Plug PCI Core version: 0.5
rtc: IRQ 8 is not free.
Non-volatile memory driver v1.2
Linux agpgart interface v0.102 (c) Dave Jones
RAMDISK driver initialized: 16 RAM disks of 16384K size 4096 blocksize
input: Macintosh mouse button emulation as /class/input/input0
Xen virtual console successfully installed as xvc0
Event-channel device installed.
usbcore: registered new interface driver hiddev
usbcore: registered new interface driver usbhid
drivers/usb/input/hid-core.c: v2.6:USB HID core driver
PNP: No PS/2 controller found. Probing ports directly.
i8042.c: No controller found.
mice: PS/2 mouse device common for all mice
TCP bic registered
Initializing XFRM netlink socket
NET: Registered protocol family 1
NET: Registered protocol family 17
XENBUS: Device with no driver: device/vbd/2049
XENBUS: Device with no driver: device/vif/0
XENBUS: Device with no driver: device/console/0
drivers/rtc/hctosys.c: unable to open rtc device (rtc0)
Freeing unused kernel memory: 200k freed
Write protecting the kernel read-only data: 981k
Red Hat nash version 6.0.19 starting
Mounting proc filesystem
Mounting sysfs filesystem
Creating /dev
Creating initial device nodes
Setting up hotplug.
Creating block device nodes.
Loading scsi_mod.ko module
SCSI subsystem initialized
Loading sd_mod.ko module
Loading xenblk.ko module
register_blkdev: cannot get major 8 for sd
vbd vbd-2049: 19 xlvbd_add at /local/domain/0/backend/vbd/22/2049
register_blkdev: cannot get major 8 for sd
vbd vbd-2049: 19 xlvbd_add at /local/domain/0/backend/vbd/22/2049
XENBUS: Timeout connecting to device: device/vbd/2049 (state 6)
Loading ehci-hcd.ko module
Loading ohci-hcd.ko module
Loading uhci-hcd.ko module
USB Universal Host Controller Interface driver v3.0
Loading mbcache.ko module
Loading jbd.ko module
Loading ext3.ko module
Loading libata.ko module
Loading ahci.ko module
Waiting for driver initialization.
Loading ata_generic.ko module
Loading usb-storage.ko module
Initializing USB Mass Storage driver...
usbcore: registered new interface driver usb-storage
USB Mass Storage support registered.
Waiting for driver initialization.
stabilized: stat /proc/bus/usb/devices: No such file or directory
Loading xennet.ko module
netfront: Initialising virtual ethernet driver.
netfront: device eth0 has copying receive path.
Loading xenbus_be.ko module
Loading xenblktap.ko module
Creating root device.
Mounting root filesystem.
mount: could not find filesystem '/dev/root'
Setting up other filesystems.
Setting up new root fs
setuproot: moving /dev failed: No such file or directory
no fstab.sys, mounting internal defaults
setuproot: error mounting /proc: No such file or directory
setuproot: error mounting /sys: No such file or directory
Switching to new root and running init.
unmounting old /dev
unmounting old /proc
unmounting old /sys
switchroot: mount failed: No such file or directory
Booting has failed.
Kernel panic - not syncing: Attempted to kill init!
--------------------------
End Complete output
--------------------------
15 years, 11 months
Weird xen network problem after upgrade
by Andy Burns
Host machine was running F7 no problems, upgraded via yum to F8, no
problems with deps, all went smoothly, installed latest fedora-updates
versions of everything.
Rebooted host, but found I had lost contact with it over the LAN, even
though the machine is on a datacentre this not a disaster because I
have remote serial port access to this machine, so I PXE booted into
rescue mode from an F8 repo I have locally, modified grub.conf to set
xen and linux to use serial console and got logged in as root OK
Networking showed the eth0 had been renamed to peth0, the eth0 bridge
created, peth0 enslaved to eth0 (virbr0 and vnet0 bridges also created
but I don't actually use those)
The problem is the IP address that ifcfg-eth0 assigns statically to
[p]eth0 ends up assigned assigned to NIC eth1 instead of bridge eth0
(won't work as that NIC is connected to a different VLAN intended for
iSCSI access).
As soon as I remove the correct IP address from the wrong NIC with
ip addr del x.x.x.x/24 dev eth1
ip link set down eth1
the same IP address somehow gets re-incarnated on the eth0 bridge!
So I manually remove all addresses and shutdown all interfaces, and
restart networking
ip addr del x.x.x.x/24 dev eth0
ip link set down eth0
brctl delif eth0 peth0,
brctl delbr eth0,
virsh net-destroy virbr0
virsh net-destroy vnet0
ip link set name eth0 dev peth0 (to rename peth0 back to eth0)
service network start
this correctly brings up only eth0 and assigns correct IP address and routes
at this point "network-bridge status" seems confused about NICs, it
seems to see two copies of eth0 and not to see eth1
# /etc/xen/scripts/network-bridge status
============================================================
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast qlen 1000
link/ether 00:04:23:d3:3c:10 brd ff:ff:ff:ff:ff:ff
inet 172.20.1.2/24 brd 172.20.1.255 scope global eth0
inet6 fe80::204:23ff:fed3:3c10/64 scope link
valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast qlen 1000
link/ether 00:04:23:d3:3c:10 brd ff:ff:ff:ff:ff:ff
inet 172.20.1.2/24 brd 172.20.1.255 scope global eth0
inet6 fe80::204:23ff:fed3:3c10/64 scope link
valid_lft forever preferred_lft forever
bridge name bridge id STP enabled interfaces
172.20.1.0/24 dev eth0 proto kernel scope link src 172.20.1.2
169.254.0.0/16 dev eth0 scope link
default via 172.20.1.1 dev eth0
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
172.20.1.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0
169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0 eth0
0.0.0.0 172.20.1.1 0.0.0.0 UG 0 0 0 eth0
============================================================
Then I then run "network-bridge start" the script properly renames
eth0 to peth0, re-creates the eth0 bridge, enslaves peth0 to eth0 and
moves the IP address, MAC address, routes over to eth0, everything is
working properly.
Yet following a reboot it goes wrong again just like before.
Any ideas what is confusing network-bridge on reboot, when it works if
manually run after networking has been shutdown?
15 years, 11 months
