On Thu, May 18, 2017 at 09:48:02AM -0500, Gary R Hook wrote:
> On 05/18/2017 03:16 AM, Roger Pau Monné wrote:
> >
> > So using your example, the config file should look like:
> >
> > extra = "root=/dev/xvda1 console=hvc0"
> > kernel = "/root/64/vmlinuz-4.11.0-pvh+"
> > ramdisk = "/root/64/initrd.
On 05/18/2017 03:16 AM, Roger Pau Monné wrote:
So using your example, the config file should look like:
extra = "root=/dev/xvda1 console=hvc0"
kernel = "/root/64/vmlinuz-4.11.0-pvh+"
ramdisk = "/root/64/initrd.img-4.11.0-pvh+"
builder="hvm"
device_model_version="none"
memory = 4096
name = "sosp
On Wed, May 17, 2017 at 07:07:25PM -0500, Gary R Hook wrote:
> On 5/16/2017 12:13 PM, Boris Ostrovsky wrote:
> > On 05/16/2017 11:52 AM, Gary R Hook wrote:
> > A PVH guest's config looks something like
> > > > kernel="/root/64/vmlinux"
> > > May I ask from whence this kernel came?
> > One of 4
On 5/16/2017 12:13 PM, Boris Ostrovsky wrote:
On 05/16/2017 11:52 AM, Gary R Hook wrote:
A PVH guest's config looks something like
kernel="/root/64/vmlinux"
May I ask from whence this kernel came?
One of 4.11's rcs. Make sure you set CONFIG_XEN_PVH in your .config file.
Please excuse my
On Tue, May 16, 2017 at 6:13 PM, Boris Ostrovsky
wrote:
> On 05/16/2017 11:52 AM, Gary R Hook wrote:
>> On 05/15/2017 09:54 PM, Boris Ostrovsky wrote:
>>>
>>
>> Possibly stupid question time...
>>
>>> On 05/15/2017 03:51 PM, Gary R Hook wrote:
>>>
2) Or, perhaps more importantly, what disti
On 05/16/2017 11:52 AM, Gary R Hook wrote:
> On 05/15/2017 09:54 PM, Boris Ostrovsky wrote:
>>
>
> Possibly stupid question time...
>
>> On 05/15/2017 03:51 PM, Gary R Hook wrote:
>>
>>> 2) Or, perhaps more importantly, what distinguishes said guest?
>>
>> Simplifying things a bit, it's an HVM gu
On 05/16/2017 04:36 AM, Andrew Cooper wrote:
On 16/05/17 03:54, Boris Ostrovsky wrote:
2) Or, perhaps more importantly, what distinguishes said guest?
Simplifying things a bit, it's an HVM guest that doesn't have device
model (i.e. qemu) and which is booted directly (i.e. without hvmloader
On 05/15/2017 09:54 PM, Boris Ostrovsky wrote:
Possibly stupid question time...
On 05/15/2017 03:51 PM, Gary R Hook wrote:
2) Or, perhaps more importantly, what distinguishes said guest?
Simplifying things a bit, it's an HVM guest that doesn't have device
model (i.e. qemu) and which is
On 16/05/17 03:54, Boris Ostrovsky wrote:
>
>> 2) Or, perhaps more importantly, what distinguishes said guest?
>
> Simplifying things a bit, it's an HVM guest that doesn't have device
> model (i.e. qemu) and which is booted directly (i.e. without hvmloader)
The "booted directly" isn't relevant h
On Mon, May 15, 2017 at 10:54:19PM -0400, Boris Ostrovsky wrote:
[...]
> An PVH guest's config looks something like
>
> kernel="/root/64/vmlinux"
> builder="hvm"
> device_model_version="none"
> extra="root=/dev/xvda1 console=hvc0"
> memory=8192
> vcpus=2
>
On 05/15/2017 03:51 PM, Gary R Hook wrote:
So I've been slogging through online docs and the code, trying to
understand where things stand with PVH.
I think my primary questions are:
1) How do I identify a PVHv2/HVMlite guest?
[root@dhcp-burlington7-2nd-B-east-10-152-55-52 ~]# dmesg | grep
So I've been slogging through online docs and the code, trying to
understand where things stand with PVH.
I think my primary questions are:
1) How do I identify a PVHv2/HVMlite guest?
2) Or, perhaps more importantly, what distinguishes said guest?
I've got Xen 4.9 unstable built/installed/bo
12 matches
Mail list logo
